public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: python26 remnants
Date: Thu, 12 Jan 2023 16:53:25 +0000	[thread overview]
Message-ID: <a9b53830-feee-12d9-dc1f-60986d7246f6@dronecode.org.uk> (raw)


Preparatory to removal of python27, the final python2 version, I've been 
cleaning up the last remnants of python26.

There are still some old (pre-2012) packages which install files into 
/usr/lib/python2.6/site-packages/, I removed the following package versions:

bzr-fastimport-0.13.0-1
cvs2svn-2.3.0-1
getmail-4.34.0-1
python-fastimport-0.9.2-1
python-feedparser-5.0.1-1
python-pyrex-0.9.9-2
xml2po-0.20.10-1 (gnome-doc-utils)

I retained for the moment, as the most recent version:

archivemail-0.9.0-1
flawfinder-1.27-2

Jari,

As the maintainer of both of these, what do you want to do with these 
two packages?

These are just python scripts, which install an .egg-info file into 
usr/lib/python2.6/site-packages/

I am sceptical that they work as desired currently, as the python 
scripts which they contain probably assume /usr/bin/python is python2, 
which is increasingly unlikely to be the case.

If you want to orphan them, they will be removed.

If you think they are still useful, it would help if you could please 
produce updated packages for python3, or assure me that isn't needed.

             reply	other threads:[~2023-01-12 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 16:53 Jon Turney [this message]
2023-02-18 16:13 ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9b53830-feee-12d9-dc1f-60986d7246f6@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=jari.aalto@cante.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).