Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pollution by Python3 prevents EasyBuild from working smoothly #1532

Closed
citibeth opened this issue Jan 3, 2016 · 4 comments
Closed

Pollution by Python3 prevents EasyBuild from working smoothly #1532

citibeth opened this issue Jan 3, 2016 · 4 comments
Milestone

Comments

@citibeth
Copy link

citibeth commented Jan 3, 2016

The problem comes when the system default "python" is python3, not python2. This causes problems at many stages:

  1. The call to
    python bootstrap_eb.py
    doesn't work because the script calls a hardcoded "python" inside. This can be fixed, see: http://stackoverflow.com/questions/2589711/find-full-path-of-python-interpreter
  2. Once things get installed, "module EasyBuild" doesn't work. Again, it gets confused by the system default python, rather than the one we originally launched with.
  3. The eb command doesn't work either. Same reason . I jury-rigged the following script, which is obviously not portable:
    export PYTHONUSERBASE=$EB_ROOT/software/EasyBuild/2.5.0
    $EB_ROOT/bin/python -m easybuild.main --robot=/Users/rpfische/eb/easyconfigs "$@

SUGGESTED TESTING APPROACH:

  1. Install Python3 on your system and configure paths so "python" defaults to "python3."
    (Alternately: just hack your system so the "python" command does something non-funtional).
  2. Follow the docs to install EasyBuild, starting with "python2.7 bootstrap_eb.py"
    1. Fix any fireworks that follow
@boegel
Copy link
Member

boegel commented Jan 17, 2016

@citibeth: a couple of problems related to having Python 3 as the default Python were handled in #1411, but apparently we didn't get the full picture here.

I'll try and look into playing around with it on a system where Python 3 is the default (e.g. Arch Linux), and see what problems are left unhandled.

This is very much related to #1410 btw.

@citibeth
Copy link
Author

Even without finding an Arch Linux, you can probably catch most of the
problems with something like the following BASH environment:

mkdir ~/python3_prototype
echo 'exit -1' >~/python3_prootype/python
chmod a+x ~/python3_prootype/python
export PATH=~/python3_prototype:$PATH

On Sun, Jan 17, 2016 at 9:30 AM, Kenneth Hoste notifications@github.com
wrote:

@citibeth https://github.com/citibeth: a couple of problems related to
having Python 3 as the default Python were handled in #1411
#1411, but
apparently we didn't get the full picture here.

I'll try and look into playing around with it on a system where Python 3
is the default (e.g. Arch Linux), and see what problems are left unhandled.

This is very much related to #1410
#1410 btw.


Reply to this email directly or view it on GitHub
#1532 (comment)
.

@boegel boegel modified the milestone: v2.x Jan 23, 2016
@boegel
Copy link
Member

boegel commented Mar 30, 2016

@citibeth This should be fixed with EasyBuild v2.7.0, please verify?

@boegel
Copy link
Member

boegel commented Aug 10, 2016

Closing this, cfr. #1410

@boegel boegel closed this as completed Aug 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants