This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients brett.cannon, ezio.melotti, georg.brandl, lemburg, ncoghlan, pitrou, r.david.murray, sbt, terry.reedy, tshepang, zach.ware
Date 2014-04-20.20:43:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7dFTRqMmyNdH-b+QUgOdS1+VGDd3LSUgiQz4yw-Xk4YaA@mail.gmail.com>
In-reply-to <1398008701.89.0.526554124831.issue18967@psf.upfronthosting.co.za>
Content
PEP 462 is months away from going anywhere, and I personally find the
current NEWS handling a major barrier to feeling inclined to work on bug
fixes.

The status quo will *definitely* be PEP 462 incompatible, though, since it
would typically prevent applying the same patch to multiple branches.
History
Date User Action Args
2014-04-20 20:43:42ncoghlansetrecipients: + ncoghlan, lemburg, brett.cannon, georg.brandl, terry.reedy, pitrou, ezio.melotti, r.david.murray, tshepang, sbt, zach.ware
2014-04-20 20:43:42ncoghlanlinkissue18967 messages
2014-04-20 20:43:42ncoghlancreate