Open Ganonmaster opened 6 years ago
@Ganonmaster there should be an error message somewhere. Its highly unlikely that it fails without an error message. Can you check for an error ?
No error, no production config.
Python 3.6.5, pip 18, pipenv 11.8.3.
Note that in the Bunq app, the API key still shows as "unassigned" as well.
Interesting, ill have a look and will let you know what my findings are.
hmm, i just ran it on macos and it seems to work as expected. 🤔
Can you try to trace the execution of go pro and see if the bash script is actually running like it should.
https://stackoverflow.com/questions/951336/how-to-debug-a-bash-script/
Found some debug output that might indicate where this is going wrong:
+ tinker/create_production_configuration.py --api-key <REMOVED>
/usr/bin/env: ‘.venv/bin/python -W ignore’: No such file or directory
It is making the assumption that my python binary is literally named python
, when it actually is not.
no, the bash script should create a dir ./.venv and in there there should indeed be a executable named python
so it seems that the installation failed.
it seems that
is not executed correctly then 🤔
I think I found the problem. I had setup a custom alias for the default python version on ubuntu (because the default is 2.7)
Edit: no luck it seems. It's still not finding the python binary.
by the look of the screen shot, are you in a virtual env ? might that be it ?
The virtualenv I enter is the one that the setup script creates. Is that not how it's supposed to work? Either way, I just tested without entering the virtualenv, and it makes no difference.
No, at least not for me on macos 🤔
might it have something to do with https://github.com/bunq/tinker_python/issues/3 ?
Environment: Ubuntu 18.04, dependencies up-to-date.