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 vstinner
Recipients methane, ned.deily, rhettinger, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-09-29.19:48:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYiX9sJJ9wrx5Br11H2tjt-xrvavF1soesNKEGtfCyHUw@mail.gmail.com>
In-reply-to <1475174737.7.0.170886360617.issue28183@psf.upfronthosting.co.za>
Content
Serhiy Storchaka added the comment:
> It looks to me that the patch contain unneeded changes. Some changes don't affect performance, others don't look well justified. Are there benchmarks that confirm the benefit of these changes?

Hum, since I expect disagreements on the changes, I propose to split
the patch into two parts: minimum change to optimize, and a second
change (later, once the first one is merged) to cleanup further the
code.

"Some changes don't affect performance"

Well, a cleanup is supposed to not affect performances at all :-)
History
Date User Action Args
2016-09-29 19:48:04vstinnersetrecipients: + vstinner, rhettinger, ned.deily, methane, serhiy.storchaka, xiang.zhang
2016-09-29 19:48:04vstinnerlinkissue28183 messages
2016-09-29 19:48:04vstinnercreate