[issue26664] find a bug in activate.fish of venv of cpython3.6
erdban fed added the comment: This bug shipped in 3.5.2. It should've been a blocker. -- nosy: +erdban fed ___ Python tracker <http://bugs.python.org/issue26664> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26664] Misuse of $ in activate.fish of venv
erdban fed added the comment: > Two, this is not a release blocker. Python itself continues to function > properly with this bug and it doesn't prevent you from working with a venv > under fish (but I recognize it's an annoyance). If you can't load the venv, I think that pretty definitely prevents you from working with one. I'll now have to edit the activation script file manually every time I create a new venv until 3.6 is released. Or revert to 3.5.1. -- ___ Python tracker <http://bugs.python.org/issue26664> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26664] Misuse of $ in activate.fish of venv
erdban fed added the comment: > Activation doesn't "load" the Python interpreter in the venv; all it does is > tweak shell variables to put the interpreter in venv early on PATH. I'm aware. > You have to realize that ... I know it's often a thankless task and that mistakes can and do happen. Not prioritising a two-click fix to a regression that was spotted several months in advance would - in my book - count as such a mistake. Okay, you were preoccupied with other things - that's fine. That's a valid excuse. And if you disagree with the importance of it, that's also fine; I'm not gonna argue my case further. -- ___ Python tracker <http://bugs.python.org/issue26664> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
