Skip to content

Update publish-conda-forge.md to fix tiny typo #225

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

Merged
merged 2 commits into from
Apr 9, 2024
Merged

Update publish-conda-forge.md to fix tiny typo #225

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
39d3314
Update publish-conda-forge.md to fix tiny typo
ptressel Apr 8, 2024
e3455a0
Update publish-conda-forge.md for more little typos
ptressel Apr 8, 2024
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
10 changes: 5 additions & 5 deletions tutorials/publish-conda-forge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -377,9 +377,9 @@ Below we break down each element of that list.

The pyOpenSci tutorials are all pure Python and as such do not use static libraries in a linked or shipped (included in the package distribution) format.

If your package has a more complex builds that includes
If your package has a more complex build that includes
links to extensions written in other languages such as
C++, then be sure that include the proper LICENSE(s) for those extensions in your metadata.
C++, then be sure to include the proper licenses for those extensions in your metadata.

:::{note}
If you want to learn more about static libraries, then [this overview](https://pypackaging-native.github.io/background/compilation_concepts/#shared-vs-static-libraries) might help.
Expand Down Expand Up @@ -454,19 +454,19 @@ We cover that next.

Every time you create a new release on PyPI, the conda-forge bots will recognize the release and will rebuild the newly released version of your package. This process may take a day or two to complete so be patient.

Once the conda-forge build it complete, all of the maintainers of your conda-forge feedstock will get a ping on GitHub that a new pull request has been opened.
Once the conda-forge build is complete, all of the maintainers of your conda-forge feedstock will get a ping on GitHub that a new pull request has been opened.

Review the pull request. If all tests are passing, you can merge it. Shortly after merging your pull request, the conda-forge release will be available for users to install:

`conda install -c conda-forge yourpackage`

## <i class="fa-solid fa-hands-bubbles"></i> Wrap up

If you have walked through this entire tutorial series you have now:
If you have walked through this entire tutorial series you will now:

1. Understand [what a Python package is ](intro.md)
2. Know how to [make your code installable](installable-code.md) into Python environments
3. Know how to create a pyproject.toml file, a README file, and a License and code of conduct.
3. Know how to create a `pyproject.toml` file, a `README` file, and a `LICENSE` and code of conduct.
4. Know how to [publish your package to PyPI](publish-pypi.md) and
5. Know how to publish your package to conda-forge

Expand Down