New release: Jython 2.7.0

[toolforger]

Please add to the list of installable Python interpreters :-) Thanks!

[toolforger]

This seems to be somewhat difficult - I'm getting errors:

(python2.6.9)jo@jodel:~/Projekte/sympy-workspace$ virtualenv -p $(pythonz locate -t jython 2.7.0) jython-2.7.0
Running virtualenv with interpreter /home/jo/.pythonz/pythons/Jython-2.7.0/bin/python
Cannot find file /home/jo/.pythonz/pythons/Jython-2.7.0/Include (bad symlink)
New jython executable in jython-2.7.0/bin/jython
Installing setuptools, pip...
  Complete output from command /home/jo/Projekte/sy...hon-2.7.0/bin/jython -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip:
  Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named pip
----------------------------------------
...Installing setuptools, pip...done.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 2378, in <module>
    main()
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 821, in main
    create_environment(home_dir,
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 1032, in create_environment
    install_wheel(to_install, py_executable, search_dirs)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 969, in install_wheel
    call_subprocess(cmd, show_stdout=False,
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 915, in call_subprocess
    raise OSError(
OSError: Command /home/jo/Projekte/sy...hon-2.7.0/bin/jython -c "import sys, pip; sys...d\"] + sys.argv[1:]))" setuptools pip failed with error code 1

[saghul]

Added support for it in master, thanks for the heads up! The problem you get seems to be something about pip, here is a workaround: https://gist.github.com/skyl/ea2ab1c62a547e381411

[toolforger]

Thanks for the pointer to the workaround. Seems like my Ubuntu install of pip isn't compatible with all versions of Python anymore (if it ever was). I'm starting to wonder whether pythonz shouldn't install its own version of pip and virtualenv/pyvenv etc. Oh right... actually there is an incompatibility with virtualenv already, your instructions say mkvirtualenv and I need to use virtualenv (maybe the Ubuntu guys renamed the script, dunno what's up with that). I guess that's serious work; should I open a new issue for that? Or is it a bad idea anyway?

[saghul]

I'm starting to wonder whether pythonz shouldn't install its own version of pip and virtualenv/pyvenv etc.

I created pythonz as a fork of pythobbrew with 2 ideas: make is simpler/smaller, and add support for pythons other than CPython. This would break my first rule, which was to keep managing virtualenvs up to the user, since everyone has its own preferences.

Oh right... actually there is an incompatibility with virtualenv already, your instructions say mkvirtualenv and I need to use virtualenv (maybe the Ubuntu guys renamed the script, dunno what's up with that).

mkvirtualenv is part of virtualenvwrapper, you'll need to install that one.

I guess that's serious work; should I open a new issue for that? Or is it a bad idea anyway?

As I mentioned, that's not something I want for pythonz, sorry. One thing you can probably do is create a virtualenv with your system Python, update pip inside it, and use that one to install stuff with pythonz. I haven't tried it myself, but that might do it.

[toolforger]

As I mentioned, that's not something I want for pythonz, sorry.

No sweat. pythonz is an immense help even if it isn't doing 100% of my own use case. I'll just wait until somebody builds on top of pythonz, as you built on top of pythonbrew. It's all open source after all :-)

[toolforger]

Hmm... seems the workaround doesn't work actually, and the jpythontools stuff is beyond my current understanding (lack of time to learn it all, unfortunately). I guess I'll give up for now.