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 steve.dower
Recipients jdemeyer, lukasz.langa, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner, willingc
Date 2019-06-20.19:57:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> While Cython may be able to respond within the beta period, scientific projects that depend on it may lag longer as rebuilds and releases will need to happen on PyPI, conda, and conda-forge. Release versioning is critical in the science world as we depend on it for scientific research reproducibility. While we may not come up with an ideal solution for everyone, let's try to find something acceptable for Cython and the Core Python devs/users.

Cython has already responded and made a new release, so the problem would be whether the scientific projects will release new sdists some time in the next four months (they will almost all have to do new wheels for 3.8 too).

Is four months really an unreasonable timeline? I thought most of these packages released more frequently than CPython.
Date User Action Args
2019-06-20 19:57:53steve.dowersetrecipients: + steve.dower, ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, jdemeyer, willingc
2019-06-20 19:57:53steve.dowersetmessageid: <>
2019-06-20 19:57:53steve.dowerlinkissue37250 messages
2019-06-20 19:57:53steve.dowercreate