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 belopolsky
Recipients belopolsky, eric.araujo, holdenweb
Date 2010-07-04.17:18:06
SpamBayes Score 0.007638911
Marked as misclassified No
Message-id <1278263888.1.0.57514081846.issue9153@psf.upfronthosting.co.za>
In-reply-to
Content
Many demos already include a self-test:

$ grep '^def test(' Demo/*/*.py
Demo/classes/Complex.py:def test():
Demo/classes/Dates.py:def test(firstyear, lastyear):
Demo/classes/Range.py:def test():
Demo/classes/Vec.py:def test():
Demo/parser/test_parser.py:def test():
Demo/pdist/FSProxy.py:def test():
Demo/pdist/RCSProxy.py:def test():
Demo/pdist/cmdfw.py:def test():
Demo/pdist/cvslib.py:def test():
Demo/pdist/cvslock.py:def test():
Demo/rpc/mountclient.py:def test():
Demo/rpc/nfsclient.py:def test():
Demo/rpc/rnusersclient.py:def test():
Demo/rpc/rpc.py:def test():
Demo/scripts/markov.py:def test():
Demo/sockets/gopher.py:def test():
Demo/threads/Generator.py:def test():
Demo/threads/sync.py:def test():
Demo/turtle/tdemo_penrose.py:def test(l=200, n=4, fun=sun, startpos=(0,0), th=2):
 
I think the first step should be to run those from regrtest.  The next step would be to convert adhoc test functions into doctests or unit tests as appropriate.

Step zero, however, should be to decide which demos are worth keeping and which should be removed.
History
Date User Action Args
2010-07-04 17:18:08belopolskysetrecipients: + belopolsky, holdenweb, eric.araujo
2010-07-04 17:18:08belopolskysetmessageid: <1278263888.1.0.57514081846.issue9153@psf.upfronthosting.co.za>
2010-07-04 17:18:07belopolskylinkissue9153 messages
2010-07-04 17:18:06belopolskycreate