Skip to content

No-config debugging: Detected activated environment #699

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.

Sign up for GitHub

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

Jump to bottom
Open
karthiknadig opened this issue Apr 27, 2025 · 0 comments
Open

No-config debugging: Detected activated environment #699

karthiknadig opened this issue Apr 27, 2025 · 0 comments
Assignees
@eleanorjboyd
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@karthiknadig
Copy link
Member

The way PATH is setup, python3 and Python have different values in your environment. That is what is breaking this. We use python3 by default . This seems like something is broken in the way environments activated by conda. Those paths must be same.

@eleanorjboyd i cases where we can detect environment activation we should use python as a mitigation.

Originally posted by @karthiknadig in #638
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eleanorjboyd eleanorjboyd

Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@karthiknadig @eleanorjboyd