[Python-Dev] Rework nntlib? (original) (raw)
Jesse Noller jnoller at gmail.com
Wed Sep 15 20:02:40 CEST 2010
- Previous message: [Python-Dev] Rework nntlib?
- Next message: [Python-Dev] Rework nntlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Sep 15, 2010 at 1:48 PM, Devin Cook <devin.c.cook at gmail.com> wrote:
On Wed, Sep 15, 2010 at 11:37 AM, Jesse Noller <jnoller at gmail.com> wrote:
You need people with the time and willingness to download, install and run production code on the releases. This might be getting off-topic, but maybe not as many people as you think. How many projects in pypi provide unittests? That's at least more tests to add to the ones already being run in the stdlib. -Devin
And who do you get to maintain all the new tests and buildbots you spawn from running hundreds of community projects unittests? How do you know those tests are real, and actually work? You quickly outstrip the ability of the core team to stay on top of it, and you run into issues in the past akin to the community build bots project.
jesse
- Previous message: [Python-Dev] Rework nntlib?
- Next message: [Python-Dev] Rework nntlib?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]