Skip to content

Avoid initializing ase.parallel.world at import time

Ask Hjorth Larsen requested to merge no-initialize-ase-world into master

ASE has a test to ensure that world is not initialized at import time. This test currently fails.

The test fails because GPAW initializes world at import time, in order to verify that world is correct.

The reason why the ASE test exists in the first place is that GPAW's and ASE's worlds must be the same.

It is for the same reason that GPAW checks that they have the same size.

We need to get rid of this cyclic hell.

Merge request reports