-
Notifications
You must be signed in to change notification settings - Fork 61
MSI installer: separate product code for Stackless? #52
Comments
Original comment by Anselm Kruis (Bitbucket: akruis, GitHub: akruis): A possible patch: https://bitbucket.org/akruis/fg2python/commits/0f618c7ea5c72f3ac847b696cace5ace472d7241?at=2.7-slp |
Original comment by RMTEW FULL NAME (Bitbucket: rmtew, GitHub: rmtew): This was done intentionally, because it made things simpler, and the only gain from not doing it was that you couldn't have mainline and stackless python installed at the same time. I think your proposal is fine by me. @krisvale was also suggesting we go this way several weeks ago, IIRC. |
Original comment by Kristján Valur Jónsson (Bitbucket: krisvale, GitHub: kristjanvalur): I don't know much about these things but if they work, that's super. |
Set name to "_curses.window" instead of "_curses.curses window" (with a space!?). (cherry picked from commit 61e2bc7)
Set name to "_curses.window" instead of "_curses.curses window" (with a space!?).
Originally reported by: Anselm Kruis (Bitbucket: akruis, GitHub: akruis)
Previous releases of the Stackless MSI installer used the same product code (an UUID) as the corresponding CPython MSI installer. To my knowledge this makes it impossible/difficult to install CPython and Stackless parallel.
Is there a technical cause for this behaviour? If not, I propose to use different product codes for Stackless.
Probably the simplest way to do so is to increment the last digit of the product code by two. That's the same mechanism, that is already used to get a different product code for the Win64 version. Win64 increases the code by one.
The text was updated successfully, but these errors were encountered: