Message306786
| Author | vinay.sajip |
|---|---|
| Recipients | Antony.Lee, vinay.sajip |
| Date | 2017-11-23.07:20:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1511421650.8.0.213398074469.issue30811@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-11-23 07:20:50 | vinay.sajip | set | recipients: + vinay.sajip, Antony.Lee |
| 2017-11-23 07:20:50 | vinay.sajip | set | messageid: <1511421650.8.0.213398074469.issue30811@psf.upfronthosting.co.za> |
| 2017-11-23 07:20:50 | vinay.sajip | link | issue30811 messages |
| 2017-11-23 07:20:50 | vinay.sajip | create | |