Synergies when doing ports from Python2 to Python3

[Andreas Tille]

Hi,

in the Debian Med team (and also Debian Science) we are quite busy to
port software from Python2 to Python3 to save it from Python2 end of
life.  Usually we forward our patches upstream or work together with
upstream to do the port.  However, in case of unresponsive or known to
be dead upstream we are on our own.

I'd love to coordinate the porting work a bit.  All packages of the
Debian Med team can be found at

   https://salsa.debian.org/med-team/

and the patches dealing with Python3 ports in most cases are named
2to3.patch.  Since Debian packages are using quilt patches you can
usually find a patch in

   https://salsa.debian.org/med-team/ __PACKAGENAME__ 
/blob/master/debian/patches/2to3.patch

Please feel free to cherry pick from there.  We would be really
interested if you find issues in those patches - so please let us
know.  As usual you can find a human readable list of Debian Med
packages here:

   https://blends.debian.org/med/tasks/bio      (Biology)
   https://blends.debian.org/med/tasks/bio-dev  (Biology development)

In this field are the most packages we are talking about.

If you might know further interested parties to coordinate, we would
be happy to know.  If you could explain where to find possible patches
you might have developed for Fedora this would also be interesting to
know.

Kind regards

       Andreas.

-- 
http://fam-tille.de

[Scitech] Synergies when doing ports from Python2 to Python3

[Jun Aruga]

On Thu, Dec 19, 2019 at 6:23 PM Andreas Tille <andreas(a)an3as.eu&gt; wrote:
>  Hi,
>
>  in the Debian Med team (and also Debian Science) we are quite busy to
>  port software from Python2 to Python3 to save it from Python2 end of
>  life.  Usually we forward our patches upstream or work together with
>  upstream to do the port.  However, in case of unresponsive or known to
>  be dead upstream we are on our own.
>
>  I'd love to coordinate the porting work a bit.  All packages of the
>  Debian Med team can be found at
>
>     https://salsa.debian.org/med-team/
>
>  and the patches dealing with Python3 ports in most cases are named
>  2to3.patch.  Since Debian packages are using quilt patches you can
>  usually find a patch in
>
>     https://salsa.debian.org/med-team/ __PACKAGENAME__ 
> /blob/master/debian/patches/2to3.patch
>
>  Please feel free to cherry pick from there.  We would be really
>  interested if you find issues in those patches - so please let us 
Hi Andreas.
Thank you for sharing the situation.
I am happy to help something to thrive our biology open ecosystem.

I am Jun Aruga talked who communicated with you about bowtie2 and
simde in Debian Med community in the past,
and also had claimed for the simde deb packaging and gave up the simde
deb packaging recently.

Is there a way to list up all the deb packages that needs Python3
ports (= currently depending on "python" deb package on master
branch?) in all the packages of Debian Med team?

python deb package (= python 2.7)
https://packages.debian.org/sid/python

In Fedora Project, here is the command to list up all the RPM packages
that needs Python3 ports on rawhide (= master branch).
This command is checking the "built" RPM packages depending on
"python" RPM (= python 2.7).
Actually patched and not built RPM packages are also listed up by the command.

```
$ dnf repoquery --disablerepo=* --enablerepo=rawhide --enablerepo
rawhide-source --whatrequires python
...
crun-0:0.10.6-1.fc32.src
htop-0:2.2.0-6.fc31.src
hyperscan-0:5.2.1-1.fc32.src
libclc-0:0.2.0-16.git9f6204e.fc31.src
libraqm-0:0.7.0-1.fc32.src
maxima-0:5.43.0-1.fc32.src
mozc-0:2.23.2815.102-8.fc31.src
tarantool-0:2.1.2.54-2.fc31.src
udis86-0:1.7.2-14.56ff6c8.fc31.src
```

1. all the deb packages depending on "python" deb package (= packages
needing Python 3 ports) (= group A)
2. all the deb packages in Debian Med group (= group B)
3. all the deb packages needing Python3 ports (= group C) = group A & group B

Can we listed up "3." automatically by script or something?
Because checking each repository is hard.

>  know.  As usual you can find a human readable list of Debian Med
>  packages here:
>
>     https://blends.debian.org/med/tasks/bio      (Biology)
>     https://blends.debian.org/med/tasks/bio-dev  (Biology development) 
Out of curiosity, what is the difference between Biology and Biology
development task?

>  In this field are the most packages we are talking about.
>
>  If you might know further interested parties to coordinate, we would
>  be happy to know.  If you could explain where to find possible patches
>  you might have developed for Fedora this would also be interesting to
>  know.
>
>  Kind regards
>
>         Andreas.
>
>  --
>  http://fam-tille.de
>  _______________________________________________
>  scitech mailing list -- scitech(a)lists.fedoraproject.org
>  To unsubscribe send an email to scitech-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]... 
Kind regards,
Jun

-- 
Jun | He - His - Him

[Scitech] Synergies when doing ports from Python2 to Python3

[Jun Aruga]

In case of Fedora Project's situation for Python 3 ports,
A Miro in Python Special Interest Group (= SIG) posted following email
to devel mailing list at the end of October.
I remember we worked applying the patch, updating the target RPM
package repository's master branch.

List of Python 2 packages to be removed mid-November
https://lists.fedoraproject.org/archives/list/[e-mail]...

Did this kind of situation happen in Debian community?
If yes, we can know the list of the target deb packages possibly?

-- 
Jun | He - His - Him