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 michael.foord
Recipients brett.cannon, eric.araujo, ezio.melotti, flox, gregory.p.smith, michael.foord, pitrou, r.david.murray, rhettinger
Date 2010-11-29.11:24:13
SpamBayes Score 3.928129e-09
Marked as misclassified No
Message-id <1291029857.14.0.210648166213.issue10273@psf.upfronthosting.co.za>
In-reply-to
Content
Raymond - I created a new issue for moving the tests: issue 10572

However, it seems that you are incorrect in saying that Python practise is to avoid putting tests inside standard library packages. In fact current Python practise seems to be that where tests themselves are a package they are *always* inside the standard library package and *not* inside Lib/test. For example:  email, distutils, ctypes, importlib, json, lib2to3, sqlite3, tkinter, 

I couldn't see any counter-examples. There are no test packages inside Lib/test (other than leakers that are obviously a category of tests and not tests for a particular package).
History
Date User Action Args
2010-11-29 11:24:17michael.foordsetrecipients: + michael.foord, brett.cannon, rhettinger, gregory.p.smith, pitrou, ezio.melotti, eric.araujo, r.david.murray, flox
2010-11-29 11:24:17michael.foordsetmessageid: <1291029857.14.0.210648166213.issue10273@psf.upfronthosting.co.za>
2010-11-29 11:24:13michael.foordlinkissue10273 messages
2010-11-29 11:24:13michael.foordcreate