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.01:37:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561081044.51.0.474199387163.issue37250@roundup.psfhosted.org>
In-reply-to
Content
> Is four months really an unreasonable timeline? I thought most of these packages released more frequently than CPython.

I can't really predict with any accuracy what the release cycle is for most scientific projects. Anywhere from 1 month to 9 months probably covers 90% of the actively maintained scientific projects. So is four months unreasonable? Not entirely unreasonable IMHO. Six months seems a safer estimate. What makes it difficult to predict is that many of the scientific projects do not have rigid release cycles and push out releases when a specific feature or bug fix warrants it.

Perhaps it would be helpful for someone to recap the current options on the table for moving forward and the most significant risk to Cython, Projects using Cython, or CPython by selecting each option.

Thanks.
History
Date User Action Args
2019-06-21 01:37:24willingcsetrecipients: + willingc, ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, jdemeyer, steve.dower
2019-06-21 01:37:24willingcsetmessageid: <1561081044.51.0.474199387163.issue37250@roundup.psfhosted.org>
2019-06-21 01:37:24willingclinkissue37250 messages
2019-06-21 01:37:23willingccreate