From 0fc8faf523ccdbbf18c2bf0dc211c79f1cd220df Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Mon, 26 Aug 2024 09:24:28 -0700 Subject: [PATCH 1/5] add initial draft of action before updating models and inevitable refinement to exclude diffs on timestamps --- .github/workflows/build-book.yml | 12 +--------- .github/workflows/i18n.yaml | 39 ++++++++++++++++++++++++++++++++ 2 files changed, 40 insertions(+), 11 deletions(-) create mode 100644 .github/workflows/i18n.yaml diff --git a/.github/workflows/build-book.yml b/.github/workflows/build-book.yml index e978b3c8..6c37c6d1 100644 --- a/.github/workflows/build-book.yml +++ b/.github/workflows/build-book.yml @@ -21,22 +21,12 @@ jobs: uses: actions/setup-python@v5 with: python-version: "3.9" + cache: pip - name: Upgrade pip run: | # install pip=>20.1 to use "pip cache dir" python3 -m pip install --upgrade pip - - name: Get pip cache dir - id: pip-cache - run: echo "::set-output name=dir::$(pip cache dir)" - - - name: Cache dependencies - uses: actions/cache@v4 - with: - path: ${{ steps.pip-cache.outputs.dir }} - key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }} - restore-keys: | - ${{ runner.os }}-pip- - name: Install dependencies run: python3 -m pip install nox diff --git a/.github/workflows/i18n.yaml b/.github/workflows/i18n.yaml new file mode 100644 index 00000000..9b3e1844 --- /dev/null +++ b/.github/workflows/i18n.yaml @@ -0,0 +1,39 @@ +name: Check Internationalization +# Ensure that the .po files are up to date with any changes to the guide text + +on: + pull_request: + push: + branches: + - main + +jobs: + update-i18n: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Setup Python + uses: actions/setup-python@v5 + with: + python-version: "3.12" + cache: pip + + - name: Install Nox + run: python3 -m pip install nox + + - name: Update .po files + run: nox -s update-translations + + - name: Test for uncommitted changes + run: | + if [ -z "$(git status --porcelain)" ]; + then + echo "No changes detected" + exit 0 + else + echo "Changes to models detected" + echo "$(git status)" + echo "$(git diff)" + exit 1 + fi From 0463f0066e3e3ed506225356ec20c409ba5938f0 Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Mon, 26 Aug 2024 09:27:15 -0700 Subject: [PATCH 2/5] update .po files --- locales/es/LC_MESSAGES/CONTRIBUTING.po | 567 +++++++++-- locales/es/LC_MESSAGES/TRANSLATING.po | 44 +- locales/es/LC_MESSAGES/documentation.po | 204 ++-- locales/es/LC_MESSAGES/index.po | 145 +-- .../es/LC_MESSAGES/package-structure-code.po | 910 +++++++++++------- locales/es/LC_MESSAGES/tests.po | 20 +- locales/es/LC_MESSAGES/tutorials.po | 548 +++++++++-- locales/ja/LC_MESSAGES/CONTRIBUTING.po | 553 +++++++++-- locales/ja/LC_MESSAGES/TRANSLATING.po | 44 +- locales/ja/LC_MESSAGES/documentation.po | 77 +- locales/ja/LC_MESSAGES/index.po | 65 +- .../ja/LC_MESSAGES/package-structure-code.po | 302 +++++- locales/ja/LC_MESSAGES/tests.po | 60 +- locales/ja/LC_MESSAGES/tutorials.po | 194 +++- 14 files changed, 2852 insertions(+), 881 deletions(-) diff --git a/locales/es/LC_MESSAGES/CONTRIBUTING.po b/locales/es/LC_MESSAGES/CONTRIBUTING.po index b2a801f4..5bd8a3bb 100644 --- a/locales/es/LC_MESSAGES/CONTRIBUTING.po +++ b/locales/es/LC_MESSAGES/CONTRIBUTING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-03 16:27-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../CONTRIBUTING.md:4 msgid "Contributing to the Python Packaging Guide" @@ -119,182 +119,481 @@ msgstr "" #: ../../CONTRIBUTING.md:35 msgid "" "Independently of the approach you choose, the first step is to fork the " -"Python Packaging Guide repository into your personal GitHub space." +"Python Packaging Guide repository into your personal GitHub space. You " +"can do this by clicking the \"Fork\" button in the top right corner of " +"the repository page." msgstr "" -#: ../../CONTRIBUTING.md:37 +#: ../../CONTRIBUTING.md:38 msgid "" -"*__TODO__: This section should show a beginner user how to fork a " -"repository in GitHub.*" +"[Learn more: Fork and Clone GitHub " +"Repos](https://datascienceskills.org/lessons/git-github/git-intro/3-fork-" +"clone/) is a good resource to learn more about forking." msgstr "" -#: ../../CONTRIBUTING.md:39 +#: ../../CONTRIBUTING.md:40 +msgid "To fork a repo," +msgstr "" + +#: ../../CONTRIBUTING.md:42 +msgid "Make sure you are logged into GitHub." +msgstr "" + +#: ../../CONTRIBUTING.md:44 +msgid "" +"Go to the repo you would like to fork, in this case the [Python Packaging" +" Guide](https://www.github.com/pyopensci/python-package-guide) repo." +msgstr "" + +#: ../../CONTRIBUTING.md:46 +msgid "" +"In the top right-hand corner of the page there is a 'Fork' button. Click " +"that button. You will be brought to a new page where you will 'Create a " +"new fork'. Feel free to keep all the default inputs and click 'Create " +"fork'. This will create a copy of the repo at " +"`https://github.com//python-package-guide`, where `` " +"is your GitHub username." +msgstr "" + +#: ../../CONTRIBUTING.md:51 msgid "Contributing via the GitHub website" msgstr "" -#: ../../CONTRIBUTING.md:41 +#: ../../CONTRIBUTING.md:53 msgid "How to edit a MarkDown file" msgstr "" -#: ../../CONTRIBUTING.md:43 +#: ../../CONTRIBUTING.md:55 +msgid "" +"The Python Packaging Guide is written in myST, a variant of MarkDown. You" +" can edit the files directly in the GitHub website. To do so, navigate to" +" the file you want to edit and click the pencil icon in the top right " +"corner of the file." +msgstr "" + +#: ../../CONTRIBUTING.md:58 +msgid "Edit button in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:64 +msgid "" +"An image showing how to edit a file in GitHub. The pencil icon is " +"highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:66 +msgid "Edit file in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:72 msgid "" -"*__TODO__: This section should show how to use the GitHub interface to " -"edit and previewing a Markdown file.*" +"An image showing when a file is being edited in GitHub. The file content " +"is displayed in a text editor." +msgstr "" + +#: ../../CONTRIBUTING.md:75 +msgid "To preview your changes, click the \"Preview changes\" tab." msgstr "" -#: ../../CONTRIBUTING.md:45 +#: ../../CONTRIBUTING.md:77 +msgid "Preview changes in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:83 +msgid "" +"An image showing how to preview changes in GitHub. The file content is " +"displayed in a text editor. The preview changes tab is highlighted with a" +" red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:86 msgid "How to commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:47 +#: ../../CONTRIBUTING.md:88 +msgid "" +"When you are done editing the file, scroll down to the bottom of the " +"page. You will see a section called \"Commit changes\". Here you can " +"write a title and a description for your changes. Make sure to write a " +"clear and concise title that describes the changes you made." +msgstr "" + +#: ../../CONTRIBUTING.md:91 +msgid "Commit changes in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:97 +msgid "" +"An image showing how to commit changes in GitHub. The commit message is " +"displayed in a text editor. The commit changes section is highlighted " +"with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:100 msgid "" -"*__TODO__: This section should show how to commit changes via the GitHub " -"interface.*" +"After writing your commit message, click the \"Commit changes\" button to" +" save your changes." msgstr "" -#: ../../CONTRIBUTING.md:49 +#: ../../CONTRIBUTING.md:102 msgid "Contributing locally on your computer" msgstr "" -#: ../../CONTRIBUTING.md:51 +#: ../../CONTRIBUTING.md:104 msgid "Clone your forked repository" msgstr "" -#: ../../CONTRIBUTING.md:53 +#: ../../CONTRIBUTING.md:106 msgid "" -"*__TODO__: This section should show how to clone a repository from GitHub" -" into your computer.*" +"To clone your forked repository to your computer, you need to copy the " +"URL of your forked repository and run the following command in your " +"terminal:" msgstr "" -#: ../../CONTRIBUTING.md:55 +#: ../../CONTRIBUTING.md:111 +msgid "" +"Replace `` with the URL of your forked repository. You can find the " +"URL by clicking the green \"Code\" button on your forked repository page." +msgstr "" + +#: ../../CONTRIBUTING.md:113 +msgid "Clone repository in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:119 +msgid "" +"An image showing how to clone a repository in GitHub. The URL of the " +"repository is displayed in a text editor. The code button is highlighted " +"with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:122 msgid "Create a new branch" msgstr "" -#: ../../CONTRIBUTING.md:57 -msgid "*__TODO__: This section should show how to create a new branch.*" +#: ../../CONTRIBUTING.md:124 +msgid "" +"Before making any changes, you should create a new branch to work on. " +"This will help keep your changes separate from the main branch and make " +"it easier to submit a pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:126 +msgid "To create a new branch, run the following command in your terminal:" msgstr "" -#: ../../CONTRIBUTING.md:59 +#: ../../CONTRIBUTING.md:132 msgid "Create a virtual environment" msgstr "" -#: ../../CONTRIBUTING.md:61 +#: ../../CONTRIBUTING.md:134 msgid "" -"*__TODO__: This section should show how to create a virtual environment " -"using venv.*" +"To build the guide locally, you need to create a virtual environment and " +"install the dependencies. You can do this by running the following " +"commands in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:136 +msgid "**On Windows**:" +msgstr "" + +#: ../../CONTRIBUTING.md:142 +msgid "**On MacOS and Linux**:" msgstr "" -#: ../../CONTRIBUTING.md:63 +#: ../../CONTRIBUTING.md:148 msgid "Install the development dependencies" msgstr "" -#: ../../CONTRIBUTING.md:65 +#: ../../CONTRIBUTING.md:150 msgid "" -"*__TODO__: This section should show how to install the development " -"dependencies defined in pyproject.toml.*" +"To install the development dependencies, run the following command in " +"your terminal:" msgstr "" -#: ../../CONTRIBUTING.md:67 +#: ../../CONTRIBUTING.md:156 msgid "Commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:69 +#: ../../CONTRIBUTING.md:158 +msgid "" +"After making your changes, you need to commit them to your local " +"repository. To do this, run the following commands in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:160 +msgid "To see the changes you made:" +msgstr "" + +#: ../../CONTRIBUTING.md:164 +msgid "To add the changes to the staging area:" +msgstr "" + +#: ../../CONTRIBUTING.md:168 +msgid "To commit the changes:" +msgstr "" + +#: ../../CONTRIBUTING.md:172 msgid "" -"*__TODO__: This section should describe how to commit from the command " -"line.*" +"Replace `\"Your commit message here\"` with a clear and concise message " +"that describes the changes you made." msgstr "" -#: ../../CONTRIBUTING.md:71 +#: ../../CONTRIBUTING.md:174 msgid "How to build the guide locally" msgstr "" -#: ../../CONTRIBUTING.md:73 +#: ../../CONTRIBUTING.md:176 msgid "" -"*__TODO__: This section should describe the different sessions in nox " -"related to building the docs: docs, docs-test, docs-live. It should also " -"show how to see the guide built locally, by opening the right file in the" -" browser or using the live version from docs-live*" +"To build the guide locally, you can use the `nox` command. This will run " +"the default `nox` session, which builds the guide and opens it in your " +"browser." msgstr "" -#: ../../CONTRIBUTING.md:75 +#: ../../CONTRIBUTING.md:178 +msgid "" +"To see the different sessions available, you can run the following " +"command in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:183 +msgid "" +"There are different sessions in nox related to building the docs: `docs`," +" `docs-test`, `docs-live`. You can run them by specifying the session " +"name after the `nox` command." +msgstr "" + +#: ../../CONTRIBUTING.md:185 +msgid "`docs`: this session builds the guide and opens it in your browser." +msgstr "" + +#: ../../CONTRIBUTING.md:189 +msgid "" +"To see the guide built locally, open the file `_build/html/index.html` in" +" your browser." +msgstr "" + +#: ../../CONTRIBUTING.md:191 +msgid "`docs-test`: this session runs the tests for the guide." +msgstr "" + +#: ../../CONTRIBUTING.md:195 +msgid "" +"If the tests fail, you will see an error message in your terminal. You " +"need to fix the errors before submitting your pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:197 +msgid "" +"`docs-live`: this session builds the guide and opens it in your browser " +"with live reloading." +msgstr "" + +#: ../../CONTRIBUTING.md:201 +msgid "" +"open the local version of the guide in your browser at ``localhost`` " +"shown in the terminal." +msgstr "" + +#: ../../CONTRIBUTING.md:203 msgid "Before you submit your pull request" msgstr "" -#: ../../CONTRIBUTING.md:77 +#: ../../CONTRIBUTING.md:205 msgid "" -"*__TODO__: This section should describe what steps a user should follow " -"before submitting the pull request: build the docs, verify your changes " -"look correct, etc.*" +"Before submitting your pull request, make sure to run the tests and check" +" the formatting of your code." msgstr "" -#: ../../CONTRIBUTING.md:79 +#: ../../CONTRIBUTING.md:210 +msgid "" +"If the tests fail, you will see an error message in your terminal. You " +"need to fix the errors before submitting your pull request. Also make " +"sure to check the formatting of your documentation by building the docs " +"locally and checking that your changes look correct." +msgstr "" + +#: ../../CONTRIBUTING.md:214 msgid "Submitting a pull request with your contribution" msgstr "" -#: ../../CONTRIBUTING.md:81 +#: ../../CONTRIBUTING.md:216 msgid "How to make a pull request" msgstr "" -#: ../../CONTRIBUTING.md:83 +#: ../../CONTRIBUTING.md:218 +msgid "" +"To open a pull request on GitHub, navigate to the main page of your " +"forked repository and click on the \"Pull requests\" tab." +msgstr "" + +#: ../../CONTRIBUTING.md:220 +msgid "Pull requests tab in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:226 +msgid "" +"An image showing how to navigate to the pull requests tab in GitHub. The " +"pull requests tab is highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:229 +msgid "Click on the \"New pull request\" button." +msgstr "" + +#: ../../CONTRIBUTING.md:231 +msgid "New pull request button in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:237 msgid "" -"*__TODO__: This section should describe how to make a pull request in " -"GitHub.*" +"An image showing how to create a new pull request in GitHub. The new pull" +" request button is highlighted with a red rectangle." msgstr "" -#: ../../CONTRIBUTING.md:85 +#: ../../CONTRIBUTING.md:240 +msgid "" +"Write a clear and concise title and description for your pull request. " +"Make sure to describe the changes you made and why they are necessary." +msgstr "" + +#: ../../CONTRIBUTING.md:242 msgid "What happens when you submit a pull request (CI/CD)" msgstr "" -#: ../../CONTRIBUTING.md:87 +#: ../../CONTRIBUTING.md:244 +msgid "" +"Once you submit a pull request, a series of checks will be run to ensure " +"that your changes do not introduce any bugs or errors. These checks " +"include:" +msgstr "" + +#: ../../CONTRIBUTING.md:246 msgid "" -"*__TODO__: This section should describe how to see the results of the " -"CD/CI checks and how to get more information about errors*" +"**Code formatting and styles**: checks that your code is formatted " +"correctly, by `pre-commit.ci - pr check`." msgstr "" -#: ../../CONTRIBUTING.md:89 +#: ../../CONTRIBUTING.md:247 +msgid "" +"**docs build**: checks that the documentation builds correctly, using " +"`circleci`." +msgstr "" + +#: ../../CONTRIBUTING.md:249 +msgid "You will see the status of these checks in your pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:251 +msgid "Pull request checks in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:257 +msgid "" +"An image showing the status of the checks in a pull request in GitHub. " +"The checks are displayed in a table with a status icon next to each " +"check. The checks are highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:259 +msgid "" +"If any of these checks fail, you will see an error message in your pull " +"request. You need to fix the errors before your changes can be merged." +msgstr "" + +#: ../../CONTRIBUTING.md:261 +msgid "Pull request checks failed in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:267 +msgid "" +"An image showing the status of the checks in a pull request in GitHub. " +"The checks are displayed in a table with a status icon next to each " +"check. The checks that failed and the details link are highlighted with a" +" red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:270 +msgid "" +"To get more information about the errors, you can click on the " +"\"Details\" link next to the failed check." +msgstr "" + +#: ../../CONTRIBUTING.md:272 msgid "What to expect from the review process" msgstr "" -#: ../../CONTRIBUTING.md:91 +#: ../../CONTRIBUTING.md:274 +msgid "" +"Once you submit a pull request, a maintainer of the repository will " +"review your changes and provide feedback. The review process may involve:" +msgstr "" + +#: ../../CONTRIBUTING.md:276 msgid "" -"*__TODO__: This section should describe how review happens in GitHub, how" -" see the comments, and how to submit changes (push a new branch)*" +"**Comments**: the reviewer may leave comments on your pull request to ask" +" questions or provide feedback." msgstr "" -#: ../../CONTRIBUTING.md:93 +#: ../../CONTRIBUTING.md:277 +msgid "" +"**Suggestions**: the reviewer may suggest changes to your code or " +"documentation." +msgstr "" + +#: ../../CONTRIBUTING.md:278 +msgid "" +"**Approvals**: once the reviewer is satisfied with your changes, they " +"will approve the pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:280 +msgid "" +"You can make changes to your pull request by pushing new commits to the " +"branch. The pull request will be updated automatically with your new " +"changes." +msgstr "" + +#: ../../CONTRIBUTING.md:282 +msgid "" +"Once your pull request is approved, it will be merged into the main " +"branch and your changes will be included in the guide." +msgstr "" + +#: ../../CONTRIBUTING.md:284 msgid "Additional help" msgstr "" -#: ../../CONTRIBUTING.md:95 +#: ../../CONTRIBUTING.md:286 msgid "How to get help" msgstr "" -#: ../../CONTRIBUTING.md:97 +#: ../../CONTRIBUTING.md:288 msgid "" "*__TODO__: This section should describe the options for finding more help" " in case beginner contributors need more help (e.g., create an issue, " "post in a forum, etc).*" msgstr "" -#: ../../CONTRIBUTING.md:99 +#: ../../CONTRIBUTING.md:290 msgid "Additional resources" msgstr "" -#: ../../CONTRIBUTING.md:101 +#: ../../CONTRIBUTING.md:292 msgid "" "*__TODO__: It should also include links to beginner documentation, like " "the GitHub docs.*" msgstr "" -#: ../../CONTRIBUTING.md:103 +#: ../../CONTRIBUTING.md:294 msgid "Annex" msgstr "" -#: ../../CONTRIBUTING.md:105 +#: ../../CONTRIBUTING.md:296 msgid "Code examples" msgstr "" -#: ../../CONTRIBUTING.md:107 +#: ../../CONTRIBUTING.md:298 msgid "" "This guide uses the [literalinclude Sphinx directive](https://www.sphinx-" "doc.org/en/master/usage/restructuredtext/directives.html#directive-" @@ -302,18 +601,18 @@ msgid "" "for use in the documentation is kept in the `examples/` folder." msgstr "" -#: ../../CONTRIBUTING.md:111 +#: ../../CONTRIBUTING.md:302 msgid "Referencing code in documentation" msgstr "" -#: ../../CONTRIBUTING.md:113 +#: ../../CONTRIBUTING.md:304 msgid "" "If an example is present elsewhere in the documentation that you want to " "use, you can copy the `literalinclude` directive verbatim and the " "examples will stay in sync." msgstr "" -#: ../../CONTRIBUTING.md:116 +#: ../../CONTRIBUTING.md:307 msgid "" "If you already see code in the examples folder that you can use for new " "documentation, a new `literalinclude` can be made to extract it into the " @@ -323,7 +622,7 @@ msgid "" "the later can protect your example from future modifications to the code." msgstr "" -#: ../../CONTRIBUTING.md:121 +#: ../../CONTRIBUTING.md:312 msgid "" "**Pro tip**: As an alternative to `:lines:` there are also the `:start-" "after:`, `:start-at:`, `:end-before:`, and `:end-at:` options. And if the" @@ -331,17 +630,17 @@ msgid "" "way to keep the same documentation content even through code refactors." msgstr "" -#: ../../CONTRIBUTING.md:125 +#: ../../CONTRIBUTING.md:316 msgid "" "If you need example code that doesn't yet exist in `examples/` see " -"creating code for documentation](#creating-code-for-documentation)." +"[creating code for documentation](#creating-code-for-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:128 +#: ../../CONTRIBUTING.md:319 msgid "Creating code for documentation" msgstr "" -#: ../../CONTRIBUTING.md:130 +#: ../../CONTRIBUTING.md:321 msgid "" "Whenever you come across a place that could benefit from a code block, " "instead of writing it in-line with a code fence (`` ``` `` blocked text) " @@ -350,7 +649,7 @@ msgid "" "code-in-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:134 +#: ../../CONTRIBUTING.md:325 msgid "" "If you want to add a new example that doesn't fit into any of the " "existing example files, you can create a new file and reference it in a " @@ -359,7 +658,7 @@ msgid "" "create a new folder in the `examples` directory." msgstr "" -#: ../../CONTRIBUTING.md:138 +#: ../../CONTRIBUTING.md:329 msgid "" "If an existing example is incomplete or a new example makes sense to be " "added to an existing file, go ahead and add it, but take care to not " @@ -368,14 +667,14 @@ msgid "" "file, new methods after all existing ones in a class." msgstr "" -#: ../../CONTRIBUTING.md:142 +#: ../../CONTRIBUTING.md:333 msgid "" "Example code is checked for correctness, so adding a new example may " "require adding additional tests for coverage, and will require fixing any" " failing tests." msgstr "" -#: ../../CONTRIBUTING.md:145 +#: ../../CONTRIBUTING.md:336 msgid "" "***⚠️ WARNING***: great care should be taken when modifying existing " "example code, especially any modification beyond appending to the end of " @@ -386,29 +685,127 @@ msgid "" "and then checking those pages in a new build." msgstr "" -#: ../../CONTRIBUTING.md:153 +#: ../../CONTRIBUTING.md:344 msgid "Example:" msgstr "" -#: ../../CONTRIBUTING.md:155 +#: ../../CONTRIBUTING.md:346 msgid "Instead of writing example code in markdown like this" msgstr "" -#: ../../CONTRIBUTING.md:166 +#: ../../CONTRIBUTING.md:357 msgid "The python can be extracted into a `.py` file" msgstr "" -#: ../../CONTRIBUTING.md:180 +#: ../../CONTRIBUTING.md:371 msgid "" "As another example, if you only need to show part of a `pyproject.toml`, " "we already have complete project definitions, you need only to find the " "relevant part." msgstr "" -#: ../../CONTRIBUTING.md:183 +#: ../../CONTRIBUTING.md:374 msgid "Instead of writing this" msgstr "" -#: ../../CONTRIBUTING.md:195 +#: ../../CONTRIBUTING.md:386 msgid "an example could be extracted from an existing toml file" msgstr "" + +#~ msgid "" +#~ "Independently of the approach you " +#~ "choose, the first step is to fork" +#~ " the Python Packaging Guide repository " +#~ "into your personal GitHub space." +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show a" +#~ " beginner user how to fork a " +#~ "repository in GitHub.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to use the GitHub interface to " +#~ "edit and previewing a Markdown file.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to commit changes via the GitHub " +#~ "interface.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to clone a repository from GitHub" +#~ " into your computer.*" +#~ msgstr "" + +#~ msgid "*__TODO__: This section should show how to create a new branch.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to create a virtual environment " +#~ "using venv.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to install the development dependencies" +#~ " defined in pyproject.toml.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to commit from the command " +#~ "line.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "the different sessions in nox related" +#~ " to building the docs: docs, docs-" +#~ "test, docs-live. It should also " +#~ "show how to see the guide built" +#~ " locally, by opening the right file" +#~ " in the browser or using the " +#~ "live version from docs-live*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "what steps a user should follow " +#~ "before submitting the pull request: " +#~ "build the docs, verify your changes " +#~ "look correct, etc.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to make a pull request in " +#~ "GitHub.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to see the results of the " +#~ "CD/CI checks and how to get more" +#~ " information about errors*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how review happens in GitHub, how " +#~ "see the comments, and how to " +#~ "submit changes (push a new branch)*" +#~ msgstr "" + +#~ msgid "" +#~ "If you need example code that " +#~ "doesn't yet exist in `examples/` see " +#~ "creating code for documentation](#creating-" +#~ "code-for-documentation)." +#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/TRANSLATING.po b/locales/es/LC_MESSAGES/TRANSLATING.po index 9c147e7c..29880ca9 100644 --- a/locales/es/LC_MESSAGES/TRANSLATING.po +++ b/locales/es/LC_MESSAGES/TRANSLATING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-07-03 16:27-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../TRANSLATING.md:5 msgid "Translation Guide for the Python Packaging Guide" @@ -165,8 +165,9 @@ msgstr "" #: ../../TRANSLATING.md:68 msgid "" -"You can find a list of the two-letter ISO language codes " -"[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." +"You can find a list of the two-letter Sphinx language option " +"[here](https://www.sphinx-doc.org/en/master/usage/configuration.html" +"#confval-language)." msgstr "" #: ../../TRANSLATING.md:71 @@ -426,7 +427,7 @@ msgid "" "Note the `--` before the language code, it indicates that the following " "arguments should be passed into the nox session and not be interpreted " "directly by nox. If you forget the `--`, nox will look instead for a " -"session named 'es' and complain that it does not exist." +"session named 'es' and raise an error that it does not exist." msgstr "" #: ../../TRANSLATING.md:241 @@ -496,7 +497,7 @@ msgid "" msgstr "" #: ../../TRANSLATING.md:268 -msgid "TODO: This tagging could be automated with a GitHub action." +msgid "TODO: This tagging could be automated with a GitHub Actions." msgstr "" #: ../../TRANSLATING.md:270 @@ -705,8 +706,7 @@ msgstr "" #: ../../TRANSLATING.md:343 msgid "" "If you have any questions or need help with your translation, you can " -"create an issue in the repository if you encounter any problems or need " -"assistance." +"create an issue in the repository." msgstr "" #: ../../TRANSLATING.md:345 @@ -715,3 +715,31 @@ msgid "" " as a way for contributors to ask for help with translations or the " "translation workflow?" msgstr "" + +#~ msgid "" +#~ "You can find a list of the " +#~ "two-letter ISO language codes " +#~ "[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." +#~ msgstr "" + +#~ msgid "" +#~ "Note the `--` before the language " +#~ "code, it indicates that the following" +#~ " arguments should be passed into the" +#~ " nox session and not be interpreted" +#~ " directly by nox. If you forget " +#~ "the `--`, nox will look instead " +#~ "for a session named 'es' and " +#~ "complain that it does not exist." +#~ msgstr "" + +#~ msgid "TODO: This tagging could be automated with a GitHub action." +#~ msgstr "" + +#~ msgid "" +#~ "If you have any questions or need" +#~ " help with your translation, you can" +#~ " create an issue in the repository" +#~ " if you encounter any problems or " +#~ "need assistance." +#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/documentation.po b/locales/es/LC_MESSAGES/documentation.po index a94cd7d6..922e0dee 100644 --- a/locales/es/LC_MESSAGES/documentation.po +++ b/locales/es/LC_MESSAGES/documentation.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-28 08:42-0400\n" +"POT-Creation-Date: 2024-08-26 09:16-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../documentation/hosting-tools/intro.md:1 msgid "Tools to Build and Host your Documentation" @@ -33,8 +33,9 @@ msgid "" msgstr "" "Sphinx es la herramienta más común para construir documentación en el " "ecosistema de Python. Sin embargo, algunos mantenedores están usando " -"herramientas como [mkdocs](https://www.mkdocs.org/) para generar la documentación. ¡Es tu " -"decisión usar la herramienta que prefieras para tu documentación!" +"herramientas como [mkdocs](https://www.mkdocs.org/) para generar la " +"documentación. ¡Es tu decisión usar la herramienta que prefieras para tu " +"documentación!" #: ../../documentation/hosting-tools/intro.md:8 msgid "" @@ -43,16 +44,16 @@ msgid "" " writing Sphinx documentation including mySt and rST." msgstr "" "En esta sección introducimos Sphinx como herramienta para construir " -"documentación. Hablamos sobre varias opciones de sintaxis que puedes usar " -"para escribir documentación de Sphinx incluyendo myST and rST." +"documentación. Hablamos sobre varias opciones de sintaxis que puedes usar" +" para escribir documentación de Sphinx incluyendo myST and rST." #: ../../documentation/hosting-tools/intro.md:12 msgid "" "We also talk about ways to publish your documentation online and Sphinx " "tools that might help you optimize your documentation website." msgstr "" -"Hablamos también sobre methodos para publicar tu documentación en línea " -"y herramientas de Sphinx que pueda ayudarte optimizar tu sitio web para " +"Hablamos también sobre methodos para publicar tu documentación en línea y" +" herramientas de Sphinx que pueda ayudarte optimizar tu sitio web para " "documentación." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:1 @@ -73,13 +74,13 @@ msgid "" " blocks and other custom elements to your documentation, you will need to" " use either **myST** or **rST**." msgstr "" -"[markdown](https://www.markdownguide.org/): Markdown es una sintaxis de texto plano " -"que es fácil aprender. Es la sintaxis por defecto para Jupyter Notebooks. Hay " -"herramientas que puedes usar con Sphinx que permiten renderizar " -"markdown como HTML. Sin embargo, usar markdown para escribir documentación " -"tiene limitaciones. Por ejemplo, si deseas añadir referencias, tarjetas " -"de colores, u otros elementos personalizados a tu documentación, necesitarás " -"usar **myST** o **rST**." +"[markdown](https://www.markdownguide.org/): Markdown es una sintaxis de " +"texto plano que es fácil aprender. Es la sintaxis por defecto para " +"Jupyter Notebooks. Hay herramientas que puedes usar con Sphinx que " +"permiten renderizar markdown como HTML. Sin embargo, usar markdown para " +"escribir documentación tiene limitaciones. Por ejemplo, si deseas añadir " +"referencias, tarjetas de colores, u otros elementos personalizados a tu " +"documentación, necesitarás usar **myST** o **rST**." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:8 msgid "" @@ -98,17 +99,18 @@ msgstr "" "flexibilidad." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:9 +#, fuzzy msgid "" "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is " -"a combination of vanilla of `markdown` and `rST` syntax. It is a nice " -"option if you are comfortable writing markdown. `myst` is preferred by " -"many because it offers both the rich functionality of rST combined with a" -" simple-to-write markdown syntax." -msgstr "" -"[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST es una " -"combinación de `markdown` y `rST`. Es una opción buena si te sientes " -"cómodo escribiendo markdown. `myst` es preferido por mucha gente dado que " -"ofrece la amplia funcionalidad de rST en combinación con la sintaxis " +"a combination of `markdown` and `rST` syntax. It is a nice option if you " +"are comfortable writing markdown. `myst` is preferred by many because it " +"offers both the rich functionality of rST combined with a simple-to-write" +" markdown syntax." +msgstr "" +"[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST es " +"una combinación de `markdown` y `rST`. Es una opción buena si te sientes " +"cómodo escribiendo markdown. `myst` es preferido por mucha gente dado que" +" ofrece la amplia funcionalidad de rST en combinación con la sintaxis " "fácil de markdown." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:12 @@ -136,8 +138,8 @@ msgid "" "Most of your core Python package text files, such as your README.md file," " are already in `.md` format" msgstr "" -"La mayoría de los archivos de texto de tus paquetes principales de Python, " -"como el archivo README.md, ya están en formato `.md`." +"La mayoría de los archivos de texto de tus paquetes principales de " +"Python, como el archivo README.md, ya están en formato `.md`." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:18 msgid "" @@ -152,8 +154,8 @@ msgid "" "If you are on the fence about myST vs rst, you might find that **myST** " "is easier for more people to contribute to." msgstr "" -"Si no estás seguro sobre si utilizar myST o rst, puede que encuentres que " -"**myST** es más fácil para contribuciones de más gente." +"Si no estás seguro sobre si utilizar myST o rst, puede que encuentres que" +" **myST** es más fácil para contribuciones de más gente." #: ../../documentation/hosting-tools/publish-documentation-online.md:1 msgid "How to publish your Python package documentation online" @@ -165,9 +167,10 @@ msgid "" "documentation. Two free and commonly used ways to quickly create a " "documentation website hosting environment are below." msgstr "" -"Sugerimos que utilizas un servicio de hosting para la documentación de tu " -"paquete de Python. Abajo encontrarás dos métodos gratuitos y comúnes para servir " -"tu documentación en un sitio web." +"Sugerimos que utilizas un servicio de hosting para la documentación de tu" +" paquete de Python. Abajo encontrarás dos métodos gratuitos y comúnes " +"para servir tu documentación en un sitio web." + #: ../../documentation/hosting-tools/publish-documentation-online.md:7 msgid "" "You can host your documentation yourself using [GitHub " @@ -193,24 +196,24 @@ msgid "" "[Read the Docs](https://readthedocs.org/) is a documentation hosting " "service that supports publishing your project's documentation." msgstr "" -"[Read the Docs](https://readthedocs.org/) es un servicio de hosting " -"que permite publicar la documentación de tu proyecto." +"[Read the Docs](https://readthedocs.org/) es un servicio de hosting que " +"permite publicar la documentación de tu proyecto." #: ../../documentation/hosting-tools/publish-documentation-online.md:13 msgid "" "Read the Docs is a fully featured, free, documentation hosting service. " "Some of its many features include:" msgstr "" -"Read the Docs es un servicio de hosting de documentación gratuito. Algunas de " -"sus funcionalidades son:" +"Read the Docs es un servicio de hosting de documentación gratuito. " +"Algunas de sus funcionalidades son:" #: ../../documentation/hosting-tools/publish-documentation-online.md:16 msgid "" "Is free to host your documentation (but there are also paid tiers if you " "wish to customize hosting)" msgstr "" -"Permite servir tu documentación de forma gratuita (pero hay opciones de pago si deseas " -"personalizar el hosting)" +"Permite servir tu documentación de forma gratuita (pero hay opciones de " +"pago si deseas personalizar el hosting)" #: ../../documentation/hosting-tools/publish-documentation-online.md:17 msgid "Automates building your documentation" @@ -221,8 +224,8 @@ msgid "" "Allows you to turn on integration with pull requests where you can view " "documentation build progress (success vs failure)." msgstr "" -"Te permite integrar solicitudes de cambio para ver el progreso de construcción " -"de la documentación (éxito vs error)" +"Te permite integrar solicitudes de cambio para ver el progreso de " +"construcción de la documentación (éxito vs error)" #: ../../documentation/hosting-tools/publish-documentation-online.md:19 msgid "" @@ -230,8 +233,9 @@ msgid "" "older tagged versions of the docs if they are using older versions of " "your package." msgstr "" -"Permite versionar tu documentación, lo que permite a los usuarios acceder a " -"versiones antiguas de la documentación en caso de que las estén usando en su paquete. " +"Permite versionar tu documentación, lo que permite a los usuarios acceder" +" a versiones antiguas de la documentación en caso de que las estén usando" +" en su paquete. " #: ../../documentation/hosting-tools/publish-documentation-online.md:20 msgid "Supports downloading of documentation in PDF and other formats." @@ -242,8 +246,8 @@ msgid "" "You can customize the documentation build using a **.readthedocs.yaml** " "file in your GitHub repository." msgstr "" -"Puedes personalizar la construcción de la documentación usando un " -"archivo **.readthedocs.yaml** en tu repositorio de GitHub." +"Puedes personalizar la construcción de la documentación usando un archivo" +" **.readthedocs.yaml** en tu repositorio de GitHub." #: ../../documentation/hosting-tools/publish-documentation-online.md:24 msgid "What is GitHub Pages?" @@ -258,10 +262,10 @@ msgid "" "GitHub repository that is setup to run the GitHub Pages web build." msgstr "" "[GitHub Pages](https://docs.github.com/en/pages/getting-started-with-" -"github-pages/about-github-pages) es un servicio web gratuito " -"de GitHub. Con GitHub Pages, puedes construir tu documentación localmente " -"o utilizando Continuous Integration, y empujar a una rama de tu repositorio " -"de GitHub que esté configurada para construir la web en GitHub Pages." +"github-pages/about-github-pages) es un servicio web gratuito de GitHub. " +"Con GitHub Pages, puedes construir tu documentación localmente o " +"utilizando Continuous Integration, y empujar a una rama de tu repositorio" +" de GitHub que esté configurada para construir la web en GitHub Pages." #: ../../documentation/hosting-tools/publish-documentation-online.md:33 msgid "Read the Docs vs GitHub Pages" @@ -283,9 +287,10 @@ msgid "" "service automates the entire process of building and deploying your " "documentation." msgstr "" -"Read the Docs se puede configurar a través de tu cuenta de Read the Docs. " -"El servicio automatiza el proceso de construcción y despliegue de tu " +"Read the Docs se puede configurar a través de tu cuenta de Read the Docs." +" El servicio automatiza el proceso de construcción y despliegue de tu " "documentación." + #: ../../documentation/hosting-tools/publish-documentation-online.md:42 msgid "" "If you don't want to maintain a documentation website for your Python " @@ -307,12 +312,13 @@ msgid "" "[mkdocs](https://www.mkdocs.org/) which is gaining popularity in the " "Python packaging ecosystem." msgstr "" -"En esta página presentamos como utilizar [Sphinx](https://www.sphinx-doc.org/) " -"para construir la documentación orientada a los usuarios de tu paquete. Aunque " -"Sphinx es la herramienta más común en la ecosistema de Python científico, " -"puedes explorar otras herramientas para construir documentación como " -"[mkdocs](https://www.mkdocs.org/) que está ganando popularidad en el " -"ecosistema de empaquetado de Python." +"En esta página presentamos como utilizar [Sphinx](https://www.sphinx-" +"doc.org/) para construir la documentación orientada a los usuarios de tu " +"paquete. Aunque Sphinx es la herramienta más común en la ecosistema de " +"Python científico, puedes explorar otras herramientas para construir " +"documentación como [mkdocs](https://www.mkdocs.org/) que está ganando " +"popularidad en el ecosistema de empaquetado de Python." + #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:25 msgid "Examples of documentation websites that we love:" msgstr "Ejemplos de sitios del web de documentación que nos gustan:" @@ -340,6 +346,7 @@ msgid "" msgstr "" "[Ver página de inicio para verde - archivo rst " ".](https://github.com/fatiando/verde/blob/main/doc/index.rst)" + #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:31 msgid "" "[Here is our documentation if you want to see a myST example of a landing" @@ -363,12 +370,12 @@ msgid "" "\"Statically\" which means that there is no generation or modification of" " the files on the fly." msgstr "" -"Sphinx es un [generador de " -"sitios estáticos](https://www.cloudflare.com/es-es/learning/performance/static-site-" -"generator/). Un generador de sitios estáticos es una herramienta que crea " -"HTML para un sitio web basado en plantillas. Los archivos HTML " -"se sirven \"estáticamente\", lo que significa que no hay generación ni modificación " -"de los archivos en línea." +"Sphinx es un [generador de sitios estáticos](https://www.cloudflare.com" +"/es-es/learning/performance/static-site-generator/). Un generador de " +"sitios estáticos es una herramienta que crea HTML para un sitio web " +"basado en plantillas. Los archivos HTML se sirven \"estáticamente\", lo " +"que significa que no hay generación ni modificación de los archivos en " +"línea." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:39 msgid "Sphinx is written using Python." @@ -376,7 +383,9 @@ msgstr "Sphinx está desarrollado en Python." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:41 msgid "Sphinx sites can be customized using extensions and themes" -msgstr "La documentación creada con Sphinx puede ser personalizada con extensiones y temas" +msgstr "" +"La documentación creada con Sphinx puede ser personalizada con " +"extensiones y temas" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:43 msgid "" @@ -391,8 +400,8 @@ msgid "" "You can apply documentation themes for quick generation of beautiful " "documentation." msgstr "" -"Puedes usar temas de documentación para generación rápida de documentación" -"hermosa." +"Puedes usar temas de documentación para generación rápida de " +"documentaciónhermosa." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:47 msgid "" @@ -401,9 +410,9 @@ msgid "" "autodoc extension](https://www.sphinx-" "doc.org/en/master/usage/extensions/autodoc.html)" msgstr "" -"Puedes [generar automáticamente documentación para las funciones y clases " -"(la API del paquete) desde los docstrings de tu código usando la extensión " -"autodoc](https://www.sphinx-" +"Puedes [generar automáticamente documentación para las funciones y clases" +" (la API del paquete) desde los docstrings de tu código usando la " +"extensión autodoc](https://www.sphinx-" "doc.org/en/master/usage/extensions/autodoc.html)" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:48 @@ -412,8 +421,8 @@ msgid "" "extension](https://www.sphinx-" "doc.org/en/master/usage/extensions/doctest.html)" msgstr "" -"Puedes [ejecutar y probar ejemplos del código en los docstrings usando la " -"extensión doctest](https://www.sphinx-" +"Puedes [ejecutar y probar ejemplos del código en los docstrings usando la" +" extensión doctest](https://www.sphinx-" "doc.org/en/master/usage/extensions/doctest.html)" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:49 @@ -422,9 +431,10 @@ msgid "" "syntax parsers to support easier-to-write syntax using tools such as [the" " MyST parser](https://myst-parser.readthedocs.io/)." msgstr "" -"Aunque Sphinx se basa en sintaxis `rST` de forma nativa, puedes añadir intérpretes de " -"sintaxis personalizadas para usar otras sintaxis más fáciles con herramientas como " -"[MyST](https://myst-parser.readthedocs.io/)." +"Aunque Sphinx se basa en sintaxis `rST` de forma nativa, puedes añadir " +"intérpretes de sintaxis personalizadas para usar otras sintaxis más " +"fáciles con herramientas como [MyST](https://myst-" +"parser.readthedocs.io/)." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:51 msgid "Commonly used Sphinx themes" @@ -437,7 +447,8 @@ msgid "" "include:" msgstr "" "Puedes usar cualquiera tema de Sphinx que prefieras. Sin embargo, los " -"temas más comúnes utilizados en la comunidad de Python científico incluyen:" +"temas más comúnes utilizados en la comunidad de Python científico " +"incluyen:" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:57 msgid "[pydata-sphinx-theme](https://pydata-sphinx-theme.readthedocs.io/)" @@ -546,10 +557,10 @@ msgid "" "documentation content pages. [The OpenGraph protocol allows other " "websites to provide a useful preview of the content on your page when " "shared](https://www.freecodecamp.org/news/what-is-open-graph-and-how-" -"can-i-use-it-for-my-website/#what-is-open-graph). This is important for " -"when the pages in your documentation are shared on social media sites " -"like Twitter and Mastodon and even for shares on tools like Slack and " -"Discourse." +"can-i-use-it-for-my-website/#heading-what-is-open-graph). This is " +"important for when the pages in your documentation are shared on social " +"media sites like Twitter and Mastodon and even for shares on tools like " +"Slack and Discourse." msgstr "" #: ../../documentation/index.md:3 @@ -1682,8 +1693,8 @@ msgstr "" msgid "" "Once you package is accepted to pyOpenSci, we will provide you with a " "badge to add to your repository that shows that it has been reviewed. " -"[![pyOpenSci](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci" -"/software-review/issues/12)" +"[![pyOpenSci](https://pyopensci.org/badges/peer-" +"reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/12)" msgstr "" #: ../../documentation/repository-files/readme-file-best-practices.md:82 @@ -2325,7 +2336,7 @@ msgstr "" msgid "" "It's important to keep in mind that examples in your docstrings help " "users using your package. Running `doctest` on those examples provides a " -"check of your package's API. doctest ensures that the functions and " +"check of your package's API. The doctest ensures that the functions and " "methods in your package run as you expect them to. Neither of these items" " replace a separate, stand-alone test suite that is designed to test your" " package's core functionality across operating systems and Python " @@ -2644,3 +2655,36 @@ msgstr "" #: ../../documentation/write-user-documentation/intro.md:15 msgid "sphinx gallery for tutorials." msgstr "" + +#~ msgid "" +#~ "OpenGraph is an extension that allows" +#~ " you to add metadata to your " +#~ "documentation content pages. [The OpenGraph" +#~ " protocol allows other websites to " +#~ "provide a useful preview of the " +#~ "content on your page when " +#~ "shared](https://www.freecodecamp.org/news/what-is-open-" +#~ "graph-and-how-can-i-use-it-for-" +#~ "my-website/#what-is-open-graph). This " +#~ "is important for when the pages in" +#~ " your documentation are shared on " +#~ "social media sites like Twitter and " +#~ "Mastodon and even for shares on " +#~ "tools like Slack and Discourse." +#~ msgstr "" + +#~ msgid "" +#~ "It's important to keep in mind " +#~ "that examples in your docstrings help" +#~ " users using your package. Running " +#~ "`doctest` on those examples provides a" +#~ " check of your package's API. doctest" +#~ " ensures that the functions and " +#~ "methods in your package run as you" +#~ " expect them to. Neither of these " +#~ "items replace a separate, stand-alone" +#~ " test suite that is designed to " +#~ "test your package's core functionality " +#~ "across operating systems and Python " +#~ "versions." +#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/index.po b/locales/es/LC_MESSAGES/index.po index b6a9f610..f62bbf09 100644 --- a/locales/es/LC_MESSAGES/index.po +++ b/locales/es/LC_MESSAGES/index.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-05 16:34-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Felipe Moreno \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../index.md:283 msgid "Tutorials" @@ -48,7 +48,9 @@ msgstr "La guía de paquetes de Python de pyOpenSci" msgid "" "We support the Python tools that scientists need to create open science " "workflows." -msgstr "Nosotros ayudamos a los científicos a crear flujos de trabajo de ciencia abierta." +msgstr "" +"Nosotros ayudamos a los científicos a crear flujos de trabajo de ciencia " +"abierta." #: ../../index.md:20 msgid "" @@ -79,22 +81,24 @@ msgid "About this guide" msgstr "Sobre esta guía" #: ../../index.md:29 +#, fuzzy msgid "" "Image with the pyOpenSci flower logo in the upper right hand corner. The " "image shows the packaging lifecycle. The graphic shows a high level " -"overview of the elements of a Python package. the inside circle has 5 " +"overview of the elements of a Python package. The inside circle has 5 " "items - user documentation, code/api, test suite, contributor " "documentation, project metadata / license / readme. In the middle of the " -"circle is says maintainers and has a small icon with people. on the " +"circle is says maintainers and has a small icon with people. On the " "outside circle there is an arrow and it says infrastructure." msgstr "" -"Imagen con el logo de la flor de pyOpenSci en la esquina superior derecha. " -"La imagen muestra el ciclo de vida del empaquetado. El gráfico muestra una " -"visión general de los elementos de un paquete de Python. el círculo interior " -"tiene 5 elementos: documentación de usuario, código/api, suite de pruebas, " -"documentación de colaboradores, metadatos del proyecto / licencia / readme. " -"El centro del círculo dice mantenedores y tiene un pequeño icono con personas. " -"En el círculo exterior hay una flecha y dice infraestructura." +"Imagen con el logo de la flor de pyOpenSci en la esquina superior " +"derecha. La imagen muestra el ciclo de vida del empaquetado. El gráfico " +"muestra una visión general de los elementos de un paquete de Python. el " +"círculo interior tiene 5 elementos: documentación de usuario, código/api," +" suite de pruebas, documentación de colaboradores, metadatos del proyecto" +" / licencia / readme. El centro del círculo dice mantenedores y tiene un " +"pequeño icono con personas. En el círculo exterior hay una flecha y dice " +"infraestructura." #: ../../index.md:35 msgid "This guide will help you:" @@ -114,13 +118,17 @@ msgstr "Navegar y tomar decisiones sobre las opciones de las herramientas" #: ../../index.md:40 msgid "Understand all of the pieces of creating and maintaining a Python package" -msgstr "Entender todas las etapas de la creación y mantenimiento de un paquete de Python" +msgstr "" +"Entender todas las etapas de la creación y mantenimiento de un paquete de" +" Python" #: ../../index.md:42 msgid "" "You will also find best practice recommendations and curated lists of " "community resources surrounding packaging and package documentation." -msgstr "Tambien encontrarás recomendaciones y listas de recursos comunitarios sobre empaquetado y documentación de paquetes." +msgstr "" +"Tambien encontrarás recomendaciones y listas de recursos comunitarios " +"sobre empaquetado y documentación de paquetes." #: ../../index.md:46 msgid "Todo" @@ -165,10 +173,11 @@ msgid "" "review process or watch development of future tutorials in our [Github " "repo here](https://github.com/pyOpenSci/python-package-guide)." msgstr "" -"La primera version de nuestra serie de tutoriales de como crear un paquete " -"de Python para científicos está completa! Únete a nuestro proceso de " -"revisión comunitaria o mira el desarrollo de futuros tutoriales en nuestro " -"[repositorio de Github](https://github.com/pyOpenSci/python-package-guide)." +"La primera version de nuestra serie de tutoriales de como crear un " +"paquete de Python para científicos está completa! Únete a nuestro proceso" +" de revisión comunitaria o mira el desarrollo de futuros tutoriales en " +"nuestro [repositorio de Github](https://github.com/pyOpenSci/python-" +"package-guide)." #: ../../index.md:71 msgid "✿ Create a Package Tutorials ✿" @@ -225,8 +234,8 @@ msgid "" "you with your Python packaging needs." msgstr "" "Aprende sobre las mejores prácticas de empaquetado de Python. También " -"conocerás el vibrante ecosistema de herramientas de empaquetado que están " -"disponibles para ayudarte con tus necesidades de empaquetado de Python." +"conocerás el vibrante ecosistema de herramientas de empaquetado que están" +" disponibles para ayudarte con tus necesidades de empaquetado de Python." #: ../../index.md:113 msgid "✨ Create your package ✨" @@ -234,7 +243,9 @@ msgstr "✨ Crea tu paquete ✨" #: ../../index.md:117 msgid "[Package file structure](/package-structure-code/python-package-structure)" -msgstr "[Estructura de archivos de paquete](/package-structure-code/python-package-structure)" +msgstr "" +"[Estructura de archivos de paquete](/package-structure-code/python-" +"package-structure)" #: ../../index.md:118 msgid "" @@ -269,8 +280,8 @@ msgid "" "[Non pure Python builds](package-structure-code/complex-python-package-" "builds.md)" msgstr "" -"[Construcción de paquetes que incluyen otros lenguajes](package-structure-code/complex-python-" -"package-builds.md)" +"[Construcción de paquetes que incluyen otros lenguajes](package-" +"structure-code/complex-python-package-builds.md)" #: ../../index.md:127 msgid "✨ Publish your package ✨" @@ -281,8 +292,8 @@ msgid "" "Gain a better understanding of the Python packaging ecosystem Learn about" " best practices for:" msgstr "" -"Entiende el ecosistema de empaquetado de Python." -"Aprende sobre las mejores prácticas para:" +"Entiende el ecosistema de empaquetado de Python.Aprende sobre las mejores" +" prácticas para:" #: ../../index.md:134 msgid "" @@ -325,8 +336,8 @@ msgid "" "[Write tutorials to show how your package is used](/documentation/write-" "user-documentation/create-package-tutorials)" msgstr "" -"[Escribe tutoriales para mostrar como se usa tu paquete](/documentation/write-" -"user-documentation/create-package-tutorials)" +"[Escribe tutoriales para mostrar como se usa tu paquete](/documentation" +"/write-user-documentation/create-package-tutorials)" #: ../../index.md:158 msgid "✨ Developer Docs ✨" @@ -345,8 +356,8 @@ msgid "" "[Write a development guide](/documentation/repository-files/development-" "guide)" msgstr "" -"[Escribe una guía de desarrollo](/documentation/repository-files/development-" -"guide)" +"[Escribe una guía de desarrollo](/documentation/repository-files" +"/development-guide)" #: ../../index.md:167 msgid "✨ Document For A Community ✨" @@ -357,16 +368,16 @@ msgid "" "[Writing a README file](/documentation/repository-files/readme-file-best-" "practices)" msgstr "" -"[Escribe un archivo README](/documentation/repository-files/readme-file-best-" -"practices)" +"[Escribe un archivo README](/documentation/repository-files/readme-file-" +"best-practices)" #: ../../index.md:171 msgid "" "[Set norms with a Code of Conduct](/documentation/repository-files/code-" "of-conduct-file)" msgstr "" -"[Establece normas con un Código de Conducta](/documentation/repository-files/code-" -"of-conduct-file)" +"[Establece normas con un Código de Conducta](/documentation/repository-" +"files/code-of-conduct-file)" #: ../../index.md:172 msgid "[License your package](/documentation/repository-files/license-files)" @@ -388,16 +399,17 @@ msgstr "[Usando Sphinx](/documentation/hosting-tools/intro)" msgid "" "[Markdown, MyST, and ReST](/documentation/hosting-tools/myst-markdown-" "rst-doc-syntax)" -msgstr "[Markdown, MyST, y ReST](/documentation/hosting-tools/myst-markdown-" -"rst-doc-syntax)" +msgstr "" +"[Markdown, MyST, y ReST](/documentation/hosting-tools/myst-markdown-rst-" +"doc-syntax)" #: ../../index.md:183 msgid "" "[Host your docs on Read The Docs or Github Pages](/documentation/hosting-" "tools/publish-documentation-online)" msgstr "" -"[Publica tu documentación en Read The Docs o Github Pages](/documentation/hosting-" -"tools/publish-documentation-online)" +"[Publica tu documentación en Read The Docs o Github Pages](/documentation" +"/hosting-tools/publish-documentation-online)" #: ../../index.md:189 msgid "" @@ -456,31 +468,32 @@ msgid "" "We welcome contributions to this guide. Learn more about how you can " "contribute." msgstr "" -"Agradecemos las contribuciones a esta guía. Aprende más sobre como puedes " -"contribuir." +"Agradecemos las contribuciones a esta guía. Aprende más sobre como puedes" +" contribuir." #: ../../index.md:246 +#, fuzzy msgid "" "xkcd comic showing a stick figure on the ground and one in the air. The " "one on the ground is saying. `You're flying! how?` The person in the air" " replies `Python!` Below is a 3 rectangle comic with the following text " -"in each box. box 1 - I learned it last night. Everything is so simple. " -"Hello world is just print hello world. box 2 - the person on the ground " -"says - come join us programming is fun again. it's a whole new world. But" +"in each box. Box 1 - I learned it last night. Everything is so simple. " +"Hello world is just print hello world. Box 2 - the person on the ground " +"says - come join us programming is fun again. It's a whole new world. But" " how are you flying? box 3 - the person flying says - i just typed import" " antigravity. I also sampled everything in the medicine cabinet. But i " -"think this is the python. the person on the ground is saying - that's it?" -msgstr "" -"Comic de xkcd mostrando una figura en el suelo y otra en el aire. " -"La que está en el suelo dice: `¡Estás volando! ¿Cómo?` La persona en el aire " -"responde: `¡Python!` Abajo hay un comic de 3 rectángulos con el siguiente " -"texto en cada uno. Rectángulo 1 - Lo aprendí anoche. Todo es tan simple. " -"Hello world es solo print hello world. Rectángulo 2 - La persona en el suelo " -"está diciendo - ven y únete, programar es divertido de nuevo. Es un mundo " -"completamente nuevo. Pero ¿cómo estás volando? Rectángulo 3 - La persona que " -"está volando dice - solo escribí import antigravity. También probé todo en " -"el botiquín. Pero creo que esto es Python. La persona en el suelo está " -"diciendo - ¿eso es todo?" +"think this is the python. The person on the ground is saying - that's it?" +msgstr "" +"Comic de xkcd mostrando una figura en el suelo y otra en el aire. La que " +"está en el suelo dice: `¡Estás volando! ¿Cómo?` La persona en el aire " +"responde: `¡Python!` Abajo hay un comic de 3 rectángulos con el siguiente" +" texto en cada uno. Rectángulo 1 - Lo aprendí anoche. Todo es tan simple." +" Hello world es solo print hello world. Rectángulo 2 - La persona en el " +"suelo está diciendo - ven y únete, programar es divertido de nuevo. Es un" +" mundo completamente nuevo. Pero ¿cómo estás volando? Rectángulo 3 - La " +"persona que está volando dice - solo escribí import antigravity. También " +"probé todo en el botiquín. Pero creo que esto es Python. La persona en el" +" suelo está diciendo - ¿eso es todo?" #: ../../index.md:252 msgid "A community-created guidebook" @@ -493,9 +506,9 @@ msgid "" "we encourage reviews from a diverse set of pythonistas and scientists " "with a wide range of skills and expertise." msgstr "" -"Cada página en esta guía es revisada extensamente por la " -"comunidad. Para asegurar que nuestra guía sea accesible a principiantes y " -"precisa, realizamos revisiones con un conjunto diverso de pythonistas y " +"Cada página en esta guía es revisada extensamente por la comunidad. Para " +"asegurar que nuestra guía sea accesible a principiantes y precisa, " +"realizamos revisiones con un conjunto diverso de pythonistas y " "científicos con una amplia gama de habilidades y experiencia." #: ../../index.md:257 @@ -523,8 +536,8 @@ msgid "" "Resources to help you navigate the Python packaging ecosystem of tools " "and approaches to packaging." msgstr "" -"Recursos para ayudarte a navegar el ecosistema de herramientas y enfoques " -"de empaquetado de Python." +"Recursos para ayudarte a navegar el ecosistema de herramientas y enfoques" +" de empaquetado de Python." #: ../../index.md:271 msgid "" @@ -545,7 +558,8 @@ msgid "" "GitHub.](https://github.com/pyOpenSci/python-package-guide/issues)." msgstr "" "Si tienes ideas de cosas que te gustaría ver aclaradas en esta guía, [te " -"invitamos a abrir un issue en GitHub.](https://github.com/pyOpenSci/python-package-guide/issues)." +"invitamos a abrir un issue en GitHub.](https://github.com/pyOpenSci" +"/python-package-guide/issues)." #: ../../index.md:278 msgid "" @@ -554,8 +568,8 @@ msgid "" "forum](https://pyopensci.discourse.group/)." msgstr "" "Si tienes preguntas sobre nuestro proceso de peer review o sobre el " -"empaquetado en general, eres bienvenido a usar nuestro [foro de Discourse " -"de pyOpenSci](https://pyopensci.discourse.group/)." +"empaquetado en general, eres bienvenido a usar nuestro [foro de Discourse" +" de pyOpenSci](https://pyopensci.discourse.group/)." #: ../../index.md:280 msgid "" @@ -563,6 +577,7 @@ msgid "" " in the Python packaging ecosystem. We will be adding new content over " "the next year." msgstr "" -"Esta es una guía en constante evolución que se actualiza a medida que las " -"herramientas y las recomendaciones prácticas evolucionan en el ecosistema de " -"empaquetado de Python. Estaremos añadiendo nuevo contenido durante el próximo año." +"Esta es una guía en constante evolución que se actualiza a medida que las" +" herramientas y las recomendaciones prácticas evolucionan en el " +"ecosistema de empaquetado de Python. Estaremos añadiendo nuevo contenido " +"durante el próximo año." diff --git a/locales/es/LC_MESSAGES/package-structure-code.po b/locales/es/LC_MESSAGES/package-structure-code.po index 32b82ba3..7b079da5 100644 --- a/locales/es/LC_MESSAGES/package-structure-code.po +++ b/locales/es/LC_MESSAGES/package-structure-code.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-28 08:42-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../package-structure-code/code-style-linting-format.md:1 msgid "Python Package Code Style, Format and Linters" @@ -361,15 +361,15 @@ msgstr "" msgid "From the project root, run:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:181 +#: ../../package-structure-code/code-style-linting-format.md:182 msgid "Python file `temporal.py` imports after `isort` has been run" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:188 +#: ../../package-structure-code/code-style-linting-format.md:189 msgid "Ruff" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:190 +#: ../../package-structure-code/code-style-linting-format.md:191 msgid "" "[Ruff](https://docs.astral.sh/ruff/) is a new addition to the code " "quality ecosystem, gaining some traction since its release. `ruff` is " @@ -379,53 +379,53 @@ msgid "" "of them." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:196 +#: ../../package-structure-code/code-style-linting-format.md:197 msgid "" "`ruff` has some interesting features that distinguish it from other " "linters:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:198 +#: ../../package-structure-code/code-style-linting-format.md:199 msgid "Linter configuration in `pyproject.toml`" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:199 +#: ../../package-structure-code/code-style-linting-format.md:200 msgid "Several hundred rules included, many of which are automatically fixable" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:200 +#: ../../package-structure-code/code-style-linting-format.md:201 msgid "" "Rules explanation, see [F403](https://docs.astral.sh/ruff/rules" "/undefined-local-with-import-star/) for an example" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:201 +#: ../../package-structure-code/code-style-linting-format.md:202 msgid "" "Fast execution time, makes a quick feedback loop possible even on large " "projects." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:203 +#: ../../package-structure-code/code-style-linting-format.md:204 msgid "" "Here is a simple configuration to get started with `ruff`. It would go " "into your `pyproject.toml`:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:211 +#: ../../package-structure-code/code-style-linting-format.md:212 msgid "" "Depending on your project, you might want to add the following to sort " "imports correctly:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:218 +#: ../../package-structure-code/code-style-linting-format.md:219 msgid "How to use code formatter in your local workflow" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:220 +#: ../../package-structure-code/code-style-linting-format.md:221 msgid "Linters, code formatters and your favorite coding tools" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:222 +#: ../../package-structure-code/code-style-linting-format.md:223 msgid "" "Linters can be run as a command-line tool as shown above. They also can " "be run within your favorite coding tool (e.g. VScode, pycharm, etc). For " @@ -434,46 +434,46 @@ msgid "" "favorite code format tools on demand." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:228 +#: ../../package-structure-code/code-style-linting-format.md:229 msgid "Use pre-commit hooks to run code formatters and linters on commits" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:230 +#: ../../package-structure-code/code-style-linting-format.md:231 msgid "You can also setup a `pre-commit hook` in your Python package repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:232 +#: ../../package-structure-code/code-style-linting-format.md:233 msgid "" "A pre-commit hook is a tool that allows an action (or actions) to be " "triggered when you apply a commit to your git repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:235 +#: ../../package-structure-code/code-style-linting-format.md:236 msgid "Pre-commit hook example workflow" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:237 +#: ../../package-structure-code/code-style-linting-format.md:238 msgid "The precommit workflow looks like this: You type and run:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:240 +#: ../../package-structure-code/code-style-linting-format.md:241 msgid "`git commit -m \"message here\"` at the command line" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:242 +#: ../../package-structure-code/code-style-linting-format.md:243 msgid "" "Once you hit return, pre-commit will run any tools that you have " "configured in a **.pre-commit-config.yaml** file." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:244 +#: ../../package-structure-code/code-style-linting-format.md:245 msgid "" "If the tools configured in the pre-commit hook run successfully without " "making changes or finding errors in your code, the commit will be applied" " to the repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:248 +#: ../../package-structure-code/code-style-linting-format.md:249 msgid "" "If the tools configured in the hook find errors in your files, the commit" " will NOT be applied to the repository. Remember from the discussion " @@ -483,20 +483,20 @@ msgid "" "those issues, manually." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:255 +#: ../../package-structure-code/code-style-linting-format.md:256 msgid "" "Once all of the fixes are applied you can re-add (stage) the files to be " "commit. And re-run your commit." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:259 +#: ../../package-structure-code/code-style-linting-format.md:260 msgid "Diagram showing the steps of a pre-commit workflow from left to right." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:261 +#: ../../package-structure-code/code-style-linting-format.md:262 msgid "" "The pre-commit workflow begins with you adding files that have changes to" -" be staged in git. Next, you'd run git commit. when you run git commit, " +" be staged in git. Next, you'd run git commit. When you run git commit, " "the pre-commit hooks will then run. In this example, Black, the code " "formatter and flake8, a linter both run. If all of the files pass Black " "and flake8 checks, then your commit will be recorded. If they don't, the " @@ -506,7 +506,7 @@ msgid "" "using-black-and-flake8/*)" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:274 +#: ../../package-structure-code/code-style-linting-format.md:275 msgid "" "If have a Python code-base and multiple maintainers actively working on " "the code, and you intend to run a tool like Black, be sure to coordinate " @@ -516,11 +516,11 @@ msgid "" "merged." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:281 +#: ../../package-structure-code/code-style-linting-format.md:282 msgid "General pre commit checks" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:283 +#: ../../package-structure-code/code-style-linting-format.md:284 msgid "" "In addition to calling tools, Pre-commit also has a suite of [built in " "format hooks](https://github.com/pre-commit/pre-commit-hooks#hooks-" @@ -529,113 +529,113 @@ msgid "" "streamlined code files." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:288 +#: ../../package-structure-code/code-style-linting-format.md:289 msgid "" "An example pre-commit-config.yaml file is below with examples of how this" " is all setup." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:291 +#: ../../package-structure-code/code-style-linting-format.md:292 msgid "Pre-commit.ci" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:293 +#: ../../package-structure-code/code-style-linting-format.md:294 msgid "" "[Pre-commit.ci](https://pre-commit.ci) is a bot that may become your new " "best friend. This bot, when setup on a repo can be configured to do the " "following:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:296 +#: ../../package-structure-code/code-style-linting-format.md:297 msgid "It will check every pull request using all of the pre-commit hook setting" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:297 +#: ../../package-structure-code/code-style-linting-format.md:298 msgid "" "If you wish, it will also submit a pull request to your repo with pre-" "commit fixes, saving you, and new contributors the time of reformatting a" " pr that has format issues." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:300 +#: ../../package-structure-code/code-style-linting-format.md:301 msgid "You can also call the bot on any pull request to run / and fix the code." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:302 +#: ../../package-structure-code/code-style-linting-format.md:303 msgid "" "The pre-commit.ci bot uses the same pre-commit-config.yaml file that you " "use to setup pre-commit locally." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:305 +#: ../../package-structure-code/code-style-linting-format.md:306 msgid "Setting up a bot like this can be valuable because:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:307 +#: ../../package-structure-code/code-style-linting-format.md:308 msgid "" "It can make is easier for maintainers as they no longer have to worry at " "allows about fixing code format. The bot will do the work for them." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:309 +#: ../../package-structure-code/code-style-linting-format.md:310 msgid "" "It can make it easier for new comers as they never have to setup pre-" "commit locally or worry about linting their code. They can even make " "small fixes to the code directly on GitHub without worry." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:311 +#: ../../package-structure-code/code-style-linting-format.md:312 msgid "Setting up a git pre-commit hook" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:313 +#: ../../package-structure-code/code-style-linting-format.md:314 msgid "To setup pre-commit locally, you need to do 3 things:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:315 +#: ../../package-structure-code/code-style-linting-format.md:316 msgid "" "Install pre-commit (and include it as a development requirement in your " "repository)" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:325 +#: ../../package-structure-code/code-style-linting-format.md:326 msgid "" "Create a .pre-commit-config.yaml file in the root of your package " "directory." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:327 +#: ../../package-structure-code/code-style-linting-format.md:328 msgid "" "Below is an example **.pre-commit-cofig.yaml** file that can be used to " "setup the pre-commit hook and the pre-commit.ci bot if you chose to " "implement that too." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:335 +#: ../../package-structure-code/code-style-linting-format.md:336 msgid "" "This file specifies a hook that will be triggered automatically before " "each `git commit`, in this case, it specifies a `flake8` using version " "`6.0.0`." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:338 +#: ../../package-structure-code/code-style-linting-format.md:339 msgid "" "Install your pre-commit hook(s) using `pre-commit install`. This will " "install all of the hooks specified in the pre-commit yaml file into your " "environment." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:340 +#: ../../package-structure-code/code-style-linting-format.md:341 msgid "" "Once you have done the above, you are ready to start working on your " "code. Pre-commit will run every time you run `git commit`." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:343 +#: ../../package-structure-code/code-style-linting-format.md:344 msgid "Summary" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:345 +#: ../../package-structure-code/code-style-linting-format.md:346 msgid "" "pyOpenSci suggests setting up a linter and a code styler for your " "package, regardless of whether you use pre-commit hooks, CI or other " @@ -816,7 +816,7 @@ msgid "" "keep this comment - https://github.com/pyOpenSci/python-package-" "guide/pull/106#issuecomment-1844278487 in this file for now - jeremiah " "did a nice inventory of common shells and whether they need quotes or " -"not. it's really comprehensive. but do we want it in the guide?? it's " +"not. It's really comprehensive. But do we want it in the guide?? it's " "really useful for more advanced users i think." msgstr "" @@ -851,18 +851,18 @@ msgid "" msgstr "" #: ../../package-structure-code/declare-dependencies.md:29 -msgid "needs to function properly." +msgid "Needs to function properly." msgstr "" #: ../../package-structure-code/declare-dependencies.md:30 msgid "" -"requires if someone wants to develop / work on improving your package " +"Requires if someone wants to develop / work on improving your package " "locally or" msgstr "" #: ../../package-structure-code/declare-dependencies.md:31 msgid "" -"requires if a user wants to add additional functionality (that is not " +"Requires if a user wants to add additional functionality (that is not " "core) to your package" msgstr "" @@ -1184,7 +1184,7 @@ msgid "" "dependency groups listed above - docs feature and tests. In the center it" " says your-package and lists the core dependencies of that package " "seaborn and numpy. To the right are two arrows. The first shows the " -"command python - m pip install your-package. it them shows how installing" +"command python - m pip install your-package. It them shows how installing" " your package that way installs only the package and the two core " "dependencies into a users environment. Below is a second arrow with " "python -m pip install youPackage[tests]. This leads to an environment " @@ -1877,7 +1877,7 @@ msgstr "" msgid "" "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 " +"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." @@ -1889,11 +1889,12 @@ msgstr "" "si creas una receta de conda-forge, puedes publicar en conda-forge." #: ../../package-structure-code/publish-python-package-pypi-conda.md:26 +#, fuzzy msgid "" "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 " +" The 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." msgstr "" "Una vez que haya publicado ambas distribuciones de paquetes (la distribución de origen " @@ -2089,10 +2090,10 @@ msgid "" "Graphic with the title Python package repositories. Below it says " "Anything hosted on PyPI can be installed using pip install. Packaging " "hosted on a conda channel can be installed using conda install. Below " -"that there are two rows. the top row says conda channels. next to it are " +"that there are two rows. The top row says conda channels. Next to it are " "three boxes one with conda-forge, community maintained; bioconda and then" " default - managed by the anaconda team. Below that there is a row that " -"says PyPI servers. PyPI - anyone can publish to PyPI. and test PyPI. a " +"says PyPI servers. PyPI - anyone can publish to PyPI. And test PyPI. A " "testbed server for you to practice." msgstr "" "Gráfico con el título Repositorios de paquetes de Python. Debajo dice " @@ -2484,7 +2485,6 @@ msgid "How the pyproject.toml is used when you build a package" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:104 -#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 msgid "" "When you publish to PyPI, you will notice that each package has metadata " "listed. Let’s have a look at [xclim](https://pypi.org/project/xclim/), " @@ -2704,7 +2704,7 @@ msgid "" "Here is an example of[ a package that has entry point " "script](https://github.com/pyOpenSci/update-web-" "metadata/blob/main/pyproject.toml#L60)s. Notice that there are several " -"core scripts defined in that package that perform sets of tasks. " +"core scripts defined in that package that perform sets of tasks. The " "pyOpenSci is using those scripts to process their metadata." msgstr "" @@ -2713,7 +2713,7 @@ msgid "" "**Dynamic Fields:** if you have fields that are dynamically populated. " "One example of this is if you are using scm / version control based " "version with tools like `setuptooms_scm`, then you might use the dynamic " -"field. such as version (using scm) **dynamic = [\"version\"]**" +"field, such as version (using scm) **dynamic = [\"version\"]**" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:189 @@ -4487,16 +4487,19 @@ msgid "Learn about Building a Python Package" msgstr "Aprenda sobre la construcción de un paquete de Python" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:8 +#, fuzzy msgid "" "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." +" The 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." msgstr "" -"Una vez que haya publicado ambas distribuciones de paquetes (la distribución del código fuente y la distribución construida o wheel) en PyPI, " -"entonces puede publicar en conda-forge. conda-forge requiere una distribución de origen en PyPI para construir su " -"paquete en conda-forge. No necesita reconstruir su paquete para publicar en conda-forge." +"Una vez que haya publicado ambas distribuciones de paquetes (la " +"distribución del código fuente y la distribución construida o wheel) en " +"PyPI, entonces puede publicar en conda-forge. conda-forge requiere una " +"distribución de origen en PyPI para construir su paquete en conda-forge. " +"No necesita reconstruir su paquete para publicar en conda-forge." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:11 msgid "" @@ -4507,12 +4510,12 @@ msgid "" "PyPI in order for conda-forge to properly build your package " "automatically." msgstr "" -"Necesita construir su paquete de Python para publicarlo en PyPI " -"(o en un canal de conda). El proceso de construcción organiza su código " -"y metadatos en un formato de distribución que puede ser subido a PyPI y " +"Necesita construir su paquete de Python para publicarlo en PyPI (o en un " +"canal de conda). El proceso de construcción organiza su código y " +"metadatos en un formato de distribución que puede ser subido a PyPI y " "posteriormente descargado e instalado por los usuarios. NOTA: necesita " -"publicar un sdist (distribución del código fuente) en PyPI para que conda-forge pueda construir su paquete " -"automáticamente." +"publicar un sdist (distribución del código fuente) en PyPI para que " +"conda-forge pueda construir su paquete automáticamente." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:14 msgid "What is building a Python package?" @@ -4523,8 +4526,9 @@ msgid "" "To [publish your Python package](publish-python-package-pypi-conda) and " "make it easy for anyone to install, you first need to build it." msgstr "" -"Para [publicar su paquete de Python](publish-python-package-pypi-conda) y " -"hacer que sea fácil de instalar para cualquiera, primero necesita construirlo." +"Para [publicar su paquete de Python](publish-python-package-pypi-conda) y" +" hacer que sea fácil de instalar para cualquiera, primero necesita " +"construirlo." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:18 msgid "But, what does it mean to build a Python package?" @@ -4538,10 +4542,11 @@ msgid "" "and metadata about the package, in the format required by the Python " "Package Index, so that it can be installed by tools like pip." msgstr "" -"[Como se muestra en la figura de arriba](#pypi-conda-channels), cuando construye su paquete de Python, convierte " -"los archivos de código fuente en algo llamado paquete de distribución." -" Un paquete de distribución contiene su código fuente " -"y metadatos sobre el paquete, en el formato requerido por el Python Package Index (PyPI), para que pueda ser " +"[Como se muestra en la figura de arriba](#pypi-conda-channels), cuando " +"construye su paquete de Python, convierte los archivos de código fuente " +"en algo llamado paquete de distribución. Un paquete de distribución " +"contiene su código fuente y metadatos sobre el paquete, en el formato " +"requerido por el Python Package Index (PyPI), para que pueda ser " "instalado por herramientas como pip." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:23 @@ -4551,9 +4556,11 @@ msgid "" " Authority](https://www.pypa.io/en/latest/) and refer to the product of " "the build step as a **distribution package**." msgstr "" -"El término paquete solía significar muchas cosas diferentes en Python y otros lenguajes. En esta página, " -"adaptamos la convención de la [Autoridad de Empaquetado de Python](https://www.pypa.io/en/latest/) y nos referimos " -"al producto del paso de construcción como un **paquete de distribución**." +"El término paquete solía significar muchas cosas diferentes en Python y " +"otros lenguajes. En esta página, adaptamos la convención de la [Autoridad" +" de Empaquetado de Python](https://www.pypa.io/en/latest/) y nos " +"referimos al producto del paso de construcción como un **paquete de " +"distribución**." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:27 msgid "" @@ -4561,8 +4568,9 @@ msgid "" " and metadata into a format that both pip and PyPI can use, is called a " "build step." msgstr "" -"Este proceso de organizar y formatear su código, documentación, pruebas y metadatos en un formato que tanto pip " -"como PyPI pueden usar, se llama paso de construcción." +"Este proceso de organizar y formatear su código, documentación, pruebas y" +" metadatos en un formato que tanto pip como PyPI pueden usar, se llama " +"paso de construcción." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:31 msgid "Project metadata and PyPI" @@ -4575,9 +4583,10 @@ msgid "" "](pyproject-toml-python-package-metadata). This metadata is used for " "several purposes:" msgstr "" -"Los metadatos que tanto las herramientas de construcción como PyPI utilizan para describir y entender su paquete " -"generalmente se almacenan en un [archivo pyproject.toml](pyproject-toml-python-package-metadata). Estos metadatos " -"se utilizan para varios propósitos:" +"Los metadatos que tanto las herramientas de construcción como PyPI " +"utilizan para describir y entender su paquete generalmente se almacenan " +"en un [archivo pyproject.toml](pyproject-toml-python-package-metadata). " +"Estos metadatos se utilizan para varios propósitos:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:35 msgid "" @@ -4586,9 +4595,10 @@ msgid "" "poetry, PDM or Hatch) understand how to build your package. Information " "it provides to your build tool includes:" msgstr "" -"Ayuda a la herramienta que use para construir su paquete (pip, [Build de pypa](https://pypi.org/project/build/) o " -"una herramienta de extremo a extremo como poetry, PDM o Hatch) a entender cómo construir su paquete. La información " -"que proporciona a su herramienta de construcción incluye:" +"Ayuda a la herramienta que use para construir su paquete (pip, [Build de " +"pypa](https://pypi.org/project/build/) o una herramienta de extremo a " +"extremo como poetry, PDM o Hatch) a entender cómo construir su paquete. " +"La información que proporciona a su herramienta de construcción incluye:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:37 msgid "" @@ -4596,16 +4606,19 @@ msgid "" "[build backend tool](build_backends) you wish to use for creating your " "sdist and wheel distributions." msgstr "" -"La tabla `[build-system]` en su archivo pyproject.toml le dice a pip qué [herramienta de backend de construcción]" -"(build_backends) desea usar para crear sus distribuciones sdist (distribución del código fuente) y wheel (distribución construida)." +"La tabla `[build-system]` en su archivo pyproject.toml le dice a pip qué " +"[herramienta de backend de construcción](build_backends) desea usar para " +"crear sus distribuciones sdist (distribución del código fuente) y wheel " +"(distribución construida)." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:45 msgid "" "And the dependencies section of your project table tells the build tool " "and PyPI what dependencies your project requires." msgstr "" -"Y la sección de dependencias de su tabla de proyecto le dice a la herramienta de construcción y a PyPI qué " -"dependencias requiere su proyecto." +"Y la sección de dependencias de su tabla de proyecto le dice a la " +"herramienta de construcción y a PyPI qué dependencias requiere su " +"proyecto." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:54 msgid "" @@ -4613,9 +4626,10 @@ msgid "" " you publish on PyPI), it also creates a METADATA file which PyPI can " "read and use to help users find your package. For example:" msgstr "" -"Cuando la herramienta de construcción crea el archivo de distribución de su paquete (el archivo que publica en " -"PyPI), también crea un archivo METADATA que PyPI puede leer y usar para ayudar a los usuarios a encontrar su paquete. " -"Por ejemplo:" +"Cuando la herramienta de construcción crea el archivo de distribución de " +"su paquete (el archivo que publica en PyPI), también crea un archivo " +"METADATA que PyPI puede leer y usar para ayudar a los usuarios a " +"encontrar su paquete. Por ejemplo:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:56 msgid "" @@ -4624,9 +4638,10 @@ msgid "" "filter for packages that contain specific licenses or that support " "specific versions of python." msgstr "" -"La sección `classifiers = ` de su tabla `[project]` en el archivo pyproject.toml proporciona información que los " -"usuarios en PyPI pueden usar para filtrar paquetes que contienen licencias específicas o que admiten versiones " -"específicas de Python." +"La sección `classifiers = ` de su tabla `[project]` en el archivo " +"pyproject.toml proporciona información que los usuarios en PyPI pueden " +"usar para filtrar paquetes que contienen licencias específicas o que " +"admiten versiones específicas de Python." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:73 msgid "What happened to setup.py and setup.cfg for metadata?" @@ -4639,34 +4654,52 @@ msgid "" "metadata is to use a pyproject.toml file. [Learn more about the " "pyproject.toml file here.](pyproject-toml-python-package-metadata)" msgstr "" -"Los metadatos del proyecto solían almacenarse en un archivo setup.py o en un archivo setup.cfg. La práctica " -"recomendada actual para almacenar metadatos de paquetes es utilizar un archivo pyproject.toml. [Aprenda más sobre el " -"archivo pyproject.toml aquí.](pyproject-toml-python-package-metadata)" +"Los metadatos del proyecto solían almacenarse en un archivo setup.py o en" +" un archivo setup.cfg. La práctica recomendada actual para almacenar " +"metadatos de paquetes es utilizar un archivo pyproject.toml. [Aprenda más" +" sobre el archivo pyproject.toml aquí.](pyproject-toml-python-package-" +"metadata)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:79 msgid "An example - xclim" msgstr "Un ejemplo - xclim" +#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 +msgid "" +"When you publish to PyPI, you will notice that each package has metadata " +"listed. Let's have a look at [xclim](https://pypi.org/project/xclim/), " +"one of our [pyOpenSci packages](https://www.pyopensci.org/python-" +"packages.html). Notice that on the PyPI landing page you see some " +"metadata about the package including python, maintainer information and " +"more. PyPI is able to populate this metadata because it was defined using" +" correct syntax and classifiers by Xclim's maintainers, [pyproject.toml " +"file](https://github.com/Ouranosinc/xclim/blob/master/pyproject.toml). " +"This metadata when the xclim package is built, is translated into a " +"distribution file that allows PyPI to read the metadata and print it out " +"on their website." +msgstr "" + #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:94 +#, fuzzy msgid "" "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" +"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 " +"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." msgstr "" -"Gráfico que muestra el flujo de trabajo de empaquetado de alto nivel." -" A la izquierda se ve un gráfico con código, metadatos y tests en él. " -"Esos elementos van todos en su paquete. La documentación y los datos " -"están debajo de ese recuadro porque normalmente no se publican en su " -"distribución construida (wheel). Una flecha a la derecha lo lleva a " -"un cuadro de archivos de distribución de construcción. Ese cuadro lo lleva " -"a publicar en TestPyPI o en el verdadero PyPI. Desde PyPI, puede conectarse " -"a conda-forge para una construcción automatizada que envía distribuciones " -"de PyPI a conda-forge." +"Gráfico que muestra el flujo de trabajo de empaquetado de alto nivel. A " +"la izquierda se ve un gráfico con código, metadatos y tests en él. Esos " +"elementos van todos en su paquete. La documentación y los datos están " +"debajo de ese recuadro porque normalmente no se publican en su " +"distribución construida (wheel). Una flecha a la derecha lo lleva a un " +"cuadro de archivos de distribución de construcción. Ese cuadro lo lleva a" +" publicar en TestPyPI o en el verdadero PyPI. Desde PyPI, puede " +"conectarse a conda-forge para una construcción automatizada que envía " +"distribuciones de PyPI a conda-forge." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:96 msgid "" @@ -4677,37 +4710,40 @@ msgid "" "PyPI in order for conda-forge to properly build your package " "automatically." msgstr "" -"Necesita construir su paquete de Python para publicarlo en PyPI (o Conda). " -"El proceso de construcción organiza su código y metadatos en un formato de " -"distribución que puede ser subido a PyPI y posteriormente descargado e " -"instalado por los usuarios. NOTA: necesita publicar distribución del código fuente (sdist) en PyPI para " -"que conda-forge pueda construir su paquete automáticamente." +"Necesita construir su paquete de Python para publicarlo en PyPI (o " +"Conda). El proceso de construcción organiza su código y metadatos en un " +"formato de distribución que puede ser subido a PyPI y posteriormente " +"descargado e instalado por los usuarios. NOTA: necesita publicar " +"distribución del código fuente (sdist) en PyPI para que conda-forge pueda" +" construir su paquete automáticamente." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:101 +#, fuzzy msgid "" -"This screenshot shows the metadata on PyPI for the xclim package. on it " +"This screenshot shows the metadata on PyPI for the xclim package. On it " "you can see the name of the license, the author and maintainer names " "keywords associated with the package and the base python version it " "requires which is 3.8." msgstr "" -"Esta captura de pantalla muestra los metadatos en PyPI para el paquete xclim. " -"En ella puede ver el nombre de la licencia, los nombres del autor y del " -"mantenedor, palabras clave asociadas con el paquete y la versión base de " -"Python que requiere, que es 3.8." +"Esta captura de pantalla muestra los metadatos en PyPI para el paquete " +"xclim. En ella puede ver el nombre de la licencia, los nombres del autor " +"y del mantenedor, palabras clave asociadas con el paquete y la versión " +"base de Python que requiere, que es 3.8." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:103 msgid "PyPI screenshot showing metadata for the xclim package." msgstr "Captura de pantalla de PyPI que muestra metadatos para el paquete xclim." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:110 +#, fuzzy msgid "" -"Here you see the maintainer metadata as it is displayed on PyPI. for " +"Here you see the maintainer metadata as it is displayed on PyPI. For " "xclim there are three maintainers listed with their profile pictures and " "github user names to the right." msgstr "" "Aquí ve los metadatos del mantenedor tal como se muestran en PyPI. Para " -"xclim hay tres mantenedores listados con sus fotos de perfil y nombres de " -"usuario de GitHub a la derecha." +"xclim hay tres mantenedores listados con sus fotos de perfil y nombres de" +" usuario de GitHub a la derecha." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:112 msgid "" @@ -4716,10 +4752,11 @@ msgid "" "and then processed by your build tool and stored in your packages sdist " "and wheel distributions." msgstr "" -"Nombres de los mantenedores y nombres de usuario de GitHub para el paquete " -"xclim tal como se muestran en PyPI. Esta información se registra en su " -"pyproject.toml y luego es procesada por su herramienta de construcción y " -"almacenada en las distribuciones sdist y wheel de sus paquetes." +"Nombres de los mantenedores y nombres de usuario de GitHub para el " +"paquete xclim tal como se muestran en PyPI. Esta información se registra " +"en su pyproject.toml y luego es procesada por su herramienta de " +"construcción y almacenada en las distribuciones sdist y wheel de sus " +"paquetes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:115 msgid "How to create the distribution format that PyPI and Pip expects?" @@ -4733,11 +4770,11 @@ msgid "" "there are packages and tools that help you create package build " "distribution files." msgstr "" -"En teoría, podría crear sus propios scripts para organizar su código " -"de la manera que PyPI quiere que sea. Sin embargo, al igual que hay " -"paquetes que manejan estructuras conocidas como dataframes de Pandas " -"y arrays de Numpy, hay paquetes y herramientas que le " -"ayudan a crear archivos de distribución de construcción de paquetes." +"En teoría, podría crear sus propios scripts para organizar su código de " +"la manera que PyPI quiere que sea. Sin embargo, al igual que hay paquetes" +" que manejan estructuras conocidas como dataframes de Pandas y arrays de " +"Numpy, hay paquetes y herramientas que le ayudan a crear archivos de " +"distribución de construcción de paquetes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:121 msgid "" @@ -4748,10 +4785,11 @@ msgid "" " with other parts of the packaging process." msgstr "" "Existen una serie de herramientas de empaquetado que pueden ayudarle con " -"todo el proceso de empaquetado o solo con un paso del proceso. Por ejemplo, " -"setuptools es un backend de construcción comúnmente utilizado que se puede " -"usar para crear su sdist y wheel. Mientras que herramientas como " -"Hatch, PDM, Poetry y flit ayudan con otras partes del proceso de empaquetado." +"todo el proceso de empaquetado o solo con un paso del proceso. Por " +"ejemplo, setuptools es un backend de construcción comúnmente utilizado " +"que se puede usar para crear su sdist y wheel. Mientras que herramientas " +"como Hatch, PDM, Poetry y flit ayudan con otras partes del proceso de " +"empaquetado." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:127 msgid "" @@ -4760,9 +4798,9 @@ msgid "" "output (with minor differences that most users may not care about). Learn" " more about those tools on this page." msgstr "" -"Si bien esto puede causar cierta confusión y complejidad en el ecosistema " -"de empaquetado, en su mayor parte, cada herramienta proporciona la misma " -"salida de distribución (con diferencias menores que a la mayoría de los " +"Si bien esto puede causar cierta confusión y complejidad en el ecosistema" +" de empaquetado, en su mayor parte, cada herramienta proporciona la misma" +" salida de distribución (con diferencias menores que a la mayoría de los " "usuarios pueden no importarles). Aprenda más sobre esas herramientas en " "esta página." @@ -4772,9 +4810,9 @@ msgid "" "you to publish: sdist and wheel. You will learn about their structure and" " what files belong in each." msgstr "" -"A continuación, aprenderá sobre los dos archivos de distribución que PyPI " -"espera que publique: sdist y wheel. Aprenderá sobre su estructura " -"y qué archivos pertenecen a cada uno." +"A continuación, aprenderá sobre los dos archivos de distribución que PyPI" +" espera que publique: sdist y wheel. Aprenderá sobre su estructura y qué " +"archivos pertenecen a cada uno." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:136 msgid "" @@ -4785,11 +4823,11 @@ msgid "" "installed onto anyones' computer." msgstr "" "Hay dos archivos de distribución principales que necesita crear para " -"publicar su paquete de Python en PyPI: la distribución de origen (a menudo " -"llamada sdist) y la distribución construida (wheel). El sdist contiene el código fuente " -"sin procesar de su paquete. La wheel (.whl) contiene los archivos " -"construidos / compilados que se pueden instalar directamente en el " -"ordenador de cualquier persona." +"publicar su paquete de Python en PyPI: la distribución de origen (a " +"menudo llamada sdist) y la distribución construida (wheel). El sdist " +"contiene el código fuente sin procesar de su paquete. La wheel (.whl) " +"contiene los archivos construidos / compilados que se pueden instalar " +"directamente en el ordenador de cualquier persona." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:142 msgid "Learn more about both distributions below." @@ -4805,9 +4843,9 @@ msgid "" msgstr "" "Si su paquete es un paquete de Python puro sin pasos adicionales de " "construcción / compilación, entonces las distribuciones sdist y wheel " -"tendrán contenido similar. Sin embargo, si su paquete tiene extensiones en " -"otros lenguajes o es más complejo en su construcción, las dos distribuciones " -"serán muy diferentes." +"tendrán contenido similar. Sin embargo, si su paquete tiene extensiones " +"en otros lenguajes o es más complejo en su construcción, las dos " +"distribuciones serán muy diferentes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:150 msgid "" @@ -4818,8 +4856,8 @@ msgid "" msgstr "" "También tenga en cuenta que no estamos discutiendo flujos de trabajo de " "construcción de conda en esta sección. [Puede aprender más sobre las " -"construcciones de conda aquí.](https://conda.io/projects/conda-build/en/" -"latest/user-guide/tutorials/index.html)" +"construcciones de conda aquí.](https://conda.io/projects/conda-" +"build/en/latest/user-guide/tutorials/index.html)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:155 msgid "Source Distribution (sdist)" @@ -4831,10 +4869,10 @@ msgid "" "These are the \"raw / as-is\" files that you store on GitHub or whatever " "platform you use to manage your code." msgstr "" -"Los **archivos de código fuente** son los archivos sin construir necesarios para " -"construir su paquete. Estos son los archivos \"originales / sin procesar\" " -"que almacena en GitHub o en cualquier plataforma que utilice para gestionar " -"su código." +"Los **archivos de código fuente** son los archivos sin construir " +"necesarios para construir su paquete. Estos son los archivos \"originales" +" / sin procesar\" que almacena en GitHub o en cualquier plataforma que " +"utilice para gestionar su código." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:161 msgid "" @@ -4846,12 +4884,14 @@ msgid "" "everything required to build a wheel (except for project dependencies) " "without network access." msgstr "" -"Las distribuciones de código fuente (del inglés, _source distribution_) se denominan sdist. Como " -"su nombre indica, una distribución sdist contiene el código fuente; no ha sido construido ni" -" compilado de ninguna manera. Por lo tanto, cuando un usuario instala su distribución de código fuente " -"usando pip, pip necesita ejecutar un paso de construcción primero. Por esta razón, " -"podría definir una distribución sdist como un archivo comprimido que contiene todo lo " -"necesario para construir una wheel (excepto las dependencias del proyecto) sin acceso a la red." +"Las distribuciones de código fuente (del inglés, _source distribution_) " +"se denominan sdist. Como su nombre indica, una distribución sdist " +"contiene el código fuente; no ha sido construido ni compilado de ninguna " +"manera. Por lo tanto, cuando un usuario instala su distribución de código" +" fuente usando pip, pip necesita ejecutar un paso de construcción " +"primero. Por esta razón, podría definir una distribución sdist como un " +"archivo comprimido que contiene todo lo necesario para construir una " +"wheel (excepto las dependencias del proyecto) sin acceso a la red." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:165 msgid "" @@ -4859,13 +4899,16 @@ msgid "" "\"tarball\"). Thus, when a user installs your source distribution using " "pip, pip needs to run a build step first." msgstr "" -"Normalmente, sdist se almacena como un archivo `.tar.gz` (a menudo llamado " -"un \"tarball\"). Por lo tanto, cuando un usuario instala su distribución de origen " -"usando pip, pip necesita ejecutar un paso de construcción primero." +"Normalmente, sdist se almacena como un archivo `.tar.gz` (a menudo " +"llamado un \"tarball\"). Por lo tanto, cuando un usuario instala su " +"distribución de origen usando pip, pip necesita ejecutar un paso de " +"construcción primero." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:167 msgid "Below is an example sdist for the stravalib Python package:" -msgstr "A continuación se muestra un ejemplo de sdist para el paquete de Python stravalib:" +msgstr "" +"A continuación se muestra un ejemplo de sdist para el paquete de Python " +"stravalib:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:219 msgid "GitHub archive vs sdist" @@ -4880,12 +4923,12 @@ msgid "" "`setuptools_scm` or `hatch_vcs` the sdist may also contain a file that " "stores the version." msgstr "" -"Cuando se crea una versión en GitHub, se crea un `git archive` que contiene " -"todos los archivos de su repositorio de GitHub. Si bien estos archivos son " -"similares a un sdist, estos dos archivos no son iguales. El sdist contiene " -"algunos otros elementos, incluido un directorio de metadatos y si utiliza " -"`setuptools_scm` o `hatch_vcs`, el sdist también puede contener un archivo " -"que almacena la versión." +"Cuando se crea una versión en GitHub, se crea un `git archive` que " +"contiene todos los archivos de su repositorio de GitHub. Si bien estos " +"archivos son similares a un sdist, estos dos archivos no son iguales. El " +"sdist contiene algunos otros elementos, incluido un directorio de " +"metadatos y si utiliza `setuptools_scm` o `hatch_vcs`, el sdist también " +"puede contener un archivo que almacena la versión." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:229 msgid "Wheel (.whl files):" @@ -4900,13 +4943,13 @@ msgid "" "may be included in source distributions are not included in wheels " "because it is a built distribution." msgstr "" -"Un archivo wheel es un archivo en formato ZIP cuyo nombre sigue" -" un formato específico (a continuación) y tiene la " -"extensión `.whl`. El archivo `.whl` contiene un conjunto específico de " -"archivos, incluidos metadatos que se generan a partir del archivo " -"pyproject.toml de su proyecto. El pyproject.toml y otros archivos que " -"pueden estar incluidos en las distribuciones de origen no se incluyen en " -"las wheels porque es una distribución construida." +"Un archivo wheel es un archivo en formato ZIP cuyo nombre sigue un " +"formato específico (a continuación) y tiene la extensión `.whl`. El " +"archivo `.whl` contiene un conjunto específico de archivos, incluidos " +"metadatos que se generan a partir del archivo pyproject.toml de su " +"proyecto. El pyproject.toml y otros archivos que pueden estar incluidos " +"en las distribuciones de origen no se incluyen en las wheels porque es " +"una distribución construida." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:238 msgid "" @@ -4918,14 +4961,14 @@ msgid "" "thus faster to install - particularly if you have a package that requires" " build steps." msgstr "" -"La wheel (.whl) es su distribución binaria construida. Los" -" **archivos binarios** son los archivos de código fuente " -"construidos / compilados. Estos archivos están listos para ser instalados." -" Una wheel (**.whl**) es un archivo **zip** que contiene todos los archivos " -"necesarios para instalar directamente su paquete. Todos los archivos en una " -"wheel son binarios, lo que significa que el código ya está compilado / " -"construido. Por lo tanto, estas son más rápidas de instalar, " -"particularmente si tiene un paquete que requiere pasos de construcción." +"La wheel (.whl) es su distribución binaria construida. Los **archivos " +"binarios** son los archivos de código fuente construidos / compilados. " +"Estos archivos están listos para ser instalados. Una wheel (**.whl**) es " +"un archivo **zip** que contiene todos los archivos necesarios para " +"instalar directamente su paquete. Todos los archivos en una wheel son " +"binarios, lo que significa que el código ya está compilado / construido. " +"Por lo tanto, estas son más rápidas de instalar, particularmente si tiene" +" un paquete que requiere pasos de construcción." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:240 msgid "" @@ -4933,17 +4976,17 @@ msgid "" " as **setup.cfg** or **pyproject.toml**. This distribution is already " "built so it's ready to install." msgstr "" -"La wheel no contiene ninguno de los archivos de configuración de su paquete " -"como **setup.cfg** o **pyproject.toml**. Esta distribución ya está construida " -"por lo que está lista para instalar." +"La wheel no contiene ninguno de los archivos de configuración de su " +"paquete como **setup.cfg** o **pyproject.toml**. Esta distribución ya " +"está construida por lo que está lista para instalar." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:244 msgid "" "Because it is built, the wheel file will be faster to install for pure " "Python projects and can lead to consistent installs across machines." msgstr "" -"Debido a que está construido, el archivo .whl será más rápido de instalar " -"para proyectos de Python puro y llevará a instalaciones consistentes " +"Debido a que está construido, el archivo .whl será más rápido de instalar" +" para proyectos de Python puro y llevará a instalaciones consistentes " #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:252 msgid "" @@ -4954,13 +4997,15 @@ msgid "" msgstr "" "Las wheels también son útiles en el caso de que un paquete necesite un " "archivo **setup.py** para admitir una construcción más compleja. En este " -"caso, debido a que los archivos en el paquete de wheel están preconstruidos, " -"el usuario que lo instala no tiene que preocuparse por inyecciones de código " -"malicioso cuando se instala." +"caso, debido a que los archivos en el paquete de wheel están " +"preconstruidos, el usuario que lo instala no tiene que preocuparse por " +"inyecciones de código malicioso cuando se instala." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:259 msgid "The filename of a wheel contains important metadata about your package." -msgstr "El nombre de archivo de una wheel contiene metadatos importantes sobre su paquete." +msgstr "" +"El nombre de archivo de una wheel contiene metadatos importantes sobre su" +" paquete." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:261 msgid "Example: **stravalib-1.1.0.post2-py3-none.whl**" @@ -4988,7 +5033,9 @@ msgstr "py3: admite Python 3.x" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:267 msgid "none: is not operating system specific (runs on windows, mac, linux)" -msgstr "none: no es específico del sistema operativo (se ejecuta en Windows, Mac, Linux)" +msgstr "" +"none: no es específico del sistema operativo (se ejecuta en Windows, Mac," +" Linux)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:268 msgid "any: runs on any computer processor / architecture" @@ -5014,10 +5061,11 @@ msgid "" "vs-flat-layout/) Both layouts have advantages for different groups of " "maintainers." msgstr "" -"Existen dos diseños diferentes que comúnmente verá dentro del ecosistema de " -"empaquetado de Python: [diseños src y flat](https://packaging.python.org/en/" -"latest/discussions/src-layout-vs-flat-layout/). Ambos diseños tienen ventajas " -"para diferentes grupos de mantenedores." +"Existen dos diseños diferentes que comúnmente verá dentro del ecosistema " +"de empaquetado de Python: [diseños src y " +"flat](https://packaging.python.org/en/latest/discussions/src-layout-vs-" +"flat-layout/). Ambos diseños tienen ventajas para diferentes grupos de " +"mantenedores." #: ../../package-structure-code/python-package-structure.md:8 msgid "" @@ -5027,22 +5075,25 @@ msgid "" "guide](https://packaging.python.org/en/latest/tutorials/packaging-" "projects/)." msgstr "" -"Le sugerimos, pero no requerimos, que use el diseño **src/** (discutido a " -"continuación) para crear su paquete de Python. Este diseño también se " -"recomienda en la [guía de empaquetado de PyPA](https://packaging.python.org/" -"en/latest/tutorials/packaging-projects/)." +"Le sugerimos, pero no requerimos, que use el diseño **src/** (discutido a" +" continuación) para crear su paquete de Python. Este diseño también se " +"recomienda en la [guía de empaquetado de " +"PyPA](https://packaging.python.org/en/latest/tutorials/packaging-" +"projects/)." #: ../../package-structure-code/python-package-structure.md:12 msgid "pyOpenSci will never require a specific package structure for peer review" -msgstr "pyOpenSci nunca requerirá una estructura de paquete específica para la revisión por pares" +msgstr "" +"pyOpenSci nunca requerirá una estructura de paquete específica para la " +"revisión por pares" #: ../../package-structure-code/python-package-structure.md:15 msgid "" "We understand that it would be tremendous effort for existing maintainers" " to move to a new layout." msgstr "" -"Entendemos que sería un esfuerzo tremendo para los mantenedores existentes " -"moverse a un nuevo diseño." +"Entendemos que sería un esfuerzo tremendo para los mantenedores " +"existentes moverse a un nuevo diseño." #: ../../package-structure-code/python-package-structure.md:18 msgid "" @@ -5051,14 +5102,16 @@ msgid "" "package has a simple build and might be open to moving to a more fail-" "proof approach." msgstr "" -"La descripción general en esta página presenta recomendaciones que creemos " -"que son las mejores para alguien que está comenzando con el empaquetado de " -"Python o para alguien cuyo paquete tiene una construcción simple y podría " -"estar abierto a moverse a un enfoque a prueba de fallos." +"La descripción general en esta página presenta recomendaciones que " +"creemos que son las mejores para alguien que está comenzando con el " +"empaquetado de Python o para alguien cuyo paquete tiene una construcción " +"simple y podría estar abierto a moverse a un enfoque a prueba de fallos." #: ../../package-structure-code/python-package-structure.md:23 msgid "An example of the **src/package** layout structure can be seen below." -msgstr "Un ejemplo de la estructura de diseño **src/package** se puede ver a continuación." +msgstr "" +"Un ejemplo de la estructura de diseño **src/package** se puede ver a " +"continuación." #: ../../package-structure-code/python-package-structure.md:45 msgid "Note the location of the following directories in the example above:" @@ -5070,10 +5123,10 @@ msgid "" "user-facing documentation website. In a **src/** layout docs/ are " "normally included at the same directory level of the **src/** folder." msgstr "" -"**docs/:** discutido en nuestro capítulo de documentación, este directorio " -"contiene el sitio web de documentación orientado al usuario. En un diseño " -"**src/**, los docs/ normalmente se incluyen en el mismo nivel de directorio " -"que la carpeta **src/**." +"**docs/:** discutido en nuestro capítulo de documentación, este " +"directorio contiene el sitio web de documentación orientado al usuario. " +"En un diseño **src/**, los docs/ normalmente se incluyen en el mismo " +"nivel de directorio que la carpeta **src/**." #: ../../package-structure-code/python-package-structure.md:48 msgid "" @@ -5081,17 +5134,17 @@ msgid "" "**src/** layout tests are normally included at the same directory level " "of the **src/** folder." msgstr "" -"**tests/** este directorio contiene las pruebas o tests para el código de su proyecto. " -"En un diseño **src/**, las pruebas o tests normalmente se incluyen en el " -"mismo nivel de directorio que la carpeta **src/**." +"**tests/** este directorio contiene las pruebas o tests para el código de" +" su proyecto. En un diseño **src/**, las pruebas o tests normalmente se " +"incluyen en el mismo nivel de directorio que la carpeta **src/**." #: ../../package-structure-code/python-package-structure.md:49 msgid "" "**src/package/**: this is the directory that contains the code for your " "Python project. \"Package\" is normally your project's name." msgstr "" -"**src/package/**: este es el directorio que contiene el código de su proyecto de Python. " -"\"Package\" es normalmente el nombre de su proyecto." +"**src/package/**: este es el directorio que contiene el código de su " +"proyecto de Python. \"Package\" es normalmente el nombre de su proyecto." #: ../../package-structure-code/python-package-structure.md:51 msgid "" @@ -5099,9 +5152,9 @@ msgid "" "files that pyOpenSci requires live in the root of your project directory." " These files include:" msgstr "" -"También en el ejemplo anterior, observe que todos los archivos de documentación " -"básicos que pyOpenSci requiere se encuentran en la raíz del directorio de su proyecto. " -"Estos archivos incluyen:" +"También en el ejemplo anterior, observe que todos los archivos de " +"documentación básicos que pyOpenSci requiere se encuentran en la raíz del" +" directorio de su proyecto. Estos archivos incluyen:" #: ../../package-structure-code/python-package-structure.md:55 msgid "CHANGELOG.md" @@ -5125,15 +5178,17 @@ msgstr "" #: ../../package-structure-code/python-package-structure.md:63 msgid "Click here to read about our packaging documentation requirements." -msgstr "Haga clic aquí para leer sobre nuestros requisitos de documentación de empaquetado." +msgstr "" +"Haga clic aquí para leer sobre nuestros requisitos de documentación de " +"empaquetado." #: ../../package-structure-code/python-package-structure.md:70 msgid "" "While we recommend the **src/** layout we also review the **flat** layout" " here. Both are used in the Python ecosystem." msgstr "" -"Aunque recomendamos el diseño **src/**, también revisamos el diseño **flat** aquí. " -"Ambos se utilizan en el ecosistema de Python." +"Aunque recomendamos el diseño **src/**, también revisamos el diseño " +"**flat** aquí. Ambos se utilizan en el ecosistema de Python." #: ../../package-structure-code/python-package-structure.md:72 msgid "Example scientific packages that use **src/package** layout" @@ -5173,11 +5228,11 @@ msgid "" "your package is installed." msgstr "" "El beneficio de usar el diseño **src/package**, particularmente si está " -"creando un nuevo paquete, es que asegura que las pruebas se ejecuten contra " -"la versión instalada de su paquete en lugar de los archivos en el directorio " -"de trabajo de su paquete. Si ejecuta sus pruebas en sus archivos en lugar de " -"la versión instalada, es posible que se pierda problemas que los usuarios " -"encuentran cuando su paquete está instalado." +"creando un nuevo paquete, es que asegura que las pruebas se ejecuten " +"contra la versión instalada de su paquete en lugar de los archivos en el " +"directorio de trabajo de su paquete. Si ejecuta sus pruebas en sus " +"archivos en lugar de la versión instalada, es posible que se pierda " +"problemas que los usuarios encuentran cuando su paquete está instalado." #: ../../package-structure-code/python-package-structure.md:91 msgid "" @@ -5186,18 +5241,18 @@ msgid "" "smaller which then places places a smaller storage burden on PyPI which " "has over 400,000 packages to support." msgstr "" -"Si `tests/` están fuera del directorio **src/package**, no se incluyen en la " -"rueda del paquete. Esto hace que el tamaño de su paquete sea ligeramente " -"más pequeño, lo que a su vez genera un almacenamiento más pequeño " -"en PyPI, que tiene más de 400,000 paquetes." +"Si `tests/` están fuera del directorio **src/package**, no se incluyen en" +" la rueda del paquete. Esto hace que el tamaño de su paquete sea " +"ligeramente más pequeño, lo que a su vez genera un almacenamiento más " +"pequeño en PyPI, que tiene más de 400,000 paquetes." #: ../../package-structure-code/python-package-structure.md:93 msgid "" "[Read more about reasons to use the **src/package** " "layout](https://hynek.me/articles/testing-packaging/)" msgstr "" -"[Lea más sobre las razones para usar el diseño" -" **src/package**](https://hynek.me/articles/testing-packaging/)" +"[Lea más sobre las razones para usar el diseño " +"**src/package**](https://hynek.me/articles/testing-packaging/)" #: ../../package-structure-code/python-package-structure.md:95 msgid "How Python discovers and prioritizes importing modules" @@ -5208,8 +5263,8 @@ msgid "" "By default, Python adds a module in your current working directory to the" " front of the Python module search path." msgstr "" -"De forma predeterminada, Python agrega un módulo en su directorio de trabajo " -"actual al principio de la ruta de búsqueda de módulos de Python." +"De forma predeterminada, Python agrega un módulo en su directorio de " +"trabajo actual al principio de la ruta de búsqueda de módulos de Python." #: ../../package-structure-code/python-package-structure.md:99 msgid "" @@ -5218,9 +5273,10 @@ msgid "" "discover `package/module.py` file before it discovers the installed " "package." msgstr "" -"Esto significa que si ejecuta sus pruebas en el directorio de trabajo de su " -"paquete, utilizando un diseño plano, `/package/module.py`, Python descubrirá " -"el archivo `package/module.py` antes de que descubra el paquete instalado." +"Esto significa que si ejecuta sus pruebas en el directorio de trabajo de " +"su paquete, utilizando un diseño plano, `/package/module.py`, Python " +"descubrirá el archivo `package/module.py` antes de que descubra el " +"paquete instalado." #: ../../package-structure-code/python-package-structure.md:101 msgid "" @@ -5229,10 +5285,10 @@ msgid "" "This means that when you import your package, Python will be forced to " "search the active environment (which has your package installed)." msgstr "" -"Sin embargo, si su paquete se encuentra en una estructura de directorio src/ " -"**src/package**, entonces no se agregará, por defecto, a la ruta de Python. " -"Esto significa que cuando importe su paquete, Python se verá obligado a buscar " -"en el entorno activo (que tiene su paquete instalado)." +"Sin embargo, si su paquete se encuentra en una estructura de directorio " +"src/ **src/package**, entonces no se agregará, por defecto, a la ruta de " +"Python. Esto significa que cuando importe su paquete, Python se verá " +"obligado a buscar en el entorno activo (que tiene su paquete instalado)." #: ../../package-structure-code/python-package-structure.md:103 msgid "" @@ -5240,9 +5296,9 @@ msgid "" "adjusted to ensure the priority is to use installed packages first (e.g. " "`PYTHONSAFEPATH`)." msgstr "" -"Nota: Las versiones de Python 3.11 y superiores tienen un ajuste de ruta que " -"se puede modificar para garantizar que la prioridad sea utilizar primero los " -"paquetes instalados (por ejemplo, `PYTHONSAFEPATH`)." +"Nota: Las versiones de Python 3.11 y superiores tienen un ajuste de ruta " +"que se puede modificar para garantizar que la prioridad sea utilizar " +"primero los paquetes instalados (por ejemplo, `PYTHONSAFEPATH`)." #: ../../package-structure-code/python-package-structure.md:106 msgid "Sometimes tests are needed in a distribution" @@ -5259,21 +5315,22 @@ msgid "" "`tests/` directory into the **src/package** directory (see example " "below)." msgstr "" -"No recomendamos incluir pruebas como parte de su rueda de paquete de forma " -"predeterminada. Sin embargo, no incluir pruebas en su distribución de paquete " -"hará que sea más difícil para las personas que no sean usted mismo probar si " -"su paquete funciona correctamente en su sistema. Si tiene un conjunto de pruebas " -"pequeño (archivos Python + datos) y cree que sus usuarios pueden querer ejecutar " -"pruebas localmente en sus sistemas, puede incluir pruebas moviendo el directorio " -"`tests/` al directorio **src/package** (ver ejemplo a continuación)." +"No recomendamos incluir pruebas como parte de su rueda de paquete de " +"forma predeterminada. Sin embargo, no incluir pruebas en su distribución " +"de paquete hará que sea más difícil para las personas que no sean usted " +"mismo probar si su paquete funciona correctamente en su sistema. Si tiene" +" un conjunto de pruebas pequeño (archivos Python + datos) y cree que sus " +"usuarios pueden querer ejecutar pruebas localmente en sus sistemas, puede" +" incluir pruebas moviendo el directorio `tests/` al directorio " +"**src/package** (ver ejemplo a continuación)." #: ../../package-structure-code/python-package-structure.md:117 msgid "" "Including the **tests/** directory in your **src/package** directory " "ensures that tests will be included in your package's wheel." msgstr "" -"Incluir el directorio **tests/** en su directorio **src/package** asegura que " -"las pruebas se incluirán en la rueda de su paquete." +"Incluir el directorio **tests/** en su directorio **src/package** asegura" +" que las pruebas se incluirán en la rueda de su paquete." #: ../../package-structure-code/python-package-structure.md:119 msgid "" @@ -5282,9 +5339,10 @@ msgid "" "distribution](https://docs.pytest.org/en/7.2.x/explanation/goodpractices.html#choosing-a" "-test-layout-import-rules)." msgstr "" -"Asegúrese de leer la [documentación de pytest para obtener más información " -"sobre cómo incluir pruebas en su distribución de paquete](https://docs.pytest.org/en/" -"7.2.x/explanation/goodpractices.html#choosing-a-test-layout-import-rules)." +"Asegúrese de leer la [documentación de pytest para obtener más " +"información sobre cómo incluir pruebas en su distribución de " +"paquete](https://docs.pytest.org/en/7.2.x/explanation/goodpractices.html#choosing-a" +"-test-layout-import-rules)." #: ../../package-structure-code/python-package-structure.md:121 msgid "Challenges with including tests and data in a package wheel" @@ -5294,7 +5352,8 @@ msgstr "Desafíos al incluir pruebas y datos en una rueda de paquete" msgid "" "Tests, especially when accompanied by test data can create a few small " "challenges including:" -msgstr "Los tests, especialmente cuando van acompañados de datos de prueba, " +msgstr "" +"Los tests, especialmente cuando van acompañados de datos de prueba, " "pueden crear algunos pequeños desafíos, incluyendo:" #: ../../package-structure-code/python-package-structure.md:126 @@ -5302,7 +5361,8 @@ msgid "" "Take up space in your distribution which will build up over time as " "storage space on PyPI" msgstr "" -"Ocupar espacio en su distribución, lo que se acumulará con el tiempo en PyPI" +"Ocupar espacio en su distribución, lo que se acumulará con el tiempo en " +"PyPI" #: ../../package-structure-code/python-package-structure.md:127 msgid "Large file sizes can also slow down package install." @@ -5313,8 +5373,8 @@ msgid "" "However, in some cases, particularly in the scientific Python ecosystems " "you may need to include tests." msgstr "" -"Sin embargo, en algunos casos, particularmente en los ecosistemas científicos " -"de Python, es posible que necesite incluir pruebas." +"Sin embargo, en algunos casos, particularmente en los ecosistemas " +"científicos de Python, es posible que necesite incluir pruebas." #: ../../package-structure-code/python-package-structure.md:132 msgid "**Don't include test suite datasets in your package**" @@ -5329,17 +5389,19 @@ msgid "" "the data when you (or a user) runs tests." msgstr "" "Si incluye sus pruebas en su distribución de paquete, le recomendamos " -"encarecidamente que no incluya datos en su directorio de pruebas. En su lugar, " -"aloje sus datos de prueba en un repositorio como Figshare o Zenodo. Utilice " -"una herramienta como [Pooch](https://www.fatiando.org/pooch/latest/) para " -"acceder a los datos cuando usted (o un usuario) ejecute pruebas." +"encarecidamente que no incluya datos en su directorio de pruebas. En su " +"lugar, aloje sus datos de prueba en un repositorio como Figshare o " +"Zenodo. Utilice una herramienta como " +"[Pooch](https://www.fatiando.org/pooch/latest/) para acceder a los datos " +"cuando usted (o un usuario) ejecute pruebas." #: ../../package-structure-code/python-package-structure.md:140 msgid "" "Check out the testing section of our guide for more information about " "tests." msgstr "" -"Consulte la sección de pruebas de nuestra guía para obtener más información sobre las pruebas." +"Consulte la sección de pruebas de nuestra guía para obtener más " +"información sobre las pruebas." #: ../../package-structure-code/python-package-structure.md:142 msgid "" @@ -5347,9 +5409,9 @@ msgid "" "found in the **src/package** directory, `tests/` and `docs/`are in the " "root directory." msgstr "" -"El diseño **src/package** es semánticamente más claro. El código siempre se " -"encuentra en el directorio **src/package**, `tests/` y `docs/` están en el " -"directorio raíz." +"El diseño **src/package** es semánticamente más claro. El código siempre " +"se encuentra en el directorio **src/package**, `tests/` y `docs/` están " +"en el directorio raíz." #: ../../package-structure-code/python-package-structure.md:146 msgid "" @@ -5360,12 +5422,12 @@ msgid "" "repositories like PyPI and Anaconda.org that have to deal with thousands " "of package uploads." msgstr "" -"Si las pruebas de su paquete requieren datos, le sugerimos que NO incluya " -"esos datos en su estructura de paquete. Discutiremos esto con más detalle en " -"un tutorial. Incluir datos en su estructura de paquete aumenta el tamaño de " -"los archivos de su distribución. Esto impone un peaje de mantenimiento en " -"repositorios como PyPI y Anaconda.org que tienen que lidiar con miles de " -"paquetes subidos." +"Si las pruebas de su paquete requieren datos, le sugerimos que NO incluya" +" esos datos en su estructura de paquete. Discutiremos esto con más " +"detalle en un tutorial. Incluir datos en su estructura de paquete aumenta" +" el tamaño de los archivos de su distribución. Esto impone un peaje de " +"mantenimiento en repositorios como PyPI y Anaconda.org que tienen que " +"lidiar con miles de paquetes subidos." #: ../../package-structure-code/python-package-structure.md:153 msgid "About the flat Python package layout" @@ -5373,7 +5435,9 @@ msgstr "Sobre el diseño plano de paquetes de Python" #: ../../package-structure-code/python-package-structure.md:155 msgid "Currently most scientific packages use the **flat-layout** given:" -msgstr "Actualmente, la mayoría de los paquetes científicos utilizan el **diseño plano** dado:" +msgstr "" +"Actualmente, la mayoría de los paquetes científicos utilizan el **diseño " +"plano** dado:" #: ../../package-structure-code/python-package-structure.md:157 msgid "" @@ -5381,9 +5445,9 @@ msgid "" "and people tend to look to other packages / maintainers that they respect" " for examples of how to build Python packages." msgstr "" -"Es el diseño más común en el ecosistema científico de Python " -"y las personas tienden a buscar otros paquetes / mantenedores que respetan " -"como ejemplos de cómo construir paquetes de Python." +"Es el diseño más común en el ecosistema científico de Python y las " +"personas tienden a buscar otros paquetes / mantenedores que respetan como" +" ejemplos de cómo construir paquetes de Python." #: ../../package-structure-code/python-package-structure.md:160 msgid "" @@ -5391,9 +5455,10 @@ msgid "" "builds with compilation steps. Many developers thus appreciate / are used" " to features of the flat layout." msgstr "" -"Muchas herramientas de Python dependen de herramientas en otros idiomas y/o " -"construcciones complejas con pasos de compilación. Por lo tanto, muchos " -"desarrolladores aprecian/están acostumbrados a las características del diseño plano." +"Muchas herramientas de Python dependen de herramientas en otros idiomas " +"y/o construcciones complejas con pasos de compilación. Por lo tanto, " +"muchos desarrolladores aprecian/están acostumbrados a las características" +" del diseño plano." #: ../../package-structure-code/python-package-structure.md:164 msgid "" @@ -5403,16 +5468,17 @@ msgid "" "move to a src/ layout](https://github.com/scikit-build/cmake-python-" "distributions/pull/145)" msgstr "" -"Aunque presentamos este diseño aquí en nuestra guía, sugerimos que aquellos " -"que recién comienzan con el empaquetado de Python comiencen con el diseño " -"src/package discutido anteriormente. Numerosos paquetes en el ecosistema " -"[han tenido que moverse a un diseño src/]" -"(https://github.com/scikit-build/cmake-python-" -"distributions/pull/145)" +"Aunque presentamos este diseño aquí en nuestra guía, sugerimos que " +"aquellos que recién comienzan con el empaquetado de Python comiencen con " +"el diseño src/package discutido anteriormente. Numerosos paquetes en el " +"ecosistema [han tenido que moverse a un diseño src/](https://github.com" +"/scikit-build/cmake-python-distributions/pull/145)" #: ../../package-structure-code/python-package-structure.md:169 msgid "Why most scientific Python packages do not use source" -msgstr "¿Por qué la mayoría de los paquetes científicos de Python no usan el código fuente?" +msgstr "" +"¿Por qué la mayoría de los paquetes científicos de Python no usan el " +"código fuente?" #: ../../package-structure-code/python-package-structure.md:172 msgid "" @@ -5421,10 +5487,10 @@ msgid "" "it. Moving from a flat layout to a **src/package** layout would come at a" " significant cost to maintainers." msgstr "" -"En la mayoría de los casos, las ventajas de usar el diseño **src/package** " -"para paquetes científicos más grandes que ya utilizan un enfoque plano no " -"merecen la pena. Pasar de un diseño plano a un diseño **src/package** " -"supondría un costo significativo para los mantenedores." +"En la mayoría de los casos, las ventajas de usar el diseño " +"**src/package** para paquetes científicos más grandes que ya utilizan un " +"enfoque plano no merecen la pena. Pasar de un diseño plano a un diseño " +"**src/package** supondría un costo significativo para los mantenedores." #: ../../package-structure-code/python-package-structure.md:177 msgid "" @@ -5433,9 +5499,9 @@ msgid "" "started with creating a package, that you consider using a " "**src/package** layout." msgstr "" -"Sin embargo, las ventajas de usar el diseño **src/package** para un principiante " -"son significativas. Por lo tanto, recomendamos que si está comenzando a crear un " -"paquete, considere usar un diseño **src/package**." +"Sin embargo, las ventajas de usar el diseño **src/package** para un " +"principiante son significativas. Por lo tanto, recomendamos que si está " +"comenzando a crear un paquete, considere usar un diseño **src/package**." #: ../../package-structure-code/python-package-structure.md:182 msgid "What does the flat layout structure look like?" @@ -5450,24 +5516,24 @@ msgid "" "The source code for your package lives in a directory with your package's" " name in the root of your directory" msgstr "" -"El código fuente de su paquete se encuentra en un directorio con el nombre de " -"su paquete en la raíz de su directorio" +"El código fuente de su paquete se encuentra en un directorio con el " +"nombre de su paquete en la raíz de su directorio" #: ../../package-structure-code/python-package-structure.md:188 msgid "" "Often the `tests/` directory also lives within that same `package` " "directory." msgstr "" -"A menudo, el directorio `tests/` también se encuentra dentro de ese mismo " -"directorio `package`." +"A menudo, el directorio `tests/` también se encuentra dentro de ese mismo" +" directorio `package`." #: ../../package-structure-code/python-package-structure.md:190 msgid "" "Below you can see the recommended structure of a scientific Python " "package using the flat layout." msgstr "" -"A continuación, puede ver la estructura recomendada de un paquete científico " -"de Python que utiliza el diseño plano." +"A continuación, puede ver la estructura recomendada de un paquete " +"científico de Python que utiliza el diseño plano." #: ../../package-structure-code/python-package-structure.md:212 msgid "Benefits of using the flat layout in your Python package" @@ -5478,15 +5544,16 @@ msgid "" "There are some benefits to the scientific community in using the flat " "layout." msgstr "" -"Existen algunos beneficios para la comunidad científica al utilizar el diseño plano." +"Existen algunos beneficios para la comunidad científica al utilizar el " +"diseño plano." #: ../../package-structure-code/python-package-structure.md:216 msgid "" "This structure has historically been used across the ecosystem and " "packages using it are unlikely to change." msgstr "" -"Esta estructura se ha utilizado históricamente en todo el ecosistema y es poco probable " -"que los paquetes que la utilizan cambien." +"Esta estructura se ha utilizado históricamente en todo el ecosistema y es" +" poco probable que los paquetes que la utilizan cambien." #: ../../package-structure-code/python-package-structure.md:218 msgid "" @@ -5496,11 +5563,11 @@ msgid "" "against the installed version of your package. Rather, you are working " "directly with the flat files." msgstr "" -"Puede importar el paquete directamente desde el directorio raíz. Para algunos, " -"esto está arraigado en sus respectivos flujos de trabajo. Sin embargo, para un " -"principiante, el peligro de hacer esto es que no está desarrollando y probando " -"contra la versión instalada de su paquete. En cambio, está trabajando directamente " -"con los archivos planos." +"Puede importar el paquete directamente desde el directorio raíz. Para " +"algunos, esto está arraigado en sus respectivos flujos de trabajo. Sin " +"embargo, para un principiante, el peligro de hacer esto es que no está " +"desarrollando y probando contra la versión instalada de su paquete. En " +"cambio, está trabajando directamente con los archivos planos." #: ../../package-structure-code/python-package-structure.md:224 msgid "Core scientific Python packages that use the flat layout" @@ -5540,9 +5607,9 @@ msgid "" "these packages to a different layout. The potential benefits of the " "source layout for these tools is not worth the maintenance investment." msgstr "" -"Sería un costo y una carga de mantenimiento significativos mover todos estos " -"paquetes a un diseño diferente. Los posibles beneficios del diseño src para " -"estas herramientas no valen la inversión en mantenimiento." +"Sería un costo y una carga de mantenimiento significativos mover todos " +"estos paquetes a un diseño diferente. Los posibles beneficios del diseño " +"src para estas herramientas no valen la inversión en mantenimiento." #: ../../package-structure-code/python-package-versions.md:1 msgid "Creating New Versions of Your Python Package" @@ -5610,7 +5677,7 @@ msgstr "" msgid "" "Consistent version increases following semver rules mean that values of " "your package version explain the extent of the changes made in the code " -"base from version to version. thus your package version numbers become " +"base from version to version. Thus your package version numbers become " "\"expressive\" in the same way that naming code variables well can [make " "code expressive](https://medium.com/@daniel.oliver.king/writing-" "expressive-code-b69ef7a5a2fa)." @@ -5774,7 +5841,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:107 msgid "" "Generally semantic release and version control system tools can be setup " -"to run automatically on GitHub using GitHub actions. This means that you " +"to run automatically on GitHub using GitHub Actions. This means that you " "can create a workflow where a GitHub release and associated new version " "tag is used to trigger an automated build that:" msgstr "" @@ -5795,7 +5862,7 @@ msgstr "" msgid "" "Bumping a package version refers to the step of increasing the package " "version after a set number of changes have been made to it. For example, " -"you might bump from version 0.8 to 0.9 of a package. or from 0.9 to 1.0." +"you might bump from version 0.8 to 0.9 of a package or from 0.9 to 1.0." msgstr "" #: ../../package-structure-code/python-package-versions.md:122 @@ -5905,7 +5972,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:173 msgid "" "When you (or your CI system) build your package, hatch checks the current" -" tag number for your package. if it has increased, it will update the " +" tag number for your package. If it has increased, it will update the " "**\\_version.py** file with the new value." msgstr "" @@ -6139,3 +6206,184 @@ msgid "" "The version number is manually updated in a configuration file such as " "`pyproject.toml` vs. in a package **\\_version.py** file." msgstr "" + +#~ msgid "" +#~ "The pre-commit workflow begins with " +#~ "you adding files that have changes " +#~ "to be staged in git. Next, you'd" +#~ " run git commit. when you run " +#~ "git commit, the pre-commit hooks " +#~ "will then run. In this example, " +#~ "Black, the code formatter and flake8," +#~ " a linter both run. If all of" +#~ " the files pass Black and flake8 " +#~ "checks, then your commit will be " +#~ "recorded. If they don't, the commit " +#~ "is canceled. You will have to fix" +#~ " any flake8 issues, and then re-" +#~ "add / stage the files to be " +#~ "committed. [_Image " +#~ "Source_](https://ljvmiranda921.github.io/notebook/2018/06/21" +#~ "/precommits-using-black-and-flake8/*)" +#~ msgstr "" + +#~ msgid "" +#~ "keep this comment - " +#~ "https://github.com/pyOpenSci/python-package-" +#~ "guide/pull/106#issuecomment-1844278487 in this file" +#~ " for now - jeremiah did a nice" +#~ " inventory of common shells and " +#~ "whether they need quotes or not. " +#~ "it's really comprehensive. but do we " +#~ "want it in the guide?? it's really" +#~ " useful for more advanced users i " +#~ "think." +#~ msgstr "" + +#~ msgid "needs to function properly." +#~ msgstr "" + +#~ msgid "" +#~ "requires if someone wants to develop " +#~ "/ work on improving your package " +#~ "locally or" +#~ msgstr "" + +#~ msgid "" +#~ "requires if a user wants to add" +#~ " additional functionality (that is not " +#~ "core) to your package" +#~ msgstr "" + +#~ msgid "" +#~ "Diagram showing a ven diagram with " +#~ "three sections representing the dependency " +#~ "groups listed above - docs feature " +#~ "and tests. In the center it says" +#~ " your-package and lists the core " +#~ "dependencies of that package seaborn and" +#~ " numpy. To the right are two " +#~ "arrows. The first shows the command " +#~ "python - m pip install your-" +#~ "package. it them shows how installing" +#~ " your package that way installs only" +#~ " the package and the two core " +#~ "dependencies into a users environment. " +#~ "Below is a second arrow with " +#~ "python -m pip install youPackage[tests]. " +#~ "This leads to an environment with " +#~ "both the package dependencies - your-" +#~ "package, seaborn and numpy and also " +#~ "the tests dependencies including pytest " +#~ "and pytest-cov" +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "Graphic with the title Python package" +#~ " repositories. Below it says Anything " +#~ "hosted on PyPI can be installed " +#~ "using pip install. Packaging hosted on" +#~ " a conda channel can be installed " +#~ "using conda install. Below that there" +#~ " are two rows. the top row says" +#~ " conda channels. next to it are " +#~ "three boxes one with conda-forge, " +#~ "community maintained; bioconda and then " +#~ "default - managed by the anaconda " +#~ "team. Below that there is a row" +#~ " that says PyPI servers. PyPI - " +#~ "anyone can publish to PyPI. and " +#~ "test PyPI. a testbed server for " +#~ "you to practice." +#~ msgstr "" + +#~ msgid "" +#~ "Here is an example of[ a package" +#~ " that has entry point " +#~ "script](https://github.com/pyOpenSci/update-web-" +#~ "metadata/blob/main/pyproject.toml#L60)s. Notice that " +#~ "there are several core scripts defined" +#~ " in that package that perform sets" +#~ " of tasks. pyOpenSci is using those" +#~ " scripts to process their metadata." +#~ msgstr "" + +#~ msgid "" +#~ "**Dynamic Fields:** if you have fields" +#~ " that are dynamically populated. One " +#~ "example of this is if you are " +#~ "using scm / version control based " +#~ "version with tools like `setuptooms_scm`, " +#~ "then you might use the dynamic " +#~ "field. such as version (using scm) " +#~ "**dynamic = [\"version\"]**" +#~ msgstr "" + +#~ msgid "" +#~ "Consistent version increases following semver" +#~ " rules mean that values of your " +#~ "package version explain the extent of" +#~ " the changes made in the code " +#~ "base from version to version. thus " +#~ "your package version numbers become " +#~ "\"expressive\" in the same way that " +#~ "naming code variables well can [make " +#~ "code expressive](https://medium.com/@daniel.oliver.king" +#~ "/writing-expressive-code-b69ef7a5a2fa)." +#~ msgstr "" + +#~ msgid "" +#~ "Generally semantic release and version " +#~ "control system tools can be setup " +#~ "to run automatically on GitHub using " +#~ "GitHub actions. This means that you " +#~ "can create a workflow where a " +#~ "GitHub release and associated new " +#~ "version tag is used to trigger an" +#~ " automated build that:" +#~ msgstr "" + +#~ msgid "" +#~ "Bumping a package version refers to " +#~ "the step of increasing the package " +#~ "version after a set number of " +#~ "changes have been made to it. For" +#~ " example, you might bump from version" +#~ " 0.8 to 0.9 of a package. or" +#~ " from 0.9 to 1.0." +#~ msgstr "" + +#~ msgid "" +#~ "When you (or your CI system) build" +#~ " your package, hatch checks the " +#~ "current tag number for your package. " +#~ "if it has increased, it will " +#~ "update the **\\_version.py** file with " +#~ "the new value." +#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/tests.po b/locales/es/LC_MESSAGES/tests.po index 07c076ae..b2cfc0c0 100644 --- a/locales/es/LC_MESSAGES/tests.po +++ b/locales/es/LC_MESSAGES/tests.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-14 09:22-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Felipe Moreno \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../tests/index.md:72 msgid "Intro" @@ -118,8 +118,9 @@ msgid "✨ Run tests online (using CI) ✨" msgstr "✨ Ejecuta pruebas en línea (usando CI) ✨" #: ../../tests/index.md:58 +#, fuzzy msgid "" -"Continuous integration platforms such as GitHub actions can be useful for" +"Continuous integration platforms such as GitHub Actions can be useful for" " running your tests across both different Python versions and different " "operating systems. Learn about setting up tests to run in Continuous " "Integration here." @@ -486,13 +487,11 @@ msgid "Other automation tools you'll see in the wild" msgstr "Otras herramientas de automatización que encontrarás" #: ../../tests/run-tests.md:125 +#, fuzzy msgid "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** is an " "automation tool that supports common steps such as building " "documentation, running tests across various versions of Python, and more." -" You can find [a nice overview of tox in the plasmaPy " -"documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" -"#using-tox)." msgstr "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** es una " "herramienta de automatización que admite pasos comunes como la " @@ -1098,12 +1097,14 @@ msgstr "" "localmente." #: ../../tests/tests-ci.md:22 -msgid "Example GitHub action that runs tests" +#, fuzzy +msgid "Example GitHub Actions that runs tests" msgstr "Ejemplo de acción de GitHub que ejecuta pruebas" #: ../../tests/tests-ci.md:24 +#, fuzzy msgid "" -"Below is an example GitHub action that runs tests using nox across both " +"Below is an example GitHub Actions that runs tests using nox across both " "Windows, Mac and Linux and on Python versions 3.9-3.11." msgstr "" "Abajo hay un ejemplo de una acción de GitHub que ejecuta pruebas " @@ -1228,9 +1229,10 @@ msgstr "" " mismo." #: ../../tests/write-tests.md:21 +#, fuzzy msgid "" "**Easier pull request reviews:** By running your tests in a CI framework " -"such as GitHub actions, each time you or a contributor makes a change to " +"such as GitHub Actions, each time you or a contributor makes a change to " "your code-base, you can catch issues and things that may have changed in " "your code base. This ensures that your software behaves the way you " "expect it to." diff --git a/locales/es/LC_MESSAGES/tutorials.po b/locales/es/LC_MESSAGES/tutorials.po index 9dbb7a74..f9e841a8 100644 --- a/locales/es/LC_MESSAGES/tutorials.po +++ b/locales/es/LC_MESSAGES/tutorials.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-28 08:42-0400\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../tutorials/add-license-coc.md:1 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" @@ -39,8 +39,9 @@ msgid "" " " "Learned about the core components that are useful to have in a `README` " "file." -msgstr "Aprendiste acerca de los componentes principales que son útiles de tener en " -"un archivo `README`." +msgstr "" +"Aprendiste acerca de los componentes principales que son útiles de tener " +"en un archivo `README`." #: ../../tutorials/add-license-coc.md:9 ../../tutorials/add-readme.md:10 msgid "Learning objectives" @@ -56,7 +57,8 @@ msgstr "En esta lección aprenderas:" msgid "" "How to select a license and add a `LICENSE` file to your package " "repository, with a focus on the GitHub interface." -msgstr "Como seleccionar una licencia y agregar un archivo `LICENSE` al " +msgstr "" +"Como seleccionar una licencia y agregar un archivo `LICENSE` al " "repositorio de tu paquete, con enfoque en la interface de Github" #: ../../tutorials/add-license-coc.md:15 @@ -67,8 +69,9 @@ msgstr "Como agregar un archivo `CODE_OF_CONDUCT` al repositorio de tu paquete" msgid "" "How you can use the Contributors Covenant website to add generic language" " as a starting place for your `CODE_OF_CONDUCT`." -msgstr "Como usar el sitio web de Contributors Covenant para agregar lenguage" -" genérico como punto de partida para tu `CODE_OF_CONDUCT`" +msgstr "" +"Como usar el sitio web de Contributors Covenant para agregar lenguage " +"genérico como punto de partida para tu `CODE_OF_CONDUCT`" #: ../../tutorials/add-license-coc.md:19 msgid "What is a license?" @@ -78,21 +81,26 @@ msgstr "¿Qué es una licencia?" msgid "" "A license contains legal language about how users can use and reuse your " "software. To set the `LICENSE` for your project, you:" -msgstr "Una licencia contiene lenguaje legal acerca de como los usuarios pueden " -"usar y reusar tu software. Para establecer un archivo `LICENSE` para tu" -" projecto, tu: " +msgstr "" +"Una licencia contiene lenguaje legal acerca de como los usuarios pueden " +"usar y reusar tu software. Para establecer un archivo `LICENSE` para tu " +"projecto, tu: " #: ../../tutorials/add-license-coc.md:23 +#, fuzzy msgid "" -"create a `LICENSE` file in your project directory that specifies the " -"license that you choose for your package and" -msgstr "creas un archivo `LICENSE` en el directorio de tu proyecto que " +"Create a `LICENSE` file in your project directory that specifies the " +"license that you choose for your package." +msgstr "" +"creas un archivo `LICENSE` en el directorio de tu proyecto que " "especifique la licencia que que elejiste para tu paquete y" #: ../../tutorials/add-license-coc.md:24 -msgid "reference that file in your `pyproject.toml` data where metadata are set." -msgstr "haces referencia a ese archivo en el `pyproject.toml` donde la metadata" -" es especificada" +#, fuzzy +msgid "Reference that file in your `pyproject.toml` data where metadata are set." +msgstr "" +"haces referencia a ese archivo en el `pyproject.toml` donde la metadata " +"es especificada" #: ../../tutorials/add-license-coc.md:26 msgid "" @@ -100,10 +108,11 @@ msgid "" " will be included in your package's metadata which is used to populate " "your package's PyPI landing page. The `LICENSE` is also used in your " "GitHub repository's landing page interface." -msgstr "Al incluir el archivo `LICENSE` en tu archivo `pyproject.toml`, la " -"`LICENSE` sera incluída en la metadata de tu paquete y esta es utilizada para" -" rellenar la página de entrada de tu paquete en PyPI. La `LICENSE` también es " -" utilizada en la página de entrada de tu repositorio de GitHub" +msgstr "" +"Al incluir el archivo `LICENSE` en tu archivo `pyproject.toml`, la " +"`LICENSE` sera incluída en la metadata de tu paquete y esta es utilizada " +"para rellenar la página de entrada de tu paquete en PyPI. La `LICENSE` " +"también es utilizada en la página de entrada de tu repositorio de GitHub" #: ../../tutorials/add-license-coc.md:28 msgid "What license should you use?" @@ -115,10 +124,12 @@ msgid "" "most commonly used licenses in the scientific Python ecosystem (MIT[^mit]" " and BSD-3[^bsd3]). If you are unsure, use MIT given it's the generally " "recommended license on [choosealicense.com](https://choosealicense.com/)." -msgstr "Nosotros sugerimos que uses una licencia permissiva que acomode otras" -" licencias comúnmente usadas en el ecosistema de Python científico (MIT[^mit]" -" and BSD-3[^bsd3]). Si tienes dudas, usa MIT dado que es la licencia" -" generalmente recomendada en [choosealicense.com](https://choosealicense.com/)" +msgstr "" +"Nosotros sugerimos que uses una licencia permissiva que acomode otras " +"licencias comúnmente usadas en el ecosistema de Python científico " +"(MIT[^mit] and BSD-3[^bsd3]). Si tienes dudas, usa MIT dado que es la " +"licencia generalmente recomendada en " +"[choosealicense.com](https://choosealicense.com/)" #: ../../tutorials/add-license-coc.md:33 msgid "Licenses for the scientific Python ecosystem" @@ -926,116 +937,231 @@ msgstr "" msgid "Discourages misuse of your package and associated code" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:1 ../../tutorials/intro.md:27 -#: ../../tutorials/setup-py-to-pyproject-toml.md:24 -msgid "Get to know Hatch" +#: ../../tutorials/get-to-know-hatch.md:1 +msgid "Get to Know Hatch" msgstr "" #: ../../tutorials/get-to-know-hatch.md:3 msgid "" -"Our Python packaging tutorials use the tool Hatch. In this tutorial, you " -"will install and get to know Hatch a bit more before starting to use it." +"Our Python packaging tutorials use the tool " +"[Hatch](https://hatch.pypa.io/latest/). While there are [many great " +"packaging tools](/package-structure-code/python-package-build-tools) out " +"there, we have selected Hatch because:" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:6 -msgid "Install Hatch" +#: ../../tutorials/get-to-know-hatch.md:8 +msgid "" +"It is an end-to-end tool that supports most of the steps required to " +"create a quality Python package. Beginners will have fewer tools to learn" +" if they use Hatch." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:11 +msgid "" +"It supports different build back-ends if you ever need to compile code in" +" other languages." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:7 +#: ../../tutorials/get-to-know-hatch.md:13 msgid "" -"To begin, install Hatch from the command line using " -"[pipx](https://pipx.pypa.io/stable/)" +"As a community, pyOpenSci has decided that Hatch is a user-friendly tool " +"that supports many different scientific Python use cases." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:14 +#: ../../tutorials/get-to-know-hatch.md:16 msgid "" -"Hatch can also be installed directly using `pip` or `conda`, but we " -"encourage you to use `pipx`. This is because `pipx` will ensure that your" -" package is available across all of your Python environments on your " -"computer rather than just in the environment that you install it into. If" -" you install hatch this way you will have to take care that the " -"environment it is installed into is activated for the command to work." +"In this tutorial, you will install and get to know Hatch a bit more " +"before starting to use it." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:19 +msgid "You need two things to successfully complete this tutorial:" msgstr "" #: ../../tutorials/get-to-know-hatch.md:21 +msgid "You need Python installed." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:22 +msgid "You need Hatch installed." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:25 msgid "" -"You can check that hatch is working properly by issuing a simple command " -"to get the version" +"If you don't already have Python installed on your computer, Hatch will " +"do it for you when you install Hatch." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:29 +msgid "Install Hatch" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:28 -msgid "Note the version numbers will likely be different" +#: ../../tutorials/get-to-know-hatch.md:31 +msgid "" +"To begin, follow the operating-system-specific instructions below to " +"install Hatch." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:30 -msgid "Configure hatch" +#: ../../tutorials/get-to-know-hatch.md +msgid "MAC" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:32 +#: ../../tutorials/get-to-know-hatch.md:38 msgid "" -"Once you have installed Hatch, you will want to customize the " -"configuration." +"Follow the instructions " +"[here](https://hatch.pypa.io/latest/install/#installers)." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:34 +#: ../../tutorials/get-to-know-hatch.md:40 msgid "" -"Hatch stores your configuration information in a [`config.toml` " +"Download the latest GUI installer for MAC [hatch-" +"universal.pkg](https://github.com/pypa/hatch/releases/latest/download" +"/hatch-universal.pkg)." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:41 +msgid "Run the installer and follow the setup instructions." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:42 +msgid "If your terminal is open, then restart it." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md +msgid "Windows" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:48 +msgid "" +"In your browser, download the correct `.msi` file for your system: " +"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch-x64.msi)" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:50 +msgid "Run your downloaded installer file and follow the on-screen instructions." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md +msgid "Linux" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:56 +msgid "" +"We suggest that you install Hatch using pipx on Linux. however, if you " +"prefer another method, check out the [Hatch installation " +"documentation](https://hatch.pypa.io/latest/install/) for other methods." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:70 +msgid "" +"Hatch can also be installed directly using " +"[pip](https://hatch.pypa.io/latest/install/#pip) or " +"[conda](https://hatch.pypa.io/latest/install/#conda). We encourage you to" +" follow the instructions above because we have found that the Hatch " +"installers for Windows and Mac are the easiest and most efficient." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:74 +msgid "" +"Our Linux users have found success installing Hatch with pipx if they " +"already use apt install." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:77 +msgid "" +"Both approaches (using a graphical installer on Windows/Mac and pipx) " +"ensure that you have Hatch installed globally. A global install means " +"that Hatch is available across all of your Python environments on your " +"computer." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:82 +msgid "Check that hatch installed correctly" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:84 +msgid "" +"Once you have completed the installation instructions above, you can open" +" your terminal, and make sure that Hatch installed correctly using the " +"command below:" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:92 +msgid "" +"*Note the version number output of `hatch --version` will likely be " +"different from the output above in this tutorial.*" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:95 +msgid "Configure Hatch" +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:97 +msgid "" +"Once you have installed Hatch, you can customize its configuration. This " +"includes setting the default name and setup for every package you create." +" While this step is not required, we suggest that you do it." +msgstr "" + +#: ../../tutorials/get-to-know-hatch.md:101 +msgid "" +"Hatch stores your configuration in a [`config.toml` " "file](https://hatch.pypa.io/latest/config/project-templates/)." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:36 +#: ../../tutorials/get-to-know-hatch.md:103 msgid "" "While you can update the `config.toml` file through the command line, it " -"might be easier to look at it and update it in a text editor if you are " +"might be easier to look at and update it in a text editor if you are " "using it for the first time." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:39 -msgid "Step 1: Open and edit your `config.toml` file" +#: ../../tutorials/get-to-know-hatch.md:107 +msgid "Step 1: Open and Edit Your `config.toml` File" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:41 +#: ../../tutorials/get-to-know-hatch.md:109 msgid "" "To open the config file in your file browser, run the following command " "in your shell:" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:43 +#: ../../tutorials/get-to-know-hatch.md:112 msgid "`hatch config explore`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:45 +#: ../../tutorials/get-to-know-hatch.md:114 msgid "" -"This will open up a directory window that will allow you to double click " -"on the file and open it in your favorite text editor." +"This will open up a directory window that allows you to double-click on " +"the file and open it in your favorite text editor." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:47 +#: ../../tutorials/get-to-know-hatch.md:117 msgid "" "You can also retrieve the location of the Hatch config file by running " "the following command in your shell:" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:54 +#: ../../tutorials/get-to-know-hatch.md:125 msgid "Step 2 - update your email and name" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:56 +#: ../../tutorials/get-to-know-hatch.md:127 msgid "" "Once the file is open, update the [template] table of the `config.toml` " "file with your name and email. This information will be used in any " "`pyproject.toml` metadata files that you create using Hatch." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:64 +#: ../../tutorials/get-to-know-hatch.md:137 msgid "Step 3" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:66 +#: ../../tutorials/get-to-know-hatch.md:139 msgid "Next, set tests to false in the `[template.plugins.default]` table." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:68 +#: ../../tutorials/get-to-know-hatch.md:141 msgid "" "While tests are important, setting the tests configuration in Hatch to " "`true` will create a more complex `pyproject.toml` file. You won't need " @@ -1043,11 +1169,11 @@ msgid "" " introduce it in later tutorials." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:73 +#: ../../tutorials/get-to-know-hatch.md:146 msgid "Your `config.toml` file should look something like the one below." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:111 +#: ../../tutorials/get-to-know-hatch.md:184 msgid "" "Also notice that the default license option is MIT. While we will discuss" " license in more detail in a later lesson, the MIT license is the " @@ -1056,11 +1182,11 @@ msgid "" "use it for this tutorial series." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:116 +#: ../../tutorials/get-to-know-hatch.md:190 msgid "You are of course welcome to select another license." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:118 +#: ../../tutorials/get-to-know-hatch.md:192 #: ../../tutorials/installable-code.md:22 #: ../../tutorials/installable-code.md:411 #: ../../tutorials/installable-code.md:502 ../../tutorials/intro.md:226 @@ -1069,84 +1195,84 @@ msgstr "" msgid "Todo" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:119 +#: ../../tutorials/get-to-know-hatch.md:193 msgid "" "I think we'd need the SPDX license options here if they want to chose " "bsd-3 for instance" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:122 +#: ../../tutorials/get-to-know-hatch.md:196 msgid "Step 4: Close the config file and run `hatch config show`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:124 +#: ../../tutorials/get-to-know-hatch.md:198 msgid "" "Once you have completed the steps above run the following command in your" " shell." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:126 +#: ../../tutorials/get-to-know-hatch.md:200 msgid "`hatch config show`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:128 +#: ../../tutorials/get-to-know-hatch.md:202 msgid "" "`hatch config show` will print out the contents of your `config.toml` " -"file in your shell. look at the values and ensure that your name, email " +"file in your shell. Look at the values and ensure that your name, email " "is set. Also make sure that `tests=false`." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:130 +#: ../../tutorials/get-to-know-hatch.md:206 msgid "Hatch features" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:132 +#: ../../tutorials/get-to-know-hatch.md:208 msgid "" "Hatch offers a suite of features that will make creating, publishing and " "maintaining your Python package easier." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:135 +#: ../../tutorials/get-to-know-hatch.md:211 msgid "Comparison to other tools" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:137 +#: ../../tutorials/get-to-know-hatch.md:213 msgid "" "[We compared Hatch to several of the other popular packaging tools in the" " ecosystem including flit, pdm and poetry. Learn more here](package-" "features)" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:140 +#: ../../tutorials/get-to-know-hatch.md:216 msgid "[More on Hatch here](hatch)" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:142 +#: ../../tutorials/get-to-know-hatch.md:218 msgid "A few features that Hatch offers" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:145 +#: ../../tutorials/get-to-know-hatch.md:220 msgid "" -"it will convert metadata stored in a `setup.py` or `setup.cfg` file to a " +"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:147 +#: ../../tutorials/get-to-know-hatch.md:222 msgid "" "It will help you by storing configuration information for publishing to " "PyPI after you've entered it once." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:149 +#: ../../tutorials/get-to-know-hatch.md:224 msgid "Use `hatch -h` to see all of the available commands." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:152 +#: ../../tutorials/get-to-know-hatch.md:226 msgid "What's next" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:154 +#: ../../tutorials/get-to-know-hatch.md:228 msgid "" "In the next lesson you'll learn how to package and make your code " "installable using Hatch." @@ -1196,7 +1322,7 @@ msgstr "" msgid "" "ADD: note about what makes something \"package worthy\", with a common " "misconception being that a package should be production-ready code that's" -" valuable to a broad audience. this may not be a pervasive misconception " +" valuable to a broad audience. This may not be a pervasive misconception " "in Python, but a quick break-out with an explanation of what a package " "can consist of would be helpful." msgstr "" @@ -1333,7 +1459,7 @@ msgid "An `__init__.py` file in your code directory." msgstr "" #: ../../tutorials/installable-code.md:83 -msgid "The directory structure you’ll create in this lesson will look like this:" +msgid "The directory structure you'll create in this lesson will look like this:" msgstr "" #: ../../tutorials/installable-code.md:95 @@ -1407,7 +1533,7 @@ msgstr "" #: ../../tutorials/installable-code.md:121 msgid "" -"Where you define your project’s metadata (including its name, authors, " +"Where you define your project's metadata (including its name, authors, " "license, etc)" msgstr "" @@ -1632,7 +1758,7 @@ msgstr "" #: ../../tutorials/installable-code.md:282 msgid "" -"If you aren’t familiar with docstrings or typing yet, that is ok. You can" +"If you aren't familiar with docstrings or typing yet, that is ok. You can" " review [this page in the pyOpenSci packaging " "guide](https://www.pyopensci.org/python-package-guide/documentation" "/write-user-documentation/document-your-code-api-docstrings.html) for an " @@ -1799,7 +1925,7 @@ msgstr "" #: ../../tutorials/installable-code.md:482 msgid "" "Once you have your project metadata in the pyproject.toml file, you will " -"rarely update it. In the next lesson you’ll add more metadata and " +"rarely update it. In the next lesson you'll add more metadata and " "structure to this file." msgstr "" @@ -2051,6 +2177,10 @@ msgstr "" msgid "[epydoc](https://epydoc.sourceforge.net/epytext.html)" msgstr "" +#: ../../tutorials/intro.md:27 ../../tutorials/setup-py-to-pyproject-toml.md:24 +msgid "Get to know Hatch" +msgstr "" + #: ../../tutorials/intro.md:27 msgid "Python Packaging Tutorial Setup" msgstr "" @@ -2760,8 +2890,8 @@ msgid "" "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 " +"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." @@ -2932,7 +3062,7 @@ msgstr "" msgid "" "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 " +"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." @@ -3280,7 +3410,7 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:279 msgid "" "There is currently a small bug in Grayskull where it doesn't populate the" -" home: element of the recipe. if you don't include this, [you will " +" home: element of the recipe. If you don't include this, [you will " "receive an error message](https://github.com/conda-forge/staged-" "recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" " linter bot." @@ -3828,8 +3958,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:60 msgid "" "In a future lesson, you will learn how to create an automated GitHub " -"action workflow that publishes an updated version of your package to PyPI" -" every time you create a GitHub release." +"Actions workflow that publishes an updated version of your package to " +"PyPI every time you create a GitHub release." msgstr "" #: ../../tutorials/publish-pypi.md:64 @@ -4366,10 +4496,10 @@ msgstr "" #: ../../tutorials/publish-pypi.md:363 msgid "" "You can also create an automated publication workflow on GitHub using " -"GitHub actions. This is a great way to make the publication process " +"GitHub Actions. This is a great way to make the publication process " "easier and it also supports a growing maintainer team. In this case we " "suggest you don't worry about the token and instead setup a specific " -"GitHub action that publishes your package when you make a release. You " +"GitHub Actions that publishes your package when you make a release. You " "can then create a \"trusted publisher\" workflow on PyPI." msgstr "" @@ -4559,7 +4689,7 @@ msgstr "" #: ../../tutorials/pyproject-toml.md:43 msgid "" "When you are adding classifiers to the **[project]** table, only use " -"valid values from [PyPI’s classifier " +"valid values from [PyPI's classifier " "page](https://PyPI.org/classifiers/). An invalid value here will raise an" " error when you build and publish your package on PyPI." msgstr "" @@ -5428,3 +5558,215 @@ msgid "" "existing functionality remains intact. Run any pre-existing tests to " "verify that everything still works as expected." msgstr "" + +#~ msgid "" +#~ "Our Python packaging tutorials use the" +#~ " tool Hatch. In this tutorial, you" +#~ " will install and get to know " +#~ "Hatch a bit more before starting " +#~ "to use it." +#~ msgstr "" + +#~ msgid "" +#~ "To begin, install Hatch from the " +#~ "command line using " +#~ "[pipx](https://pipx.pypa.io/stable/)" +#~ msgstr "" + +#~ msgid "" +#~ "Hatch can also be installed directly " +#~ "using `pip` or `conda`, but we " +#~ "encourage you to use `pipx`. This " +#~ "is because `pipx` will ensure that " +#~ "your package is available across all " +#~ "of your Python environments on your " +#~ "computer rather than just in the " +#~ "environment that you install it into." +#~ " If you install hatch this way " +#~ "you will have to take care that" +#~ " the environment it is installed into" +#~ " is activated for the command to " +#~ "work." +#~ msgstr "" + +#~ msgid "" +#~ "You can check that hatch is " +#~ "working properly by issuing a simple " +#~ "command to get the version" +#~ msgstr "" + +#~ msgid "Note the version numbers will likely be different" +#~ msgstr "" + +#~ msgid "Configure hatch" +#~ msgstr "" + +#~ msgid "" +#~ "Once you have installed Hatch, you " +#~ "will want to customize the " +#~ "configuration." +#~ msgstr "" + +#~ msgid "" +#~ "Hatch stores your configuration information" +#~ " in a [`config.toml` " +#~ "file](https://hatch.pypa.io/latest/config/project-templates/)." +#~ msgstr "" + +#~ msgid "" +#~ "While you can update the `config.toml`" +#~ " file through the command line, it" +#~ " might be easier to look at it" +#~ " and update it in a text editor" +#~ " if you are using it for the" +#~ " first time." +#~ msgstr "" + +#~ msgid "Step 1: Open and edit your `config.toml` file" +#~ msgstr "" + +#~ msgid "" +#~ "This will open up a directory " +#~ "window that will allow you to " +#~ "double click on the file and open" +#~ " it in your favorite text editor." +#~ msgstr "" + +#~ msgid "" +#~ "`hatch config show` will print out " +#~ "the contents of your `config.toml` file" +#~ " in your shell. look at the " +#~ "values and ensure that your name, " +#~ "email is set. Also make sure that" +#~ " `tests=false`." +#~ msgstr "" + +#~ msgid "" +#~ "it will convert metadata stored in " +#~ "a `setup.py` or `setup.cfg` file to " +#~ "a pyproject.toml file for you (see " +#~ "[Migrating setup.py to pyproject.toml using" +#~ " Hatch](setup-py-to-pyproject-toml.md " +#~ "))" +#~ msgstr "" + +#~ msgid "" +#~ "ADD: note about what makes something " +#~ "\"package worthy\", with a common " +#~ "misconception being that a package " +#~ "should be production-ready code that's" +#~ " valuable to a broad audience. this" +#~ " may not be a pervasive misconception" +#~ " in Python, but a quick break-" +#~ "out with an explanation of what a" +#~ " package can consist of would be " +#~ "helpful." +#~ msgstr "" + +#~ msgid "" +#~ "The directory structure you’ll create in" +#~ " this lesson will look like this:" +#~ msgstr "" + +#~ msgid "" +#~ "Where you define your project’s metadata" +#~ " (including its name, authors, license, " +#~ "etc)" +#~ msgstr "" + +#~ msgid "" +#~ "If you aren’t familiar with docstrings" +#~ " or typing yet, that is ok. You" +#~ " can review [this page in the " +#~ "pyOpenSci packaging guide](https://www.pyopensci.org" +#~ "/python-package-guide/documentation/write-user-" +#~ "documentation/document-your-code-api-" +#~ "docstrings.html) for an overview of both" +#~ " topics." +#~ msgstr "" + +#~ msgid "" +#~ "Once you have your project metadata " +#~ "in the pyproject.toml file, you will " +#~ "rarely update it. In the next " +#~ "lesson you’ll add more metadata and " +#~ "structure to this file." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "There is currently a small bug in" +#~ " Grayskull where it doesn't populate " +#~ "the home: element of the recipe. " +#~ "if you don't include this, [you " +#~ "will receive an error " +#~ "message](https://github.com/conda-forge/staged-" +#~ "recipes/pull/25173#issuecomment-1917916528) from the " +#~ "friendly conda-forge linter bot." +#~ msgstr "" + +#~ msgid "" +#~ "In a future lesson, you will learn" +#~ " how to create an automated GitHub" +#~ " action workflow that publishes an " +#~ "updated version of your package to " +#~ "PyPI every time you create a " +#~ "GitHub release." +#~ msgstr "" + +#~ msgid "" +#~ "You can also create an automated " +#~ "publication workflow on GitHub using " +#~ "GitHub actions. This is a great " +#~ "way to make the publication process " +#~ "easier and it also supports a " +#~ "growing maintainer team. In this case" +#~ " we suggest you don't worry about " +#~ "the token and instead setup a " +#~ "specific GitHub action that publishes " +#~ "your package when you make a " +#~ "release. You can then create a " +#~ "\"trusted publisher\" workflow on PyPI." +#~ msgstr "" + +#~ msgid "" +#~ "When you are adding classifiers to " +#~ "the **[project]** table, only use valid" +#~ " values from [PyPI’s classifier " +#~ "page](https://PyPI.org/classifiers/). An invalid " +#~ "value here will raise an error " +#~ "when you build and publish your " +#~ "package on PyPI." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/CONTRIBUTING.po b/locales/ja/LC_MESSAGES/CONTRIBUTING.po index 16c831c9..e71205f1 100644 --- a/locales/ja/LC_MESSAGES/CONTRIBUTING.po +++ b/locales/ja/LC_MESSAGES/CONTRIBUTING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../CONTRIBUTING.md:4 msgid "Contributing to the Python Packaging Guide" @@ -119,27 +119,33 @@ msgstr "" #: ../../CONTRIBUTING.md:35 msgid "" "Independently of the approach you choose, the first step is to fork the " -"Python Packaging Guide repository into your personal GitHub space. To " -"\"fork\" a repository in GitHub means to create a copy of the main " -"repository, or repo, that you have complete control over and can modify " -"as you see fit." +"Python Packaging Guide repository into your personal GitHub space. You " +"can do this by clicking the \"Fork\" button in the top right corner of " +"the repository page." msgstr "" -#: ../../CONTRIBUTING.md:37 +#: ../../CONTRIBUTING.md:38 +msgid "" +"[Learn more: Fork and Clone GitHub " +"Repos](https://datascienceskills.org/lessons/git-github/git-intro/3-fork-" +"clone/) is a good resource to learn more about forking." +msgstr "" + +#: ../../CONTRIBUTING.md:40 msgid "To fork a repo," msgstr "" -#: ../../CONTRIBUTING.md:39 +#: ../../CONTRIBUTING.md:42 msgid "Make sure you are logged into GitHub." msgstr "" -#: ../../CONTRIBUTING.md:41 +#: ../../CONTRIBUTING.md:44 msgid "" "Go to the repo you would like to fork, in this case the [Python Packaging" " Guide](https://www.github.com/pyopensci/python-package-guide) repo." msgstr "" -#: ../../CONTRIBUTING.md:43 +#: ../../CONTRIBUTING.md:46 msgid "" "In the top right-hand corner of the page there is a 'Fork' button. Click " "that button. You will be brought to a new page where you will 'Create a " @@ -149,173 +155,445 @@ msgid "" "is your GitHub username." msgstr "" -#: ../../CONTRIBUTING.md:47 +#: ../../CONTRIBUTING.md:51 msgid "Contributing via the GitHub website" msgstr "" -#: ../../CONTRIBUTING.md:49 +#: ../../CONTRIBUTING.md:53 msgid "How to edit a MarkDown file" msgstr "" -#: ../../CONTRIBUTING.md:51 +#: ../../CONTRIBUTING.md:55 msgid "" -"*__TODO__: This section should show how to use the GitHub interface to " -"edit and previewing a Markdown file.*" +"The Python Packaging Guide is written in myST, a variant of MarkDown. You" +" can edit the files directly in the GitHub website. To do so, navigate to" +" the file you want to edit and click the pencil icon in the top right " +"corner of the file." msgstr "" -#: ../../CONTRIBUTING.md:53 +#: ../../CONTRIBUTING.md:58 +msgid "Edit button in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:64 +msgid "" +"An image showing how to edit a file in GitHub. The pencil icon is " +"highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:66 +msgid "Edit file in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:72 +msgid "" +"An image showing when a file is being edited in GitHub. The file content " +"is displayed in a text editor." +msgstr "" + +#: ../../CONTRIBUTING.md:75 +msgid "To preview your changes, click the \"Preview changes\" tab." +msgstr "" + +#: ../../CONTRIBUTING.md:77 +msgid "Preview changes in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:83 +msgid "" +"An image showing how to preview changes in GitHub. The file content is " +"displayed in a text editor. The preview changes tab is highlighted with a" +" red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:86 msgid "How to commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:55 +#: ../../CONTRIBUTING.md:88 msgid "" -"*__TODO__: This section should show how to commit changes via the GitHub " -"interface.*" +"When you are done editing the file, scroll down to the bottom of the " +"page. You will see a section called \"Commit changes\". Here you can " +"write a title and a description for your changes. Make sure to write a " +"clear and concise title that describes the changes you made." +msgstr "" + +#: ../../CONTRIBUTING.md:91 +msgid "Commit changes in GitHub" msgstr "" -#: ../../CONTRIBUTING.md:57 +#: ../../CONTRIBUTING.md:97 +msgid "" +"An image showing how to commit changes in GitHub. The commit message is " +"displayed in a text editor. The commit changes section is highlighted " +"with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:100 +msgid "" +"After writing your commit message, click the \"Commit changes\" button to" +" save your changes." +msgstr "" + +#: ../../CONTRIBUTING.md:102 msgid "Contributing locally on your computer" msgstr "" -#: ../../CONTRIBUTING.md:59 +#: ../../CONTRIBUTING.md:104 msgid "Clone your forked repository" msgstr "" -#: ../../CONTRIBUTING.md:61 +#: ../../CONTRIBUTING.md:106 +msgid "" +"To clone your forked repository to your computer, you need to copy the " +"URL of your forked repository and run the following command in your " +"terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:111 msgid "" -"*__TODO__: This section should show how to clone a repository from GitHub" -" into your computer.*" +"Replace `` with the URL of your forked repository. You can find the " +"URL by clicking the green \"Code\" button on your forked repository page." +msgstr "" + +#: ../../CONTRIBUTING.md:113 +msgid "Clone repository in GitHub" msgstr "" -#: ../../CONTRIBUTING.md:63 +#: ../../CONTRIBUTING.md:119 +msgid "" +"An image showing how to clone a repository in GitHub. The URL of the " +"repository is displayed in a text editor. The code button is highlighted " +"with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:122 msgid "Create a new branch" msgstr "" -#: ../../CONTRIBUTING.md:65 -msgid "*__TODO__: This section should show how to create a new branch.*" +#: ../../CONTRIBUTING.md:124 +msgid "" +"Before making any changes, you should create a new branch to work on. " +"This will help keep your changes separate from the main branch and make " +"it easier to submit a pull request." msgstr "" -#: ../../CONTRIBUTING.md:67 +#: ../../CONTRIBUTING.md:126 +msgid "To create a new branch, run the following command in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:132 msgid "Create a virtual environment" msgstr "" -#: ../../CONTRIBUTING.md:69 +#: ../../CONTRIBUTING.md:134 msgid "" -"*__TODO__: This section should show how to create a virtual environment " -"using venv.*" +"To build the guide locally, you need to create a virtual environment and " +"install the dependencies. You can do this by running the following " +"commands in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:136 +msgid "**On Windows**:" +msgstr "" + +#: ../../CONTRIBUTING.md:142 +msgid "**On MacOS and Linux**:" msgstr "" -#: ../../CONTRIBUTING.md:71 +#: ../../CONTRIBUTING.md:148 msgid "Install the development dependencies" msgstr "" -#: ../../CONTRIBUTING.md:73 +#: ../../CONTRIBUTING.md:150 msgid "" -"*__TODO__: This section should show how to install the development " -"dependencies defined in pyproject.toml.*" +"To install the development dependencies, run the following command in " +"your terminal:" msgstr "" -#: ../../CONTRIBUTING.md:75 +#: ../../CONTRIBUTING.md:156 msgid "Commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:77 +#: ../../CONTRIBUTING.md:158 msgid "" -"*__TODO__: This section should describe how to commit from the command " -"line.*" +"After making your changes, you need to commit them to your local " +"repository. To do this, run the following commands in your terminal:" msgstr "" -#: ../../CONTRIBUTING.md:79 +#: ../../CONTRIBUTING.md:160 +msgid "To see the changes you made:" +msgstr "" + +#: ../../CONTRIBUTING.md:164 +msgid "To add the changes to the staging area:" +msgstr "" + +#: ../../CONTRIBUTING.md:168 +msgid "To commit the changes:" +msgstr "" + +#: ../../CONTRIBUTING.md:172 +msgid "" +"Replace `\"Your commit message here\"` with a clear and concise message " +"that describes the changes you made." +msgstr "" + +#: ../../CONTRIBUTING.md:174 msgid "How to build the guide locally" msgstr "" -#: ../../CONTRIBUTING.md:81 +#: ../../CONTRIBUTING.md:176 msgid "" -"*__TODO__: This section should describe the different sessions in nox " -"related to building the docs: docs, docs-test, docs-live. It should also " -"show how to see the guide built locally, by opening the right file in the" -" browser or using the live version from docs-live*" +"To build the guide locally, you can use the `nox` command. This will run " +"the default `nox` session, which builds the guide and opens it in your " +"browser." msgstr "" -#: ../../CONTRIBUTING.md:83 +#: ../../CONTRIBUTING.md:178 +msgid "" +"To see the different sessions available, you can run the following " +"command in your terminal:" +msgstr "" + +#: ../../CONTRIBUTING.md:183 +msgid "" +"There are different sessions in nox related to building the docs: `docs`," +" `docs-test`, `docs-live`. You can run them by specifying the session " +"name after the `nox` command." +msgstr "" + +#: ../../CONTRIBUTING.md:185 +msgid "`docs`: this session builds the guide and opens it in your browser." +msgstr "" + +#: ../../CONTRIBUTING.md:189 +msgid "" +"To see the guide built locally, open the file `_build/html/index.html` in" +" your browser." +msgstr "" + +#: ../../CONTRIBUTING.md:191 +msgid "`docs-test`: this session runs the tests for the guide." +msgstr "" + +#: ../../CONTRIBUTING.md:195 +msgid "" +"If the tests fail, you will see an error message in your terminal. You " +"need to fix the errors before submitting your pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:197 +msgid "" +"`docs-live`: this session builds the guide and opens it in your browser " +"with live reloading." +msgstr "" + +#: ../../CONTRIBUTING.md:201 +msgid "" +"open the local version of the guide in your browser at ``localhost`` " +"shown in the terminal." +msgstr "" + +#: ../../CONTRIBUTING.md:203 msgid "Before you submit your pull request" msgstr "" -#: ../../CONTRIBUTING.md:85 +#: ../../CONTRIBUTING.md:205 +msgid "" +"Before submitting your pull request, make sure to run the tests and check" +" the formatting of your code." +msgstr "" + +#: ../../CONTRIBUTING.md:210 msgid "" -"*__TODO__: This section should describe what steps a user should follow " -"before submitting the pull request: build the docs, verify your changes " -"look correct, etc.*" +"If the tests fail, you will see an error message in your terminal. You " +"need to fix the errors before submitting your pull request. Also make " +"sure to check the formatting of your documentation by building the docs " +"locally and checking that your changes look correct." msgstr "" -#: ../../CONTRIBUTING.md:87 +#: ../../CONTRIBUTING.md:214 msgid "Submitting a pull request with your contribution" msgstr "" -#: ../../CONTRIBUTING.md:89 +#: ../../CONTRIBUTING.md:216 msgid "How to make a pull request" msgstr "" -#: ../../CONTRIBUTING.md:91 +#: ../../CONTRIBUTING.md:218 +msgid "" +"To open a pull request on GitHub, navigate to the main page of your " +"forked repository and click on the \"Pull requests\" tab." +msgstr "" + +#: ../../CONTRIBUTING.md:220 +msgid "Pull requests tab in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:226 msgid "" -"*__TODO__: This section should describe how to make a pull request in " -"GitHub.*" +"An image showing how to navigate to the pull requests tab in GitHub. The " +"pull requests tab is highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:229 +msgid "Click on the \"New pull request\" button." +msgstr "" + +#: ../../CONTRIBUTING.md:231 +msgid "New pull request button in GitHub" msgstr "" -#: ../../CONTRIBUTING.md:93 +#: ../../CONTRIBUTING.md:237 +msgid "" +"An image showing how to create a new pull request in GitHub. The new pull" +" request button is highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:240 +msgid "" +"Write a clear and concise title and description for your pull request. " +"Make sure to describe the changes you made and why they are necessary." +msgstr "" + +#: ../../CONTRIBUTING.md:242 msgid "What happens when you submit a pull request (CI/CD)" msgstr "" -#: ../../CONTRIBUTING.md:95 +#: ../../CONTRIBUTING.md:244 msgid "" -"*__TODO__: This section should describe how to see the results of the " -"CD/CI checks and how to get more information about errors*" +"Once you submit a pull request, a series of checks will be run to ensure " +"that your changes do not introduce any bugs or errors. These checks " +"include:" msgstr "" -#: ../../CONTRIBUTING.md:97 +#: ../../CONTRIBUTING.md:246 +msgid "" +"**Code formatting and styles**: checks that your code is formatted " +"correctly, by `pre-commit.ci - pr check`." +msgstr "" + +#: ../../CONTRIBUTING.md:247 +msgid "" +"**docs build**: checks that the documentation builds correctly, using " +"`circleci`." +msgstr "" + +#: ../../CONTRIBUTING.md:249 +msgid "You will see the status of these checks in your pull request." +msgstr "" + +#: ../../CONTRIBUTING.md:251 +msgid "Pull request checks in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:257 +msgid "" +"An image showing the status of the checks in a pull request in GitHub. " +"The checks are displayed in a table with a status icon next to each " +"check. The checks are highlighted with a red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:259 +msgid "" +"If any of these checks fail, you will see an error message in your pull " +"request. You need to fix the errors before your changes can be merged." +msgstr "" + +#: ../../CONTRIBUTING.md:261 +msgid "Pull request checks failed in GitHub" +msgstr "" + +#: ../../CONTRIBUTING.md:267 +msgid "" +"An image showing the status of the checks in a pull request in GitHub. " +"The checks are displayed in a table with a status icon next to each " +"check. The checks that failed and the details link are highlighted with a" +" red rectangle." +msgstr "" + +#: ../../CONTRIBUTING.md:270 +msgid "" +"To get more information about the errors, you can click on the " +"\"Details\" link next to the failed check." +msgstr "" + +#: ../../CONTRIBUTING.md:272 msgid "What to expect from the review process" msgstr "" -#: ../../CONTRIBUTING.md:99 +#: ../../CONTRIBUTING.md:274 +msgid "" +"Once you submit a pull request, a maintainer of the repository will " +"review your changes and provide feedback. The review process may involve:" +msgstr "" + +#: ../../CONTRIBUTING.md:276 +msgid "" +"**Comments**: the reviewer may leave comments on your pull request to ask" +" questions or provide feedback." +msgstr "" + +#: ../../CONTRIBUTING.md:277 +msgid "" +"**Suggestions**: the reviewer may suggest changes to your code or " +"documentation." +msgstr "" + +#: ../../CONTRIBUTING.md:278 msgid "" -"*__TODO__: This section should describe how review happens in GitHub, how" -" see the comments, and how to submit changes (push a new branch)*" +"**Approvals**: once the reviewer is satisfied with your changes, they " +"will approve the pull request." msgstr "" -#: ../../CONTRIBUTING.md:101 +#: ../../CONTRIBUTING.md:280 +msgid "" +"You can make changes to your pull request by pushing new commits to the " +"branch. The pull request will be updated automatically with your new " +"changes." +msgstr "" + +#: ../../CONTRIBUTING.md:282 +msgid "" +"Once your pull request is approved, it will be merged into the main " +"branch and your changes will be included in the guide." +msgstr "" + +#: ../../CONTRIBUTING.md:284 msgid "Additional help" msgstr "" -#: ../../CONTRIBUTING.md:103 +#: ../../CONTRIBUTING.md:286 msgid "How to get help" msgstr "" -#: ../../CONTRIBUTING.md:105 +#: ../../CONTRIBUTING.md:288 msgid "" "*__TODO__: This section should describe the options for finding more help" " in case beginner contributors need more help (e.g., create an issue, " "post in a forum, etc).*" msgstr "" -#: ../../CONTRIBUTING.md:107 +#: ../../CONTRIBUTING.md:290 msgid "Additional resources" msgstr "" -#: ../../CONTRIBUTING.md:109 +#: ../../CONTRIBUTING.md:292 msgid "" "*__TODO__: It should also include links to beginner documentation, like " "the GitHub docs.*" msgstr "" -#: ../../CONTRIBUTING.md:111 +#: ../../CONTRIBUTING.md:294 msgid "Annex" msgstr "" -#: ../../CONTRIBUTING.md:113 +#: ../../CONTRIBUTING.md:296 msgid "Code examples" msgstr "" -#: ../../CONTRIBUTING.md:115 +#: ../../CONTRIBUTING.md:298 msgid "" "This guide uses the [literalinclude Sphinx directive](https://www.sphinx-" "doc.org/en/master/usage/restructuredtext/directives.html#directive-" @@ -323,18 +601,18 @@ msgid "" "for use in the documentation is kept in the `examples/` folder." msgstr "" -#: ../../CONTRIBUTING.md:119 +#: ../../CONTRIBUTING.md:302 msgid "Referencing code in documentation" msgstr "" -#: ../../CONTRIBUTING.md:121 +#: ../../CONTRIBUTING.md:304 msgid "" "If an example is present elsewhere in the documentation that you want to " "use, you can copy the `literalinclude` directive verbatim and the " "examples will stay in sync." msgstr "" -#: ../../CONTRIBUTING.md:124 +#: ../../CONTRIBUTING.md:307 msgid "" "If you already see code in the examples folder that you can use for new " "documentation, a new `literalinclude` can be made to extract it into the " @@ -344,7 +622,7 @@ msgid "" "the later can protect your example from future modifications to the code." msgstr "" -#: ../../CONTRIBUTING.md:129 +#: ../../CONTRIBUTING.md:312 msgid "" "**Pro tip**: As an alternative to `:lines:` there are also the `:start-" "after:`, `:start-at:`, `:end-before:`, and `:end-at:` options. And if the" @@ -352,17 +630,17 @@ msgid "" "way to keep the same documentation content even through code refactors." msgstr "" -#: ../../CONTRIBUTING.md:133 +#: ../../CONTRIBUTING.md:316 msgid "" "If you need example code that doesn't yet exist in `examples/` see " -"creating code for documentation](#creating-code-for-documentation)." +"[creating code for documentation](#creating-code-for-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:136 +#: ../../CONTRIBUTING.md:319 msgid "Creating code for documentation" msgstr "" -#: ../../CONTRIBUTING.md:138 +#: ../../CONTRIBUTING.md:321 msgid "" "Whenever you come across a place that could benefit from a code block, " "instead of writing it in-line with a code fence (`` ``` `` blocked text) " @@ -371,7 +649,7 @@ msgid "" "code-in-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:142 +#: ../../CONTRIBUTING.md:325 msgid "" "If you want to add a new example that doesn't fit into any of the " "existing example files, you can create a new file and reference it in a " @@ -380,7 +658,7 @@ msgid "" "create a new folder in the `examples` directory." msgstr "" -#: ../../CONTRIBUTING.md:146 +#: ../../CONTRIBUTING.md:329 msgid "" "If an existing example is incomplete or a new example makes sense to be " "added to an existing file, go ahead and add it, but take care to not " @@ -389,14 +667,14 @@ msgid "" "file, new methods after all existing ones in a class." msgstr "" -#: ../../CONTRIBUTING.md:150 +#: ../../CONTRIBUTING.md:333 msgid "" "Example code is checked for correctness, so adding a new example may " "require adding additional tests for coverage, and will require fixing any" " failing tests." msgstr "" -#: ../../CONTRIBUTING.md:153 +#: ../../CONTRIBUTING.md:336 msgid "" "***⚠️ WARNING***: great care should be taken when modifying existing " "example code, especially any modification beyond appending to the end of " @@ -407,29 +685,126 @@ msgid "" "and then checking those pages in a new build." msgstr "" -#: ../../CONTRIBUTING.md:161 +#: ../../CONTRIBUTING.md:344 msgid "Example:" msgstr "" -#: ../../CONTRIBUTING.md:163 +#: ../../CONTRIBUTING.md:346 msgid "Instead of writing example code in markdown like this" msgstr "" -#: ../../CONTRIBUTING.md:174 +#: ../../CONTRIBUTING.md:357 msgid "The python can be extracted into a `.py` file" msgstr "" -#: ../../CONTRIBUTING.md:188 +#: ../../CONTRIBUTING.md:371 msgid "" "As another example, if you only need to show part of a `pyproject.toml`, " "we already have complete project definitions, you need only to find the " "relevant part." msgstr "" -#: ../../CONTRIBUTING.md:191 +#: ../../CONTRIBUTING.md:374 msgid "Instead of writing this" msgstr "" -#: ../../CONTRIBUTING.md:203 +#: ../../CONTRIBUTING.md:386 msgid "an example could be extracted from an existing toml file" msgstr "" + +#~ msgid "" +#~ "Independently of the approach you " +#~ "choose, the first step is to fork" +#~ " the Python Packaging Guide repository " +#~ "into your personal GitHub space. To " +#~ "\"fork\" a repository in GitHub means" +#~ " to create a copy of the main" +#~ " repository, or repo, that you have" +#~ " complete control over and can modify" +#~ " as you see fit." +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to use the GitHub interface to " +#~ "edit and previewing a Markdown file.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to commit changes via the GitHub " +#~ "interface.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to clone a repository from GitHub" +#~ " into your computer.*" +#~ msgstr "" + +#~ msgid "*__TODO__: This section should show how to create a new branch.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to create a virtual environment " +#~ "using venv.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should show how" +#~ " to install the development dependencies" +#~ " defined in pyproject.toml.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to commit from the command " +#~ "line.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "the different sessions in nox related" +#~ " to building the docs: docs, docs-" +#~ "test, docs-live. It should also " +#~ "show how to see the guide built" +#~ " locally, by opening the right file" +#~ " in the browser or using the " +#~ "live version from docs-live*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "what steps a user should follow " +#~ "before submitting the pull request: " +#~ "build the docs, verify your changes " +#~ "look correct, etc.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to make a pull request in " +#~ "GitHub.*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how to see the results of the " +#~ "CD/CI checks and how to get more" +#~ " information about errors*" +#~ msgstr "" + +#~ msgid "" +#~ "*__TODO__: This section should describe " +#~ "how review happens in GitHub, how " +#~ "see the comments, and how to " +#~ "submit changes (push a new branch)*" +#~ msgstr "" + +#~ msgid "" +#~ "If you need example code that " +#~ "doesn't yet exist in `examples/` see " +#~ "creating code for documentation](#creating-" +#~ "code-for-documentation)." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/TRANSLATING.po b/locales/ja/LC_MESSAGES/TRANSLATING.po index 13765fc7..5a3de41c 100644 --- a/locales/ja/LC_MESSAGES/TRANSLATING.po +++ b/locales/ja/LC_MESSAGES/TRANSLATING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../TRANSLATING.md:5 msgid "Translation Guide for the Python Packaging Guide" @@ -165,8 +165,9 @@ msgstr "" #: ../../TRANSLATING.md:68 msgid "" -"You can find a list of the two-letter ISO language codes " -"[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." +"You can find a list of the two-letter Sphinx language option " +"[here](https://www.sphinx-doc.org/en/master/usage/configuration.html" +"#confval-language)." msgstr "" #: ../../TRANSLATING.md:71 @@ -426,7 +427,7 @@ msgid "" "Note the `--` before the language code, it indicates that the following " "arguments should be passed into the nox session and not be interpreted " "directly by nox. If you forget the `--`, nox will look instead for a " -"session named 'es' and complain that it does not exist." +"session named 'es' and raise an error that it does not exist." msgstr "" #: ../../TRANSLATING.md:241 @@ -496,7 +497,7 @@ msgid "" msgstr "" #: ../../TRANSLATING.md:268 -msgid "TODO: This tagging could be automated with a GitHub action." +msgid "TODO: This tagging could be automated with a GitHub Actions." msgstr "" #: ../../TRANSLATING.md:270 @@ -705,8 +706,7 @@ msgstr "" #: ../../TRANSLATING.md:343 msgid "" "If you have any questions or need help with your translation, you can " -"create an issue in the repository if you encounter any problems or need " -"assistance." +"create an issue in the repository." msgstr "" #: ../../TRANSLATING.md:345 @@ -715,3 +715,31 @@ msgid "" " as a way for contributors to ask for help with translations or the " "translation workflow?" msgstr "" + +#~ msgid "" +#~ "You can find a list of the " +#~ "two-letter ISO language codes " +#~ "[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." +#~ msgstr "" + +#~ msgid "" +#~ "Note the `--` before the language " +#~ "code, it indicates that the following" +#~ " arguments should be passed into the" +#~ " nox session and not be interpreted" +#~ " directly by nox. If you forget " +#~ "the `--`, nox will look instead " +#~ "for a session named 'es' and " +#~ "complain that it does not exist." +#~ msgstr "" + +#~ msgid "TODO: This tagging could be automated with a GitHub action." +#~ msgstr "" + +#~ msgid "" +#~ "If you have any questions or need" +#~ " help with your translation, you can" +#~ " create an issue in the repository" +#~ " if you encounter any problems or " +#~ "need assistance." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/documentation.po b/locales/ja/LC_MESSAGES/documentation.po index ea6bdd72..5afd138f 100644 --- a/locales/ja/LC_MESSAGES/documentation.po +++ b/locales/ja/LC_MESSAGES/documentation.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-26 09:16-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../documentation/hosting-tools/intro.md:1 msgid "Tools to Build and Host your Documentation" @@ -77,10 +77,10 @@ msgstr "" #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:9 msgid "" "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is " -"a combination of vanilla of `markdown` and `rST` syntax. It is a nice " -"option if you are comfortable writing markdown. `myst` is preferred by " -"many because it offers both the rich functionality of rST combined with a" -" simple-to-write markdown syntax." +"a combination of `markdown` and `rST` syntax. It is a nice option if you " +"are comfortable writing markdown. `myst` is preferred by many because it " +"offers both the rich functionality of rST combined with a simple-to-write" +" markdown syntax." msgstr "" #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:12 @@ -322,7 +322,7 @@ msgstr "" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:49 msgid "" -"While Sphinx natively supports the `rST` syntax. You can add custom " +"While Sphinx natively supports the `rST` syntax, you can add custom " "syntax parsers to support easier-to-write syntax using tools such as [the" " MyST parser](https://myst-parser.readthedocs.io/)." msgstr "" @@ -445,10 +445,10 @@ msgid "" "documentation content pages. [The OpenGraph protocol allows other " "websites to provide a useful preview of the content on your page when " "shared](https://www.freecodecamp.org/news/what-is-open-graph-and-how-" -"can-i-use-it-for-my-website/#what-is-open-graph). This is important for " -"when the pages in your documentation are shared on social media sites " -"like Twitter and Mastodon and even for shares on tools like Slack and " -"Discourse." +"can-i-use-it-for-my-website/#heading-what-is-open-graph). This is " +"important for when the pages in your documentation are shared on social " +"media sites like Twitter and Mastodon and even for shares on tools like " +"Slack and Discourse." msgstr "" #: ../../documentation/index.md:3 @@ -2224,7 +2224,7 @@ msgstr "" msgid "" "It's important to keep in mind that examples in your docstrings help " "users using your package. Running `doctest` on those examples provides a " -"check of your package's API. doctest ensures that the functions and " +"check of your package's API. The doctest ensures that the functions and " "methods in your package run as you expect them to. Neither of these items" " replace a separate, stand-alone test suite that is designed to test your" " package's core functionality across operating systems and Python " @@ -2543,3 +2543,56 @@ msgstr "" #: ../../documentation/write-user-documentation/intro.md:15 msgid "sphinx gallery for tutorials." msgstr "" + +#~ msgid "" +#~ "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html)" +#~ " myST is a combination of vanilla " +#~ "of `markdown` and `rST` syntax. It " +#~ "is a nice option if you are " +#~ "comfortable writing markdown. `myst` is " +#~ "preferred by many because it offers " +#~ "both the rich functionality of rST " +#~ "combined with a simple-to-write " +#~ "markdown syntax." +#~ msgstr "" + +#~ msgid "" +#~ "While Sphinx natively supports the `rST`" +#~ " syntax. You can add custom syntax" +#~ " parsers to support easier-to-write" +#~ " syntax using tools such as [the " +#~ "MyST parser](https://myst-parser.readthedocs.io/)." +#~ msgstr "" + +#~ msgid "" +#~ "OpenGraph is an extension that allows" +#~ " you to add metadata to your " +#~ "documentation content pages. [The OpenGraph" +#~ " protocol allows other websites to " +#~ "provide a useful preview of the " +#~ "content on your page when " +#~ "shared](https://www.freecodecamp.org/news/what-is-open-" +#~ "graph-and-how-can-i-use-it-for-" +#~ "my-website/#what-is-open-graph). This " +#~ "is important for when the pages in" +#~ " your documentation are shared on " +#~ "social media sites like Twitter and " +#~ "Mastodon and even for shares on " +#~ "tools like Slack and Discourse." +#~ msgstr "" + +#~ msgid "" +#~ "It's important to keep in mind " +#~ "that examples in your docstrings help" +#~ " users using your package. Running " +#~ "`doctest` on those examples provides a" +#~ " check of your package's API. doctest" +#~ " ensures that the functions and " +#~ "methods in your package run as you" +#~ " expect them to. Neither of these " +#~ "items replace a separate, stand-alone" +#~ " test suite that is designed to " +#~ "test your package's core functionality " +#~ "across operating systems and Python " +#~ "versions." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/index.po b/locales/ja/LC_MESSAGES/index.po index 83e4bdda..558b22c9 100644 --- a/locales/ja/LC_MESSAGES/index.po +++ b/locales/ja/LC_MESSAGES/index.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../index.md:283 msgid "Tutorials" @@ -79,13 +79,14 @@ msgid "About this guide" msgstr "このガイドについて" #: ../../index.md:29 +#, fuzzy msgid "" "Image with the pyOpenSci flower logo in the upper right hand corner. The " "image shows the packaging lifecycle. The graphic shows a high level " -"overview of the elements of a Python package. the inside circle has 5 " +"overview of the elements of a Python package. The inside circle has 5 " "items - user documentation, code/api, test suite, contributor " "documentation, project metadata / license / readme. In the middle of the " -"circle is says maintainers and has a small icon with people. on the " +"circle is says maintainers and has a small icon with people. On the " "outside circle there is an arrow and it says infrastructure." msgstr "" "右上にpyOpenSciの花のロゴがある画像。画像はパッケージングのライフサイクルを示しています。図にはPythonパッケージの要素のハイレベルな概要が示されています。内側の円には5つの項目があります" @@ -116,8 +117,7 @@ msgstr "Pythonパッケージの作成と保守のすべてを理解する" msgid "" "You will also find best practice recommendations and curated lists of " "community resources surrounding packaging and package documentation." -msgstr "" -"また、パッケージングとパッケージドキュメンテーションにまつわるベストプラクティスの推奨や、コミュニティリソースのキュレーションリストもご覧いただけます。" +msgstr "また、パッケージングとパッケージドキュメンテーションにまつわるベストプラクティスの推奨や、コミュニティリソースのキュレーションリストもご覧いただけます。" #: ../../index.md:46 msgid "Todo" @@ -163,9 +163,8 @@ msgid "" "repo here](https://github.com/pyOpenSci/python-package-guide)." msgstr "" "コミュニティが開発した、科学者のためのPythonパッケージの作り方チュートリアルシリーズの第一弾が完成しました！ " -"コミュニティのレビュープロセスに参加したり、 [Github " -"リポジトリはこちら](https://github.com/pyOpenSci/python-package-guide) " -"で今後のチュートリアルの開発を見守ったりしてください。" +"コミュニティのレビュープロセスに参加したり、 [Github リポジトリはこちら](https://github.com/pyOpenSci" +"/python-package-guide) で今後のチュートリアルの開発を見守ったりしてください。" #: ../../index.md:71 msgid "✿ Create a Package Tutorials ✿" @@ -200,7 +199,8 @@ msgid "" "[How to add metadata to a pyproject.toml file for publication to " "PyPI.](/tutorials/pyproject-toml.md)" msgstr "" -"[PyPIに公開するためにpyproject.tomlファイルにメタデータを追加する方法](/tutorials/pyproject-toml.md)" +"[PyPIに公開するためにpyproject.tomlファイルにメタデータを追加する方法](/tutorials/pyproject-" +"toml.md)" #: ../../index.md:93 msgid "✿ Packaging Tool Tutorials ✿" @@ -236,8 +236,8 @@ msgid "" "[Package metadata / pyproject.toml](package-structure-code/pyproject-" "toml-python-package-metadata.md)" msgstr "" -"[パッケージメタデータ / pyproject.toml](package-structure-code/pyproject-toml-python-" -"package-metadata.md)" +"[パッケージメタデータ / pyproject.toml](package-structure-code/pyproject-toml-" +"python-package-metadata.md)" #: ../../index.md:119 msgid "" @@ -264,7 +264,8 @@ msgid "" "[Non pure Python builds](package-structure-code/complex-python-package-" "builds.md)" msgstr "" -"[純粋な Python 以外のビルド](package-structure-code/complex-python-package-builds.md)" +"[純粋な Python 以外のビルド](package-structure-code/complex-python-package-" +"builds.md)" #: ../../index.md:127 msgid "✨ Publish your package ✨" @@ -280,16 +281,15 @@ msgstr "Pythonのパッケージングエコシステムをより深く理解す msgid "" "[Package versioning & release](/package-structure-code/python-package-" "versions.md)" -msgstr "" -"[パッケージのバージョン管理とリリース](/package-structure-code/python-package-versions.md)" +msgstr "[パッケージのバージョン管理とリリース](/package-structure-code/python-package-versions.md)" #: ../../index.md:135 msgid "" "[Publish to PyPI & Conda-forge](/package-structure-code/publish-python-" "package-pypi-conda.md)" msgstr "" -"[PyPIとConda-forgeへの公開](/package-structure-code/publish-python-package-pypi-" -"conda.md)" +"[PyPIとConda-forgeへの公開](/package-structure-code/publish-python-package-" +"pypi-conda.md)" #: ../../index.md:148 msgid "✨ Write The Docs ✨" @@ -312,8 +312,8 @@ msgid "" "[Write tutorials to show how your package is used](/documentation/write-" "user-documentation/create-package-tutorials)" msgstr "" -"[パッケージがどのように使われるかを示すチュートリアルを書く](/documentation/write-user-" -"documentation/create-package-tutorials)" +"[パッケージがどのように使われるかを示すチュートリアルを書く](/documentation/write-user-documentation" +"/create-package-tutorials)" #: ../../index.md:158 msgid "✨ Developer Docs ✨" @@ -323,8 +323,7 @@ msgstr "✨開発者向けドキュメント✨" msgid "" "[Create documentation for collaborating developers](/documentation" "/repository-files/contributing-file)" -msgstr "" -"[共同開発者のためのドキュメントの作成](/documentation/repository-files/contributing-file)" +msgstr "[共同開発者のためのドキュメントの作成](/documentation/repository-files/contributing-file)" #: ../../index.md:162 msgid "" @@ -341,7 +340,8 @@ msgid "" "[Writing a README file](/documentation/repository-files/readme-file-best-" "practices)" msgstr "" -"[READMEファイルの書き方](/documentation/repository-files/readme-file-best-practices)" +"[READMEファイルの書き方](/documentation/repository-files/readme-file-best-" +"practices)" #: ../../index.md:171 msgid "" @@ -370,8 +370,8 @@ msgid "" "[Markdown, MyST, and ReST](/documentation/hosting-tools/myst-markdown-" "rst-doc-syntax)" msgstr "" -"[Markdown、MyST、およびReST](/documentation/hosting-tools/myst-markdown-rst-doc-" -"syntax)" +"[Markdown、MyST、およびReST](/documentation/hosting-tools/myst-markdown-rst-" +"doc-syntax)" #: ../../index.md:183 msgid "" @@ -386,8 +386,8 @@ msgid "" "*We are actively working on this section. [Follow development " "here.](https://github.com/pyOpenSci/python-package-guide)*" msgstr "" -"*私たちはこのセクションに積極的に取り組んでいます。 " -"[開発のフォローはこちら](https://github.com/pyOpenSci/python-package-guide)*" +"*私たちはこのセクションに積極的に取り組んでいます。 [開発のフォローはこちら](https://github.com/pyOpenSci" +"/python-package-guide)*" #: ../../index.md:197 msgid "✨ Tests for your Python package ✨" @@ -440,19 +440,20 @@ msgid "" msgstr "このガイドへのご貢献をお待ちしております。貢献方法についてはこちらをご覧ください。" #: ../../index.md:246 +#, fuzzy msgid "" "xkcd comic showing a stick figure on the ground and one in the air. The " "one on the ground is saying. `You're flying! how?` The person in the air" " replies `Python!` Below is a 3 rectangle comic with the following text " -"in each box. box 1 - I learned it last night. Everything is so simple. " -"Hello world is just print hello world. box 2 - the person on the ground " -"says - come join us programming is fun again. it's a whole new world. But" +"in each box. Box 1 - I learned it last night. Everything is so simple. " +"Hello world is just print hello world. Box 2 - the person on the ground " +"says - come join us programming is fun again. It's a whole new world. But" " how are you flying? box 3 - the person flying says - i just typed import" " antigravity. I also sampled everything in the medicine cabinet. But i " -"think this is the python. the person on the ground is saying - that's it?" +"think this is the python. The person on the ground is saying - that's it?" msgstr "" -"xkcdの漫画で、地面に置かれた棒人間と空中にある棒人間が描かれている。地上にいる人が言っている。 `あなたは飛んでいる！どうやって？` 空中にいる人は" -" `Python!` と答える。以下は3つの長方形のマンガで、各ボックスに次のテキストが入っている。ボックス1 - " +"xkcdの漫画で、地面に置かれた棒人間と空中にある棒人間が描かれている。地上にいる人が言っている。 `あなたは飛んでいる！どうやって？` " +"空中にいる人は `Python!` と答える。以下は3つの長方形のマンガで、各ボックスに次のテキストが入っている。ボックス1 - " "昨夜学んだ。すべてがとてもシンプルだ。Hello worldはprint hello worldだけ。ボックス2 - " "地上にいる人が言う。まったく新しい世界だ。でもどうやって飛んでるの？ボックス3 - 飛んでいる人はこう言う。- " "`反重力をインポートしました。薬箱の中のものも全部試しました。でもこれがpythonだと思う。地上の人はこう言っている。- これで終わり？" diff --git a/locales/ja/LC_MESSAGES/package-structure-code.po b/locales/ja/LC_MESSAGES/package-structure-code.po index f02e7e1e..4a574f61 100644 --- a/locales/ja/LC_MESSAGES/package-structure-code.po +++ b/locales/ja/LC_MESSAGES/package-structure-code.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../package-structure-code/code-style-linting-format.md:1 msgid "Python Package Code Style, Format and Linters" @@ -496,7 +496,7 @@ msgstr "" #: ../../package-structure-code/code-style-linting-format.md:262 msgid "" "The pre-commit workflow begins with you adding files that have changes to" -" be staged in git. Next, you'd run git commit. when you run git commit, " +" be staged in git. Next, you'd run git commit. When you run git commit, " "the pre-commit hooks will then run. In this example, Black, the code " "formatter and flake8, a linter both run. If all of the files pass Black " "and flake8 checks, then your commit will be recorded. If they don't, the " @@ -762,7 +762,7 @@ msgid "" "keep this comment - https://github.com/pyOpenSci/python-package-" "guide/pull/106#issuecomment-1844278487 in this file for now - jeremiah " "did a nice inventory of common shells and whether they need quotes or " -"not. it's really comprehensive. but do we want it in the guide?? it's " +"not. It's really comprehensive. But do we want it in the guide?? it's " "really useful for more advanced users i think." msgstr "" @@ -797,18 +797,18 @@ msgid "" msgstr "" #: ../../package-structure-code/declare-dependencies.md:29 -msgid "needs to function properly." +msgid "Needs to function properly." msgstr "" #: ../../package-structure-code/declare-dependencies.md:30 msgid "" -"requires if someone wants to develop / work on improving your package " +"Requires if someone wants to develop / work on improving your package " "locally or" msgstr "" #: ../../package-structure-code/declare-dependencies.md:31 msgid "" -"requires if a user wants to add additional functionality (that is not " +"Requires if a user wants to add additional functionality (that is not " "core) to your package" msgstr "" @@ -1130,7 +1130,7 @@ msgid "" "dependency groups listed above - docs feature and tests. In the center it" " says your-package and lists the core dependencies of that package " "seaborn and numpy. To the right are two arrows. The first shows the " -"command python - m pip install your-package. it them shows how installing" +"command python - m pip install your-package. It them shows how installing" " your package that way installs only the package and the two core " "dependencies into a users environment. Below is a second arrow with " "python -m pip install youPackage[tests]. This leads to an environment " @@ -1744,7 +1744,7 @@ msgstr "" msgid "" "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 " +"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." @@ -1754,8 +1754,8 @@ msgstr "" msgid "" "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 " +" The 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." msgstr "" @@ -1903,10 +1903,10 @@ msgid "" "Graphic with the title Python package repositories. Below it says " "Anything hosted on PyPI can be installed using pip install. Packaging " "hosted on a conda channel can be installed using conda install. Below " -"that there are two rows. the top row says conda channels. next to it are " +"that there are two rows. The top row says conda channels. Next to it are " "three boxes one with conda-forge, community maintained; bioconda and then" " default - managed by the anaconda team. Below that there is a row that " -"says PyPI servers. PyPI - anyone can publish to PyPI. and test PyPI. a " +"says PyPI servers. PyPI - anyone can publish to PyPI. And test PyPI. A " "testbed server for you to practice." msgstr "" @@ -2233,7 +2233,6 @@ msgid "How the pyproject.toml is used when you build a package" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:104 -#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 msgid "" "When you publish to PyPI, you will notice that each package has metadata " "listed. Let’s have a look at [xclim](https://pypi.org/project/xclim/), " @@ -2453,7 +2452,7 @@ msgid "" "Here is an example of[ a package that has entry point " "script](https://github.com/pyOpenSci/update-web-" "metadata/blob/main/pyproject.toml#L60)s. Notice that there are several " -"core scripts defined in that package that perform sets of tasks. " +"core scripts defined in that package that perform sets of tasks. The " "pyOpenSci is using those scripts to process their metadata." msgstr "" @@ -2462,7 +2461,7 @@ msgid "" "**Dynamic Fields:** if you have fields that are dynamically populated. " "One example of this is if you are using scm / version control based " "version with tools like `setuptooms_scm`, then you might use the dynamic " -"field. such as version (using scm) **dynamic = [\"version\"]**" +"field, such as version (using scm) **dynamic = [\"version\"]**" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:189 @@ -3913,9 +3912,9 @@ msgstr "" msgid "" "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." +" The 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." msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:11 @@ -4030,14 +4029,29 @@ msgstr "" msgid "An example - xclim" msgstr "" +#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 +msgid "" +"When you publish to PyPI, you will notice that each package has metadata " +"listed. Let's have a look at [xclim](https://pypi.org/project/xclim/), " +"one of our [pyOpenSci packages](https://www.pyopensci.org/python-" +"packages.html). Notice that on the PyPI landing page you see some " +"metadata about the package including python, maintainer information and " +"more. PyPI is able to populate this metadata because it was defined using" +" correct syntax and classifiers by Xclim's maintainers, [pyproject.toml " +"file](https://github.com/Ouranosinc/xclim/blob/master/pyproject.toml). " +"This metadata when the xclim package is built, is translated into a " +"distribution file that allows PyPI to read the metadata and print it out " +"on their website." +msgstr "" + #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:94 msgid "" "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" +"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 " +"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." msgstr "" @@ -4054,7 +4068,7 @@ msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:101 msgid "" -"This screenshot shows the metadata on PyPI for the xclim package. on it " +"This screenshot shows the metadata on PyPI for the xclim package. On it " "you can see the name of the license, the author and maintainer names " "keywords associated with the package and the base python version it " "requires which is 3.8." @@ -4066,7 +4080,7 @@ msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:110 msgid "" -"Here you see the maintinaer metadata as it is displayed on PyPI. for " +"Here you see the maintainer metadata as it is displayed on PyPI. For " "xclim there are three maintainers listed with their profile pictures and " "github user names to the right." msgstr "" @@ -4770,7 +4784,7 @@ msgstr "" msgid "" "Consistent version increases following semver rules mean that values of " "your package version explain the extent of the changes made in the code " -"base from version to version. thus your package version numbers become " +"base from version to version. Thus your package version numbers become " "\"expressive\" in the same way that naming code variables well can [make " "code expressive](https://medium.com/@daniel.oliver.king/writing-" "expressive-code-b69ef7a5a2fa)." @@ -4934,7 +4948,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:107 msgid "" "Generally semantic release and version control system tools can be setup " -"to run automatically on GitHub using GitHub actions. This means that you " +"to run automatically on GitHub using GitHub Actions. This means that you " "can create a workflow where a GitHub release and associated new version " "tag is used to trigger an automated build that:" msgstr "" @@ -4955,7 +4969,7 @@ msgstr "" msgid "" "Bumping a package version refers to the step of increasing the package " "version after a set number of changes have been made to it. For example, " -"you might bump from version 0.8 to 0.9 of a package. or from 0.9 to 1.0." +"you might bump from version 0.8 to 0.9 of a package or from 0.9 to 1.0." msgstr "" #: ../../package-structure-code/python-package-versions.md:122 @@ -5065,7 +5079,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:173 msgid "" "When you (or your CI system) build your package, hatch checks the current" -" tag number for your package. if it has increased, it will update the " +" tag number for your package. If it has increased, it will update the " "**\\_version.py** file with the new value." msgstr "" @@ -5299,3 +5313,233 @@ msgid "" "The version number is manually updated in a configuration file such as " "`pyproject.toml` vs. in a package **\\_version.py** file." msgstr "" + +#~ msgid "" +#~ "The pre-commit workflow begins with " +#~ "you adding files that have changes " +#~ "to be staged in git. Next, you'd" +#~ " run git commit. when you run " +#~ "git commit, the pre-commit hooks " +#~ "will then run. In this example, " +#~ "Black, the code formatter and flake8," +#~ " a linter both run. If all of" +#~ " the files pass Black and flake8 " +#~ "checks, then your commit will be " +#~ "recorded. If they don't, the commit " +#~ "is canceled. You will have to fix" +#~ " any flake8 issues, and then re-" +#~ "add / stage the files to be " +#~ "committed. [_Image " +#~ "Source_](https://ljvmiranda921.github.io/notebook/2018/06/21" +#~ "/precommits-using-black-and-flake8/*)" +#~ msgstr "" + +#~ msgid "" +#~ "keep this comment - " +#~ "https://github.com/pyOpenSci/python-package-" +#~ "guide/pull/106#issuecomment-1844278487 in this file" +#~ " for now - jeremiah did a nice" +#~ " inventory of common shells and " +#~ "whether they need quotes or not. " +#~ "it's really comprehensive. but do we " +#~ "want it in the guide?? it's really" +#~ " useful for more advanced users i " +#~ "think." +#~ msgstr "" + +#~ msgid "needs to function properly." +#~ msgstr "" + +#~ msgid "" +#~ "requires if someone wants to develop " +#~ "/ work on improving your package " +#~ "locally or" +#~ msgstr "" + +#~ msgid "" +#~ "requires if a user wants to add" +#~ " additional functionality (that is not " +#~ "core) to your package" +#~ msgstr "" + +#~ msgid "" +#~ "Diagram showing a ven diagram with " +#~ "three sections representing the dependency " +#~ "groups listed above - docs feature " +#~ "and tests. In the center it says" +#~ " your-package and lists the core " +#~ "dependencies of that package seaborn and" +#~ " numpy. To the right are two " +#~ "arrows. The first shows the command " +#~ "python - m pip install your-" +#~ "package. it them shows how installing" +#~ " your package that way installs only" +#~ " the package and the two core " +#~ "dependencies into a users environment. " +#~ "Below is a second arrow with " +#~ "python -m pip install youPackage[tests]. " +#~ "This leads to an environment with " +#~ "both the package dependencies - your-" +#~ "package, seaborn and numpy and also " +#~ "the tests dependencies including pytest " +#~ "and pytest-cov" +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "Graphic with the title Python package" +#~ " repositories. Below it says Anything " +#~ "hosted on PyPI can be installed " +#~ "using pip install. Packaging hosted on" +#~ " a conda channel can be installed " +#~ "using conda install. Below that there" +#~ " are two rows. the top row says" +#~ " conda channels. next to it are " +#~ "three boxes one with conda-forge, " +#~ "community maintained; bioconda and then " +#~ "default - managed by the anaconda " +#~ "team. Below that there is a row" +#~ " that says PyPI servers. PyPI - " +#~ "anyone can publish to PyPI. and " +#~ "test PyPI. a testbed server for " +#~ "you to practice." +#~ msgstr "" + +#~ msgid "" +#~ "Here is an example of[ a package" +#~ " that has entry point " +#~ "script](https://github.com/pyOpenSci/update-web-" +#~ "metadata/blob/main/pyproject.toml#L60)s. Notice that " +#~ "there are several core scripts defined" +#~ " in that package that perform sets" +#~ " of tasks. pyOpenSci is using those" +#~ " scripts to process their metadata." +#~ msgstr "" + +#~ msgid "" +#~ "**Dynamic Fields:** if you have fields" +#~ " that are dynamically populated. One " +#~ "example of this is if you are " +#~ "using scm / version control based " +#~ "version with tools like `setuptooms_scm`, " +#~ "then you might use the dynamic " +#~ "field. such as version (using scm) " +#~ "**dynamic = [\"version\"]**" +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "This screenshot shows the metadata on" +#~ " PyPI for the xclim package. on " +#~ "it you can see the name of " +#~ "the license, the author and maintainer" +#~ " names keywords associated with the " +#~ "package and the base python version " +#~ "it requires which is 3.8." +#~ msgstr "" + +#~ msgid "" +#~ "Here you see the maintinaer metadata " +#~ "as it is displayed on PyPI. for" +#~ " xclim there are three maintainers " +#~ "listed with their profile pictures and" +#~ " github user names to the right." +#~ msgstr "" + +#~ msgid "" +#~ "Consistent version increases following semver" +#~ " rules mean that values of your " +#~ "package version explain the extent of" +#~ " the changes made in the code " +#~ "base from version to version. thus " +#~ "your package version numbers become " +#~ "\"expressive\" in the same way that " +#~ "naming code variables well can [make " +#~ "code expressive](https://medium.com/@daniel.oliver.king" +#~ "/writing-expressive-code-b69ef7a5a2fa)." +#~ msgstr "" + +#~ msgid "" +#~ "Generally semantic release and version " +#~ "control system tools can be setup " +#~ "to run automatically on GitHub using " +#~ "GitHub actions. This means that you " +#~ "can create a workflow where a " +#~ "GitHub release and associated new " +#~ "version tag is used to trigger an" +#~ " automated build that:" +#~ msgstr "" + +#~ msgid "" +#~ "Bumping a package version refers to " +#~ "the step of increasing the package " +#~ "version after a set number of " +#~ "changes have been made to it. For" +#~ " example, you might bump from version" +#~ " 0.8 to 0.9 of a package. or" +#~ " from 0.9 to 1.0." +#~ msgstr "" + +#~ msgid "" +#~ "When you (or your CI system) build" +#~ " your package, hatch checks the " +#~ "current tag number for your package. " +#~ "if it has increased, it will " +#~ "update the **\\_version.py** file with " +#~ "the new value." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/tests.po b/locales/ja/LC_MESSAGES/tests.po index 1b5994c6..bf826243 100644 --- a/locales/ja/LC_MESSAGES/tests.po +++ b/locales/ja/LC_MESSAGES/tests.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../tests/index.md:72 msgid "Intro" @@ -102,7 +102,7 @@ msgstr "" #: ../../tests/index.md:58 msgid "" -"Continuous integration platforms such as GitHub actions can be useful for" +"Continuous integration platforms such as GitHub Actions can be useful for" " running your tests across both different Python versions and different " "operating systems. Learn about setting up tests to run in Continuous " "Integration here." @@ -383,9 +383,6 @@ msgid "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** is an " "automation tool that supports common steps such as building " "documentation, running tests across various versions of Python, and more." -" You can find [a nice overview of tox in the plasmaPy " -"documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" -"#using-tox)." msgstr "" #: ../../tests/run-tests.md:127 @@ -805,12 +802,12 @@ msgid "" msgstr "" #: ../../tests/tests-ci.md:22 -msgid "Example GitHub action that runs tests" +msgid "Example GitHub Actions that runs tests" msgstr "" #: ../../tests/tests-ci.md:24 msgid "" -"Below is an example GitHub action that runs tests using nox across both " +"Below is an example GitHub Actions that runs tests using nox across both " "Windows, Mac and Linux and on Python versions 3.9-3.11." msgstr "" @@ -896,7 +893,7 @@ msgstr "" #: ../../tests/write-tests.md:21 msgid "" "**Easier pull request reviews:** By running your tests in a CI framework " -"such as GitHub actions, each time you or a contributor makes a change to " +"such as GitHub Actions, each time you or a contributor makes a change to " "your code-base, you can catch issues and things that may have changed in " "your code base. This ensures that your software behaves the way you " "expect it to." @@ -1000,3 +997,48 @@ msgid "" "the user can easily understand why if failed (provides a useful error " "message)." msgstr "" + +#~ msgid "" +#~ "Continuous integration platforms such as " +#~ "GitHub actions can be useful for " +#~ "running your tests across both different" +#~ " Python versions and different operating" +#~ " systems. Learn about setting up " +#~ "tests to run in Continuous Integration" +#~ " here." +#~ msgstr "" + +#~ msgid "" +#~ "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)**" +#~ " is an automation tool that supports" +#~ " common steps such as building " +#~ "documentation, running tests across various" +#~ " versions of Python, and more. You" +#~ " can find [a nice overview of " +#~ "tox in the plasmaPy " +#~ "documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" +#~ "#using-tox)." +#~ msgstr "" + +#~ msgid "Example GitHub action that runs tests" +#~ msgstr "" + +#~ msgid "" +#~ "Below is an example GitHub action " +#~ "that runs tests using nox across " +#~ "both Windows, Mac and Linux and on" +#~ " Python versions 3.9-3.11." +#~ msgstr "" + +#~ msgid "" +#~ "**Easier pull request reviews:** By " +#~ "running your tests in a CI " +#~ "framework such as GitHub actions, each" +#~ " time you or a contributor makes " +#~ "a change to your code-base, you" +#~ " can catch issues and things that " +#~ "may have changed in your code " +#~ "base. This ensures that your software" +#~ " behaves the way you expect it " +#~ "to." +#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index 7eb0df48..6dd97827 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-02 18:04+0900\n" +"POT-Creation-Date: 2024-08-23 21:12-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.15.0\n" +"Generated-By: Babel 2.16.0\n" #: ../../tutorials/add-license-coc.md:1 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" @@ -79,12 +79,12 @@ msgstr "" #: ../../tutorials/add-license-coc.md:23 msgid "" -"create a `LICENSE` file in your project directory that specifies the " -"license that you choose for your package and" +"Create a `LICENSE` file in your project directory that specifies the " +"license that you choose for your package." msgstr "" #: ../../tutorials/add-license-coc.md:24 -msgid "reference that file in your `pyproject.toml` data where metadata are set." +msgid "Reference that file in your `pyproject.toml` data where metadata are set." msgstr "" #: ../../tutorials/add-license-coc.md:26 @@ -1194,7 +1194,7 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:202 msgid "" "`hatch config show` will print out the contents of your `config.toml` " -"file in your shell. look at the values and ensure that your name, email " +"file in your shell. Look at the values and ensure that your name, email " "is set. Also make sure that `tests=false`." msgstr "" @@ -1229,7 +1229,7 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:220 msgid "" -"it will convert metadata stored in a `setup.py` or `setup.cfg` file to a " +"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" @@ -1298,7 +1298,7 @@ msgstr "" msgid "" "ADD: note about what makes something \"package worthy\", with a common " "misconception being that a package should be production-ready code that's" -" valuable to a broad audience. this may not be a pervasive misconception " +" valuable to a broad audience. This may not be a pervasive misconception " "in Python, but a quick break-out with an explanation of what a package " "can consist of would be helpful." msgstr "" @@ -1435,7 +1435,7 @@ msgid "An `__init__.py` file in your code directory." msgstr "" #: ../../tutorials/installable-code.md:83 -msgid "The directory structure you’ll create in this lesson will look like this:" +msgid "The directory structure you'll create in this lesson will look like this:" msgstr "" #: ../../tutorials/installable-code.md:95 @@ -1509,7 +1509,7 @@ msgstr "" #: ../../tutorials/installable-code.md:121 msgid "" -"Where you define your project’s metadata (including its name, authors, " +"Where you define your project's metadata (including its name, authors, " "license, etc)" msgstr "" @@ -1734,7 +1734,7 @@ msgstr "" #: ../../tutorials/installable-code.md:282 msgid "" -"If you aren’t familiar with docstrings or typing yet, that is ok. You can" +"If you aren't familiar with docstrings or typing yet, that is ok. You can" " review [this page in the pyOpenSci packaging " "guide](https://www.pyopensci.org/python-package-guide/documentation" "/write-user-documentation/document-your-code-api-docstrings.html) for an " @@ -1901,7 +1901,7 @@ msgstr "" #: ../../tutorials/installable-code.md:482 msgid "" "Once you have your project metadata in the pyproject.toml file, you will " -"rarely update it. In the next lesson you’ll add more metadata and " +"rarely update it. In the next lesson you'll add more metadata and " "structure to this file." msgstr "" @@ -2866,8 +2866,8 @@ msgid "" "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 " +"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." @@ -3038,7 +3038,7 @@ msgstr "" msgid "" "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 " +"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." @@ -3386,7 +3386,7 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:279 msgid "" "There is currently a small bug in Grayskull where it doesn't populate the" -" home: element of the recipe. if you don't include this, [you will " +" home: element of the recipe. If you don't include this, [you will " "receive an error message](https://github.com/conda-forge/staged-" "recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" " linter bot." @@ -3934,8 +3934,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:60 msgid "" "In a future lesson, you will learn how to create an automated GitHub " -"action workflow that publishes an updated version of your package to PyPI" -" every time you create a GitHub release." +"Actions workflow that publishes an updated version of your package to " +"PyPI every time you create a GitHub release." msgstr "" #: ../../tutorials/publish-pypi.md:64 @@ -4472,10 +4472,10 @@ msgstr "" #: ../../tutorials/publish-pypi.md:363 msgid "" "You can also create an automated publication workflow on GitHub using " -"GitHub actions. This is a great way to make the publication process " +"GitHub Actions. This is a great way to make the publication process " "easier and it also supports a growing maintainer team. In this case we " "suggest you don't worry about the token and instead setup a specific " -"GitHub action that publishes your package when you make a release. You " +"GitHub Actions that publishes your package when you make a release. You " "can then create a \"trusted publisher\" workflow on PyPI." msgstr "" @@ -4665,7 +4665,7 @@ msgstr "" #: ../../tutorials/pyproject-toml.md:43 msgid "" "When you are adding classifiers to the **[project]** table, only use " -"valid values from [PyPI’s classifier " +"valid values from [PyPI's classifier " "page](https://PyPI.org/classifiers/). An invalid value here will raise an" " error when you build and publish your package on PyPI." msgstr "" @@ -5534,3 +5534,155 @@ msgid "" "existing functionality remains intact. Run any pre-existing tests to " "verify that everything still works as expected." msgstr "" + +#~ msgid "" +#~ "create a `LICENSE` file in your " +#~ "project directory that specifies the " +#~ "license that you choose for your " +#~ "package and" +#~ msgstr "" + +#~ msgid "" +#~ "reference that file in your " +#~ "`pyproject.toml` data where metadata are " +#~ "set." +#~ msgstr "" + +#~ msgid "" +#~ "`hatch config show` will print out " +#~ "the contents of your `config.toml` file" +#~ " in your shell. look at the " +#~ "values and ensure that your name, " +#~ "email is set. Also make sure that" +#~ " `tests=false`." +#~ msgstr "" + +#~ msgid "" +#~ "it will convert metadata stored in " +#~ "a `setup.py` or `setup.cfg` file to " +#~ "a pyproject.toml file for you (see " +#~ "[Migrating setup.py to pyproject.toml using" +#~ " Hatch](setup-py-to-pyproject-toml.md " +#~ "))" +#~ msgstr "" + +#~ msgid "" +#~ "ADD: note about what makes something " +#~ "\"package worthy\", with a common " +#~ "misconception being that a package " +#~ "should be production-ready code that's" +#~ " valuable to a broad audience. this" +#~ " may not be a pervasive misconception" +#~ " in Python, but a quick break-" +#~ "out with an explanation of what a" +#~ " package can consist of would be " +#~ "helpful." +#~ msgstr "" + +#~ msgid "" +#~ "The directory structure you’ll create in" +#~ " this lesson will look like this:" +#~ msgstr "" + +#~ msgid "" +#~ "Where you define your project’s metadata" +#~ " (including its name, authors, license, " +#~ "etc)" +#~ msgstr "" + +#~ msgid "" +#~ "If you aren’t familiar with docstrings" +#~ " or typing yet, that is ok. You" +#~ " can review [this page in the " +#~ "pyOpenSci packaging guide](https://www.pyopensci.org" +#~ "/python-package-guide/documentation/write-user-" +#~ "documentation/document-your-code-api-" +#~ "docstrings.html) for an overview of both" +#~ " topics." +#~ msgstr "" + +#~ msgid "" +#~ "Once you have your project metadata " +#~ "in the pyproject.toml file, you will " +#~ "rarely update it. In the next " +#~ "lesson you’ll add more metadata and " +#~ "structure to this file." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "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." +#~ msgstr "" + +#~ msgid "" +#~ "There is currently a small bug in" +#~ " Grayskull where it doesn't populate " +#~ "the home: element of the recipe. " +#~ "if you don't include this, [you " +#~ "will receive an error " +#~ "message](https://github.com/conda-forge/staged-" +#~ "recipes/pull/25173#issuecomment-1917916528) from the " +#~ "friendly conda-forge linter bot." +#~ msgstr "" + +#~ msgid "" +#~ "In a future lesson, you will learn" +#~ " how to create an automated GitHub" +#~ " action workflow that publishes an " +#~ "updated version of your package to " +#~ "PyPI every time you create a " +#~ "GitHub release." +#~ msgstr "" + +#~ msgid "" +#~ "You can also create an automated " +#~ "publication workflow on GitHub using " +#~ "GitHub actions. This is a great " +#~ "way to make the publication process " +#~ "easier and it also supports a " +#~ "growing maintainer team. In this case" +#~ " we suggest you don't worry about " +#~ "the token and instead setup a " +#~ "specific GitHub action that publishes " +#~ "your package when you make a " +#~ "release. You can then create a " +#~ "\"trusted publisher\" workflow on PyPI." +#~ msgstr "" + +#~ msgid "" +#~ "When you are adding classifiers to " +#~ "the **[project]** table, only use valid" +#~ " values from [PyPI’s classifier " +#~ "page](https://PyPI.org/classifiers/). An invalid " +#~ "value here will raise an error " +#~ "when you build and publish your " +#~ "package on PyPI." +#~ msgstr "" From d42497516a79707f070729414c70d2eee897d9be Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Mon, 26 Aug 2024 11:47:21 -0700 Subject: [PATCH 3/5] better print messages --- .github/workflows/i18n.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/i18n.yaml b/.github/workflows/i18n.yaml index 9b3e1844..7a9e2944 100644 --- a/.github/workflows/i18n.yaml +++ b/.github/workflows/i18n.yaml @@ -29,10 +29,10 @@ jobs: run: | if [ -z "$(git status --porcelain)" ]; then - echo "No changes detected" + echo "No changes detected, translations are up to date!" >> $GITHUB_STEP_SUMMARY exit 0 else - echo "Changes to models detected" + echo "Changes to .po files detected, please run `nox -s update-translations` to reflect changes to source text" >> $GITHUB_STEP_SUMMARY echo "$(git status)" echo "$(git diff)" exit 1 From e023e7f3d1189c09705211b361c4cceff8d920bc Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Tue, 1 Oct 2024 14:04:23 -0700 Subject: [PATCH 4/5] update to new nox session name --- .github/workflows/i18n.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/i18n.yaml b/.github/workflows/i18n.yaml index 7a9e2944..28fe71ec 100644 --- a/.github/workflows/i18n.yaml +++ b/.github/workflows/i18n.yaml @@ -23,7 +23,7 @@ jobs: run: python3 -m pip install nox - name: Update .po files - run: nox -s update-translations + run: nox -s update-release-languages - name: Test for uncommitted changes run: | From 5b34effdc69a96e8563ebeb7906d36d1b79ea9e7 Mon Sep 17 00:00:00 2001 From: sneakers-the-rat Date: Tue, 1 Oct 2024 19:00:25 -0700 Subject: [PATCH 5/5] Revert "update .po files" This reverts commit 0463f0066e3e3ed506225356ec20c409ba5938f0. --- locales/es/LC_MESSAGES/CONTRIBUTING.po | 567 ++--------- locales/es/LC_MESSAGES/TRANSLATING.po | 44 +- locales/es/LC_MESSAGES/documentation.po | 204 ++-- locales/es/LC_MESSAGES/index.po | 145 ++- .../es/LC_MESSAGES/package-structure-code.po | 910 +++++++----------- locales/es/LC_MESSAGES/tests.po | 20 +- locales/es/LC_MESSAGES/tutorials.po | 548 ++--------- locales/ja/LC_MESSAGES/CONTRIBUTING.po | 553 ++--------- locales/ja/LC_MESSAGES/TRANSLATING.po | 44 +- locales/ja/LC_MESSAGES/documentation.po | 77 +- locales/ja/LC_MESSAGES/index.po | 65 +- .../ja/LC_MESSAGES/package-structure-code.po | 302 +----- locales/ja/LC_MESSAGES/tests.po | 60 +- locales/ja/LC_MESSAGES/tutorials.po | 194 +--- 14 files changed, 881 insertions(+), 2852 deletions(-) diff --git a/locales/es/LC_MESSAGES/CONTRIBUTING.po b/locales/es/LC_MESSAGES/CONTRIBUTING.po index 5bd8a3bb..b2a801f4 100644 --- a/locales/es/LC_MESSAGES/CONTRIBUTING.po +++ b/locales/es/LC_MESSAGES/CONTRIBUTING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-07-03 16:27-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../CONTRIBUTING.md:4 msgid "Contributing to the Python Packaging Guide" @@ -119,481 +119,182 @@ msgstr "" #: ../../CONTRIBUTING.md:35 msgid "" "Independently of the approach you choose, the first step is to fork the " -"Python Packaging Guide repository into your personal GitHub space. You " -"can do this by clicking the \"Fork\" button in the top right corner of " -"the repository page." +"Python Packaging Guide repository into your personal GitHub space." msgstr "" -#: ../../CONTRIBUTING.md:38 +#: ../../CONTRIBUTING.md:37 msgid "" -"[Learn more: Fork and Clone GitHub " -"Repos](https://datascienceskills.org/lessons/git-github/git-intro/3-fork-" -"clone/) is a good resource to learn more about forking." +"*__TODO__: This section should show a beginner user how to fork a " +"repository in GitHub.*" msgstr "" -#: ../../CONTRIBUTING.md:40 -msgid "To fork a repo," -msgstr "" - -#: ../../CONTRIBUTING.md:42 -msgid "Make sure you are logged into GitHub." -msgstr "" - -#: ../../CONTRIBUTING.md:44 -msgid "" -"Go to the repo you would like to fork, in this case the [Python Packaging" -" Guide](https://www.github.com/pyopensci/python-package-guide) repo." -msgstr "" - -#: ../../CONTRIBUTING.md:46 -msgid "" -"In the top right-hand corner of the page there is a 'Fork' button. Click " -"that button. You will be brought to a new page where you will 'Create a " -"new fork'. Feel free to keep all the default inputs and click 'Create " -"fork'. This will create a copy of the repo at " -"`https://github.com//python-package-guide`, where `` " -"is your GitHub username." -msgstr "" - -#: ../../CONTRIBUTING.md:51 +#: ../../CONTRIBUTING.md:39 msgid "Contributing via the GitHub website" msgstr "" -#: ../../CONTRIBUTING.md:53 +#: ../../CONTRIBUTING.md:41 msgid "How to edit a MarkDown file" msgstr "" -#: ../../CONTRIBUTING.md:55 -msgid "" -"The Python Packaging Guide is written in myST, a variant of MarkDown. You" -" can edit the files directly in the GitHub website. To do so, navigate to" -" the file you want to edit and click the pencil icon in the top right " -"corner of the file." -msgstr "" - -#: ../../CONTRIBUTING.md:58 -msgid "Edit button in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:64 -msgid "" -"An image showing how to edit a file in GitHub. The pencil icon is " -"highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:66 -msgid "Edit file in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:72 +#: ../../CONTRIBUTING.md:43 msgid "" -"An image showing when a file is being edited in GitHub. The file content " -"is displayed in a text editor." -msgstr "" - -#: ../../CONTRIBUTING.md:75 -msgid "To preview your changes, click the \"Preview changes\" tab." +"*__TODO__: This section should show how to use the GitHub interface to " +"edit and previewing a Markdown file.*" msgstr "" -#: ../../CONTRIBUTING.md:77 -msgid "Preview changes in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:83 -msgid "" -"An image showing how to preview changes in GitHub. The file content is " -"displayed in a text editor. The preview changes tab is highlighted with a" -" red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:86 +#: ../../CONTRIBUTING.md:45 msgid "How to commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:88 -msgid "" -"When you are done editing the file, scroll down to the bottom of the " -"page. You will see a section called \"Commit changes\". Here you can " -"write a title and a description for your changes. Make sure to write a " -"clear and concise title that describes the changes you made." -msgstr "" - -#: ../../CONTRIBUTING.md:91 -msgid "Commit changes in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:97 -msgid "" -"An image showing how to commit changes in GitHub. The commit message is " -"displayed in a text editor. The commit changes section is highlighted " -"with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:100 +#: ../../CONTRIBUTING.md:47 msgid "" -"After writing your commit message, click the \"Commit changes\" button to" -" save your changes." +"*__TODO__: This section should show how to commit changes via the GitHub " +"interface.*" msgstr "" -#: ../../CONTRIBUTING.md:102 +#: ../../CONTRIBUTING.md:49 msgid "Contributing locally on your computer" msgstr "" -#: ../../CONTRIBUTING.md:104 +#: ../../CONTRIBUTING.md:51 msgid "Clone your forked repository" msgstr "" -#: ../../CONTRIBUTING.md:106 -msgid "" -"To clone your forked repository to your computer, you need to copy the " -"URL of your forked repository and run the following command in your " -"terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:111 -msgid "" -"Replace `` with the URL of your forked repository. You can find the " -"URL by clicking the green \"Code\" button on your forked repository page." -msgstr "" - -#: ../../CONTRIBUTING.md:113 -msgid "Clone repository in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:119 +#: ../../CONTRIBUTING.md:53 msgid "" -"An image showing how to clone a repository in GitHub. The URL of the " -"repository is displayed in a text editor. The code button is highlighted " -"with a red rectangle." +"*__TODO__: This section should show how to clone a repository from GitHub" +" into your computer.*" msgstr "" -#: ../../CONTRIBUTING.md:122 +#: ../../CONTRIBUTING.md:55 msgid "Create a new branch" msgstr "" -#: ../../CONTRIBUTING.md:124 -msgid "" -"Before making any changes, you should create a new branch to work on. " -"This will help keep your changes separate from the main branch and make " -"it easier to submit a pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:126 -msgid "To create a new branch, run the following command in your terminal:" +#: ../../CONTRIBUTING.md:57 +msgid "*__TODO__: This section should show how to create a new branch.*" msgstr "" -#: ../../CONTRIBUTING.md:132 +#: ../../CONTRIBUTING.md:59 msgid "Create a virtual environment" msgstr "" -#: ../../CONTRIBUTING.md:134 +#: ../../CONTRIBUTING.md:61 msgid "" -"To build the guide locally, you need to create a virtual environment and " -"install the dependencies. You can do this by running the following " -"commands in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:136 -msgid "**On Windows**:" -msgstr "" - -#: ../../CONTRIBUTING.md:142 -msgid "**On MacOS and Linux**:" +"*__TODO__: This section should show how to create a virtual environment " +"using venv.*" msgstr "" -#: ../../CONTRIBUTING.md:148 +#: ../../CONTRIBUTING.md:63 msgid "Install the development dependencies" msgstr "" -#: ../../CONTRIBUTING.md:150 +#: ../../CONTRIBUTING.md:65 msgid "" -"To install the development dependencies, run the following command in " -"your terminal:" +"*__TODO__: This section should show how to install the development " +"dependencies defined in pyproject.toml.*" msgstr "" -#: ../../CONTRIBUTING.md:156 +#: ../../CONTRIBUTING.md:67 msgid "Commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:158 -msgid "" -"After making your changes, you need to commit them to your local " -"repository. To do this, run the following commands in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:160 -msgid "To see the changes you made:" -msgstr "" - -#: ../../CONTRIBUTING.md:164 -msgid "To add the changes to the staging area:" -msgstr "" - -#: ../../CONTRIBUTING.md:168 -msgid "To commit the changes:" -msgstr "" - -#: ../../CONTRIBUTING.md:172 +#: ../../CONTRIBUTING.md:69 msgid "" -"Replace `\"Your commit message here\"` with a clear and concise message " -"that describes the changes you made." +"*__TODO__: This section should describe how to commit from the command " +"line.*" msgstr "" -#: ../../CONTRIBUTING.md:174 +#: ../../CONTRIBUTING.md:71 msgid "How to build the guide locally" msgstr "" -#: ../../CONTRIBUTING.md:176 +#: ../../CONTRIBUTING.md:73 msgid "" -"To build the guide locally, you can use the `nox` command. This will run " -"the default `nox` session, which builds the guide and opens it in your " -"browser." +"*__TODO__: This section should describe the different sessions in nox " +"related to building the docs: docs, docs-test, docs-live. It should also " +"show how to see the guide built locally, by opening the right file in the" +" browser or using the live version from docs-live*" msgstr "" -#: ../../CONTRIBUTING.md:178 -msgid "" -"To see the different sessions available, you can run the following " -"command in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:183 -msgid "" -"There are different sessions in nox related to building the docs: `docs`," -" `docs-test`, `docs-live`. You can run them by specifying the session " -"name after the `nox` command." -msgstr "" - -#: ../../CONTRIBUTING.md:185 -msgid "`docs`: this session builds the guide and opens it in your browser." -msgstr "" - -#: ../../CONTRIBUTING.md:189 -msgid "" -"To see the guide built locally, open the file `_build/html/index.html` in" -" your browser." -msgstr "" - -#: ../../CONTRIBUTING.md:191 -msgid "`docs-test`: this session runs the tests for the guide." -msgstr "" - -#: ../../CONTRIBUTING.md:195 -msgid "" -"If the tests fail, you will see an error message in your terminal. You " -"need to fix the errors before submitting your pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:197 -msgid "" -"`docs-live`: this session builds the guide and opens it in your browser " -"with live reloading." -msgstr "" - -#: ../../CONTRIBUTING.md:201 -msgid "" -"open the local version of the guide in your browser at ``localhost`` " -"shown in the terminal." -msgstr "" - -#: ../../CONTRIBUTING.md:203 +#: ../../CONTRIBUTING.md:75 msgid "Before you submit your pull request" msgstr "" -#: ../../CONTRIBUTING.md:205 -msgid "" -"Before submitting your pull request, make sure to run the tests and check" -" the formatting of your code." -msgstr "" - -#: ../../CONTRIBUTING.md:210 +#: ../../CONTRIBUTING.md:77 msgid "" -"If the tests fail, you will see an error message in your terminal. You " -"need to fix the errors before submitting your pull request. Also make " -"sure to check the formatting of your documentation by building the docs " -"locally and checking that your changes look correct." +"*__TODO__: This section should describe what steps a user should follow " +"before submitting the pull request: build the docs, verify your changes " +"look correct, etc.*" msgstr "" -#: ../../CONTRIBUTING.md:214 +#: ../../CONTRIBUTING.md:79 msgid "Submitting a pull request with your contribution" msgstr "" -#: ../../CONTRIBUTING.md:216 +#: ../../CONTRIBUTING.md:81 msgid "How to make a pull request" msgstr "" -#: ../../CONTRIBUTING.md:218 -msgid "" -"To open a pull request on GitHub, navigate to the main page of your " -"forked repository and click on the \"Pull requests\" tab." -msgstr "" - -#: ../../CONTRIBUTING.md:220 -msgid "Pull requests tab in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:226 -msgid "" -"An image showing how to navigate to the pull requests tab in GitHub. The " -"pull requests tab is highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:229 -msgid "Click on the \"New pull request\" button." -msgstr "" - -#: ../../CONTRIBUTING.md:231 -msgid "New pull request button in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:237 -msgid "" -"An image showing how to create a new pull request in GitHub. The new pull" -" request button is highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:240 +#: ../../CONTRIBUTING.md:83 msgid "" -"Write a clear and concise title and description for your pull request. " -"Make sure to describe the changes you made and why they are necessary." +"*__TODO__: This section should describe how to make a pull request in " +"GitHub.*" msgstr "" -#: ../../CONTRIBUTING.md:242 +#: ../../CONTRIBUTING.md:85 msgid "What happens when you submit a pull request (CI/CD)" msgstr "" -#: ../../CONTRIBUTING.md:244 -msgid "" -"Once you submit a pull request, a series of checks will be run to ensure " -"that your changes do not introduce any bugs or errors. These checks " -"include:" -msgstr "" - -#: ../../CONTRIBUTING.md:246 +#: ../../CONTRIBUTING.md:87 msgid "" -"**Code formatting and styles**: checks that your code is formatted " -"correctly, by `pre-commit.ci - pr check`." +"*__TODO__: This section should describe how to see the results of the " +"CD/CI checks and how to get more information about errors*" msgstr "" -#: ../../CONTRIBUTING.md:247 -msgid "" -"**docs build**: checks that the documentation builds correctly, using " -"`circleci`." -msgstr "" - -#: ../../CONTRIBUTING.md:249 -msgid "You will see the status of these checks in your pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:251 -msgid "Pull request checks in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:257 -msgid "" -"An image showing the status of the checks in a pull request in GitHub. " -"The checks are displayed in a table with a status icon next to each " -"check. The checks are highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:259 -msgid "" -"If any of these checks fail, you will see an error message in your pull " -"request. You need to fix the errors before your changes can be merged." -msgstr "" - -#: ../../CONTRIBUTING.md:261 -msgid "Pull request checks failed in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:267 -msgid "" -"An image showing the status of the checks in a pull request in GitHub. " -"The checks are displayed in a table with a status icon next to each " -"check. The checks that failed and the details link are highlighted with a" -" red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:270 -msgid "" -"To get more information about the errors, you can click on the " -"\"Details\" link next to the failed check." -msgstr "" - -#: ../../CONTRIBUTING.md:272 +#: ../../CONTRIBUTING.md:89 msgid "What to expect from the review process" msgstr "" -#: ../../CONTRIBUTING.md:274 -msgid "" -"Once you submit a pull request, a maintainer of the repository will " -"review your changes and provide feedback. The review process may involve:" -msgstr "" - -#: ../../CONTRIBUTING.md:276 -msgid "" -"**Comments**: the reviewer may leave comments on your pull request to ask" -" questions or provide feedback." -msgstr "" - -#: ../../CONTRIBUTING.md:277 -msgid "" -"**Suggestions**: the reviewer may suggest changes to your code or " -"documentation." -msgstr "" - -#: ../../CONTRIBUTING.md:278 -msgid "" -"**Approvals**: once the reviewer is satisfied with your changes, they " -"will approve the pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:280 -msgid "" -"You can make changes to your pull request by pushing new commits to the " -"branch. The pull request will be updated automatically with your new " -"changes." -msgstr "" - -#: ../../CONTRIBUTING.md:282 +#: ../../CONTRIBUTING.md:91 msgid "" -"Once your pull request is approved, it will be merged into the main " -"branch and your changes will be included in the guide." +"*__TODO__: This section should describe how review happens in GitHub, how" +" see the comments, and how to submit changes (push a new branch)*" msgstr "" -#: ../../CONTRIBUTING.md:284 +#: ../../CONTRIBUTING.md:93 msgid "Additional help" msgstr "" -#: ../../CONTRIBUTING.md:286 +#: ../../CONTRIBUTING.md:95 msgid "How to get help" msgstr "" -#: ../../CONTRIBUTING.md:288 +#: ../../CONTRIBUTING.md:97 msgid "" "*__TODO__: This section should describe the options for finding more help" " in case beginner contributors need more help (e.g., create an issue, " "post in a forum, etc).*" msgstr "" -#: ../../CONTRIBUTING.md:290 +#: ../../CONTRIBUTING.md:99 msgid "Additional resources" msgstr "" -#: ../../CONTRIBUTING.md:292 +#: ../../CONTRIBUTING.md:101 msgid "" "*__TODO__: It should also include links to beginner documentation, like " "the GitHub docs.*" msgstr "" -#: ../../CONTRIBUTING.md:294 +#: ../../CONTRIBUTING.md:103 msgid "Annex" msgstr "" -#: ../../CONTRIBUTING.md:296 +#: ../../CONTRIBUTING.md:105 msgid "Code examples" msgstr "" -#: ../../CONTRIBUTING.md:298 +#: ../../CONTRIBUTING.md:107 msgid "" "This guide uses the [literalinclude Sphinx directive](https://www.sphinx-" "doc.org/en/master/usage/restructuredtext/directives.html#directive-" @@ -601,18 +302,18 @@ msgid "" "for use in the documentation is kept in the `examples/` folder." msgstr "" -#: ../../CONTRIBUTING.md:302 +#: ../../CONTRIBUTING.md:111 msgid "Referencing code in documentation" msgstr "" -#: ../../CONTRIBUTING.md:304 +#: ../../CONTRIBUTING.md:113 msgid "" "If an example is present elsewhere in the documentation that you want to " "use, you can copy the `literalinclude` directive verbatim and the " "examples will stay in sync." msgstr "" -#: ../../CONTRIBUTING.md:307 +#: ../../CONTRIBUTING.md:116 msgid "" "If you already see code in the examples folder that you can use for new " "documentation, a new `literalinclude` can be made to extract it into the " @@ -622,7 +323,7 @@ msgid "" "the later can protect your example from future modifications to the code." msgstr "" -#: ../../CONTRIBUTING.md:312 +#: ../../CONTRIBUTING.md:121 msgid "" "**Pro tip**: As an alternative to `:lines:` there are also the `:start-" "after:`, `:start-at:`, `:end-before:`, and `:end-at:` options. And if the" @@ -630,17 +331,17 @@ msgid "" "way to keep the same documentation content even through code refactors." msgstr "" -#: ../../CONTRIBUTING.md:316 +#: ../../CONTRIBUTING.md:125 msgid "" "If you need example code that doesn't yet exist in `examples/` see " -"[creating code for documentation](#creating-code-for-documentation)." +"creating code for documentation](#creating-code-for-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:319 +#: ../../CONTRIBUTING.md:128 msgid "Creating code for documentation" msgstr "" -#: ../../CONTRIBUTING.md:321 +#: ../../CONTRIBUTING.md:130 msgid "" "Whenever you come across a place that could benefit from a code block, " "instead of writing it in-line with a code fence (`` ``` `` blocked text) " @@ -649,7 +350,7 @@ msgid "" "code-in-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:325 +#: ../../CONTRIBUTING.md:134 msgid "" "If you want to add a new example that doesn't fit into any of the " "existing example files, you can create a new file and reference it in a " @@ -658,7 +359,7 @@ msgid "" "create a new folder in the `examples` directory." msgstr "" -#: ../../CONTRIBUTING.md:329 +#: ../../CONTRIBUTING.md:138 msgid "" "If an existing example is incomplete or a new example makes sense to be " "added to an existing file, go ahead and add it, but take care to not " @@ -667,14 +368,14 @@ msgid "" "file, new methods after all existing ones in a class." msgstr "" -#: ../../CONTRIBUTING.md:333 +#: ../../CONTRIBUTING.md:142 msgid "" "Example code is checked for correctness, so adding a new example may " "require adding additional tests for coverage, and will require fixing any" " failing tests." msgstr "" -#: ../../CONTRIBUTING.md:336 +#: ../../CONTRIBUTING.md:145 msgid "" "***⚠️ WARNING***: great care should be taken when modifying existing " "example code, especially any modification beyond appending to the end of " @@ -685,127 +386,29 @@ msgid "" "and then checking those pages in a new build." msgstr "" -#: ../../CONTRIBUTING.md:344 +#: ../../CONTRIBUTING.md:153 msgid "Example:" msgstr "" -#: ../../CONTRIBUTING.md:346 +#: ../../CONTRIBUTING.md:155 msgid "Instead of writing example code in markdown like this" msgstr "" -#: ../../CONTRIBUTING.md:357 +#: ../../CONTRIBUTING.md:166 msgid "The python can be extracted into a `.py` file" msgstr "" -#: ../../CONTRIBUTING.md:371 +#: ../../CONTRIBUTING.md:180 msgid "" "As another example, if you only need to show part of a `pyproject.toml`, " "we already have complete project definitions, you need only to find the " "relevant part." msgstr "" -#: ../../CONTRIBUTING.md:374 +#: ../../CONTRIBUTING.md:183 msgid "Instead of writing this" msgstr "" -#: ../../CONTRIBUTING.md:386 +#: ../../CONTRIBUTING.md:195 msgid "an example could be extracted from an existing toml file" msgstr "" - -#~ msgid "" -#~ "Independently of the approach you " -#~ "choose, the first step is to fork" -#~ " the Python Packaging Guide repository " -#~ "into your personal GitHub space." -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show a" -#~ " beginner user how to fork a " -#~ "repository in GitHub.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to use the GitHub interface to " -#~ "edit and previewing a Markdown file.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to commit changes via the GitHub " -#~ "interface.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to clone a repository from GitHub" -#~ " into your computer.*" -#~ msgstr "" - -#~ msgid "*__TODO__: This section should show how to create a new branch.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to create a virtual environment " -#~ "using venv.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to install the development dependencies" -#~ " defined in pyproject.toml.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to commit from the command " -#~ "line.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "the different sessions in nox related" -#~ " to building the docs: docs, docs-" -#~ "test, docs-live. It should also " -#~ "show how to see the guide built" -#~ " locally, by opening the right file" -#~ " in the browser or using the " -#~ "live version from docs-live*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "what steps a user should follow " -#~ "before submitting the pull request: " -#~ "build the docs, verify your changes " -#~ "look correct, etc.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to make a pull request in " -#~ "GitHub.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to see the results of the " -#~ "CD/CI checks and how to get more" -#~ " information about errors*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how review happens in GitHub, how " -#~ "see the comments, and how to " -#~ "submit changes (push a new branch)*" -#~ msgstr "" - -#~ msgid "" -#~ "If you need example code that " -#~ "doesn't yet exist in `examples/` see " -#~ "creating code for documentation](#creating-" -#~ "code-for-documentation)." -#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/TRANSLATING.po b/locales/es/LC_MESSAGES/TRANSLATING.po index 29880ca9..9c147e7c 100644 --- a/locales/es/LC_MESSAGES/TRANSLATING.po +++ b/locales/es/LC_MESSAGES/TRANSLATING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-07-03 16:27-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../TRANSLATING.md:5 msgid "Translation Guide for the Python Packaging Guide" @@ -165,9 +165,8 @@ msgstr "" #: ../../TRANSLATING.md:68 msgid "" -"You can find a list of the two-letter Sphinx language option " -"[here](https://www.sphinx-doc.org/en/master/usage/configuration.html" -"#confval-language)." +"You can find a list of the two-letter ISO language codes " +"[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." msgstr "" #: ../../TRANSLATING.md:71 @@ -427,7 +426,7 @@ msgid "" "Note the `--` before the language code, it indicates that the following " "arguments should be passed into the nox session and not be interpreted " "directly by nox. If you forget the `--`, nox will look instead for a " -"session named 'es' and raise an error that it does not exist." +"session named 'es' and complain that it does not exist." msgstr "" #: ../../TRANSLATING.md:241 @@ -497,7 +496,7 @@ msgid "" msgstr "" #: ../../TRANSLATING.md:268 -msgid "TODO: This tagging could be automated with a GitHub Actions." +msgid "TODO: This tagging could be automated with a GitHub action." msgstr "" #: ../../TRANSLATING.md:270 @@ -706,7 +705,8 @@ msgstr "" #: ../../TRANSLATING.md:343 msgid "" "If you have any questions or need help with your translation, you can " -"create an issue in the repository." +"create an issue in the repository if you encounter any problems or need " +"assistance." msgstr "" #: ../../TRANSLATING.md:345 @@ -715,31 +715,3 @@ msgid "" " as a way for contributors to ask for help with translations or the " "translation workflow?" msgstr "" - -#~ msgid "" -#~ "You can find a list of the " -#~ "two-letter ISO language codes " -#~ "[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." -#~ msgstr "" - -#~ msgid "" -#~ "Note the `--` before the language " -#~ "code, it indicates that the following" -#~ " arguments should be passed into the" -#~ " nox session and not be interpreted" -#~ " directly by nox. If you forget " -#~ "the `--`, nox will look instead " -#~ "for a session named 'es' and " -#~ "complain that it does not exist." -#~ msgstr "" - -#~ msgid "TODO: This tagging could be automated with a GitHub action." -#~ msgstr "" - -#~ msgid "" -#~ "If you have any questions or need" -#~ " help with your translation, you can" -#~ " create an issue in the repository" -#~ " if you encounter any problems or " -#~ "need assistance." -#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/documentation.po b/locales/es/LC_MESSAGES/documentation.po index 922e0dee..a94cd7d6 100644 --- a/locales/es/LC_MESSAGES/documentation.po +++ b/locales/es/LC_MESSAGES/documentation.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-26 09:16-0700\n" +"POT-Creation-Date: 2024-06-28 08:42-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../documentation/hosting-tools/intro.md:1 msgid "Tools to Build and Host your Documentation" @@ -33,9 +33,8 @@ msgid "" msgstr "" "Sphinx es la herramienta más común para construir documentación en el " "ecosistema de Python. Sin embargo, algunos mantenedores están usando " -"herramientas como [mkdocs](https://www.mkdocs.org/) para generar la " -"documentación. ¡Es tu decisión usar la herramienta que prefieras para tu " -"documentación!" +"herramientas como [mkdocs](https://www.mkdocs.org/) para generar la documentación. ¡Es tu " +"decisión usar la herramienta que prefieras para tu documentación!" #: ../../documentation/hosting-tools/intro.md:8 msgid "" @@ -44,16 +43,16 @@ msgid "" " writing Sphinx documentation including mySt and rST." msgstr "" "En esta sección introducimos Sphinx como herramienta para construir " -"documentación. Hablamos sobre varias opciones de sintaxis que puedes usar" -" para escribir documentación de Sphinx incluyendo myST and rST." +"documentación. Hablamos sobre varias opciones de sintaxis que puedes usar " +"para escribir documentación de Sphinx incluyendo myST and rST." #: ../../documentation/hosting-tools/intro.md:12 msgid "" "We also talk about ways to publish your documentation online and Sphinx " "tools that might help you optimize your documentation website." msgstr "" -"Hablamos también sobre methodos para publicar tu documentación en línea y" -" herramientas de Sphinx que pueda ayudarte optimizar tu sitio web para " +"Hablamos también sobre methodos para publicar tu documentación en línea " +"y herramientas de Sphinx que pueda ayudarte optimizar tu sitio web para " "documentación." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:1 @@ -74,13 +73,13 @@ msgid "" " blocks and other custom elements to your documentation, you will need to" " use either **myST** or **rST**." msgstr "" -"[markdown](https://www.markdownguide.org/): Markdown es una sintaxis de " -"texto plano que es fácil aprender. Es la sintaxis por defecto para " -"Jupyter Notebooks. Hay herramientas que puedes usar con Sphinx que " -"permiten renderizar markdown como HTML. Sin embargo, usar markdown para " -"escribir documentación tiene limitaciones. Por ejemplo, si deseas añadir " -"referencias, tarjetas de colores, u otros elementos personalizados a tu " -"documentación, necesitarás usar **myST** o **rST**." +"[markdown](https://www.markdownguide.org/): Markdown es una sintaxis de texto plano " +"que es fácil aprender. Es la sintaxis por defecto para Jupyter Notebooks. Hay " +"herramientas que puedes usar con Sphinx que permiten renderizar " +"markdown como HTML. Sin embargo, usar markdown para escribir documentación " +"tiene limitaciones. Por ejemplo, si deseas añadir referencias, tarjetas " +"de colores, u otros elementos personalizados a tu documentación, necesitarás " +"usar **myST** o **rST**." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:8 msgid "" @@ -99,18 +98,17 @@ msgstr "" "flexibilidad." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:9 -#, fuzzy msgid "" "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is " -"a combination of `markdown` and `rST` syntax. It is a nice option if you " -"are comfortable writing markdown. `myst` is preferred by many because it " -"offers both the rich functionality of rST combined with a simple-to-write" -" markdown syntax." -msgstr "" -"[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST es " -"una combinación de `markdown` y `rST`. Es una opción buena si te sientes " -"cómodo escribiendo markdown. `myst` es preferido por mucha gente dado que" -" ofrece la amplia funcionalidad de rST en combinación con la sintaxis " +"a combination of vanilla of `markdown` and `rST` syntax. It is a nice " +"option if you are comfortable writing markdown. `myst` is preferred by " +"many because it offers both the rich functionality of rST combined with a" +" simple-to-write markdown syntax." +msgstr "" +"[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST es una " +"combinación de `markdown` y `rST`. Es una opción buena si te sientes " +"cómodo escribiendo markdown. `myst` es preferido por mucha gente dado que " +"ofrece la amplia funcionalidad de rST en combinación con la sintaxis " "fácil de markdown." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:12 @@ -138,8 +136,8 @@ msgid "" "Most of your core Python package text files, such as your README.md file," " are already in `.md` format" msgstr "" -"La mayoría de los archivos de texto de tus paquetes principales de " -"Python, como el archivo README.md, ya están en formato `.md`." +"La mayoría de los archivos de texto de tus paquetes principales de Python, " +"como el archivo README.md, ya están en formato `.md`." #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:18 msgid "" @@ -154,8 +152,8 @@ msgid "" "If you are on the fence about myST vs rst, you might find that **myST** " "is easier for more people to contribute to." msgstr "" -"Si no estás seguro sobre si utilizar myST o rst, puede que encuentres que" -" **myST** es más fácil para contribuciones de más gente." +"Si no estás seguro sobre si utilizar myST o rst, puede que encuentres que " +"**myST** es más fácil para contribuciones de más gente." #: ../../documentation/hosting-tools/publish-documentation-online.md:1 msgid "How to publish your Python package documentation online" @@ -167,10 +165,9 @@ msgid "" "documentation. Two free and commonly used ways to quickly create a " "documentation website hosting environment are below." msgstr "" -"Sugerimos que utilizas un servicio de hosting para la documentación de tu" -" paquete de Python. Abajo encontrarás dos métodos gratuitos y comúnes " -"para servir tu documentación en un sitio web." - +"Sugerimos que utilizas un servicio de hosting para la documentación de tu " +"paquete de Python. Abajo encontrarás dos métodos gratuitos y comúnes para servir " +"tu documentación en un sitio web." #: ../../documentation/hosting-tools/publish-documentation-online.md:7 msgid "" "You can host your documentation yourself using [GitHub " @@ -196,24 +193,24 @@ msgid "" "[Read the Docs](https://readthedocs.org/) is a documentation hosting " "service that supports publishing your project's documentation." msgstr "" -"[Read the Docs](https://readthedocs.org/) es un servicio de hosting que " -"permite publicar la documentación de tu proyecto." +"[Read the Docs](https://readthedocs.org/) es un servicio de hosting " +"que permite publicar la documentación de tu proyecto." #: ../../documentation/hosting-tools/publish-documentation-online.md:13 msgid "" "Read the Docs is a fully featured, free, documentation hosting service. " "Some of its many features include:" msgstr "" -"Read the Docs es un servicio de hosting de documentación gratuito. " -"Algunas de sus funcionalidades son:" +"Read the Docs es un servicio de hosting de documentación gratuito. Algunas de " +"sus funcionalidades son:" #: ../../documentation/hosting-tools/publish-documentation-online.md:16 msgid "" "Is free to host your documentation (but there are also paid tiers if you " "wish to customize hosting)" msgstr "" -"Permite servir tu documentación de forma gratuita (pero hay opciones de " -"pago si deseas personalizar el hosting)" +"Permite servir tu documentación de forma gratuita (pero hay opciones de pago si deseas " +"personalizar el hosting)" #: ../../documentation/hosting-tools/publish-documentation-online.md:17 msgid "Automates building your documentation" @@ -224,8 +221,8 @@ msgid "" "Allows you to turn on integration with pull requests where you can view " "documentation build progress (success vs failure)." msgstr "" -"Te permite integrar solicitudes de cambio para ver el progreso de " -"construcción de la documentación (éxito vs error)" +"Te permite integrar solicitudes de cambio para ver el progreso de construcción " +"de la documentación (éxito vs error)" #: ../../documentation/hosting-tools/publish-documentation-online.md:19 msgid "" @@ -233,9 +230,8 @@ msgid "" "older tagged versions of the docs if they are using older versions of " "your package." msgstr "" -"Permite versionar tu documentación, lo que permite a los usuarios acceder" -" a versiones antiguas de la documentación en caso de que las estén usando" -" en su paquete. " +"Permite versionar tu documentación, lo que permite a los usuarios acceder a " +"versiones antiguas de la documentación en caso de que las estén usando en su paquete. " #: ../../documentation/hosting-tools/publish-documentation-online.md:20 msgid "Supports downloading of documentation in PDF and other formats." @@ -246,8 +242,8 @@ msgid "" "You can customize the documentation build using a **.readthedocs.yaml** " "file in your GitHub repository." msgstr "" -"Puedes personalizar la construcción de la documentación usando un archivo" -" **.readthedocs.yaml** en tu repositorio de GitHub." +"Puedes personalizar la construcción de la documentación usando un " +"archivo **.readthedocs.yaml** en tu repositorio de GitHub." #: ../../documentation/hosting-tools/publish-documentation-online.md:24 msgid "What is GitHub Pages?" @@ -262,10 +258,10 @@ msgid "" "GitHub repository that is setup to run the GitHub Pages web build." msgstr "" "[GitHub Pages](https://docs.github.com/en/pages/getting-started-with-" -"github-pages/about-github-pages) es un servicio web gratuito de GitHub. " -"Con GitHub Pages, puedes construir tu documentación localmente o " -"utilizando Continuous Integration, y empujar a una rama de tu repositorio" -" de GitHub que esté configurada para construir la web en GitHub Pages." +"github-pages/about-github-pages) es un servicio web gratuito " +"de GitHub. Con GitHub Pages, puedes construir tu documentación localmente " +"o utilizando Continuous Integration, y empujar a una rama de tu repositorio " +"de GitHub que esté configurada para construir la web en GitHub Pages." #: ../../documentation/hosting-tools/publish-documentation-online.md:33 msgid "Read the Docs vs GitHub Pages" @@ -287,10 +283,9 @@ msgid "" "service automates the entire process of building and deploying your " "documentation." msgstr "" -"Read the Docs se puede configurar a través de tu cuenta de Read the Docs." -" El servicio automatiza el proceso de construcción y despliegue de tu " +"Read the Docs se puede configurar a través de tu cuenta de Read the Docs. " +"El servicio automatiza el proceso de construcción y despliegue de tu " "documentación." - #: ../../documentation/hosting-tools/publish-documentation-online.md:42 msgid "" "If you don't want to maintain a documentation website for your Python " @@ -312,13 +307,12 @@ msgid "" "[mkdocs](https://www.mkdocs.org/) which is gaining popularity in the " "Python packaging ecosystem." msgstr "" -"En esta página presentamos como utilizar [Sphinx](https://www.sphinx-" -"doc.org/) para construir la documentación orientada a los usuarios de tu " -"paquete. Aunque Sphinx es la herramienta más común en la ecosistema de " -"Python científico, puedes explorar otras herramientas para construir " -"documentación como [mkdocs](https://www.mkdocs.org/) que está ganando " -"popularidad en el ecosistema de empaquetado de Python." - +"En esta página presentamos como utilizar [Sphinx](https://www.sphinx-doc.org/) " +"para construir la documentación orientada a los usuarios de tu paquete. Aunque " +"Sphinx es la herramienta más común en la ecosistema de Python científico, " +"puedes explorar otras herramientas para construir documentación como " +"[mkdocs](https://www.mkdocs.org/) que está ganando popularidad en el " +"ecosistema de empaquetado de Python." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:25 msgid "Examples of documentation websites that we love:" msgstr "Ejemplos de sitios del web de documentación que nos gustan:" @@ -346,7 +340,6 @@ msgid "" msgstr "" "[Ver página de inicio para verde - archivo rst " ".](https://github.com/fatiando/verde/blob/main/doc/index.rst)" - #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:31 msgid "" "[Here is our documentation if you want to see a myST example of a landing" @@ -370,12 +363,12 @@ msgid "" "\"Statically\" which means that there is no generation or modification of" " the files on the fly." msgstr "" -"Sphinx es un [generador de sitios estáticos](https://www.cloudflare.com" -"/es-es/learning/performance/static-site-generator/). Un generador de " -"sitios estáticos es una herramienta que crea HTML para un sitio web " -"basado en plantillas. Los archivos HTML se sirven \"estáticamente\", lo " -"que significa que no hay generación ni modificación de los archivos en " -"línea." +"Sphinx es un [generador de " +"sitios estáticos](https://www.cloudflare.com/es-es/learning/performance/static-site-" +"generator/). Un generador de sitios estáticos es una herramienta que crea " +"HTML para un sitio web basado en plantillas. Los archivos HTML " +"se sirven \"estáticamente\", lo que significa que no hay generación ni modificación " +"de los archivos en línea." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:39 msgid "Sphinx is written using Python." @@ -383,9 +376,7 @@ msgstr "Sphinx está desarrollado en Python." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:41 msgid "Sphinx sites can be customized using extensions and themes" -msgstr "" -"La documentación creada con Sphinx puede ser personalizada con " -"extensiones y temas" +msgstr "La documentación creada con Sphinx puede ser personalizada con extensiones y temas" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:43 msgid "" @@ -400,8 +391,8 @@ msgid "" "You can apply documentation themes for quick generation of beautiful " "documentation." msgstr "" -"Puedes usar temas de documentación para generación rápida de " -"documentaciónhermosa." +"Puedes usar temas de documentación para generación rápida de documentación" +"hermosa." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:47 msgid "" @@ -410,9 +401,9 @@ msgid "" "autodoc extension](https://www.sphinx-" "doc.org/en/master/usage/extensions/autodoc.html)" msgstr "" -"Puedes [generar automáticamente documentación para las funciones y clases" -" (la API del paquete) desde los docstrings de tu código usando la " -"extensión autodoc](https://www.sphinx-" +"Puedes [generar automáticamente documentación para las funciones y clases " +"(la API del paquete) desde los docstrings de tu código usando la extensión " +"autodoc](https://www.sphinx-" "doc.org/en/master/usage/extensions/autodoc.html)" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:48 @@ -421,8 +412,8 @@ msgid "" "extension](https://www.sphinx-" "doc.org/en/master/usage/extensions/doctest.html)" msgstr "" -"Puedes [ejecutar y probar ejemplos del código en los docstrings usando la" -" extensión doctest](https://www.sphinx-" +"Puedes [ejecutar y probar ejemplos del código en los docstrings usando la " +"extensión doctest](https://www.sphinx-" "doc.org/en/master/usage/extensions/doctest.html)" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:49 @@ -431,10 +422,9 @@ msgid "" "syntax parsers to support easier-to-write syntax using tools such as [the" " MyST parser](https://myst-parser.readthedocs.io/)." msgstr "" -"Aunque Sphinx se basa en sintaxis `rST` de forma nativa, puedes añadir " -"intérpretes de sintaxis personalizadas para usar otras sintaxis más " -"fáciles con herramientas como [MyST](https://myst-" -"parser.readthedocs.io/)." +"Aunque Sphinx se basa en sintaxis `rST` de forma nativa, puedes añadir intérpretes de " +"sintaxis personalizadas para usar otras sintaxis más fáciles con herramientas como " +"[MyST](https://myst-parser.readthedocs.io/)." #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:51 msgid "Commonly used Sphinx themes" @@ -447,8 +437,7 @@ msgid "" "include:" msgstr "" "Puedes usar cualquiera tema de Sphinx que prefieras. Sin embargo, los " -"temas más comúnes utilizados en la comunidad de Python científico " -"incluyen:" +"temas más comúnes utilizados en la comunidad de Python científico incluyen:" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:57 msgid "[pydata-sphinx-theme](https://pydata-sphinx-theme.readthedocs.io/)" @@ -557,10 +546,10 @@ msgid "" "documentation content pages. [The OpenGraph protocol allows other " "websites to provide a useful preview of the content on your page when " "shared](https://www.freecodecamp.org/news/what-is-open-graph-and-how-" -"can-i-use-it-for-my-website/#heading-what-is-open-graph). This is " -"important for when the pages in your documentation are shared on social " -"media sites like Twitter and Mastodon and even for shares on tools like " -"Slack and Discourse." +"can-i-use-it-for-my-website/#what-is-open-graph). This is important for " +"when the pages in your documentation are shared on social media sites " +"like Twitter and Mastodon and even for shares on tools like Slack and " +"Discourse." msgstr "" #: ../../documentation/index.md:3 @@ -1693,8 +1682,8 @@ msgstr "" msgid "" "Once you package is accepted to pyOpenSci, we will provide you with a " "badge to add to your repository that shows that it has been reviewed. " -"[![pyOpenSci](https://pyopensci.org/badges/peer-" -"reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/12)" +"[![pyOpenSci](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci" +"/software-review/issues/12)" msgstr "" #: ../../documentation/repository-files/readme-file-best-practices.md:82 @@ -2336,7 +2325,7 @@ msgstr "" msgid "" "It's important to keep in mind that examples in your docstrings help " "users using your package. Running `doctest` on those examples provides a " -"check of your package's API. The doctest ensures that the functions and " +"check of your package's API. doctest ensures that the functions and " "methods in your package run as you expect them to. Neither of these items" " replace a separate, stand-alone test suite that is designed to test your" " package's core functionality across operating systems and Python " @@ -2655,36 +2644,3 @@ msgstr "" #: ../../documentation/write-user-documentation/intro.md:15 msgid "sphinx gallery for tutorials." msgstr "" - -#~ msgid "" -#~ "OpenGraph is an extension that allows" -#~ " you to add metadata to your " -#~ "documentation content pages. [The OpenGraph" -#~ " protocol allows other websites to " -#~ "provide a useful preview of the " -#~ "content on your page when " -#~ "shared](https://www.freecodecamp.org/news/what-is-open-" -#~ "graph-and-how-can-i-use-it-for-" -#~ "my-website/#what-is-open-graph). This " -#~ "is important for when the pages in" -#~ " your documentation are shared on " -#~ "social media sites like Twitter and " -#~ "Mastodon and even for shares on " -#~ "tools like Slack and Discourse." -#~ msgstr "" - -#~ msgid "" -#~ "It's important to keep in mind " -#~ "that examples in your docstrings help" -#~ " users using your package. Running " -#~ "`doctest` on those examples provides a" -#~ " check of your package's API. doctest" -#~ " ensures that the functions and " -#~ "methods in your package run as you" -#~ " expect them to. Neither of these " -#~ "items replace a separate, stand-alone" -#~ " test suite that is designed to " -#~ "test your package's core functionality " -#~ "across operating systems and Python " -#~ "versions." -#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/index.po b/locales/es/LC_MESSAGES/index.po index f62bbf09..b6a9f610 100644 --- a/locales/es/LC_MESSAGES/index.po +++ b/locales/es/LC_MESSAGES/index.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-06-05 16:34-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Felipe Moreno \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../index.md:283 msgid "Tutorials" @@ -48,9 +48,7 @@ msgstr "La guía de paquetes de Python de pyOpenSci" msgid "" "We support the Python tools that scientists need to create open science " "workflows." -msgstr "" -"Nosotros ayudamos a los científicos a crear flujos de trabajo de ciencia " -"abierta." +msgstr "Nosotros ayudamos a los científicos a crear flujos de trabajo de ciencia abierta." #: ../../index.md:20 msgid "" @@ -81,24 +79,22 @@ msgid "About this guide" msgstr "Sobre esta guía" #: ../../index.md:29 -#, fuzzy msgid "" "Image with the pyOpenSci flower logo in the upper right hand corner. The " "image shows the packaging lifecycle. The graphic shows a high level " -"overview of the elements of a Python package. The inside circle has 5 " +"overview of the elements of a Python package. the inside circle has 5 " "items - user documentation, code/api, test suite, contributor " "documentation, project metadata / license / readme. In the middle of the " -"circle is says maintainers and has a small icon with people. On the " +"circle is says maintainers and has a small icon with people. on the " "outside circle there is an arrow and it says infrastructure." msgstr "" -"Imagen con el logo de la flor de pyOpenSci en la esquina superior " -"derecha. La imagen muestra el ciclo de vida del empaquetado. El gráfico " -"muestra una visión general de los elementos de un paquete de Python. el " -"círculo interior tiene 5 elementos: documentación de usuario, código/api," -" suite de pruebas, documentación de colaboradores, metadatos del proyecto" -" / licencia / readme. El centro del círculo dice mantenedores y tiene un " -"pequeño icono con personas. En el círculo exterior hay una flecha y dice " -"infraestructura." +"Imagen con el logo de la flor de pyOpenSci en la esquina superior derecha. " +"La imagen muestra el ciclo de vida del empaquetado. El gráfico muestra una " +"visión general de los elementos de un paquete de Python. el círculo interior " +"tiene 5 elementos: documentación de usuario, código/api, suite de pruebas, " +"documentación de colaboradores, metadatos del proyecto / licencia / readme. " +"El centro del círculo dice mantenedores y tiene un pequeño icono con personas. " +"En el círculo exterior hay una flecha y dice infraestructura." #: ../../index.md:35 msgid "This guide will help you:" @@ -118,17 +114,13 @@ msgstr "Navegar y tomar decisiones sobre las opciones de las herramientas" #: ../../index.md:40 msgid "Understand all of the pieces of creating and maintaining a Python package" -msgstr "" -"Entender todas las etapas de la creación y mantenimiento de un paquete de" -" Python" +msgstr "Entender todas las etapas de la creación y mantenimiento de un paquete de Python" #: ../../index.md:42 msgid "" "You will also find best practice recommendations and curated lists of " "community resources surrounding packaging and package documentation." -msgstr "" -"Tambien encontrarás recomendaciones y listas de recursos comunitarios " -"sobre empaquetado y documentación de paquetes." +msgstr "Tambien encontrarás recomendaciones y listas de recursos comunitarios sobre empaquetado y documentación de paquetes." #: ../../index.md:46 msgid "Todo" @@ -173,11 +165,10 @@ msgid "" "review process or watch development of future tutorials in our [Github " "repo here](https://github.com/pyOpenSci/python-package-guide)." msgstr "" -"La primera version de nuestra serie de tutoriales de como crear un " -"paquete de Python para científicos está completa! Únete a nuestro proceso" -" de revisión comunitaria o mira el desarrollo de futuros tutoriales en " -"nuestro [repositorio de Github](https://github.com/pyOpenSci/python-" -"package-guide)." +"La primera version de nuestra serie de tutoriales de como crear un paquete " +"de Python para científicos está completa! Únete a nuestro proceso de " +"revisión comunitaria o mira el desarrollo de futuros tutoriales en nuestro " +"[repositorio de Github](https://github.com/pyOpenSci/python-package-guide)." #: ../../index.md:71 msgid "✿ Create a Package Tutorials ✿" @@ -234,8 +225,8 @@ msgid "" "you with your Python packaging needs." msgstr "" "Aprende sobre las mejores prácticas de empaquetado de Python. También " -"conocerás el vibrante ecosistema de herramientas de empaquetado que están" -" disponibles para ayudarte con tus necesidades de empaquetado de Python." +"conocerás el vibrante ecosistema de herramientas de empaquetado que están " +"disponibles para ayudarte con tus necesidades de empaquetado de Python." #: ../../index.md:113 msgid "✨ Create your package ✨" @@ -243,9 +234,7 @@ msgstr "✨ Crea tu paquete ✨" #: ../../index.md:117 msgid "[Package file structure](/package-structure-code/python-package-structure)" -msgstr "" -"[Estructura de archivos de paquete](/package-structure-code/python-" -"package-structure)" +msgstr "[Estructura de archivos de paquete](/package-structure-code/python-package-structure)" #: ../../index.md:118 msgid "" @@ -280,8 +269,8 @@ msgid "" "[Non pure Python builds](package-structure-code/complex-python-package-" "builds.md)" msgstr "" -"[Construcción de paquetes que incluyen otros lenguajes](package-" -"structure-code/complex-python-package-builds.md)" +"[Construcción de paquetes que incluyen otros lenguajes](package-structure-code/complex-python-" +"package-builds.md)" #: ../../index.md:127 msgid "✨ Publish your package ✨" @@ -292,8 +281,8 @@ msgid "" "Gain a better understanding of the Python packaging ecosystem Learn about" " best practices for:" msgstr "" -"Entiende el ecosistema de empaquetado de Python.Aprende sobre las mejores" -" prácticas para:" +"Entiende el ecosistema de empaquetado de Python." +"Aprende sobre las mejores prácticas para:" #: ../../index.md:134 msgid "" @@ -336,8 +325,8 @@ msgid "" "[Write tutorials to show how your package is used](/documentation/write-" "user-documentation/create-package-tutorials)" msgstr "" -"[Escribe tutoriales para mostrar como se usa tu paquete](/documentation" -"/write-user-documentation/create-package-tutorials)" +"[Escribe tutoriales para mostrar como se usa tu paquete](/documentation/write-" +"user-documentation/create-package-tutorials)" #: ../../index.md:158 msgid "✨ Developer Docs ✨" @@ -356,8 +345,8 @@ msgid "" "[Write a development guide](/documentation/repository-files/development-" "guide)" msgstr "" -"[Escribe una guía de desarrollo](/documentation/repository-files" -"/development-guide)" +"[Escribe una guía de desarrollo](/documentation/repository-files/development-" +"guide)" #: ../../index.md:167 msgid "✨ Document For A Community ✨" @@ -368,16 +357,16 @@ msgid "" "[Writing a README file](/documentation/repository-files/readme-file-best-" "practices)" msgstr "" -"[Escribe un archivo README](/documentation/repository-files/readme-file-" -"best-practices)" +"[Escribe un archivo README](/documentation/repository-files/readme-file-best-" +"practices)" #: ../../index.md:171 msgid "" "[Set norms with a Code of Conduct](/documentation/repository-files/code-" "of-conduct-file)" msgstr "" -"[Establece normas con un Código de Conducta](/documentation/repository-" -"files/code-of-conduct-file)" +"[Establece normas con un Código de Conducta](/documentation/repository-files/code-" +"of-conduct-file)" #: ../../index.md:172 msgid "[License your package](/documentation/repository-files/license-files)" @@ -399,17 +388,16 @@ msgstr "[Usando Sphinx](/documentation/hosting-tools/intro)" msgid "" "[Markdown, MyST, and ReST](/documentation/hosting-tools/myst-markdown-" "rst-doc-syntax)" -msgstr "" -"[Markdown, MyST, y ReST](/documentation/hosting-tools/myst-markdown-rst-" -"doc-syntax)" +msgstr "[Markdown, MyST, y ReST](/documentation/hosting-tools/myst-markdown-" +"rst-doc-syntax)" #: ../../index.md:183 msgid "" "[Host your docs on Read The Docs or Github Pages](/documentation/hosting-" "tools/publish-documentation-online)" msgstr "" -"[Publica tu documentación en Read The Docs o Github Pages](/documentation" -"/hosting-tools/publish-documentation-online)" +"[Publica tu documentación en Read The Docs o Github Pages](/documentation/hosting-" +"tools/publish-documentation-online)" #: ../../index.md:189 msgid "" @@ -468,32 +456,31 @@ msgid "" "We welcome contributions to this guide. Learn more about how you can " "contribute." msgstr "" -"Agradecemos las contribuciones a esta guía. Aprende más sobre como puedes" -" contribuir." +"Agradecemos las contribuciones a esta guía. Aprende más sobre como puedes " +"contribuir." #: ../../index.md:246 -#, fuzzy msgid "" "xkcd comic showing a stick figure on the ground and one in the air. The " "one on the ground is saying. `You're flying! how?` The person in the air" " replies `Python!` Below is a 3 rectangle comic with the following text " -"in each box. Box 1 - I learned it last night. Everything is so simple. " -"Hello world is just print hello world. Box 2 - the person on the ground " -"says - come join us programming is fun again. It's a whole new world. But" +"in each box. box 1 - I learned it last night. Everything is so simple. " +"Hello world is just print hello world. box 2 - the person on the ground " +"says - come join us programming is fun again. it's a whole new world. But" " how are you flying? box 3 - the person flying says - i just typed import" " antigravity. I also sampled everything in the medicine cabinet. But i " -"think this is the python. The person on the ground is saying - that's it?" -msgstr "" -"Comic de xkcd mostrando una figura en el suelo y otra en el aire. La que " -"está en el suelo dice: `¡Estás volando! ¿Cómo?` La persona en el aire " -"responde: `¡Python!` Abajo hay un comic de 3 rectángulos con el siguiente" -" texto en cada uno. Rectángulo 1 - Lo aprendí anoche. Todo es tan simple." -" Hello world es solo print hello world. Rectángulo 2 - La persona en el " -"suelo está diciendo - ven y únete, programar es divertido de nuevo. Es un" -" mundo completamente nuevo. Pero ¿cómo estás volando? Rectángulo 3 - La " -"persona que está volando dice - solo escribí import antigravity. También " -"probé todo en el botiquín. Pero creo que esto es Python. La persona en el" -" suelo está diciendo - ¿eso es todo?" +"think this is the python. the person on the ground is saying - that's it?" +msgstr "" +"Comic de xkcd mostrando una figura en el suelo y otra en el aire. " +"La que está en el suelo dice: `¡Estás volando! ¿Cómo?` La persona en el aire " +"responde: `¡Python!` Abajo hay un comic de 3 rectángulos con el siguiente " +"texto en cada uno. Rectángulo 1 - Lo aprendí anoche. Todo es tan simple. " +"Hello world es solo print hello world. Rectángulo 2 - La persona en el suelo " +"está diciendo - ven y únete, programar es divertido de nuevo. Es un mundo " +"completamente nuevo. Pero ¿cómo estás volando? Rectángulo 3 - La persona que " +"está volando dice - solo escribí import antigravity. También probé todo en " +"el botiquín. Pero creo que esto es Python. La persona en el suelo está " +"diciendo - ¿eso es todo?" #: ../../index.md:252 msgid "A community-created guidebook" @@ -506,9 +493,9 @@ msgid "" "we encourage reviews from a diverse set of pythonistas and scientists " "with a wide range of skills and expertise." msgstr "" -"Cada página en esta guía es revisada extensamente por la comunidad. Para " -"asegurar que nuestra guía sea accesible a principiantes y precisa, " -"realizamos revisiones con un conjunto diverso de pythonistas y " +"Cada página en esta guía es revisada extensamente por la " +"comunidad. Para asegurar que nuestra guía sea accesible a principiantes y " +"precisa, realizamos revisiones con un conjunto diverso de pythonistas y " "científicos con una amplia gama de habilidades y experiencia." #: ../../index.md:257 @@ -536,8 +523,8 @@ msgid "" "Resources to help you navigate the Python packaging ecosystem of tools " "and approaches to packaging." msgstr "" -"Recursos para ayudarte a navegar el ecosistema de herramientas y enfoques" -" de empaquetado de Python." +"Recursos para ayudarte a navegar el ecosistema de herramientas y enfoques " +"de empaquetado de Python." #: ../../index.md:271 msgid "" @@ -558,8 +545,7 @@ msgid "" "GitHub.](https://github.com/pyOpenSci/python-package-guide/issues)." msgstr "" "Si tienes ideas de cosas que te gustaría ver aclaradas en esta guía, [te " -"invitamos a abrir un issue en GitHub.](https://github.com/pyOpenSci" -"/python-package-guide/issues)." +"invitamos a abrir un issue en GitHub.](https://github.com/pyOpenSci/python-package-guide/issues)." #: ../../index.md:278 msgid "" @@ -568,8 +554,8 @@ msgid "" "forum](https://pyopensci.discourse.group/)." msgstr "" "Si tienes preguntas sobre nuestro proceso de peer review o sobre el " -"empaquetado en general, eres bienvenido a usar nuestro [foro de Discourse" -" de pyOpenSci](https://pyopensci.discourse.group/)." +"empaquetado en general, eres bienvenido a usar nuestro [foro de Discourse " +"de pyOpenSci](https://pyopensci.discourse.group/)." #: ../../index.md:280 msgid "" @@ -577,7 +563,6 @@ msgid "" " in the Python packaging ecosystem. We will be adding new content over " "the next year." msgstr "" -"Esta es una guía en constante evolución que se actualiza a medida que las" -" herramientas y las recomendaciones prácticas evolucionan en el " -"ecosistema de empaquetado de Python. Estaremos añadiendo nuevo contenido " -"durante el próximo año." +"Esta es una guía en constante evolución que se actualiza a medida que las " +"herramientas y las recomendaciones prácticas evolucionan en el ecosistema de " +"empaquetado de Python. Estaremos añadiendo nuevo contenido durante el próximo año." diff --git a/locales/es/LC_MESSAGES/package-structure-code.po b/locales/es/LC_MESSAGES/package-structure-code.po index 7b079da5..32b82ba3 100644 --- a/locales/es/LC_MESSAGES/package-structure-code.po +++ b/locales/es/LC_MESSAGES/package-structure-code.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-06-28 08:42-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../package-structure-code/code-style-linting-format.md:1 msgid "Python Package Code Style, Format and Linters" @@ -361,15 +361,15 @@ msgstr "" msgid "From the project root, run:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:182 +#: ../../package-structure-code/code-style-linting-format.md:181 msgid "Python file `temporal.py` imports after `isort` has been run" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:189 +#: ../../package-structure-code/code-style-linting-format.md:188 msgid "Ruff" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:191 +#: ../../package-structure-code/code-style-linting-format.md:190 msgid "" "[Ruff](https://docs.astral.sh/ruff/) is a new addition to the code " "quality ecosystem, gaining some traction since its release. `ruff` is " @@ -379,53 +379,53 @@ msgid "" "of them." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:197 +#: ../../package-structure-code/code-style-linting-format.md:196 msgid "" "`ruff` has some interesting features that distinguish it from other " "linters:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:199 +#: ../../package-structure-code/code-style-linting-format.md:198 msgid "Linter configuration in `pyproject.toml`" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:200 +#: ../../package-structure-code/code-style-linting-format.md:199 msgid "Several hundred rules included, many of which are automatically fixable" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:201 +#: ../../package-structure-code/code-style-linting-format.md:200 msgid "" "Rules explanation, see [F403](https://docs.astral.sh/ruff/rules" "/undefined-local-with-import-star/) for an example" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:202 +#: ../../package-structure-code/code-style-linting-format.md:201 msgid "" "Fast execution time, makes a quick feedback loop possible even on large " "projects." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:204 +#: ../../package-structure-code/code-style-linting-format.md:203 msgid "" "Here is a simple configuration to get started with `ruff`. It would go " "into your `pyproject.toml`:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:212 +#: ../../package-structure-code/code-style-linting-format.md:211 msgid "" "Depending on your project, you might want to add the following to sort " "imports correctly:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:219 +#: ../../package-structure-code/code-style-linting-format.md:218 msgid "How to use code formatter in your local workflow" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:221 +#: ../../package-structure-code/code-style-linting-format.md:220 msgid "Linters, code formatters and your favorite coding tools" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:223 +#: ../../package-structure-code/code-style-linting-format.md:222 msgid "" "Linters can be run as a command-line tool as shown above. They also can " "be run within your favorite coding tool (e.g. VScode, pycharm, etc). For " @@ -434,46 +434,46 @@ msgid "" "favorite code format tools on demand." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:229 +#: ../../package-structure-code/code-style-linting-format.md:228 msgid "Use pre-commit hooks to run code formatters and linters on commits" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:231 +#: ../../package-structure-code/code-style-linting-format.md:230 msgid "You can also setup a `pre-commit hook` in your Python package repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:233 +#: ../../package-structure-code/code-style-linting-format.md:232 msgid "" "A pre-commit hook is a tool that allows an action (or actions) to be " "triggered when you apply a commit to your git repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:236 +#: ../../package-structure-code/code-style-linting-format.md:235 msgid "Pre-commit hook example workflow" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:238 +#: ../../package-structure-code/code-style-linting-format.md:237 msgid "The precommit workflow looks like this: You type and run:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:241 +#: ../../package-structure-code/code-style-linting-format.md:240 msgid "`git commit -m \"message here\"` at the command line" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:243 +#: ../../package-structure-code/code-style-linting-format.md:242 msgid "" "Once you hit return, pre-commit will run any tools that you have " "configured in a **.pre-commit-config.yaml** file." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:245 +#: ../../package-structure-code/code-style-linting-format.md:244 msgid "" "If the tools configured in the pre-commit hook run successfully without " "making changes or finding errors in your code, the commit will be applied" " to the repository." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:249 +#: ../../package-structure-code/code-style-linting-format.md:248 msgid "" "If the tools configured in the hook find errors in your files, the commit" " will NOT be applied to the repository. Remember from the discussion " @@ -483,20 +483,20 @@ msgid "" "those issues, manually." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:256 +#: ../../package-structure-code/code-style-linting-format.md:255 msgid "" "Once all of the fixes are applied you can re-add (stage) the files to be " "commit. And re-run your commit." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:260 +#: ../../package-structure-code/code-style-linting-format.md:259 msgid "Diagram showing the steps of a pre-commit workflow from left to right." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:262 +#: ../../package-structure-code/code-style-linting-format.md:261 msgid "" "The pre-commit workflow begins with you adding files that have changes to" -" be staged in git. Next, you'd run git commit. When you run git commit, " +" be staged in git. Next, you'd run git commit. when you run git commit, " "the pre-commit hooks will then run. In this example, Black, the code " "formatter and flake8, a linter both run. If all of the files pass Black " "and flake8 checks, then your commit will be recorded. If they don't, the " @@ -506,7 +506,7 @@ msgid "" "using-black-and-flake8/*)" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:275 +#: ../../package-structure-code/code-style-linting-format.md:274 msgid "" "If have a Python code-base and multiple maintainers actively working on " "the code, and you intend to run a tool like Black, be sure to coordinate " @@ -516,11 +516,11 @@ msgid "" "merged." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:282 +#: ../../package-structure-code/code-style-linting-format.md:281 msgid "General pre commit checks" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:284 +#: ../../package-structure-code/code-style-linting-format.md:283 msgid "" "In addition to calling tools, Pre-commit also has a suite of [built in " "format hooks](https://github.com/pre-commit/pre-commit-hooks#hooks-" @@ -529,113 +529,113 @@ msgid "" "streamlined code files." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:289 +#: ../../package-structure-code/code-style-linting-format.md:288 msgid "" "An example pre-commit-config.yaml file is below with examples of how this" " is all setup." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:292 +#: ../../package-structure-code/code-style-linting-format.md:291 msgid "Pre-commit.ci" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:294 +#: ../../package-structure-code/code-style-linting-format.md:293 msgid "" "[Pre-commit.ci](https://pre-commit.ci) is a bot that may become your new " "best friend. This bot, when setup on a repo can be configured to do the " "following:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:297 +#: ../../package-structure-code/code-style-linting-format.md:296 msgid "It will check every pull request using all of the pre-commit hook setting" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:298 +#: ../../package-structure-code/code-style-linting-format.md:297 msgid "" "If you wish, it will also submit a pull request to your repo with pre-" "commit fixes, saving you, and new contributors the time of reformatting a" " pr that has format issues." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:301 +#: ../../package-structure-code/code-style-linting-format.md:300 msgid "You can also call the bot on any pull request to run / and fix the code." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:303 +#: ../../package-structure-code/code-style-linting-format.md:302 msgid "" "The pre-commit.ci bot uses the same pre-commit-config.yaml file that you " "use to setup pre-commit locally." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:306 +#: ../../package-structure-code/code-style-linting-format.md:305 msgid "Setting up a bot like this can be valuable because:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:308 +#: ../../package-structure-code/code-style-linting-format.md:307 msgid "" "It can make is easier for maintainers as they no longer have to worry at " "allows about fixing code format. The bot will do the work for them." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:310 +#: ../../package-structure-code/code-style-linting-format.md:309 msgid "" "It can make it easier for new comers as they never have to setup pre-" "commit locally or worry about linting their code. They can even make " "small fixes to the code directly on GitHub without worry." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:312 +#: ../../package-structure-code/code-style-linting-format.md:311 msgid "Setting up a git pre-commit hook" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:314 +#: ../../package-structure-code/code-style-linting-format.md:313 msgid "To setup pre-commit locally, you need to do 3 things:" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:316 +#: ../../package-structure-code/code-style-linting-format.md:315 msgid "" "Install pre-commit (and include it as a development requirement in your " "repository)" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:326 +#: ../../package-structure-code/code-style-linting-format.md:325 msgid "" "Create a .pre-commit-config.yaml file in the root of your package " "directory." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:328 +#: ../../package-structure-code/code-style-linting-format.md:327 msgid "" "Below is an example **.pre-commit-cofig.yaml** file that can be used to " "setup the pre-commit hook and the pre-commit.ci bot if you chose to " "implement that too." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:336 +#: ../../package-structure-code/code-style-linting-format.md:335 msgid "" "This file specifies a hook that will be triggered automatically before " "each `git commit`, in this case, it specifies a `flake8` using version " "`6.0.0`." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:339 +#: ../../package-structure-code/code-style-linting-format.md:338 msgid "" "Install your pre-commit hook(s) using `pre-commit install`. This will " "install all of the hooks specified in the pre-commit yaml file into your " "environment." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:341 +#: ../../package-structure-code/code-style-linting-format.md:340 msgid "" "Once you have done the above, you are ready to start working on your " "code. Pre-commit will run every time you run `git commit`." msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:344 +#: ../../package-structure-code/code-style-linting-format.md:343 msgid "Summary" msgstr "" -#: ../../package-structure-code/code-style-linting-format.md:346 +#: ../../package-structure-code/code-style-linting-format.md:345 msgid "" "pyOpenSci suggests setting up a linter and a code styler for your " "package, regardless of whether you use pre-commit hooks, CI or other " @@ -816,7 +816,7 @@ msgid "" "keep this comment - https://github.com/pyOpenSci/python-package-" "guide/pull/106#issuecomment-1844278487 in this file for now - jeremiah " "did a nice inventory of common shells and whether they need quotes or " -"not. It's really comprehensive. But do we want it in the guide?? it's " +"not. it's really comprehensive. but do we want it in the guide?? it's " "really useful for more advanced users i think." msgstr "" @@ -851,18 +851,18 @@ msgid "" msgstr "" #: ../../package-structure-code/declare-dependencies.md:29 -msgid "Needs to function properly." +msgid "needs to function properly." msgstr "" #: ../../package-structure-code/declare-dependencies.md:30 msgid "" -"Requires if someone wants to develop / work on improving your package " +"requires if someone wants to develop / work on improving your package " "locally or" msgstr "" #: ../../package-structure-code/declare-dependencies.md:31 msgid "" -"Requires if a user wants to add additional functionality (that is not " +"requires if a user wants to add additional functionality (that is not " "core) to your package" msgstr "" @@ -1184,7 +1184,7 @@ msgid "" "dependency groups listed above - docs feature and tests. In the center it" " says your-package and lists the core dependencies of that package " "seaborn and numpy. To the right are two arrows. The first shows the " -"command python - m pip install your-package. It them shows how installing" +"command python - m pip install your-package. it them shows how installing" " your package that way installs only the package and the two core " "dependencies into a users environment. Below is a second arrow with " "python -m pip install youPackage[tests]. This leads to an environment " @@ -1877,7 +1877,7 @@ msgstr "" msgid "" "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 " +"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." @@ -1889,12 +1889,11 @@ msgstr "" "si creas una receta de conda-forge, puedes publicar en conda-forge." #: ../../package-structure-code/publish-python-package-pypi-conda.md:26 -#, fuzzy msgid "" "Once you have published both package distributions (the source " "distribution and the wheel) to PyPI, you can then publish to conda-forge." -" The 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 " +" 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." msgstr "" "Una vez que haya publicado ambas distribuciones de paquetes (la distribución de origen " @@ -2090,10 +2089,10 @@ msgid "" "Graphic with the title Python package repositories. Below it says " "Anything hosted on PyPI can be installed using pip install. Packaging " "hosted on a conda channel can be installed using conda install. Below " -"that there are two rows. The top row says conda channels. Next to it are " +"that there are two rows. the top row says conda channels. next to it are " "three boxes one with conda-forge, community maintained; bioconda and then" " default - managed by the anaconda team. Below that there is a row that " -"says PyPI servers. PyPI - anyone can publish to PyPI. And test PyPI. A " +"says PyPI servers. PyPI - anyone can publish to PyPI. and test PyPI. a " "testbed server for you to practice." msgstr "" "Gráfico con el título Repositorios de paquetes de Python. Debajo dice " @@ -2485,6 +2484,7 @@ msgid "How the pyproject.toml is used when you build a package" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:104 +#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 msgid "" "When you publish to PyPI, you will notice that each package has metadata " "listed. Let’s have a look at [xclim](https://pypi.org/project/xclim/), " @@ -2704,7 +2704,7 @@ msgid "" "Here is an example of[ a package that has entry point " "script](https://github.com/pyOpenSci/update-web-" "metadata/blob/main/pyproject.toml#L60)s. Notice that there are several " -"core scripts defined in that package that perform sets of tasks. The " +"core scripts defined in that package that perform sets of tasks. " "pyOpenSci is using those scripts to process their metadata." msgstr "" @@ -2713,7 +2713,7 @@ msgid "" "**Dynamic Fields:** if you have fields that are dynamically populated. " "One example of this is if you are using scm / version control based " "version with tools like `setuptooms_scm`, then you might use the dynamic " -"field, such as version (using scm) **dynamic = [\"version\"]**" +"field. such as version (using scm) **dynamic = [\"version\"]**" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:189 @@ -4487,19 +4487,16 @@ msgid "Learn about Building a Python Package" msgstr "Aprenda sobre la construcción de un paquete de Python" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:8 -#, fuzzy msgid "" "Once you have published both package distributions (the source " "distribution and the wheel) to PyPI, you can then publish to conda-forge." -" The 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." +" 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." msgstr "" -"Una vez que haya publicado ambas distribuciones de paquetes (la " -"distribución del código fuente y la distribución construida o wheel) en " -"PyPI, entonces puede publicar en conda-forge. conda-forge requiere una " -"distribución de origen en PyPI para construir su paquete en conda-forge. " -"No necesita reconstruir su paquete para publicar en conda-forge." +"Una vez que haya publicado ambas distribuciones de paquetes (la distribución del código fuente y la distribución construida o wheel) en PyPI, " +"entonces puede publicar en conda-forge. conda-forge requiere una distribución de origen en PyPI para construir su " +"paquete en conda-forge. No necesita reconstruir su paquete para publicar en conda-forge." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:11 msgid "" @@ -4510,12 +4507,12 @@ msgid "" "PyPI in order for conda-forge to properly build your package " "automatically." msgstr "" -"Necesita construir su paquete de Python para publicarlo en PyPI (o en un " -"canal de conda). El proceso de construcción organiza su código y " -"metadatos en un formato de distribución que puede ser subido a PyPI y " +"Necesita construir su paquete de Python para publicarlo en PyPI " +"(o en un canal de conda). El proceso de construcción organiza su código " +"y metadatos en un formato de distribución que puede ser subido a PyPI y " "posteriormente descargado e instalado por los usuarios. NOTA: necesita " -"publicar un sdist (distribución del código fuente) en PyPI para que " -"conda-forge pueda construir su paquete automáticamente." +"publicar un sdist (distribución del código fuente) en PyPI para que conda-forge pueda construir su paquete " +"automáticamente." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:14 msgid "What is building a Python package?" @@ -4526,9 +4523,8 @@ msgid "" "To [publish your Python package](publish-python-package-pypi-conda) and " "make it easy for anyone to install, you first need to build it." msgstr "" -"Para [publicar su paquete de Python](publish-python-package-pypi-conda) y" -" hacer que sea fácil de instalar para cualquiera, primero necesita " -"construirlo." +"Para [publicar su paquete de Python](publish-python-package-pypi-conda) y " +"hacer que sea fácil de instalar para cualquiera, primero necesita construirlo." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:18 msgid "But, what does it mean to build a Python package?" @@ -4542,11 +4538,10 @@ msgid "" "and metadata about the package, in the format required by the Python " "Package Index, so that it can be installed by tools like pip." msgstr "" -"[Como se muestra en la figura de arriba](#pypi-conda-channels), cuando " -"construye su paquete de Python, convierte los archivos de código fuente " -"en algo llamado paquete de distribución. Un paquete de distribución " -"contiene su código fuente y metadatos sobre el paquete, en el formato " -"requerido por el Python Package Index (PyPI), para que pueda ser " +"[Como se muestra en la figura de arriba](#pypi-conda-channels), cuando construye su paquete de Python, convierte " +"los archivos de código fuente en algo llamado paquete de distribución." +" Un paquete de distribución contiene su código fuente " +"y metadatos sobre el paquete, en el formato requerido por el Python Package Index (PyPI), para que pueda ser " "instalado por herramientas como pip." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:23 @@ -4556,11 +4551,9 @@ msgid "" " Authority](https://www.pypa.io/en/latest/) and refer to the product of " "the build step as a **distribution package**." msgstr "" -"El término paquete solía significar muchas cosas diferentes en Python y " -"otros lenguajes. En esta página, adaptamos la convención de la [Autoridad" -" de Empaquetado de Python](https://www.pypa.io/en/latest/) y nos " -"referimos al producto del paso de construcción como un **paquete de " -"distribución**." +"El término paquete solía significar muchas cosas diferentes en Python y otros lenguajes. En esta página, " +"adaptamos la convención de la [Autoridad de Empaquetado de Python](https://www.pypa.io/en/latest/) y nos referimos " +"al producto del paso de construcción como un **paquete de distribución**." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:27 msgid "" @@ -4568,9 +4561,8 @@ msgid "" " and metadata into a format that both pip and PyPI can use, is called a " "build step." msgstr "" -"Este proceso de organizar y formatear su código, documentación, pruebas y" -" metadatos en un formato que tanto pip como PyPI pueden usar, se llama " -"paso de construcción." +"Este proceso de organizar y formatear su código, documentación, pruebas y metadatos en un formato que tanto pip " +"como PyPI pueden usar, se llama paso de construcción." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:31 msgid "Project metadata and PyPI" @@ -4583,10 +4575,9 @@ msgid "" "](pyproject-toml-python-package-metadata). This metadata is used for " "several purposes:" msgstr "" -"Los metadatos que tanto las herramientas de construcción como PyPI " -"utilizan para describir y entender su paquete generalmente se almacenan " -"en un [archivo pyproject.toml](pyproject-toml-python-package-metadata). " -"Estos metadatos se utilizan para varios propósitos:" +"Los metadatos que tanto las herramientas de construcción como PyPI utilizan para describir y entender su paquete " +"generalmente se almacenan en un [archivo pyproject.toml](pyproject-toml-python-package-metadata). Estos metadatos " +"se utilizan para varios propósitos:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:35 msgid "" @@ -4595,10 +4586,9 @@ msgid "" "poetry, PDM or Hatch) understand how to build your package. Information " "it provides to your build tool includes:" msgstr "" -"Ayuda a la herramienta que use para construir su paquete (pip, [Build de " -"pypa](https://pypi.org/project/build/) o una herramienta de extremo a " -"extremo como poetry, PDM o Hatch) a entender cómo construir su paquete. " -"La información que proporciona a su herramienta de construcción incluye:" +"Ayuda a la herramienta que use para construir su paquete (pip, [Build de pypa](https://pypi.org/project/build/) o " +"una herramienta de extremo a extremo como poetry, PDM o Hatch) a entender cómo construir su paquete. La información " +"que proporciona a su herramienta de construcción incluye:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:37 msgid "" @@ -4606,19 +4596,16 @@ msgid "" "[build backend tool](build_backends) you wish to use for creating your " "sdist and wheel distributions." msgstr "" -"La tabla `[build-system]` en su archivo pyproject.toml le dice a pip qué " -"[herramienta de backend de construcción](build_backends) desea usar para " -"crear sus distribuciones sdist (distribución del código fuente) y wheel " -"(distribución construida)." +"La tabla `[build-system]` en su archivo pyproject.toml le dice a pip qué [herramienta de backend de construcción]" +"(build_backends) desea usar para crear sus distribuciones sdist (distribución del código fuente) y wheel (distribución construida)." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:45 msgid "" "And the dependencies section of your project table tells the build tool " "and PyPI what dependencies your project requires." msgstr "" -"Y la sección de dependencias de su tabla de proyecto le dice a la " -"herramienta de construcción y a PyPI qué dependencias requiere su " -"proyecto." +"Y la sección de dependencias de su tabla de proyecto le dice a la herramienta de construcción y a PyPI qué " +"dependencias requiere su proyecto." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:54 msgid "" @@ -4626,10 +4613,9 @@ msgid "" " you publish on PyPI), it also creates a METADATA file which PyPI can " "read and use to help users find your package. For example:" msgstr "" -"Cuando la herramienta de construcción crea el archivo de distribución de " -"su paquete (el archivo que publica en PyPI), también crea un archivo " -"METADATA que PyPI puede leer y usar para ayudar a los usuarios a " -"encontrar su paquete. Por ejemplo:" +"Cuando la herramienta de construcción crea el archivo de distribución de su paquete (el archivo que publica en " +"PyPI), también crea un archivo METADATA que PyPI puede leer y usar para ayudar a los usuarios a encontrar su paquete. " +"Por ejemplo:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:56 msgid "" @@ -4638,10 +4624,9 @@ msgid "" "filter for packages that contain specific licenses or that support " "specific versions of python." msgstr "" -"La sección `classifiers = ` de su tabla `[project]` en el archivo " -"pyproject.toml proporciona información que los usuarios en PyPI pueden " -"usar para filtrar paquetes que contienen licencias específicas o que " -"admiten versiones específicas de Python." +"La sección `classifiers = ` de su tabla `[project]` en el archivo pyproject.toml proporciona información que los " +"usuarios en PyPI pueden usar para filtrar paquetes que contienen licencias específicas o que admiten versiones " +"específicas de Python." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:73 msgid "What happened to setup.py and setup.cfg for metadata?" @@ -4654,52 +4639,34 @@ msgid "" "metadata is to use a pyproject.toml file. [Learn more about the " "pyproject.toml file here.](pyproject-toml-python-package-metadata)" msgstr "" -"Los metadatos del proyecto solían almacenarse en un archivo setup.py o en" -" un archivo setup.cfg. La práctica recomendada actual para almacenar " -"metadatos de paquetes es utilizar un archivo pyproject.toml. [Aprenda más" -" sobre el archivo pyproject.toml aquí.](pyproject-toml-python-package-" -"metadata)" +"Los metadatos del proyecto solían almacenarse en un archivo setup.py o en un archivo setup.cfg. La práctica " +"recomendada actual para almacenar metadatos de paquetes es utilizar un archivo pyproject.toml. [Aprenda más sobre el " +"archivo pyproject.toml aquí.](pyproject-toml-python-package-metadata)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:79 msgid "An example - xclim" msgstr "Un ejemplo - xclim" -#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 -msgid "" -"When you publish to PyPI, you will notice that each package has metadata " -"listed. Let's have a look at [xclim](https://pypi.org/project/xclim/), " -"one of our [pyOpenSci packages](https://www.pyopensci.org/python-" -"packages.html). Notice that on the PyPI landing page you see some " -"metadata about the package including python, maintainer information and " -"more. PyPI is able to populate this metadata because it was defined using" -" correct syntax and classifiers by Xclim's maintainers, [pyproject.toml " -"file](https://github.com/Ouranosinc/xclim/blob/master/pyproject.toml). " -"This metadata when the xclim package is built, is translated into a " -"distribution file that allows PyPI to read the metadata and print it out " -"on their website." -msgstr "" - #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:94 -#, fuzzy msgid "" "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" +"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 " +"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." msgstr "" -"Gráfico que muestra el flujo de trabajo de empaquetado de alto nivel. A " -"la izquierda se ve un gráfico con código, metadatos y tests en él. Esos " -"elementos van todos en su paquete. La documentación y los datos están " -"debajo de ese recuadro porque normalmente no se publican en su " -"distribución construida (wheel). Una flecha a la derecha lo lleva a un " -"cuadro de archivos de distribución de construcción. Ese cuadro lo lleva a" -" publicar en TestPyPI o en el verdadero PyPI. Desde PyPI, puede " -"conectarse a conda-forge para una construcción automatizada que envía " -"distribuciones de PyPI a conda-forge." +"Gráfico que muestra el flujo de trabajo de empaquetado de alto nivel." +" A la izquierda se ve un gráfico con código, metadatos y tests en él. " +"Esos elementos van todos en su paquete. La documentación y los datos " +"están debajo de ese recuadro porque normalmente no se publican en su " +"distribución construida (wheel). Una flecha a la derecha lo lleva a " +"un cuadro de archivos de distribución de construcción. Ese cuadro lo lleva " +"a publicar en TestPyPI o en el verdadero PyPI. Desde PyPI, puede conectarse " +"a conda-forge para una construcción automatizada que envía distribuciones " +"de PyPI a conda-forge." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:96 msgid "" @@ -4710,40 +4677,37 @@ msgid "" "PyPI in order for conda-forge to properly build your package " "automatically." msgstr "" -"Necesita construir su paquete de Python para publicarlo en PyPI (o " -"Conda). El proceso de construcción organiza su código y metadatos en un " -"formato de distribución que puede ser subido a PyPI y posteriormente " -"descargado e instalado por los usuarios. NOTA: necesita publicar " -"distribución del código fuente (sdist) en PyPI para que conda-forge pueda" -" construir su paquete automáticamente." +"Necesita construir su paquete de Python para publicarlo en PyPI (o Conda). " +"El proceso de construcción organiza su código y metadatos en un formato de " +"distribución que puede ser subido a PyPI y posteriormente descargado e " +"instalado por los usuarios. NOTA: necesita publicar distribución del código fuente (sdist) en PyPI para " +"que conda-forge pueda construir su paquete automáticamente." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:101 -#, fuzzy msgid "" -"This screenshot shows the metadata on PyPI for the xclim package. On it " +"This screenshot shows the metadata on PyPI for the xclim package. on it " "you can see the name of the license, the author and maintainer names " "keywords associated with the package and the base python version it " "requires which is 3.8." msgstr "" -"Esta captura de pantalla muestra los metadatos en PyPI para el paquete " -"xclim. En ella puede ver el nombre de la licencia, los nombres del autor " -"y del mantenedor, palabras clave asociadas con el paquete y la versión " -"base de Python que requiere, que es 3.8." +"Esta captura de pantalla muestra los metadatos en PyPI para el paquete xclim. " +"En ella puede ver el nombre de la licencia, los nombres del autor y del " +"mantenedor, palabras clave asociadas con el paquete y la versión base de " +"Python que requiere, que es 3.8." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:103 msgid "PyPI screenshot showing metadata for the xclim package." msgstr "Captura de pantalla de PyPI que muestra metadatos para el paquete xclim." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:110 -#, fuzzy msgid "" -"Here you see the maintainer metadata as it is displayed on PyPI. For " +"Here you see the maintainer metadata as it is displayed on PyPI. for " "xclim there are three maintainers listed with their profile pictures and " "github user names to the right." msgstr "" "Aquí ve los metadatos del mantenedor tal como se muestran en PyPI. Para " -"xclim hay tres mantenedores listados con sus fotos de perfil y nombres de" -" usuario de GitHub a la derecha." +"xclim hay tres mantenedores listados con sus fotos de perfil y nombres de " +"usuario de GitHub a la derecha." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:112 msgid "" @@ -4752,11 +4716,10 @@ msgid "" "and then processed by your build tool and stored in your packages sdist " "and wheel distributions." msgstr "" -"Nombres de los mantenedores y nombres de usuario de GitHub para el " -"paquete xclim tal como se muestran en PyPI. Esta información se registra " -"en su pyproject.toml y luego es procesada por su herramienta de " -"construcción y almacenada en las distribuciones sdist y wheel de sus " -"paquetes." +"Nombres de los mantenedores y nombres de usuario de GitHub para el paquete " +"xclim tal como se muestran en PyPI. Esta información se registra en su " +"pyproject.toml y luego es procesada por su herramienta de construcción y " +"almacenada en las distribuciones sdist y wheel de sus paquetes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:115 msgid "How to create the distribution format that PyPI and Pip expects?" @@ -4770,11 +4733,11 @@ msgid "" "there are packages and tools that help you create package build " "distribution files." msgstr "" -"En teoría, podría crear sus propios scripts para organizar su código de " -"la manera que PyPI quiere que sea. Sin embargo, al igual que hay paquetes" -" que manejan estructuras conocidas como dataframes de Pandas y arrays de " -"Numpy, hay paquetes y herramientas que le ayudan a crear archivos de " -"distribución de construcción de paquetes." +"En teoría, podría crear sus propios scripts para organizar su código " +"de la manera que PyPI quiere que sea. Sin embargo, al igual que hay " +"paquetes que manejan estructuras conocidas como dataframes de Pandas " +"y arrays de Numpy, hay paquetes y herramientas que le " +"ayudan a crear archivos de distribución de construcción de paquetes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:121 msgid "" @@ -4785,11 +4748,10 @@ msgid "" " with other parts of the packaging process." msgstr "" "Existen una serie de herramientas de empaquetado que pueden ayudarle con " -"todo el proceso de empaquetado o solo con un paso del proceso. Por " -"ejemplo, setuptools es un backend de construcción comúnmente utilizado " -"que se puede usar para crear su sdist y wheel. Mientras que herramientas " -"como Hatch, PDM, Poetry y flit ayudan con otras partes del proceso de " -"empaquetado." +"todo el proceso de empaquetado o solo con un paso del proceso. Por ejemplo, " +"setuptools es un backend de construcción comúnmente utilizado que se puede " +"usar para crear su sdist y wheel. Mientras que herramientas como " +"Hatch, PDM, Poetry y flit ayudan con otras partes del proceso de empaquetado." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:127 msgid "" @@ -4798,9 +4760,9 @@ msgid "" "output (with minor differences that most users may not care about). Learn" " more about those tools on this page." msgstr "" -"Si bien esto puede causar cierta confusión y complejidad en el ecosistema" -" de empaquetado, en su mayor parte, cada herramienta proporciona la misma" -" salida de distribución (con diferencias menores que a la mayoría de los " +"Si bien esto puede causar cierta confusión y complejidad en el ecosistema " +"de empaquetado, en su mayor parte, cada herramienta proporciona la misma " +"salida de distribución (con diferencias menores que a la mayoría de los " "usuarios pueden no importarles). Aprenda más sobre esas herramientas en " "esta página." @@ -4810,9 +4772,9 @@ msgid "" "you to publish: sdist and wheel. You will learn about their structure and" " what files belong in each." msgstr "" -"A continuación, aprenderá sobre los dos archivos de distribución que PyPI" -" espera que publique: sdist y wheel. Aprenderá sobre su estructura y qué " -"archivos pertenecen a cada uno." +"A continuación, aprenderá sobre los dos archivos de distribución que PyPI " +"espera que publique: sdist y wheel. Aprenderá sobre su estructura " +"y qué archivos pertenecen a cada uno." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:136 msgid "" @@ -4823,11 +4785,11 @@ msgid "" "installed onto anyones' computer." msgstr "" "Hay dos archivos de distribución principales que necesita crear para " -"publicar su paquete de Python en PyPI: la distribución de origen (a " -"menudo llamada sdist) y la distribución construida (wheel). El sdist " -"contiene el código fuente sin procesar de su paquete. La wheel (.whl) " -"contiene los archivos construidos / compilados que se pueden instalar " -"directamente en el ordenador de cualquier persona." +"publicar su paquete de Python en PyPI: la distribución de origen (a menudo " +"llamada sdist) y la distribución construida (wheel). El sdist contiene el código fuente " +"sin procesar de su paquete. La wheel (.whl) contiene los archivos " +"construidos / compilados que se pueden instalar directamente en el " +"ordenador de cualquier persona." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:142 msgid "Learn more about both distributions below." @@ -4843,9 +4805,9 @@ msgid "" msgstr "" "Si su paquete es un paquete de Python puro sin pasos adicionales de " "construcción / compilación, entonces las distribuciones sdist y wheel " -"tendrán contenido similar. Sin embargo, si su paquete tiene extensiones " -"en otros lenguajes o es más complejo en su construcción, las dos " -"distribuciones serán muy diferentes." +"tendrán contenido similar. Sin embargo, si su paquete tiene extensiones en " +"otros lenguajes o es más complejo en su construcción, las dos distribuciones " +"serán muy diferentes." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:150 msgid "" @@ -4856,8 +4818,8 @@ msgid "" msgstr "" "También tenga en cuenta que no estamos discutiendo flujos de trabajo de " "construcción de conda en esta sección. [Puede aprender más sobre las " -"construcciones de conda aquí.](https://conda.io/projects/conda-" -"build/en/latest/user-guide/tutorials/index.html)" +"construcciones de conda aquí.](https://conda.io/projects/conda-build/en/" +"latest/user-guide/tutorials/index.html)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:155 msgid "Source Distribution (sdist)" @@ -4869,10 +4831,10 @@ msgid "" "These are the \"raw / as-is\" files that you store on GitHub or whatever " "platform you use to manage your code." msgstr "" -"Los **archivos de código fuente** son los archivos sin construir " -"necesarios para construir su paquete. Estos son los archivos \"originales" -" / sin procesar\" que almacena en GitHub o en cualquier plataforma que " -"utilice para gestionar su código." +"Los **archivos de código fuente** son los archivos sin construir necesarios para " +"construir su paquete. Estos son los archivos \"originales / sin procesar\" " +"que almacena en GitHub o en cualquier plataforma que utilice para gestionar " +"su código." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:161 msgid "" @@ -4884,14 +4846,12 @@ msgid "" "everything required to build a wheel (except for project dependencies) " "without network access." msgstr "" -"Las distribuciones de código fuente (del inglés, _source distribution_) " -"se denominan sdist. Como su nombre indica, una distribución sdist " -"contiene el código fuente; no ha sido construido ni compilado de ninguna " -"manera. Por lo tanto, cuando un usuario instala su distribución de código" -" fuente usando pip, pip necesita ejecutar un paso de construcción " -"primero. Por esta razón, podría definir una distribución sdist como un " -"archivo comprimido que contiene todo lo necesario para construir una " -"wheel (excepto las dependencias del proyecto) sin acceso a la red." +"Las distribuciones de código fuente (del inglés, _source distribution_) se denominan sdist. Como " +"su nombre indica, una distribución sdist contiene el código fuente; no ha sido construido ni" +" compilado de ninguna manera. Por lo tanto, cuando un usuario instala su distribución de código fuente " +"usando pip, pip necesita ejecutar un paso de construcción primero. Por esta razón, " +"podría definir una distribución sdist como un archivo comprimido que contiene todo lo " +"necesario para construir una wheel (excepto las dependencias del proyecto) sin acceso a la red." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:165 msgid "" @@ -4899,16 +4859,13 @@ msgid "" "\"tarball\"). Thus, when a user installs your source distribution using " "pip, pip needs to run a build step first." msgstr "" -"Normalmente, sdist se almacena como un archivo `.tar.gz` (a menudo " -"llamado un \"tarball\"). Por lo tanto, cuando un usuario instala su " -"distribución de origen usando pip, pip necesita ejecutar un paso de " -"construcción primero." +"Normalmente, sdist se almacena como un archivo `.tar.gz` (a menudo llamado " +"un \"tarball\"). Por lo tanto, cuando un usuario instala su distribución de origen " +"usando pip, pip necesita ejecutar un paso de construcción primero." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:167 msgid "Below is an example sdist for the stravalib Python package:" -msgstr "" -"A continuación se muestra un ejemplo de sdist para el paquete de Python " -"stravalib:" +msgstr "A continuación se muestra un ejemplo de sdist para el paquete de Python stravalib:" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:219 msgid "GitHub archive vs sdist" @@ -4923,12 +4880,12 @@ msgid "" "`setuptools_scm` or `hatch_vcs` the sdist may also contain a file that " "stores the version." msgstr "" -"Cuando se crea una versión en GitHub, se crea un `git archive` que " -"contiene todos los archivos de su repositorio de GitHub. Si bien estos " -"archivos son similares a un sdist, estos dos archivos no son iguales. El " -"sdist contiene algunos otros elementos, incluido un directorio de " -"metadatos y si utiliza `setuptools_scm` o `hatch_vcs`, el sdist también " -"puede contener un archivo que almacena la versión." +"Cuando se crea una versión en GitHub, se crea un `git archive` que contiene " +"todos los archivos de su repositorio de GitHub. Si bien estos archivos son " +"similares a un sdist, estos dos archivos no son iguales. El sdist contiene " +"algunos otros elementos, incluido un directorio de metadatos y si utiliza " +"`setuptools_scm` o `hatch_vcs`, el sdist también puede contener un archivo " +"que almacena la versión." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:229 msgid "Wheel (.whl files):" @@ -4943,13 +4900,13 @@ msgid "" "may be included in source distributions are not included in wheels " "because it is a built distribution." msgstr "" -"Un archivo wheel es un archivo en formato ZIP cuyo nombre sigue un " -"formato específico (a continuación) y tiene la extensión `.whl`. El " -"archivo `.whl` contiene un conjunto específico de archivos, incluidos " -"metadatos que se generan a partir del archivo pyproject.toml de su " -"proyecto. El pyproject.toml y otros archivos que pueden estar incluidos " -"en las distribuciones de origen no se incluyen en las wheels porque es " -"una distribución construida." +"Un archivo wheel es un archivo en formato ZIP cuyo nombre sigue" +" un formato específico (a continuación) y tiene la " +"extensión `.whl`. El archivo `.whl` contiene un conjunto específico de " +"archivos, incluidos metadatos que se generan a partir del archivo " +"pyproject.toml de su proyecto. El pyproject.toml y otros archivos que " +"pueden estar incluidos en las distribuciones de origen no se incluyen en " +"las wheels porque es una distribución construida." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:238 msgid "" @@ -4961,14 +4918,14 @@ msgid "" "thus faster to install - particularly if you have a package that requires" " build steps." msgstr "" -"La wheel (.whl) es su distribución binaria construida. Los **archivos " -"binarios** son los archivos de código fuente construidos / compilados. " -"Estos archivos están listos para ser instalados. Una wheel (**.whl**) es " -"un archivo **zip** que contiene todos los archivos necesarios para " -"instalar directamente su paquete. Todos los archivos en una wheel son " -"binarios, lo que significa que el código ya está compilado / construido. " -"Por lo tanto, estas son más rápidas de instalar, particularmente si tiene" -" un paquete que requiere pasos de construcción." +"La wheel (.whl) es su distribución binaria construida. Los" +" **archivos binarios** son los archivos de código fuente " +"construidos / compilados. Estos archivos están listos para ser instalados." +" Una wheel (**.whl**) es un archivo **zip** que contiene todos los archivos " +"necesarios para instalar directamente su paquete. Todos los archivos en una " +"wheel son binarios, lo que significa que el código ya está compilado / " +"construido. Por lo tanto, estas son más rápidas de instalar, " +"particularmente si tiene un paquete que requiere pasos de construcción." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:240 msgid "" @@ -4976,17 +4933,17 @@ msgid "" " as **setup.cfg** or **pyproject.toml**. This distribution is already " "built so it's ready to install." msgstr "" -"La wheel no contiene ninguno de los archivos de configuración de su " -"paquete como **setup.cfg** o **pyproject.toml**. Esta distribución ya " -"está construida por lo que está lista para instalar." +"La wheel no contiene ninguno de los archivos de configuración de su paquete " +"como **setup.cfg** o **pyproject.toml**. Esta distribución ya está construida " +"por lo que está lista para instalar." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:244 msgid "" "Because it is built, the wheel file will be faster to install for pure " "Python projects and can lead to consistent installs across machines." msgstr "" -"Debido a que está construido, el archivo .whl será más rápido de instalar" -" para proyectos de Python puro y llevará a instalaciones consistentes " +"Debido a que está construido, el archivo .whl será más rápido de instalar " +"para proyectos de Python puro y llevará a instalaciones consistentes " #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:252 msgid "" @@ -4997,15 +4954,13 @@ msgid "" msgstr "" "Las wheels también son útiles en el caso de que un paquete necesite un " "archivo **setup.py** para admitir una construcción más compleja. En este " -"caso, debido a que los archivos en el paquete de wheel están " -"preconstruidos, el usuario que lo instala no tiene que preocuparse por " -"inyecciones de código malicioso cuando se instala." +"caso, debido a que los archivos en el paquete de wheel están preconstruidos, " +"el usuario que lo instala no tiene que preocuparse por inyecciones de código " +"malicioso cuando se instala." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:259 msgid "The filename of a wheel contains important metadata about your package." -msgstr "" -"El nombre de archivo de una wheel contiene metadatos importantes sobre su" -" paquete." +msgstr "El nombre de archivo de una wheel contiene metadatos importantes sobre su paquete." #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:261 msgid "Example: **stravalib-1.1.0.post2-py3-none.whl**" @@ -5033,9 +4988,7 @@ msgstr "py3: admite Python 3.x" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:267 msgid "none: is not operating system specific (runs on windows, mac, linux)" -msgstr "" -"none: no es específico del sistema operativo (se ejecuta en Windows, Mac," -" Linux)" +msgstr "none: no es específico del sistema operativo (se ejecuta en Windows, Mac, Linux)" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:268 msgid "any: runs on any computer processor / architecture" @@ -5061,11 +5014,10 @@ msgid "" "vs-flat-layout/) Both layouts have advantages for different groups of " "maintainers." msgstr "" -"Existen dos diseños diferentes que comúnmente verá dentro del ecosistema " -"de empaquetado de Python: [diseños src y " -"flat](https://packaging.python.org/en/latest/discussions/src-layout-vs-" -"flat-layout/). Ambos diseños tienen ventajas para diferentes grupos de " -"mantenedores." +"Existen dos diseños diferentes que comúnmente verá dentro del ecosistema de " +"empaquetado de Python: [diseños src y flat](https://packaging.python.org/en/" +"latest/discussions/src-layout-vs-flat-layout/). Ambos diseños tienen ventajas " +"para diferentes grupos de mantenedores." #: ../../package-structure-code/python-package-structure.md:8 msgid "" @@ -5075,25 +5027,22 @@ msgid "" "guide](https://packaging.python.org/en/latest/tutorials/packaging-" "projects/)." msgstr "" -"Le sugerimos, pero no requerimos, que use el diseño **src/** (discutido a" -" continuación) para crear su paquete de Python. Este diseño también se " -"recomienda en la [guía de empaquetado de " -"PyPA](https://packaging.python.org/en/latest/tutorials/packaging-" -"projects/)." +"Le sugerimos, pero no requerimos, que use el diseño **src/** (discutido a " +"continuación) para crear su paquete de Python. Este diseño también se " +"recomienda en la [guía de empaquetado de PyPA](https://packaging.python.org/" +"en/latest/tutorials/packaging-projects/)." #: ../../package-structure-code/python-package-structure.md:12 msgid "pyOpenSci will never require a specific package structure for peer review" -msgstr "" -"pyOpenSci nunca requerirá una estructura de paquete específica para la " -"revisión por pares" +msgstr "pyOpenSci nunca requerirá una estructura de paquete específica para la revisión por pares" #: ../../package-structure-code/python-package-structure.md:15 msgid "" "We understand that it would be tremendous effort for existing maintainers" " to move to a new layout." msgstr "" -"Entendemos que sería un esfuerzo tremendo para los mantenedores " -"existentes moverse a un nuevo diseño." +"Entendemos que sería un esfuerzo tremendo para los mantenedores existentes " +"moverse a un nuevo diseño." #: ../../package-structure-code/python-package-structure.md:18 msgid "" @@ -5102,16 +5051,14 @@ msgid "" "package has a simple build and might be open to moving to a more fail-" "proof approach." msgstr "" -"La descripción general en esta página presenta recomendaciones que " -"creemos que son las mejores para alguien que está comenzando con el " -"empaquetado de Python o para alguien cuyo paquete tiene una construcción " -"simple y podría estar abierto a moverse a un enfoque a prueba de fallos." +"La descripción general en esta página presenta recomendaciones que creemos " +"que son las mejores para alguien que está comenzando con el empaquetado de " +"Python o para alguien cuyo paquete tiene una construcción simple y podría " +"estar abierto a moverse a un enfoque a prueba de fallos." #: ../../package-structure-code/python-package-structure.md:23 msgid "An example of the **src/package** layout structure can be seen below." -msgstr "" -"Un ejemplo de la estructura de diseño **src/package** se puede ver a " -"continuación." +msgstr "Un ejemplo de la estructura de diseño **src/package** se puede ver a continuación." #: ../../package-structure-code/python-package-structure.md:45 msgid "Note the location of the following directories in the example above:" @@ -5123,10 +5070,10 @@ msgid "" "user-facing documentation website. In a **src/** layout docs/ are " "normally included at the same directory level of the **src/** folder." msgstr "" -"**docs/:** discutido en nuestro capítulo de documentación, este " -"directorio contiene el sitio web de documentación orientado al usuario. " -"En un diseño **src/**, los docs/ normalmente se incluyen en el mismo " -"nivel de directorio que la carpeta **src/**." +"**docs/:** discutido en nuestro capítulo de documentación, este directorio " +"contiene el sitio web de documentación orientado al usuario. En un diseño " +"**src/**, los docs/ normalmente se incluyen en el mismo nivel de directorio " +"que la carpeta **src/**." #: ../../package-structure-code/python-package-structure.md:48 msgid "" @@ -5134,17 +5081,17 @@ msgid "" "**src/** layout tests are normally included at the same directory level " "of the **src/** folder." msgstr "" -"**tests/** este directorio contiene las pruebas o tests para el código de" -" su proyecto. En un diseño **src/**, las pruebas o tests normalmente se " -"incluyen en el mismo nivel de directorio que la carpeta **src/**." +"**tests/** este directorio contiene las pruebas o tests para el código de su proyecto. " +"En un diseño **src/**, las pruebas o tests normalmente se incluyen en el " +"mismo nivel de directorio que la carpeta **src/**." #: ../../package-structure-code/python-package-structure.md:49 msgid "" "**src/package/**: this is the directory that contains the code for your " "Python project. \"Package\" is normally your project's name." msgstr "" -"**src/package/**: este es el directorio que contiene el código de su " -"proyecto de Python. \"Package\" es normalmente el nombre de su proyecto." +"**src/package/**: este es el directorio que contiene el código de su proyecto de Python. " +"\"Package\" es normalmente el nombre de su proyecto." #: ../../package-structure-code/python-package-structure.md:51 msgid "" @@ -5152,9 +5099,9 @@ msgid "" "files that pyOpenSci requires live in the root of your project directory." " These files include:" msgstr "" -"También en el ejemplo anterior, observe que todos los archivos de " -"documentación básicos que pyOpenSci requiere se encuentran en la raíz del" -" directorio de su proyecto. Estos archivos incluyen:" +"También en el ejemplo anterior, observe que todos los archivos de documentación " +"básicos que pyOpenSci requiere se encuentran en la raíz del directorio de su proyecto. " +"Estos archivos incluyen:" #: ../../package-structure-code/python-package-structure.md:55 msgid "CHANGELOG.md" @@ -5178,17 +5125,15 @@ msgstr "" #: ../../package-structure-code/python-package-structure.md:63 msgid "Click here to read about our packaging documentation requirements." -msgstr "" -"Haga clic aquí para leer sobre nuestros requisitos de documentación de " -"empaquetado." +msgstr "Haga clic aquí para leer sobre nuestros requisitos de documentación de empaquetado." #: ../../package-structure-code/python-package-structure.md:70 msgid "" "While we recommend the **src/** layout we also review the **flat** layout" " here. Both are used in the Python ecosystem." msgstr "" -"Aunque recomendamos el diseño **src/**, también revisamos el diseño " -"**flat** aquí. Ambos se utilizan en el ecosistema de Python." +"Aunque recomendamos el diseño **src/**, también revisamos el diseño **flat** aquí. " +"Ambos se utilizan en el ecosistema de Python." #: ../../package-structure-code/python-package-structure.md:72 msgid "Example scientific packages that use **src/package** layout" @@ -5228,11 +5173,11 @@ msgid "" "your package is installed." msgstr "" "El beneficio de usar el diseño **src/package**, particularmente si está " -"creando un nuevo paquete, es que asegura que las pruebas se ejecuten " -"contra la versión instalada de su paquete en lugar de los archivos en el " -"directorio de trabajo de su paquete. Si ejecuta sus pruebas en sus " -"archivos en lugar de la versión instalada, es posible que se pierda " -"problemas que los usuarios encuentran cuando su paquete está instalado." +"creando un nuevo paquete, es que asegura que las pruebas se ejecuten contra " +"la versión instalada de su paquete en lugar de los archivos en el directorio " +"de trabajo de su paquete. Si ejecuta sus pruebas en sus archivos en lugar de " +"la versión instalada, es posible que se pierda problemas que los usuarios " +"encuentran cuando su paquete está instalado." #: ../../package-structure-code/python-package-structure.md:91 msgid "" @@ -5241,18 +5186,18 @@ msgid "" "smaller which then places places a smaller storage burden on PyPI which " "has over 400,000 packages to support." msgstr "" -"Si `tests/` están fuera del directorio **src/package**, no se incluyen en" -" la rueda del paquete. Esto hace que el tamaño de su paquete sea " -"ligeramente más pequeño, lo que a su vez genera un almacenamiento más " -"pequeño en PyPI, que tiene más de 400,000 paquetes." +"Si `tests/` están fuera del directorio **src/package**, no se incluyen en la " +"rueda del paquete. Esto hace que el tamaño de su paquete sea ligeramente " +"más pequeño, lo que a su vez genera un almacenamiento más pequeño " +"en PyPI, que tiene más de 400,000 paquetes." #: ../../package-structure-code/python-package-structure.md:93 msgid "" "[Read more about reasons to use the **src/package** " "layout](https://hynek.me/articles/testing-packaging/)" msgstr "" -"[Lea más sobre las razones para usar el diseño " -"**src/package**](https://hynek.me/articles/testing-packaging/)" +"[Lea más sobre las razones para usar el diseño" +" **src/package**](https://hynek.me/articles/testing-packaging/)" #: ../../package-structure-code/python-package-structure.md:95 msgid "How Python discovers and prioritizes importing modules" @@ -5263,8 +5208,8 @@ msgid "" "By default, Python adds a module in your current working directory to the" " front of the Python module search path." msgstr "" -"De forma predeterminada, Python agrega un módulo en su directorio de " -"trabajo actual al principio de la ruta de búsqueda de módulos de Python." +"De forma predeterminada, Python agrega un módulo en su directorio de trabajo " +"actual al principio de la ruta de búsqueda de módulos de Python." #: ../../package-structure-code/python-package-structure.md:99 msgid "" @@ -5273,10 +5218,9 @@ msgid "" "discover `package/module.py` file before it discovers the installed " "package." msgstr "" -"Esto significa que si ejecuta sus pruebas en el directorio de trabajo de " -"su paquete, utilizando un diseño plano, `/package/module.py`, Python " -"descubrirá el archivo `package/module.py` antes de que descubra el " -"paquete instalado." +"Esto significa que si ejecuta sus pruebas en el directorio de trabajo de su " +"paquete, utilizando un diseño plano, `/package/module.py`, Python descubrirá " +"el archivo `package/module.py` antes de que descubra el paquete instalado." #: ../../package-structure-code/python-package-structure.md:101 msgid "" @@ -5285,10 +5229,10 @@ msgid "" "This means that when you import your package, Python will be forced to " "search the active environment (which has your package installed)." msgstr "" -"Sin embargo, si su paquete se encuentra en una estructura de directorio " -"src/ **src/package**, entonces no se agregará, por defecto, a la ruta de " -"Python. Esto significa que cuando importe su paquete, Python se verá " -"obligado a buscar en el entorno activo (que tiene su paquete instalado)." +"Sin embargo, si su paquete se encuentra en una estructura de directorio src/ " +"**src/package**, entonces no se agregará, por defecto, a la ruta de Python. " +"Esto significa que cuando importe su paquete, Python se verá obligado a buscar " +"en el entorno activo (que tiene su paquete instalado)." #: ../../package-structure-code/python-package-structure.md:103 msgid "" @@ -5296,9 +5240,9 @@ msgid "" "adjusted to ensure the priority is to use installed packages first (e.g. " "`PYTHONSAFEPATH`)." msgstr "" -"Nota: Las versiones de Python 3.11 y superiores tienen un ajuste de ruta " -"que se puede modificar para garantizar que la prioridad sea utilizar " -"primero los paquetes instalados (por ejemplo, `PYTHONSAFEPATH`)." +"Nota: Las versiones de Python 3.11 y superiores tienen un ajuste de ruta que " +"se puede modificar para garantizar que la prioridad sea utilizar primero los " +"paquetes instalados (por ejemplo, `PYTHONSAFEPATH`)." #: ../../package-structure-code/python-package-structure.md:106 msgid "Sometimes tests are needed in a distribution" @@ -5315,22 +5259,21 @@ msgid "" "`tests/` directory into the **src/package** directory (see example " "below)." msgstr "" -"No recomendamos incluir pruebas como parte de su rueda de paquete de " -"forma predeterminada. Sin embargo, no incluir pruebas en su distribución " -"de paquete hará que sea más difícil para las personas que no sean usted " -"mismo probar si su paquete funciona correctamente en su sistema. Si tiene" -" un conjunto de pruebas pequeño (archivos Python + datos) y cree que sus " -"usuarios pueden querer ejecutar pruebas localmente en sus sistemas, puede" -" incluir pruebas moviendo el directorio `tests/` al directorio " -"**src/package** (ver ejemplo a continuación)." +"No recomendamos incluir pruebas como parte de su rueda de paquete de forma " +"predeterminada. Sin embargo, no incluir pruebas en su distribución de paquete " +"hará que sea más difícil para las personas que no sean usted mismo probar si " +"su paquete funciona correctamente en su sistema. Si tiene un conjunto de pruebas " +"pequeño (archivos Python + datos) y cree que sus usuarios pueden querer ejecutar " +"pruebas localmente en sus sistemas, puede incluir pruebas moviendo el directorio " +"`tests/` al directorio **src/package** (ver ejemplo a continuación)." #: ../../package-structure-code/python-package-structure.md:117 msgid "" "Including the **tests/** directory in your **src/package** directory " "ensures that tests will be included in your package's wheel." msgstr "" -"Incluir el directorio **tests/** en su directorio **src/package** asegura" -" que las pruebas se incluirán en la rueda de su paquete." +"Incluir el directorio **tests/** en su directorio **src/package** asegura que " +"las pruebas se incluirán en la rueda de su paquete." #: ../../package-structure-code/python-package-structure.md:119 msgid "" @@ -5339,10 +5282,9 @@ msgid "" "distribution](https://docs.pytest.org/en/7.2.x/explanation/goodpractices.html#choosing-a" "-test-layout-import-rules)." msgstr "" -"Asegúrese de leer la [documentación de pytest para obtener más " -"información sobre cómo incluir pruebas en su distribución de " -"paquete](https://docs.pytest.org/en/7.2.x/explanation/goodpractices.html#choosing-a" -"-test-layout-import-rules)." +"Asegúrese de leer la [documentación de pytest para obtener más información " +"sobre cómo incluir pruebas en su distribución de paquete](https://docs.pytest.org/en/" +"7.2.x/explanation/goodpractices.html#choosing-a-test-layout-import-rules)." #: ../../package-structure-code/python-package-structure.md:121 msgid "Challenges with including tests and data in a package wheel" @@ -5352,8 +5294,7 @@ msgstr "Desafíos al incluir pruebas y datos en una rueda de paquete" msgid "" "Tests, especially when accompanied by test data can create a few small " "challenges including:" -msgstr "" -"Los tests, especialmente cuando van acompañados de datos de prueba, " +msgstr "Los tests, especialmente cuando van acompañados de datos de prueba, " "pueden crear algunos pequeños desafíos, incluyendo:" #: ../../package-structure-code/python-package-structure.md:126 @@ -5361,8 +5302,7 @@ msgid "" "Take up space in your distribution which will build up over time as " "storage space on PyPI" msgstr "" -"Ocupar espacio en su distribución, lo que se acumulará con el tiempo en " -"PyPI" +"Ocupar espacio en su distribución, lo que se acumulará con el tiempo en PyPI" #: ../../package-structure-code/python-package-structure.md:127 msgid "Large file sizes can also slow down package install." @@ -5373,8 +5313,8 @@ msgid "" "However, in some cases, particularly in the scientific Python ecosystems " "you may need to include tests." msgstr "" -"Sin embargo, en algunos casos, particularmente en los ecosistemas " -"científicos de Python, es posible que necesite incluir pruebas." +"Sin embargo, en algunos casos, particularmente en los ecosistemas científicos " +"de Python, es posible que necesite incluir pruebas." #: ../../package-structure-code/python-package-structure.md:132 msgid "**Don't include test suite datasets in your package**" @@ -5389,19 +5329,17 @@ msgid "" "the data when you (or a user) runs tests." msgstr "" "Si incluye sus pruebas en su distribución de paquete, le recomendamos " -"encarecidamente que no incluya datos en su directorio de pruebas. En su " -"lugar, aloje sus datos de prueba en un repositorio como Figshare o " -"Zenodo. Utilice una herramienta como " -"[Pooch](https://www.fatiando.org/pooch/latest/) para acceder a los datos " -"cuando usted (o un usuario) ejecute pruebas." +"encarecidamente que no incluya datos en su directorio de pruebas. En su lugar, " +"aloje sus datos de prueba en un repositorio como Figshare o Zenodo. Utilice " +"una herramienta como [Pooch](https://www.fatiando.org/pooch/latest/) para " +"acceder a los datos cuando usted (o un usuario) ejecute pruebas." #: ../../package-structure-code/python-package-structure.md:140 msgid "" "Check out the testing section of our guide for more information about " "tests." msgstr "" -"Consulte la sección de pruebas de nuestra guía para obtener más " -"información sobre las pruebas." +"Consulte la sección de pruebas de nuestra guía para obtener más información sobre las pruebas." #: ../../package-structure-code/python-package-structure.md:142 msgid "" @@ -5409,9 +5347,9 @@ msgid "" "found in the **src/package** directory, `tests/` and `docs/`are in the " "root directory." msgstr "" -"El diseño **src/package** es semánticamente más claro. El código siempre " -"se encuentra en el directorio **src/package**, `tests/` y `docs/` están " -"en el directorio raíz." +"El diseño **src/package** es semánticamente más claro. El código siempre se " +"encuentra en el directorio **src/package**, `tests/` y `docs/` están en el " +"directorio raíz." #: ../../package-structure-code/python-package-structure.md:146 msgid "" @@ -5422,12 +5360,12 @@ msgid "" "repositories like PyPI and Anaconda.org that have to deal with thousands " "of package uploads." msgstr "" -"Si las pruebas de su paquete requieren datos, le sugerimos que NO incluya" -" esos datos en su estructura de paquete. Discutiremos esto con más " -"detalle en un tutorial. Incluir datos en su estructura de paquete aumenta" -" el tamaño de los archivos de su distribución. Esto impone un peaje de " -"mantenimiento en repositorios como PyPI y Anaconda.org que tienen que " -"lidiar con miles de paquetes subidos." +"Si las pruebas de su paquete requieren datos, le sugerimos que NO incluya " +"esos datos en su estructura de paquete. Discutiremos esto con más detalle en " +"un tutorial. Incluir datos en su estructura de paquete aumenta el tamaño de " +"los archivos de su distribución. Esto impone un peaje de mantenimiento en " +"repositorios como PyPI y Anaconda.org que tienen que lidiar con miles de " +"paquetes subidos." #: ../../package-structure-code/python-package-structure.md:153 msgid "About the flat Python package layout" @@ -5435,9 +5373,7 @@ msgstr "Sobre el diseño plano de paquetes de Python" #: ../../package-structure-code/python-package-structure.md:155 msgid "Currently most scientific packages use the **flat-layout** given:" -msgstr "" -"Actualmente, la mayoría de los paquetes científicos utilizan el **diseño " -"plano** dado:" +msgstr "Actualmente, la mayoría de los paquetes científicos utilizan el **diseño plano** dado:" #: ../../package-structure-code/python-package-structure.md:157 msgid "" @@ -5445,9 +5381,9 @@ msgid "" "and people tend to look to other packages / maintainers that they respect" " for examples of how to build Python packages." msgstr "" -"Es el diseño más común en el ecosistema científico de Python y las " -"personas tienden a buscar otros paquetes / mantenedores que respetan como" -" ejemplos de cómo construir paquetes de Python." +"Es el diseño más común en el ecosistema científico de Python " +"y las personas tienden a buscar otros paquetes / mantenedores que respetan " +"como ejemplos de cómo construir paquetes de Python." #: ../../package-structure-code/python-package-structure.md:160 msgid "" @@ -5455,10 +5391,9 @@ msgid "" "builds with compilation steps. Many developers thus appreciate / are used" " to features of the flat layout." msgstr "" -"Muchas herramientas de Python dependen de herramientas en otros idiomas " -"y/o construcciones complejas con pasos de compilación. Por lo tanto, " -"muchos desarrolladores aprecian/están acostumbrados a las características" -" del diseño plano." +"Muchas herramientas de Python dependen de herramientas en otros idiomas y/o " +"construcciones complejas con pasos de compilación. Por lo tanto, muchos " +"desarrolladores aprecian/están acostumbrados a las características del diseño plano." #: ../../package-structure-code/python-package-structure.md:164 msgid "" @@ -5468,17 +5403,16 @@ msgid "" "move to a src/ layout](https://github.com/scikit-build/cmake-python-" "distributions/pull/145)" msgstr "" -"Aunque presentamos este diseño aquí en nuestra guía, sugerimos que " -"aquellos que recién comienzan con el empaquetado de Python comiencen con " -"el diseño src/package discutido anteriormente. Numerosos paquetes en el " -"ecosistema [han tenido que moverse a un diseño src/](https://github.com" -"/scikit-build/cmake-python-distributions/pull/145)" +"Aunque presentamos este diseño aquí en nuestra guía, sugerimos que aquellos " +"que recién comienzan con el empaquetado de Python comiencen con el diseño " +"src/package discutido anteriormente. Numerosos paquetes en el ecosistema " +"[han tenido que moverse a un diseño src/]" +"(https://github.com/scikit-build/cmake-python-" +"distributions/pull/145)" #: ../../package-structure-code/python-package-structure.md:169 msgid "Why most scientific Python packages do not use source" -msgstr "" -"¿Por qué la mayoría de los paquetes científicos de Python no usan el " -"código fuente?" +msgstr "¿Por qué la mayoría de los paquetes científicos de Python no usan el código fuente?" #: ../../package-structure-code/python-package-structure.md:172 msgid "" @@ -5487,10 +5421,10 @@ msgid "" "it. Moving from a flat layout to a **src/package** layout would come at a" " significant cost to maintainers." msgstr "" -"En la mayoría de los casos, las ventajas de usar el diseño " -"**src/package** para paquetes científicos más grandes que ya utilizan un " -"enfoque plano no merecen la pena. Pasar de un diseño plano a un diseño " -"**src/package** supondría un costo significativo para los mantenedores." +"En la mayoría de los casos, las ventajas de usar el diseño **src/package** " +"para paquetes científicos más grandes que ya utilizan un enfoque plano no " +"merecen la pena. Pasar de un diseño plano a un diseño **src/package** " +"supondría un costo significativo para los mantenedores." #: ../../package-structure-code/python-package-structure.md:177 msgid "" @@ -5499,9 +5433,9 @@ msgid "" "started with creating a package, that you consider using a " "**src/package** layout." msgstr "" -"Sin embargo, las ventajas de usar el diseño **src/package** para un " -"principiante son significativas. Por lo tanto, recomendamos que si está " -"comenzando a crear un paquete, considere usar un diseño **src/package**." +"Sin embargo, las ventajas de usar el diseño **src/package** para un principiante " +"son significativas. Por lo tanto, recomendamos que si está comenzando a crear un " +"paquete, considere usar un diseño **src/package**." #: ../../package-structure-code/python-package-structure.md:182 msgid "What does the flat layout structure look like?" @@ -5516,24 +5450,24 @@ msgid "" "The source code for your package lives in a directory with your package's" " name in the root of your directory" msgstr "" -"El código fuente de su paquete se encuentra en un directorio con el " -"nombre de su paquete en la raíz de su directorio" +"El código fuente de su paquete se encuentra en un directorio con el nombre de " +"su paquete en la raíz de su directorio" #: ../../package-structure-code/python-package-structure.md:188 msgid "" "Often the `tests/` directory also lives within that same `package` " "directory." msgstr "" -"A menudo, el directorio `tests/` también se encuentra dentro de ese mismo" -" directorio `package`." +"A menudo, el directorio `tests/` también se encuentra dentro de ese mismo " +"directorio `package`." #: ../../package-structure-code/python-package-structure.md:190 msgid "" "Below you can see the recommended structure of a scientific Python " "package using the flat layout." msgstr "" -"A continuación, puede ver la estructura recomendada de un paquete " -"científico de Python que utiliza el diseño plano." +"A continuación, puede ver la estructura recomendada de un paquete científico " +"de Python que utiliza el diseño plano." #: ../../package-structure-code/python-package-structure.md:212 msgid "Benefits of using the flat layout in your Python package" @@ -5544,16 +5478,15 @@ msgid "" "There are some benefits to the scientific community in using the flat " "layout." msgstr "" -"Existen algunos beneficios para la comunidad científica al utilizar el " -"diseño plano." +"Existen algunos beneficios para la comunidad científica al utilizar el diseño plano." #: ../../package-structure-code/python-package-structure.md:216 msgid "" "This structure has historically been used across the ecosystem and " "packages using it are unlikely to change." msgstr "" -"Esta estructura se ha utilizado históricamente en todo el ecosistema y es" -" poco probable que los paquetes que la utilizan cambien." +"Esta estructura se ha utilizado históricamente en todo el ecosistema y es poco probable " +"que los paquetes que la utilizan cambien." #: ../../package-structure-code/python-package-structure.md:218 msgid "" @@ -5563,11 +5496,11 @@ msgid "" "against the installed version of your package. Rather, you are working " "directly with the flat files." msgstr "" -"Puede importar el paquete directamente desde el directorio raíz. Para " -"algunos, esto está arraigado en sus respectivos flujos de trabajo. Sin " -"embargo, para un principiante, el peligro de hacer esto es que no está " -"desarrollando y probando contra la versión instalada de su paquete. En " -"cambio, está trabajando directamente con los archivos planos." +"Puede importar el paquete directamente desde el directorio raíz. Para algunos, " +"esto está arraigado en sus respectivos flujos de trabajo. Sin embargo, para un " +"principiante, el peligro de hacer esto es que no está desarrollando y probando " +"contra la versión instalada de su paquete. En cambio, está trabajando directamente " +"con los archivos planos." #: ../../package-structure-code/python-package-structure.md:224 msgid "Core scientific Python packages that use the flat layout" @@ -5607,9 +5540,9 @@ msgid "" "these packages to a different layout. The potential benefits of the " "source layout for these tools is not worth the maintenance investment." msgstr "" -"Sería un costo y una carga de mantenimiento significativos mover todos " -"estos paquetes a un diseño diferente. Los posibles beneficios del diseño " -"src para estas herramientas no valen la inversión en mantenimiento." +"Sería un costo y una carga de mantenimiento significativos mover todos estos " +"paquetes a un diseño diferente. Los posibles beneficios del diseño src para " +"estas herramientas no valen la inversión en mantenimiento." #: ../../package-structure-code/python-package-versions.md:1 msgid "Creating New Versions of Your Python Package" @@ -5677,7 +5610,7 @@ msgstr "" msgid "" "Consistent version increases following semver rules mean that values of " "your package version explain the extent of the changes made in the code " -"base from version to version. Thus your package version numbers become " +"base from version to version. thus your package version numbers become " "\"expressive\" in the same way that naming code variables well can [make " "code expressive](https://medium.com/@daniel.oliver.king/writing-" "expressive-code-b69ef7a5a2fa)." @@ -5841,7 +5774,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:107 msgid "" "Generally semantic release and version control system tools can be setup " -"to run automatically on GitHub using GitHub Actions. This means that you " +"to run automatically on GitHub using GitHub actions. This means that you " "can create a workflow where a GitHub release and associated new version " "tag is used to trigger an automated build that:" msgstr "" @@ -5862,7 +5795,7 @@ msgstr "" msgid "" "Bumping a package version refers to the step of increasing the package " "version after a set number of changes have been made to it. For example, " -"you might bump from version 0.8 to 0.9 of a package or from 0.9 to 1.0." +"you might bump from version 0.8 to 0.9 of a package. or from 0.9 to 1.0." msgstr "" #: ../../package-structure-code/python-package-versions.md:122 @@ -5972,7 +5905,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:173 msgid "" "When you (or your CI system) build your package, hatch checks the current" -" tag number for your package. If it has increased, it will update the " +" tag number for your package. if it has increased, it will update the " "**\\_version.py** file with the new value." msgstr "" @@ -6206,184 +6139,3 @@ msgid "" "The version number is manually updated in a configuration file such as " "`pyproject.toml` vs. in a package **\\_version.py** file." msgstr "" - -#~ msgid "" -#~ "The pre-commit workflow begins with " -#~ "you adding files that have changes " -#~ "to be staged in git. Next, you'd" -#~ " run git commit. when you run " -#~ "git commit, the pre-commit hooks " -#~ "will then run. In this example, " -#~ "Black, the code formatter and flake8," -#~ " a linter both run. If all of" -#~ " the files pass Black and flake8 " -#~ "checks, then your commit will be " -#~ "recorded. If they don't, the commit " -#~ "is canceled. You will have to fix" -#~ " any flake8 issues, and then re-" -#~ "add / stage the files to be " -#~ "committed. [_Image " -#~ "Source_](https://ljvmiranda921.github.io/notebook/2018/06/21" -#~ "/precommits-using-black-and-flake8/*)" -#~ msgstr "" - -#~ msgid "" -#~ "keep this comment - " -#~ "https://github.com/pyOpenSci/python-package-" -#~ "guide/pull/106#issuecomment-1844278487 in this file" -#~ " for now - jeremiah did a nice" -#~ " inventory of common shells and " -#~ "whether they need quotes or not. " -#~ "it's really comprehensive. but do we " -#~ "want it in the guide?? it's really" -#~ " useful for more advanced users i " -#~ "think." -#~ msgstr "" - -#~ msgid "needs to function properly." -#~ msgstr "" - -#~ msgid "" -#~ "requires if someone wants to develop " -#~ "/ work on improving your package " -#~ "locally or" -#~ msgstr "" - -#~ msgid "" -#~ "requires if a user wants to add" -#~ " additional functionality (that is not " -#~ "core) to your package" -#~ msgstr "" - -#~ msgid "" -#~ "Diagram showing a ven diagram with " -#~ "three sections representing the dependency " -#~ "groups listed above - docs feature " -#~ "and tests. In the center it says" -#~ " your-package and lists the core " -#~ "dependencies of that package seaborn and" -#~ " numpy. To the right are two " -#~ "arrows. The first shows the command " -#~ "python - m pip install your-" -#~ "package. it them shows how installing" -#~ " your package that way installs only" -#~ " the package and the two core " -#~ "dependencies into a users environment. " -#~ "Below is a second arrow with " -#~ "python -m pip install youPackage[tests]. " -#~ "This leads to an environment with " -#~ "both the package dependencies - your-" -#~ "package, seaborn and numpy and also " -#~ "the tests dependencies including pytest " -#~ "and pytest-cov" -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "Graphic with the title Python package" -#~ " repositories. Below it says Anything " -#~ "hosted on PyPI can be installed " -#~ "using pip install. Packaging hosted on" -#~ " a conda channel can be installed " -#~ "using conda install. Below that there" -#~ " are two rows. the top row says" -#~ " conda channels. next to it are " -#~ "three boxes one with conda-forge, " -#~ "community maintained; bioconda and then " -#~ "default - managed by the anaconda " -#~ "team. Below that there is a row" -#~ " that says PyPI servers. PyPI - " -#~ "anyone can publish to PyPI. and " -#~ "test PyPI. a testbed server for " -#~ "you to practice." -#~ msgstr "" - -#~ msgid "" -#~ "Here is an example of[ a package" -#~ " that has entry point " -#~ "script](https://github.com/pyOpenSci/update-web-" -#~ "metadata/blob/main/pyproject.toml#L60)s. Notice that " -#~ "there are several core scripts defined" -#~ " in that package that perform sets" -#~ " of tasks. pyOpenSci is using those" -#~ " scripts to process their metadata." -#~ msgstr "" - -#~ msgid "" -#~ "**Dynamic Fields:** if you have fields" -#~ " that are dynamically populated. One " -#~ "example of this is if you are " -#~ "using scm / version control based " -#~ "version with tools like `setuptooms_scm`, " -#~ "then you might use the dynamic " -#~ "field. such as version (using scm) " -#~ "**dynamic = [\"version\"]**" -#~ msgstr "" - -#~ msgid "" -#~ "Consistent version increases following semver" -#~ " rules mean that values of your " -#~ "package version explain the extent of" -#~ " the changes made in the code " -#~ "base from version to version. thus " -#~ "your package version numbers become " -#~ "\"expressive\" in the same way that " -#~ "naming code variables well can [make " -#~ "code expressive](https://medium.com/@daniel.oliver.king" -#~ "/writing-expressive-code-b69ef7a5a2fa)." -#~ msgstr "" - -#~ msgid "" -#~ "Generally semantic release and version " -#~ "control system tools can be setup " -#~ "to run automatically on GitHub using " -#~ "GitHub actions. This means that you " -#~ "can create a workflow where a " -#~ "GitHub release and associated new " -#~ "version tag is used to trigger an" -#~ " automated build that:" -#~ msgstr "" - -#~ msgid "" -#~ "Bumping a package version refers to " -#~ "the step of increasing the package " -#~ "version after a set number of " -#~ "changes have been made to it. For" -#~ " example, you might bump from version" -#~ " 0.8 to 0.9 of a package. or" -#~ " from 0.9 to 1.0." -#~ msgstr "" - -#~ msgid "" -#~ "When you (or your CI system) build" -#~ " your package, hatch checks the " -#~ "current tag number for your package. " -#~ "if it has increased, it will " -#~ "update the **\\_version.py** file with " -#~ "the new value." -#~ msgstr "" diff --git a/locales/es/LC_MESSAGES/tests.po b/locales/es/LC_MESSAGES/tests.po index b2cfc0c0..07c076ae 100644 --- a/locales/es/LC_MESSAGES/tests.po +++ b/locales/es/LC_MESSAGES/tests.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-06-14 09:22-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Felipe Moreno \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../tests/index.md:72 msgid "Intro" @@ -118,9 +118,8 @@ msgid "✨ Run tests online (using CI) ✨" msgstr "✨ Ejecuta pruebas en línea (usando CI) ✨" #: ../../tests/index.md:58 -#, fuzzy msgid "" -"Continuous integration platforms such as GitHub Actions can be useful for" +"Continuous integration platforms such as GitHub actions can be useful for" " running your tests across both different Python versions and different " "operating systems. Learn about setting up tests to run in Continuous " "Integration here." @@ -487,11 +486,13 @@ msgid "Other automation tools you'll see in the wild" msgstr "Otras herramientas de automatización que encontrarás" #: ../../tests/run-tests.md:125 -#, fuzzy msgid "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** is an " "automation tool that supports common steps such as building " "documentation, running tests across various versions of Python, and more." +" You can find [a nice overview of tox in the plasmaPy " +"documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" +"#using-tox)." msgstr "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** es una " "herramienta de automatización que admite pasos comunes como la " @@ -1097,14 +1098,12 @@ msgstr "" "localmente." #: ../../tests/tests-ci.md:22 -#, fuzzy -msgid "Example GitHub Actions that runs tests" +msgid "Example GitHub action that runs tests" msgstr "Ejemplo de acción de GitHub que ejecuta pruebas" #: ../../tests/tests-ci.md:24 -#, fuzzy msgid "" -"Below is an example GitHub Actions that runs tests using nox across both " +"Below is an example GitHub action that runs tests using nox across both " "Windows, Mac and Linux and on Python versions 3.9-3.11." msgstr "" "Abajo hay un ejemplo de una acción de GitHub que ejecuta pruebas " @@ -1229,10 +1228,9 @@ msgstr "" " mismo." #: ../../tests/write-tests.md:21 -#, fuzzy msgid "" "**Easier pull request reviews:** By running your tests in a CI framework " -"such as GitHub Actions, each time you or a contributor makes a change to " +"such as GitHub actions, each time you or a contributor makes a change to " "your code-base, you can catch issues and things that may have changed in " "your code base. This ensures that your software behaves the way you " "expect it to." diff --git a/locales/es/LC_MESSAGES/tutorials.po b/locales/es/LC_MESSAGES/tutorials.po index f9e841a8..9dbb7a74 100644 --- a/locales/es/LC_MESSAGES/tutorials.po +++ b/locales/es/LC_MESSAGES/tutorials.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-06-28 08:42-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: es\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../tutorials/add-license-coc.md:1 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" @@ -39,9 +39,8 @@ msgid "" " " "Learned about the core components that are useful to have in a `README` " "file." -msgstr "" -"Aprendiste acerca de los componentes principales que son útiles de tener " -"en un archivo `README`." +msgstr "Aprendiste acerca de los componentes principales que son útiles de tener en " +"un archivo `README`." #: ../../tutorials/add-license-coc.md:9 ../../tutorials/add-readme.md:10 msgid "Learning objectives" @@ -57,8 +56,7 @@ msgstr "En esta lección aprenderas:" msgid "" "How to select a license and add a `LICENSE` file to your package " "repository, with a focus on the GitHub interface." -msgstr "" -"Como seleccionar una licencia y agregar un archivo `LICENSE` al " +msgstr "Como seleccionar una licencia y agregar un archivo `LICENSE` al " "repositorio de tu paquete, con enfoque en la interface de Github" #: ../../tutorials/add-license-coc.md:15 @@ -69,9 +67,8 @@ msgstr "Como agregar un archivo `CODE_OF_CONDUCT` al repositorio de tu paquete" msgid "" "How you can use the Contributors Covenant website to add generic language" " as a starting place for your `CODE_OF_CONDUCT`." -msgstr "" -"Como usar el sitio web de Contributors Covenant para agregar lenguage " -"genérico como punto de partida para tu `CODE_OF_CONDUCT`" +msgstr "Como usar el sitio web de Contributors Covenant para agregar lenguage" +" genérico como punto de partida para tu `CODE_OF_CONDUCT`" #: ../../tutorials/add-license-coc.md:19 msgid "What is a license?" @@ -81,26 +78,21 @@ msgstr "¿Qué es una licencia?" msgid "" "A license contains legal language about how users can use and reuse your " "software. To set the `LICENSE` for your project, you:" -msgstr "" -"Una licencia contiene lenguaje legal acerca de como los usuarios pueden " -"usar y reusar tu software. Para establecer un archivo `LICENSE` para tu " -"projecto, tu: " +msgstr "Una licencia contiene lenguaje legal acerca de como los usuarios pueden " +"usar y reusar tu software. Para establecer un archivo `LICENSE` para tu" +" projecto, tu: " #: ../../tutorials/add-license-coc.md:23 -#, fuzzy msgid "" -"Create a `LICENSE` file in your project directory that specifies the " -"license that you choose for your package." -msgstr "" -"creas un archivo `LICENSE` en el directorio de tu proyecto que " +"create a `LICENSE` file in your project directory that specifies the " +"license that you choose for your package and" +msgstr "creas un archivo `LICENSE` en el directorio de tu proyecto que " "especifique la licencia que que elejiste para tu paquete y" #: ../../tutorials/add-license-coc.md:24 -#, fuzzy -msgid "Reference that file in your `pyproject.toml` data where metadata are set." -msgstr "" -"haces referencia a ese archivo en el `pyproject.toml` donde la metadata " -"es especificada" +msgid "reference that file in your `pyproject.toml` data where metadata are set." +msgstr "haces referencia a ese archivo en el `pyproject.toml` donde la metadata" +" es especificada" #: ../../tutorials/add-license-coc.md:26 msgid "" @@ -108,11 +100,10 @@ msgid "" " will be included in your package's metadata which is used to populate " "your package's PyPI landing page. The `LICENSE` is also used in your " "GitHub repository's landing page interface." -msgstr "" -"Al incluir el archivo `LICENSE` en tu archivo `pyproject.toml`, la " -"`LICENSE` sera incluída en la metadata de tu paquete y esta es utilizada " -"para rellenar la página de entrada de tu paquete en PyPI. La `LICENSE` " -"también es utilizada en la página de entrada de tu repositorio de GitHub" +msgstr "Al incluir el archivo `LICENSE` en tu archivo `pyproject.toml`, la " +"`LICENSE` sera incluída en la metadata de tu paquete y esta es utilizada para" +" rellenar la página de entrada de tu paquete en PyPI. La `LICENSE` también es " +" utilizada en la página de entrada de tu repositorio de GitHub" #: ../../tutorials/add-license-coc.md:28 msgid "What license should you use?" @@ -124,12 +115,10 @@ msgid "" "most commonly used licenses in the scientific Python ecosystem (MIT[^mit]" " and BSD-3[^bsd3]). If you are unsure, use MIT given it's the generally " "recommended license on [choosealicense.com](https://choosealicense.com/)." -msgstr "" -"Nosotros sugerimos que uses una licencia permissiva que acomode otras " -"licencias comúnmente usadas en el ecosistema de Python científico " -"(MIT[^mit] and BSD-3[^bsd3]). Si tienes dudas, usa MIT dado que es la " -"licencia generalmente recomendada en " -"[choosealicense.com](https://choosealicense.com/)" +msgstr "Nosotros sugerimos que uses una licencia permissiva que acomode otras" +" licencias comúnmente usadas en el ecosistema de Python científico (MIT[^mit]" +" and BSD-3[^bsd3]). Si tienes dudas, usa MIT dado que es la licencia" +" generalmente recomendada en [choosealicense.com](https://choosealicense.com/)" #: ../../tutorials/add-license-coc.md:33 msgid "Licenses for the scientific Python ecosystem" @@ -937,231 +926,116 @@ msgstr "" msgid "Discourages misuse of your package and associated code" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:1 -msgid "Get to Know Hatch" +#: ../../tutorials/get-to-know-hatch.md:1 ../../tutorials/intro.md:27 +#: ../../tutorials/setup-py-to-pyproject-toml.md:24 +msgid "Get to know Hatch" msgstr "" #: ../../tutorials/get-to-know-hatch.md:3 msgid "" -"Our Python packaging tutorials use the tool " -"[Hatch](https://hatch.pypa.io/latest/). While there are [many great " -"packaging tools](/package-structure-code/python-package-build-tools) out " -"there, we have selected Hatch because:" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:8 -msgid "" -"It is an end-to-end tool that supports most of the steps required to " -"create a quality Python package. Beginners will have fewer tools to learn" -" if they use Hatch." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:11 -msgid "" -"It supports different build back-ends if you ever need to compile code in" -" other languages." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:13 -msgid "" -"As a community, pyOpenSci has decided that Hatch is a user-friendly tool " -"that supports many different scientific Python use cases." +"Our Python packaging tutorials use the tool Hatch. In this tutorial, you " +"will install and get to know Hatch a bit more before starting to use it." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:16 -msgid "" -"In this tutorial, you will install and get to know Hatch a bit more " -"before starting to use it." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:19 -msgid "You need two things to successfully complete this tutorial:" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:21 -msgid "You need Python installed." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:22 -msgid "You need Hatch installed." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:25 -msgid "" -"If you don't already have Python installed on your computer, Hatch will " -"do it for you when you install Hatch." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:29 +#: ../../tutorials/get-to-know-hatch.md:6 msgid "Install Hatch" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:31 +#: ../../tutorials/get-to-know-hatch.md:7 msgid "" -"To begin, follow the operating-system-specific instructions below to " -"install Hatch." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md -msgid "MAC" +"To begin, install Hatch from the command line using " +"[pipx](https://pipx.pypa.io/stable/)" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:38 +#: ../../tutorials/get-to-know-hatch.md:14 msgid "" -"Follow the instructions " -"[here](https://hatch.pypa.io/latest/install/#installers)." +"Hatch can also be installed directly using `pip` or `conda`, but we " +"encourage you to use `pipx`. This is because `pipx` will ensure that your" +" package is available across all of your Python environments on your " +"computer rather than just in the environment that you install it into. If" +" you install hatch this way you will have to take care that the " +"environment it is installed into is activated for the command to work." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:40 -msgid "" -"Download the latest GUI installer for MAC [hatch-" -"universal.pkg](https://github.com/pypa/hatch/releases/latest/download" -"/hatch-universal.pkg)." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:41 -msgid "Run the installer and follow the setup instructions." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:42 -msgid "If your terminal is open, then restart it." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md -msgid "Windows" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:48 -msgid "" -"In your browser, download the correct `.msi` file for your system: " -"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch-x64.msi)" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:50 -msgid "Run your downloaded installer file and follow the on-screen instructions." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md -msgid "Linux" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:56 -msgid "" -"We suggest that you install Hatch using pipx on Linux. however, if you " -"prefer another method, check out the [Hatch installation " -"documentation](https://hatch.pypa.io/latest/install/) for other methods." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:70 -msgid "" -"Hatch can also be installed directly using " -"[pip](https://hatch.pypa.io/latest/install/#pip) or " -"[conda](https://hatch.pypa.io/latest/install/#conda). We encourage you to" -" follow the instructions above because we have found that the Hatch " -"installers for Windows and Mac are the easiest and most efficient." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:74 -msgid "" -"Our Linux users have found success installing Hatch with pipx if they " -"already use apt install." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:77 +#: ../../tutorials/get-to-know-hatch.md:21 msgid "" -"Both approaches (using a graphical installer on Windows/Mac and pipx) " -"ensure that you have Hatch installed globally. A global install means " -"that Hatch is available across all of your Python environments on your " -"computer." +"You can check that hatch is working properly by issuing a simple command " +"to get the version" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:82 -msgid "Check that hatch installed correctly" +#: ../../tutorials/get-to-know-hatch.md:28 +msgid "Note the version numbers will likely be different" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:84 -msgid "" -"Once you have completed the installation instructions above, you can open" -" your terminal, and make sure that Hatch installed correctly using the " -"command below:" +#: ../../tutorials/get-to-know-hatch.md:30 +msgid "Configure hatch" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:92 +#: ../../tutorials/get-to-know-hatch.md:32 msgid "" -"*Note the version number output of `hatch --version` will likely be " -"different from the output above in this tutorial.*" -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:95 -msgid "Configure Hatch" +"Once you have installed Hatch, you will want to customize the " +"configuration." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:97 +#: ../../tutorials/get-to-know-hatch.md:34 msgid "" -"Once you have installed Hatch, you can customize its configuration. This " -"includes setting the default name and setup for every package you create." -" While this step is not required, we suggest that you do it." -msgstr "" - -#: ../../tutorials/get-to-know-hatch.md:101 -msgid "" -"Hatch stores your configuration in a [`config.toml` " +"Hatch stores your configuration information in a [`config.toml` " "file](https://hatch.pypa.io/latest/config/project-templates/)." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:103 +#: ../../tutorials/get-to-know-hatch.md:36 msgid "" "While you can update the `config.toml` file through the command line, it " -"might be easier to look at and update it in a text editor if you are " +"might be easier to look at it and update it in a text editor if you are " "using it for the first time." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:107 -msgid "Step 1: Open and Edit Your `config.toml` File" +#: ../../tutorials/get-to-know-hatch.md:39 +msgid "Step 1: Open and edit your `config.toml` file" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:109 +#: ../../tutorials/get-to-know-hatch.md:41 msgid "" "To open the config file in your file browser, run the following command " "in your shell:" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:112 +#: ../../tutorials/get-to-know-hatch.md:43 msgid "`hatch config explore`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:114 +#: ../../tutorials/get-to-know-hatch.md:45 msgid "" -"This will open up a directory window that allows you to double-click on " -"the file and open it in your favorite text editor." +"This will open up a directory window that will allow you to double click " +"on the file and open it in your favorite text editor." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:117 +#: ../../tutorials/get-to-know-hatch.md:47 msgid "" "You can also retrieve the location of the Hatch config file by running " "the following command in your shell:" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:125 +#: ../../tutorials/get-to-know-hatch.md:54 msgid "Step 2 - update your email and name" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:127 +#: ../../tutorials/get-to-know-hatch.md:56 msgid "" "Once the file is open, update the [template] table of the `config.toml` " "file with your name and email. This information will be used in any " "`pyproject.toml` metadata files that you create using Hatch." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:137 +#: ../../tutorials/get-to-know-hatch.md:64 msgid "Step 3" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:139 +#: ../../tutorials/get-to-know-hatch.md:66 msgid "Next, set tests to false in the `[template.plugins.default]` table." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:141 +#: ../../tutorials/get-to-know-hatch.md:68 msgid "" "While tests are important, setting the tests configuration in Hatch to " "`true` will create a more complex `pyproject.toml` file. You won't need " @@ -1169,11 +1043,11 @@ msgid "" " introduce it in later tutorials." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:146 +#: ../../tutorials/get-to-know-hatch.md:73 msgid "Your `config.toml` file should look something like the one below." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:184 +#: ../../tutorials/get-to-know-hatch.md:111 msgid "" "Also notice that the default license option is MIT. While we will discuss" " license in more detail in a later lesson, the MIT license is the " @@ -1182,11 +1056,11 @@ msgid "" "use it for this tutorial series." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:190 +#: ../../tutorials/get-to-know-hatch.md:116 msgid "You are of course welcome to select another license." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:192 +#: ../../tutorials/get-to-know-hatch.md:118 #: ../../tutorials/installable-code.md:22 #: ../../tutorials/installable-code.md:411 #: ../../tutorials/installable-code.md:502 ../../tutorials/intro.md:226 @@ -1195,84 +1069,84 @@ msgstr "" msgid "Todo" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:193 +#: ../../tutorials/get-to-know-hatch.md:119 msgid "" "I think we'd need the SPDX license options here if they want to chose " "bsd-3 for instance" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:196 +#: ../../tutorials/get-to-know-hatch.md:122 msgid "Step 4: Close the config file and run `hatch config show`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:198 +#: ../../tutorials/get-to-know-hatch.md:124 msgid "" "Once you have completed the steps above run the following command in your" " shell." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:200 +#: ../../tutorials/get-to-know-hatch.md:126 msgid "`hatch config show`" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:202 +#: ../../tutorials/get-to-know-hatch.md:128 msgid "" "`hatch config show` will print out the contents of your `config.toml` " -"file in your shell. Look at the values and ensure that your name, email " +"file in your shell. look at the values and ensure that your name, email " "is set. Also make sure that `tests=false`." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:206 +#: ../../tutorials/get-to-know-hatch.md:130 msgid "Hatch features" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:208 +#: ../../tutorials/get-to-know-hatch.md:132 msgid "" "Hatch offers a suite of features that will make creating, publishing and " "maintaining your Python package easier." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:211 +#: ../../tutorials/get-to-know-hatch.md:135 msgid "Comparison to other tools" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:213 +#: ../../tutorials/get-to-know-hatch.md:137 msgid "" "[We compared Hatch to several of the other popular packaging tools in the" " ecosystem including flit, pdm and poetry. Learn more here](package-" "features)" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:216 +#: ../../tutorials/get-to-know-hatch.md:140 msgid "[More on Hatch here](hatch)" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:218 +#: ../../tutorials/get-to-know-hatch.md:142 msgid "A few features that Hatch offers" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:220 +#: ../../tutorials/get-to-know-hatch.md:145 msgid "" -"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " +"it will convert metadata stored in a `setup.py` or `setup.cfg` file to a " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:222 +#: ../../tutorials/get-to-know-hatch.md:147 msgid "" "It will help you by storing configuration information for publishing to " "PyPI after you've entered it once." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:224 +#: ../../tutorials/get-to-know-hatch.md:149 msgid "Use `hatch -h` to see all of the available commands." msgstr "" -#: ../../tutorials/get-to-know-hatch.md:226 +#: ../../tutorials/get-to-know-hatch.md:152 msgid "What's next" msgstr "" -#: ../../tutorials/get-to-know-hatch.md:228 +#: ../../tutorials/get-to-know-hatch.md:154 msgid "" "In the next lesson you'll learn how to package and make your code " "installable using Hatch." @@ -1322,7 +1196,7 @@ msgstr "" msgid "" "ADD: note about what makes something \"package worthy\", with a common " "misconception being that a package should be production-ready code that's" -" valuable to a broad audience. This may not be a pervasive misconception " +" valuable to a broad audience. this may not be a pervasive misconception " "in Python, but a quick break-out with an explanation of what a package " "can consist of would be helpful." msgstr "" @@ -1459,7 +1333,7 @@ msgid "An `__init__.py` file in your code directory." msgstr "" #: ../../tutorials/installable-code.md:83 -msgid "The directory structure you'll create in this lesson will look like this:" +msgid "The directory structure you’ll create in this lesson will look like this:" msgstr "" #: ../../tutorials/installable-code.md:95 @@ -1533,7 +1407,7 @@ msgstr "" #: ../../tutorials/installable-code.md:121 msgid "" -"Where you define your project's metadata (including its name, authors, " +"Where you define your project’s metadata (including its name, authors, " "license, etc)" msgstr "" @@ -1758,7 +1632,7 @@ msgstr "" #: ../../tutorials/installable-code.md:282 msgid "" -"If you aren't familiar with docstrings or typing yet, that is ok. You can" +"If you aren’t familiar with docstrings or typing yet, that is ok. You can" " review [this page in the pyOpenSci packaging " "guide](https://www.pyopensci.org/python-package-guide/documentation" "/write-user-documentation/document-your-code-api-docstrings.html) for an " @@ -1925,7 +1799,7 @@ msgstr "" #: ../../tutorials/installable-code.md:482 msgid "" "Once you have your project metadata in the pyproject.toml file, you will " -"rarely update it. In the next lesson you'll add more metadata and " +"rarely update it. In the next lesson you’ll add more metadata and " "structure to this file." msgstr "" @@ -2177,10 +2051,6 @@ msgstr "" msgid "[epydoc](https://epydoc.sourceforge.net/epytext.html)" msgstr "" -#: ../../tutorials/intro.md:27 ../../tutorials/setup-py-to-pyproject-toml.md:24 -msgid "Get to know Hatch" -msgstr "" - #: ../../tutorials/intro.md:27 msgid "Python Packaging Tutorial Setup" msgstr "" @@ -2890,8 +2760,8 @@ msgid "" "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 " +"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." @@ -3062,7 +2932,7 @@ msgstr "" msgid "" "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 " +"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." @@ -3410,7 +3280,7 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:279 msgid "" "There is currently a small bug in Grayskull where it doesn't populate the" -" home: element of the recipe. If you don't include this, [you will " +" home: element of the recipe. if you don't include this, [you will " "receive an error message](https://github.com/conda-forge/staged-" "recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" " linter bot." @@ -3958,8 +3828,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:60 msgid "" "In a future lesson, you will learn how to create an automated GitHub " -"Actions workflow that publishes an updated version of your package to " -"PyPI every time you create a GitHub release." +"action workflow that publishes an updated version of your package to PyPI" +" every time you create a GitHub release." msgstr "" #: ../../tutorials/publish-pypi.md:64 @@ -4496,10 +4366,10 @@ msgstr "" #: ../../tutorials/publish-pypi.md:363 msgid "" "You can also create an automated publication workflow on GitHub using " -"GitHub Actions. This is a great way to make the publication process " +"GitHub actions. This is a great way to make the publication process " "easier and it also supports a growing maintainer team. In this case we " "suggest you don't worry about the token and instead setup a specific " -"GitHub Actions that publishes your package when you make a release. You " +"GitHub action that publishes your package when you make a release. You " "can then create a \"trusted publisher\" workflow on PyPI." msgstr "" @@ -4689,7 +4559,7 @@ msgstr "" #: ../../tutorials/pyproject-toml.md:43 msgid "" "When you are adding classifiers to the **[project]** table, only use " -"valid values from [PyPI's classifier " +"valid values from [PyPI’s classifier " "page](https://PyPI.org/classifiers/). An invalid value here will raise an" " error when you build and publish your package on PyPI." msgstr "" @@ -5558,215 +5428,3 @@ msgid "" "existing functionality remains intact. Run any pre-existing tests to " "verify that everything still works as expected." msgstr "" - -#~ msgid "" -#~ "Our Python packaging tutorials use the" -#~ " tool Hatch. In this tutorial, you" -#~ " will install and get to know " -#~ "Hatch a bit more before starting " -#~ "to use it." -#~ msgstr "" - -#~ msgid "" -#~ "To begin, install Hatch from the " -#~ "command line using " -#~ "[pipx](https://pipx.pypa.io/stable/)" -#~ msgstr "" - -#~ msgid "" -#~ "Hatch can also be installed directly " -#~ "using `pip` or `conda`, but we " -#~ "encourage you to use `pipx`. This " -#~ "is because `pipx` will ensure that " -#~ "your package is available across all " -#~ "of your Python environments on your " -#~ "computer rather than just in the " -#~ "environment that you install it into." -#~ " If you install hatch this way " -#~ "you will have to take care that" -#~ " the environment it is installed into" -#~ " is activated for the command to " -#~ "work." -#~ msgstr "" - -#~ msgid "" -#~ "You can check that hatch is " -#~ "working properly by issuing a simple " -#~ "command to get the version" -#~ msgstr "" - -#~ msgid "Note the version numbers will likely be different" -#~ msgstr "" - -#~ msgid "Configure hatch" -#~ msgstr "" - -#~ msgid "" -#~ "Once you have installed Hatch, you " -#~ "will want to customize the " -#~ "configuration." -#~ msgstr "" - -#~ msgid "" -#~ "Hatch stores your configuration information" -#~ " in a [`config.toml` " -#~ "file](https://hatch.pypa.io/latest/config/project-templates/)." -#~ msgstr "" - -#~ msgid "" -#~ "While you can update the `config.toml`" -#~ " file through the command line, it" -#~ " might be easier to look at it" -#~ " and update it in a text editor" -#~ " if you are using it for the" -#~ " first time." -#~ msgstr "" - -#~ msgid "Step 1: Open and edit your `config.toml` file" -#~ msgstr "" - -#~ msgid "" -#~ "This will open up a directory " -#~ "window that will allow you to " -#~ "double click on the file and open" -#~ " it in your favorite text editor." -#~ msgstr "" - -#~ msgid "" -#~ "`hatch config show` will print out " -#~ "the contents of your `config.toml` file" -#~ " in your shell. look at the " -#~ "values and ensure that your name, " -#~ "email is set. Also make sure that" -#~ " `tests=false`." -#~ msgstr "" - -#~ msgid "" -#~ "it will convert metadata stored in " -#~ "a `setup.py` or `setup.cfg` file to " -#~ "a pyproject.toml file for you (see " -#~ "[Migrating setup.py to pyproject.toml using" -#~ " Hatch](setup-py-to-pyproject-toml.md " -#~ "))" -#~ msgstr "" - -#~ msgid "" -#~ "ADD: note about what makes something " -#~ "\"package worthy\", with a common " -#~ "misconception being that a package " -#~ "should be production-ready code that's" -#~ " valuable to a broad audience. this" -#~ " may not be a pervasive misconception" -#~ " in Python, but a quick break-" -#~ "out with an explanation of what a" -#~ " package can consist of would be " -#~ "helpful." -#~ msgstr "" - -#~ msgid "" -#~ "The directory structure you’ll create in" -#~ " this lesson will look like this:" -#~ msgstr "" - -#~ msgid "" -#~ "Where you define your project’s metadata" -#~ " (including its name, authors, license, " -#~ "etc)" -#~ msgstr "" - -#~ msgid "" -#~ "If you aren’t familiar with docstrings" -#~ " or typing yet, that is ok. You" -#~ " can review [this page in the " -#~ "pyOpenSci packaging guide](https://www.pyopensci.org" -#~ "/python-package-guide/documentation/write-user-" -#~ "documentation/document-your-code-api-" -#~ "docstrings.html) for an overview of both" -#~ " topics." -#~ msgstr "" - -#~ msgid "" -#~ "Once you have your project metadata " -#~ "in the pyproject.toml file, you will " -#~ "rarely update it. In the next " -#~ "lesson you’ll add more metadata and " -#~ "structure to this file." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "There is currently a small bug in" -#~ " Grayskull where it doesn't populate " -#~ "the home: element of the recipe. " -#~ "if you don't include this, [you " -#~ "will receive an error " -#~ "message](https://github.com/conda-forge/staged-" -#~ "recipes/pull/25173#issuecomment-1917916528) from the " -#~ "friendly conda-forge linter bot." -#~ msgstr "" - -#~ msgid "" -#~ "In a future lesson, you will learn" -#~ " how to create an automated GitHub" -#~ " action workflow that publishes an " -#~ "updated version of your package to " -#~ "PyPI every time you create a " -#~ "GitHub release." -#~ msgstr "" - -#~ msgid "" -#~ "You can also create an automated " -#~ "publication workflow on GitHub using " -#~ "GitHub actions. This is a great " -#~ "way to make the publication process " -#~ "easier and it also supports a " -#~ "growing maintainer team. In this case" -#~ " we suggest you don't worry about " -#~ "the token and instead setup a " -#~ "specific GitHub action that publishes " -#~ "your package when you make a " -#~ "release. You can then create a " -#~ "\"trusted publisher\" workflow on PyPI." -#~ msgstr "" - -#~ msgid "" -#~ "When you are adding classifiers to " -#~ "the **[project]** table, only use valid" -#~ " values from [PyPI’s classifier " -#~ "page](https://PyPI.org/classifiers/). An invalid " -#~ "value here will raise an error " -#~ "when you build and publish your " -#~ "package on PyPI." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/CONTRIBUTING.po b/locales/ja/LC_MESSAGES/CONTRIBUTING.po index e71205f1..16c831c9 100644 --- a/locales/ja/LC_MESSAGES/CONTRIBUTING.po +++ b/locales/ja/LC_MESSAGES/CONTRIBUTING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../CONTRIBUTING.md:4 msgid "Contributing to the Python Packaging Guide" @@ -119,33 +119,27 @@ msgstr "" #: ../../CONTRIBUTING.md:35 msgid "" "Independently of the approach you choose, the first step is to fork the " -"Python Packaging Guide repository into your personal GitHub space. You " -"can do this by clicking the \"Fork\" button in the top right corner of " -"the repository page." +"Python Packaging Guide repository into your personal GitHub space. To " +"\"fork\" a repository in GitHub means to create a copy of the main " +"repository, or repo, that you have complete control over and can modify " +"as you see fit." msgstr "" -#: ../../CONTRIBUTING.md:38 -msgid "" -"[Learn more: Fork and Clone GitHub " -"Repos](https://datascienceskills.org/lessons/git-github/git-intro/3-fork-" -"clone/) is a good resource to learn more about forking." -msgstr "" - -#: ../../CONTRIBUTING.md:40 +#: ../../CONTRIBUTING.md:37 msgid "To fork a repo," msgstr "" -#: ../../CONTRIBUTING.md:42 +#: ../../CONTRIBUTING.md:39 msgid "Make sure you are logged into GitHub." msgstr "" -#: ../../CONTRIBUTING.md:44 +#: ../../CONTRIBUTING.md:41 msgid "" "Go to the repo you would like to fork, in this case the [Python Packaging" " Guide](https://www.github.com/pyopensci/python-package-guide) repo." msgstr "" -#: ../../CONTRIBUTING.md:46 +#: ../../CONTRIBUTING.md:43 msgid "" "In the top right-hand corner of the page there is a 'Fork' button. Click " "that button. You will be brought to a new page where you will 'Create a " @@ -155,445 +149,173 @@ msgid "" "is your GitHub username." msgstr "" -#: ../../CONTRIBUTING.md:51 +#: ../../CONTRIBUTING.md:47 msgid "Contributing via the GitHub website" msgstr "" -#: ../../CONTRIBUTING.md:53 +#: ../../CONTRIBUTING.md:49 msgid "How to edit a MarkDown file" msgstr "" -#: ../../CONTRIBUTING.md:55 -msgid "" -"The Python Packaging Guide is written in myST, a variant of MarkDown. You" -" can edit the files directly in the GitHub website. To do so, navigate to" -" the file you want to edit and click the pencil icon in the top right " -"corner of the file." -msgstr "" - -#: ../../CONTRIBUTING.md:58 -msgid "Edit button in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:64 -msgid "" -"An image showing how to edit a file in GitHub. The pencil icon is " -"highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:66 -msgid "Edit file in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:72 -msgid "" -"An image showing when a file is being edited in GitHub. The file content " -"is displayed in a text editor." -msgstr "" - -#: ../../CONTRIBUTING.md:75 -msgid "To preview your changes, click the \"Preview changes\" tab." -msgstr "" - -#: ../../CONTRIBUTING.md:77 -msgid "Preview changes in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:83 +#: ../../CONTRIBUTING.md:51 msgid "" -"An image showing how to preview changes in GitHub. The file content is " -"displayed in a text editor. The preview changes tab is highlighted with a" -" red rectangle." +"*__TODO__: This section should show how to use the GitHub interface to " +"edit and previewing a Markdown file.*" msgstr "" -#: ../../CONTRIBUTING.md:86 +#: ../../CONTRIBUTING.md:53 msgid "How to commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:88 -msgid "" -"When you are done editing the file, scroll down to the bottom of the " -"page. You will see a section called \"Commit changes\". Here you can " -"write a title and a description for your changes. Make sure to write a " -"clear and concise title that describes the changes you made." -msgstr "" - -#: ../../CONTRIBUTING.md:91 -msgid "Commit changes in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:97 -msgid "" -"An image showing how to commit changes in GitHub. The commit message is " -"displayed in a text editor. The commit changes section is highlighted " -"with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:100 +#: ../../CONTRIBUTING.md:55 msgid "" -"After writing your commit message, click the \"Commit changes\" button to" -" save your changes." +"*__TODO__: This section should show how to commit changes via the GitHub " +"interface.*" msgstr "" -#: ../../CONTRIBUTING.md:102 +#: ../../CONTRIBUTING.md:57 msgid "Contributing locally on your computer" msgstr "" -#: ../../CONTRIBUTING.md:104 +#: ../../CONTRIBUTING.md:59 msgid "Clone your forked repository" msgstr "" -#: ../../CONTRIBUTING.md:106 -msgid "" -"To clone your forked repository to your computer, you need to copy the " -"URL of your forked repository and run the following command in your " -"terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:111 +#: ../../CONTRIBUTING.md:61 msgid "" -"Replace `` with the URL of your forked repository. You can find the " -"URL by clicking the green \"Code\" button on your forked repository page." -msgstr "" - -#: ../../CONTRIBUTING.md:113 -msgid "Clone repository in GitHub" +"*__TODO__: This section should show how to clone a repository from GitHub" +" into your computer.*" msgstr "" -#: ../../CONTRIBUTING.md:119 -msgid "" -"An image showing how to clone a repository in GitHub. The URL of the " -"repository is displayed in a text editor. The code button is highlighted " -"with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:122 +#: ../../CONTRIBUTING.md:63 msgid "Create a new branch" msgstr "" -#: ../../CONTRIBUTING.md:124 -msgid "" -"Before making any changes, you should create a new branch to work on. " -"This will help keep your changes separate from the main branch and make " -"it easier to submit a pull request." +#: ../../CONTRIBUTING.md:65 +msgid "*__TODO__: This section should show how to create a new branch.*" msgstr "" -#: ../../CONTRIBUTING.md:126 -msgid "To create a new branch, run the following command in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:132 +#: ../../CONTRIBUTING.md:67 msgid "Create a virtual environment" msgstr "" -#: ../../CONTRIBUTING.md:134 +#: ../../CONTRIBUTING.md:69 msgid "" -"To build the guide locally, you need to create a virtual environment and " -"install the dependencies. You can do this by running the following " -"commands in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:136 -msgid "**On Windows**:" -msgstr "" - -#: ../../CONTRIBUTING.md:142 -msgid "**On MacOS and Linux**:" +"*__TODO__: This section should show how to create a virtual environment " +"using venv.*" msgstr "" -#: ../../CONTRIBUTING.md:148 +#: ../../CONTRIBUTING.md:71 msgid "Install the development dependencies" msgstr "" -#: ../../CONTRIBUTING.md:150 +#: ../../CONTRIBUTING.md:73 msgid "" -"To install the development dependencies, run the following command in " -"your terminal:" +"*__TODO__: This section should show how to install the development " +"dependencies defined in pyproject.toml.*" msgstr "" -#: ../../CONTRIBUTING.md:156 +#: ../../CONTRIBUTING.md:75 msgid "Commit your changes" msgstr "" -#: ../../CONTRIBUTING.md:158 -msgid "" -"After making your changes, you need to commit them to your local " -"repository. To do this, run the following commands in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:160 -msgid "To see the changes you made:" -msgstr "" - -#: ../../CONTRIBUTING.md:164 -msgid "To add the changes to the staging area:" -msgstr "" - -#: ../../CONTRIBUTING.md:168 -msgid "To commit the changes:" -msgstr "" - -#: ../../CONTRIBUTING.md:172 +#: ../../CONTRIBUTING.md:77 msgid "" -"Replace `\"Your commit message here\"` with a clear and concise message " -"that describes the changes you made." +"*__TODO__: This section should describe how to commit from the command " +"line.*" msgstr "" -#: ../../CONTRIBUTING.md:174 +#: ../../CONTRIBUTING.md:79 msgid "How to build the guide locally" msgstr "" -#: ../../CONTRIBUTING.md:176 -msgid "" -"To build the guide locally, you can use the `nox` command. This will run " -"the default `nox` session, which builds the guide and opens it in your " -"browser." -msgstr "" - -#: ../../CONTRIBUTING.md:178 -msgid "" -"To see the different sessions available, you can run the following " -"command in your terminal:" -msgstr "" - -#: ../../CONTRIBUTING.md:183 -msgid "" -"There are different sessions in nox related to building the docs: `docs`," -" `docs-test`, `docs-live`. You can run them by specifying the session " -"name after the `nox` command." -msgstr "" - -#: ../../CONTRIBUTING.md:185 -msgid "`docs`: this session builds the guide and opens it in your browser." -msgstr "" - -#: ../../CONTRIBUTING.md:189 +#: ../../CONTRIBUTING.md:81 msgid "" -"To see the guide built locally, open the file `_build/html/index.html` in" -" your browser." +"*__TODO__: This section should describe the different sessions in nox " +"related to building the docs: docs, docs-test, docs-live. It should also " +"show how to see the guide built locally, by opening the right file in the" +" browser or using the live version from docs-live*" msgstr "" -#: ../../CONTRIBUTING.md:191 -msgid "`docs-test`: this session runs the tests for the guide." -msgstr "" - -#: ../../CONTRIBUTING.md:195 -msgid "" -"If the tests fail, you will see an error message in your terminal. You " -"need to fix the errors before submitting your pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:197 -msgid "" -"`docs-live`: this session builds the guide and opens it in your browser " -"with live reloading." -msgstr "" - -#: ../../CONTRIBUTING.md:201 -msgid "" -"open the local version of the guide in your browser at ``localhost`` " -"shown in the terminal." -msgstr "" - -#: ../../CONTRIBUTING.md:203 +#: ../../CONTRIBUTING.md:83 msgid "Before you submit your pull request" msgstr "" -#: ../../CONTRIBUTING.md:205 -msgid "" -"Before submitting your pull request, make sure to run the tests and check" -" the formatting of your code." -msgstr "" - -#: ../../CONTRIBUTING.md:210 +#: ../../CONTRIBUTING.md:85 msgid "" -"If the tests fail, you will see an error message in your terminal. You " -"need to fix the errors before submitting your pull request. Also make " -"sure to check the formatting of your documentation by building the docs " -"locally and checking that your changes look correct." +"*__TODO__: This section should describe what steps a user should follow " +"before submitting the pull request: build the docs, verify your changes " +"look correct, etc.*" msgstr "" -#: ../../CONTRIBUTING.md:214 +#: ../../CONTRIBUTING.md:87 msgid "Submitting a pull request with your contribution" msgstr "" -#: ../../CONTRIBUTING.md:216 +#: ../../CONTRIBUTING.md:89 msgid "How to make a pull request" msgstr "" -#: ../../CONTRIBUTING.md:218 -msgid "" -"To open a pull request on GitHub, navigate to the main page of your " -"forked repository and click on the \"Pull requests\" tab." -msgstr "" - -#: ../../CONTRIBUTING.md:220 -msgid "Pull requests tab in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:226 -msgid "" -"An image showing how to navigate to the pull requests tab in GitHub. The " -"pull requests tab is highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:229 -msgid "Click on the \"New pull request\" button." -msgstr "" - -#: ../../CONTRIBUTING.md:231 -msgid "New pull request button in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:237 -msgid "" -"An image showing how to create a new pull request in GitHub. The new pull" -" request button is highlighted with a red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:240 +#: ../../CONTRIBUTING.md:91 msgid "" -"Write a clear and concise title and description for your pull request. " -"Make sure to describe the changes you made and why they are necessary." +"*__TODO__: This section should describe how to make a pull request in " +"GitHub.*" msgstr "" -#: ../../CONTRIBUTING.md:242 +#: ../../CONTRIBUTING.md:93 msgid "What happens when you submit a pull request (CI/CD)" msgstr "" -#: ../../CONTRIBUTING.md:244 -msgid "" -"Once you submit a pull request, a series of checks will be run to ensure " -"that your changes do not introduce any bugs or errors. These checks " -"include:" -msgstr "" - -#: ../../CONTRIBUTING.md:246 -msgid "" -"**Code formatting and styles**: checks that your code is formatted " -"correctly, by `pre-commit.ci - pr check`." -msgstr "" - -#: ../../CONTRIBUTING.md:247 -msgid "" -"**docs build**: checks that the documentation builds correctly, using " -"`circleci`." -msgstr "" - -#: ../../CONTRIBUTING.md:249 -msgid "You will see the status of these checks in your pull request." -msgstr "" - -#: ../../CONTRIBUTING.md:251 -msgid "Pull request checks in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:257 +#: ../../CONTRIBUTING.md:95 msgid "" -"An image showing the status of the checks in a pull request in GitHub. " -"The checks are displayed in a table with a status icon next to each " -"check. The checks are highlighted with a red rectangle." +"*__TODO__: This section should describe how to see the results of the " +"CD/CI checks and how to get more information about errors*" msgstr "" -#: ../../CONTRIBUTING.md:259 -msgid "" -"If any of these checks fail, you will see an error message in your pull " -"request. You need to fix the errors before your changes can be merged." -msgstr "" - -#: ../../CONTRIBUTING.md:261 -msgid "Pull request checks failed in GitHub" -msgstr "" - -#: ../../CONTRIBUTING.md:267 -msgid "" -"An image showing the status of the checks in a pull request in GitHub. " -"The checks are displayed in a table with a status icon next to each " -"check. The checks that failed and the details link are highlighted with a" -" red rectangle." -msgstr "" - -#: ../../CONTRIBUTING.md:270 -msgid "" -"To get more information about the errors, you can click on the " -"\"Details\" link next to the failed check." -msgstr "" - -#: ../../CONTRIBUTING.md:272 +#: ../../CONTRIBUTING.md:97 msgid "What to expect from the review process" msgstr "" -#: ../../CONTRIBUTING.md:274 -msgid "" -"Once you submit a pull request, a maintainer of the repository will " -"review your changes and provide feedback. The review process may involve:" -msgstr "" - -#: ../../CONTRIBUTING.md:276 -msgid "" -"**Comments**: the reviewer may leave comments on your pull request to ask" -" questions or provide feedback." -msgstr "" - -#: ../../CONTRIBUTING.md:277 -msgid "" -"**Suggestions**: the reviewer may suggest changes to your code or " -"documentation." -msgstr "" - -#: ../../CONTRIBUTING.md:278 +#: ../../CONTRIBUTING.md:99 msgid "" -"**Approvals**: once the reviewer is satisfied with your changes, they " -"will approve the pull request." +"*__TODO__: This section should describe how review happens in GitHub, how" +" see the comments, and how to submit changes (push a new branch)*" msgstr "" -#: ../../CONTRIBUTING.md:280 -msgid "" -"You can make changes to your pull request by pushing new commits to the " -"branch. The pull request will be updated automatically with your new " -"changes." -msgstr "" - -#: ../../CONTRIBUTING.md:282 -msgid "" -"Once your pull request is approved, it will be merged into the main " -"branch and your changes will be included in the guide." -msgstr "" - -#: ../../CONTRIBUTING.md:284 +#: ../../CONTRIBUTING.md:101 msgid "Additional help" msgstr "" -#: ../../CONTRIBUTING.md:286 +#: ../../CONTRIBUTING.md:103 msgid "How to get help" msgstr "" -#: ../../CONTRIBUTING.md:288 +#: ../../CONTRIBUTING.md:105 msgid "" "*__TODO__: This section should describe the options for finding more help" " in case beginner contributors need more help (e.g., create an issue, " "post in a forum, etc).*" msgstr "" -#: ../../CONTRIBUTING.md:290 +#: ../../CONTRIBUTING.md:107 msgid "Additional resources" msgstr "" -#: ../../CONTRIBUTING.md:292 +#: ../../CONTRIBUTING.md:109 msgid "" "*__TODO__: It should also include links to beginner documentation, like " "the GitHub docs.*" msgstr "" -#: ../../CONTRIBUTING.md:294 +#: ../../CONTRIBUTING.md:111 msgid "Annex" msgstr "" -#: ../../CONTRIBUTING.md:296 +#: ../../CONTRIBUTING.md:113 msgid "Code examples" msgstr "" -#: ../../CONTRIBUTING.md:298 +#: ../../CONTRIBUTING.md:115 msgid "" "This guide uses the [literalinclude Sphinx directive](https://www.sphinx-" "doc.org/en/master/usage/restructuredtext/directives.html#directive-" @@ -601,18 +323,18 @@ msgid "" "for use in the documentation is kept in the `examples/` folder." msgstr "" -#: ../../CONTRIBUTING.md:302 +#: ../../CONTRIBUTING.md:119 msgid "Referencing code in documentation" msgstr "" -#: ../../CONTRIBUTING.md:304 +#: ../../CONTRIBUTING.md:121 msgid "" "If an example is present elsewhere in the documentation that you want to " "use, you can copy the `literalinclude` directive verbatim and the " "examples will stay in sync." msgstr "" -#: ../../CONTRIBUTING.md:307 +#: ../../CONTRIBUTING.md:124 msgid "" "If you already see code in the examples folder that you can use for new " "documentation, a new `literalinclude` can be made to extract it into the " @@ -622,7 +344,7 @@ msgid "" "the later can protect your example from future modifications to the code." msgstr "" -#: ../../CONTRIBUTING.md:312 +#: ../../CONTRIBUTING.md:129 msgid "" "**Pro tip**: As an alternative to `:lines:` there are also the `:start-" "after:`, `:start-at:`, `:end-before:`, and `:end-at:` options. And if the" @@ -630,17 +352,17 @@ msgid "" "way to keep the same documentation content even through code refactors." msgstr "" -#: ../../CONTRIBUTING.md:316 +#: ../../CONTRIBUTING.md:133 msgid "" "If you need example code that doesn't yet exist in `examples/` see " -"[creating code for documentation](#creating-code-for-documentation)." +"creating code for documentation](#creating-code-for-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:319 +#: ../../CONTRIBUTING.md:136 msgid "Creating code for documentation" msgstr "" -#: ../../CONTRIBUTING.md:321 +#: ../../CONTRIBUTING.md:138 msgid "" "Whenever you come across a place that could benefit from a code block, " "instead of writing it in-line with a code fence (`` ``` `` blocked text) " @@ -649,7 +371,7 @@ msgid "" "code-in-documentation)." msgstr "" -#: ../../CONTRIBUTING.md:325 +#: ../../CONTRIBUTING.md:142 msgid "" "If you want to add a new example that doesn't fit into any of the " "existing example files, you can create a new file and reference it in a " @@ -658,7 +380,7 @@ msgid "" "create a new folder in the `examples` directory." msgstr "" -#: ../../CONTRIBUTING.md:329 +#: ../../CONTRIBUTING.md:146 msgid "" "If an existing example is incomplete or a new example makes sense to be " "added to an existing file, go ahead and add it, but take care to not " @@ -667,14 +389,14 @@ msgid "" "file, new methods after all existing ones in a class." msgstr "" -#: ../../CONTRIBUTING.md:333 +#: ../../CONTRIBUTING.md:150 msgid "" "Example code is checked for correctness, so adding a new example may " "require adding additional tests for coverage, and will require fixing any" " failing tests." msgstr "" -#: ../../CONTRIBUTING.md:336 +#: ../../CONTRIBUTING.md:153 msgid "" "***⚠️ WARNING***: great care should be taken when modifying existing " "example code, especially any modification beyond appending to the end of " @@ -685,126 +407,29 @@ msgid "" "and then checking those pages in a new build." msgstr "" -#: ../../CONTRIBUTING.md:344 +#: ../../CONTRIBUTING.md:161 msgid "Example:" msgstr "" -#: ../../CONTRIBUTING.md:346 +#: ../../CONTRIBUTING.md:163 msgid "Instead of writing example code in markdown like this" msgstr "" -#: ../../CONTRIBUTING.md:357 +#: ../../CONTRIBUTING.md:174 msgid "The python can be extracted into a `.py` file" msgstr "" -#: ../../CONTRIBUTING.md:371 +#: ../../CONTRIBUTING.md:188 msgid "" "As another example, if you only need to show part of a `pyproject.toml`, " "we already have complete project definitions, you need only to find the " "relevant part." msgstr "" -#: ../../CONTRIBUTING.md:374 +#: ../../CONTRIBUTING.md:191 msgid "Instead of writing this" msgstr "" -#: ../../CONTRIBUTING.md:386 +#: ../../CONTRIBUTING.md:203 msgid "an example could be extracted from an existing toml file" msgstr "" - -#~ msgid "" -#~ "Independently of the approach you " -#~ "choose, the first step is to fork" -#~ " the Python Packaging Guide repository " -#~ "into your personal GitHub space. To " -#~ "\"fork\" a repository in GitHub means" -#~ " to create a copy of the main" -#~ " repository, or repo, that you have" -#~ " complete control over and can modify" -#~ " as you see fit." -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to use the GitHub interface to " -#~ "edit and previewing a Markdown file.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to commit changes via the GitHub " -#~ "interface.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to clone a repository from GitHub" -#~ " into your computer.*" -#~ msgstr "" - -#~ msgid "*__TODO__: This section should show how to create a new branch.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to create a virtual environment " -#~ "using venv.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should show how" -#~ " to install the development dependencies" -#~ " defined in pyproject.toml.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to commit from the command " -#~ "line.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "the different sessions in nox related" -#~ " to building the docs: docs, docs-" -#~ "test, docs-live. It should also " -#~ "show how to see the guide built" -#~ " locally, by opening the right file" -#~ " in the browser or using the " -#~ "live version from docs-live*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "what steps a user should follow " -#~ "before submitting the pull request: " -#~ "build the docs, verify your changes " -#~ "look correct, etc.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to make a pull request in " -#~ "GitHub.*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how to see the results of the " -#~ "CD/CI checks and how to get more" -#~ " information about errors*" -#~ msgstr "" - -#~ msgid "" -#~ "*__TODO__: This section should describe " -#~ "how review happens in GitHub, how " -#~ "see the comments, and how to " -#~ "submit changes (push a new branch)*" -#~ msgstr "" - -#~ msgid "" -#~ "If you need example code that " -#~ "doesn't yet exist in `examples/` see " -#~ "creating code for documentation](#creating-" -#~ "code-for-documentation)." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/TRANSLATING.po b/locales/ja/LC_MESSAGES/TRANSLATING.po index 5a3de41c..13765fc7 100644 --- a/locales/ja/LC_MESSAGES/TRANSLATING.po +++ b/locales/ja/LC_MESSAGES/TRANSLATING.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../TRANSLATING.md:5 msgid "Translation Guide for the Python Packaging Guide" @@ -165,9 +165,8 @@ msgstr "" #: ../../TRANSLATING.md:68 msgid "" -"You can find a list of the two-letter Sphinx language option " -"[here](https://www.sphinx-doc.org/en/master/usage/configuration.html" -"#confval-language)." +"You can find a list of the two-letter ISO language codes " +"[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." msgstr "" #: ../../TRANSLATING.md:71 @@ -427,7 +426,7 @@ msgid "" "Note the `--` before the language code, it indicates that the following " "arguments should be passed into the nox session and not be interpreted " "directly by nox. If you forget the `--`, nox will look instead for a " -"session named 'es' and raise an error that it does not exist." +"session named 'es' and complain that it does not exist." msgstr "" #: ../../TRANSLATING.md:241 @@ -497,7 +496,7 @@ msgid "" msgstr "" #: ../../TRANSLATING.md:268 -msgid "TODO: This tagging could be automated with a GitHub Actions." +msgid "TODO: This tagging could be automated with a GitHub action." msgstr "" #: ../../TRANSLATING.md:270 @@ -706,7 +705,8 @@ msgstr "" #: ../../TRANSLATING.md:343 msgid "" "If you have any questions or need help with your translation, you can " -"create an issue in the repository." +"create an issue in the repository if you encounter any problems or need " +"assistance." msgstr "" #: ../../TRANSLATING.md:345 @@ -715,31 +715,3 @@ msgid "" " as a way for contributors to ask for help with translations or the " "translation workflow?" msgstr "" - -#~ msgid "" -#~ "You can find a list of the " -#~ "two-letter ISO language codes " -#~ "[here](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)." -#~ msgstr "" - -#~ msgid "" -#~ "Note the `--` before the language " -#~ "code, it indicates that the following" -#~ " arguments should be passed into the" -#~ " nox session and not be interpreted" -#~ " directly by nox. If you forget " -#~ "the `--`, nox will look instead " -#~ "for a session named 'es' and " -#~ "complain that it does not exist." -#~ msgstr "" - -#~ msgid "TODO: This tagging could be automated with a GitHub action." -#~ msgstr "" - -#~ msgid "" -#~ "If you have any questions or need" -#~ " help with your translation, you can" -#~ " create an issue in the repository" -#~ " if you encounter any problems or " -#~ "need assistance." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/documentation.po b/locales/ja/LC_MESSAGES/documentation.po index 5afd138f..ea6bdd72 100644 --- a/locales/ja/LC_MESSAGES/documentation.po +++ b/locales/ja/LC_MESSAGES/documentation.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-26 09:16-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../documentation/hosting-tools/intro.md:1 msgid "Tools to Build and Host your Documentation" @@ -77,10 +77,10 @@ msgstr "" #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:9 msgid "" "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html) myST is " -"a combination of `markdown` and `rST` syntax. It is a nice option if you " -"are comfortable writing markdown. `myst` is preferred by many because it " -"offers both the rich functionality of rST combined with a simple-to-write" -" markdown syntax." +"a combination of vanilla of `markdown` and `rST` syntax. It is a nice " +"option if you are comfortable writing markdown. `myst` is preferred by " +"many because it offers both the rich functionality of rST combined with a" +" simple-to-write markdown syntax." msgstr "" #: ../../documentation/hosting-tools/myst-markdown-rst-doc-syntax.md:12 @@ -322,7 +322,7 @@ msgstr "" #: ../../documentation/hosting-tools/sphinx-python-package-documentation-tools.md:49 msgid "" -"While Sphinx natively supports the `rST` syntax, you can add custom " +"While Sphinx natively supports the `rST` syntax. You can add custom " "syntax parsers to support easier-to-write syntax using tools such as [the" " MyST parser](https://myst-parser.readthedocs.io/)." msgstr "" @@ -445,10 +445,10 @@ msgid "" "documentation content pages. [The OpenGraph protocol allows other " "websites to provide a useful preview of the content on your page when " "shared](https://www.freecodecamp.org/news/what-is-open-graph-and-how-" -"can-i-use-it-for-my-website/#heading-what-is-open-graph). This is " -"important for when the pages in your documentation are shared on social " -"media sites like Twitter and Mastodon and even for shares on tools like " -"Slack and Discourse." +"can-i-use-it-for-my-website/#what-is-open-graph). This is important for " +"when the pages in your documentation are shared on social media sites " +"like Twitter and Mastodon and even for shares on tools like Slack and " +"Discourse." msgstr "" #: ../../documentation/index.md:3 @@ -2224,7 +2224,7 @@ msgstr "" msgid "" "It's important to keep in mind that examples in your docstrings help " "users using your package. Running `doctest` on those examples provides a " -"check of your package's API. The doctest ensures that the functions and " +"check of your package's API. doctest ensures that the functions and " "methods in your package run as you expect them to. Neither of these items" " replace a separate, stand-alone test suite that is designed to test your" " package's core functionality across operating systems and Python " @@ -2543,56 +2543,3 @@ msgstr "" #: ../../documentation/write-user-documentation/intro.md:15 msgid "sphinx gallery for tutorials." msgstr "" - -#~ msgid "" -#~ "[myST:](https://myst-parser.readthedocs.io/en/latest/intro.html)" -#~ " myST is a combination of vanilla " -#~ "of `markdown` and `rST` syntax. It " -#~ "is a nice option if you are " -#~ "comfortable writing markdown. `myst` is " -#~ "preferred by many because it offers " -#~ "both the rich functionality of rST " -#~ "combined with a simple-to-write " -#~ "markdown syntax." -#~ msgstr "" - -#~ msgid "" -#~ "While Sphinx natively supports the `rST`" -#~ " syntax. You can add custom syntax" -#~ " parsers to support easier-to-write" -#~ " syntax using tools such as [the " -#~ "MyST parser](https://myst-parser.readthedocs.io/)." -#~ msgstr "" - -#~ msgid "" -#~ "OpenGraph is an extension that allows" -#~ " you to add metadata to your " -#~ "documentation content pages. [The OpenGraph" -#~ " protocol allows other websites to " -#~ "provide a useful preview of the " -#~ "content on your page when " -#~ "shared](https://www.freecodecamp.org/news/what-is-open-" -#~ "graph-and-how-can-i-use-it-for-" -#~ "my-website/#what-is-open-graph). This " -#~ "is important for when the pages in" -#~ " your documentation are shared on " -#~ "social media sites like Twitter and " -#~ "Mastodon and even for shares on " -#~ "tools like Slack and Discourse." -#~ msgstr "" - -#~ msgid "" -#~ "It's important to keep in mind " -#~ "that examples in your docstrings help" -#~ " users using your package. Running " -#~ "`doctest` on those examples provides a" -#~ " check of your package's API. doctest" -#~ " ensures that the functions and " -#~ "methods in your package run as you" -#~ " expect them to. Neither of these " -#~ "items replace a separate, stand-alone" -#~ " test suite that is designed to " -#~ "test your package's core functionality " -#~ "across operating systems and Python " -#~ "versions." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/index.po b/locales/ja/LC_MESSAGES/index.po index 558b22c9..83e4bdda 100644 --- a/locales/ja/LC_MESSAGES/index.po +++ b/locales/ja/LC_MESSAGES/index.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../index.md:283 msgid "Tutorials" @@ -79,14 +79,13 @@ msgid "About this guide" msgstr "このガイドについて" #: ../../index.md:29 -#, fuzzy msgid "" "Image with the pyOpenSci flower logo in the upper right hand corner. The " "image shows the packaging lifecycle. The graphic shows a high level " -"overview of the elements of a Python package. The inside circle has 5 " +"overview of the elements of a Python package. the inside circle has 5 " "items - user documentation, code/api, test suite, contributor " "documentation, project metadata / license / readme. In the middle of the " -"circle is says maintainers and has a small icon with people. On the " +"circle is says maintainers and has a small icon with people. on the " "outside circle there is an arrow and it says infrastructure." msgstr "" "右上にpyOpenSciの花のロゴがある画像。画像はパッケージングのライフサイクルを示しています。図にはPythonパッケージの要素のハイレベルな概要が示されています。内側の円には5つの項目があります" @@ -117,7 +116,8 @@ msgstr "Pythonパッケージの作成と保守のすべてを理解する" msgid "" "You will also find best practice recommendations and curated lists of " "community resources surrounding packaging and package documentation." -msgstr "また、パッケージングとパッケージドキュメンテーションにまつわるベストプラクティスの推奨や、コミュニティリソースのキュレーションリストもご覧いただけます。" +msgstr "" +"また、パッケージングとパッケージドキュメンテーションにまつわるベストプラクティスの推奨や、コミュニティリソースのキュレーションリストもご覧いただけます。" #: ../../index.md:46 msgid "Todo" @@ -163,8 +163,9 @@ msgid "" "repo here](https://github.com/pyOpenSci/python-package-guide)." msgstr "" "コミュニティが開発した、科学者のためのPythonパッケージの作り方チュートリアルシリーズの第一弾が完成しました！ " -"コミュニティのレビュープロセスに参加したり、 [Github リポジトリはこちら](https://github.com/pyOpenSci" -"/python-package-guide) で今後のチュートリアルの開発を見守ったりしてください。" +"コミュニティのレビュープロセスに参加したり、 [Github " +"リポジトリはこちら](https://github.com/pyOpenSci/python-package-guide) " +"で今後のチュートリアルの開発を見守ったりしてください。" #: ../../index.md:71 msgid "✿ Create a Package Tutorials ✿" @@ -199,8 +200,7 @@ msgid "" "[How to add metadata to a pyproject.toml file for publication to " "PyPI.](/tutorials/pyproject-toml.md)" msgstr "" -"[PyPIに公開するためにpyproject.tomlファイルにメタデータを追加する方法](/tutorials/pyproject-" -"toml.md)" +"[PyPIに公開するためにpyproject.tomlファイルにメタデータを追加する方法](/tutorials/pyproject-toml.md)" #: ../../index.md:93 msgid "✿ Packaging Tool Tutorials ✿" @@ -236,8 +236,8 @@ msgid "" "[Package metadata / pyproject.toml](package-structure-code/pyproject-" "toml-python-package-metadata.md)" msgstr "" -"[パッケージメタデータ / pyproject.toml](package-structure-code/pyproject-toml-" -"python-package-metadata.md)" +"[パッケージメタデータ / pyproject.toml](package-structure-code/pyproject-toml-python-" +"package-metadata.md)" #: ../../index.md:119 msgid "" @@ -264,8 +264,7 @@ msgid "" "[Non pure Python builds](package-structure-code/complex-python-package-" "builds.md)" msgstr "" -"[純粋な Python 以外のビルド](package-structure-code/complex-python-package-" -"builds.md)" +"[純粋な Python 以外のビルド](package-structure-code/complex-python-package-builds.md)" #: ../../index.md:127 msgid "✨ Publish your package ✨" @@ -281,15 +280,16 @@ msgstr "Pythonのパッケージングエコシステムをより深く理解す msgid "" "[Package versioning & release](/package-structure-code/python-package-" "versions.md)" -msgstr "[パッケージのバージョン管理とリリース](/package-structure-code/python-package-versions.md)" +msgstr "" +"[パッケージのバージョン管理とリリース](/package-structure-code/python-package-versions.md)" #: ../../index.md:135 msgid "" "[Publish to PyPI & Conda-forge](/package-structure-code/publish-python-" "package-pypi-conda.md)" msgstr "" -"[PyPIとConda-forgeへの公開](/package-structure-code/publish-python-package-" -"pypi-conda.md)" +"[PyPIとConda-forgeへの公開](/package-structure-code/publish-python-package-pypi-" +"conda.md)" #: ../../index.md:148 msgid "✨ Write The Docs ✨" @@ -312,8 +312,8 @@ msgid "" "[Write tutorials to show how your package is used](/documentation/write-" "user-documentation/create-package-tutorials)" msgstr "" -"[パッケージがどのように使われるかを示すチュートリアルを書く](/documentation/write-user-documentation" -"/create-package-tutorials)" +"[パッケージがどのように使われるかを示すチュートリアルを書く](/documentation/write-user-" +"documentation/create-package-tutorials)" #: ../../index.md:158 msgid "✨ Developer Docs ✨" @@ -323,7 +323,8 @@ msgstr "✨開発者向けドキュメント✨" msgid "" "[Create documentation for collaborating developers](/documentation" "/repository-files/contributing-file)" -msgstr "[共同開発者のためのドキュメントの作成](/documentation/repository-files/contributing-file)" +msgstr "" +"[共同開発者のためのドキュメントの作成](/documentation/repository-files/contributing-file)" #: ../../index.md:162 msgid "" @@ -340,8 +341,7 @@ msgid "" "[Writing a README file](/documentation/repository-files/readme-file-best-" "practices)" msgstr "" -"[READMEファイルの書き方](/documentation/repository-files/readme-file-best-" -"practices)" +"[READMEファイルの書き方](/documentation/repository-files/readme-file-best-practices)" #: ../../index.md:171 msgid "" @@ -370,8 +370,8 @@ msgid "" "[Markdown, MyST, and ReST](/documentation/hosting-tools/myst-markdown-" "rst-doc-syntax)" msgstr "" -"[Markdown、MyST、およびReST](/documentation/hosting-tools/myst-markdown-rst-" -"doc-syntax)" +"[Markdown、MyST、およびReST](/documentation/hosting-tools/myst-markdown-rst-doc-" +"syntax)" #: ../../index.md:183 msgid "" @@ -386,8 +386,8 @@ msgid "" "*We are actively working on this section. [Follow development " "here.](https://github.com/pyOpenSci/python-package-guide)*" msgstr "" -"*私たちはこのセクションに積極的に取り組んでいます。 [開発のフォローはこちら](https://github.com/pyOpenSci" -"/python-package-guide)*" +"*私たちはこのセクションに積極的に取り組んでいます。 " +"[開発のフォローはこちら](https://github.com/pyOpenSci/python-package-guide)*" #: ../../index.md:197 msgid "✨ Tests for your Python package ✨" @@ -440,20 +440,19 @@ msgid "" msgstr "このガイドへのご貢献をお待ちしております。貢献方法についてはこちらをご覧ください。" #: ../../index.md:246 -#, fuzzy msgid "" "xkcd comic showing a stick figure on the ground and one in the air. The " "one on the ground is saying. `You're flying! how?` The person in the air" " replies `Python!` Below is a 3 rectangle comic with the following text " -"in each box. Box 1 - I learned it last night. Everything is so simple. " -"Hello world is just print hello world. Box 2 - the person on the ground " -"says - come join us programming is fun again. It's a whole new world. But" +"in each box. box 1 - I learned it last night. Everything is so simple. " +"Hello world is just print hello world. box 2 - the person on the ground " +"says - come join us programming is fun again. it's a whole new world. But" " how are you flying? box 3 - the person flying says - i just typed import" " antigravity. I also sampled everything in the medicine cabinet. But i " -"think this is the python. The person on the ground is saying - that's it?" +"think this is the python. the person on the ground is saying - that's it?" msgstr "" -"xkcdの漫画で、地面に置かれた棒人間と空中にある棒人間が描かれている。地上にいる人が言っている。 `あなたは飛んでいる！どうやって？` " -"空中にいる人は `Python!` と答える。以下は3つの長方形のマンガで、各ボックスに次のテキストが入っている。ボックス1 - " +"xkcdの漫画で、地面に置かれた棒人間と空中にある棒人間が描かれている。地上にいる人が言っている。 `あなたは飛んでいる！どうやって？` 空中にいる人は" +" `Python!` と答える。以下は3つの長方形のマンガで、各ボックスに次のテキストが入っている。ボックス1 - " "昨夜学んだ。すべてがとてもシンプルだ。Hello worldはprint hello worldだけ。ボックス2 - " "地上にいる人が言う。まったく新しい世界だ。でもどうやって飛んでるの？ボックス3 - 飛んでいる人はこう言う。- " "`反重力をインポートしました。薬箱の中のものも全部試しました。でもこれがpythonだと思う。地上の人はこう言っている。- これで終わり？" diff --git a/locales/ja/LC_MESSAGES/package-structure-code.po b/locales/ja/LC_MESSAGES/package-structure-code.po index 4a574f61..f02e7e1e 100644 --- a/locales/ja/LC_MESSAGES/package-structure-code.po +++ b/locales/ja/LC_MESSAGES/package-structure-code.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../package-structure-code/code-style-linting-format.md:1 msgid "Python Package Code Style, Format and Linters" @@ -496,7 +496,7 @@ msgstr "" #: ../../package-structure-code/code-style-linting-format.md:262 msgid "" "The pre-commit workflow begins with you adding files that have changes to" -" be staged in git. Next, you'd run git commit. When you run git commit, " +" be staged in git. Next, you'd run git commit. when you run git commit, " "the pre-commit hooks will then run. In this example, Black, the code " "formatter and flake8, a linter both run. If all of the files pass Black " "and flake8 checks, then your commit will be recorded. If they don't, the " @@ -762,7 +762,7 @@ msgid "" "keep this comment - https://github.com/pyOpenSci/python-package-" "guide/pull/106#issuecomment-1844278487 in this file for now - jeremiah " "did a nice inventory of common shells and whether they need quotes or " -"not. It's really comprehensive. But do we want it in the guide?? it's " +"not. it's really comprehensive. but do we want it in the guide?? it's " "really useful for more advanced users i think." msgstr "" @@ -797,18 +797,18 @@ msgid "" msgstr "" #: ../../package-structure-code/declare-dependencies.md:29 -msgid "Needs to function properly." +msgid "needs to function properly." msgstr "" #: ../../package-structure-code/declare-dependencies.md:30 msgid "" -"Requires if someone wants to develop / work on improving your package " +"requires if someone wants to develop / work on improving your package " "locally or" msgstr "" #: ../../package-structure-code/declare-dependencies.md:31 msgid "" -"Requires if a user wants to add additional functionality (that is not " +"requires if a user wants to add additional functionality (that is not " "core) to your package" msgstr "" @@ -1130,7 +1130,7 @@ msgid "" "dependency groups listed above - docs feature and tests. In the center it" " says your-package and lists the core dependencies of that package " "seaborn and numpy. To the right are two arrows. The first shows the " -"command python - m pip install your-package. It them shows how installing" +"command python - m pip install your-package. it them shows how installing" " your package that way installs only the package and the two core " "dependencies into a users environment. Below is a second arrow with " "python -m pip install youPackage[tests]. This leads to an environment " @@ -1744,7 +1744,7 @@ msgstr "" msgid "" "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 " +"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." @@ -1754,8 +1754,8 @@ msgstr "" msgid "" "Once you have published both package distributions (the source " "distribution and the wheel) to PyPI, you can then publish to conda-forge." -" The 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 " +" 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." msgstr "" @@ -1903,10 +1903,10 @@ msgid "" "Graphic with the title Python package repositories. Below it says " "Anything hosted on PyPI can be installed using pip install. Packaging " "hosted on a conda channel can be installed using conda install. Below " -"that there are two rows. The top row says conda channels. Next to it are " +"that there are two rows. the top row says conda channels. next to it are " "three boxes one with conda-forge, community maintained; bioconda and then" " default - managed by the anaconda team. Below that there is a row that " -"says PyPI servers. PyPI - anyone can publish to PyPI. And test PyPI. A " +"says PyPI servers. PyPI - anyone can publish to PyPI. and test PyPI. a " "testbed server for you to practice." msgstr "" @@ -2233,6 +2233,7 @@ msgid "How the pyproject.toml is used when you build a package" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:104 +#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 msgid "" "When you publish to PyPI, you will notice that each package has metadata " "listed. Let’s have a look at [xclim](https://pypi.org/project/xclim/), " @@ -2452,7 +2453,7 @@ msgid "" "Here is an example of[ a package that has entry point " "script](https://github.com/pyOpenSci/update-web-" "metadata/blob/main/pyproject.toml#L60)s. Notice that there are several " -"core scripts defined in that package that perform sets of tasks. The " +"core scripts defined in that package that perform sets of tasks. " "pyOpenSci is using those scripts to process their metadata." msgstr "" @@ -2461,7 +2462,7 @@ msgid "" "**Dynamic Fields:** if you have fields that are dynamically populated. " "One example of this is if you are using scm / version control based " "version with tools like `setuptooms_scm`, then you might use the dynamic " -"field, such as version (using scm) **dynamic = [\"version\"]**" +"field. such as version (using scm) **dynamic = [\"version\"]**" msgstr "" #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:189 @@ -3912,9 +3913,9 @@ msgstr "" msgid "" "Once you have published both package distributions (the source " "distribution and the wheel) to PyPI, you can then publish to conda-forge." -" The 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." +" 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." msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:11 @@ -4029,29 +4030,14 @@ msgstr "" msgid "An example - xclim" msgstr "" -#: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:81 -msgid "" -"When you publish to PyPI, you will notice that each package has metadata " -"listed. Let's have a look at [xclim](https://pypi.org/project/xclim/), " -"one of our [pyOpenSci packages](https://www.pyopensci.org/python-" -"packages.html). Notice that on the PyPI landing page you see some " -"metadata about the package including python, maintainer information and " -"more. PyPI is able to populate this metadata because it was defined using" -" correct syntax and classifiers by Xclim's maintainers, [pyproject.toml " -"file](https://github.com/Ouranosinc/xclim/blob/master/pyproject.toml). " -"This metadata when the xclim package is built, is translated into a " -"distribution file that allows PyPI to read the metadata and print it out " -"on their website." -msgstr "" - #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:94 msgid "" "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" +"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 " +"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." msgstr "" @@ -4068,7 +4054,7 @@ msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:101 msgid "" -"This screenshot shows the metadata on PyPI for the xclim package. On it " +"This screenshot shows the metadata on PyPI for the xclim package. on it " "you can see the name of the license, the author and maintainer names " "keywords associated with the package and the base python version it " "requires which is 3.8." @@ -4080,7 +4066,7 @@ msgstr "" #: ../../package-structure-code/python-package-distribution-files-sdist-wheel.md:110 msgid "" -"Here you see the maintainer metadata as it is displayed on PyPI. For " +"Here you see the maintinaer metadata as it is displayed on PyPI. for " "xclim there are three maintainers listed with their profile pictures and " "github user names to the right." msgstr "" @@ -4784,7 +4770,7 @@ msgstr "" msgid "" "Consistent version increases following semver rules mean that values of " "your package version explain the extent of the changes made in the code " -"base from version to version. Thus your package version numbers become " +"base from version to version. thus your package version numbers become " "\"expressive\" in the same way that naming code variables well can [make " "code expressive](https://medium.com/@daniel.oliver.king/writing-" "expressive-code-b69ef7a5a2fa)." @@ -4948,7 +4934,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:107 msgid "" "Generally semantic release and version control system tools can be setup " -"to run automatically on GitHub using GitHub Actions. This means that you " +"to run automatically on GitHub using GitHub actions. This means that you " "can create a workflow where a GitHub release and associated new version " "tag is used to trigger an automated build that:" msgstr "" @@ -4969,7 +4955,7 @@ msgstr "" msgid "" "Bumping a package version refers to the step of increasing the package " "version after a set number of changes have been made to it. For example, " -"you might bump from version 0.8 to 0.9 of a package or from 0.9 to 1.0." +"you might bump from version 0.8 to 0.9 of a package. or from 0.9 to 1.0." msgstr "" #: ../../package-structure-code/python-package-versions.md:122 @@ -5079,7 +5065,7 @@ msgstr "" #: ../../package-structure-code/python-package-versions.md:173 msgid "" "When you (or your CI system) build your package, hatch checks the current" -" tag number for your package. If it has increased, it will update the " +" tag number for your package. if it has increased, it will update the " "**\\_version.py** file with the new value." msgstr "" @@ -5313,233 +5299,3 @@ msgid "" "The version number is manually updated in a configuration file such as " "`pyproject.toml` vs. in a package **\\_version.py** file." msgstr "" - -#~ msgid "" -#~ "The pre-commit workflow begins with " -#~ "you adding files that have changes " -#~ "to be staged in git. Next, you'd" -#~ " run git commit. when you run " -#~ "git commit, the pre-commit hooks " -#~ "will then run. In this example, " -#~ "Black, the code formatter and flake8," -#~ " a linter both run. If all of" -#~ " the files pass Black and flake8 " -#~ "checks, then your commit will be " -#~ "recorded. If they don't, the commit " -#~ "is canceled. You will have to fix" -#~ " any flake8 issues, and then re-" -#~ "add / stage the files to be " -#~ "committed. [_Image " -#~ "Source_](https://ljvmiranda921.github.io/notebook/2018/06/21" -#~ "/precommits-using-black-and-flake8/*)" -#~ msgstr "" - -#~ msgid "" -#~ "keep this comment - " -#~ "https://github.com/pyOpenSci/python-package-" -#~ "guide/pull/106#issuecomment-1844278487 in this file" -#~ " for now - jeremiah did a nice" -#~ " inventory of common shells and " -#~ "whether they need quotes or not. " -#~ "it's really comprehensive. but do we " -#~ "want it in the guide?? it's really" -#~ " useful for more advanced users i " -#~ "think." -#~ msgstr "" - -#~ msgid "needs to function properly." -#~ msgstr "" - -#~ msgid "" -#~ "requires if someone wants to develop " -#~ "/ work on improving your package " -#~ "locally or" -#~ msgstr "" - -#~ msgid "" -#~ "requires if a user wants to add" -#~ " additional functionality (that is not " -#~ "core) to your package" -#~ msgstr "" - -#~ msgid "" -#~ "Diagram showing a ven diagram with " -#~ "three sections representing the dependency " -#~ "groups listed above - docs feature " -#~ "and tests. In the center it says" -#~ " your-package and lists the core " -#~ "dependencies of that package seaborn and" -#~ " numpy. To the right are two " -#~ "arrows. The first shows the command " -#~ "python - m pip install your-" -#~ "package. it them shows how installing" -#~ " your package that way installs only" -#~ " the package and the two core " -#~ "dependencies into a users environment. " -#~ "Below is a second arrow with " -#~ "python -m pip install youPackage[tests]. " -#~ "This leads to an environment with " -#~ "both the package dependencies - your-" -#~ "package, seaborn and numpy and also " -#~ "the tests dependencies including pytest " -#~ "and pytest-cov" -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "Graphic with the title Python package" -#~ " repositories. Below it says Anything " -#~ "hosted on PyPI can be installed " -#~ "using pip install. Packaging hosted on" -#~ " a conda channel can be installed " -#~ "using conda install. Below that there" -#~ " are two rows. the top row says" -#~ " conda channels. next to it are " -#~ "three boxes one with conda-forge, " -#~ "community maintained; bioconda and then " -#~ "default - managed by the anaconda " -#~ "team. Below that there is a row" -#~ " that says PyPI servers. PyPI - " -#~ "anyone can publish to PyPI. and " -#~ "test PyPI. a testbed server for " -#~ "you to practice." -#~ msgstr "" - -#~ msgid "" -#~ "Here is an example of[ a package" -#~ " that has entry point " -#~ "script](https://github.com/pyOpenSci/update-web-" -#~ "metadata/blob/main/pyproject.toml#L60)s. Notice that " -#~ "there are several core scripts defined" -#~ " in that package that perform sets" -#~ " of tasks. pyOpenSci is using those" -#~ " scripts to process their metadata." -#~ msgstr "" - -#~ msgid "" -#~ "**Dynamic Fields:** if you have fields" -#~ " that are dynamically populated. One " -#~ "example of this is if you are " -#~ "using scm / version control based " -#~ "version with tools like `setuptooms_scm`, " -#~ "then you might use the dynamic " -#~ "field. such as version (using scm) " -#~ "**dynamic = [\"version\"]**" -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "This screenshot shows the metadata on" -#~ " PyPI for the xclim package. on " -#~ "it you can see the name of " -#~ "the license, the author and maintainer" -#~ " names keywords associated with the " -#~ "package and the base python version " -#~ "it requires which is 3.8." -#~ msgstr "" - -#~ msgid "" -#~ "Here you see the maintinaer metadata " -#~ "as it is displayed on PyPI. for" -#~ " xclim there are three maintainers " -#~ "listed with their profile pictures and" -#~ " github user names to the right." -#~ msgstr "" - -#~ msgid "" -#~ "Consistent version increases following semver" -#~ " rules mean that values of your " -#~ "package version explain the extent of" -#~ " the changes made in the code " -#~ "base from version to version. thus " -#~ "your package version numbers become " -#~ "\"expressive\" in the same way that " -#~ "naming code variables well can [make " -#~ "code expressive](https://medium.com/@daniel.oliver.king" -#~ "/writing-expressive-code-b69ef7a5a2fa)." -#~ msgstr "" - -#~ msgid "" -#~ "Generally semantic release and version " -#~ "control system tools can be setup " -#~ "to run automatically on GitHub using " -#~ "GitHub actions. This means that you " -#~ "can create a workflow where a " -#~ "GitHub release and associated new " -#~ "version tag is used to trigger an" -#~ " automated build that:" -#~ msgstr "" - -#~ msgid "" -#~ "Bumping a package version refers to " -#~ "the step of increasing the package " -#~ "version after a set number of " -#~ "changes have been made to it. For" -#~ " example, you might bump from version" -#~ " 0.8 to 0.9 of a package. or" -#~ " from 0.9 to 1.0." -#~ msgstr "" - -#~ msgid "" -#~ "When you (or your CI system) build" -#~ " your package, hatch checks the " -#~ "current tag number for your package. " -#~ "if it has increased, it will " -#~ "update the **\\_version.py** file with " -#~ "the new value." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/tests.po b/locales/ja/LC_MESSAGES/tests.po index bf826243..1b5994c6 100644 --- a/locales/ja/LC_MESSAGES/tests.po +++ b/locales/ja/LC_MESSAGES/tests.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../tests/index.md:72 msgid "Intro" @@ -102,7 +102,7 @@ msgstr "" #: ../../tests/index.md:58 msgid "" -"Continuous integration platforms such as GitHub Actions can be useful for" +"Continuous integration platforms such as GitHub actions can be useful for" " running your tests across both different Python versions and different " "operating systems. Learn about setting up tests to run in Continuous " "Integration here." @@ -383,6 +383,9 @@ msgid "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** is an " "automation tool that supports common steps such as building " "documentation, running tests across various versions of Python, and more." +" You can find [a nice overview of tox in the plasmaPy " +"documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" +"#using-tox)." msgstr "" #: ../../tests/run-tests.md:127 @@ -802,12 +805,12 @@ msgid "" msgstr "" #: ../../tests/tests-ci.md:22 -msgid "Example GitHub Actions that runs tests" +msgid "Example GitHub action that runs tests" msgstr "" #: ../../tests/tests-ci.md:24 msgid "" -"Below is an example GitHub Actions that runs tests using nox across both " +"Below is an example GitHub action that runs tests using nox across both " "Windows, Mac and Linux and on Python versions 3.9-3.11." msgstr "" @@ -893,7 +896,7 @@ msgstr "" #: ../../tests/write-tests.md:21 msgid "" "**Easier pull request reviews:** By running your tests in a CI framework " -"such as GitHub Actions, each time you or a contributor makes a change to " +"such as GitHub actions, each time you or a contributor makes a change to " "your code-base, you can catch issues and things that may have changed in " "your code base. This ensures that your software behaves the way you " "expect it to." @@ -997,48 +1000,3 @@ msgid "" "the user can easily understand why if failed (provides a useful error " "message)." msgstr "" - -#~ msgid "" -#~ "Continuous integration platforms such as " -#~ "GitHub actions can be useful for " -#~ "running your tests across both different" -#~ " Python versions and different operating" -#~ " systems. Learn about setting up " -#~ "tests to run in Continuous Integration" -#~ " here." -#~ msgstr "" - -#~ msgid "" -#~ "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)**" -#~ " is an automation tool that supports" -#~ " common steps such as building " -#~ "documentation, running tests across various" -#~ " versions of Python, and more. You" -#~ " can find [a nice overview of " -#~ "tox in the plasmaPy " -#~ "documentation](https://docs.plasmapy.org/en/stable/contributing/testing_guide.html" -#~ "#using-tox)." -#~ msgstr "" - -#~ msgid "Example GitHub action that runs tests" -#~ msgstr "" - -#~ msgid "" -#~ "Below is an example GitHub action " -#~ "that runs tests using nox across " -#~ "both Windows, Mac and Linux and on" -#~ " Python versions 3.9-3.11." -#~ msgstr "" - -#~ msgid "" -#~ "**Easier pull request reviews:** By " -#~ "running your tests in a CI " -#~ "framework such as GitHub actions, each" -#~ " time you or a contributor makes " -#~ "a change to your code-base, you" -#~ " can catch issues and things that " -#~ "may have changed in your code " -#~ "base. This ensures that your software" -#~ " behaves the way you expect it " -#~ "to." -#~ msgstr "" diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index 6dd97827..7eb0df48 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-08-23 21:12-0700\n" +"POT-Creation-Date: 2024-08-02 18:04+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -18,7 +18,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.16.0\n" +"Generated-By: Babel 2.15.0\n" #: ../../tutorials/add-license-coc.md:1 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" @@ -79,12 +79,12 @@ msgstr "" #: ../../tutorials/add-license-coc.md:23 msgid "" -"Create a `LICENSE` file in your project directory that specifies the " -"license that you choose for your package." +"create a `LICENSE` file in your project directory that specifies the " +"license that you choose for your package and" msgstr "" #: ../../tutorials/add-license-coc.md:24 -msgid "Reference that file in your `pyproject.toml` data where metadata are set." +msgid "reference that file in your `pyproject.toml` data where metadata are set." msgstr "" #: ../../tutorials/add-license-coc.md:26 @@ -1194,7 +1194,7 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:202 msgid "" "`hatch config show` will print out the contents of your `config.toml` " -"file in your shell. Look at the values and ensure that your name, email " +"file in your shell. look at the values and ensure that your name, email " "is set. Also make sure that `tests=false`." msgstr "" @@ -1229,7 +1229,7 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:220 msgid "" -"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " +"it will convert metadata stored in a `setup.py` or `setup.cfg` file to a " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" @@ -1298,7 +1298,7 @@ msgstr "" msgid "" "ADD: note about what makes something \"package worthy\", with a common " "misconception being that a package should be production-ready code that's" -" valuable to a broad audience. This may not be a pervasive misconception " +" valuable to a broad audience. this may not be a pervasive misconception " "in Python, but a quick break-out with an explanation of what a package " "can consist of would be helpful." msgstr "" @@ -1435,7 +1435,7 @@ msgid "An `__init__.py` file in your code directory." msgstr "" #: ../../tutorials/installable-code.md:83 -msgid "The directory structure you'll create in this lesson will look like this:" +msgid "The directory structure you’ll create in this lesson will look like this:" msgstr "" #: ../../tutorials/installable-code.md:95 @@ -1509,7 +1509,7 @@ msgstr "" #: ../../tutorials/installable-code.md:121 msgid "" -"Where you define your project's metadata (including its name, authors, " +"Where you define your project’s metadata (including its name, authors, " "license, etc)" msgstr "" @@ -1734,7 +1734,7 @@ msgstr "" #: ../../tutorials/installable-code.md:282 msgid "" -"If you aren't familiar with docstrings or typing yet, that is ok. You can" +"If you aren’t familiar with docstrings or typing yet, that is ok. You can" " review [this page in the pyOpenSci packaging " "guide](https://www.pyopensci.org/python-package-guide/documentation" "/write-user-documentation/document-your-code-api-docstrings.html) for an " @@ -1901,7 +1901,7 @@ msgstr "" #: ../../tutorials/installable-code.md:482 msgid "" "Once you have your project metadata in the pyproject.toml file, you will " -"rarely update it. In the next lesson you'll add more metadata and " +"rarely update it. In the next lesson you’ll add more metadata and " "structure to this file." msgstr "" @@ -2866,8 +2866,8 @@ msgid "" "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 " +"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." @@ -3038,7 +3038,7 @@ msgstr "" msgid "" "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 " +"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." @@ -3386,7 +3386,7 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:279 msgid "" "There is currently a small bug in Grayskull where it doesn't populate the" -" home: element of the recipe. If you don't include this, [you will " +" home: element of the recipe. if you don't include this, [you will " "receive an error message](https://github.com/conda-forge/staged-" "recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" " linter bot." @@ -3934,8 +3934,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:60 msgid "" "In a future lesson, you will learn how to create an automated GitHub " -"Actions workflow that publishes an updated version of your package to " -"PyPI every time you create a GitHub release." +"action workflow that publishes an updated version of your package to PyPI" +" every time you create a GitHub release." msgstr "" #: ../../tutorials/publish-pypi.md:64 @@ -4472,10 +4472,10 @@ msgstr "" #: ../../tutorials/publish-pypi.md:363 msgid "" "You can also create an automated publication workflow on GitHub using " -"GitHub Actions. This is a great way to make the publication process " +"GitHub actions. This is a great way to make the publication process " "easier and it also supports a growing maintainer team. In this case we " "suggest you don't worry about the token and instead setup a specific " -"GitHub Actions that publishes your package when you make a release. You " +"GitHub action that publishes your package when you make a release. You " "can then create a \"trusted publisher\" workflow on PyPI." msgstr "" @@ -4665,7 +4665,7 @@ msgstr "" #: ../../tutorials/pyproject-toml.md:43 msgid "" "When you are adding classifiers to the **[project]** table, only use " -"valid values from [PyPI's classifier " +"valid values from [PyPI’s classifier " "page](https://PyPI.org/classifiers/). An invalid value here will raise an" " error when you build and publish your package on PyPI." msgstr "" @@ -5534,155 +5534,3 @@ msgid "" "existing functionality remains intact. Run any pre-existing tests to " "verify that everything still works as expected." msgstr "" - -#~ msgid "" -#~ "create a `LICENSE` file in your " -#~ "project directory that specifies the " -#~ "license that you choose for your " -#~ "package and" -#~ msgstr "" - -#~ msgid "" -#~ "reference that file in your " -#~ "`pyproject.toml` data where metadata are " -#~ "set." -#~ msgstr "" - -#~ msgid "" -#~ "`hatch config show` will print out " -#~ "the contents of your `config.toml` file" -#~ " in your shell. look at the " -#~ "values and ensure that your name, " -#~ "email is set. Also make sure that" -#~ " `tests=false`." -#~ msgstr "" - -#~ msgid "" -#~ "it will convert metadata stored in " -#~ "a `setup.py` or `setup.cfg` file to " -#~ "a pyproject.toml file for you (see " -#~ "[Migrating setup.py to pyproject.toml using" -#~ " Hatch](setup-py-to-pyproject-toml.md " -#~ "))" -#~ msgstr "" - -#~ msgid "" -#~ "ADD: note about what makes something " -#~ "\"package worthy\", with a common " -#~ "misconception being that a package " -#~ "should be production-ready code that's" -#~ " valuable to a broad audience. this" -#~ " may not be a pervasive misconception" -#~ " in Python, but a quick break-" -#~ "out with an explanation of what a" -#~ " package can consist of would be " -#~ "helpful." -#~ msgstr "" - -#~ msgid "" -#~ "The directory structure you’ll create in" -#~ " this lesson will look like this:" -#~ msgstr "" - -#~ msgid "" -#~ "Where you define your project’s metadata" -#~ " (including its name, authors, license, " -#~ "etc)" -#~ msgstr "" - -#~ msgid "" -#~ "If you aren’t familiar with docstrings" -#~ " or typing yet, that is ok. You" -#~ " can review [this page in the " -#~ "pyOpenSci packaging guide](https://www.pyopensci.org" -#~ "/python-package-guide/documentation/write-user-" -#~ "documentation/document-your-code-api-" -#~ "docstrings.html) for an overview of both" -#~ " topics." -#~ msgstr "" - -#~ msgid "" -#~ "Once you have your project metadata " -#~ "in the pyproject.toml file, you will " -#~ "rarely update it. In the next " -#~ "lesson you’ll add more metadata and " -#~ "structure to this file." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "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." -#~ msgstr "" - -#~ msgid "" -#~ "There is currently a small bug in" -#~ " Grayskull where it doesn't populate " -#~ "the home: element of the recipe. " -#~ "if you don't include this, [you " -#~ "will receive an error " -#~ "message](https://github.com/conda-forge/staged-" -#~ "recipes/pull/25173#issuecomment-1917916528) from the " -#~ "friendly conda-forge linter bot." -#~ msgstr "" - -#~ msgid "" -#~ "In a future lesson, you will learn" -#~ " how to create an automated GitHub" -#~ " action workflow that publishes an " -#~ "updated version of your package to " -#~ "PyPI every time you create a " -#~ "GitHub release." -#~ msgstr "" - -#~ msgid "" -#~ "You can also create an automated " -#~ "publication workflow on GitHub using " -#~ "GitHub actions. This is a great " -#~ "way to make the publication process " -#~ "easier and it also supports a " -#~ "growing maintainer team. In this case" -#~ " we suggest you don't worry about " -#~ "the token and instead setup a " -#~ "specific GitHub action that publishes " -#~ "your package when you make a " -#~ "release. You can then create a " -#~ "\"trusted publisher\" workflow on PyPI." -#~ msgstr "" - -#~ msgid "" -#~ "When you are adding classifiers to " -#~ "the **[project]** table, only use valid" -#~ " values from [PyPI’s classifier " -#~ "page](https://PyPI.org/classifiers/). An invalid " -#~ "value here will raise an error " -#~ "when you build and publish your " -#~ "package on PyPI." -#~ msgstr ""