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

[pull] main from astral-sh:main #34

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

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 28, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Feb 28, 2024
soof-golan and others added 30 commits September 2, 2024 21:46
Using `rye toolchain remove` now lists all tools that use a specific
toolchain.

This eliminates the Whac-a-Mole game of reiterating through the `rye
toolchain remove blabla` command in order to actually remove it.

## Example Usage

```bash
$ rye install black --quiet --python 3.11.7
$ rye toolchain remove 3.11.7
error: toolchain [email protected] is still in use by tool black
$ rye install ruff --quiet --python 3.11.7
$ rye toolchain remove 3.11.7
error: toolchain [email protected] is still in use by tools: black, ruff
```

_(Side note: Rust isn't my main d2d language, feel free to comment on
coding style and unidiomatic code)_
Explanations:

* `.*?$` is the same as `.*`: Being lazy at the end is the same as being
greedy.
* `[^\-]` is the same as `[^-]`: The `-` here cannot be considered a
part of a range.
* The dot in `user.(name|email)` acts as a metacharacter.
* `(?:(via)|(?:via (.*?))|(?: (.*?)))$` is equivalent to `(?:via$|via
(.*)| (.*))`.
Consequently, a line below was changed from `.get(2).or_else(||
m.get(3))` to `.get(1).or_else(|| m.get(2))`.
Previously, in *some* situations, `rye pin <pythonversion>; rye list`
could lead to rye deleting the existing virtualenv.

I suggest that `rye list` should be an interrogator and never modify any
project. With this change, it lists its own and non-rye virtualenvs
(same behaviour as uv pip freeze) but should never create, recreate or
overwrite environments (own or non-rye).

Fixes #1352
- Synced latest UV releases

<sup>Auto-generated by
[sync-uv-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-uv-releases.yml)</sup>

Co-authored-by: mitsuhiko <[email protected]>
- Synced latest Python releases

<sup>Auto-generated by
[sync-python-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-python-releases.yml)</sup>

---------

Co-authored-by: mitsuhiko <[email protected]>
Co-authored-by: Charlie Marsh <[email protected]>
- Synced latest UV releases

<sup>Auto-generated by
[sync-uv-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-uv-releases.yml)</sup>

Co-authored-by: mitsuhiko <[email protected]>
- Synced latest UV releases

<sup>Auto-generated by
[sync-uv-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-uv-releases.yml)</sup>

Co-authored-by: mitsuhiko <[email protected]>
## Summary

Regression introduced in #1357.

Closes #1402.

Closes #1398.
This PR edits the copy in `workspaces.md` adding small improvements in
use of prepositions, punctuation, etc.

Addresses #1396
- Synced latest Python releases

<sup>Auto-generated by
[sync-python-releases.yml](https://github.com/astral-sh/rye/blob/main/.github/workflows/sync-python-releases.yml)</sup>

Co-authored-by: mitsuhiko <[email protected]>
Co-authored-by: zanieb <[email protected]>
Resolves: #1426

This pull request includes an update to the compatibility range for the
supported Python versions in the `is_self_compatible_toolchain`
function.

*
[`rye/src/bootstrap.rs`](diffhunk://#diff-5e3b4dd9c9d72709e7551b50ad0bb8933e251e3f7ea71370a13637900c1b349cL285-R287):
Updated the supported Python versions to include cpython 3.13.
Fixes #1436

This seemed like the simplest fix to ignore freethreaded builds.

Couple other thoughts/things that could happen later:

* this won't help with folks who already downloaded a 3.13.0 CPython
(they'll need to `rye toolchain remove [email protected]` first, and then
`fetch` it again)
* `PlatformTriple#flavor` should probably be a `set[str]`; so
`freethreaded+pgo+lto-full` would become `{'freethreaded', 'pgo',
'lto'}` (tbd what to do with `full`)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.