about to collapse for some sleep -- let me just comment on cython: the reason is the same as with any other 3rd party dependency -- if we fix some issue in cython package which would relfect itself in generated code, we would just need to binNMU all dependent packages instead of requiring source full uploads manually recythoning sources
and -- what if we leave python2 builds to default (i.e. with --force) which would regenerate using system wide cython -- then build python3 one without --force thus reusing (re)generated files by python2 rules? ;) On Mon, 04 Jun 2012, Bradley M. Froehle wrote: > What is the benefit of running the system wide cython? I do see that some > other cython-based packages do choose to run cython (or at least > build-depend on cython). �Unfortunately the current lack of a > python3-cython package would prevent us from running cython on the > python3-mpi4py build anyway. �:( > bin/python-mpi: Yes, it's a new "feature" but it is of questionable > relevance. �I have yet to encounter an actual use case, as the "from > mpi4py import MPI" line in your code runs the same MPI_Init routine. > �Perhaps this might be of use with certain versions of MPI? > �Regardless, > the�setup.py script installs this file into > /.../dist-packages/mpi4py/bin/python-mpi which is outside the default > PATH. �I suppose we should move this to /usr/bin/pythonX.Y-mpi? > The lib-pmpi/*.so files do seem to be used by some profiling feature. > �I've re-included them and updated the package. -- 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
