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 mark.dickinson
Recipients Francesco Biscani, Saksham Agrawal, berker.peksag, eric.smith, ezio.melotti, lemburg, mark.dickinson, steven.daprano, stutzbach, tim.peters
Date 2015-10-21.19:02:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445454137.05.0.796654977271.issue25453@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the update.

I'm not too worried about performance: I suspect that any additional overhead would be lost in the overhead of the Python machinery. It would be worth profiling to check, of course, before any change went in. I'd expect that most performance critical code of this type would be using NumPy/SciPy anyway.

I'm still unsure about whether the code is worth changing: I do agree that the behaviour suggested by C99 Annex G is (in the abstract) an improvement on Python's current behaviour, and compatibility with C would be a plus. On the other side, introducing an incompatibility with other versions of Python and with NumPy isn't ideal. For me, the potential benefits don't really overcome the drawbacks here, but I'd like to hear other opinions.
History
Date User Action Args
2015-10-21 19:02:17mark.dickinsonsetrecipients: + mark.dickinson, lemburg, tim.peters, eric.smith, stutzbach, ezio.melotti, steven.daprano, berker.peksag, Francesco Biscani, Saksham Agrawal
2015-10-21 19:02:17mark.dickinsonsetmessageid: <1445454137.05.0.796654977271.issue25453@psf.upfronthosting.co.za>
2015-10-21 19:02:17mark.dickinsonlinkissue25453 messages
2015-10-21 19:02:16mark.dickinsoncreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.