Message327364
| Author | steve.dower |
|---|---|
| Recipients | eric.snow, mariofutire, ncoghlan, paul.moore, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2018-10-08.16:54:26 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1539017666.48.0.545547206417.issue34725@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Py_SetProgramName() should be a relative or absolute path that can be used to set sys.executable and other values appropriately. Key point here is *can be*, but it doesn't have to be. Given it has fallbacks all the way to "python"/"python3", we can't realistically use it as sys.executable just because it has a value. And right now, it's used to locate the current executable (which is unnecessary on Windows), which is then assumed to be correct for sys.executable. Most embedding cases require *this* assumption to be overridden, not the previous assumption. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-10-08 16:54:26 | steve.dower | set | recipients: + steve.dower, paul.moore, ncoghlan, vstinner, tim.golden, eric.snow, zach.ware, mariofutire |
| 2018-10-08 16:54:26 | steve.dower | set | messageid: <1539017666.48.0.545547206417.issue34725@psf.upfronthosting.co.za> |
| 2018-10-08 16:54:26 | steve.dower | link | issue34725 messages |
| 2018-10-08 16:54:26 | steve.dower | create | |