2010/3/30 David Cournapeau <da...@silveregg.co.jp>:
> Currently, when building numpy with python 3, the 2to3 conversion
> happens before calling any distutils command. Was there a reason for
> doing it as it is done now ?
This allowed 2to3 to also port the various setup*.py files and
numpy.distutils, and implementing it this way required the minimum
amount of work and understanding of distutils -- you need to force it
to proceed with the build using the set of output files from 2to3.
> I would like to make a proper numpy.distutils command for it, so that it
> can be more finely controlled (in particular, using the -j option). It
> would also avoid duplication in scipy.
Are you sure you want to mix distutils in this? Wouldn't it only
obscure how things work?
If the aim is in making the 2to3 processing reusable, I'd rather
simply move tools/py3tool.py under numpy.distutils (+ perhaps do some
cleanups), and otherwise keep it completely separate from distutils.
It could be nice to have the 2to3 conversion parallelizable, but there
are probably simple ways to do it without mixing distutils in.
But if you think this is really worth doing, go ahead.
Pauli
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
