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 rhettinger, serhiy.storchaka, sir-sigurd, vstinner
Date 2019-02-21.15:20:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Once I had wrote a similar patch that adds PyTuple_FromArray, but never published it because I did not found enough use cases for this function.  Although I considered using it only for removing some code duplication, but Sergey shown that it can be used for small performance boost in some special cases. I am still not sure, but this argument makes this change a tiny bit more attractive. Leave this on Raymond.

The micro-benchmark results are not really impressive. I still like PR 11954 because it removes code (simply loops). _PyTuple_FromArray() has a well defined API and is safe (I'm saying that because PR 11927 adds an "unsafe" function). As soon as it's private, I'm fine with it.

I'm more attracted by the code simplification than performance boost here.
Date User Action Args
2019-02-21 15:20:55vstinnersetrecipients: + vstinner, rhettinger, serhiy.storchaka, sir-sigurd
2019-02-21 15:20:55vstinnersetmessageid: <>
2019-02-21 15:20:55vstinnerlinkissue36030 messages
2019-02-21 15:20:55vstinnercreate