On Wed, Mar 11, 2009 at 21:47, P.J. Eby <pje at telecommunity.com> wrote:
> Why not just invoke:
>> python3 -m unittest somemodule.somesuite
>> Then there are no dependencies on distutils or setuptools.
Because it needs to run 2to3 on the code first.
Also, python3 setup.py install will fail, becuase the installation
depends on setuptools, and then I need to do build_py_2to3 on the
code, which isn't going to work if the install program depends on
setuptools, as it hasn't been converted to Python3 yet.
The alternative, which seems less likely, is to rewrite setuptools to
run under Python 2.3, 2.4, 2.5, 2.6 and 3.0 without using 2to3. :-D
Or of course, continue having a separate source distribution for
Python 3 and a bit complicated development process, which is
survivable, but I don't think it's a good long term strategy.
--
Lennart Regebro: Pythonista, Barista, Notsotrista.
http://regebro.wordpress.com/
+33 661 58 14 64