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

Error on Ubuntu on WSL #3

Closed
IcyPalm opened this issue Mar 21, 2018 · 5 comments
Closed

Error on Ubuntu on WSL #3

IcyPalm opened this issue Mar 21, 2018 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@IcyPalm
Copy link
Contributor

IcyPalm commented Mar 21, 2018

Installed PyEnv to have python 3.6.4

Ran the script from bunq.com/dev

entered the virtualenv with pipenv shell

Tried to run: tinker/user_overview.py
Got the error:

/usr/bin/env: ‘.venv/bin/python -W ignore’: No such file or directory

In the bunq Telegram group another user had the same issue, we have no idea what is wrong

@OGKevin OGKevin self-assigned this Mar 21, 2018
@OGKevin OGKevin added the bug Something isn't working label Mar 21, 2018
@OGKevin OGKevin added this to the 0.9.2 milestone Mar 21, 2018
@OGKevin OGKevin added this to To do in 0.9.3 - Tinker Mar 21, 2018
@IcyPalm
Copy link
Contributor Author

IcyPalm commented Mar 21, 2018

Workaround:
Install virtual env in the directory of tinker:
PIPENV_VENV_IN_PROJECT=1 pipenv install --python 3.6

run
/usr/bin/env .venv/bin/python -W ignore tinker/user_overview.py

When trying to get a production ready key the same issue arrises here:

tinker/create_production_configuration.py --api-key "${apiKey}"

Change that line to
/usr/bin/env .venv/bin/python -W ignore tinker/create_production_configuration.py --api-key "${apiKey}"

@OGKevin
Copy link
Contributor

OGKevin commented Mar 23, 2018

@IcyPalm could you find out what the working dir is for that script once you run tinker/user_overview.py

I have a felling that that might be the difference between Linux and Unix.

@IcyPalm
Copy link
Contributor Author

IcyPalm commented Mar 23, 2018

I have been tinkering around quite a lot. It seems unable to find the python executable with the current shebang header.

Tried this:
#!.venv/bin/python -W ignore

And that works since it directly points to the .venv executable.
Needs the virtual environment to be installed into the project dir though.
PIPENV_VENV_IN_PROJECT=1

@OGKevin
Copy link
Contributor

OGKevin commented Mar 23, 2018

@IcyPalm the header #!.venv/bin/python -W ignore seems to work on Unix as well 🤔 .

Feel free to create a PR! if not we will pick this up soon.

FYI @JordyHeemskerk

@IcyPalm
Copy link
Contributor Author

IcyPalm commented Mar 23, 2018

Woosh ✈️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants