[Python-Dev] Python environment registration in the Windows Registry
Matthew Einhorn
moiein2000 at gmail.com
Wed Feb 3 14:32:18 EST 2016
More information about the Python-Dev mailing list
Wed Feb 3 14:32:18 EST 2016
- Previous message (by thread): [Python-Dev] Python environment registration in the Windows Registry
- Next message (by thread): [Python-Dev] Python environment registration in the Windows Registry
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Feb 3, 2016 at 3:15 AM, Alexander Walters <tritium-list at sdamon.com> wrote: > ...just when I thought I have solved the registry headaches I have been > dealing with... > > I am not saying this proposal will make the registry situation worse, but > it may break my solution to the headaches Python's registry use causes with > some non-standard module installers (and even the standard distutils exe > installers, but that is being mitigated). In the wild exist modules with > their own EXE or MSI installers that check the registry for 'the system > python'. No matter how hard you hit them, they will only install to *that > one python*. If I remember correctly, you can use `wheel convert filename.exe` on those installers which create a wheel that you can install. I think that's what I used to do with pywin32 before pypiwin32 came along. I just tested it and it still works on the pywin32 exe. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160203/cb300d74/attachment.html>
- Previous message (by thread): [Python-Dev] Python environment registration in the Windows Registry
- Next message (by thread): [Python-Dev] Python environment registration in the Windows Registry
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list