[issue39296] Windows register keys

was confused about this behavior. So, again, many thanks for your explanation! Tony Kalf. Van: Steve Dower Verzonden: maandag 13 januari 2020 19:49 Aan: factoryx.c...@gmail.com Onderwerp: [issue39296] Windows register keys Steve Dower added the comment: You should read the version number from

[issue39296] Windows register keys

Steve Dower added the comment: You should read the version number from the Version or SysVersion values, rather than from the tag. Having -32 in the key name is a compatibility requirement. Without it, if you installed 32-bit and 64-bit versions for the current user (which is now the defaul

[issue39296] Windows register keys

Tony added the comment: The attachment I forgot.. Greetings, Tony. Van: Steve Dower Verzonden: zaterdag 11 januari 2020 17:30 Aan: factoryx.c...@gmail.com Onderwerp: [issue39296] Windows register keys Steve Dower added the comment: Have you read PEP 514? Does that help? If not, can you

[issue39296] Windows register keys

-user option: “..\WOW6432Node”. I hope I explained enough about this. Greetings, Tony. Van: Steve Dower Verzonden: zaterdag 11 januari 2020 17:30 Aan: factoryx.c...@gmail.com Onderwerp: [issue39296] Windows register keys Steve Dower added the comment: Have you read PEP 514? Does that help? If

[issue39296] Windows register keys

Steve Dower added the comment: Have you read PEP 514? Does that help? If not, can you provide specific suggestions in terms of that standard to help us understand what you are suggesting? -- ___ Python tracker

[issue39296] Windows register keys

New submission from Tony : It would be more practical to name the Windows main registry keys 'python', with for example 'python32' or 'python64'. This would make searching the registry for registered python versions (single and/or multi users) a lot easier. -- components: Windows mes