Closed fenekku closed 5 years ago
@fenekku I updated the issue, as I don't believe the step included pipenv install --editable .[all]
at step 1.
I think I figured what happened here though, and this will probably still happen on fresh setups. First, we know 'ipython' is listed in Pipfile, but not 'appnope'. After doing pipenv run pip freeze
I could see 'ipython' installed, but not 'appnope'. So you get the above error. Next I ran a pipenv run pip install ipython
, which will install 'appnope', but not add to Pipfile.lock, and then the pipenv run ./scripts/server
will work.
Anyways, I suspect there is an issue with 'IPython' in the Pipfile.
If you do your installation above and run:
pipenv run ./scripts/run-tests.sh
do all tests pass?
Also if you remove "IPython" from the Pipfile, install the project again pipenv install -e .
and again run pipenv run ./scripts/run-tests.sh
or even pipenv run ./scripts/server.sh
what do you get? (I get some breaking tests)
pipenv run ./run-tests.sh
will pass after pipenv run ./scripts/update
Removing 'IPython' from Pipfile, then pipenv install -e .
will throw errors/fail for pipenv run ./scripts/server
and pipenv run ./run-tests.sh
, mostly complaining about elasticsearch version.
Fixed by #217
Investigate IPython 7.0.0 bug on macOS that prevents project from being run on that platform.
Steps to reproduce: 0- Use macOS 1- PIPENV_VENV_IN_PROJECT=1 pipenv install --dev 2- pipenv run ./scripts/server Expected: 3- server to run without issue Got:
Playing around with the IPython version boundaries might be enough. Ubuntu and other nixes have not experienced this issue (yet?).