Python 3.3

[michaelklishin]

We need to package 3.3 and provision it. In addition, we are blocked on this Virtualenv issue with 3.3.

We now have own PPA and publish 3.3 packages there with the help of the awesome @Mezzle.

[Mezzle]

Python 3.3 RC2 has built correctly.

https://launchpad.net/~travis-ci/+archive/python3.3/+packages

I'd suggest someone try out the package, as I'm not too sure how to test that it works!

[peterjc]

When you say someone needs to try it, would "apt-get install python3.3" in my .travis.yml file get it from here?:
https://launchpad.net/~travis-ci/+archive/python3.3/+packages

Now that Python 3.3 final is out I'd like to test with it under TravisCI :)

[michaelklishin]

@peterjc see the virtualenv issue linked to from this issue and help Virtualenv developers get Virtualenv 3.3-compatible. It currently does not work.

[g2p]

It now works if you use the development version of virtualenv.
See for example: https://github.com/g2p/rfc6266/blob/master/.travis.yml

[ghost]

@michaelklishin: FYI, virtualenv 1.8.2 is now working with Python 3.3.

bmcustodio@bmcustodio:~$ virtualenv --version
1.8.2
bmcustodio@bmcustodio:~$ virtualenv --python=python3.3 .venv-3.3
Running virtualenv with interpreter /usr/bin/python3.3
New python executable in .venv-3.3/bin/python3.3
Also creating executable in .venv-3.3/bin/python
Installing distribute...................................................................................................................................................................................................................................................................................................................................................................................done.
Installing pip................done.
bmcustodio@bmcustodio:~$ source .venv-3.3/bin/activate
(.venv-3.3)bmcustodio@bmcustodio:~$ python
Python 3.3.0 (default, Oct  7 2012, 14:43:21) 
[GCC 4.6.3] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

[g2p]

@bmcustodio, either you have a version of Python that doesn't enable multiarch, which will work, or you have one with multiarch, which will silently fail to install distribute. The patches for both issues are fixed in the development version of virtualenv, but there hasn't been a release yet.

[g2p]

virtualenv 1.8.3 has been released! rejoice!

[michaelklishin]

Provisioning 3.3 locally worked with the exception of NumPy installation but that was expected. We will try to push it live by early next week.

[glyphobet]

I don't think this is fixed yet. Maybe it is not pushed out? Or is there some other magic required to get Python 3.3 working?

Trying to run tests under Python 3.3 fails with the same error as before:

cd ~/builds
git clone --branch=master --depth=100 --quiet git://github.com/glyphobet/pottymouth.git glyphobet/pottymouth
cd glyphobet/pottymouth
git checkout -qf 80529f54ea4f2a2914359745beb8a4eb6d0c8d9c
source ~/virtualenv/python3.3/bin/activate
bash: /home/travis/virtualenv/python3.3/bin/activate: No such file or directory
python --version
Python 2.7.3

see https://travis-ci.org/glyphobet/pottymouth/jobs/3368975 for an example.

In addition, the commit has removed Python 3.1 from ci_environment/python/attributes/default.rb, was that intentional?

[michaelklishin]

Yes, it was intentional. We are replacing 3.1 with 3.3. 3.1 was never documented to be supported, we cannot grow the list of runtimes forever, it is unsustainable.

We are deploying new images tomorrow.

[glyphobet]

Cool, ok, thanks for the quick response. I'm excited to start testing stuff under Python 3.3!

[takluyver]

The virtualenv for Python 3.3 doesn't appear to be working for me, see this log.

-bash: /home/travis/virtualenv/python3.3/bin/activate: No such file or directory

[FiloSottile]

Same here, it does not seem deployed. Any ETA?

[ghost]

bump. Still no joy on 3.3 a month after closing the ticket?

[michaelklishin]

@joshk can you please deploy new ppp images?

[ghost]

thanks. it's live.

[jacobian]

I'm still getting these same errors (i.e. python3.3/bin/activate: No such file or directory) about py3.3. This is on a private job, if that makes a difference; is this perhaps not fixed there?