We are translating the Python Package Guide into Spanish, and we need new contributors. If you speak Spanish and you are new to open source, this is a great place to start!
What you will be doing
The guide is divided into sections. For each section, the English text is stored in a .po file inside ./locales/es/LC_MESSAGES. Next to each English string, there is a space to write the Spanish translation.
Getting started
Read the Translation Guide first. It explains the workflow and how to set up your local environment.
New to open source? You can also work entirely from the GitHub website. Fork the repository into your account, make your changes on your copy, and open a Pull Request. Two parts of the Translation Guide are worth reading first: Editing the Translation Files, which shows what a .po entry looks like, and the Frequently Asked Questions (FAQ).
If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up.
Pick a file and claim your work
Each file in the table below has its own issue. Click a file name to open it. There, leave a comment claiming a range of lines to work on, so your work does not overlap with anyone else's. Read the existing comments first to see which lines are already taken.
Look at the untranslated column — a file with a smaller number there is an easier place to start.
See an example
Want to see what a translated file looks like? Look at index.po. It holds the strings for the guide's landing page, and it is the file that is furthest along. It is not done yet, so you will still find untranslated and fuzzy strings in it.
Translation status as of 2026-07-09
The table shows the number of strings in each file.
If you come across a string marked fuzzy, it already has a Spanish translation, but that translation needs a second look to confirm it is correct. Usually this is because the English text changed after the string was translated, though a string can be marked fuzzy for other reasons too. Compare the translation against the English text above it. If it still says the right thing, simply remove the line with the fuzzy tag. If it does not, rewrite it and then remove the tag. The Translation Guide explains this further in What happens when a string has changed in the original English text.
We are translating the Python Package Guide into Spanish, and we need new contributors. If you speak Spanish and you are new to open source, this is a great place to start!
What you will be doing
The guide is divided into sections. For each section, the English text is stored in a
.pofile inside./locales/es/LC_MESSAGES. Next to each English string, there is a space to write the Spanish translation.Getting started
Read the Translation Guide first. It explains the workflow and how to set up your local environment.
New to open source? You can also work entirely from the GitHub website. Fork the repository into your account, make your changes on your copy, and open a Pull Request. Two parts of the Translation Guide are worth reading first: Editing the Translation Files, which shows what a
.poentry looks like, and the Frequently Asked Questions (FAQ).If you are working in one of our development sprints at a conference, someone from the pyOpenSci team will be available to help you get set up.
Pick a file and claim your work
Each file in the table below has its own issue. Click a file name to open it. There, leave a comment claiming a range of lines to work on, so your work does not overlap with anyone else's. Read the existing comments first to see which lines are already taken.
Look at the untranslated column — a file with a smaller number there is an easier place to start.
See an example
Want to see what a translated file looks like? Look at
index.po. It holds the strings for the guide's landing page, and it is the file that is furthest along. It is not done yet, so you will still find untranslated and fuzzy strings in it.Translation status as of 2026-07-09
The table shows the number of strings in each file.
If you come across a string marked
fuzzy, it already has a Spanish translation, but that translation needs a second look to confirm it is correct. Usually this is because the English text changed after the string was translated, though a string can be marked fuzzy for other reasons too. Compare the translation against the English text above it. If it still says the right thing, simply remove the line with the fuzzy tag. If it does not, rewrite it and then remove the tag. The Translation Guide explains this further in What happens when a string has changed in the original English text.index.popackage-structure-code.potests.podocumentation.potutorials.poTRANSLATING.pomaintain-automate.poCONTRIBUTING.pocontinuous-integration.po