Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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
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.
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.
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
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
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.
@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.
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 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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
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.
