Terry Reedy writes: > "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > | The impression that many people (including python-dev regulars) have > | that there is a "policy" of "support" for both the current release > | (2.5) and the (still very widely used) previous release (2.4) is a > | real problem, and needs to be addressed.
> I agree that such mis-understanding should be addressed. So I now think a > paragraph summarizing Martin's info PEP, ending with "For details, see > PEPxxx.", would be a good idea. FWIW, after Martin's explanation, and considering the annoyance of keeping updates sync'ed (can PEPs be amended after acceptance, or only superseded by a new PEP, like IETF RFCs?), I tend to support Barry's suggestion of a brief listing of current releases and next planned, and "Python policy concerning release planning is defined by [the current version of] PEPxxx", with a link. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
