2009/9/21 Wolfgang Schnerring <w...@gocept.com>:
> 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
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
