What's wrong with:

apt-get install python3

It's always worked for me.

Django targets Python >= 3.2, and Debian stable provides 3.1.

FYI the demo uses a manually compiled Python.

In that case, I wouldn't worry about installing for all users. I'd build from source and configure with the --prefix argument. Then I'd start Django using that specific Python.

Or, since Django on Python3 doesn't seem production ready yet, I'd "upgrade" to Debian testing or unstable, and hope that by the time Django became production ready Py3.2 was in Debian stable.

If you're currently on stable but are comfortable running a mixed system, you can install python3 from testing to get 3.2.

Check out pythonbrew [1] - it makes installing different Pythons pretty simple. Perhaps not the best solution for a server, though.

[1] https://github.com/utahta/pythonbrew/

EDIT: pythonz is pretty good too (http://saghul.github.com/pythonz/)

Debian and Ubuntu have their own way of managing Python libraries and paths and I can't say I understand it. The modules are stored all over the place, with 'site-packages' being in one place, another called 'distro-packages' (if memory doesn't fail me) somewhere else, and user installed packages in yet another directory. It's hell.

It is absolute confusion, and when you think you've got it, they change it again. I suppose it makes sense to someone somewhere, who probably thinks they're being helpful by inventing all these complicated schemes.

Look up virtualenv and virtualenvwrapper. It isn't quite analogous, but I think of virtualenv as Python's RVM. Works well enough for me.

See this answer here: http://askubuntu.com/questions/14615/how-do-i-make-the-termi...