Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment: > I guess it's reasonable, I'll see whether we can use the workaround you > proposed.
OK, please post your findings here. > (Could a fix on virtualenv's side help?) Probably not, as it's not behaving unexpectedly. It might be worth asking the Travis devs for an enhancement to allow the choice of -m venv rather than virtualenv to create venvs for Python >= 3.3, via an option in .travis.yml. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue30811> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
