-
Notifications
You must be signed in to change notification settings - Fork 133
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
Feature Request: Support publishing to testPyPI without manual edit to .pypirc file #125
Comments
Thanks I will certainly consider that. I saw this morning that there's a longer term plan to replace TestPyPI with a staged upload mechanism in PyPI. But I think that's some way off, and I hope that TestPyPI stays around as well. |
This is more tractable now that Flit can prompt for a username & password, because it doesn't depend so much on the config file. We could allow passing a URL like |
|
Any update on this? Frankly, I find the |
Follow up from #122
Members of Vancouver PyLadies are interested to learn how to publish a package to PyPI, but they are not package maintainers. I'm thinking to introduce
flit
to our members during an upcoming workshop. I'm thinking that they should publish to testPyPI instead of to the production PyPI.I now know how to publish to testPyPI using flit, but if this can be done without them needing to modify
~/.pypirc
manually, then it would make things simpler.Thanks for the great tool, and I hope you will consider this feature request 🙏 😄
The text was updated successfully, but these errors were encountered: