-
Notifications
You must be signed in to change notification settings - Fork 26
pet
reports nested conda
as unique conda
installs
#184
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
Comments
@karthiknadig Not sure what this is trying to solve.
Also, its possible for users to change the This same logic applies to installing miniconda, anaconda, etc all together. Basically I think this tool should return the managers and its upto the user to determine which manager to use and when. |
What logic is it using to determine the priority of the found managers? This logic appears to have changed between Python extension versions, such that in my particular case, it deselects the global one in |
Please can you explain this statement.
@karthiknadig Do you have more context on this issue? |
Not environment - conda executable. When the Python extension runs commands like activation, it needs to invoke a particular This is just one symptom of a broader issue that is linked at the top. |
@gandhis1 thank you for the response, at this stage, I think I need to converse with @karthiknadig to figure out the technical solution. you have been kind to reply, however those are symptoms of the problem, and the fix is slightly different. @karthiknadig I think the problem here is Python extension only supports one Conda exe. |
@DonJayamanne Would it be possible to add the source of detection to the The problem here is, if user does something like install conda into an environment, Do let me know if you have a different idea to solve this scenario, because this is something that I think does not require a |
conda
binaries from base
environment (like /opt/miniconda3/bin/conda)pet
reports nested conda
as unique conda
installs
@gandhis1 If you are still seeing this please can you share the logs
|
@karthiknadig I would like to repro this issue before making any changes. |
In the logs follow Repro steps:
logs :
|
Weird, I cannot repro this at all, with those same steps, |
Logs from the PR, still the same problem:
|
@karthiknadig I think i found the issue, please can you test this again with the latest changes, |
Still happening:
|
Please try again. |
Still the same :(
|
again 🙏🏾 |
This is better but, now it is not detecting named envs: (expected Name field to be set)
logs:
|
Yeah, thats a more challenging issue. lets focus on that after I first get this fixed. |
Originally posted by @gandhis1 in #24627
The text was updated successfully, but these errors were encountered: