Python 2 or 3

[Enrico 'Henryx' Bianchi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steven D'Aprano wrote:

> RHEL supports Python 3, it just doesn't provide Python 3.

True, but as you say later, the only method is to recompile. So, if I want 
to use Python 3 in a production environment like RHEL, I need:

 - A development environment similar to production (e.g. if I use RHEL 5 in
   production, I need at least a CentOS 5.x);
 - Compile Python 3 in a development environment;
 - Write the python app;
 - Release a *huge* package to install.

The only bright side is to freeze version of Python and the libraries, but 
every update (e.g. bug fixing on a library) is by hand

> When installing, don't use "make install", as that will replace the
> system Python, instead use "make altinstall".

Good, I didn't know this option

> Then the command "python"
> will still refer to the system Python (probably Python 2.4 or 2.5?), and
> "python3" should refer to Python 3.x.

RHEL (and CentOS) 5.x use Python 2.4

> You shouldn't be learning programming on a production server :)

Of course, but if I want to use an application written in Python 3 on a 
production environment which doesn't support it, I have to prepare at least 
a development environment similar to production (ok, ok, with a VM is 
simple, but I need to track the exception)

Enrico
P.S. an alternative may be cx_freeze, but I don't know exactly hot it works
P.P.S. I'm boring, but I would like my point of view because I've found 
precisely in this case
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJO40dHAAoJED3SMOGZLYdYIPoH/1J6OljjCJQnmR/uwjEFCrHy
TEMpfKodD40gL7lOZLMHnpJrs+Ct2Vo/1+mtAIi+vZ6rkhFG50ykBJMAlMgXkCjt
I6fkp9YLKmFX9OjRuJ9qE+2P5PliyNDPKVljyfaXMhalbrtHnn7mrL9524TzhcoG
+Ape1U9MPTu3naVULKWK0FjGa/RwhbSOdDOKX2IBmRHFEgtf3dZJ2xNYXUJnhnT8
fbfD87ykXyyVg6LS8c14PPeWnpFeeZBQappjoHg9+XZd8/Y1uH1NuP7k4cepzJB2
Car4lucChW9+llM4mz1BADQZuo4J1v71K5DR8mVXyM2usUlNWelkgR6GVWUmXE0=
=trwj
-----END PGP SIGNATURE-----