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 | lemburg |
|---|---|
| Recipients | amaury.forgeotdarc, jafo, lemburg, orivej, pitrou |
| Date | 2008年03月20日.14:34:33 |
| SpamBayes Score | 0.06926216 |
| Marked as misclassified | No |
| Message-id | <1206023674.55.0.839632337311.issue1943@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I've read the comments from Guido and Martin, but they don't convince me in changing my -1. As you say: it's difficult to get support for optimizations such a slicing and concatenation into the core. And that's exactly why I want to keep the door open for developers to add such support via extension modules. With the 8-bit string implementation this was never possible. With the Unicode implementation and the subclassing support for builtin types, it is possible to add support without having to go through all the hoops and discussions on python-dev or py3k lists. I'm also for making Python faster, but not if it limits future optimizations and produces dead-ends. The fact that such optimizations haven't been implemented yet doesn't really mean anything either - people are not yet using Unicode intensively enough to let the need arise. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月20日 14:34:34 | lemburg | set | spambayes_score: 0.0692622 -> 0.06926216 recipients: + lemburg, jafo, amaury.forgeotdarc, pitrou, orivej |
| 2008年03月20日 14:34:34 | lemburg | set | spambayes_score: 0.0692622 -> 0.0692622 messageid: <1206023674.55.0.839632337311.issue1943@psf.upfronthosting.co.za> |
| 2008年03月20日 14:34:33 | lemburg | link | issue1943 messages |
| 2008年03月20日 14:34:33 | lemburg | create | |