Update self-venv on rye update

[mitsuhiko]

After update this will attempt to run rye init and the python shim in the context of that project. This under all known Rye versions should trigger a python only sync and updating of the internals.

Fixes #859

[monospacedmagic]

Just to clarify, doesn't rye init initialize a prohect at . if used outside of a project? I feel like that would be unintended behavior when using rye update with the intention to update just rye itself and its venv, no? Am I missing something?

[mitsuhiko]

@monospacedmagic it initializes a project in a temporary folder. This is the most portable way even when downgrading to trigger the update of the venv.

Future versions could gain a specific command to update the internal venv but since this should support downgrades too that’s not too helpful today.

[bluss]

One question I have, is it possible that pip-tools is never updated automatically - it looks that way from a few bugs reported here? It should hopefully be removed by uv soon, but still could be good to know for sure.

[mitsuhiko]

Yeah I think this might have regressed. It used to be that pip-tools was wiped together with the self venv on update:

rye/rye/src/bootstrap.rs

Lines 82 to 86 in f5525c9

	fs::remove_dir_all(&venv_dir).context("could not remove self-venv for update")?;
	if pip_tools_dir.is_dir() {
	fs::remove_dir_all(&pip_tools_dir)
	.context("could not remove pip-tools for update")?;
	}

The current code does not do that:

rye/rye/src/bootstrap.rs

Lines 108 to 109 in 71166f4

	fs::remove_dir_all(&venv_dir)
	.path_context(&venv_dir, "could not remove self-venv for update")?;