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
Question about pyenv #1062
Comments
pyenv is the source of too many unwanted issue and I don't think it's gef's job to check if it's running in a venv or not. In addition, none of the
Exactly. As I mentioned in #1048 the correct approach IMO is simply to remove all code related to pyenv detection in gef itself, and instead we can have a standalone script (in @samas69420 If you're willing to do this, such PR would be most welcome - simply because I don't think many of the other devs (include myself) use pyenv for gdb. |
what should the script do besides detecting pyenv? |
Exactly that, but in a separate script: Lines 11396 to 11415 in ece5728
|
And maybe leave an additional global variable or environment variable like |
i can try, but anyway i already made a little edit on the code (still in gef.py tho), now users are forced to explicitly select "system" python version if they're using pyenv and if they don't do it they get a error message, i also moved the gef declaration above so i could use the err function to print the message, if it's ok i can open a PR |
pyenv support has been support with #1084 Closing this issue |
After my last pull request (#1058) I've noticed that the "is_dir()"assertion still fails when using "system" python version in pyenv and when virtual environments managed with pyenv-virtualenv are active, I did fix it but I'm not sure if I should open a new pull request since multiple site-packages directories from different python versions would be allowed to be simultaneously in sys.path and I don't know if this could lead to conflicts, maybe it would be better to just force users to set the global python version to "system" from pyenv and deactivate any virtual environment before running gdb if pyenv is detected
The text was updated successfully, but these errors were encountered: