Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Piotr =?utf-8?Q?O=C5=BCarowski?= <piotr@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Byte-compilation for pypy3
Date: Fri, 28 Sep 2018 00:00:02 +0200
Message-ID: <wCMue-8v4-1@gated-at.bofh.it>
References: <wrf8B-Ua-1@gated-at.bofh.it> <wrlH3-4QW-3@gated-at.bofh.it> <wrlQJ-4Ua-1@gated-at.bofh.it> <wrlQJ-4Ua-9@gated-at.bofh.it> <wrsfv-hF-3@gated-at.bofh.it>
Old-Return-Path: <ozarow@gmail.com>
Sender: robomod@news.nic.it
Mail-Followup-To: debian-python@lists.debian.org
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="t4vilmrw3aeukgu5"
Content-Disposition: inline
User-Agent: NeoMutt/20180716
Approved: robomod@news.nic.it
Lines: 67
Organization: linux.* mail to news gateway
Xref: csiph.com linux.debian.maint.python:10947


--t4vilmrw3aeukgu5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> > 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}

this is now available in dh-python 3.20180927. Only postinst files are
checking for pypy3compile, though. py3clean in prerm will remove .pyc
generated by PyPy3 as well (so no need to call pypy3clean in there)

> 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 :/

I think we should create a separate runtime.d for pypy3 and a separate one
for bcep files as well while we're at it.

FTR: bcep files are used to describe files that py3compile should avoid.
F.e. files meant for Python >= 3.6 ('async' keyword, etc.) should not be
byte-compiled using python3.5 (see dh_python3's manpage for details or
python3-jinja2 and pylint3 binary packages for examples).

Since we will share dist-package directory, we'll need to describe
exceptions for pypy3compile. One way is to extend version range syntax
in current /usr/share/python3/bcep/ files but I'd rather have separate
/usr/share/pypy/bcep/ used by pypy3compile.


--t4vilmrw3aeukgu5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAlutUhgACgkQrvbxoqdF
dkUcVQ//VCcsL10NrN088dv/bQRgmFL8rO77zsY68WHJxW3PONphV7dHg2dVXt59
lSgR9P17wnK5dzUWKHfihEmcHio6Gezts5+1KnhbtUqahN1KygmCpxBjlFrlADS3
MmMG9uFZMg6m43NxmBnzz7rSaEJ7YmAIEyf3wgrMlaauHlhAxcF1n9swrvjzVEz4
LsZL9ODQWSFfTh6Iuknu6tWA7j4ZGcsQsp9TizIUtC2vStV1Lnx78zaqLRQw7IM9
RF/LxSeEdZVR33IgR7rCzZDMu0Pt+hsskyOPrGH9TSRAriSRRgWC4G0Sh1zght5Y
YBr0X+6F/iDb1C+s8Bx2XYbCHi5cPpwyj3WxEF4ahHXzG3Vq715TJF8gYSRT3hUN
3DWouHGxDhZCMVwPsIM6pc8bDhGK20HvNaZZrVmKvsCTip2jfFiO7uwjNYE/gy3F
Zf8slnKqhf0K0jegS2R9Eqsi3I6LolqDH8BZYOk33C2zLIhcZEs9ICs4flJRH2zy
dEdYZGn/3EjUa8ASagGwtdpY5Kt6+JdBE34oK5XE3jkZ+rfcwMOLe2DZRAYM+pz4
SpSlqEVDHimE4T4K3bm63na/njAfC6BtiShO7LKZ+7/hJKCbCsE+PNmIVrldGBpX
YB5HJaFykTqMCMh8a92c2IfRX3Jqv2PFCoB8N0OzEq4Lu2dnCDU=
=UzX9
-----END PGP SIGNATURE-----

--t4vilmrw3aeukgu5--