Message324433
| Author | zach.ware |
|---|---|
| Recipients | cooperlees, vinay.sajip, zach.ware |
| Date | 2018-08-31.15:42:45 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1535730165.88.0.56676864532.issue34556@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This sounds good to me; my `python -m venv venv` commands are also almost always followed up by `venv/bin/python -m pip install -U pip setuptools wheel`. I wouldn't get the `wheel` from this, but it's not always necessary anyway. Rather than importing or forking, I would expect this could just be done by invoking the venv's pip as a subprocess. Also, it would need to be a different flag than `--upgrade`, which already exists. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-08-31 15:42:45 | zach.ware | set | recipients: + zach.ware, vinay.sajip, cooperlees |
| 2018-08-31 15:42:45 | zach.ware | set | messageid: <1535730165.88.0.56676864532.issue34556@psf.upfronthosting.co.za> |
| 2018-08-31 15:42:45 | zach.ware | link | issue34556 messages |
| 2018-08-31 15:42:45 | zach.ware | create | |