starteam / starcellbio_html

2 stars 7 forks source link

Installation errors #765

Closed jmclaus closed 7 years ago

jmclaus commented 7 years ago

When installing on two different machines (Linux Mint 18.2 & Ubuntu 15.10), I ran into errors when Ansible tried installing certain dev requirements: ipdb and ipython. This can be fixed by locking down the version of these ie by modifying these entries in requirements.dev.txt as follows:

ipdb==0.10.2
ipython==5.3.0

Below are the errors encountered:

TASK: [Install dev requirements] ********************************************** 
failed: [default] => {"cmd": "/home/vagrant/.virtualenvs/starcellbio/bin/pip install -r /vagrant/requirements.dev.txt", "failed": true}
msg: stdout: Downloading/unpacking pre-commit (from -r /vagrant/requirements.dev.txt (line 1))
Downloading/unpacking flake8 (from -r /vagrant/requirements.dev.txt (line 2))
Downloading/unpacking ipdb (from -r /vagrant/requirements.dev.txt (line 3))
  Downloading ipdb-0.10.3.tar.gz
  Running setup.py (path:/home/vagrant/.virtualenvs/starcellbio/build/ipdb/setup.py) egg_info for package ipdb
    error in ipdb setup command: Invalid environment marker: python_version >= "3.3"
    Complete output from command python setup.py egg_info:
    error in ipdb setup command: Invalid environment marker: python_version >= "3.3"

AND

TASK: [Install dev requirements] ********************************************** 
failed: [default] => {"cmd": "/home/vagrant/.virtualenvs/starcellbio/bin/pip install -r /vagrant/requirements.dev.txt", "failed": true}
msg: stdout: Downloading/unpacking pre-commit (from -r /vagrant/requirements.dev.txt (line 1))
Downloading/unpacking flake8 (from -r /vagrant/requirements.dev.txt (line 2))
Downloading/unpacking ipdb==0.10.2 (from -r /vagrant/requirements.dev.txt (line 3))
  Downloading ipdb-0.10.2.tar.gz
  Running setup.py (path:/home/vagrant/.virtualenvs/starcellbio/build/ipdb/setup.py) egg_info for package ipdb

Downloading/unpacking ipython (from -r /vagrant/requirements.dev.txt (line 4))
  Running setup.py (path:/home/vagrant/.virtualenvs/starcellbio/build/ipython/setup.py) egg_info for package ipython

    IPython 6.0+ does not support Python 2.6, 2.7, 3.0, 3.1, or 3.2.
    When using Python 2.7, please install IPython 5.x LTS Long Term Support version.
    Beginning with IPython 6.0, Python 3.3 and above is required.

    See IPython `README.rst` file for more information:

        https://github.com/ipython/ipython/blob/master/README.rst

    Python sys.version_info(major=2, minor=7, micro=6, releaselevel='final', serial=0) detected.
    Your pip version is out of date, please install pip >= 9.0.1. pip 1.5.4 detected.

    Complete output from command python setup.py egg_info:

IPython 6.0+ does not support Python 2.6, 2.7, 3.0, 3.1, or 3.2.

When using Python 2.7, please install IPython 5.x LTS Long Term Support version.

Beginning with IPython 6.0, Python 3.3 and above is required.

See IPython `README.rst` file for more information:

    https://github.com/ipython/ipython/blob/master/README.rst

Python sys.version_info(major=2, minor=7, micro=6, releaselevel='final', serial=0) detected.

Your pip version is out of date, please install pip >= 9.0.1. pip 1.5.4 detected.
pdpinch commented 7 years ago

Which branch were you trying to install? You probably want to be working with develop

For historical reasons, we don't use master. New work goes into develop and the current production version is in release

FYI @blarghmatey, it looks like these are different requirements issues than the ones you saw yesterday.

jmclaus commented 7 years ago

@pdpinch Indeed, I first built and set up the dev environment after cloning the git repo and using master. I guess this should be mentioned somewhere in the developer guide to avoid future confusions.

In any case, all is fine, I have a functional dev environment and am doing work on branches based off of develop.

Thanks

annagav commented 7 years ago

@jmclaus, which ansible version are you using?

jmclaus commented 7 years ago

@annagav On the Linux Mint machine, version 2.3.1, on the Ubuntu one , version 1.7.2

annagav commented 7 years ago

I ran into same errors, so I am going to open a PR for this.