Forums

I really like that python goes to python2 (latest version you have) and python3 goes to python3.

Python 3's latest released version is, as of a few days ago, no longer 3.4, but 3.5. When will you add it in here?

I know, greedy greedy. And I probably won't use much of Python 3.5's new features yet.

But PythonAnywhere is so good, I figure I can ask for more! ;-)

It's definitely coming! One problem we have is that right now, everyone has to use the same set of Python versions. And virtualenvs link to the specific point release of Python, for example to 2.7.6 rather than to 2.7. If we upgrade a specific Python version (let's say, 2.7.6 to 2.7.10) everyone's virtualenvs will be broken because you can't have two different point releases installed on the same system.

This means that if we install 3.5.0, we'll not be able to upgrade it to 3.5.1. So we're waiting until we're pretty sure that 3.5.0 is reasonably bug-free before installing it.

Of course, the proper long-term fix is to support different execution environments, so that we can upgrade the default system image to the latest point releases but people can choose to remain on older ones if they have virtualenvs depending on them. We're working on that (our most recent blog post is about some Docker-related work that is largely driven by that requirement). But that's a little bit of a way down the line.

So what do I do if my django project is in Python 3.5.0 and I would like to use your services ?

It's going to be a while before we can support 3.5 I'm afraid.

Does your project actually use any Python 3.5-only features, as far as you know? Because otherwise, you'll probably find it'll work fine in 3.4...