Python-3.7.2 arrived in current

marrowsuck · 02-21-2019, 12:24 AM

I've waited for this. No all that's left is the final switch to python -> python3.

Many thanks

!

khronosschoty · 02-21-2019, 05:57 PM

teoberi · 02-22-2019, 05:25 AM

And break all the modules compiled with the previous version of Python (3.6). Ex. pypolicyd-spf.

bassmadrigal · 02-22-2019, 11:55 AM

Quote:

Originally Posted by teoberi

And break all the modules compiled with the previous version of Python (3.6). Ex. pypolicyd-spf.

Breakages are expected to happen on -current with 3rd-party packages when upgrades like this occur. It is just one of the things that you have to deal with when you run -current.

dugan · 02-22-2019, 01:21 PM

Quote:

Originally Posted by teoberi

And break all the modules compiled with the previous version of Python (3.6). Ex. pypolicyd-spf.

Post a complete list please.

bassmadrigal · 02-22-2019, 04:18 PM

Quote:

Originally Posted by dugan

Post a complete list please.

I think it was just because it was compiled against python3.6. My guess is it and its dependencies just needs to be compiled against python3.7. Pat recompiled many python programs when he migrated to 3.7.

dugan · 02-22-2019, 04:22 PM

Aah, right. . In that case, you can just look in /usr/lib64/python3.6/site-packages for the list.

USUARIONUEVO · 02-22-2019, 04:25 PM

Quote:

Originally Posted by teoberi

And break all the modules compiled with the previous version of Python (3.6). Ex. pypolicyd-spf.

If no like breakegaes, go then with stable 14.2 , but if you use slackbuilds , bad notives for you , migration to 3.7 are testing ..hahaha

https://git.slackbuilds.org/slackbui...87cc158e7ad7c8

marrowsuck · 02-22-2019, 05:18 PM

To list all your packages with python3.6 modules you can use this command:

Quote:

grep "usr/lib64/python3.6/" /var/log/packages/* | awk -F ":" '{ print $1 }' | uniq

bassmadrigal · 02-22-2019, 05:58 PM

Quote:

Originally Posted by marrowsuck

To list all your packages with python3.6 modules you can use this command:

I had more fun with it and updated your command to just show package names and make it work with both 32bit and 64bit Slackware.

Code:

grep "/python3.6/" /var/log/packages/* | awk -F ":" '{ print $1 }' | uniq | cut -d/ -f5 | rev | cut -d- -f4- | rev

teoberi · 02-23-2019, 01:26 AM

My post was not a complaint but just a little alert.
I've been using Slackware-current for a few years, so I like breakages though there are few (in the case of major updates for Perl, Python, Dovecot, etc.).
I do not use Slackbuilds because the compilation options are not always what I want (sometimes even some original Slackware packages), so I compile them from sources.
In my post I have referred to modules compiled by me not to those included in Slackware, for example those required for pypolicyd-spf.

chrisVV · 02-23-2019, 04:28 AM

I have noticed one oddity with python-3.7. Packages installed with the --user option ('python3 setup.py install --user'), including with pip ('pip3 install --user [package]'), using slackware64-current appear in $HOME/.local/lib64/python[2.7][3.6]/site-packages with python-2.7 and python-3.6, but in $HOME/.local/lib/python3.7/site-packages with python-3.7.

That is to say, they are installed in the user's local lib directory rather than the lib64 directory. Despite that, they appear to work fine.