Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Publish this tool on PyPI
See original GitHub issueIssue Analytics
- State:
- Created 5 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
How to Publish an Open-Source Python Package to PyPI
In this tutorial, you'll learn how to upload your own package to PyPI. Publishing your project is easier than it used to be....
Read more >How to publish a Python Package to PyPi | by Aveek Das
In this article, let us understand how to develop a python package and then publish it to PyPi for distribution. This is a...
Read more >How to Publish Python Package on PyPI - Geeky Humans
In this tutorial, we are going to introduce a step-by-step guide to help you on how to publish Python package on PyPi so...
Read more >publish - PyPI
publish is a tool to package and release a python project. It will create a changelog and upload artifacts to Github and PyPI....
Read more >PyPi - How to Publish your own PIP package - YouTube
In this video, I go over how you can publish a package to Pypi. This will allow anyone in the world you do...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
However, it looks like
pip install saberhas already been snagged…Update: I’ve dealt with packages whose names on pip and the thing they install are not the same. I would strongly recommend against doing that. It’s a huge problem for users.
That doesn’t mean that the project name has to be changed nor the repository name on GitHub (in fact, I think your acronym is very cool). What I might suggest is changing the folder in the repository where all the code lives to something else like
saber_nerand also change the name insetup.pyto match. Of course a new name would be up to you.That’s a cool solution. For the time being, it’s probably okay to just remove these requirements from the pip installation and make sure that there is adequate user documentation on how to install these last two packages in the README (which goes to PyPI too)