-
Notifications
You must be signed in to change notification settings - Fork 57
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
Python Package Guide: Fix breakout box / admonition that shows a user how to rename their package if the name is taken on pypi #244
Comments
This issue relates to a documentation / tutorial page around what happens if you create a package locally, want to publish it to pypi and then learn AFTER that the name is already taken. it would walk a user through all of the places that they'd want to update things following best practices. this likely looks like
@Tyler-Bonnell if i didn't capture this quite right please let me know! |
For me, the work is captured in the following two commits, with the second being optional but recommended.
More info about my experience under #261, including errors encountered when trying to have hyphens in new name. |
@Tyler-Bonnell @pb-413 submitted a pr that i just merged - the text is here does that fix address your concerns? (you have to open the dropdown on the page - the styles are odd but we can fix that later - that is a sphinx theme issue!. |
I do want to keep this issue open. I think what we want to do is
Once we do that this issue is complete. this is a very beginner friendly task!! |
When setting up the TestPyPi upload for my custom package -- I noticed there was already a package with my name available in TestPyPi and PyPi. The Package Guide (https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html) Step 3. Setup your TestPyPI account states to rename your package (to avoid duplicate names).
I am currently working through the process now, and it is unclear the steps that need to be taken to successfully rename the package?
src/
dist
files after renaming the packageThese were the steps I am considering -- but I am unsure if there are others (what the ideal order of operations would be). It would be great if further documentation could be provided on this.
The text was updated successfully, but these errors were encountered: