Skip to content

docs: clarify PyPI distribution type requirements #552

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify PyPI distribution type requirements #552

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions locales/es/LC_MESSAGES/tutorials.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3290,9 +3290,8 @@ msgstr ""
#: ../../tutorials/intro.md:341
msgid ""
"In the image above, you can see the steps associated with publishing your"
" package on PyPI and conda-forge. Note that the distribution files that "
"PyPI requires are the [sdist](#python-source-distribution) and [wheel"
"](#python-wheel) files. Once you are ready to make your code publicly "
" package on PyPI and conda-forge. PyPI supports [sdist](#python-source-distribution)"
and [wheel](#python-wheel) files. Once you are ready to make your code publicly "
"installable, you can publish it on PyPI. Once your code is on PyPI it is "
"straight forward to then publish to conda-forge. You create a recipe "
"using the Grayskull package and then you open a pr in the conda-forge "
Expand Down
5 changes: 2 additions & 3 deletions locales/ja/LC_MESSAGES/tutorials.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3685,9 +3685,8 @@ msgstr ""
#: ../../tutorials/intro.md:341
msgid ""
"In the image above, you can see the steps associated with publishing your"
" package on PyPI and conda-forge. Note that the distribution files that "
"PyPI requires are the [sdist](#python-source-distribution) and [wheel"
"](#python-wheel) files. Once you are ready to make your code publicly "
" package on PyPI and conda-forge. PyPI supports [sdist](#python-source-distribution)"
and [wheel](#python-wheel) files. Once you are ready to make your code publicly "
"installable, you can publish it on PyPI. Once your code is on PyPI it is "
"straight forward to then publish to conda-forge. You create a recipe "
"using the Grayskull package and then you open a pr in the conda-forge "
Expand Down
2 changes: 1 addition & 1 deletion tutorials/intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@ Then you can create a conda-forge recipe using the [Grayskull](https://github.co
<img src="../images/tutorials/publish-package-pypi-conda.png" alt="Graphic showing the high level packaging workflow. On the left you see a graphic with code, metadata and tests in it. Those items all go into your package. Documentation and data are below that box because they aren't normally published in your packaging wheel distribution. An arrow to the right takes you to a build distribution files box. That box leads you to either publishing to TestPyPI or the real PyPI. From PyPI you can then connect to conda-forge for an automated build that sends distributions from PyPI to conda-forge." width="700px">

In the image above, you can see the steps associated with publishing
your package on PyPI and conda-forge. Note that the distribution files that PyPI requires are the [sdist](#python-source-distribution) and [wheel](#python-wheel) files. Once you are ready to make your code publicly installable, you can publish it on PyPI. Once your code is on PyPI it is straight forward to then publish to conda-forge. You create a recipe using the Grayskull package and then you open a pr in the conda-forge recipe repository. You will learn more about this process in the [conda-forge lesson](/tutorials/publish-conda-forge).
your package on PyPI and conda-forge. PyPI supports [sdist](#python-source-distribution) and [wheel](#python-wheel) files. Once you are ready to make your code publicly installable, you can publish it on PyPI. Once your code is on PyPI it is straight forward to then publish to conda-forge. You create a recipe using the Grayskull package and then you open a pr in the conda-forge recipe repository. You will learn more about this process in the [conda-forge lesson](/tutorials/publish-conda-forge).
:::

## Yay, your package has users! Now what?
Expand Down
Loading