Hi, Le 22/06/2020 à 11:21, Stefan Behnel a écrit : > [...] > > Basically, for maintained packages, I consider shipping the generated C > code the right way. Less hassle, easier debugging, better user experience. > For unmaintained packages, regenerating the C code at build time *can* > extend the lifetime of the package to newer environments for as long as it > does not run into failures due to Cython compiler changes (so you trade one > compatibility level for another one). > > The question is whether the point at which a package becomes unmaintained > can ever be clear enough to make the switch. Regardless of which way you > choose, at some point in the future someone will have to do something, > either to your code or to your build setup, in order to prevent fatal bitrot.
This makes me wonder: could there be a (non-default, use at your own risk) pip option to rerun Cython before compile? This would allow users to try and workaround compilation failures on their side. Not that the unpack/run Cython/bdist_wheel dance is really difficult, but users have to find out/remember how to do it. Cheers, Baptiste _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/6GTTUMLAT3MMMOTNHLQFRH2C2PZBFWOB/ Code of Conduct: http://python.org/psf/codeofconduct/
