[
https://issues.apache.org/jira/browse/AVRO-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102517#comment-18102517
]
ASF subversion and git services commented on AVRO-4232:
-------------------------------------------------------
Commit d5a84a3789e1c82c9cbe9e80ed8acc51a3eb33ee in avro's branch
refs/heads/branch-1.12 from Ismaël Mejía
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=d5a84a3789 ]
AVRO-4232: [Build] Install uv in the Docker build image (#3925)
The lang/py build.sh now relies on uv, but the Docker test image did not
install it, breaking Python builds/tests in the container.
Install the pinned uv 0.10.4 (matching main branch) into $HOME/.local/bin
and add that directory to PATH alongside cargo.
> [Python] Modernize the Python tooling
> -------------------------------------
>
> Key: AVRO-4232
> URL: https://issues.apache.org/jira/browse/AVRO-4232
> Project: Apache Avro
> Issue Type: Task
> Components: python
> Reporter: Martin Tzvetanov Grigorov
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.2
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> The Python build often fails without any changes in avro/lang/py/ folder!
> If a new version of Python itself or some tool
> (linter/formatter/typechecker/...) is released then the Python build usually
> needs some work to pass again.
> It would be nice to use something more stable/modern to make the build stable
> and reliable. Maybe uv, ruff, ... ?! Anything that won't break unless we
> change something in our code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
