Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PYTHONENVIRONMENTDIR can be set for the wrong version #32

Open
peardox opened this issue Nov 14, 2022 · 2 comments
Open

PYTHONENVIRONMENTDIR can be set for the wrong version #32

peardox opened this issue Nov 14, 2022 · 2 comments
Assignees
Labels
invalid This doesn't seem right

Comments

@peardox
Copy link
Contributor

peardox commented Nov 14, 2022

The IDE plugin sets PYTHONENVIRONMENTDIR but it appears to do so without checking which version of Delphi the user has

This is a problem ONLY if the user has multiple Delphi's installed (I've got four) - actually might be an issue if you downgrade (e.g. remove trial) I guess as well

The HKCU\Software\Embarcadero\BDS registry key can have more than one sub-key (one for each Delphi). The "Environment Variables" of the BDS version that is being used needs the PYTHONENVIRONMENTDIR setting.

I noticed this when I just re-installed P4D-everything in 10.4.2 and 11.2.0 started complaining it couldn't find the zip python payloads

This can be simply resolved by paying attention to the $(ProductVersion) Environment variable when chosing which BDS reg key to alter

@peardox peardox changed the title PYTHONENVIRONMENTDIR can set for the wrong version PYTHONENVIRONMENTDIR can be set for the wrong version Nov 14, 2022
@lmbelo
Copy link
Member

lmbelo commented Nov 28, 2022

Have you tried it at least? We get this info directly from the current Delphi IDE, as follows:

reg add "HKEY_CURRENT_USER\Software\Embarcadero\BDS\%PRODVER%\Environment Variables" /v PYTHONENVIRONMENTDIR /d %PYENVPATH% /f

@lmbelo lmbelo self-assigned this Nov 28, 2022
@lmbelo lmbelo added the invalid This doesn't seem right label Nov 28, 2022
@peardox
Copy link
Contributor Author

peardox commented Nov 28, 2022

I noticed it owing to the value being wrong - it's not fresh in my memory after 14 days so I'd have to reconstruct the problem (takes a while)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants