On 2018-10-04, 16:39 GMT, Jan Engelhardt wrote:
Or one could remove py and keep pyc/pyo. That's basically how GNU C C++ & Fortran, Erlang, ocaml, .. all work ;-)
Well, it's a bit more complicated than that. 1. *.pyc files are arch independent (it's just an ouput of the marshall underneath), but they are not interpreter independent. So, if you install only *.pyc files generated by CPython, you cannot use the same library with Jython or PyPy (IronPython seems to be catching second breath on https://github.com/IronLanguages/ironpython2). That limitation probably isn’t a problem with IoT microimages, but I think it is quite showstopper for the general openSUSE/SLE. And no, if you study https://is.gd/EgL9S4 (Case 3 and Case 4) carefully, it is not possible to have both __pycache__ and sourceless *.pyc files together. 2. We would need to port patches from https://bugs.python.org/issue33499 to all desired versions of Python. 3. I am not sure how big the performance penalty will be. 4. We would need to make an extensive changes to our packaging macros to allow automatic generation of python-foo-source modules and working with them. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Anger is often what pain looks like when it shows itself in public. -- Krista Tippett -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org