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 <rep...@bugs.python.org> <http://bugs.python.org/issue26664> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
