Prior to #1412 one could use any virtual environment manager (introduced by #863). Now #1412 clamps down on this flexibility. Even if one has a virtualenv with all of algo's dependencies installed (through pipenv / poetry / something else) the ./algo script will fail. I'm unsure if there is a perfect solution, as the use case in #1412 (having a wrong virtualenv activated) is fundamentally at odds with #863 (allowing any virtualenv). I believe the algo maintainers will need to decide what is more important, but I wanted to bring this up as it is a regression that users may run into.
Prior to #1412 one could use any virtual environment manager (introduced by #863). Now #1412 clamps down on this flexibility. Even if one has a virtualenv with all of algo's dependencies installed (through pipenv / poetry / something else) the
./algo
script will fail. I'm unsure if there is a perfect solution, as the use case in #1412 (having a wrong virtualenv activated) is fundamentally at odds with #863 (allowing any virtualenv). I believe the algo maintainers will need to decide what is more important, but I wanted to bring this up as it is a regression that users may run into.To Reproduce
Steps to reproduce the behavior:
Results in:
Expected behavior
Used to work just fine