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 willingc
Recipients jdemeyer, lukasz.langa, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner, willingc
Date 2019-06-21.17:14:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks Petr for the wonderful summary.

Of the pros/cons that you mention (if I am understanding correctly), I think that the issue comes down to sdist consumers and regeneration.

1. If sdist consumers will need to regenerate an sdist?
2. How many sdist consumers will likely be impacted?
3. If impacted, how difficult would the regeneration be for a scientist who is moderately comfortable with compilation?
4. Is there any guidance or information that can be given to sdist consumers?

Do we have any good metrics/insights on Question 2 and 3?


While TypeObject size, updating a pinned version, and vectorcall optimization for prior versions are considerations, I believe that they are secondary:

- Typeobject size: Nice to have a smaller size but probably not a concern of the sdist consumer or general user.
- Update a pinned Cython version: General expectation is it should work with the environment which it was pinned within. There should not be an expectation that the pinned version will work if other parts of the environment change.
- vectorcall optimization extends to prior versions: While perhaps nice to have, it is likely more an added benefit instead of an implicit contract or expectation.
Date User Action Args
2019-06-21 17:14:07willingcsetrecipients: + willingc, ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, jdemeyer, steve.dower
2019-06-21 17:14:07willingcsetmessageid: <>
2019-06-21 17:14:07willingclinkissue37250 messages
2019-06-21 17:14:07willingccreate