8000 Deprecate flit publish? · Issue #709 · pypa/flit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Deprecate flit publish? 8000 #709

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.

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

Open
takluyver opened this issue Dec 13, 2024 · 2 comments
Open

Deprecate flit publish? #709

takluyver opened this issue Dec 13, 2024 · 2 comments
Labels

Comments

@takluyver
Copy link
Member

It's increasingly the norm to upload packages from CI rather than a local terminal, and now also encouraged, because attestations are only available for CI uploads. Meanwhile, local uploads are either inconvenient, if you create a token for each project (doubly so if you do this for each release) or pretty poor security, if you create & store a user token which can upload all your projects.

I have asked for a nicer way to upload packages with 2FA (pypi/warehouse#6396 ), but that issue has been open for over 5 years now, and there's no movement. I looked into contributing, but it's part of a bigger thing (pypi/warehouse#13409 ).

This is still up for discussion, but I'm using flit publish less and less because of the above, and I can't get motivated to make improvements to it. So I'm leaning towards deprecating it and eventually removing it. People who want to do local uploads could make the packages and then use twine to upload them.

@Carreau
Copy link
Contributor
Carreau commented Jan 11, 2025

I think this is reasonable. We can have it print please use twine upload; The best code is no code.

@AndydeCleyre
Copy link

I've been replacing my flit publishes with uv publish --trusted-publishing always in CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
0