Updating Python version

vysero · 07-19-2018, 01:23 PM

Quote:

Originally Posted by hydrurga

Yes. A PPA is a Personal Package Archive. That's what you added to your software sources.

Alright, I went ahead and sent him an email describing the problem and a link to this discussion. Hopefully, he will respond fairly quickly. In the meantime, I was wondering.. if I just unpack this tgz file directly into usr/local/lib (which is where py2.7 and py3.5 currently reside) will it just work or is there something else I am going to have to do? I got the tgz directly from python website.

vysero · 07-19-2018, 01:24 PM

Quote:

Originally Posted by hydrurga

Just a thought. Disable the PPA and then run apt update again - if you don't receive the same "AppStream cache update completed, but some metadata was ignored due to errors" message then faulty metadata at that PPA is most probably to blame.

Okay, um how would I go about disabling the PPA?

hydrurga · 07-19-2018, 01:27 PM

Either uncheck it in Software Sources, or sudo gedit /etc/apt/sources.list.d/jonathonf-ubuntu-python-3_7-xenial.list and insert a # character at the start of the deb line to comment it out.

vysero · 07-19-2018, 01:34 PM

Quote:

Originally Posted by hydrurga

Either uncheck it in Software Sources, or sudo gedit /etc/apt/sources.list.d/jonathonf-ubuntu-python-3_7-xenial.list and insert a # character at the start of the deb line to comment it out.

Interesting:

Code:

rob@server038:~$ sudo gedit /etc/apt/sources.list.d/jonathonf-ubuntu-python-3_7-xenial.list

(gedit:18118): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (gedit:18118): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported

** (gedit:18118): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported

** (gedit:18118): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported

brought up the file:

Code:

deb http://ppa.launchpad.net/jonathonf/python-3.7/ubuntu xenial main
# deb-src http://ppa.launchpad.net/jonathonf/python-3.7/ubuntu xenial main

Why is the second deb-src line already commented out?

Anyways I commented out that first line and saved it and then I ran apt update again:

Code:

rob@server038:~$ sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]                                                                      
Hit:3 http://ppa.launchpad.net/dominik-stadler/dsta-xenial-ppa/ubuntu xenial InRelease                                                           
Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]                                                    
Hit:6 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu xenial InRelease                                                                                                  
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]                                                                                              
Hit:8 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease                                                                                                              
Hit:5 http://screenshots.getdeb.net trusty-getdeb InRelease
Fetched 323 kB in 1s (259 kB/s)                   
Reading package lists... Done
Building dependency tree       
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.

Edit: *first

hydrurga · 07-19-2018, 01:44 PM

You can just ignore those warnings when starting gedit.

Your packaging system is probably configured to disable source code repositories (perhaps a setting in Software Sources, or whatever the Ubuntu equivalent is).

It looks as if the metadata in that PPA is faulty then. Annoying, I know. You either need to find another PPA/repo/way of updating Python, or contact the PPA administrator.

Just a note that personally I don't like changing the two versions of Python (2 and 3) that normally come with an LTS distro - they are much used by the system so I prefer to stick to the main repo versions rather than risk breaking my system. The very least you should be doing, imo, is making a system backup/snapshot/image before you muck around with the Python 3 version so that you can roll back if things go awry.

vysero · 07-19-2018, 01:57 PM

Quote:

Originally Posted by hydrurga

You can just ignore those warnings when starting gedit.

Your packaging system is probably configured to disable source code repositories (perhaps a setting in Software Sources, or whatever the Ubuntu equivalent is).

It looks as if the metadata in that PPA is faulty then. Annoying, I know. You either need to find another PPA/repo/way of updating Python, or contact the PPA administrator.

Just a note that personally I don't like changing the two versions of Python (2 and 3) that normally come with an LTS distro - they are much used by the system so I prefer to stick to the main repo versions rather than risk breaking my system. The very least you should be doing, imo, is making a system backup/snapshot/image before you muck around with the Python 3 version so that you can roll back if things go awry.

Hm well I decided to give the guid I found here at:
https://www.linuxbabe.com/ubuntu/ins...04-16-10-17-04

a shot and apparently it worked. I will get back to you if I run into any problems from here on out. Unfortunately, I did not read your last message before I went ahead with the instillation of 3.7

hydrurga · 07-19-2018, 02:04 PM

Quote:

Originally Posted by vysero

Hm well I decided to give the guid I found here at:
https://www.linuxbabe.com/ubuntu/ins...04-16-10-17-04

a shot and apparently it worked. I will get back to you if I run into any problems from here on out. Unfortunately, I did not read your last message before I went ahead with the instillation of 3.7

No problem. Which method did you use in the end?

vysero · 07-19-2018, 02:12 PM

Quote:

Originally Posted by hydrurga

No problem. Which method did you use in the end?

I used: Method 1: Compile and Install Python 3.6 on Ubuntu 16.04. Unfortunately, I am having trouble with:

a) installing modules
b) getting PyCharm to use 3.7

apparently, the executable for 3.7 is not located in the same area as the exicutables for 2.x and 3.5

hydrurga · 07-19-2018, 02:23 PM

That sounds like a new thread.

I have to say that personally if I were wanting to run the latest versions of Python, I would go with a rolling release distro such as Manjaro where they are supported as being part of the main system. You'd probably have less problems that way. You could even run that rolling release distro in a VM and do all your Python development work in that. That would mean that you could leave your main system alone while being able to indulge in cutting-edge development. Just a thought.

vysero · 07-19-2018, 02:23 PM

@hydrurga The fellow who hosted that PPA said there are not packages in that PPA.

hydrurga · 07-19-2018, 02:26 PM

Quote:

Originally Posted by vysero

@hydrurga The fellow who hosted that PPA said there are not packages in that PPA.

That would explain what you've seen. The question is: why is it maintained then? Maybe it's a temporary issue while the package is being updated or something. If not, other people are going to be led astray.

vysero · 07-19-2018, 02:28 PM

Quote:

Originally Posted by hydrurga

That sounds like a new thread.

I have to say that personally if I were wanting to run the latest versions of Python, I would go with a rolling release distro such as Manjaro where they are supported as being part of the main system. You'd probably have less problems that way. You could even run that rolling release distro in a VM and do all your Python development work in that. That would mean that you could leave your main system alone while being able to indulge in cutting-edge development. Just a thought.

Myk267 · 07-19-2018, 09:04 PM

I found a healthier looking PPA, if our OP would like to try that route again: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa

I don't think building Python from source is all that scary as long as one carefully read the instructions.

Quote:

Originally Posted by hydrurga

That sounds like a new thread.

I have to say that personally if I were wanting to run the latest versions of Python, I would go with a rolling release distro such as Manjaro where they are supported as being part of the main system. You'd probably have less problems that way. You could even run that rolling release distro in a VM and do all your Python development work in that. That would mean that you could leave your main system alone while being able to indulge in cutting-edge development. Just a thought.

I think suggesting a completely different distribution is a little extreme.

hydrurga · 07-20-2018, 04:59 AM

Quote:

Originally Posted by Myk267

I found a healthier looking PPA, if our OP would like to try that route again: https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa

I don't think building Python from source is all that scary as long as one carefully read the instructions.

I think suggesting a completely different distribution is a little extreme.

It would be a VM work area where the OP could play with different Python versions without danger of breaking their main production system. Not extreme in the slightest.