-
Notifications
You must be signed in to change notification settings - Fork 41
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
How to release a Python package to PyPI #7
Labels
Comments
|
DESCRIPTION.rst 很难设置,会导致上传到pypi失败。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Releasing a Python package to PyPI (Python Package Index) involves several steps. Here's a step-by-step guide to help you publish your Python package:
1. Create Your Python Package:
First, make sure your Python package is properly structured. It should contain the necessary files like
setup.py
(for package metadata), your Python code, and any other required files.2. Prepare Your Package:
setup.py
file in your package directory. Here's an examplesetup.py
file:DESCRIPTION.rst
file in your package directory. Here's an exampleDESCRIPTION.rst
file:See the details: https://github.com/chengjun/iching/blob/master/DESCRIPTION.rst
3. Create an Account on PyPI:
If you haven't already, create an account on PyPI.
4. Install Required Tools:
Make sure you have the necessary tools installed:
5. Build Your Package:
Navigate to your package directory and run the following commands to build your package:
For example:
(base) MacBook-Pro-4:iching datalab$ python setup.py sdist bdist_wheel
This will create distribution packages in the
dist
directory.6. Upload Your Package:
Use
twine
to upload your package to PyPI. Run the following command:twine upload dist/*
(base) MacBook-Pro-4:iching datalab$ twine upload --verbose --repository-url https://upload.pypi.org/legacy/ --username chengjun --password <your_password> dist/*
Please replace <your_password> with your PyPI password.
This command will upload all files in the
dist
directory to PyPI.The text was updated successfully, but these errors were encountered: