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

pixi exec auto-update #2914

Open
ytausch opened this issue Jan 15, 2025 · 3 comments
Open

pixi exec auto-update #2914

ytausch opened this issue Jan 15, 2025 · 3 comments
Labels
area:exec needs-decision Undecided if this should be done ✨ enhancement Feature request

Comments

@ytausch
Copy link
Contributor

ytausch commented Jan 15, 2025

Problem description

Currently, pixi exec always uses an existent temporary environment if one exists, and only reinstalls it if the --force-reinstall flag is set.

However, as a user, I want to always use the latest compatible version of the packages I've requested with pixi exec and do not really care about existing temporary environments on my machine. If a newer version of a package exists, the environment should be reinstalled. If not, the existing environment can be used.

Is there anything speaking against making this the default behavior?

Cc @pavelzw

@ruben-arts
Copy link
Contributor

@baszalmstra what do you think?

@ruben-arts ruben-arts added ✨ enhancement Feature request area:exec needs-decision Undecided if this should be done labels Jan 17, 2025
@baszalmstra
Copy link
Contributor

The downside is that we'll always have to fetch repodata and perform a solve before we can know whether the version is up to date. It will slow down the case where you run pixi exec often.

But if you find that acceptable Id be fine changing the default.

@pavelzw
Copy link
Contributor

pavelzw commented Jan 17, 2025

especially with sharded repodata this should not be a huge issue, right?
Maybe adding a --no-check-latest mode to skip the check in case you are not connected to the internet? Or let the user configure this behavior in pixi global config with the default being what yannik suggests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:exec needs-decision Undecided if this should be done ✨ enhancement Feature request
Projects
None yet
Development

No branches or pull requests

4 participants