Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #97227 > unrolled thread

Re: Linux Mint installation of Python 3.5

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Linux Mint installation of Python 3.5 Mario Figueiredo <marfig@gmx.com> - 2015-09-30 04:00 +0100
    Re: Linux Mint installation of Python 3.5 Steven D'Aprano <steve@pearwood.info> - 2015-09-30 13:23 +1000
      Re: Linux Mint installation of Python 3.5 Chris Angelico <rosuav@gmail.com> - 2015-09-30 13:36 +1000

#97227 — Re: Linux Mint installation of Python 3.5

On 09/30/2015 03:44 AM, Chris Angelico wrote:
> 
> The easiest way to install something from source is to use 'make
> altinstall' for the final step. That should install you a 'python3.5'
> binary without touching the 'python3' binary. That said, though, it's
> entirely possible that upgrading 'python3' from 3.4 to 3.5 won't
> actually break anything; it won't break any script that explicitly
> looks for python3.4, and there's not a huge amount of breakage. But to
> be on the safe side, use altinstall and explicitly ask for python3.5
> any time you want it.
> 

Thank you Chris. That will set me on my path.

> Personally, I use the regular 'make install', but that's because I'm
> on Debian - the system Python is 2.7.

Unfortunately Ubuntu based distros are going through a 2.x to 3.x
transition period. Both Pythons are installed and are system dependencies.

And their finicky dependency on Python really make these distros not
very friendly for Python development. If I do end up successfully
upgrading from 3.4 to 3.5, I will most likely forfeit my ability to
upgrade the Mint version in the future without a full system
installation. So the solution is to just maintain 3 different versions
of python my machine. Ridiculous.

[toc] | [next] | [standalone]

#97232

On Wed, 30 Sep 2015 01:00 pm, Mario Figueiredo wrote:

> So the solution is to just maintain 3 different versions
> of python my machine. Ridiculous.

Not at all. It's not like a Python install is that big -- Python 3.3 is only
about 150MB.

It's a little sad that Ubuntu isn't able to transition between 2 and 3 in
one release, but that's their problem, not yours. You shouldn't be touching
the system Python(s), you should leave that for Ubuntu to upgrade.

I think that it is generally a good idea to keep your development Python
separate from the system Python, even if they use the same version. That
way, even if you accidentally break your development Python, the system
Python will continue to work.



-- 
Steven

[toc] | [prev] | [next] | [standalone]

#97233

On Wed, Sep 30, 2015 at 1:23 PM, Steven D'Aprano <steve@pearwood.info> wrote:
> I think that it is generally a good idea to keep your development Python
> separate from the system Python, even if they use the same version. That
> way, even if you accidentally break your development Python, the system
> Python will continue to work.

What, you don't enjoy fixing a broken Python using no tool that itself
requires Python? Where's the fun in a boring life?!?

ChrisA

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web