-
Notifications
You must be signed in to change notification settings - Fork 9
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
glibc version problem with virtualenv #13
Comments
No. Any virtual env just must be made in the sandbox not outside. |
So then it is needed to always create a virtualenv on the base of the python version of the related flatpak platform version? |
Create it from within flatpak, either some graphical tool provided by Pycharm or from the cli: |
I ran into this same problem. Using @TingPing's command above I was able to get a shell in the Flatpak, however virtualenv isn't installed in it so I had to do the following (inside the Flatpak shell):
From there I was able to add the virtualenv to my PyCharm settings for my project |
BTW, this is needed because /usr/bin/python that PyCharm can see inside the Flatpak environment is different from /usr/bin/python on your host, and it's built against a different version of glibc. A virtualenv created using the host's python won't necessarily be usable using the Flatpak's python. I think that if the Flatpak were to include the virtualenv executable that PyCharm would be able to create a new virtualenv without problem. I've created issue #29 to do this. |
@mhall119 Verified that it creates virtualenvs correctly now. Can we close the issue? |
I haven't actually verified this yet. I didn't rebuild the flatpak, but I'm assuming it will. |
You can use |
I think all library-loading errors (i.e. "library not found") should be consolidated under #14. |
When I use the snap version (2017.3.3 on Ubuntu 17.10) adding a existing virtualenv works flawlessly.
But not for the flatpak version (2017.3).
There the following dialog pops up:
In the log file:
The python 3.6.3 env is derived from the ubuntu system install.
Seems that python needs access to the systems glibc.
Could this be accomplished?
The text was updated successfully, but these errors were encountered: