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, jafo, lemburg, orivej, pitrou |
| Date | 2008年03月20日.11:32:37 |
| SpamBayes Score | 0.09027668 |
| Marked as misclassified | No |
| Message-id | <1206012759.83.0.71634043205.issue1943@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hi, Marc-André, I'm all for "real-life" benchmarks if someone proposes some. Until that we have to live with micro-benchmarks, which seems to be the method used for other CPython optimizations by the way. You are talking about slicing optimizations but you forget that the "lazy slices" idea has been shot down by Guido and others when proposed by Larry Hastings (with a patch) some time ago. Also the "lazy slices" patch was for 8-bit strings, which *are* variable-size objects, which seems to counter your argument that variable-size Unicode objects would prevent making such optimizations. As I said the freelist changes actually have mixed consequences, and in general don't improve much (and that improvement is just backed by micro-benchmarks after all... why would it be more convincing than the far greater improvement brought by making Unicode objects variable-size objects?). Why wouldn't you express your arguments in the python-3000 thread I launched one month ago, so that at least there is a clear picture of the different arguments for and against this approach? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月20日 11:32:39 | pitrou | set | spambayes_score: 0.0902767 -> 0.09027668 recipients: + pitrou, lemburg, jafo, amaury.forgeotdarc, orivej |
| 2008年03月20日 11:32:39 | pitrou | set | spambayes_score: 0.0902767 -> 0.0902767 messageid: <1206012759.83.0.71634043205.issue1943@psf.upfronthosting.co.za> |
| 2008年03月20日 11:32:38 | pitrou | link | issue1943 messages |
| 2008年03月20日 11:32:37 | pitrou | create | |