From a7808368cda447d3ce3e0e6bd41a621faeddf152 Mon Sep 17 00:00:00 2001 From: James Lamb Date: Sat, 12 Jul 2025 17:11:49 -0700 Subject: [PATCH 1/2] docs: clarify PyPI distribution type requirements --- locales/es/LC_MESSAGES/tutorials.po | 5 ++--- locales/ja/LC_MESSAGES/tutorials.po | 5 ++--- tutorials/intro.md | 2 +- 3 files changed, 5 insertions(+), 7 deletions(-) diff --git a/locales/es/LC_MESSAGES/tutorials.po b/locales/es/LC_MESSAGES/tutorials.po index a58ae8753..b9f8d8922 100644 --- a/locales/es/LC_MESSAGES/tutorials.po +++ b/locales/es/LC_MESSAGES/tutorials.po @@ -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 " diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index 8cd0b7e94..f6577ec2d 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -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 " diff --git a/tutorials/intro.md b/tutorials/intro.md index fd62dcaf6..2b1d0087b 100644 --- a/tutorials/intro.md +++ b/tutorials/intro.md @@ -339,7 +339,7 @@ Then you can create a conda-forge recipe using the [Grayskull](https://github.co 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. 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? From 09003f9a5c0d17558393eb950a821ae18a725df2 Mon Sep 17 00:00:00 2001 From: James Lamb Date: Mon, 14 Jul 2025 22:55:24 -0500 Subject: [PATCH 2/2] Apply suggestions from code review --- locales/es/LC_MESSAGES/tutorials.po | 2 +- locales/ja/LC_MESSAGES/tutorials.po | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/locales/es/LC_MESSAGES/tutorials.po b/locales/es/LC_MESSAGES/tutorials.po index b9f8d8922..a5f07ece1 100644 --- a/locales/es/LC_MESSAGES/tutorials.po +++ b/locales/es/LC_MESSAGES/tutorials.po @@ -3291,7 +3291,7 @@ msgstr "" msgid "" "In the image above, you can see the steps associated with publishing 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 " +" 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 " diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index f6577ec2d..801a931da 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -3686,7 +3686,7 @@ msgstr "" msgid "" "In the image above, you can see the steps associated with publishing 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 " +" 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 "