Skip to content

Commit 48f45bc

Browse files
lwasserkierisi
andauthored
Update package-structure-code/publish-python-package-pypi-conda.md
Co-authored-by: Jesse Mostipak <jesse.maegan@gmail.com>
1 parent 5e8060c commit 48f45bc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

package-structure-code/publish-python-package-pypi-conda.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Below you will learn more specifics about the differences between PyPI and conda
2323

2424
<img src="../images/publish-python-package-pypi-conda.png" alt="Image showing the progression of creating a Python package, building it and then publishing to PyPI and conda-forge. You take your code and turn it into distribution files (sdist and wheel) that PyPI accepts. then there is an arrow towards the PyPI repository where ou publish both distributions. From PyPI if you create a conda-forge recipe you can then publish to conda-forge. " width="700px">
2525

26-
Once you have published both package distributions (the source distribution and the wheel) to PyPI, you can then publish to conda-forge. Conda forge requires an source distribution on PyPI in order to build your package on conda-forge. You do not need to rebuild your package to publish to conda-forge.
26+
Once you have published both package distributions (the source distribution and the wheel) to PyPI, you can then publish to conda-forge. Conda forge requires a source distribution on PyPI in order to build your package on conda-forge. You do not need to rebuild your package to publish to conda-forge.
2727
:::
2828

2929
## What is PyPI

0 commit comments

Comments
 (0)