This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Antony.Lee
Recipients Antony.Lee, vinay.sajip
Date 2017-11-21.19:28:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Travis uses virtualenvs as toplevel containers for running CI.  Some projects need (or would like to) set up venvs as part of their test suites.  On example is, which profiles a project's speed across revisions; in order to do so it sets up an environment for each revision to run the test suite.  Currently, it can either set up a virtualenv or a conda env, but it would make sense for it to be able to set up a venv too (  But the unability to nest a venv into a virtualenv makes this impossible to test on Travis.
Date User Action Args
2017-11-21 19:28:49Antony.Leesetrecipients: + Antony.Lee, vinay.sajip
2017-11-21 19:28:49Antony.Leesetmessageid: <>
2017-11-21 19:28:49Antony.Leelinkissue30811 messages
2017-11-21 19:28:49Antony.Leecreate