Lennart Regebro kirjoitti:

2009/9/18 Lennart Regebro :

...

2. There is now a build_py that will run 2to3 on the code. That's cool, but there doesn't seem to be a way to enable it. It looks for a setuptools.use_2to3 attribute to check if it should be used, but I couldn't see a way of setting that. Passing it in as a parameter to setup() gives you a warning, that the parameter is unknown.

How should it be done?

OK, seems i can do this with import setuptools setuptools.run_2to3 = True

This should not be necessary. The run_2to3 keyword argument to setup() is the way to go. I haven't had a good chance to check out Martin's work, but if that option is missing, I'll add it.

2009/9/18 Lennart Regebro :

2009/9/18 Alex Grönholm :

...

This should not be necessary. The run_2to3 keyword argument to setup() is the way to go.

Yeah, but that's not added. But if all others agree that a keyword is better then we should go with that.

+1

...

I haven't had a good chance to check out Martin's work, but if that option is missing, I'll add it.

Nah, I'll already added it, but not pushed it yet. :) I want confirmation from the list, and some more testing. (I'm using zope.interface as a testing platform at the moment).

Also, a full example on "how to use distribute with python 3" in the docs/ would be nice to have. btw, I propose to release 0.6.2 as soon as py3 support has been tested by a few more people. Tarek -- Tarek Ziadé | http://ziade.org | オープンソースはすごい!

2009/9/18 Lennart Regebro :

Right. I'm working on also reimplementing the rest of the 2to3 options into keywords, and I'll make a quick documentation of this, and notify people here. Should be done today or tomorrow.

Checked in. Also made the test command run 2to3 if necessary. It now works on my zope.interfaces Python3-branch. Will try to document this during the weekend. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64

2009/9/19 Wolfgang Schnerring :

The idea of this *not* being a setup() argument was to keep compatibility with setuptools (since it will complain about arguments it doesn't understand). This would enable a package to use setuptools or distribute (or whatever ;) for python2, and only require distribute for the python3/2to3 goodness.

Ah, OK. Well, I added the extra parameters in via an **extras dict in zope.interfaces, so I didn't think of that. Still, I probably prefer that we keep one API, and not two. :) The warning that you'll get under setuptools is not an actual problem is it? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64

2009/9/21 Wolfgang Schnerring :

Very much agreed, let's use setup() arguments.

Great. I've checked in some docs too, I expanded the section on Python 3 support and ended up creating a new document, python3.txt. Feedback on that is appreciated. Also, feedback on the naming of the keywords is appreciated. Yes, I know it's bikeshedding, but I find the current parameter names clunky, but have no better ideas. ``run_2to3`` Convert the source code from Python 2 to Python 3 with 2to3 during the build process. ``convert_doctests_2to3`` List of doctest source files that need to be converted with 2to3. See :doc:`python3` for more details. ``additional_2to3_fixers`` A list of modules to serach for additional fixers to be used during the 2to3 conversion. See :doc:`python3` for more details. If better names for these can be invented before the first release that would probably be beneficial. (run_2to3 I find OK, though, it's basically the other ones). -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64

2009/9/21 Wolfgang Schnerring :

My favourite colour: use 2to3 as the prefix (consistency helps, I think), like so:  2to3_enabled, 2to3_convert_doctests, 2to3_fixers, ...

That works. Maybe just 2to3_doctests? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64