Rye 0.21.0 cannot locate pip

[raanasn]

Steps to Reproduce

Script:

$ curl -sSf https://rye-up.com/get | RYE_INSTALL_OPTION="--yes" bash
$ . "$HOME/.rye/env"
$ rye sync --no-lock

Expected Result

Downloading [email protected]
Checking checksum
success: Downloaded [email protected]
Initializing new virtualenv in /builds/FOLDERNAME/.venv
Python version: [email protected]
Installing dependencies
Creating virtualenv for pip-tools
Looking in indexes: https://pypi.org/simple/

Actual Result

Downloading [email protected]
Checking checksum
success: Downloaded [email protected]
Reusing already existing virtualenv
Installing dependencies
error: could not locate pip
Caused by:
No such file or directory (os error 2)

Version Info

0.21.0

Stacktrace

No response

[mitsuhiko]

I'm quite confused that it tried to download 3.9. Can you wipe the .rye folder and re-run this? It might be that it picked up an old installation and the upgrade did not function.

[raanasn]

@mitsuhiko I wanted python 3.9 and added this to the pyproject.toml:

requires-python = ">=3.9"

First it installs 3.12.1 like this:

Bootstrapping rye internals
Downloading [email protected]

Then when it comes to $ rye sync --no-lock it installs this:

Downloading [email protected]

But fails because of pip.

[mitsuhiko]

Can you please dump the output of rye --version?

[nrydanov]

Got same error, this error occurs with Rye version 0.20.0 and higher. Currently, we downgraded Rye to 0.19.0, what solved the problem.

[mitsuhiko]

Same question, can you share the output of rye --version? I was not able to repro this on my machine yet and would need the full dump of what the version output generates.

[mitsuhiko]

I believe I have found a case where this can happen. Should be fixed in the next version but it would be great if you could check if this fixes it already.

[raanasn]

@mitsuhiko this did not fix it.

Here is additional Info:

[raanasn]

@mitsuhiko will this be fixed in the next version or should I create a new issue for that?

[eifinger]

I had the same issue and investigated a bit in this draft PR: eifinger/setup-rye#153

1st commit just using rye sync --no-lock failed : link to run

2nd commit updating the lock files with 0.21.0 locally and pushing again failed : link to run

3rd commit running rye sync once before rye sync --no-lock succeeded : link to run

[mitsuhiko]

Please open a new issue if this still reproduces on the latest version.

[raanasn]

@mitsuhiko works perfectly on the latest version! Thanks a lot!

[eifinger]

Also fixed on my end. Thanks!