Hello all, I’ve been bit by creating virtualenvs against a homebrew-installed systemwide Python, upgrading the system Python, running "brew cleanup” which deletes the previous Python that the virtualenv was created against. Is there a way to get virtualenvs to “see” the new Python? Or should I just stop with the “brew cleanup” after brew upgrading the system Python?
I figure this is a common enough scenario that there has to be a good answer/best practice/light to dim the darkness of my ignorance. Thanks, John _______________________________________________ Portland mailing list [email protected] https://mail.python.org/mailman/listinfo/portland
