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 pablogsal
Recipients jdemeyer, lukasz.langa, ncoghlan, pablogsal, scoder, serhiy.storchaka
Date 2019-06-11.12:27:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560256070.05.0.71359740003.issue37221@roundup.psfhosted.org>
In-reply-to
Content
> You already broke backwards compatibility once in beta1

There is one other thing to consider, that is projects with pinned dependencies will have to upgrade to the last Cython and update their generated sources if we don't do the renaming. I don't know how often this happens (for example, Python3.7 changed the result of PyUnicode_AsUTF8AndSize() and PyUnicode_AsUTF8() to type const char * rather of char * and that is backward incompatible if you compile with a C++ compiler or with -Werror) but certainly is worth to consider.

Also, take into account that beta period is precisely the moment to fix these kinds of problems (although I apologize for any inconvenience this may have caused).
History
Date User Action Args
2019-06-11 12:27:50pablogsalsetrecipients: + pablogsal, ncoghlan, scoder, lukasz.langa, serhiy.storchaka, jdemeyer
2019-06-11 12:27:50pablogsalsetmessageid: <1560256070.05.0.71359740003.issue37221@roundup.psfhosted.org>
2019-06-11 12:27:50pablogsallinkissue37221 messages
2019-06-11 12:27:49pablogsalcreate