forked from astral-sh/rye
-
Notifications
You must be signed in to change notification settings - Fork 0
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
pull
wants to merge
211
commits into
psy-repos-rust:main
Choose a base branch
from
astral-sh:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: mitsuhiko <[email protected]>
Co-authored-by: mitsuhiko <[email protected]>
* Ignore .rye folder added by github action * Update pyproject.toml
Co-authored-by: mitsuhiko <[email protected]>
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]>
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`)
## Summary The `macos-12` runners are deprecated: https://github.com/astral-sh/rye/actions/runs/12244443745
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )