I am about to test 1.3 on s390 (lazy me waiting for cython to be installed ;) )
as for python-mpi binaries ... you have done all the work -- so I guess it wouldn't be fair to not use master-with-python-mpi (yet to review)... alternatively due to your arguments we can stay without it indeed -- you make decision ;) On Tue, 05 Jun 2012, Bradley M. Froehle wrote: > Letting python2 build with the default does regenerate cython bindings > which then do get picked up by the python3 build. �Smart :) �I've > updated�[1]https://github.com/bfroehle/debian-mpi4py > I still think we do not need to include the python-mpi binaries. From the > install.rst file: > � � �Some MPI-1 implementations **do require** the actual > � � �command line arguments to be passed in :c:func:`MPI_Init()`. In > � � �this case, you will need to use a rebuilt, MPI-enabled, Python > � � �interpreter executable. *MPI for Python* has some support for > � � �alleviating you from this task. Check the instructions at > � � �:ref:`python-mpi` in the appendix. > As far as I know OpenMPI, MPICH2, and LAM [the various MPI implementations > included by mpi-default-dev] all support MPI-2 and hence this specialized > python-mpi binary is not necessary. > Nonetheless if we do want to include the python-mpi binaries I started a > > branch�[2]https://github.com/bfroehle/debian-mpi4py/compare/master...master-with-python-mpi > -Brad > References > Visible links > 1. https://github.com/bfroehle/debian-mpi4py > 2. > https://github.com/bfroehle/debian-mpi4py/compare/master...master-with-python-mpi -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
