[Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Steven D'Aprano
Hi, I have raise a tracker item and PEP for adding a statistics module to the standard library: http://bugs.python.org/issue18606 http://www.python.org/dev/peps/pep-0450/ and I'm about to submit a patch containing my updated code and tests, but I've run into a problem with testing. My

Re: [Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Ethan Furman
On 08/13/2013 04:51 PM, Steven D'Aprano wrote: I have raise a tracker item and PEP for adding a statistics module to the standard library: http://bugs.python.org/issue18606 http://www.python.org/dev/peps/pep-0450/ The bug-tracker doesn't think you've submitted a CLA yet. If you haven't

Re: [Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Ethan Furman
On 08/13/2013 04:51 PM, Steven D'Aprano wrote: My question is, is it acceptable to post the code and tests to the tracker as-is, and ask for a pronouncement on the PEP first, and then fix the test breakage later? Certainly. -- ~Ethan~ ___

Re: [Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Victor Stinner
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

Re: [Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Nick Coghlan
On 13 Aug 2013 19:40, Victor Stinner victor.stin...@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?

Re: [Python-Dev] Guidance regarding tests for the standard lib

2013-08-13 Thread Terry Reedy
On 8/13/2013 7:51 PM, Steven D'Aprano wrote: http://bugs.python.org/issue18606 Tests at end of statistics.patch. and I'm about to submit a patch containing my updated code and tests, but I've run into a problem with testing. My existing tests use unittest, and follow the basic boilerplate