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 gregory.p.smith
Recipients alex, brett.cannon, gregory.p.smith, santoso.wijaya, serhiy.storchaka, terry.reedy, tshepang
Date 2013-03-09.16:38:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It'd perhaps have been better if things like memoryview were never exposed to the user at all as a distinct type and became an internal implementation detail behind PyBytes and PyUnicode objects (they could hold a reference to something else or collapse that down to their own copy on their own terms, up to the particulars of the Python VM).

Anyways, the above is getting off topic for this issue.  I retract my memoryview suggestion; that belongs in its own issue.

An iterating version of str.split is indeed hard to add today IFF we are against a str.itersplit() method name or against an optional keyword only argument that'd cause split(iterator=True)'s return type to potentially be different.
Date User Action Args
2013-03-09 16:38:24gregory.p.smithsetrecipients: + gregory.p.smith, brett.cannon, terry.reedy, alex, santoso.wijaya, tshepang, serhiy.storchaka
2013-03-09 16:38:24gregory.p.smithsetmessageid: <>
2013-03-09 16:38:24gregory.p.smithlinkissue17343 messages
2013-03-09 16:38:24gregory.p.smithcreate