[Python-Dev] 3to2 0.1 alpha 1 released (original) (raw)
Joe Amenta amentajo at msu.edu
Tue Sep 1 07:10:35 CEST 2009
- Previous message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
- Next message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks Brett and Sridhar for the info. 3to2's version info has been PEP386-ified, and the latest version can always be found at http://pypi.python.org/pypi/3to2/ (the previous link will now generate an error).
--Joe
On Mon, Aug 31, 2009 at 3:25 PM, Brett Cannon <brett at python.org> wrote:
On Mon, Aug 31, 2009 at 12:18, Sridhar Ratnakumar<SridharR at activestate.com> wrote: > On Wed, 26 Aug 2009 15:55:54 -0700, Joe Amenta <amentajo at msu.edu> wrote: > >> -- 3to2 is now registered with PyPI. Did I do it right? > >> http://pypi.python.org/pypi/3to2/0.1%20alpha%201 > > Please fix the version number to not contain any whitespace characters. Also > set the
versionargument in setup(..) in your setup.py. And then you may > want to use theuploadcommand to upload the new tarball to PyPI. See > http://wiki.python.org/moin/Distutils/Tutorial for more details.See PEP 386 (http://www.python.org/dev/peps/pep-0386/) for what the current thinking on version numbers is. -Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090901/bdc5e704/attachment.htm>
- Previous message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
- Next message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]