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 alexandre.vassalotti, belopolsky, benjamin.peterson, pitrou
Date 2010-06-28.19:30:02
SpamBayes Score 0.0009970831
Marked as misclassified No
Message-id <1277753405.4.0.611383489425.issue9104@psf.upfronthosting.co.za>
In-reply-to
Content
In the new patch, issue9104.diff, I factored out import machinery into test.support.import_module_implementations and added it to a a couple of other test modules.  I did not attempt to improve all pickle tests.

The availability of import_module_implementations raises an interesting question of what to do in cases like heapq where one can potentially test 4 combinations of heapq/_heapq with pickle/_pickle.  Given that currently pickling of heapq objects is either not supported or not tested, we don't need to worry about it, but as parallel optimized/pure python module implementations proliferate, we may face exponential explosion of potential test cases.
History
Date User Action Args
2010-06-28 19:30:05belopolskysetrecipients: + belopolsky, pitrou, alexandre.vassalotti, benjamin.peterson
2010-06-28 19:30:05belopolskysetmessageid: <1277753405.4.0.611383489425.issue9104@psf.upfronthosting.co.za>
2010-06-28 19:30:03belopolskylinkissue9104 messages
2010-06-28 19:30:03belopolskycreate