[Python-Dev] PEP 386 and dev repository versions workflow (original) (raw)
Tarek Ziadé ziade.tarek at gmail.com
Mon May 2 19:19:28 CEST 2011
- Previous message: [Python-Dev] PEP 386 and dev repository versions workflow
- Next message: [Python-Dev] Issue Tracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, May 2, 2011 at 7:14 PM, anatoly techtonik <techtonik at gmail.com> wrote:
http://guide.python-distribute.org/quickstart.html proposes suffixing version of a module in repository with 'dev' in a way that after release of '1.0' version, the repository version is changed to '2.0dev'. This makes sense, but it is not compatible with PEP 386, which suggests using 2.0.devN, where N is a repository revision number. I'd expand PEP 386 to include 2.0dev use case.
This is a typo I'll fix, thanks for noticing
-- anatoly t.
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com
-- Tarek Ziadé | http://ziade.org
- Previous message: [Python-Dev] PEP 386 and dev repository versions workflow
- Next message: [Python-Dev] Issue Tracker
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]