Thomas Lotze kirjoitti:
Lennart Regebro wrote:
2009/9/21 P.J. Eby p...@telecommunity.com:
Really? I would think 2to3_anything is not a valid keyword argument
name.
D'oh!
You are right. OK, other ideas?
The trivial one would be to use 2to3 as a postfix rather than as a
2009/9/22 Alex Grönholm alex.gronh...@nextday.fi
Thomas Lotze kirjoitti:
The trivial one would be to use 2to3 as a postfix rather than as a prefix.
use_2to3, convert_2to3_doctests, use_2to3_fixers?
OK, I'll go for this. Good enough. Discussion over. :)
--
Lennart Regebro: Python, Zope,
* Lennart Regebro rege...@gmail.com [2009-09-22 05:03]:
2to3_enabled, 2to3_convert_doctests, 2to3_fixers, ...
That works. Maybe just 2to3_doctests?
Really? I would think 2to3_anything is not a valid keyword argument name.
You are right. OK, other ideas?
Damn. It'll be downhill from there.
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
* Lennart Regebro rege...@gmail.com [2009-09-19 08:16]:
2009/9/19 Wolfgang Schnerring w...@wosc.de:
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
* Lennart Regebro rege...@gmail.com [2009-09-21 12:04]:
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.
Excellent! I think that covers it pretty well.
Also, feedback on the
2009/9/21 Wolfgang Schnerring w...@gocept.com:
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
At 10:15 PM 9/21/2009 +0200, Lennart Regebro wrote:
2009/9/21 Wolfgang Schnerring w...@gocept.com:
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?
Really? I
2009/9/21 P.J. Eby p...@telecommunity.com:
At 10:15 PM 9/21/2009 +0200, Lennart Regebro wrote:
2009/9/21 Wolfgang Schnerring w...@gocept.com:
My favourite colour: use 2to3 as the prefix (consistency helps, I
think), like so:
2to3_enabled, 2to3_convert_doctests, 2to3_fixers, ...
That
Lennart Regebro wrote:
2009/9/21 P.J. Eby p...@telecommunity.com:
Really? I would think 2to3_anything is not a valid keyword argument
name.
D'oh!
You are right. OK, other ideas?
The trivial one would be to use 2to3 as a postfix rather than as a prefix.
--
Thomas
2009/9/19 Wolfgang Schnerring w...@wosc.de:
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
Hiya all!
Tarek alerted me to that Martin v Löwis has checked in the great job
done during the DZUG-sprint of adding Python 3 support to the 0.6
maintenance branch. I tested it yesterday, and I have two comments.
1. First a little heads up!!
When I tested this yesterday, I first ran the tests
2009/9/18 Lennart Regebro rege...@gmail.com:
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
Lennart Regebro kirjoitti:
2009/9/18 Lennart Regebro rege...@gmail.com:
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
2009/9/18 Alex Grönholm alex.gronh...@nextday.fi:
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.
I haven't had a good chance to check out
2009/9/18 Lennart Regebro rege...@gmail.com:
2009/9/18 Alex Grönholm alex.gronh...@nextday.fi:
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.
2009/9/18 Tarek Ziadé ziade.ta...@gmail.com:
Also, a full example on how to use distribute with python 3 in the docs/
would be nice to have.
Absolutely.
btw, I propose to release 0.6.2 as soon as py3 support has been tested
by a few more people.
Right. I'm working on also reimplementing the
2009/9/18 Lennart Regebro rege...@gmail.com:
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
* Lennart Regebro rege...@gmail.com [2009-09-18 15:46]:
2009/9/18 Alex Grönholm alex.gronh...@nextday.fi:
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
19 matches
Mail list logo
