Skip to content

Release 0.5.0#8419

Merged
zanieb merged 19 commits intomainfrom
tracking/050
Nov 7, 2024
Merged

Release 0.5.0#8419
zanieb merged 19 commits intomainfrom
tracking/050

Conversation

@zanieb
Copy link
Copy Markdown
Member

@zanieb zanieb commented Oct 21, 2024

@zanieb zanieb added the tracking A "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues. label Oct 21, 2024
@zanieb zanieb added this to the v0.5.0 milestone Oct 21, 2024
@zanieb zanieb temporarily deployed to uv-test-publish October 21, 2024 17:07 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 22, 2024 16:47 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 24, 2024 16:25 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 24, 2024 20:17 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 25, 2024 16:12 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 25, 2024 16:24 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 25, 2024 20:39 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish October 29, 2024 16:26 — with GitHub Actions Inactive
@zanieb zanieb temporarily deployed to uv-test-publish November 4, 2024 13:00 — with GitHub Actions Inactive
zanieb and others added 19 commits November 7, 2024 14:11
closes #6640

Could you suggest how I should test it?

(already tested locally)

---------

Co-authored-by: konstin <konstin@mailbox.org>
Co-authored-by: Charles Tapley Hoyt <cthoyt@gmail.com>
Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
Migrate all directory related logic to `etcetera`, eliminated two
dependecies.
These settings can only be defined in `pyproject.toml`, since they're
project-centric, and not _configuration_.

Closes #8539.

---------

Co-authored-by: Zanie Blue <contact@zanie.dev>
Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
Co-authored-by: konsti <konstin@mailbox.org>
See extensive discussion in
#8433 (comment).

This PR brings us into alignment with the standard library by using
`sys._base_executable` rather than canonicalizing the executable path.

The benefits are primarily for Homebrew, where we'll now resolve to
paths like `/opt/homebrew/opt/python@3.12/bin` instead of the
undesirable
`/opt/homebrew/Cellar/python@3.9/3.9.19_1/Frameworks/Python.framework/Versions/3.9/bin`.

Most other users should see no change, though in some cases, nested
virtual environments now have slightly different behavior -- namely,
they _sometimes_ resolve to the virtual environment Python (at least for
Homebrew; not for rtx or uv Pythons though). See
[here](https://docs.google.com/spreadsheets/d/1Vw5ClYEjgrBJJhQiwa3cCenIA1GbcRyudYN9NwQaEcM/edit?gid=0#gid=0)
for a breakdown.

Closes #1640.
Closes #1795.
Not verifying the certificates of certain hosts should be supported for
all kinds of HTTPS connections, so we're making it a global option, just
like native tls. This fixes the remaining places using a client but were
not configuring allow insecure host.

Fixes #6983 (i think)
Closes #6983

---------

Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>
…6370)

Uses #6369 for test coverage.

Updates version file discovery to search up into parent directories.
Also refactors Python request determination to avoid duplicating the
user request / version file / workspace lookup logic in every command
(this supersedes the work started in
#6372).

There is a bit of remaining work here, mostly around documentation.
There are some edge-cases where we don't use the refactored request
utility, like `uv build` — I'm not sure how I'm going to handle that yet
as it needs a separate root directory.
Implement a full working version of local version semantics. The (AFAIA)
major move towards this was implemented in #2430. This added support
such that the version specifier `torch==2.1.0+cpu` would install
`torch@2.1.0+cpu` and consider `torch@2.1.0+cpu` a valid way to satisfy
the requirement `torch==2.1.0` in further dependency resolution.

In this feature, we more fully support local version semantics. Namely,
we now allow `torch==2.1.0` to install `torch@2.1.0+cpu` regardless of
whether `torch@2.1.0` (no local tag) actually exists.

We do this by adding an internal-only `Max` value to local versions that
compare greater to all other local versions. Then we can translate
`torch==2.1.0` into bounds: greater than 2.1.0 with no local tag and
less than 2.1.0 with the `Max` local tag.

Depends on astral-sh/packse#227.
After #8797, we have spec-compliant
handling for local version identifiers and can completely remove all the
special-casing around it.
We don't actually want users to see this, but we should be stripping it
anyway. Without this change, we show ranges in the debug logs that look
like `>=1.0.0, <1.0.0`, which is more confusing than helpful. (We may
want to post-process those debug ranges to remove these.)
…bers if the version differs (#8897)

We'll read these from the workspace root anyway!
@zanieb zanieb marked this pull request as ready for review November 7, 2024 20:21
@zanieb zanieb temporarily deployed to uv-test-publish November 7, 2024 20:23 — with GitHub Actions Inactive
@zanieb zanieb merged commit daa929a into main Nov 7, 2024
@zanieb zanieb deleted the tracking/050 branch November 7, 2024 20:29
@edmorley
Copy link
Copy Markdown
Contributor

Should the 0.5.0 GitHub milestone be closed out now (also the 0.3.0 milestone) + emptied of non-closed issues/PRs?https://github.com/astral-sh/uv/milestones?state=open

@zanieb
Copy link
Copy Markdown
Member Author

zanieb commented Nov 25, 2024

Thanks for the reminder. I'll do that / migrate the unclosed issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tracking A "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants