Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.maint.python Subject: Byte-compilation for pypy3 Date: Mon, 27 Aug 2018 04:10:01 +0200 Message-ID: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 27 02:03:59 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 X-Greylist: delayed 369 seconds by postgrey-1.36 at bendel; Mon, 27 Aug 2018 02:02:24 UTC 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/16272 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20180827015556.a7us7rxxkv6thflt@bach.rivera.co.za Approved: robomod@news.nic.it Lines: 45 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 27 Aug 2018 03:55:56 +0200 X-Original-Message-ID: <20180827015556.a7us7rxxkv6thflt@bach.rivera.co.za> Xref: csiph.com linux.debian.maint.python:10850 So, I've had some pypy3 packages sitting around for a while, and the main thing that's stopped me from uploading, is figuring out a plan for byte-compilation. If it's sharing /usr/lib/python3/dist-packages with cPython (which it currently is) then we should figure out a plat for byte-compiling for it. rtupdate and postinst / prerm hooks for python3 packages currently call py3{compile,clean} which only operates on cpython3. Options I can think of: 1. Ignore byte-compilation entirely. 2. Change py3{compile,clean} to call pypy3{compile,clean} too. And do some extra compiling / cleaning when pypy3 is installed and removed. 3. Change py3{compile,clean} to do the work of pypy3{compile,clean} too. And do some extra compiling / cleaning when pypy3 is installed and removed. 4. Change the snipets dh_python3 generates, to include pypy3{compile,clean}, when they exist. And again, do the extra compiling / cleanup. 5. Something else? 3 *seems* like the right option - py3{compile,clean} supports a range of cpython versions, already. But I'm not really sure. Here's what I've got: https://salsa.debian.org/debian/pypy3 https://people.debian.org/~stefanor/pypy3/ Other TODOs that need some attention but possibly aren't blocking an upload to unstable: * test failures and errors * import paths aren't quite right, yet, e.g.: - setup.py install installs to a /usr/local path that isn't on sys.path - plat-linux2 is on sys.path, but doesn't exist SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272