2008/10/5 Kevin Teague <kevin at bud.ca>: > on Python 3 after running it through 2to3. The source code is different so > that to me suggests different version numbers - but the API will be the > same, so maybe the same version number should be used? That is should there > be? > > foobar-1.0-py2.6.tar.gz > foobar-1.0-py3.0.tar.gz More likely, in this way: foobar-1.0-py2.tar.gz foobar-1.0-py3.tar.gz > Or should it be something like? > > foobar-1.0.tar.gz # Python 2 > foobar-1.1.tar.gz # Python 3 The problem here is that I can foresee libs or apps that have a mixed path, starting to support Py 3 at some point, and deprecating the Py 2 support after a while: foobar-1.0.tar.gz # Py 2 foobar-1.1.tar.gz # Py 2 & 3 foobar-1.2.tar.gz # Py 2 & 3 foobar-1.3.tar.gz # Py 2 & 3 foobar-1.4.tar.gz # Py 2 & 3 foobar-1.5.tar.gz # Py 3 Regards, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4