Hi Piotr (2018.08.27_11:15:05_+0200)
> > err, you meant for python3-foo packages
Yes, I did.
> err again (sorry, to many things at once), I meant option 4 (I can
> change dh-python to generate additional checks for pypy{compile,clean})
That'd be pypy3{compile,clean}
OK, so, now to figure out the "magic" part (byte-compiling already
installed modules when pypy3 is installed / removed.
Should I run the runtime.d directory? Currently everything in that will
only do things with cpython bytecode.
Apps that aren't in dist-packages probably don't need pypy3 bytecode,
unless they want to be run with pypy.
Anything that tries to determine the version (e.g
/usr/share/python3/runtime.d/public_modules.rtinstall and
/usr/share/python3/runtime.d/public_modules.rtremove) looks like they
would break if I told them the version was pypy3.
So, I'm somewhat tempted to ignore runtime.d entirely, and just
byte-compile /usr/lib/python3/dist-packages. That seems pretty hacky,
though :/
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
