From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: pip newer version available
Date: Sat, 28 Nov 2020 15:18:22 +0100 [thread overview]
Message-ID: <CAEhDDbCfa06owmc_g7jpfBAmJemtUHi_P2cCHr-g5C+FQb3hyw@mail.gmail.com> (raw)
Hi all,
I recently installed python27-pip (20.2.2-1) and did a "pip install
grip", and at the end, pip displayed the following warning (or maybe
it's just an advertisement)
WARNING: You are using pip version 20.1.1; however, version 20.2.4 is available.
You should consider upgrading via the
'c:\users\csaba\appdata\local\programs\python\python38\python.exe -m
pip install --upgrade pip
' command.
Is it a good idea doing this upgrade ("behind the back" of the Cygwin
installer), or should I ignore this message until pip 20.2.4 (or
higher) becomes available as a Cygwin package?
Also, why is there a discrepancy between Cygwin's pip version and
pip's own version?
$ which python
/usr/bin/python
$ python -V
Python 2.7.18
$ which pip
/cygdrive/c/Users/Csaba/AppData/Local/Programs/Python/Python38/Scripts/pip
Whoops!
$ which grip
/cygdrive/c/Users/Csaba/AppData/Local/Programs/Python/Python38/Scripts/grip
$ find /usr -name pip -type f
$
Check https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fpython27-pip%2Fpython27-pip-20.2.2-1&grep=%5Cbpip%5Cb
$ which pip2
/usr/bin/pip2
Aha!
$ pip2 install grip
... lots of output ...
WARNING: You are using pip version 20.2.2; however, version 20.2.4 is available.
You should consider upgrading via the '/usr/bin/python2.7 -m pip
install --upgrade pip' command.
$ which grip
/usr/bin/grip
Finally, sanity returns. Still, the question remains whether upgrading
pip like this is advisable or not.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next reply other threads:[~2020-11-28 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 14:18 Csaba Raduly [this message]
2020-11-28 17:54 ` Ken Brown
2020-11-28 18:27 ` Marco Atzeri
2020-11-28 19:05 ` Nicholas Clark
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=CAEhDDbCfa06owmc_g7jpfBAmJemtUHi_P2cCHr-g5C+FQb3hyw@mail.gmail.com \
--to=rcsaba@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).