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 | torsten.becker |
|---|---|
| Recipients | torsten.becker |
| Date | 2011年08月22日.18:51:33 |
| SpamBayes Score | 0.0009024752 |
| Marked as misclassified | No |
| Message-id | <1314039095.43.0.38343392107.issue12819@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I have started an implementation of PEP 393 -- Flexible String Representation [1] on bitbucket [2]. Not all code is ported to use the new API yet, but the interpreter starts with the new unicode representation, all unit tests pass, and some micro benchmarks show potential. Please see the related wiki page [3] for details of my implementation. [1]: http://www.python.org/dev/peps/pep-0393/ [2]: https://bitbucket.org/t0rsten/pep-393 [2]: http://wiki.python.org/moin/SummerOfCode/2011/PEP393 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年08月22日 18:51:41 | torsten.becker | set | recipients: + torsten.becker |
| 2011年08月22日 18:51:35 | torsten.becker | set | messageid: <1314039095.43.0.38343392107.issue12819@psf.upfronthosting.co.za> |
| 2011年08月22日 18:51:34 | torsten.becker | link | issue12819 messages |
| 2011年08月22日 18:51:34 | torsten.becker | create | |