Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should uv graduate from 'beta' on PyPI? #8941

Closed
paveldikov opened this issue Nov 8, 2024 · 1 comment · Fixed by #8943
Closed

Should uv graduate from 'beta' on PyPI? #8941

paveldikov opened this issue Nov 8, 2024 · 1 comment · Fixed by #8943
Labels
releases Related to building and distributing release artifacts of uv

Comments

@paveldikov
Copy link
Contributor

The release announcement for 0.5.0 alludes to uv's increasing maturity; maybe the time is now?

Cf. ruff already having been classified as 5 - Production/Stable for quite some time now.

IME it's not a big issue, but it does on occasion raise some eyebrows: 'is it appropriate to cast our lot with a package that is marked as beta?'
@zanieb zanieb mentioned this issue Nov 8, 2024
Merged
@drmikehenry drmikehenry mentioned this issue Nov 8, 2024
Open
11 tasks
@charliermarsh charliermarsh added the releases Related to building and distributing release artifacts of uv label Nov 9, 2024
@charliermarsh
Copy link
Member

Good call -- done in the next release!

konstin pushed a commit that referenced this issue Nov 10, 2024
@zanieb @konstin
Update uv development status classifier to "Stable" on PyPI (#8943)
738f372 
Closes #8941
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
releases Related to building and distributing release artifacts of uv
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update uv development status classifier to "Stable" on PyPI astral-sh/uv
2 participants
@charliermarsh @paveldikov