python2 removal

python2 removal

[Jon Turney]

This has come up in discussion a few times, and is now well overdue, I 
think.

Python 2.7 is the last python2 version, which was sunsetted on January 
1, 2020.

1)  I will be making the following hopefully uncontroversial changes to 
cygport in it's next release:

* Make 'inherit python2{,-disutils,-wheel}' an error
* Make 'inherit python-wheel' with PYTHON_WHEEL_VERSIONS containing "2" 
or "2.*" an error.

2) Looking for packages whose names don't start with 'python', but where 
the current version installs something into 
/usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
containing 'python2', the following packages appear to need rebuilding 
for python3:

package             source package     maintainer

alacarte                               ORPHANED (Yaakov Selkowitz)
avahi-ui-tools      avahi              ORPHANED (Yaakov Selkowitz)
buildbot-slave                         Jon Turney [1]
bzr-fastimport      python-fastimport  Ken Brown
bzr                                    Jari Aalto
caribou                                ORPHANED (Yaakov Selkowitz)
cfget                                  Jari Aalto
chm2pdf                                ORPHANED (Yaakov Selkowitz)
codeville                              Jari Aalto
cvs2svn                                ORPHANED (Yaakov Selkowitz)
d-feet                                 ORPHANED (Yaakov Selkowitz)
getmail                                Jari Aalto
gnome-activity-journal                 ORPHANED (Yaakov Selkowitz)
guake                                  ORPHANED (Yaakov Selkowitz)
kf5-kapidox                            ORPHANED (Yaakov Selkowitz)
mozo                                   ORPHANED (Yaakov Selkowitz)
net-snmp-python     net-snmp           David Rothenberger [2]
offlineimap                            Jari Aalto
picard                                 ORPHANED (Dr. Volker Zell)
planet                                 ORPHANED (Yaakov Selkowitz)
rpm-python          rpm                Pavel Fedin
spambayes                              ORPHANED  (Jari Aalto)
tailor                                 Jari Aalto
terminator                             Mike DePaulo
urlgrabber                             Jari Aalto
xml2po              gnome-doc-utils    ORPHANED (Yaakov Selkowitz)
xxdiff                                 ORPHANED (Yaakov Selkowitz)

[1] effectively obsoleted by buildbot-worker, so should just be removed.
[2] also needs rebuilding for perl 5.32

3) There might also still be some other packages lurking which just 
install a script with a shebang containing 'python', and assume that 
python is python2.  I don't know how we could identify those.

4) With that done, one would hope we could just expire all packages as
with names matching:

python27
python27-* (127 of)
python2-*
python-*

But there may be some cases not caught in step 2), where

- the package is not a python module (i.e. source package is not python-*)
- the package shouldn't be removed because it's a dependency of something

So those will need to be identified and inspected to determine what 
should happen to them.

5) Other post-cleanup tasks

e.g. python-beautifulsoup can become a virtual package for python-bs4, 
once that name isn't being used by the python2-only beautifulsoup 3.x.

Re: python2 removal

[Ken Brown]

On 1/15/2023 7:52 AM, Jon Turney via Cygwin-apps wrote:
> bzr-fastimport      python-fastimport  Ken Brown

I'm not interested in maintaining these any longer.  If no one else wants to 
take over, they could just be removed from the distro as far as I'm concerned. 
The only package that would suffer from this is cvs2svn, but that's currently 
unmaintained anyway.

Ken

Re: python2 removal

[Jon Turney]

On 15/01/2023 19:31, Ken Brown via Cygwin-apps wrote:
> On 1/15/2023 7:52 AM, Jon Turney via Cygwin-apps wrote:
>> bzr-fastimport      python-fastimport  Ken Brown
> 
> I'm not interested in maintaining these any longer.  If no one else 
> wants to take over, they could just be removed from the distro as far as 
> I'm concerned. The only package that would suffer from this is cvs2svn, 
> but that's currently unmaintained anyway.

That's fine, of course.

I meant to write some words saying 'please update or orphan (which will 
probably lead to removal)', but forgot.  Sorry about that.

Re: python2 removal

[Jon Turney]

On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
[...]
> Python 2.7 is the last python2 version, which was sunsetted on January 
> 1, 2020.
[...]
> 2) Looking for packages whose names don't start with 'python', but where 
> the current version installs something into 
> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
> containing 'python2', the following packages appear to need rebuilding 
> for python3:

Hi maintainers,

Please consider rebuilding your packages listed below for python3.

If you are no longer interested in being a maintainer for these (or all 
of your) Cygwin packages, please let us know, so we can update our 
records and stop bothering you about them!

> package             source package     maintainer
> 
> alacarte                               ORPHANED (Yaakov Selkowitz)
> avahi-ui-tools      avahi              ORPHANED (Yaakov Selkowitz)
> buildbot-slave                         Jon Turney [1]
> bzr-fastimport      python-fastimport  Ken Brown
> bzr                                    Jari Aalto
> caribou                                ORPHANED (Yaakov Selkowitz)
> cfget                                  Jari Aalto
> chm2pdf                                ORPHANED (Yaakov Selkowitz)
> codeville                              Jari Aalto
> cvs2svn                                ORPHANED (Yaakov Selkowitz)
> d-feet                                 ORPHANED (Yaakov Selkowitz)
> getmail                                Jari Aalto
> gnome-activity-journal                 ORPHANED (Yaakov Selkowitz)
> guake                                  ORPHANED (Yaakov Selkowitz)
> kf5-kapidox                            ORPHANED (Yaakov Selkowitz)
> mozo                                   ORPHANED (Yaakov Selkowitz)
> net-snmp-python     net-snmp           David Rothenberger [2]
> offlineimap                            Jari Aalto
> picard                                 ORPHANED (Dr. Volker Zell)
> planet                                 ORPHANED (Yaakov Selkowitz)
> rpm-python          rpm                Pavel Fedin
> spambayes                              ORPHANED  (Jari Aalto)
> tailor                                 Jari Aalto
> terminator                             Mike DePaulo
> urlgrabber                             Jari Aalto
> xml2po              gnome-doc-utils    ORPHANED (Yaakov Selkowitz)
> xxdiff                                 ORPHANED (Yaakov Selkowitz)
> 
> [1] effectively obsoleted by buildbot-worker, so should just be removed.
> [2] also needs rebuilding for perl 5.32

I might look at some of the more important ORPHANED packages, as time 
permits, and some of these are candidates for removal if not updated, 
but obviously adoptions are welcomed!

Re: python2 removal

[Ken Brown]

On 1/16/2023 7:49 AM, Jon Turney wrote:
> On 15/01/2023 19:31, Ken Brown via Cygwin-apps wrote:
>> On 1/15/2023 7:52 AM, Jon Turney via Cygwin-apps wrote:
>>> bzr-fastimport      python-fastimport  Ken Brown
>>
>> I'm not interested in maintaining these any longer.  If no one else wants to 
>> take over, they could just be removed from the distro as far as I'm concerned. 
>> The only package that would suffer from this is cvs2svn, but that's currently 
>> unmaintained anyway.
> 
> That's fine, of course.
> 
> I meant to write some words saying 'please update or orphan (which will probably 
> lead to removal)', but forgot.  Sorry about that.

NP.  I've marked them as orphaned.

Ken

Re: python2 removal

[David Rothenberger]

On 1/15/2023 4:52 AM, Jon Turney via Cygwin-apps wrote:
> net-snmp-python     net-snmp           David Rothenberger [2]

Getting net-snmp to compile is currently beyond me, so please consider 
it orphaned.

-- 
David Rothenberger  ----  daveroth@acm.org

lighthouse, n.:
         A tall building on the seashore in which the government
         maintains a lamp and the friend of a politician.

Re: python2 removal

[Jon Turney]

On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> [...]
>> Python 2.7 is the last python2 version, which was sunsetted on January 
>> 1, 2020.
> [...]
>> 2) Looking for packages whose names don't start with 'python', but 
>> where the current version installs something into 
>> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
>> containing 'python2', the following packages appear to need rebuilding 
>> for python3:
> 
> Hi maintainers,
> 
> Please consider rebuilding your packages listed below for python3.
> 
> If you are no longer interested in being a maintainer for these (or all 
> of your) Cygwin packages, please let us know, so we can update our 
> records and stop bothering you about them!
> 
>> package             source package     maintainer
>>
>> bzr                                    Jari Aalto
>> cfget                                  Jari Aalto
>> codeville                              Jari Aalto
>> getmail                                Jari Aalto
>> offlineimap                            Jari Aalto
>> tailor                                 Jari Aalto
>> urlgrabber                             Jari Aalto
>>

Hi Jari,

In the absence of any response, I have assumed these are all orphaned.

If that's not what you wanted to happen, please let me know.

 From a brief survey, only offlineimap and urlgrabber (which should 
probably be named python-urlgrabber, since it contains a python module) 
seem to be actively maintained enough to support python3.

So I will probably remove the others, and consider if it's possible and 
worthwhile to update those.

(I also noted that breezy appears to be the python3 replacement for bzr 
and getmail6 appears to be the python3 replacement for getmail.)

Re: python2 removal

[Jon Turney]

On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> [...]
>> Python 2.7 is the last python2 version, which was sunsetted on January 
>> 1, 2020.
> [...]
>> 2) Looking for packages whose names don't start with 'python', but 
>> where the current version installs something into 
>> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
>> containing 'python2', the following packages appear to need rebuilding 
>> for python3:
> 
> Hi maintainers,
> 
> Please consider rebuilding your packages listed below for python3.
> 
> If you are no longer interested in being a maintainer for these (or all 
> of your) Cygwin packages, please let us know, so we can update our 
> records and stop bothering you about them!
> 
>> package             source package     maintainer
>>
>> rpm-python          rpm                Pavel Fedin

Hi Pavel,

In the absence of any response, I have assumed this is orphaned.

If that's not what you wanted to happen, please let me know.

Re: python2 removal

[Jon Turney]

On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> [...]
>> Python 2.7 is the last python2 version, which was sunsetted on January 
>> 1, 2020.
> [...]
>> 2) Looking for packages whose names don't start with 'python', but 
>> where the current version installs something into 
>> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
>> containing 'python2', the following packages appear to need rebuilding 
>> for python3:
> 
> Hi maintainers,
> 
> Please consider rebuilding your packages listed below for python3.
> 
> If you are no longer interested in being a maintainer for these (or all 
> of your) Cygwin packages, please let us know, so we can update our 
> records and stop bothering you about them!
> 
>> package             source package     maintainer
>>
>> terminator                             Mike DePaulo
Hi Mike,

In the absence of any response, I have assumed this, and gtkperf, your 
only other package, are orphaned.

If that's not what you wanted to happen, please let me know.

Re: python2 removal

[Adam Dinwoodie]

On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> > On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> > [...]
> >> Python 2.7 is the last python2 version, which was sunsetted on January
> >> 1, 2020.
> > [...]
> >> 2) Looking for packages whose names don't start with 'python', but
> >> where the current version installs something into
> >> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang
> >> containing 'python2', the following packages appear to need rebuilding
> >> for python3:
> >
> > Hi maintainers,
> >
> > Please consider rebuilding your packages listed below for python3.
> >
> > If you are no longer interested in being a maintainer for these (or all
> > of your) Cygwin packages, please let us know, so we can update our
> > records and stop bothering you about them!
> >
> >> package             source package     maintainer
> >>
> >> bzr                                    Jari Aalto
> >> cfget                                  Jari Aalto
> >> codeville                              Jari Aalto
> >> getmail                                Jari Aalto
> >> offlineimap                            Jari Aalto
> >> tailor                                 Jari Aalto
> >> urlgrabber                             Jari Aalto
> >>
>
> Hi Jari,
>
> In the absence of any response, I have assumed these are all orphaned.
>
> If that's not what you wanted to happen, please let me know.
>
>  From a brief survey, only offlineimap and urlgrabber (which should
> probably be named python-urlgrabber, since it contains a python module)
> seem to be actively maintained enough to support python3.
>
> So I will probably remove the others, and consider if it's possible and
> worthwhile to update those.
>
> (I also noted that breezy appears to be the python3 replacement for bzr
> and getmail6 appears to be the python3 replacement for getmail.)

I'm happy to adopt both of these. I'll give Jari a little while to
reclaim them first, not least as I'm not going to have the time to
spend on packaging these for at least a week or so, but if Jari (or
anyone else) doesn't claim them first, I'll send an ITA once I've
checked I can get the packaging to work.

Re: python2 removal

[Jon Turney]

On 25/02/2023 16:51, Adam Dinwoodie via Cygwin-apps wrote:
> On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
>> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>> [...]
>>>> Python 2.7 is the last python2 version, which was sunsetted on January
>>>> 1, 2020.
>>> [...]
>>>> 2) Looking for packages whose names don't start with 'python', but
>>>> where the current version installs something into
>>>> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang
>>>> containing 'python2', the following packages appear to need rebuilding
>>>> for python3:
>>>
>>> Hi maintainers,
>>>
>>> Please consider rebuilding your packages listed below for python3.
>>>
>>> If you are no longer interested in being a maintainer for these (or all
>>> of your) Cygwin packages, please let us know, so we can update our
>>> records and stop bothering you about them!
>>>
>>>> package             source package     maintainer
>>>>
>>>> bzr                                    Jari Aalto
>>>> cfget                                  Jari Aalto
>>>> codeville                              Jari Aalto
>>>> getmail                                Jari Aalto
>>>> offlineimap                            Jari Aalto
>>>> tailor                                 Jari Aalto
>>>> urlgrabber                             Jari Aalto
>>>>
>>
>> Hi Jari,
>>
>> In the absence of any response, I have assumed these are all orphaned.
>>
>> If that's not what you wanted to happen, please let me know.
>>
>>   From a brief survey, only offlineimap and urlgrabber (which should
>> probably be named python-urlgrabber, since it contains a python module)
>> seem to be actively maintained enough to support python3.
>>
>> So I will probably remove the others, and consider if it's possible and
>> worthwhile to update those.
>>
>> (I also noted that breezy appears to be the python3 replacement for bzr
>> and getmail6 appears to be the python3 replacement for getmail.)
> 
> I'm happy to adopt both of these. I'll give Jari a little while to
> reclaim them first, not least as I'm not going to have the time to
> spend on packaging these for at least a week or so, but if Jari (or
> anyone else) doesn't claim them first, I'll send an ITA once I've
> checked I can get the packaging to work.

Thanks. I appreciate that.

Re: python2 removal

[Jon Turney]

On 27/02/2023 08:35, Pavel Fedin wrote:
>   Hello!
> 
>   Sorry for a huge delay, i forgot.
>   Unfortunately at the moment i am not using Cygwin intensively; and i am not dealing with RPMs.
>   I thought about having a look at a possibility to update the package, but it's very low on my priority list. Have tons of other things to do.
> 

No problem.

Thanks for your efforts in the past.

Re: python2 removal

[Jon Turney]

On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> [...]
>> Python 2.7 is the last python2 version, which was sunsetted on January 
>> 1, 2020.
> [...]
>> 2) Looking for packages whose names don't start with 'python', but 
>> where the current version installs something into 
>> /usr/lib/python2.7/site-packages/ and/or into /usr/bin/ with a shebang 
>> containing 'python2', the following packages appear to need rebuilding 
>> for python3:
> 
> Hi maintainers,
> 
> Please consider rebuilding your packages listed below for python3.
> 
> If you are no longer interested in being a maintainer for these (or all 
> of your) Cygwin packages, please let us know, so we can update our 
> records and stop bothering you about them!
> 
>> package             source package     maintainer
>>
[...]
> 
> I might look at some of the more important ORPHANED packages, as time 
> permits, and some of these are candidates for removal if not updated, 
> but obviously adoptions are welcomed!

> package             source package     maintainer                    notes     disposition                 
> 
> alacarte                               ORPHANED (Yaakov Selkowitz)             update and rebuild          
> avahi-ui-tools      avahi              ORPHANED (Yaakov Selkowitz)             update and rebuild          
> buildbot-slave                         Jon Turney                    [1]       remove                      
> bzr-fastimport                         Ken Brown                               remove                      
> bzr                                    Jari Aalto                    [†]       remove                      
> caribou                                ORPHANED (Yaakov Selkowitz)             rebuild                     
> cfget                                  Jari Aalto                              remove                      
> chm2pdf                                ORPHANED (Yaakov Selkowitz)   [†]       remove                      
> codeville                              Jari Aalto                              remove                      
> cvs2svn                                ORPHANED (Yaakov Selkowitz)   [†]       remove                      
> d-feet                                 ORPHANED (Yaakov Selkowitz)             update and rebuild          
> getmail                                Jari Aalto                              remove                      
> gnome-activity-journal                 ORPHANED (Yaakov Selkowitz)   [2]       update and rebuild          
> guake                                  ORPHANED (Yaakov Selkowitz)             update and rebuild          
> kf5-kapidox                            ORPHANED (Yaakov Selkowitz)             rebuild                     
> mozo                                   ORPHANED (Yaakov Selkowitz)   [3]       update and rebuild          
> net-snmp-python     net-snmp           ORPHANED (David Rothenberger) [*]       update and rebuild, orphan  
> offlineimap                            Jari Aalto                              adoption pending                     
> picard                                 ORPHANED (Dr. Volker Zell)              remove                      
> planet                                 ORPHANED (Yaakov Selkowitz)   [†]       remove                      
> python-fastimport                      Ken Brown                               remove                      
> rpm-python          rpm                ORPHANED (Pavel Fedin)                  update and rebuild, orphan  
> spambayes                              ORPHANED (Jari Aalto)                   remove                      
> tailor                                 Jari Aalto                              remove                      
> terminator                             ORPHANED (Mike DePaulo)       [4]       remove                      
> urlgrabber                             Jari Aalto                              adoption pending                     
> xml2po              gnome-doc-utils    ORPHANED (Yaakov Selkowitz)   [†][5]    remove                      
> xxdiff                                 ORPHANED (Yaakov Selkowitz)             update and rebuild          
> 
> [†] python2 only
> [*] also needed rebuilding for perl 5.32
> [1] effectively obsoleted by buildbot-worker, so removed.
> [2] required updated python-zeitgeist, which in turn required updated python-rdflib
> [3] required updated mate-menus
> [4] I feel bad about removing this, but versions which support python3 also require python-psutil which still isn't ported to cygwin
> [5] gnome-doc-utils is a python2-only, GNOME2 era documentation tool.  It is required by gnome-common, which is itself deprecated.
>     I have temporarily removed that requirement. The GNOME3 era replacement is yelp-tools.

Re: python2 removal

[Jon Turney]

On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> 
> 4) With that done, one would hope we could just expire all packages as
> with names matching:
> 
> python27
> python27-* (127 of)
> python2-*
> python-*
> 
> But there may be some cases not caught in step 2), where
> 
> - the package is not a python module (i.e. source package is not python-*)
> - the package shouldn't be removed because it's a dependency of something
> 
> So those will need to be identified and inspected to determine what 
> should happen to them.

I looked for python{,2}-foo package which have a source which isn't 
python-foo, and doesn't also produce python3*-foo (note: in many cases 
the python3 binding doesn't exist for the latest python3 version)

None of these seem to have current versions of other packages which 
depend on them, so just removing these python2 bindings would seem to be 
safe.

Many of these are old (maybe gtk2, gnome2-era) stuff which we should 
probably also work on removing.

> package                      source package          maintainer                  notes
> 
> python2-avogadro             avogadro                ORPHANED (Yaakov Selkowitz)
> python2-ibus                 ibus                    ORPHANED (Yaakov Selkowitz)
> python2-ktoblzcheck          ktoblzcheck             ORPHANED (Yaakov Selkowitz)
> python2-ayatana_appindicator libayatana-appindicator ORPHANED (Yaakov Selkowitz)
> python2-iptcdata             libiptcdata             ORPHANED (Yaakov Selkowitz)
> python2-libpst               libpst                  ORPHANED (Yaakov Selkowitz)
> python2-ming                 ming                    ORPHANED (Dr. Volker Zell)  [*]
> python2-zbar                 zbar                    ORPHANED (Yaakov Selkowitz) [*]
> python2-zinnia               zinnia                  ORPHANED (Yaakov Selkowitz) [*]
> 
> python-botan                 botan1.10               ORPHANED (Yaakov Selkowitz)
> python-gamin                 gamin                   ORPHANED (Yaakov Selkowitz)
> python-bonobo2               gnome-python            ORPHANED (Yaakov Selkowitz)
> python-gconf2                gnome-python            "
> python-gnome2                gnome-python            "
> python-gnomecanvas2          gnome-python            "
> python-gnomevfs2             gnome-python            "
> python-gnomekeyring          gnome-python-desktop    ORPHANED (Yaakov Selkowitz)
> python-gtop2                 gnome-python-desktop    "
> python-rsvg2                 gnome-python-desktop    "
> python-totem-plparser        gnome-python-desktop    "
> python-wnck                  gnome-python-desktop    "
> python-egg                   gnome-python-extras     ORPHANED (Yaakov Selkowitz)
> python-gtkspell              gnome-python-extras     "
> python-gtkvnc                gtk-vnc                 ORPHANED (Yaakov Selkowitz)
> python-keybinder             keybinder               ORPHANED (Yaakov Selkowitz)
> python-lcms                  lcms                    ORPHANED (Dr. Volker Zell)
> python-appindicator          libappindicator         ORPHANED (Yaakov Selkowitz)
> python-gucharmap             libgucharmap            ORPHANED (Yaakov Selkowitz)
> python-libxslt               libxslt                 ORPHANED (Yaakov Selkowitz)
> python-PyOpenColorIO         OpenColorIO             ORPHANED (Yaakov Selkowitz)
> python-vte                   vte                     ORPHANED (Yaakov Selkowitz)
> python-wx2.8                 wxWidgets2.8            ORPHANED (Yaakov Selkowitz)

[*] also needs rebuilding for perl 5.32

Again, I might look at rebuilding some of the more important packages, 
as time permits, and some of these are candidates for removal if not 
updated, but obviously adoptions and input on what is no longer useful 
is welcomed!

Re: python2 removal

[Jon Turney]

On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> 
> This has come up in discussion a few times, and is now well overdue, I 
> think.
> 
> Python 2.7 is the last python2 version, which was sunsetted on January 
> 1, 2020.
> 
[...]
> 
> 3) There might also still be some other packages lurking which just 
> install a script with a shebang containing 'python', and assume that 
> python is python2.  I don't know how we could identify those.

The remaining cases of packages which have a dependency on python and/or 
python2 are either this (packages which contain a python script with a 
python shebang line), or the other case which I hadn't previously 
considered - a package which contain an executable or shared library 
linked with libpython2.7.dll.

So, again I need inspect these to determine what should happen to them.

Re: python2 removal

[Brian Inglis]

On 2023-03-14 13:17, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>
>> This has come up in discussion a few times, and is now well overdue, I think.
>>
>> Python 2.7 is the last python2 version, which was sunsetted on January 1, 2020.
>>
> [...]
>>
>> 3) There might also still be some other packages lurking which just install a 
>> script with a shebang containing 'python', and assume that python is python2.  
>> I don't know how we could identify those.
> 
> The remaining cases of packages which have a dependency on python and/or python2 
> are either this (packages which contain a python script with a python shebang 
> line), or the other case which I hadn't previously considered - a package which 
> contain an executable or shared library linked with libpython2.7.dll.
> 
> So, again I need inspect these to determine what should happen to them.

Add:

$ apt-cyg category Python | grep -iv python | xargs apt-cyg listall | awk '...'
cfv			1.18.3-1			x86_64
emacs-mercurial		2.7.1-1				x86_64
git-filter-repo		2.38.0-1			noarch
idle2			2.7.18-4			x86_64
idle27			2.7.18-4			x86_64
idle35			3.5.7-2				x86_64
idle36			3.6.15-1			x86_64
idle37			3.7.12-1			x86_64
idle38			3.8.16-1			x86_64
idle39			3.9.16-1			x86_64
mercurial		6.3.2-1				noarch
mercurial-convert	2.7.1-1				x86_64
mercurial-gui		2.7.1-1				x86_64
mercurial-highlight	2.7.1-1				x86_64
mutagen-utils		1.45.1-2			noarch
offlineimap		6.5.5-1				x86_64
scons			4.4.0-1				x86_64
stgit			0.19-2				noarch
svn-load		1.3-1				x86_64
urlgrabber		3.1.0-3				x86_64
xlsx2csv		0.11+20120814+gitf54ab78-2	noarch

I'd like to adopt *xlsx2csv* - for an initial build see:

https://cygwin.com/cgi-bin2/jobs.cgi?id=5607
https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=af279166a903b526274f8b10264e206fc5010a68
https://github.com/cygwin/scallywag/actions/runs/4419738199

The author remains the same but version numbering staggers around then jumps to 
0.5 and is now up to 0.8.1.
The manual was a POD file from Jaari run thru pod2man for 0.11 from 2010, but 
very outdated now, not to mention using Perl docs for Python modules, so I'm 
rewriting from help2man output to be current, comprehensive, and functional with 
`groff -man`.

[I use it to get data into portable form, make it threat free, and fake 
spreadsheets for my accountant, if I want to use gvim instead of Gnumeric or 
Libre Office calc! ;^> ]

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

Re: python2 removal

[marco atzeri]

On Wed, Mar 15, 2023 at 1:56 PM Brian Inglis via Cygwin-apps  wrote:
>
> On 2023-03-14 13:17, Jon Turney via Cygwin-apps wrote:
> > On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> >>
> >> This has come up in discussion a few times, and is now well overdue, I think.
> >>
> >> Python 2.7 is the last python2 version, which was sunsetted on January 1, 2020.
> >>
> > [...]
> >>
> >> 3) There might also still be some other packages lurking which just install a
> >> script with a shebang containing 'python', and assume that python is python2.
> >> I don't know how we could identify those.
> >
> > The remaining cases of packages which have a dependency on python and/or python2
> > are either this (packages which contain a python script with a python shebang
> > line), or the other case which I hadn't previously considered - a package which
> > contain an executable or shared library linked with libpython2.7.dll.
> >
> > So, again I need inspect these to determine what should happen to them.
>
> Add:
>
> $ apt-cyg category Python | grep -iv python | xargs apt-cyg listall | awk '...'

Is apt-cyg an "official" tool now
:-?

> scons                   4.4.0-1                         x86_64

scons is already built for 3.9

ITA (was Re: python2 removal)

[Jon Turney]

On 15/03/2023 12:56, Brian Inglis via Cygwin-apps wrote:
> On 2023-03-14 13:17, Jon Turney via Cygwin-apps wrote:
>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>
>>> This has come up in discussion a few times, and is now well overdue, 
>>> I think.
>>>
>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>> January 1, 2020.
>>>
>> [...]
>>>
>>> 3) There might also still be some other packages lurking which just 
>>> install a script with a shebang containing 'python', and assume that 
>>> python is python2. I don't know how we could identify those.
>>
>> The remaining cases of packages which have a dependency on python 
>> and/or python2 are either this (packages which contain a python script 
>> with a python shebang line), or the other case which I hadn't 
>> previously considered - a package which contain an executable or 
>> shared library linked with libpython2.7.dll.
>>
>> So, again I need inspect these to determine what should happen to them.
> 
[..]

> I'd like to adopt *xlsx2csv* - for an initial build see:

Jari is still the maintainer of record for that package, so I need to 
give him an opportunity to reply here.

> https://cygwin.com/cgi-bin2/jobs.cgi?id=5607
> https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=af279166a903b526274f8b10264e206fc5010a68
> https://github.com/cygwin/scallywag/actions/runs/4419738199
> 
> The author remains the same but version numbering staggers around then 
> jumps to 0.5 and is now up to 0.8.1.
> The manual was a POD file from Jaari run thru pod2man for 0.11 from 
> 2010, but very outdated now, not to mention using Perl docs for Python 
> modules, so I'm rewriting from help2man output to be current, 
> comprehensive, and functional with `groff -man`.
> 
> [I use it to get data into portable form, make it threat free, and fake 
> spreadsheets for my accountant, if I want to use gvim instead of 
> Gnumeric or Libre Office calc! ;^> ]

The critical piece of data I'm missing here is which of these is true:

a) This package contains a script with a python shebang. The current 
version doesn't work when python is python3, so an upgrade is needed to 
continue working when python2 is removed, or

b) This package contains a script with a python shebang. The current 
version will continue to work when python is python3.

Re: ITA xlsx2csv (was Re: python2 removal)

[Brian Inglis]

[-- Attachment #1: Type: text/plain, Size: 3231 bytes --]

On 2023-03-16 07:29, Jon Turney wrote:
> On 15/03/2023 12:56, Brian Inglis via Cygwin-apps wrote:
>> On 2023-03-14 13:17, Jon Turney via Cygwin-apps wrote:
>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>> This has come up in discussion a few times, and is now well overdue, I think.
>>>> Python 2.7 is the last python2 version, which was sunsetted on January 1, 2020.

>>>> 3) There might also still be some other packages lurking which just install 
>>>> a script with a shebang containing 'python', and assume that python is 
>>>> python2. I don't know how we could identify those.

>>> The remaining cases of packages which have a dependency on python and/or 
>>> python2 are either this (packages which contain a python script with a python 
>>> shebang line), or the other case which I hadn't previously considered - a 
>>> package which contain an executable or shared library linked with 
>>> libpython2.7.dll.
>>> So, again I need inspect these to determine what should happen to them.

>> I'd like to adopt *xlsx2csv* - for an initial build see:

> Jari is still the maintainer of record for that package, so I need to give him 
> an opportunity to reply here.

>> https://cygwin.com/cgi-bin2/jobs.cgi?id=5607
>> https://cygwin.com/cgit/cygwin-packages/playground/commit/?id=af279166a903b526274f8b10264e206fc5010a68
>> https://github.com/cygwin/scallywag/actions/runs/4419738199
>> The author remains the same but version numbering staggers around then jumps 
>> to 0.5 and is now up to 0.8.1.
>> The manual was a POD file from Jari run thru pod2man for 0.11 from 2010, but 
>> very outdated now, not to mention using Perl docs for Python modules, so I'm 
>> rewriting from help2man output to be current, comprehensive, and functional 
>> with `groff -man`.
>> [I use it to get data into portable form, make it threat free, and fake 
>> spreadsheets for my accountant, if I want to use gvim instead of Gnumeric or 
>> Libre Office calc! ;^> ]

> The critical piece of data I'm missing here is which of these is true:
> a) This package contains a script with a python shebang. The current version 
> doesn't work when python is python3, so an upgrade is needed to continue working 
> when python2 is removed, or
> b) This package contains a script with a python shebang. The current version 
> will continue to work when python is python3.

Unfortunately only a generic cygbuild sh script is supplied with the package - 
does nothing but complain without some other "magic" script or data! ;^>
Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027 from 
0.11+20120814.

$ sed 1q xlsx2csv.py
#!/usr/bin/env python

Does not work with python3, nor after running 2to3 fixes - see attached logs - 
IANAPythonista

Anyway pylint was not useful compared to 2to3 - see attached pylint before and 
after 2to3 logs compared to 2to3 log.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

[-- Attachment #2: xlsx2csv-pylint-2.log --]
[-- Type: text/plain, Size: 198 bytes --]

************* Module xlsx2csv.py
xlsx2csv.py.bak:286:65: E0001: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers (<unknown>, line 286) (syntax-error)

[-- Attachment #3: xlsx2csv-2to3.log --]
[-- Type: text/plain, Size: 6228 bytes --]

RefactoringTool: Adding transformation: apply
RefactoringTool: Adding transformation: asserts
RefactoringTool: Adding transformation: basestring
RefactoringTool: Skipping optional fixer: buffer
RefactoringTool: Adding transformation: dict
RefactoringTool: Adding transformation: except
RefactoringTool: Adding transformation: exec
RefactoringTool: Adding transformation: execfile
RefactoringTool: Adding transformation: exitfunc
RefactoringTool: Adding transformation: filter
RefactoringTool: Adding transformation: funcattrs
RefactoringTool: Adding transformation: future
RefactoringTool: Adding transformation: getcwdu
RefactoringTool: Adding transformation: has_key
RefactoringTool: Skipping optional fixer: idioms
RefactoringTool: Adding transformation: import
RefactoringTool: Adding transformation: imports
RefactoringTool: Adding transformation: imports2
RefactoringTool: Adding transformation: input
RefactoringTool: Adding transformation: intern
RefactoringTool: Adding transformation: isinstance
RefactoringTool: Adding transformation: itertools
RefactoringTool: Adding transformation: itertools_imports
RefactoringTool: Adding transformation: long
RefactoringTool: Adding transformation: map
RefactoringTool: Adding transformation: metaclass
RefactoringTool: Adding transformation: methodattrs
RefactoringTool: Adding transformation: ne
RefactoringTool: Adding transformation: next
RefactoringTool: Adding transformation: nonzero
RefactoringTool: Adding transformation: numliterals
RefactoringTool: Adding transformation: operator
RefactoringTool: Adding transformation: paren
RefactoringTool: Adding transformation: print
RefactoringTool: Adding transformation: raise
RefactoringTool: Adding transformation: raw_input
RefactoringTool: Adding transformation: reduce
RefactoringTool: Adding transformation: reload
RefactoringTool: Adding transformation: renames
RefactoringTool: Adding transformation: repr
RefactoringTool: Skipping optional fixer: set_literal
RefactoringTool: Adding transformation: standarderror
RefactoringTool: Adding transformation: sys_exc
RefactoringTool: Adding transformation: throw
RefactoringTool: Adding transformation: tuple_params
RefactoringTool: Adding transformation: types
RefactoringTool: Adding transformation: unicode
RefactoringTool: Adding transformation: urllib
RefactoringTool: Skipping optional fixer: ws_comma
RefactoringTool: Adding transformation: xrange
RefactoringTool: Adding transformation: xreadlines
RefactoringTool: Adding transformation: zip
RefactoringTool: Refactoring xlsx2csv.py
RefactoringTool: Refactored xlsx2csv.py
RefactoringTool: Wrote changes to xlsx2csv.py
RefactoringTool: Files that were modified:
RefactoringTool: xlsx2csv.py
--- xlsx2csv.py	(original)
+++ xlsx2csv.py	(refactored)
@@ -148,10 +148,10 @@
             attrs = sheetNode._attrs
             name = attrs["name"].value
             if self.appName == 'xl':
-                if attrs.has_key('r:id'): id = int(attrs["r:id"].value[3:])
+                if 'r:id' in attrs: id = int(attrs["r:id"].value[3:])
                 else: id = int(attrs['sheetId'].value)
             else:
-                if attrs.has_key('sheetId'): id = int(attrs["sheetId"].value)
+                if 'sheetId' in attrs: id = int(attrs["sheetId"].value)
                 else: id = int(attrs['r:id'].value[3:])
             self.sheets.append({'name': name, 'id': id})
 
@@ -272,18 +272,18 @@
                 # get cell format
                 format = None
                 xfs_numfmt = self.styles.cellXfs[s]
-                if self.styles.numFmts.has_key(xfs_numfmt):
+                if xfs_numfmt in self.styles.numFmts:
                     format = self.styles.numFmts[xfs_numfmt]
-                elif STANDARD_FORMATS.has_key(xfs_numfmt):
+                elif xfs_numfmt in STANDARD_FORMATS:
                     format = STANDARD_FORMATS[xfs_numfmt]
                 # get format type
-                if format and FORMATS.has_key(format):
+                if format and format in FORMATS:
                     format_type = FORMATS[format]
 
                     if format_type == 'date': # date/time
                         try:
                             if self.workbook.date1904:
-                                date = datetime.datetime(1904, 01, 01) + datetime.timedelta(float(data))
+                                date = datetime.datetime(1904, 0o1, 0o1) + datetime.timedelta(float(data))
                             else:
                                 date = datetime.datetime(1899, 12, 30) + datetime.timedelta(float(data))
                             if self.dateformat:
@@ -322,12 +322,12 @@
             self.in_cell_value = True
         #elif self.in_cell and name == 'f':
         #    self.in_cell_formula = True
-        elif self.in_sheet and name == 'row' and attrs.has_key('r'):
+        elif self.in_sheet and name == 'row' and 'r' in attrs:
             self.rowNum = attrs['r']
             self.in_row = True
             self.columns = {}
             self.spans = None
-            if attrs.has_key('spans'):
+            if 'spans' in attrs:
                 self.spans = [int(i) for i in attrs['spans'].split(":")]
         elif name == 'sheetData':
             self.in_sheet = True
@@ -343,9 +343,9 @@
             self.columns[t - 1 + self.colIndex] = self.data
             self.in_cell = False
         if self.in_row and name == 'row':
-            if len(self.columns.keys()) > 0:
+            if len(list(self.columns.keys())) > 0:
                 d = [""] * (max(self.columns.keys()) + 1)
-                for k in self.columns.keys():
+                for k in list(self.columns.keys()):
                     d[k] = self.columns[k].encode("utf-8")
                 if self.spans:
                     l = self.spans[0] + self.spans[1] - 1
@@ -366,7 +366,7 @@
         else:
             if fullpath.lower().endswith(".xlsx"):
                 outfilepath = fullpath[:-4] + 'csv'
-                print("Converting %s to %s" %(fullpath, outfilepath))
+                print(("Converting %s to %s" %(fullpath, outfilepath)))
                 f = open(outfilepath, 'w+b')
                 try:
                     xlsx2csv(fullpath, f, **kwargs)

[-- Attachment #4: xlsx2csv-pylint-3.log --]
[-- Type: text/plain, Size: 371 bytes --]

************* Module xlsx2csv
xlsx2csv.py:140:27: E1101: Instance of 'Document' has no 'firstChild' member (no-member)
xlsx2csv.py:142:28: E1101: Instance of 'Document' has no 'firstChild' member (no-member)
xlsx2csv.py:146:17: E1101: Instance of 'Document' has no 'firstChild' member (no-member)

-----------------------------------
Your code has been rated at 9.44/10

Re: ITA xlsx2csv (was Re: python2 removal)

[Jon Turney]

On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote:
> On 2023-03-16 07:29, Jon Turney wrote:
> 
>> The critical piece of data I'm missing here is which of these is true:
>> a) This package contains a script with a python shebang. The current 
>> version doesn't work when python is python3, so an upgrade is needed 
>> to continue working when python2 is removed, or
>> b) This package contains a script with a python shebang. The current 
>> version will continue to work when python is python3.
> 
> Unfortunately only a generic cygbuild sh script is supplied with the 
> package - does nothing but complain without some other "magic" script or 
> data! ;^>
> Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027 
> from 0.11+20120814.
> 
> $ sed 1q xlsx2csv.py
> #!/usr/bin/env python
> 
> Does not work with python3, nor after running 2to3 fixes - see attached 
> logs - IANAPythonista
> 
> Anyway pylint was not useful compared to 2to3 - see attached pylint 
> before and after 2to3 logs compared to 2to3 log.

This is not an unequivocal answer to my question.

It sounds like you are saying "even the most recent version of xlsx2cvs 
doesn't work with python3", in which case the only sane option is to 
remove this package when python2 is removed.

Is that what you mean? If not, what do you mean?

Please answer with a single sentence.

Re: ITA xlsx2csv (was Re: python2 removal)

[Brian Inglis]

On 2023-03-16 12:57, Jon Turney wrote:
> On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote:
>> On 2023-03-16 07:29, Jon Turney wrote:
>>
>>> The critical piece of data I'm missing here is which of these is true:
>>> a) This package contains a script with a python shebang. The current version 
>>> doesn't work when python is python3, so an upgrade is needed to continue 
>>> working when python2 is removed, or
>>> b) This package contains a script with a python shebang. The current version 
>>> will continue to work when python is python3.

>> Unfortunately only a generic cygbuild sh script is supplied with the package - 
>> does nothing but complain without some other "magic" script or data! ;^>
>> Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027 from 
>> 0.11+20120814.
>> $ sed 1q xlsx2csv.py
>> #!/usr/bin/env python
>> Does not work with python3, nor after running 2to3 fixes - see attached logs - 
>> IANAPythonista
>> Anyway pylint was not useful compared to 2to3 - see attached pylint before and 
>> after 2to3 logs compared to 2to3 log.

> This is not an unequivocal answer to my question.
> It sounds like you are saying "even the most recent version of xlsx2cvs doesn't 
> work with python3", in which case the only sane option is to remove this package 
> when python2 is removed.

Sorry if I was not sufficiently clear but that is not the case at all.

> Is that what you mean? If not, what do you mean?
> Please answer with a single sentence.

Current Cygwin package is python2 only from 2010 when python3 first came out.

You asked about the current Cygwin source package - that is all those answers 
refer to - and the logs relate to - nothing about the latest upstream package.

The Cygwin source package as distributed does not work with python3, it can not 
be easily upgraded to work with python3 using 2to3, and there is no way for us 
to rebuild it anyway, as it depends on some cygbuild "magic" not provided in the 
source package.

The latest version of the upstream package builds, installs, checks, and runs 
fine using minimal cygport and python3 cygclasses, as referred to in the 
scallywag links provided.

I am replacing the upstream man page provided, as it was written in POD, applies 
to the outdated 2010 release, and the latest upstream version's help has many 
more options, is more comprehensive, and was started with help2man.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

Re: ITA xlsx2csv (was Re: python2 removal)

[Jari Aalto]

On 2023-03-16 18:57, Jon Turney via Cygwin-apps wrote:
> On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote:
> > On 2023-03-16 07:29, Jon Turney wrote:
> > 
> > > The critical piece of data I'm missing here is which of these is true:
> > > a) This package contains a script with a python shebang. The current
> > > version doesn't work when python is python3, so an upgrade is needed
> > > to continue working when python2 is removed, or
> > > b) This package contains a script with a python shebang. The current
> > > version will continue to work when python is python3.
> > 
> > Unfortunately only a generic cygbuild sh script is supplied with the
> > package - does nothing but complain without some other "magic" script or
> > data! ;^>
> > Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027
> > from 0.11+20120814.
> > 
> > $ sed 1q xlsx2csv.py
> > #!/usr/bin/env python

I updated the the latest from upstream repository and it shoudl now
work with Python 3.

thanks,
Jari

Re: ITA xlsx2csv (was Re: python2 removal)

[Jon Turney]

On 22/03/2023 07:36, Jari Aalto via Cygwin-apps wrote:
> On 2023-03-16 18:57, Jon Turney via Cygwin-apps wrote:
>> On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote:
>>> On 2023-03-16 07:29, Jon Turney wrote:
>>>
>>>> The critical piece of data I'm missing here is which of these is true:
>>>> a) This package contains a script with a python shebang. The current
>>>> version doesn't work when python is python3, so an upgrade is needed
>>>> to continue working when python2 is removed, or
>>>> b) This package contains a script with a python shebang. The current
>>>> version will continue to work when python is python3.
>>>
>>> Unfortunately only a generic cygbuild sh script is supplied with the
>>> package - does nothing but complain without some other "magic" script or
>>> data! ;^>
>>> Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027
>>> from 0.11+20120814.
>>>
>>> $ sed 1q xlsx2csv.py
>>> #!/usr/bin/env python
> 
> I updated the the latest from upstream repository and it shoudl now
> work with Python 3.

Thanks.

Re: python2 removal

[Jon Turney]

On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>
>> This has come up in discussion a few times, and is now well overdue, I 
>> think.
>>
>> Python 2.7 is the last python2 version, which was sunsetted on January 
>> 1, 2020.
>>
> [...]
>>
>> 3) There might also still be some other packages lurking which just 
>> install a script with a shebang containing 'python', and assume that 
>> python is python2.  I don't know how we could identify those.
> 
> The remaining cases of packages which have a dependency on python and/or 
> python2 are either this (packages which contain a python script with a 
> python shebang line), or the other case which I hadn't previously 
> considered - a package which contain an executable or shared library 
> linked with libpython2.7.dll.
> 
> So, again I need inspect these to determine what should happen to them.

So here's the list, with *tentative* notes of the disposition for each 
package.

As before, I might look at rebuilding some of the more important 
packages, as time permits, and some of these are candidates for removal 
if not updated, but obviously adoptions and input on what is no longer 
useful is welcomed!

I've also adjusted numerous old package versions which depend on 
'python' to depend on 'python2' when that's what they actually require, 
so they will become not-installable when python2 is removed, and can 
subsequently be expired.

(often these are historical package requirements which were synthesized 
from the current package requirements from before we had per-version 
requirements)

Contrariwise, a few packages (e.g. clang, ibus, libglib2.0-devel, llvm, 
lv2-devel, mysql-server, pulseaudio-equalizer) which depend on python2, 
but contain a script which appears to work with python3 have been 
adjusted to depend on 'python'

> source package         package                 maintainer                    notes      disposition                                    
> 
> GConf2                 GConf2                  ORPHANED (Yaakov Selkowitz)   [†][§][1]  ?                                              
> XtoW                   XtoW                    Jon Turney                    [†][§]     remove (experiment has run it's course)       
> anjuta                 anjuta                  ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild                             
> avogadro               libavogadro1            ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild (not to avogadro2?)
> boost                  boost-build             ORPHANED (Yaakov Selkowitz)   [†]        unclear? depends on python2 and python3?
> boost                  libboost_mpi_python*    "                             [*]        libboost_mpi_python3* exists, so just remove?
> boost                  libboost_numpy*         "                             [*]        libboost_numpy3* exists, so just remove?
> boost                  libboost_python*        "                             [*]        libboost_python3_* exists, so just remove?
> caja-python            caja-python             ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild
> cantor                 cantor-backend-python2  ORPHANED (Yaakov Selkowitz)   [*]        cantor-backend-python3 exists, so just remove? 
> cfv                    cfv                     Jari Aalto                    [†][§]     update and rebuild
> extra-cmake-modules    extra-cmake-modules     ORPHANED (Yaakov Selkowitz)   [†]        probably ok, but should probably update & rebuild
> fluxbox                fluxbox                 ORPHANED (Yaakov Selkowitz)   [†][§][2]  rebuild                                        
> fvwm                   fvwm                    ORPHANED (Yaakov Selkowitz)   [†]        rebuild                                        
> geany-plugins          geany-plugins-geanypy   ORPHANED (Yaakov Selkowitz)   [*][3]     leave as is, becomes not-installable
> gimp                   gimp-python             ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild
> gnome-commander        gnome-commander         ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild
> gnubg                  gnubg                   ORPHANED (Dr. Volker Zell)    [*]        update and rebuild
> gnumeric               gnumeric-python         ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild
> gonvert                gonvert                 ORPHANED (Yaakov Selkowitz)   [†][§][4]  remove
> gtk2.0                 libgtk2.0-devel         ORPHANED (Yaakov Selkowitz)   [†][§][9]  update and rebuild
> gtksourceview2.0       libgtksourceview2.0_0   ORPHANED (Yaakov Selkowitz)   [†][§][6]  leave as is, becomes not-installable
> gtranslator            gtranslator             ORPHANED (Yaakov Selkowitz)   [†]        ?
> inkscape               inkscape                ORPHANED (Yaakov Selkowitz)   [†][§][5]  update and rebuild
> kde-dev-scripts        kde-dev-scripts         ORPHANED (Yaakov Selkowitz)   [†]        ?
> kf5-kross-interpreters kf5-kross-python        ORPHANED (Yaakov Selkowitz)   [*]        ?
> kig                    kig                     ORPHANED (Yaakov Selkowitz)   [†][§]     update and rebuild
> kross-interpreters     kross-python            ORPHANED (Yaakov Selkowitz)   [*]        ? KDE4-era
> libdbusmenu            libdbusmenu-tools       ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable ?
> libgda5.0              libgda5.0_4             ORPHANED (Yaakov Selkowitz)   [†][§]     update and rebuild (5.2.10)
> libglade2.0            libglade2.0-devel       ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable (upstream unchanged)
> libkkc                 libkkc-common           ORPHANED (Yaakov Selkowitz)   [†][§][7]  update and rebuild
> libpeas                libpeas1.0_0            ORPHANED (Yaakov Selkowitz)   [*][8]     update and rebuild
> lokalize               lokalize                ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable
> mingw64-i686-gconf2    mingw64-i686-gconf2     ORPHANED (Yaakov Selkowitz)   [†][§][1]  remove? but has dependencies?                 
> mingw64-i686-gtk2.0    mingw64-i686-gtk2.0     ORPHANED (Yaakov Selkowitz)   [†][§][9]  ?
> mingw64-x86_64-gconf2  mingw64-x86_64-gconf2   ORPHANED (Yaakov Selkowitz)   [†][§][1]  "                                              
> mingw64-x86_64-gtk2.0  mingw64-x86_64-gtk2.0   ORPHANED (Yaakov Selkowitz)   [†][§][9]  ?
> monotone               monotone                ORPHANED (Yaakov Selkowitz)   [†][§]     rebuild? fedora has python3 patches
> mypaint                mypaint                 ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild
> mypaint                mypaint-ora-thumbnailer "                             [†]
> octave-miscellaneous   octave-miscellaneous    Marco Atzeri                  [†]        ?
> openbox                openbox                 ORPHANED (Yaakov Selkowitz)   [†][§]     rebuild? fedora has python3 patches          
> parley                 parley                  ORPHANED (Yaakov Selkowitz)   [†]        leave as is, becomes not-installable?
> pidgin                 libgnt0                 ORPHANED (Yaakov Selkowitz)   [*]        update and rebuild??
> pidgin                 pidgin                  "                             [†]        ?
> pluma                  pluma                   ORPHANED (Yaakov Selkowitz)   [†][§]     update and rebuild?? python plugin scripts
> scribus                scribus                 ORPHANED (Yaakov Selkowitz)   [*]        leave as is, becomes not-installable?
> svn-load               svn-load                Jari Aalto                    [†][§]     ?
> telepathy-gabble       telepathy-gabble        ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable?
> tellico                tellico                 ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable?
> tracker-miners         tracker-miners          ORPHANED (Yaakov Selkowitz)   [†][§][10] leave as is, becomes not-installable?
> vim                    vim-python              Marco Atzeri                             empty and obsolete, remove
> virt-manager           virt-manager            ORPHANED (Yaakov Selkowitz)   [†]        leave as is, becomes not-installable?
> webcheck               webcheck                Jari Aalto                    [†][§]
> xf86-video-qxl         xf86-video-qxl          ORPHANED (Yaakov Selkowitz)   [†][§]     update and rebuild                              
> xplayer                xplayer                 ORPHANED (Yaakov Selkowitz)   [†][§]     update and rebuild ? unclear if supports python3? peas for plugins
> 
> [*] linked against libpython2.7.dll
> [†] contains some python scripts
> [§] script is python2 only, not compatible with python3
> 
> [1] gsettings-schema-convert script is python2 only; gconf is obsolete to dconfg/gsettings, so should be removed when it's users are removed or updated
>     rebuild with explicit python2 shebang in gsettings-schema-convert? use python3 patch in upstream PR?
> [2] drop unmaintained fluxbox-xdg-menu.py script; if needed package xdgmenumaker instead
> [3] geanypy is python2 only, removed upstream (replaced by peasy), so just make this uninstallable without python2 for the moment
> [4] dead upstream, python2 only
> [5] need a later version of inkscape for python extensions to work when python is python3
> [6] obsolete upstream to gtksourceview3 and later; things which depend on this need updating
> [7] no release upstream, so need to use git commit with python3 fixes
> [8] has python2 and python3 loaders; disable python2 when rebuilding
> [9] upstream patch available to make gtk-builder-convert work with python3
> [10] this dependency seems to be because of a test script which is installed

Re: python2 removal

[Jon Turney]

On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>
>>> This has come up in discussion a few times, and is now well overdue, 
>>> I think.
>>>
>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>> January 1, 2020.
>>>
>> [...]
>>>
>>> 3) There might also still be some other packages lurking which just 
>>> install a script with a shebang containing 'python', and assume that 
>>> python is python2.  I don't know how we could identify those.
>>
>> The remaining cases of packages which have a dependency on python 
>> and/or python2 are either this (packages which contain a python script 
>> with a python shebang line), or the other case which I hadn't 
>> previously considered - a package which contain an executable or 
>> shared library linked with libpython2.7.dll.
>>
>> So, again I need inspect these to determine what should happen to them.
> 
> So here's the list, with *tentative* notes of the disposition for each 
> package.
[...]
	
> source package         package                 maintainer                    notes      
> 
> cfv                    cfv                     Jari Aalto                    [†][§]
> svn-load               svn-load                Jari Aalto                    [†][§]
> webcheck               webcheck                Jari Aalto                    [†][§]
> 
> [†] contains some python scripts
> [§] script is python2 only, not compatible with python3

Hi Jari,

I believe these packages all need updating for python3.

Please confirm if this assessment is correct, and let me know if you 
intend to do this, otherwise I will assume these packages are orphaned 
and they will be removed.

Thanks.

Re: python2 removal

[Jon Turney]

On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>
>>> This has come up in discussion a few times, and is now well overdue, 
>>> I think.
>>>
>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>> January 1, 2020.
>>>
>> [...]
>>>
>>> 3) There might also still be some other packages lurking which just 
>>> install a script with a shebang containing 'python', and assume that 
>>> python is python2.  I don't know how we could identify those.
>>
>> The remaining cases of packages which have a dependency on python 
>> and/or python2 are either this (packages which contain a python script 
>> with a python shebang line), or the other case which I hadn't 
>> previously considered - a package which contain an executable or 
>> shared library linked with libpython2.7.dll.
>>
>> So, again I need inspect these to determine what should happen to them.
> 
> So here's the list, with *tentative* notes of the disposition for each 
> package.
> 
[...]

> source package         package                 maintainer                    notes      disposition                       
> 
> octave-miscellaneous   octave-miscellaneous    Marco Atzeri                  [†]        ?
> 
> [†] contains some python scripts
> [§] script is python2 only, not compatible with python3

Hi Marco,

Currently, octave-miscellaneous depends on python2.  It would help me 
greatly if you could tell me if that's correct or if it should depend on 
python (if all the scripts in it also work with python3), or it should 
be updated to work with python3?

Additionally, I noted that subversion-tools depends on python (due to an 
explicit requires in the cygport), but... I don't see any python scripts 
there, so I wonder if that should just be removed in future.

Re: python2 removal

[marco atzeri]

On Sun, Apr 2, 2023 at 11:47 AM Jon Turney via Cygwin-apps wrote:
>
> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
> > On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> >>
> >> This has come up in discussion a few times, and is now well overdue, I
> >> think.
> >>
> >> Python 2.7 is the last python2 version, which was sunsetted on January
> >> 1, 2020.
> >>
> > [...]
> >>
> >> 3) There might also still be some other packages lurking which just
> >> install a script with a shebang containing 'python', and assume that
> >> python is python2.  I don't know how we could identify those.
> >
> > The remaining cases of packages which have a dependency on python and/or
> > python2 are either this (packages which contain a python script with a
> > python shebang line), or the other case which I hadn't previously
> > considered - a package which contain an executable or shared library
> > linked with libpython2.7.dll.
> >
> > So, again I need inspect these to determine what should happen to them.
>
> So here's the list, with *tentative* notes of the disposition for each
> package.
>
> As before, I might look at rebuilding some of the more important
> packages, as time permits, and some of these are candidates for removal
> if not updated, but obviously adoptions and input on what is no longer
> useful is welcomed!
>
> I've also adjusted numerous old package versions which depend on
> 'python' to depend on 'python2' when that's what they actually require,
> so they will become not-installable when python2 is removed, and can
> subsequently be expired.
>
> (often these are historical package requirements which were synthesized
> from the current package requirements from before we had per-version
> requirements)
>
> Contrariwise, a few packages (e.g. clang, ibus, libglib2.0-devel, llvm,
> lv2-devel, mysql-server, pulseaudio-equalizer) which depend on python2,
> but contain a script which appears to work with python3 have been
> adjusted to depend on 'python'
>

Thanks John

> > source package         package                 maintainer                    notes      disposition
> > boost                  boost-build             ORPHANED (Yaakov Selkowitz)   [†]        unclear? depends on python2 and python3?
> > boost                  libboost_mpi_python*    "                             [*]        libboost_mpi_python3* exists, so just remove?
> > boost                  libboost_numpy*         "                             [*]        libboost_numpy3* exists, so just remove?
> > boost                  libboost_python*        "                             [*]        libboost_python3_* exists, so just remove?

I will adopt boost.

> > extra-cmake-modules    extra-cmake-modules     ORPHANED (Yaakov Selkowitz)   [†]        probably ok, but should probably update & rebuild

I will look on it

> > inkscape               inkscape                ORPHANED (Yaakov Selkowitz)   [†][§][5]  update and rebuild

I will adopt inkscape

> > octave-miscellaneous   octave-miscellaneous    Marco Atzeri                  [†]        ?
ignore the dependency, it is coming from a demo script. I will remove
on next octave rebuild

> > vim                    vim-python              Marco Atzeri                             empty and obsolete, remove
Noted

Re: python2 removal

[Marco Atzeri]

On 03.04.2023 03:08, marco atzeri wrote:
> On Sun, Apr 2, 2023 at 11:47 AM Jon Turney via Cygwin-apps wrote:

> 
>>> extra-cmake-modules    extra-cmake-modules     ORPHANED (Yaakov Selkowitz)   [†]        probably ok, but should probably update & rebuild
> 

I adopted  extra-cmake-modules and appstream that is required by it.

I will upload as soon finished to clean both builds

Regards
Marco

Re: python2 removal

[Jon Turney]

On 25/02/2023 16:51, Adam Dinwoodie via Cygwin-apps wrote:
> On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
>> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>> [...]
>>>> Python 2.7 is the last python2 version, which was sunsetted on January
>>>> 1, 2020.
>>> [...]
[...]
>>
>>   From a brief survey, only offlineimap and urlgrabber (which should
>> probably be named python-urlgrabber, since it contains a python module)
>> seem to be actively maintained enough to support python3.
>>
>> So I will probably remove the others, and consider if it's possible and
>> worthwhile to update those.
>>
>> (I also noted that breezy appears to be the python3 replacement for bzr
>> and getmail6 appears to be the python3 replacement for getmail.)
> 
> I'm happy to adopt both of these. I'll give Jari a little while to
> reclaim them first, not least as I'm not going to have the time to
> spend on packaging these for at least a week or so, but if Jari (or
> anyone else) doesn't claim them first, I'll send an ITA once I've
> checked I can get the packaging to work.
Gentle ping to ask if you are still intending to package these?

Re: python2 removal

[Adam Dinwoodie]

On Sun, 30 Apr 2023 at 19:25, Jon Turney <jon.turney@dronecode.org.uk> wrote:
>
> On 25/02/2023 16:51, Adam Dinwoodie via Cygwin-apps wrote:
> > On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
> >> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
> >>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
> >>> [...]
> >>>> Python 2.7 is the last python2 version, which was sunsetted on January
> >>>> 1, 2020.
> >>> [...]
> [...]
> >>
> >>   From a brief survey, only offlineimap and urlgrabber (which should
> >> probably be named python-urlgrabber, since it contains a python module)
> >> seem to be actively maintained enough to support python3.
> >>
> >> So I will probably remove the others, and consider if it's possible and
> >> worthwhile to update those.
> >>
> >> (I also noted that breezy appears to be the python3 replacement for bzr
> >> and getmail6 appears to be the python3 replacement for getmail.)
> >
> > I'm happy to adopt both of these. I'll give Jari a little while to
> > reclaim them first, not least as I'm not going to have the time to
> > spend on packaging these for at least a week or so, but if Jari (or
> > anyone else) doesn't claim them first, I'll send an ITA once I've
> > checked I can get the packaging to work.
> Gentle ping to ask if you are still intending to package these?

Yes, they're both on my to-do list, but I've had a whole bunch of real
life come up over the past few months. If the delay is causing issues,
though, I can bump them up my priority list…

Re: python2 removal

[Jon Turney]

On 30/04/2023 21:32, Adam Dinwoodie wrote:
> On Sun, 30 Apr 2023 at 19:25, Jon Turney <jon.turney@dronecode.org.uk> wrote:
>>
>> On 25/02/2023 16:51, Adam Dinwoodie via Cygwin-apps wrote:
>>> On Sat, 25 Feb 2023 at 16:23, Jon Turney via Cygwin-apps wrote:
>>>> On 16/01/2023 12:49, Jon Turney via Cygwin-apps wrote:
>>>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>>> [...]
>>>>>> Python 2.7 is the last python2 version, which was sunsetted on January
>>>>>> 1, 2020.
>>>>> [...]
>> [...]
>>>>
>>>>    From a brief survey, only offlineimap and urlgrabber (which should
>>>> probably be named python-urlgrabber, since it contains a python module)
>>>> seem to be actively maintained enough to support python3.
>>>>
>>>> So I will probably remove the others, and consider if it's possible and
>>>> worthwhile to update those.
>>>>
>>>> (I also noted that breezy appears to be the python3 replacement for bzr
>>>> and getmail6 appears to be the python3 replacement for getmail.)
>>>
>>> I'm happy to adopt both of these. I'll give Jari a little while to
>>> reclaim them first, not least as I'm not going to have the time to
>>> spend on packaging these for at least a week or so, but if Jari (or
>>> anyone else) doesn't claim them first, I'll send an ITA once I've
>>> checked I can get the packaging to work.
>> Gentle ping to ask if you are still intending to package these?
> 
> Yes, they're both on my to-do list, but I've had a whole bunch of real
> life come up over the past few months. If the delay is causing issues,
> though, I can bump them up my priority list…

That's no problem.  Just checking you hadn't changed your mind :)

Re: python2 removal

[Jon Turney]

On 02/04/2023 16:55, Jon Turney via Cygwin-apps wrote:
> On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
>> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
>>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>>
>>>> This has come up in discussion a few times, and is now well overdue, 
>>>> I think.
>>>>
>>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>>> January 1, 2020.
>>>>
[...]
> 
>> source package         package                 
>> maintainer                    notes
>> cfv                    cfv                     Jari 
>> Aalto                    [†][§]
>> svn-load               svn-load                Jari 
>> Aalto                    [†][§]
>> webcheck               webcheck                Jari 
>> Aalto                    [†][§]
>>
>> [†] contains some python scripts
>> [§] script is python2 only, not compatible with python3
> 
> Hi Jari,
> 
> I believe these packages all need updating for python3.
> 
> Please confirm if this assessment is correct, and let me know if you 
> intend to do this, otherwise I will assume these packages are orphaned 
> and they will be removed.

In the absence of any response, I have assumed they are orphaned, and 
removed these.

If that's not what you wanted to happen, please let me know.

Re: python2 removal

[Jon Turney]

On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>
>>> This has come up in discussion a few times, and is now well overdue, 
>>> I think.
>>>
>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>> January 1, 2020.
>>>
>> [...]
>>>
>>> 3) There might also still be some other packages lurking which just 
>>> install a script with a shebang containing 'python', and assume that 
>>> python is python2.  I don't know how we could identify those.
>>
>> The remaining cases of packages which have a dependency on python 
>> and/or python2 are either this (packages which contain a python script 
>> with a python shebang line), or the other case which I hadn't 
>> previously considered - a package which contain an executable or 
>> shared library linked with libpython2.7.dll.
>>
>> So, again I need inspect these to determine what should happen to them.
> 
> So here's the list, with *tentative* notes of the disposition for each 
> package.
> 
> As before, I might look at rebuilding some of the more important 
> packages, as time permits, and some of these are candidates for removal 
> if not updated, but obviously adoptions and input on what is no longer 
> useful is welcomed!

So, I think I've more or less come to the end of packages which seems 
worthwhile for me to rebuild and/or update.

(There's several things which I haven't updated because their 
dependencies also need updating - usually glib, which definitely needs 
attending to, but I'm not going to pull on that thread right now...)


I think the next step is to remove the python27 package itself.

This will make it impossible to install anything which requires it on 
new installations (existing installations which already have the package 
installed will be uneffected).

Once the wailing, rending of garments and gnashing of teeth has died 
down, I can remove the python2 modules and bindings at leisure.

Marco,

As python maintainer, any thoughts on when to do this? Anything you want 
to get done before that?

Re: python2 removal

[Jon Turney]

On 02/04/2023 16:47, Jon Turney via Cygwin-apps wrote:
> On 14/03/2023 19:17, Jon Turney via Cygwin-apps wrote:
>> On 15/01/2023 12:52, Jon Turney via Cygwin-apps wrote:
>>>
>>> This has come up in discussion a few times, and is now well overdue, 
>>> I think.
>>>
>>> Python 2.7 is the last python2 version, which was sunsetted on 
>>> January 1, 2020.
>>>
>> [...]
>>>
>>> 3) There might also still be some other packages lurking which just 
>>> install a script with a shebang containing 'python', and assume that 
>>> python is python2.  I don't know how we could identify those.
>>
>> The remaining cases of packages which have a dependency on python 
>> and/or python2 are either this (packages which contain a python script 
>> with a python shebang line), or the other case which I hadn't 
>> previously considered - a package which contain an executable or 
>> shared library linked with libpython2.7.dll.
>>
>> So, again I need inspect these to determine what should happen to them.
> 
> So here's the list, with *tentative* notes of the disposition for each 
> package.

Here's an updated list of the remaining packages, after removals, 
rebuilds and/or updates:

> source package         package                 maintainer                    notes      disposition
> 
> boost                  boost-build             ORPHANED (Yaakov Selkowitz)   [†]        depends on python2 and python3? Marco Atzeri may adopt
> boost                  libboost_mpi_python*    "                             [*]        libboost_mpi_python3* exists, so just remove?
> boost                  libboost_numpy*         "                             [*]        libboost_numpy3* exists, so just remove?
> boost                  libboost_python*        "                             [*]        libboost_python3_* exists, so just remove?
> cantor                 cantor-backend-python2  ORPHANED (Yaakov Selkowitz)   [*]        leave as is, becomes not-installable (cantor-backend-python3 exists)
> extra-cmake-modules    extra-cmake-modules     Marco Atzeri                  [†]        probably ok, but should probably rebuild
> geany-plugins          geany-plugins-geanypy   ORPHANED (Yaakov Selkowitz)   [*][1]     leave as is, becomes not-installable
> gimp                   gimp-python             ORPHANED (Yaakov Selkowitz)   [*][4]     leave as is, becomes not-installable
> gnome-commander        gnome-commander         ORPHANED (Yaakov Selkowitz)   [*][5]     update and rebuild
> gnumeric               gnumeric-python         ORPHANED (Yaakov Selkowitz)   [*][6]     update and rebuild
> gtranslator            gtranslator             ORPHANED (Yaakov Selkowitz)   [†][5]     update and rebuild
> inkscape               inkscape                ORPHANED (Yaakov Selkowitz)   [†][§][2]  update and rebuild
> kf5-kross-interpreters kf5-kross-python        ORPHANED (Yaakov Selkowitz)   [*][7]     update and rebuild
> kig                    kig                     ORPHANED (Yaakov Selkowitz)   [†][§][7]  update and rebuild
> kross-interpreters     kross-python            ORPHANED (Yaakov Selkowitz)   [*]        leave as is, becomes not-installable (KDE4-era)
> libglade2.0            libglade2.0-devel       ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable (upstream unchanged)
> llvm                   llvm                    ORPHANED (Yaakov Selkowitz)   [†]        leave as is, needs updating but not by me
> lokalize               lokalize                ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable
> octave-miscellaneous   octave-miscellaneous    Marco Atzeri                  [†]        ?
> parley                 parley                  ORPHANED (Yaakov Selkowitz)   [†]        leave as is, becomes not-installable?
> pidgin                 libgnt0                 ORPHANED (Yaakov Selkowitz)   [*]        leave as is, becomes not-installable?
> pidgin                 pidgin                  "                             [†]        leave as is, becomes not-installable?
> pluma                  pluma                   ORPHANED (Yaakov Selkowitz)   [†][§][8]  update and rebuild
> pulseaudio-equalizer   pulseaudio-equalizer    Takashi Yano                  [†]        ?
> scribus                scribus                 ORPHANED (Yaakov Selkowitz)   [*]        leave as is, becomes not-installable
> telepathy-gabble       telepathy-gabble        ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable
> tellico                tellico                 ORPHANED (Yaakov Selkowitz)   [†][§]     leave as is, becomes not-installable
> tracker-miners         tracker-miners          ORPHANED (Yaakov Selkowitz)   [†][§][3]  leave as is, becomes not-installable
> vim                    vim-python              Marco Atzeri                             empty and obsolete, remove
> virt-manager           virt-manager            Jason Pyeron                  [†]        update and rebuild
> xplayer                xplayer                 ORPHANED (Yaakov Selkowitz)   [†][§][5]  update and rebuild
> 
> [*] linked against libpython2.7.dll
> [†] contains some python scripts
> [§] script is python2 only, not compatible with python3
> 
> [1] geanypy is python2 only, removed upstream (replaced by peasy), so just make this uninstallable without python2 for the moment
> [2] needs updated pangocairo
> [3] this dependency seems to be because of a test script which is installed
> [4] it seems like gimp 2.x doesn't support python3, so we'd rebuild without python support; to update also needs many dependencies updating
> [5] needs glib update
> [6] needs libgoffice, libgsf update
> [7] needs updated extra-cmake-modules
> [8] requires gtksourceview4 packaging

Re: python2 removal

[Jon Turney]

On 04/06/2023 20:17, Jon Turney via Cygwin-apps wrote:
[...]
> 
> I think the next step is to remove the python27 package itself.
> 
> This will make it impossible to install anything which requires it on 
> new installations (existing installations which already have the package 
> installed will be uneffected).
> 
> Once the wailing, rending of garments and gnashing of teeth has died 
> down, I can remove the python2 modules and bindings at leisure.
> 
> Marco,
> 
> As python maintainer, any thoughts on when to do this? Anything you want 
> to get done before that?

Marco,

Unless I hear otherwise from you, I shall try to do this removal 
sometime this coming week.

Re: python2 removal

[Marco Atzeri]

On 02.07.2023 16:30, Jon Turney wrote:
> On 04/06/2023 20:17, Jon Turney via Cygwin-apps wrote:
> [...]
>>
>> I think the next step is to remove the python27 package itself.
>>
>> This will make it impossible to install anything which requires it on 
>> new installations (existing installations which already have the 
>> package installed will be uneffected).
>>
>> Once the wailing, rending of garments and gnashing of teeth has died 
>> down, I can remove the python2 modules and bindings at leisure.
>>
>> Marco,
>>
>> As python maintainer, any thoughts on when to do this? Anything you 
>> want to get done before that?
> 
> Marco,
> 
> Unless I hear otherwise from you, I shall try to do this removal 
> sometime this coming week.
> 

Jon,
feel free.

For personal reason I will not be present in the coming weeks

Thanks
MArco

Re: python2 removal

[Jon Turney]

On 07/07/2023 19:54, Marco Atzeri via Cygwin-apps wrote:
> On 02.07.2023 16:30, Jon Turney wrote:
>> On 04/06/2023 20:17, Jon Turney via Cygwin-apps wrote:
>> [...]
>>>
>>> I think the next step is to remove the python27 package itself.
>>>
>>> This will make it impossible to install anything which requires it on 
>>> new installations (existing installations which already have the 
>>> package installed will be uneffected).
>>>
>>> Once the wailing, rending of garments and gnashing of teeth has died 
>>> down, I can remove the python2 modules and bindings at leisure.
>>>
>>> Marco,
>>>
>>> As python maintainer, any thoughts on when to do this? Anything you 
>>> want to get done before that?
>>
>> Marco,
>>
>> Unless I hear otherwise from you, I shall try to do this removal 
>> sometime this coming week.
>>
> 
> Jon,
> feel free.

Done!

> For personal reason I will not be present in the coming weeks

Thanks for letting me know.

Re: python2 removal

[Jon Turney]

On 09/07/2023 17:50, Jon Turney via Cygwin-apps wrote:
> On 07/07/2023 19:54, Marco Atzeri via Cygwin-apps wrote:
>> On 02.07.2023 16:30, Jon Turney wrote:
>>> On 04/06/2023 20:17, Jon Turney via Cygwin-apps wrote:
>>> [...]
>>>>
>>>> I think the next step is to remove the python27 package itself.
>>>>
>>>> This will make it impossible to install anything which requires it 
>>>> on new installations (existing installations which already have the 
>>>> package installed will be uneffected).
>>>>
>>>> Once the wailing, rending of garments and gnashing of teeth has died 
>>>> down, I can remove the python2 modules and bindings at leisure.

I've finally got around to vaulting all the remaining python2 modules 
and bindings.

Looking at the remaining python(|2)-* packages:

> python-cairo-devel	Python bindings to libcairo
> python-dbus-devel	Python D-Bus bindings
> python-gdal	Geospatial Data Abstraction Library - (Python)
> python-gi-common	Python GObject Introspection bindings
> python-gi-devel	Python GObject Introspection bindings
> python-gobject-common	Python GLib/GObject/GIO bindings
> python-gobject-devel	Python GLib/GObject/GIO bindings
> python-gobject-doc	Python GLib/GObject/GIO bindings
> python-gtk2.0-demo	Python bindings for GTK+2 and libglade (demo application)
> python-gtk2.0-devel	Python bindings for GTK+2 and libglade (development files)
> python-gtk2.0-doc	Python bindings for GTK+2 and libglade
> python-netsnmp	Net-SNMP (python)
> python-orbit-devel	Python bindings for ORBit-2
> python-pip-wheel	Python package installation tool
> python-pyatspi-common	Python AT-SPI/D-Bus bindings
> python-pykde4-common	Python KDE4 bindings
> python-pykde4-devel	Python KDE4 bindings
> python-pyqt4-common	Python Qt4 bindings
> python-pyqt4-devel	Python Qt4 bindings
> python-pyqt5-common	Python Qt5 bindings
> python-pyqt5-qt3d-common	Python Qt3D bindings
> python-pyqt5-qt3d-devel	Python Qt3D bindings
> python-pyqt5-qtchart-common	Python QtCharts bindings
> python-pyqt5-qtchart-devel	Python QtCharts bindings
> python-pyqt5-qtdatavisualization-common	Python QtDataVisualization bindings
> python-pyqt5-qtdatavisualization-devel	Python QtDataVisualization bindings
> python-setuptools-wheel	Python package management tool
> python-webkit-devel	Python WebKit/GTK+ bindings
> python-wheel-wheel	Python package format module
> python-wx-devel	wxWidgets C++ application framework (Python bindings)
> python2-xapian-doc	Python bindings for the Xapian search engine library

I'll have to look these over in more detail, but most of the python-*- 
{common,devel,wheel) seem reasonable to allow to continue to exist.

python2-xapian-doc can obviously also be removed.

python-wx-devel is the last remnant of python2 bindings for wx (the 
python3 binding comes from a different, irregularly named source package 
python3-wx), so can also be removed.

python-{gdal,netsnmp} are irregularly named, and should be obsoleted and 
renamed as python3-foo and/or python3X-foo when they next get rebuilt.

There's still some packages which depend on python2 and python2 modules 
remaining, which haven't been rebuilt yet, which are probably all 
candidates for removal if not adopted.  I'll produce a list before that 
happens, though.

On to python3.5 (EOL Sep 2020) next, I suppose...

Re: python2 removal

[Jon Turney]

On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
[...]
>> python-wx-devel    wxWidgets C++ application framework (Python bindings)
[...]
> 
> python-wx-devel is the last remnant of python2 bindings for wx (the 
> python3 binding comes from a different, irregularly named source package 
> python3-wx), so can also be removed.

Cc:ing Hamish as a note that if/when python3-wx is updated, we should 
see if it's now possible to rename the source package to python-wx.

Unrelated question: Do you mind if I vault the (orphaned, last updated 
circa 2016) wxWidgets 2.8 packages, which I assume are of very limited 
use to anybody...

Re: python2 removal

[Hamish McIntyre-Bhatty]

On 18/01/2024 19:40, Jon Turney wrote:
> On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
> [...]
>>> python-wx-devel    wxWidgets C++ application framework (Python 
>>> bindings)
> [...]
>>
>> python-wx-devel is the last remnant of python2 bindings for wx (the 
>> python3 binding comes from a different, irregularly named source 
>> package python3-wx), so can also be removed.
>
> Cc:ing Hamish as a note that if/when python3-wx is updated, we should 
> see if it's now possible to rename the source package to python-wx.
>
> Unrelated question: Do you mind if I vault the (orphaned, last updated 
> circa 2016) wxWidgets 2.8 packages, which I assume are of very limited 
> use to anybody...

Okay, I'd be happy to try renaming the package to python-wx the next 
time I update python3-wx.

I'm indifferent to the wxWidgets 2.8 packages, I've never used them and 
wxWIdgets 3.0 is also pretty compatible with 2.8 from my understanding, 
so the 2.8 packages aren't needed.

Hamish

Re: python2 removal

[Hamish McIntyre-Bhatty]

On 19/01/2024 18:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 18/01/2024 19:40, Jon Turney wrote:
>> On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
>> [...]
>>>> python-wx-devel    wxWidgets C++ application framework (Python 
>>>> bindings)
>> [...]
>>>
>>> python-wx-devel is the last remnant of python2 bindings for wx (the 
>>> python3 binding comes from a different, irregularly named source 
>>> package python3-wx), so can also be removed.
>>
>> Cc:ing Hamish as a note that if/when python3-wx is updated, we should 
>> see if it's now possible to rename the source package to python-wx.
>>
>> Unrelated question: Do you mind if I vault the (orphaned, last updated 
>> circa 2016) wxWidgets 2.8 packages, which I assume are of very limited 
>> use to anybody...
> 
> Okay, I'd be happy to try renaming the package to python-wx the next 
> time I update python3-wx.
> 
> I'm indifferent to the wxWidgets 2.8 packages, I've never used them and 
> wxWIdgets 3.0 is also pretty compatible with 2.8 from my understanding, 
> so the 2.8 packages aren't needed.
> 
> Hamish
> 
>
I realise I forgot to ask, but how could I go about renaming python3-wx 
to python-wx when I update? I also maintained python-wx, so I shouldn't 
need any extra permissions I don't think.

Best,
Hamish

Re: python2 removal

[Jon Turney]

On 10/04/2024 20:19, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 19/01/2024 18:23, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 18/01/2024 19:40, Jon Turney wrote:
>>> On 18/01/2024 19:31, Jon Turney via Cygwin-apps wrote:
>>> [...]
>>>>> python-wx-devel    wxWidgets C++ application framework (Python 
>>>>> bindings)
>>> [...]
>>>>
>>>> python-wx-devel is the last remnant of python2 bindings for wx (the 
>>>> python3 binding comes from a different, irregularly named source 
>>>> package python3-wx), so can also be removed.
>>>
>>> Cc:ing Hamish as a note that if/when python3-wx is updated, we should 
>>> see if it's now possible to rename the source package to python-wx.
>>>
[...]
>>
>> Okay, I'd be happy to try renaming the package to python-wx the next 
>> time I update python3-wx.
>>
[...]
>>
> I realise I forgot to ask, but how could I go about renaming python3-wx 
> to python-wx when I update? I also maintained python-wx, so I shouldn't 
> need any extra permissions I don't think.

Uh, yeah, this is made more complex as we had a 'python-wx' source 
package (for the python2 bindings, now removed), and a separate 
'python3-wx' source package (for python3 bindings).

I guess what wants to happen is:

* (If you care about such things) Merge the python3-wx history into the 
python-wx packaging git repo (git merge --allow-unrelated-histories 
seems like it might be the right voodoo runes).

* Rename python3-wx.cygport to python-wx.cygport and update version or 
bump release.
  * When it comes to uploading the rebuilt packages, there's 
unfortunately (currently) a manual step involved (for me to) adjust the 
"allegiance" of the 'python3n-wx' install packages from the 'python3-wx' 
source package to 'python-wx', but I'll do that when needed (or maybe 
even get around to automating it this time...)