Skip to content

Add uv project#533

Merged
andersju merged 2 commits intodevelopfrom
feature/lxl-4675-prepare-for-uv
Jul 30, 2025
Merged

Add uv project#533
andersju merged 2 commits intodevelopfrom
feature/lxl-4675-prepare-for-uv

Conversation

@andersju
Copy link
Member

@andersju andersju commented Jul 3, 2025

See https://kbse.atlassian.net/browse/LXL-4675

I removed .python-version from .gitignore because consensus seems to be that it should be checked in, to make sure we're all running the same version. (uv init foo creates both foo/.gitignore and foo/.python-version and doesn't git-ignore the latter.) From one of the main uv authors:

The information [.python-version] captures is materially different than requires-python. requires-python just tells you the range of supported versions; meanwhile, teams use .python-version to dictate the version that should be used during development. That’s useful both for libraries and applications.

It also does not need to be a patch version – you can put 3.12 or similar to ensure that everyone is using Python 3.12, rather than anything later or earlier.

(https://discuss.python.org/t/standardize-python-version-file-in-pyproject-toml/86342/18)

Keeping requirements.txt around for now but at some point (after the next release?) it should be removed.

@andersju andersju requested a review from olovy July 29, 2025 15:45
Copy link
Contributor

@olovy olovy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works!
LGTM.

See comment about version in pyproject.toml

@andersju andersju merged commit dfd697c into develop Jul 30, 2025
@andersju andersju deleted the feature/lxl-4675-prepare-for-uv branch July 30, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants