Message316954
| Author | carljm |
|---|---|
| Recipients | barry, brett.cannon, carljm, eric.snow, lukasz.langa, ncoghlan, rhettinger |
| Date | 2018-05-17.16:10:52 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1526573452.52.0.682650639539.issue33499@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Can we have a named -X option that also takes a parameter? I don't see any existing examples of that. This option needs to take the path where bytecode should be written. Are there strong use-cases for having a CLI arg for this? I don't mind doing the implementation work if there are, but right now I'm struggling to think of any case where it would be better to run `python -C /tmp/bytecode` than `PYTHONBYTECODEPATH=/tmp/bytecode python`. Our existing "takes a path" env variables (`PYTHONHOME` and `PYTHONPATH`) do not have CLI equivalents. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-05-17 16:10:52 | carljm | set | recipients: + carljm, barry, brett.cannon, rhettinger, ncoghlan, lukasz.langa, eric.snow |
| 2018-05-17 16:10:52 | carljm | set | messageid: <1526573452.52.0.682650639539.issue33499@psf.upfronthosting.co.za> |
| 2018-05-17 16:10:52 | carljm | link | issue33499 messages |
| 2018-05-17 16:10:52 | carljm | create | |