[issue44575] Windows installer prohibits different patches for the same version

Change by Zachary Ware : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44575] Windows installer prohibits different patches for the same version

Константин Глухов added the comment: After reviewing all the suggested options of the "versioned" Windows install I came to the conclusion that the "NuGet" path is the easiest. Assuming x - version, y - patch number, the following steps work 1. Unzip 'Tools' folder of the NuGet archive into

[issue44575] Windows installer prohibits different patches for the same version

Steve Dower added the comment: Huh, interesting that the email reply is identical to the one above from Константин, but the email I received had no reference to bpo in it... Okay, consider my reply above identical to the one I sent off list :) --

[issue44575] Windows installer prohibits different patches for the same version

Steve Dower added the comment: Some quotes from my reply to an off-list email that may be useful for other people who encounter this issue: --- Apps that use Python-based plugins we can't make Just Work - it's up to the host application to work with Python installs (or to bundle its own,

[issue44575] Windows installer prohibits different patches for the same version

Eric V. Smith added the comment: > As a side note, I think making the install restrictive is more work than just let it install where user wants to install. The restrictions need to be coded - don't they? :) Well at this point, the restrictions already exist! So change it now is the

[issue44575] Windows installer prohibits different patches for the same version

Константин Глухов added the comment: Hi Steve, Thank you for taking time to reply. I do appreciate it. I did try nuget installs but they a little bit weird for my taste. Anaconda is too bloated. I also tried python-webinstall.exe /layout and install from .msi, these work OK for the command

[issue44575] Windows installer prohibits different patches for the same version

Steve Dower added the comment: You found your way to the issue tracker where we can help, which is more enlightened than most of our other ~20 million users :) Nuget allows you to download the packages directly. Go to the page I linked and choose your version, then find the download link.

[issue44575] Windows installer prohibits different patches for the same version

Константин Глухов added the comment: Unfortunately I am not so enlightened to figure out how to do it on my own, and python.org obviously wants to keep it secret. I am also not on a friendly basis with kami-sama and don't know what other users want, but the common sense tells me that having

[issue44575] Windows installer prohibits different patches for the same version

Steve Dower added the comment: > Why does it have to be so complicated? What is the rationale behind > prohibiting different patches in separate folders? Most users don't want different patches in separate folders - they want to update to the latest and greatest and use it everywhere.

[issue44575] Windows installer prohibits different patches for the same version

Константин Глухов added the comment: Why does it have to be so complicated? What is the rationale behind prohibiting different patches in separate folders? -- ___ Python tracker

[issue44575] Windows installer prohibits different patches for the same version

neonene added the comment: To debug pure python, use embeddable pythons in different folders and copy Lib folder from source archive instead of using python3.9.zip. When using msvc (python3*.lib), I think it's enouth to install python as follows or build from source. 1.Copy Installed

[issue44575] Windows installer prohibits different patches for the same version

New submission from Константин Глухов : Windows installer prohibits different patches for the same version. I do not see any reason why the installer cannot put two different versions, e.g. 3.9.4 and 3.9.6 into different folders. This makes it very difficult to debug issues introduced in higher