On 11 November 2013 17:26, Marius Gedminas <[email protected]> wrote: > On Mon, Nov 11, 2013 at 04:29:32PM +0000, Paul Moore wrote: >> I'm trying to convert a setup.py to use setuptools (specifically the >> docutils build, FWIW). The existing setup.py has some custom command >> stuff to run 2to3 on build. > > Aside: I believe there's consensus now that 2to3 is not the best way to > support Python 2.x and 3.x. It's not that hard to have a single source > tree in a portable subset of Python 2.x and 3.x. See python3porting.com > and https://pypi.python.org/pypi/six.
Yes, I realise that. I'm not a fan of 2to3 at all myself, but it's what docutils uses and I'm not trying to do a full docutils port to shared source, just a quick local fork of setup.py to allow me to make some simple changes (using entry points rather than custom scripts, in particular). I only started looking at the 2to3 stuff because docutils' setup.py does some complex distutils customisation that I thought might give setuptools some problems. And as all it was doing was implementing things that are built into setuptools, it seemed worth looking at as a simplification. > I wouldn't be surprised to learn that bdist_wheel doesn't support > use_2to3, but I don't actually *know* that for a fact, since I never > used 2to3. It's possible I guess. But I thought bdist_wheel used the normal build command, so stuff like 2to3 support should be unchanged. Thanks for the comments anyway, Paul _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
