public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: python 3.9 packages
Date: Fri, 24 Dec 2021 07:57:43 +0100	[thread overview]
Message-ID: <3c789d7a-e4ac-f68c-4d01-dc9d88e25857@gmail.com> (raw)
In-Reply-To: <CANV2+nXWaHiui6JdsdvhtMLjDzmPCUx-VrmoALWDYVq8ooTxsg@mail.gmail.com>

On 23.12.2021 21:34, Russell VT wrote:
> Thanks Marco!
> 
> One small question/caveat, though, if I may?
> 
> 
> On Tue, Dec 21, 2021, 9:11 AM Marco Atzeri via Cygwin-announce <
> cygwin-announce@cygwin.com> wrote:
> 
>> [...]
>>
>> https://www.python.org/dev/peps/pep-0394/
>> In other systems as Debian
>> /usr/bin/python is discouraged.
>>
>> As on Cygwin we have still several third packages depending on
>> python2, the usage of alternatives should allow to manage
>> until all are updated to python3
>>
> 
> Even being a Debian / Mint / Ubuntu fan, there's still an incredible of
> stuff that uses "/usr/bin/python," instead of something like "/usr/bin/env
> python." It seems "not unreasonable" to continue to support that link, just
> to allow people who use Cygwin for development, a little additional sanity
> for the time being?
> 
> That said, people *should* be transitioning to other tools, such as pyenv
> or pipenv, to better manage their environments (or, in the case of later
> python 3 versions, the built-in venv mechanism)
> 
> 
> Regards
>> Marco Atzeri
>>
> 
> Cheers!
> Russell VT
> 

Hi Russell,

  $ alternatives --display python
python - status is auto.
  link currently points to /usr/bin/python3.9
/usr/bin/python2.7 - priority 27
/usr/bin/python3.6 - priority 36
/usr/bin/python3.7 - priority 37
/usr/bin/python3.8 - priority 38
/usr/bin/python3.9 - priority 39
Current `best' version is /usr/bin/python3.9.

python and python3 are still provided.
I am not planning to remove it.

"until all are updated to python3" means that some packages are
still build with python2 and need rebuild/update for python3

Regards

  reply	other threads:[~2021-12-24  6:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 16:06 Marco Atzeri via Cygwin-announce
2021-12-22 13:52 ` airplanemath
2021-12-23 20:00   ` Marco Atzeri
2021-12-24 10:57     ` Jon Turney
2021-12-24 11:16       ` Marco Atzeri
2021-12-24 13:53         ` Jon Turney
2021-12-23 20:34 ` Russell VT
2021-12-24  6:57   ` Marco Atzeri [this message]
2022-03-20 16:00 ` deprecate pytz? Brian Inglis
2023-03-07 21:18   ` deprecate pytz? or update pytz to 2022g/2022.7.1 Brian Inglis
2023-03-07 21:35     ` marco atzeri
2023-03-08  5:11       ` Marco Atzeri
2023-03-26 20:45         ` update pytz to 2023.2/2023b tzdata Brian Inglis
2023-03-27  0:13           ` update pytz to 2023.2/2023b tzdata? Brian Inglis
2021-12-31 10:41 [ANNOUNCEMENT] Updated: python 3.9 packages Marco Atzeri via Cygwin-announce
2022-01-09 13:33 Marco Atzeri via Cygwin-announce
     [not found] <280449814.1214701.1641799592359.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-10  7:26 ` Tatsuro MATSUOKA
2022-01-10 13:09   ` marco atzeri
2022-01-10 22:45     ` Marco Atzeri
2022-01-23 11:49 Marco Atzeri via Cygwin-announce
2022-01-24  5:15 Marco Atzeri via Cygwin-announce
2022-02-27 12:00 Marco Atzeri via Cygwin-announce

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=3c789d7a-e4ac-f68c-4d01-dc9d88e25857@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).