Fixing the mpi4py library rename issue

[Keaton Burns]

Hi all,

Just wanted to send out a note saying that the library rename in mpi4py 2.0.0 that has been causing issues has a real fix on the horizon: there’s been a PR to h5py that works around the issue by building a little config file during the python setup to direct cython on which name to import. The change is going to be included in h5py 2.6.0, but it’s not clear when that will be released. See:

https://github.com/h5py/h5py/pull/640

At that point, I guess we have 2 options:

1) Just change to the new library name in our own cython and require mpi4py >= 2.0.0 going forward
2) Implement the same config-based work around the support both.

Any thoughts? I don’t thing bumped the required mpi4py version is too big of a deal… that release also includes some major improvements in terms of wrapping for recent mpi features, etc.

-Keaton

[Ben Brown]

My vote would be to take path 1) and bump our stack to >= 2.0.0. 

Reasoning:
There's nothing we're relying on in the pre-2.0 world, we have a working >= 2.0 implementation, that implementation works under openmpi, and bumping to >= 2.0 fixes at lest one major stack problem (compiling on NASA/Pleiades under mpi-sgi).  With h5py also taking the steps to post-2.0, I don't think we have any other stack conflicts.

--Ben

-Keaton

--
You received this message because you are subscribed to the Google Groups "Dedalus Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dedalus-dev...@googlegroups.com.
To post to this group, send email to dedal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dedalus-dev/E4F6B36D-F0D7-42FF-95A7-3BE93D25B059%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Geoff Vasil]

I think everything worth anything should come with a 2 at the end. 

Sent from my iPhone

To view this discussion on the web visit https://groups.google.com/d/msgid/dedalus-dev/CAHqBLzz3q3GgAD39xADZxGZbnsqCKwvfGQMNf%3DHyx1C07CzLvw%40mail.gmail.com.