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 | belopolsky |
|---|---|
| Recipients | bdkearns, belopolsky, benjamin.peterson, josh.r, lemburg, tim.peters |
| Date | 2014年07月13日.15:53:56 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1405266836.77.0.37746324913.issue20858@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Here is the tuple hash caching thread that I mentioned above: https://mail.python.org/pipermail/python-dev/2003-August/037416.html Since the C code uses caching already, I don't think we need to discuss it any further. And the thread on tuples does not give any good reason not to cache anyways. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年07月13日 15:53:56 | belopolsky | set | recipients: + belopolsky, lemburg, tim.peters, benjamin.peterson, bdkearns, josh.r |
| 2014年07月13日 15:53:56 | belopolsky | set | messageid: <1405266836.77.0.37746324913.issue20858@psf.upfronthosting.co.za> |
| 2014年07月13日 15:53:56 | belopolsky | link | issue20858 messages |
| 2014年07月13日 15:53:56 | belopolsky | create | |