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 pitrou
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, pitrou, r.david.murray, techtonik, vstinner
Date 2010-06-17.14:32:17
SpamBayes Score 0.011422041
Marked as misclassified No
Message-id <1276785139.1.0.556544341467.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
> Is this still the state of the art?  What about parsing overhead?

The io module has three modules:
- io.py just imports everything from _io
- _io is the default C implementation
- _pyio.py must be imported explicitly to get the pure Python implementation

=> no parsing overhead for the default case of importing the C implementation

> Is there direct regrtest support for this?

You can take a look at test_io, test_memoryio or test_heapq for inspiration.
History
Date User Action Args
2010-06-17 14:32:19pitrousetrecipients: + pitrou, lemburg, brett.cannon, amaury.forgeotdarc, belopolsky, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-17 14:32:19pitrousetmessageid: <1276785139.1.0.556544341467.issue7989@psf.upfronthosting.co.za>
2010-06-17 14:32:17pitroulinkissue7989 messages
2010-06-17 14:32:17pitroucreate