Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!ecngs!feeder2.ecngs.de!87.79.20.101.MISMATCH!newsreader4.netcologne.de!news.netcologne.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.maint.python Subject: Re: Byte-compilation for pypy3 Date: Mon, 27 Aug 2018 18:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 27 16:01:39 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Gpg-Public-Key: http://www.rivera.za.net/stefano.gpg User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/16280 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20180827160121.mnvgfjixnb6o3dmt@bach.rivera.co.za Approved: robomod@news.nic.it Lines: 34 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 27 Aug 2018 18:01:21 +0200 X-Original-Message-ID: <20180827160121.mnvgfjixnb6o3dmt@bach.rivera.co.za> X-Original-References: <20180827015556.a7us7rxxkv6thflt@bach.rivera.co.za> <20180827090620.arbkko72uq4j4aix@sar0.p1otr.com> <20180827091036.honigvvbd543zqzs@sar0.p1otr.com> <20180827091505.2toz3hmw5n3aw2wv@sar0.p1otr.com> Xref: csiph.com linux.debian.maint.python:10858 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