[Python-Dev] PEP 386 and PEP 345

Brett Cannon brett at python.org
Wed Jan 6 06:20:30 CET 2010

On Tue, Jan 5, 2010 at 16:08, Tarek Ziadé <ziade.tarek at gmail.com> wrote:

> Hi,
> I think we've reached a consensus on those two PEPs.
> Although, there's one last point that was forgotten in the discussions
> : I've introduced "rc" in the pre-releases markers, so PEP 386 is
> compatible with Python's own version scheme.  "rc" comes right after
> "c" in the sorting. It's slightly redundant with the "c" marker but I
> don't think this really matters as long as consumers know how to order
> them (a < b < c < rc). I have also stated that "c" is the preferred
> marker for third party projects, from PEP 386 point of view.
> Is there anything else I can do to make those two PEPs accepted ?

As you said, consensus has been reached, so just Guido's BDFL stamp of
approval is all I can think of.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100105/a76cb75b/attachment-0007.htm>

More information about the Python-Dev mailing list