➜
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.
Created on 2016-01-27 16:10 by Wallison Resende Santos, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg259028 - (view) | Author: Wallison Resende Santos (Wallison Resende Santos) | Date: 2016-01-27 16:10 | |
Please, set the PrependPath configuration to true. It's a good option for console developers on windows. |
|||
| msg259029 - (view) | Author: Bruno Salvino (Bruno Salvino) | Date: 2016-01-27 16:13 | |
Please, set the PrependPath configuration to true. |
|||
| msg259231 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2016-01-30 02:18 | |
Are you are referring to the option in the Windows installer to prepend the currently-being-installed Python directory (and the scripts directory) to the system PATH variable? Is so, making this the default has been proposed and rejected before. Some developers think it a bad idea. In any case, the current choice is not a bug. |
|||
| msg259235 - (view) | Author: Steve Dower (steve.dower) * |
Date: 2016-01-30 03:52 | |
Sorry, not happening. There's a very prominent checkbox on the first page of the installer, which was added under protest. I'd suggest learning the py.exe launcher instead, which does not suffer from any of the issues that are caused by modifying the global PATH variable. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:26 | admin | set | github: 70406 |
| 2016-01-30 03:52:38 | steve.dower | set | status: open -> closed resolution: rejected messages: + msg259235 |
| 2016-01-30 02:18:07 | terry.reedy | set | nosy:
+ terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower messages: + msg259231 components: + Windows type: behavior -> enhancement |
| 2016-01-27 16:13:54 | Bruno Salvino | set | nosy:
+ Bruno Salvino messages: + msg259029 |
| 2016-01-27 16:10:06 | Wallison Resende Santos | create | |