[Python-Dev] Guidance regarding tests for the standard lib (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Wed Aug 14 02:50:23 CEST 2013

On 13 Aug 2013 19:40, "Victor Stinner" <victor.stinner at gmail.com> wrote:

Send the patch somewhere (ex: attach it to an email, or to the bug tracker, as you want), or give the error message, if you want some help. > Ask for a pronouncement on the PEP first, and then fix the test breakage later? Sometimes, it's possible to pronounce on a PEP without a working implementation. But it's easier to pronounce with a working implementation :-)

It's more typical for reference implementations to be "proof of concept" quality code, though. It's very rare to have a full, ready to apply patch (although we certainly don't complain if that happens!)

(To directly answer the original question: a test integration glitch isn't a blocker for PEP acceptance, just for actually committing the implementation)

Cheers, Nick.

Victor

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/ncoghlan%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130813/ff39110a/attachment-0001.html>

More information about the Python-Dev mailing list