I started putting together a list of standard library modules that are
also available on PyPI for the
https://wiki.python.org/moin/Python2orPython3 wiki page.
Dariusz Suchojad suggested it might be easier if there was a suitable
classifier to mark such modules rather than trying to keep a list on
On Thu, 2/1/14, Nick Coghlan ncogh...@gmail.com wrote:
Dariusz Suchojad suggested it might be easier if there was a
suitable classifier to mark such modules rather than trying to keep a
list on the wiki up to date by hand. Perhaps something like
On Thu, Jan 2, 2014 at 9:37 AM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
On Thu, 2/1/14, Nick Coghlan ncogh...@gmail.com wrote:
Dariusz Suchojad suggested it might be easier if there was a
suitable classifier to mark such modules rather than
On Thu, 2/1/14, Brett Cannon br...@python.org wrote:
Progamming Language :: Python :: Python2and3
or some such.
How is that any better than specifying the Python
2 classifier and the Python 3 one? One should specify every
individual version of
On Thu, Jan 2, 2014 at 11:12 AM, Vinay Sajip vinay_sa...@yahoo.co.ukwrote:
On Thu, 2/1/14, Brett Cannon br...@python.org wrote:
Progamming Language :: Python :: Python2and3
or some such.
How is that any better than specifying the Python
2
I guess my question then is why do you
care? If 2to3 is run at install time then it's a
cost, but it's one-time and if you really care you can
always create your own wheel of the translated code or
something.
Because I've written a packaging tool that doesn't use setup.py but instead
uses a
On 3 Jan 2014 08:20, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
I guess my question then is why do you
care? If 2to3 is run at install time then it's a
cost, but it's one-time and if you really care you can
always create your own wheel of the translated code or
something.
Because I've
