Skip to content

Always pass python version when creating mamba/conda env #1495

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jder
Copy link

@jder jder commented May 12, 2025

When we have no environment file, we weren't passing a python version constraint after #1444. We now create one if the user did not specify an environment file.

Fixes #1486.

@@ -36,7 +36,7 @@
from asv.plugins.conda import _find_conda

# Two Python versions for testing
PYTHON_VER1, PYTHON_VER2 = '3.8', platform.python_version()
PYTHON_VER1, PYTHON_VER2 = '3.8', ".".join(platform.python_version_tuple()[:2])
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is somewhat unrelated but I couldn't make tests pass locally with the previous code, since my local version (3.12.10) was not resolvable by mamba. Seems like this makes more sense anyway? Happy to revert or break out if you prefer.

@mattip
Copy link
Contributor

mattip commented May 20, 2025

This now has conflicts

@jder jder force-pushed the always-pass-python-version branch from 0d44656 to 1ce4c24 Compare May 20, 2025 17:32
@jder
Copy link
Author

jder commented May 20, 2025

@mattip rebased, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Python version no longer respected in main
2 participants