You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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?
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
The text was updated successfully, but these errors were encountered: