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 gvanrossum
Recipients georg.brandl, gvanrossum, larry, pitrou, sbt, serhiy.storchaka
Date 2013-10-14.22:23:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381789437.17.0.248706474412.issue19262@psf.upfronthosting.co.za>
In-reply-to
Content
What I need help with most right now is a suggestion of where the unittests should go. There are too many of them to all put in one file. Some options:

asyncio/test/*_test.py
asyncio/test/test_*.py
test/test_asyncio/<either of the above>

What's the best current practice?

(I also want to add some hacks so that the files can actually be identical in the stdlib and in the separate 3rd party repo, otherwise keeping the two in sync will be too much work.)
History
Date User Action Args
2013-10-14 22:23:57gvanrossumsetrecipients: + gvanrossum, georg.brandl, pitrou, larry, sbt, serhiy.storchaka
2013-10-14 22:23:57gvanrossumsetmessageid: <1381789437.17.0.248706474412.issue19262@psf.upfronthosting.co.za>
2013-10-14 22:23:57gvanrossumlinkissue19262 messages
2013-10-14 22:23:57gvanrossumcreate