Well, the uv 0.3.x release series barely lasted a week – now it’s
on to uv 0.4[1]! We already have uv 0.3.5 in Rawhide/F42, and
0.3.3 in F41 (0.3.5 in updates-testing). This is the notice that I
plan to build 0.4.x in Fedora 42/Rawhide and 41/Branched in a
week, 2024-09-05. This release includes some breaking changes to
default behaviors in uv’s Python project management
functionality[2]. As I understand it, this shouldn’t affect the
“uv pip” or “uv venv” functionality, and I’ll double-check that
the few dependent packages remain compatible.
Since FESCo approved a permanent exception to the Updates Policy
for uv[3], I’ll build 0.4.x for Fedora 40 and 39 at the same time
as 42 and 41. I previously announced uv 0.3.x for F40 and F39, to
be built on 2024-08-30, but since those updates would not reach
stable before being obsoleted by the 0.4.x updates, I’ll just wait
until 2024-09-05 and skip directly to 0.4.x.
-----
Upstream writes:
This release adds first-class support for Python projects that are not designed as Python packages (e.g., web applications, data science projects, etc.).
In doing so, it includes some breaking changes around uv's
handling of projects. Previously, uv required that all projects
could be built into distributable Python packages, and installed
them into the virtual environment. Projects created by uv
init always included a [build-system]
definition and existing projects that did not define a [build-system]
would use the legacy setuptools build backend by default.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/uv/pull-request/10
[2] https://github.com/astral-sh/uv/releases/tag/0.4.0
[3] https://pagure.io/fesco/issue/3262
I’ve been asked[1] to get this update into F41 before the Beta Freeze so that uv 0.3 can appear on the beta ISOs, since uv is now among the packages in the Python Classroom Lab group. Together with the fact that uv has only been in Fedora for a few weeks anyway (and almost nothing relies on it), this seems like an adequate justification for cheating a bit on the Update Policy’s one-week notice period for a technically-breaking update. Unless someone complains, I’ll plan to build this update for F42 and F41 on 2024-08-25 or 2024-08-26 instead of waiting until 2024-08-30. This does not affect F40 and F39, which will still wait for the full week and for a FESCo decision.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2307495#c1
On 8/23/24 8:18 AM, Ben Beasley wrote:
In one week, 2024-08-30, I plan to update the Python package manager uv from 0.2.37 to 0.3.x (currently 0.3.2)[1]:
- in Fedora 42/Rawhide,
- in Fedora 41/Branched (where availability will be delayed by the Beta Freeze),
- and – if approved by FESCo[2] – in Fedora 40 and Fedora 39.
This release brings many new features[3] as well as some small breaking changes[4].
The handful of packages that depend on uv – it is a build dependency for tests in fawltydeps and python-build, and a runtime dependency for hatch – should not experience any disruption.
[1] https://src.fedoraproject.org/rpms/uv/pull-request/6
[2] https://pagure.io/fesco/issue/3262
[3] https://astral.sh/blog/uv-unified-python-packaging
[4] https://github.com/astral-sh/uv/releases/tag/0.3.0
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
