Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: teng zhaozhi <freet15@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Byte-compilation for pypy3
Date: Mon, 27 Aug 2018 07:50:02 +0200
Message-ID: <wrizw-2S5-1@gated-at.bofh.it>
References: <wrf8B-Ua-1@gated-at.bofh.it>
Old-Return-Path: <freet15@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="000000000000f4088305746428fc"
Approved: robomod@news.nic.it
Lines: 139
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10851

--000000000000f4088305746428fc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Unsubscribed

On Mon, Aug 27, 2018 at 10:04 AM Stefano Rivera <stefanor@debian.org> wrote=
:

> 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
>
>

--=20
Kind regards
=E6=BB=95=E5=8F=AC=E6=99=BA (Ben teng)
Cell:   13381221392
MSN:   freet15@hotmail.com
Skype: freet15

--000000000000f4088305746428fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"color:rgb(204,0,0);font-family:arial;font-s=
ize:13px">Unsubscribed</span><br></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Mon, Aug 27, 2018 at 10:04 AM Stefano Rivera &lt;<a href=3D"=
mailto:stefanor@debian.org">stefanor@debian.org</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">So, I&#39;ve had some pypy3 packages sitting ar=
ound for a while, and the<br>
main thing that&#39;s stopped me from uploading, is figuring out a plan for=
<br>
byte-compilation.<br>
<br>
If it&#39;s sharing /usr/lib/python3/dist-packages with cPython (which it<b=
r>
currently is) then we should figure out a plat for byte-compiling for<br>
it.<br>
<br>
rtupdate and postinst / prerm hooks for python3 packages currently call<br>
py3{compile,clean} which only operates on cpython3.<br>
<br>
Options I can think of:<br>
1. Ignore byte-compilation entirely.<br>
2. Change py3{compile,clean} to call pypy3{compile,clean} too.<br>
=C2=A0 =C2=A0And do some extra compiling / cleaning when pypy3 is installed=
 and<br>
=C2=A0 =C2=A0removed.<br>
3. Change py3{compile,clean} to do the work of pypy3{compile,clean} too.<br=
>
=C2=A0 =C2=A0And do some extra compiling / cleaning when pypy3 is installed=
 and<br>
=C2=A0 =C2=A0removed.<br>
4. Change the snipets dh_python3 generates, to include<br>
=C2=A0 =C2=A0pypy3{compile,clean}, when they exist. And again, do the extra=
<br>
=C2=A0 =C2=A0compiling / cleanup.<br>
5. Something else?<br>
<br>
3 *seems* like the right option - py3{compile,clean} supports a range of<br=
>
cpython versions, already. But I&#39;m not really sure.<br>
<br>
Here&#39;s what I&#39;ve got:<br>
<a href=3D"https://salsa.debian.org/debian/pypy3" rel=3D"noreferrer" target=
=3D"_blank">https://salsa.debian.org/debian/pypy3</a><br>
<a href=3D"https://people.debian.org/~stefanor/pypy3/" rel=3D"noreferrer" t=
arget=3D"_blank">https://people.debian.org/~stefanor/pypy3/</a><br>
<br>
Other TODOs that need some attention but possibly aren&#39;t blocking an<br=
>
upload to unstable:<br>
* test failures and errors<br>
* import paths aren&#39;t quite right, yet, e.g.:<br>
=C2=A0 - setup.py install installs to a /usr/local path that isn&#39;t on<b=
r>
=C2=A0 =C2=A0 sys.path<br>
=C2=A0 - plat-linux2 is on sys.path, but doesn&#39;t exist<br>
<br>
SR<br>
<br>
-- <br>
Stefano Rivera<br>
=C2=A0 <a href=3D"http://tumbleweed.org.za/" rel=3D"noreferrer" target=3D"_=
blank">http://tumbleweed.org.za/</a><br>
=C2=A0 +1 415 683 3272<br>
<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Kind regards<=
br>=E6=BB=95=E5=8F=AC=E6=99=BA (Ben teng)<br>Cell:=C2=A0=C2=A0 13381221392<=
br>MSN:=C2=A0=C2=A0 <a href=3D"mailto:freet15@hotmail.com">freet15@hotmail.=
com</a><br>Skype: freet15</div>

--000000000000f4088305746428fc--