On Sat, 26 Dec 2020, Terry Reedy wrote:
Separate 'pip' executables can be ambiguous as to which python they will
invoke. Some people consider them a mistake.
Terry,
Until there's no more python2 it can remain confusing.
I found part, if not all, of my problem. The SlackBuild scripts for
mult
On Sat, 26 Dec 2020, Barry Scott wrote:
It works great with 3.9. which web psge did you see the claim on?
Barry,
I don't recall which pip3 installation page it was. But I used 'python3
get-pip.py' and that worked.
Stay well,
Rich
--
https://mail.python.org/mailman/listinfo/python-list
On 12/26/2020 12:13 PM, Rich Shepard wrote:
Running Slackware-14.2/x86_64 here. I'm trying to learn if any installed
applications are still dependent on Python2 (version 2.7.17 installed) as
its EOL is this coming Thursday and I want to clean out all Python2 modules
and replace them with their Py
On Sat, 26 Dec 2020, Mats Wichmann wrote:
pip supports 3.9 fine, and is just about to lose support for 2.x entirely.
Mats,
Yes, it does.
this sounds like a Slack packaging issue, have you checked with appropriate
forums_
It's apparently a local issue: my python3 packages ended up in
/usr/
On 12/26/20 10:13 AM, Rich Shepard wrote:
Running Slackware-14.2/x86_64 here. I'm trying to learn if any installed
applications are still dependent on Python2 (version 2.7.17 installed) as
its EOL is this coming Thursday and I want to clean out all Python2 modules
and replace them with their Pyth
> On 26 Dec 2020, at 17:13, Rich Shepard wrote:
>
> Running Slackware-14.2/x86_64 here. I'm trying to learn if any installed
> applications are still dependent on Python2 (version 2.7.17 installed) as
> its EOL is this coming Thursday and I want to clean out all Python2 modules
> and replace t
