From 6f04b24a0debdfe85cd4c8d0a3e9d112eb13121d Mon Sep 17 00:00:00 2001 From: Felipe Moreno Date: Fri, 22 May 2026 12:21:33 -0700 Subject: [PATCH 1/3] update Japanese translation --- locales/ja/LC_MESSAGES/TRANSLATING.po | 8 +- locales/ja/LC_MESSAGES/documentation.po | 614 +++- locales/ja/LC_MESSAGES/index.po | 229 +- .../ja/LC_MESSAGES/package-structure-code.po | 388 ++- locales/ja/LC_MESSAGES/tests.po | 1806 +++++++---- locales/ja/LC_MESSAGES/tutorials.po | 2775 ++++++++++------- 6 files changed, 3895 insertions(+), 1925 deletions(-) diff --git a/locales/ja/LC_MESSAGES/TRANSLATING.po b/locales/ja/LC_MESSAGES/TRANSLATING.po index 89094d41..4fb15466 100644 --- a/locales/ja/LC_MESSAGES/TRANSLATING.po +++ b/locales/ja/LC_MESSAGES/TRANSLATING.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-07-12 11:17+0200\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -20,7 +20,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" #: ../../TRANSLATING.md:5 msgid "Translation Guide for the Python Packaging Guide" @@ -162,9 +162,10 @@ msgstr "" "/python-package-guide/issues) ことから始めてください。" #: ../../TRANSLATING.md:60 +#, fuzzy msgid "" "To generate the translation files for a new language, add the language to" -" the `LANGUAGES` list in the `noxfile.py` configuration file. " +" the `LANGUAGES` list in the `conf.py` configuration file. " "[Nox](https://nox.thea.codes/en/stable/index.html) is the tool we use to " "manage the building of the guide and its translations." msgstr "" @@ -844,3 +845,4 @@ msgstr "" "、私たちのワークフロー、プロセス、ツールに関する一般的な質問用のチャンネル (translation-general) " "と、私たちが取り組んでいる各言語のチャンネル (spanish-translation、japanese-translationなど) " "があります。" + diff --git a/locales/ja/LC_MESSAGES/documentation.po b/locales/ja/LC_MESSAGES/documentation.po index 45ea2588..a55a1c52 100644 --- a/locales/ja/LC_MESSAGES/documentation.po +++ b/locales/ja/LC_MESSAGES/documentation.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -20,7 +20,535 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" + +#: ../../documentation/glossary.md:7 +msgid "Python packaging glossary" +msgstr "" + +#: ../../documentation/glossary.md:9 +#, fuzzy +msgid "Core packaging" +msgstr "あなたのパッケージ" + +#: ../../documentation/glossary.md +msgid "`__init__.py`" +msgstr "" + +#: ../../documentation/glossary.md:13 +msgid "" +"A special Python file that marks a directory as a Python package. When " +"Python sees this file, it knows the folder contains importable code. It " +"can either be empty or contain code that runs when the package is " +"imported." +msgstr "" + +#: ../../documentation/glossary.md:6 +msgid "API token" +msgstr "" + +#: ../../documentation/glossary.md:19 +msgid "" +"A secret key used to authenticate with PyPI or TestPyPI when publishing a" +" package. You generate one in your account settings and use it in place " +"of a password. **Treat it like a password and never share it or commit it" +" to version control**." +msgstr "" + +#: ../../documentation/glossary.md:12 +msgid "Build backend" +msgstr "" + +#: ../../documentation/glossary.md:25 +msgid "" +"The tool that does the actual work of building your package into " +"distribution files. In this guide, the build backend is Hatchling. You " +"specify it in your `pyproject.toml` file under `[build-system]`." +msgstr "" + +#: ../../documentation/glossary.md:29 +msgid "" +"You execute a build by running `hatch build`. Alternatively, you can run" +" `python -m build`. [Reference: official Python Packaging " +"documentation](https://packaging.python.org/en/latest/tutorials" +"/packaging-projects/#choosing-a-build-backend)" +msgstr "" + +#: ../../documentation/glossary.md:20 +#, fuzzy +msgid "Distribution files" +msgstr "貢献ファイル" + +#: ../../documentation/glossary.md:33 +msgid "" +"The files you upload to PyPI so others can install your package. There " +"are two common types: a wheel (`.whl`) and a source distribution " +"(`.tar.gz`). See also `Wheel (.whl)` and `Source distribution (sdist)`." +msgstr "" + +#: ../../documentation/glossary.md:26 +msgid "Module" +msgstr "" + +#: ../../documentation/glossary.md:39 +msgid "" +"A single Python file (`.py`) containing code such as functions, classes, " +"or variables that can be imported. A package is made up of one or more " +"modules." +msgstr "" + +#: ../../documentation/glossary.md:31 +msgid "`pyproject.toml`" +msgstr "" + +#: ../../documentation/glossary.md:44 +msgid "" +"The configuration file at the root of your Python package. Written in " +"TOML format, it stores metadata such as name, version, authors, and " +"license. It can also configure tools such as Hatch, uv, and pytest. See " +"also [Make your Python package PyPI ready](../tutorials/pyproject-toml)." +msgstr "" + +#: ../../documentation/glossary.md:37 +#, fuzzy +msgid "Python package" +msgstr "あなたのパッケージ" + +#: ../../documentation/glossary.md:50 +msgid "" +"A directory of Python code structured so it can be installed, imported, " +"and shared with others. A package includes at least an `__init__.py` file" +" and a `pyproject.toml` file. This is sometimes referred to as a " +"**regular package**." +msgstr "" + +#: ../../documentation/glossary.md:55 +msgid "" +"Info: You may hear the term **namespaced package** which is not really a " +"package at all but a container of subpackages. This is out of scope for " +"this guide. If interested, consult the [Python " +"documentation](https://docs.python.org/3/glossary.html#term-namespace-" +"package)." +msgstr "" + +#: ../../documentation/glossary.md:47 +msgid "PyPI / TestPyPI" +msgstr "" + +#: ../../documentation/glossary.md:60 +msgid "" +"PyPI (the Python Package Index) is the official repository where Python " +"packages are published and installed from. TestPyPI is a separate " +"practice environment used for learning and testing publishing workflows. " +"See [pypi.org](https://pypi.org) and " +"[test.pypi.org](https://test.pypi.org). See also [Publish your Python " +"package to PyPI](../tutorials/publish-pypi)." +msgstr "" + +#: ../../documentation/glossary.md:55 +msgid "Source distribution (sdist)" +msgstr "" + +#: ../../documentation/glossary.md:68 +msgid "" +"One of the two distribution file types for a Python package. The sdist " +"(`.tar.gz`) contains source code and project files. When someone installs" +" from an sdist, tools build the package locally first. See also [Publish " +"your Python package to PyPI](../tutorials/publish-pypi)." +msgstr "" + +#: ../../documentation/glossary.md:61 +msgid "TOML" +msgstr "" + +#: ../../documentation/glossary.md:74 +msgid "" +"Tom's Obvious Minimal Language, a simple format for configuration files. " +"TOML organizes data into tables such as `[project]` or `[tool.hatch]` and" +" arrays. `pyproject.toml` uses TOML." +msgstr "" + +#: ../../documentation/glossary.md:66 +msgid "Trusted publishing" +msgstr "" + +#: ../../documentation/glossary.md:79 +msgid "" +"A secure way to publish to PyPI using GitHub Actions instead of an API " +"token. Rather than storing a secret token, you configure PyPI to trust " +"your repository directly. See also [Setup Trusted Publishing for secure " +"and automated publishing via GitHub Actions](../tutorials/trusted-" +"publishing)." +msgstr "" + +#: ../../documentation/glossary.md:72 +msgid "Wheel (.whl)" +msgstr "" + +#: ../../documentation/glossary.md:85 +msgid "" +"The binary distribution type for a Python package. A wheel is a pre-built" +" binary format (`.whl`, a ZIP file) that installs directly without a " +"build step. For many pure Python packages, one wheel can work across " +"platforms. See also [Publish your Python package to PyPI](../tutorials" +"/publish-pypi)." +msgstr "" + +#: ../../documentation/glossary.md:92 +#, fuzzy +msgid "Tools" +msgstr "Todo" + +#: ../../documentation/glossary.md +#, fuzzy +msgid "copier" +msgstr "互換性" + +#: ../../documentation/glossary.md:96 +msgid "" +"A command-line tool for creating new projects from templates. In this " +"guide, you can use copier with the pyOpenSci package template to set up " +"structure, configuration, and tooling quickly. See " +"[copier.readthedocs.io](https://copier.readthedocs.io)." +msgstr "" + +#: ../../documentation/glossary.md:6 +msgid "coverage.py" +msgstr "" + +#: ../../documentation/glossary.md:102 +msgid "" +"A tool that measures how much of your code is exercised by tests, often " +"as a percentage. It shows which lines and branches are covered. See " +"[coverage.readthedocs.io](https://coverage.readthedocs.io)." +msgstr "" + +#: ../../documentation/glossary.md:11 +msgid "Hatch" +msgstr "" + +#: ../../documentation/glossary.md:107 +msgid "" +"A modern Python packaging and project management tool. In this guide, " +"Hatch is used to build packages, manage environments, run scripts, and " +"publish. Configuration lives in `pyproject.toml`. See " +"[hatch.pypa.io](https://hatch.pypa.io). See also [Get to know " +"Hatch](../tutorials/get-to-know-hatch)." +msgstr "" + +#: ../../documentation/glossary.md:18 +msgid "Hatchling" +msgstr "" + +#: ../../documentation/glossary.md:114 +msgid "" +"The build backend used by Hatch. When you run `python -m build` or `hatch" +" build`, Hatchling reads `pyproject.toml` and creates sdist and wheel " +"files. See " +"[hatch.pypa.io/latest/backend](https://hatch.pypa.io/latest/backend/)." +msgstr "" + +#: ../../documentation/glossary.md:24 +msgid "pip" +msgstr "" + +#: ../../documentation/glossary.md:120 +msgid "" +"Python's default package installer. You can use it to install packages " +"from PyPI into an environment with commands such as `pip install package-" +"name`. See [pip.pypa.io](https://pip.pypa.io)." +msgstr "" + +#: ../../documentation/glossary.md:29 +msgid "pytest" +msgstr "" + +#: ../../documentation/glossary.md:125 +msgid "" +"A widely used Python testing framework for discovering and running tests." +" In this guide, pytest often runs through Hatch scripts. See " +"[docs.pytest.org](https://docs.pytest.org)." +msgstr "" + +#: ../../documentation/glossary.md:34 +msgid "Ruff" +msgstr "" + +#: ../../documentation/glossary.md:130 +msgid "" +"A fast Python linter and formatter. It checks style and can automatically" +" fix many styling issues. See " +"[docs.astral.sh/ruff](https://docs.astral.sh/ruff)." +msgstr "" + +#: ../../documentation/glossary.md:39 +msgid "Sphinx" +msgstr "" + +#: ../../documentation/glossary.md:135 +msgid "" +"A documentation generator for Python projects. Sphinx reads docstrings " +"and documentation files to build a docs site. See [sphinx-" +"doc.org](https://www.sphinx-doc.org)." +msgstr "" + +#: ../../documentation/glossary.md:44 +msgid "Twine" +msgstr "" + +#: ../../documentation/glossary.md:140 +msgid "" +"A tool for securely uploading distribution files to PyPI or TestPyPI. See" +" [twine.readthedocs.io](https://twine.readthedocs.io)." +msgstr "" + +#: ../../documentation/glossary.md:48 +msgid "uv" +msgstr "" + +#: ../../documentation/glossary.md:144 +msgid "" +"A fast Python package and environment manager. In this guide, you can use" +" uv to manage dependencies and run commands in project environments. See " +"[docs.astral.sh/uv](https://docs.astral.sh/uv)." +msgstr "" + +#: ../../documentation/glossary.md:149 +msgid "Hatch-specific concepts" +msgstr "" + +#: ../../documentation/glossary.md +msgid "Hatch environment" +msgstr "" + +#: ../../documentation/glossary.md:153 +msgid "" +"An isolated Python environment managed by Hatch. You can define multiple " +"environments in `pyproject.toml` for testing, docs, builds, and style " +"checks, each with its own dependencies and scripts." +msgstr "" + +#: ../../documentation/glossary.md:5 +msgid "Script (Hatch)" +msgstr "" + +#: ../../documentation/glossary.md:158 +msgid "" +"A named command defined inside a Hatch environment in `pyproject.toml`. " +"Scripts provide shortcuts such as `hatch run build:check` and `hatch run " +"test:run`." +msgstr "" + +#: ../../documentation/glossary.md:10 +msgid "Task runner" +msgstr "" + +#: ../../documentation/glossary.md:163 +msgid "" +"A tool that automates repetitive development workflows. Hatch can " +"function as a task runner by letting you define scripts that run in " +"specific environments." +msgstr "" + +#: ../../documentation/glossary.md:168 +#, fuzzy +msgid "Development concepts" +msgstr "開発ガイド" + +#: ../../documentation/glossary.md +msgid "Code coverage" +msgstr "" + +#: ../../documentation/glossary.md:172 +msgid "" +"A measure of how much source code executes during tests, usually as a " +"percentage. High coverage does not guarantee no bugs, but low coverage " +"can indicate untested areas." +msgstr "" + +#: ../../documentation/glossary.md:5 +#, fuzzy +msgid "Dependencies" +msgstr "参考文献" + +#: ../../documentation/glossary.md:177 +msgid "" +"Other Python packages needed for your package to work. Common classes " +"include required dependencies, optional dependencies, and development " +"dependencies." +msgstr "" + +#: ../../documentation/glossary.md:10 +#, fuzzy +msgid "Docstring" +msgstr "ドキュメントビルディング" + +#: ../../documentation/glossary.md:182 +msgid "" +"A string at the top of a function, class, or module that describes " +"behavior, inputs, and outputs. Docstrings can be used by tools such as " +"Sphinx to generate API documentation." +msgstr "" + +#: ../../documentation/glossary.md:15 +msgid "End-to-end test" +msgstr "" + +#: ../../documentation/glossary.md:187 +msgid "" +"A test that simulates a complete user workflow from start to finish. In " +"scientific packages, tutorials executed during docs builds can serve as " +"end-to-end tests." +msgstr "" + +#: ../../documentation/glossary.md:20 +msgid "Integration test" +msgstr "" + +#: ../../documentation/glossary.md:192 +msgid "" +"A test that checks how multiple functions or components work together. " +"Unlike a unit test, it verifies behavior across a broader workflow." +msgstr "" + +#: ../../documentation/glossary.md:24 +msgid "Linting" +msgstr "" + +#: ../../documentation/glossary.md:196 +msgid "" +"Automatic checks for style issues, formatting problems, and potential " +"errors in code." +msgstr "" + +#: ../../documentation/glossary.md:28 +msgid "Unit test" +msgstr "" + +#: ../../documentation/glossary.md:200 +msgid "" +"A test that checks one function or method in isolation. Unit tests are " +"fast and help pinpoint where failures occur." +msgstr "" + +#: ../../documentation/glossary.md:32 +msgid "Version specifier / lower bound" +msgstr "" + +#: ../../documentation/glossary.md:204 +msgid "" +"A constraint on which dependency versions are accepted. For example, " +"`numpy>=1.24` sets a lower bound so versions older than 1.24 are not " +"used." +msgstr "" + +#: ../../documentation/glossary.md:209 +msgid "Git / GitHub" +msgstr "" + +#: ../../documentation/glossary.md +msgid "git" +msgstr "" + +#: ../../documentation/glossary.md:213 +msgid "A tool for version control." +msgstr "" + +#: ../../documentation/glossary.md:3 +msgid "GitHub" +msgstr "" + +#: ../../documentation/glossary.md:216 +msgid "" +"A service providing accounts and organizations to facilitate sharing " +"repositories." +msgstr "" + +#: ../../documentation/glossary.md:6 +msgid "GitHub Codespace" +msgstr "" + +#: ../../documentation/glossary.md:219 +msgid "" +"A cloud-based development environment that runs in a browser. See " +"[github.com/features/codespaces](https://github.com/features/codespaces)." +msgstr "" + +#: ../../documentation/glossary.md:10 +msgid "Scoped commit" +msgstr "" + +#: ../../documentation/glossary.md:223 +msgid "" +"A git commit that makes one focused change, such as one fix or one " +"feature update. Scoped commits improve reviewability and history clarity." +msgstr "" + +#: ../../documentation/glossary.md:228 +#, fuzzy +msgid "Documentation" +msgstr "ドキュメントの概要" + +#: ../../documentation/glossary.md +#, fuzzy +msgid "Code of conduct" +msgstr "あなたの行動規範" + +#: ../../documentation/glossary.md:232 +msgid "" +"A document that sets expectations for how contributors and community " +"members treat one another in a project." +msgstr "" + +#: ../../documentation/glossary.md:4 +#, fuzzy +msgid "Contributing guide" +msgstr "貢献ファイル" + +#: ../../documentation/glossary.md:236 +msgid "" +"A document, often `CONTRIBUTING.md`, that explains how others can " +"contribute, including setup steps, workflow, and code style." +msgstr "" + +#: ../../documentation/glossary.md:8 +#, fuzzy +msgid "MyST Markdown" +msgstr "myST vs Markdown vs rst" + +#: ../../documentation/glossary.md:240 +msgid "" +"Markedly Structured Text, a Markdown flavor that supports Sphinx " +"directives and roles. It allows Markdown-based docs while keeping Sphinx " +"features. See [myst-parser.readthedocs.io](https://myst-" +"parser.readthedocs.io)." +msgstr "" + +#: ../../documentation/glossary.md:14 +#, fuzzy +msgid "README" +msgstr "README ファイル" + +#: ../../documentation/glossary.md:246 +msgid "" +"The front page of your package on GitHub and often on PyPI. A good README" +" explains purpose, installation, usage, and support options." +msgstr "" + +#: ../../documentation/glossary.md:250 +msgid "AI" +msgstr "" + +#: ../../documentation/glossary.md +msgid "Generative AI / LLM" +msgstr "" + +#: ../../documentation/glossary.md:254 +msgid "" +"Generative AI systems produce content such as text, code, or images. LLM " +"stands for Large Language Model, the technology behind tools such as " +"ChatGPT, GitHub Copilot, and Claude." +msgstr "" #: ../../documentation/hosting-tools/intro.md:1 msgid "Tools to Build and Host your Documentation" @@ -520,6 +1048,7 @@ msgid "[sphinxext.opengraph](https://github.com/sphinx-doc/sphinxext-opengraph)" msgstr "[sphinxext.opengraph](https://github.com/sphinx-doc/sphinxext-opengraph)" #: ../../documentation/hosting-tools/website-hosting-optimizing-your-docs.md:42 +#, fuzzy msgid "" "OpenGraph is an extension that allows you to add metadata to your " "documentation content pages. [The OpenGraph protocol allows other " @@ -527,8 +1056,8 @@ msgid "" "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." +"media and even for shares on collaboration platforms like Slack and " +"Discourse." msgstr "" "OpenGraphは、ドキュメントのコンテンツページにメタデータを追加できる拡張機能です。 " "[OpenGraphプロトコルは、共有されたときに他のウェブサイトがあなたのページのコンテンツの有用なプレビューを提供することを可能にします](https://www.freecodecamp.org/news" @@ -866,8 +1395,9 @@ msgstr "" "このドキュメントは、ソフトウェアの各バージョンで何が追加、修正、変更、削除されたかをユーザーが理解するのに役立ちます。" #: ../../documentation/repository-files/changelog-file.md:11 +#, fuzzy msgid "" -"[Keep a CHAGELOG.md](https://keepachangelog.com/en/1.1.0/) is a great, " +"[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) is a great, " "simple resource for understanding what a changelog is and how to create a" " good changelog. It also includes examples of things to avoid." msgstr "" @@ -921,11 +1451,12 @@ msgid "What does it include?" msgstr "その内容は？" #: ../../documentation/repository-files/changelog-file.md:27 +#, fuzzy msgid "" -"The contents of a changelog.md file typically follow a structured format," -" detailing the changes introduced in each release. While the exact format" -" may vary depending on the project's conventions, some common elements " -"found in changelogs for Python packages include:" +"The contents of a `CHANGELOG.md` file typically follow a structured " +"format, detailing the changes introduced in each release. While the exact" +" format may vary depending on the project's conventions, some common " +"elements found in changelogs for Python packages include:" msgstr "" "changelog.md ファイルの内容は一般的に構造化されたフォーマットに従い、各リリースで導入された変更の詳細を記述します。 " "正確なフォーマットはプロジェクトの規約によって異なるかもしれませんが、 Python パッケージの changelog " @@ -1328,10 +1859,11 @@ msgstr "" "formatting-and-styling-tools), など。" #: ../../documentation/repository-files/contributing-file.md:53 +#, fuzzy msgid "" "This guide should also include information for someone interested in " "asking questions. Some projects accept questions as GitHub or GitLab " -"issues. Others use GitHub discussions, Discourse, or even a Discord " +"issues. Others use GitHub Discussions, Discourse, or even a Discord " "server." msgstr "" "このガイドには、質問することに興味がある人のための情報も含まれているはずです。 " @@ -1917,11 +2449,31 @@ msgstr "" "repository/about-citation-files) を使うことで、あなたのパッケージの引用方法をユーザに伝えることができます。 " "このトピックについては、Zenodoを使ってパッケージのDOIを作成する際に説明します。" -#: ../../documentation/repository-files/license-files.md:135 +#: ../../documentation/repository-files/license-files.md:136 +msgid "" +"Additional resources on software citation The Turing Way has excellent " +"guides on this topic:" +msgstr "" + +#: ../../documentation/repository-files/license-files.md:139 +msgid "" +"[CITATION.cff files](https://book.the-turing-" +"way.org/communication/citable/citable-cff) — detailed guide on creating " +"and maintaining citation files" +msgstr "" + +#: ../../documentation/repository-files/license-files.md:140 +msgid "" +"[Software citation pathways](https://book.the-turing-way.org/pathways" +"/pathways-software-citation) — overview of how software citation works in" +" practice" +msgstr "" + +#: ../../documentation/repository-files/license-files.md:142 msgid "Citation.cff files: Making your software citable" msgstr "" -#: ../../documentation/repository-files/license-files.md:137 +#: ../../documentation/repository-files/license-files.md:144 msgid "" "A `CITATION.cff` file is a machine-readable file that provides citation " "information for your software package. The \"cff\" stands for \"Citation " @@ -1929,11 +2481,11 @@ msgid "" "metadata." msgstr "" -#: ../../documentation/repository-files/license-files.md:139 +#: ../../documentation/repository-files/license-files.md:146 msgid "What citation.cff files add to your repository" msgstr "" -#: ../../documentation/repository-files/license-files.md:141 +#: ../../documentation/repository-files/license-files.md:148 msgid "" "When you add a `CITATION.cff` file to your repository, GitHub " "automatically detects it and displays a \"Cite this repository\" button. " @@ -1943,11 +2495,11 @@ msgid "" "citation formats for users." msgstr "" -#: ../../documentation/repository-files/license-files.md:143 +#: ../../documentation/repository-files/license-files.md:150 msgid "How dates are tracked in citation.cff files" msgstr "" -#: ../../documentation/repository-files/license-files.md:145 +#: ../../documentation/repository-files/license-files.md:152 msgid "" "The citation file tracks important dates for your software. The `date-" "released` field shows when the current version was released. The `date-" @@ -1955,17 +2507,17 @@ msgid "" "also include a `version` field with the specific version number." msgstr "" -#: ../../documentation/repository-files/license-files.md:147 +#: ../../documentation/repository-files/license-files.md:154 msgid "" "You should update these dates with each new release so people cite the " "correct version of your software." msgstr "" -#: ../../documentation/repository-files/license-files.md:149 +#: ../../documentation/repository-files/license-files.md:156 msgid "Integration with Zenodo" msgstr "" -#: ../../documentation/repository-files/license-files.md:151 +#: ../../documentation/repository-files/license-files.md:158 msgid "" "Citation.cff files work well with Zenodo, which is a popular place to " "store research software and get DOIs. When you create a Zenodo release, " @@ -1976,11 +2528,11 @@ msgid "" "citation information." msgstr "" -#: ../../documentation/repository-files/license-files.md:154 +#: ../../documentation/repository-files/license-files.md:161 msgid "Here's a basic example of what a `CITATION.cff` file might look like:" msgstr "" -#: ../../documentation/repository-files/license-files.md:170 +#: ../../documentation/repository-files/license-files.md:177 msgid "References" msgstr "参考文献" @@ -2385,6 +2937,25 @@ msgstr "" "[Art of README - Kira (@hackergrrl)](https://github.com/hackergrrl/art-" "of-readme)" +#: ../../documentation/repository-files/readme-file-best-practices.md:178 +#, python-format +msgid "" +"[Standard Readme - Richard Littauer](https://github.com/RichardLitt" +"/standard-readme) [![standard-readme " +"compliant](https://img.shields.io/badge/readme%20style-standard-" +"brightgreen.svg)](https://github.com/RichardLitt/standard-readme)" +msgstr "" + +#: ../../documentation/repository-files/readme-file-best-practices.md:178 +msgid "standard-readme compliant" +msgstr "" + +#: ../../documentation/repository-files/readme-file-best-practices.md:179 +msgid "" +"[Standard Readme pre-commit hooks](https://github.com/tkoyama010" +"/standard-readme-pre-commit)" +msgstr "" + #: ../../documentation/write-user-documentation/create-package-tutorials.md:1 msgid "Create tutorials in your Python package documentation" msgstr "Pythonパッケージのドキュメントにチュートリアルを作成する" @@ -3301,3 +3872,4 @@ msgstr "autodocは、あなたのコードの関数、クラス、メソッド #, fuzzy msgid "sphinx gallery for tutorials." msgstr "チュートリアルのためのsphinxギャラリー。" + diff --git a/locales/ja/LC_MESSAGES/index.po b/locales/ja/LC_MESSAGES/index.po index b6fe51d2..d2046544 100644 --- a/locales/ja/LC_MESSAGES/index.po +++ b/locales/ja/LC_MESSAGES/index.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -20,36 +20,45 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" -#: ../../index.md:284 +#: ../../index.md:257 msgid "Tutorials" msgstr "チュートリアル" -#: ../../index.md:291 +#: ../../index.md:264 msgid "Packaging" msgstr "パッケージング" -#: ../../index.md:146 ../../index.md:299 +#: ../../index.md:135 ../../index.md:272 msgid "Documentation" msgstr "ドキュメンテーション" -#: ../../index.md:194 ../../index.md:307 +#: ../../index.md:175 ../../index.md:280 msgid "Tests" msgstr "テスト" -#: ../../index.md:307 +#: ../../index.md:280 msgid "Testing" msgstr "テスト" -#: ../../index.md:315 +#: ../../index.md:288 msgid "Maintain" msgstr "" -#: ../../index.md:315 +#: ../../index.md:288 msgid "Continuous Integration" msgstr "継続的インテグレーション" +#: ../../index.md:296 +msgid "Glossary" +msgstr "" + +#: ../../index.md:296 +#, fuzzy +msgid "Reference" +msgstr "✿ リファレンスガイド ✿" + #: ../../index.md:1 msgid "pyOpenSci Python Package Guide" msgstr "pyOpenSci Pythonパッケージガイド" @@ -61,12 +70,13 @@ msgid "" msgstr "私たちは、科学者がオープンサイエンスのワークフローを作成するために必要なPythonツールをサポートしています。" #: ../../index.md:20 +#, fuzzy msgid "" "![GitHub release (latest by " "date)](https://img.shields.io/github/v/release/pyopensci/python-package-" "guide?color=purple&display_name=tag&style=plastic) " "[![](https://img.shields.io/github/stars/pyopensci/python-package-" -"guide?style=social)](https://github.com/pyopensci/contributing-guide) " +"guide?style=social)](https://github.com/pyopensci/python-package-guide) " "[![DOI](https://zenodo.org/badge/556814582.svg)](https://zenodo.org/badge/latestdoi/556814582)" msgstr "" "![GitHub release (latest by " @@ -176,36 +186,36 @@ msgstr "" "コミュニティのレビュープロセスに参加したり、 [GitHub リポジトリはこちら](https://github.com/pyOpenSci" "/python-package-guide) で今後のチュートリアルの開発を見守ったりしてください。" -#: ../../index.md:70 +#: ../../index.md:68 msgid "✿ Create a Package Tutorials ✿" msgstr "✿ チュートリアルパッケージの作成 ✿" -#: ../../index.md:74 +#: ../../index.md:72 msgid "[What is a Python package?](/tutorials/intro)" msgstr "[Pythonパッケージとは何か?](/tutorials/intro)" -#: ../../index.md:75 +#: ../../index.md:73 #, fuzzy msgid "[Create a Python package](/tutorials/create-python-package)" msgstr "[コードをインストール可能にする](/tutorials/create-python-package)" -#: ../../index.md:76 +#: ../../index.md:74 msgid "[Publish your package to (test) PyPI](/tutorials/publish-pypi)" msgstr "[パッケージを(テスト用の)PyPIに公開する](/tutorials/publish-pypi)" -#: ../../index.md:77 +#: ../../index.md:75 msgid "[Publish your package to conda-forge](/tutorials/publish-conda-forge)" msgstr "[パッケージを conda-forge に公開する](/tutorials/publish-conda-forge)" -#: ../../index.md:82 +#: ../../index.md:78 msgid "✿ Package Metadata Tutorials ✿" msgstr "✿パッケージメタデータチュートリアル✿" -#: ../../index.md:86 +#: ../../index.md:82 msgid "[How to add a README file](/tutorials/add-readme)" msgstr "[READMEファイルの追加方法](/tutorials/add-readme)" -#: ../../index.md:87 +#: ../../index.md:83 msgid "" "[How to add metadata to a pyproject.toml file for publication to " "PyPI.](/tutorials/pyproject-toml.md)" @@ -213,27 +223,32 @@ msgstr "" "[PyPIに公開するためにpyproject.tomlファイルにメタデータを追加する方法](/tutorials/pyproject-" "toml.md)" -#: ../../index.md:92 +#: ../../index.md:86 msgid "✿ Packaging Tool Tutorials ✿" msgstr "✿パッケージングツールのチュートリアル✿" -#: ../../index.md:96 +#: ../../index.md:90 msgid "[Introduction to Hatch](/tutorials/get-to-know-hatch)" msgstr "[Hatch入門](/tutorials/get-to-know-hatch)" -#: ../../index.md:101 +#: ../../index.md:91 +#, fuzzy +msgid "[Run Python scripts using Hatch](/tutorials/run-python-scripts-hatch)" +msgstr "[コードをインストール可能にする](/tutorials/create-python-package)" + +#: ../../index.md:94 msgid "✿ Reference Guides ✿" msgstr "✿ リファレンスガイド ✿" -#: ../../index.md:105 +#: ../../index.md:98 msgid "[Command Line Reference Guide](/tutorials/command-line-reference)" msgstr "[コマンドラインリファレンスガイド](/tutorials/command-line-reference)" -#: ../../index.md:109 +#: ../../index.md:102 msgid "Python Packaging for Scientists" msgstr "科学者のためのPythonパッケージング" -#: ../../index.md:111 +#: ../../index.md:104 msgid "" "Learn about Python packaging best practices. You will also get to know " "the the vibrant ecosystem of packaging tools that are available to help " @@ -242,15 +257,15 @@ msgstr "" "Python のパッケージングのベストプラクティスについて学びます。 また、Python " "のパッケージングを支援するために利用可能なパッケージングツールの活発なエコシステムを知ることができます。" -#: ../../index.md:120 +#: ../../index.md:111 msgid "✨ Create your package ✨" msgstr "✨パッケージの作成✨" -#: ../../index.md:124 +#: ../../index.md:115 msgid "[Package file structure](/package-structure-code/python-package-structure)" msgstr "[パッケージファイル構造](/package-structure-code/python-package-structure)" -#: ../../index.md:125 +#: ../../index.md:116 msgid "" "[Package metadata / pyproject.toml](package-structure-code/pyproject-" "toml-python-package-metadata.md)" @@ -258,7 +273,7 @@ msgstr "" "[パッケージメタデータ / pyproject.toml](package-structure-code/pyproject-toml-" "python-package-metadata.md)" -#: ../../index.md:126 +#: ../../index.md:117 msgid "" "[Build your package (sdist / wheel)](package-structure-code/python-" "package-distribution-files-sdist-wheel.md)" @@ -266,11 +281,11 @@ msgstr "" "[パッケージのビルド (sdist / wheel)](package-structure-code/python-package-" "distribution-files-sdist-wheel.md)" -#: ../../index.md:127 +#: ../../index.md:118 msgid "[Declare dependencies](package-structure-code/declare-dependencies.md)" msgstr "[依存関係の宣言](package-structure-code/declare-dependencies.md)" -#: ../../index.md:128 +#: ../../index.md:119 msgid "" "[Navigate the packaging tool ecosystem](package-structure-code/python-" "package-build-tools.md)" @@ -278,7 +293,7 @@ msgstr "" "[パッケージングツールのエコシステムをナビゲートする](package-structure-code/python-package-build-" "tools.md)" -#: ../../index.md:129 +#: ../../index.md:120 msgid "" "[Non pure Python builds](package-structure-code/complex-python-package-" "builds.md)" @@ -286,23 +301,23 @@ msgstr "" "[純粋な Python 以外のビルド](package-structure-code/complex-python-package-" "builds.md)" -#: ../../index.md:134 +#: ../../index.md:123 msgid "✨ Publish your package ✨" msgstr "✨パッケージを公開する✨" -#: ../../index.md:138 +#: ../../index.md:127 msgid "" "Gain a better understanding of the Python packaging ecosystem Learn about" " best practices for:" msgstr "Pythonのパッケージングエコシステムをより深く理解するためのベストプラクティスを学ぶ:" -#: ../../index.md:141 +#: ../../index.md:130 msgid "" "[Package versioning & release](/package-structure-code/python-package-" "versions.md)" msgstr "[パッケージのバージョン管理とリリース](/package-structure-code/python-package-versions.md)" -#: ../../index.md:142 +#: ../../index.md:131 msgid "" "[Publish to PyPI & Conda-forge](/package-structure-code/publish-python-" "package-pypi-conda.md)" @@ -310,23 +325,23 @@ msgstr "" "[PyPIとConda-forgeへの公開](/package-structure-code/publish-python-package-" "pypi-conda.md)" -#: ../../index.md:155 +#: ../../index.md:142 msgid "✨ Write The Docs ✨" msgstr "✨ドキュメントを書く✨" -#: ../../index.md:158 +#: ../../index.md:145 msgid "" "[Create documentation for your users](/documentation/write-user-" "documentation/intro)" msgstr "[ユーザーのための文書を作成する](/documentation/write-user-documentation/intro)" -#: ../../index.md:159 +#: ../../index.md:146 msgid "" "[Core files to include in your package repository](/documentation" "/repository-files/intro)" msgstr "[パッケージリポジトリに含めるコアファイル](/documentation/repository-files/intro)" -#: ../../index.md:160 +#: ../../index.md:147 msgid "" "[Write tutorials to show how your package is used](/documentation/write-" "user-documentation/create-package-tutorials)" @@ -334,27 +349,27 @@ msgstr "" "[パッケージがどのように使われるかを示すチュートリアルを書く](/documentation/write-user-documentation" "/create-package-tutorials)" -#: ../../index.md:165 +#: ../../index.md:150 msgid "✨ Developer Docs ✨" msgstr "✨開発者向けドキュメント✨" -#: ../../index.md:168 +#: ../../index.md:153 msgid "" "[Create documentation for collaborating developers](/documentation" "/repository-files/contributing-file)" msgstr "[共同開発者のためのドキュメントの作成](/documentation/repository-files/contributing-file)" -#: ../../index.md:169 +#: ../../index.md:154 msgid "" "[Write a development guide](/documentation/repository-files/development-" "guide)" msgstr "[開発ガイドを書く](/documentation/repository-files/development-guide)" -#: ../../index.md:174 +#: ../../index.md:157 msgid "✨ Document For A Community ✨" msgstr "✨コミュニティのためのドキュメント✨" -#: ../../index.md:177 +#: ../../index.md:160 msgid "" "[Writing a README file](/documentation/repository-files/readme-file-best-" "practices)" @@ -362,29 +377,29 @@ msgstr "" "[READMEファイルの書き方](/documentation/repository-files/readme-file-best-" "practices)" -#: ../../index.md:178 +#: ../../index.md:161 msgid "" "[Set norms with a Code of Conduct](/documentation/repository-files/code-" "of-conduct-file)" msgstr "[行動規範で規範を定める](/documentation/repository-files/code-of-conduct-file)" -#: ../../index.md:179 +#: ../../index.md:162 msgid "[License your package](/documentation/repository-files/license-files)" msgstr "[パッケージのライセンス](/documentation/repository-files/license-files)" -#: ../../index.md:184 +#: ../../index.md:165 msgid "✨ Publish Your Docs ✨" msgstr "✨ドキュメントを公開する✨" -#: ../../index.md:187 +#: ../../index.md:168 msgid "[How to publish your docs](/documentation/hosting-tools/intro)" msgstr "[ドキュメントを公開する方法](/documentation/hosting-tools/intro)" -#: ../../index.md:188 +#: ../../index.md:169 msgid "[Using Sphinx](/documentation/hosting-tools/intro)" msgstr "[Sphinxを使う](/documentation/hosting-tools/intro)" -#: ../../index.md:189 +#: ../../index.md:170 msgid "" "[Markdown, MyST, and ReST](/documentation/hosting-tools/myst-markdown-" "rst-doc-syntax)" @@ -392,7 +407,7 @@ msgstr "" "[Markdown、MyST、およびReST](/documentation/hosting-tools/myst-markdown-rst-" "doc-syntax)" -#: ../../index.md:190 +#: ../../index.md:171 msgid "" "[Host your docs on Read The Docs or GitHub Pages](/documentation/hosting-" "tools/publish-documentation-online)" @@ -400,79 +415,71 @@ msgstr "" "[Read The Docs または GitHub Pages でドキュメントをホストする](/documentation/hosting-" "tools/publish-documentation-online)" -#: ../../index.md:203 +#: ../../index.md:181 msgid "✨ Tests for your Python package ✨" msgstr "✨Pythonパッケージのテスト✨" -#: ../../index.md:206 +#: ../../index.md:184 msgid "[Intro to testing](tests/index.md)" msgstr "[テスト入門](tests/index.md)" -#: ../../index.md:207 +#: ../../index.md:185 msgid "[Write tests](tests/write-tests)" msgstr "[テストを書く](tests/write-tests)" -#: ../../index.md:208 +#: ../../index.md:186 msgid "[Types of tests](tests/test-types)" msgstr "[テストの種類](tests/test-types)" -#: ../../index.md:213 +#: ../../index.md:189 msgid "✨ Run your tests ✨" msgstr "✨テストの実行✨" -#: ../../index.md:216 -msgid "[Run tests locally](tests/run-tests)" +#: ../../index.md:192 +#, fuzzy +msgid "[Run tests locally with Hatch](tests/run-tests)" msgstr "[ローカルでテストを実行する](tests/run-tests)" -#: ../../index.md:217 +#: ../../index.md:193 +#, fuzzy +msgid "[Run tests with nox](tests/run-tests-nox)" +msgstr "[ローカルでテストを実行する](tests/run-tests)" + +#: ../../index.md:194 msgid "[Run tests in CI](tests/tests-ci)" msgstr "[CIでテストを実行する](tests/tests-ci)" -#: ../../index.md:221 +#: ../../index.md:198 msgid "Contributing" msgstr "貢献" -#: ../../index.md:230 +#: ../../index.md:205 msgid "✨ Code style & Format ✨" msgstr "✨コードスタイルとフォーマット✨" -#: ../../index.md:233 +#: ../../index.md:208 msgid "[Code style](package-structure-code/code-style-linting-format.md)" msgstr "[コードスタイル](package-structure-code/code-style-linting-format.md)" -#: ../../index.md:238 +#: ../../index.md:211 msgid "✨ Want to contribute? ✨" msgstr "✨貢献したいですか？ ✨" -#: ../../index.md:243 +#: ../../index.md:216 msgid "" "We welcome contributions to this guide. Learn more about how you can " "contribute." msgstr "このガイドへのご貢献をお待ちしております。貢献方法についてはこちらをご覧ください。" -#: ../../index.md:248 -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" -" 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?" +#: ../../index.md:221 +msgid "A group of people building a pyramid with blocks" msgstr "" -"xkcdの漫画で、地面に置かれた棒人間と空中にある棒人間が描かれている。地上にいる人が言っている。 `あなたは飛んでいる！どうやって？` " -"空中にいる人は `Python!` と答える。以下は3つの長方形のマンガで、各ボックスに次のテキストが入っている。ボックス1 - " -"昨夜学んだ。すべてがとてもシンプルだ。Hello worldはprint hello worldだけ。ボックス2 - " -"地上にいる人が言う。まったく新しい世界だ。でもどうやって飛んでるの？ボックス3 - 飛んでいる人はこう言う。- " -"`反重力をインポートしました。薬箱の中のものも全部試しました。でもこれがpythonだと思う。地上の人はこう言っている。- これで終わり？" -#: ../../index.md:254 +#: ../../index.md:227 msgid "A community-created guidebook" msgstr "コミュニティが作るガイドブック" -#: ../../index.md:256 +#: ../../index.md:229 msgid "" "Every page in this guidebook goes through an extensive community review " "process. To ensure our guidebook is both beginner-friendly and accurate, " @@ -482,41 +489,41 @@ msgstr "" "このガイドブックのすべてのページは、コミュニティの広範なレビュープロセスを経ています。 " "このガイドブックが初心者にやさしく、正確であることを保証するために、私たちは幅広いスキルと専門知識を持つ多様なpythonistaや科学者からのレビューを奨励しています。" -#: ../../index.md:259 +#: ../../index.md:232 msgid "View guidebook contributors" msgstr "ガイドブックの貢献者を見る" -#: ../../index.md:267 +#: ../../index.md:240 msgid "Who this guidebook is for" msgstr "このガイドブックの対象者" -#: ../../index.md:269 +#: ../../index.md:242 msgid "" "This guidebook is for anyone interested in learning more about Python " "packaging. It is beginner-friendly and will provide:" msgstr "このガイドブックはPythonのパッケージングについてもっと学びたいと思っている人のためのものです。 初心者に優しく、以下を提供します:" -#: ../../index.md:271 +#: ../../index.md:244 msgid "Beginning-to-end guidance on creating a Python package." msgstr "Pythonパッケージの作成に関する初歩から終わりまでのガイダンス。" -#: ../../index.md:272 +#: ../../index.md:245 msgid "" "Resources to help you navigate the Python packaging ecosystem of tools " "and approaches to packaging." msgstr "Python のパッケージングエコシステムをナビゲートするのに役立つリソースです。" -#: ../../index.md:273 +#: ../../index.md:246 msgid "" "A curated list of resources to help you get your package into documented," " usable and maintainable shape." msgstr "あなたのパッケージが文書化され、使用可能で保守可能な形になるのを助けるリソースの厳選されたリストです。" -#: ../../index.md:275 +#: ../../index.md:248 msgid "Where this guide is headed" msgstr "このガイドの方向性" -#: ../../index.md:277 +#: ../../index.md:250 msgid "" "If you have ideas of things you'd like to see here clarified in this " "guide, [we invite you to open an issue on " @@ -526,16 +533,17 @@ msgstr "" "[GitHubにissueを開いてください。](https://github.com/pyOpenSci/python-package-" "guide/issues) 。" -#: ../../index.md:280 +#: ../../index.md:253 +#, fuzzy msgid "" "If you have questions about our peer review process or packaging in " -"general, you are welcome to use our [pyOpenSci Discourse " -"forum](https://pyopensci.discourse.group/)." +"general, you are welcome to use our [GitHub " +"Discussions](https://github.com/orgs/pyOpenSci/discussions)." msgstr "" "レビュープロセスやパッケージング全般について質問がある場合は、 [pyOpenSci Discourse " "forum](https://pyopensci.discourse.group/) をご利用ください。" -#: ../../index.md:282 +#: ../../index.md:255 msgid "" "This living Python packaging guide is updated as tools and best practices" " evolve in the Python packaging ecosystem. We will be adding new content " @@ -555,3 +563,36 @@ msgstr "" #~ "*私たちはこのセクションに積極的に取り組んでいます。 " #~ "[開発のフォローはこちら](https://github.com/pyOpenSci/python-package-" #~ "guide)*" + +#~ 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 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 "" +#~ "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 071d9423..defab535 100644 --- a/locales/ja/LC_MESSAGES/package-structure-code.po +++ b/locales/ja/LC_MESSAGES/package-structure-code.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -20,7 +20,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" #: ../../package-structure-code/code-style-linting-format.md:1 msgid "Python Package Code Style, Format and Linters" @@ -1669,51 +1669,51 @@ msgid "" "different specifiers" msgstr "依存関係を指定する理由 依存関係を指定する方法 異なる指定子を使用する場合" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Intro" msgstr "イントロ" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Python package structure" msgstr "Pythonパッケージ構造" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "pyproject.toml Package Metadata" msgstr "pyproject.toml パッケージのメタデータ" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Declare dependencies" msgstr "依存関係の宣言" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Package Build Tools" msgstr "パッケージビルドツール" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Build Your Package" msgstr "パッケージをビルドする" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Complex Builds" msgstr "複雑なビルド" -#: ../../package-structure-code/intro.md:183 +#: ../../package-structure-code/intro.md:163 msgid "Create & Build Your Package" msgstr "パッケージを作成 & ビルドする" -#: ../../package-structure-code/intro.md:197 +#: ../../package-structure-code/intro.md:177 msgid "Publish with Conda / PyPI" msgstr "Conda / PyPIで公開する" -#: ../../package-structure-code/intro.md:197 +#: ../../package-structure-code/intro.md:177 msgid "Package versions" msgstr "パッケージバージョン" -#: ../../package-structure-code/intro.md:197 +#: ../../package-structure-code/intro.md:177 msgid "Code style" msgstr "コードスタイル" -#: ../../package-structure-code/intro.md:197 +#: ../../package-structure-code/intro.md:177 msgid "Publish your package" msgstr "パッケージを公開する" @@ -1729,62 +1729,113 @@ msgid "" " and conda-forge." msgstr "" -#: ../../package-structure-code/intro.md:44 +#: ../../package-structure-code/intro.md:9 +#, fuzzy +msgid "New to Python packaging?" +msgstr "Pythonパッケージングツール" + +#: ../../package-structure-code/intro.md:13 +msgid "**Start with our step-by-step tutorials:**" +msgstr "" + +#: ../../package-structure-code/intro.md:15 +msgid "Follow along as we create a package from scratch" +msgstr "" + +#: ../../package-structure-code/intro.md:16 +msgid "Learn by doing with guided examples" +msgstr "" + +#: ../../package-structure-code/intro.md:17 +#, fuzzy +msgid "Perfect for your first package" +msgstr "Pythonパッケージのバージョンを管理するツール" + +#: ../../package-structure-code/intro.md:19 +msgid "Start the tutorial series" +msgstr "" + +#: ../../package-structure-code/intro.md:27 +msgid "Already have code to package?" +msgstr "" + +#: ../../package-structure-code/intro.md:30 +msgid "**Jump into the reference guides:**" +msgstr "" + +#: ../../package-structure-code/intro.md:32 +#, fuzzy +msgid "Learn about package structure and metadata" +msgstr "Pythonパッケージ構造" + +#: ../../package-structure-code/intro.md:33 +msgid "Compare build tools and choose what's right for you" +msgstr "" + +#: ../../package-structure-code/intro.md:34 +msgid "Understand the publishing process" +msgstr "" + +#: ../../package-structure-code/intro.md:36 +msgid "Start with the cards below ↓" +msgstr "" + +#: ../../package-structure-code/intro.md:40 msgid "How this content is developed" msgstr "このコンテンツの開発方法" -#: ../../package-structure-code/intro.md:47 +#: ../../package-structure-code/intro.md:43 msgid "" "All of the content in this guide has been vetted by community members, " "including maintainers and developers of the core packaging tools." msgstr "このガイドの内容はすべて、コアパッケージングツールのメンテナや開発者を含むコミュニティメンバーによって吟味されています。" -#: ../../package-structure-code/intro.md:50 +#: ../../package-structure-code/intro.md:46 #, fuzzy msgid "What you'll learn" msgstr "ここで学べること" -#: ../../package-structure-code/intro.md:52 +#: ../../package-structure-code/intro.md:48 msgid "In this section, you'll learn how to:" msgstr "" -#: ../../package-structure-code/intro.md:54 +#: ../../package-structure-code/intro.md:50 msgid "" "**Structure your package** - Choose between src and flat layouts, " "organize tests and documentation" msgstr "" -#: ../../package-structure-code/intro.md:55 +#: ../../package-structure-code/intro.md:51 msgid "" "**Configure metadata** - Set up `pyproject.toml` with project " "information, dependencies, and versioning" msgstr "" -#: ../../package-structure-code/intro.md:56 +#: ../../package-structure-code/intro.md:52 msgid "" "**Choose build tools** - Compare Hatch, PDM, Poetry, and setuptools to " "find the right fit" msgstr "" -#: ../../package-structure-code/intro.md:57 +#: ../../package-structure-code/intro.md:53 msgid "" "**Build distributions** - Create sdist and wheel files ready for " "publication" msgstr "" -#: ../../package-structure-code/intro.md:58 +#: ../../package-structure-code/intro.md:54 msgid "" "**Publish your package** - Make your package available on PyPI and " "optionally conda-forge" msgstr "" -#: ../../package-structure-code/intro.md:59 +#: ../../package-structure-code/intro.md:55 msgid "" "**Maintain code quality** - Set up linters and formatters to keep your " "code consistent" msgstr "" -#: ../../package-structure-code/intro.md:61 +#: ../../package-structure-code/intro.md:57 #, fuzzy msgid "" "Our recommendations align with current [Python packaging " @@ -1796,17 +1847,17 @@ msgstr "" "[Pythonコミュニティ](https://packaging.python.org/en/latest/) と " "[科学コミュニティ](https://scientific-python.org/specs/) に合わせることも試みています。" -#: ../../package-structure-code/intro.md:63 +#: ../../package-structure-code/intro.md:59 #, fuzzy msgid "Package setup" msgstr "パッケージバージョン" -#: ../../package-structure-code/intro.md:72 +#: ../../package-structure-code/intro.md:66 #, fuzzy msgid "✨ Package file structure ✨" msgstr "✨ 1. パッケージのファイル構成 ✨" -#: ../../package-structure-code/intro.md:74 +#: ../../package-structure-code/intro.md:68 msgid "" "Learn how to organize your package files using [src or flat layouts" "](package-source-layout). This page helps you decide on a package " @@ -1815,12 +1866,12 @@ msgid "" "layout)." msgstr "" -#: ../../package-structure-code/intro.md:79 +#: ../../package-structure-code/intro.md:71 #, fuzzy msgid "✨ Add metadata ✨" msgstr "✨ 4. メタデータを追加する ✨" -#: ../../package-structure-code/intro.md:81 +#: ../../package-structure-code/intro.md:73 #, fuzzy msgid "" "Learn how to add [project metadata](pyproject-toml-python-package-" @@ -1831,12 +1882,12 @@ msgstr "" "Python パッケージにプロジェクトのメタデータを追加して、PyPI " "でのフィルタリングと、パッケージインストーラがパッケージをビルドしてインストールするために必要なメタデータの両方をサポートする方法を学びましょう。" -#: ../../package-structure-code/intro.md:88 +#: ../../package-structure-code/intro.md:78 #, fuzzy msgid "✨ Declare dependencies ✨" msgstr "依存関係の宣言" -#: ../../package-structure-code/intro.md:90 +#: ../../package-structure-code/intro.md:80 msgid "" "Learn how to specify [required dependencies](required-dependencies), " "[optional feature dependencies](optional-dependencies), and [development " @@ -1844,12 +1895,12 @@ msgid "" "toml-overview)." msgstr "" -#: ../../package-structure-code/intro.md:95 +#: ../../package-structure-code/intro.md:83 #, fuzzy msgid "✨ Setup package versioning ✨" msgstr "✨ 5. パッケージのバージョニングを設定する ✨" -#: ../../package-structure-code/intro.md:97 +#: ../../package-structure-code/intro.md:85 msgid "" "Learn how to manage package versions using [semantic versioning (SemVer" ")](package-versioning) or [calendar versioning (CalVer)](package-" @@ -1858,17 +1909,17 @@ msgid "" "tools like hatch_vcs or setuptools-scm." msgstr "" -#: ../../package-structure-code/intro.md:101 +#: ../../package-structure-code/intro.md:89 #, fuzzy msgid "Development practices" msgstr "開発状況" -#: ../../package-structure-code/intro.md:110 +#: ../../package-structure-code/intro.md:96 #, fuzzy msgid "✨ Code style & linters ✨" msgstr "✨6. コードスタイルとリンター✨" -#: ../../package-structure-code/intro.md:112 +#: ../../package-structure-code/intro.md:98 msgid "" "Learn how to set up [code formatters and linters](code-style-tools) " "([Black](about-black), [Ruff](about-ruff), [flake8](about-flake8)) to " @@ -1876,16 +1927,16 @@ msgid "" "maintains consistent code style throughout your project." msgstr "" -#: ../../package-structure-code/intro.md:116 +#: ../../package-structure-code/intro.md:102 msgid "Build & publish" msgstr "" -#: ../../package-structure-code/intro.md:125 +#: ../../package-structure-code/intro.md:109 #, fuzzy msgid "✨ Choose your build tool ✨" msgstr "ビルドワークフローツールの選択" -#: ../../package-structure-code/intro.md:127 +#: ../../package-structure-code/intro.md:111 msgid "" "Learn how to choose the right packaging tool for your project. Compare " "[Hatch](about-hatch), [PDM](about-pdm), [Poetry](about-poetry), and " @@ -1893,24 +1944,24 @@ msgid "" "See the [summary comparison](summary-build-tools) to help decide." msgstr "" -#: ../../package-structure-code/intro.md:132 +#: ../../package-structure-code/intro.md:114 #, fuzzy msgid "✨ Build your package ✨" msgstr "パッケージをビルドする" -#: ../../package-structure-code/intro.md:134 +#: ../../package-structure-code/intro.md:116 msgid "" "Learn how to build your Python package into [distribution files](build-" "package) ([sdist](python-source-distribution) and [wheel](python-wheel)) " "that can be published on [PyPI](publish-pypi-conda)." msgstr "" -#: ../../package-structure-code/intro.md:139 +#: ../../package-structure-code/intro.md:119 #, fuzzy msgid "✨ Publish to PyPI and Conda ✨" msgstr "✨ 4. PyPIとCondaに公開する ✨" -#: ../../package-structure-code/intro.md:141 +#: ../../package-structure-code/intro.md:121 msgid "" "Learn how to publish your package to [PyPI](publish-pypi-conda) and " "optionally to [conda-forge](how-to-submit-to-conda-forge). This page " @@ -1919,48 +1970,48 @@ msgid "" "forge) after publishing to PyPI." msgstr "" -#: ../../package-structure-code/intro.md:145 +#: ../../package-structure-code/intro.md:125 msgid "Choosing the right tools" msgstr "" -#: ../../package-structure-code/intro.md:147 +#: ../../package-structure-code/intro.md:127 msgid "" "Not sure which build tool to use? This decision tree can help you choose " "based on your package's needs:" msgstr "" -#: ../../package-structure-code/intro.md:151 +#: ../../package-structure-code/intro.md:131 msgid "" "Figure showing a decision tree with the various packaging tool front-end " "and back-end options." msgstr "様々なパッケージングツールのフロントエンドとバックエンドのオプションの決定ツリーを示す図。" -#: ../../package-structure-code/intro.md:153 +#: ../../package-structure-code/intro.md:133 msgid "" "Use this decision tree to help select a packaging tool. See the " "[packaging tools page](python-package-build-tools) for detailed " "comparisons and recommendations." msgstr "" -#: ../../package-structure-code/intro.md:156 +#: ../../package-structure-code/intro.md:136 msgid "Our recommendations" msgstr "" -#: ../../package-structure-code/intro.md:158 +#: ../../package-structure-code/intro.md:138 msgid "We suggest tools and approaches based on three principles:" msgstr "" -#: ../../package-structure-code/intro.md:160 +#: ../../package-structure-code/intro.md:140 msgid "" "**Beginner-friendly** - Tools that are easy to learn and use for those " "new to packaging" msgstr "" -#: ../../package-structure-code/intro.md:161 +#: ../../package-structure-code/intro.md:141 msgid "**Well-maintained** - Tools with active development and good documentation" msgstr "" -#: ../../package-structure-code/intro.md:162 +#: ../../package-structure-code/intro.md:142 #, fuzzy msgid "" "**Standards-aligned** - Tools that follow current [Python packaging " @@ -1971,18 +2022,18 @@ msgstr "" "[Pythonコミュニティ](https://packaging.python.org/en/latest/) と " "[科学コミュニティ](https://scientific-python.org/specs/) に合わせることも試みています。" -#: ../../package-structure-code/intro.md:164 +#: ../../package-structure-code/intro.md:144 #, fuzzy msgid "Pure Python vs. complex builds" msgstr "複雑なビルド" -#: ../../package-structure-code/intro.md:166 +#: ../../package-structure-code/intro.md:146 msgid "" "**Pure Python packages** can use any modern tool (Hatch, PDM, Poetry, " "Flit) - choose based on the features you want" msgstr "" -#: ../../package-structure-code/intro.md:167 +#: ../../package-structure-code/intro.md:147 msgid "" "**Packages with C/C++ extensions** may need additional build steps. See " "our [complex builds page](complex-python-package-builds) for guidance. " @@ -1991,17 +2042,17 @@ msgid "" ".scientific-python.org/development/guides/packaging-compiled/)." msgstr "" -#: ../../package-structure-code/intro.md:169 +#: ../../package-structure-code/intro.md:149 msgid "" "Most scientific Python packages start simple and can evolve to handle " "more complex requirements as needed." msgstr "" -#: ../../package-structure-code/intro.md:171 +#: ../../package-structure-code/intro.md:151 msgid "Submitting your package for peer review?" msgstr "" -#: ../../package-structure-code/intro.md:173 +#: ../../package-structure-code/intro.md:153 #, fuzzy msgid "" "If you're planning to submit your package to pyOpenSci for [peer " @@ -2016,18 +2067,18 @@ msgstr "" "chief-guide.html#editor-checklist-template) " "を見てください。これらのチェックは、私たちにパッケージをレビューのために提出しようと計画している作者と、Pythonパッケージを作成し始めたばかりの人の両方にとって、調べるのに便利です。" -#: ../../package-structure-code/intro.md:175 +#: ../../package-structure-code/intro.md:155 msgid "These are recommendations, not requirements" msgstr "" -#: ../../package-structure-code/intro.md:178 +#: ../../package-structure-code/intro.md:158 msgid "" "The suggestions in this guide are designed to help you create a well-" "structured package. They are **not** specific requirements for pyOpenSci " "peer review." msgstr "" -#: ../../package-structure-code/intro.md:180 +#: ../../package-structure-code/intro.md:160 #, fuzzy msgid "" "If you're submitting to pyOpenSci, see our [package " @@ -5238,41 +5289,115 @@ msgid "README.md" msgstr "README.md" #: ../../package-structure-code/python-package-structure.md:80 -#, python-brace-format -msgid "" -"Click here to read about our packaging documentation requirements. ::: " -":::{admonition} Example scientific packages that use src/package layout " -"* Sourmash * bokeh * openscm * awkward * poliastro ::: (src-layout-" -"test)= ## The src/ layout and testing The benefit of using the " -"src/package layout is that it ensures tests are run against the installed" -" version of your package rather than the files in your package working " -"directory. If you run your tests on your files rather than the installed " -"version of your package, you may be missing issues that users encounter " -"when your package is installed. If tests/ are outside the src/package " -"directory, they aren't included in the package's wheel. This makes your " -"package size slightly smaller, which places a smaller storage burden on " -"PyPI, and makes them faster to fetch. - Read more about reasons to use " -"the src/package layout :::{admonition} How Python discovers and " -"prioritizes importing modules By default, Python adds a module in your " -"current working directory to the front of the Python module search path." -" This means that if you run your tests in your package's working " -"directory, using a flat layout, /package/module.py, Python will discover " -"package/module.py file before it discovers the installed package. " -"However, if your package lives in a src/ directory structure src/package," -" then it won't be added to the Python path by default. This means that " -"when you import your package, Python will be forced to search the active " -"environment (which has your package installed). Note: Python versions " -"3.11 and above have a path setting that can be adjusted to ensure the " -"priority is to use installed packages first (e.g., PYTHONSAFEPATH). ::: " -"### Don't include tests in your package wheel Writing tests for your " -"package is important; however, we do not recommend including tests as " -"part of your package wheel by default. However, not including tests in " -"your package distribution will make it harder for people other than " -"yourself to test whether your package runs properly on their system. If " -"you have a small test suite (Python files + data), and think your users " -"may want to run tests locally on their systems, you can include tests by " -"moving the tests/ directory into the src/package directory (see example " -"below). ```bash src/ package/ tests/ docs/" +msgid "Click here to read about our packaging documentation requirements." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:87 +#, fuzzy +msgid "Example scientific packages that use **src/package** layout" +msgstr "フラットレイアウトを使用する科学的Pythonのコアパッケージ" + +#: ../../package-structure-code/python-package-structure.md:89 +#, fuzzy +msgid "[Sourmash](https://github.com/sourmash-bio/sourmash)" +msgstr "[numpy](https://github.com/numpy/numpy)" + +#: ../../package-structure-code/python-package-structure.md:90 +#, fuzzy +msgid "[bokeh](https://github.com/bokeh/bokeh)" +msgstr "[Jupyter notebook](https://github.com/jupyter/notebook)" + +#: ../../package-structure-code/python-package-structure.md:91 +#, fuzzy +msgid "[openscm](https://github.com/openscm/openscm-runner)" +msgstr "[scipy](https://github.com/scipy/scipy)" + +#: ../../package-structure-code/python-package-structure.md:92 +#, fuzzy +msgid "[awkward](https://github.com/scikit-hep/awkward)" +msgstr "[scikit-learn](https://github.com/scikit-learn/scikit-learn)" + +#: ../../package-structure-code/python-package-structure.md:93 +#, fuzzy +msgid "[poliastro](https://github.com/poliastro/poliastro/)" +msgstr "[pandas](https://github.com/pandas-dev/pandas)" + +#: ../../package-structure-code/python-package-structure.md:98 +msgid "The src layout and testing" +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:100 +msgid "" +"The benefit of using the **src/package** layout is that it ensures tests " +"are run against the installed version of your package rather than the " +"files in your package working directory. If you run your tests on your " +"files rather than the installed version of your package, you may be " +"missing issues that users encounter when your package is installed." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:106 +msgid "" +"If `tests/` are outside the **src/package** directory, they aren't " +"included in the package's [wheel](python-wheel). This makes your package " +"size slightly smaller, which places a smaller storage burden on PyPI, and" +" makes them faster to fetch." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:108 +msgid "" +"[Read more about reasons to use the **src/package** " +"layout](https://hynek.me/articles/testing-packaging/)" +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:110 +msgid "How Python discovers and prioritizes importing modules" +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:112 +msgid "" +"By default, Python adds a module in your current working directory to the" +" front of the Python module search path." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:114 +msgid "" +"This means that if you run your tests in your package's working " +"directory, using a flat layout, `/package/module.py`, Python will " +"discover `package/module.py` file before it discovers the installed " +"package." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:116 +msgid "" +"However, if your package lives in a src/ directory structure " +"**src/package**, then it won't be added to the Python path by default. " +"This means that when you import your package, Python will be forced to " +"search the active environment (which has your package installed)." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:118 +msgid "" +"Note: Python versions 3.11 and above have a path setting that can be " +"adjusted to ensure the priority is to use installed packages first (e.g.," +" `PYTHONSAFEPATH`)." +msgstr "" + +#: ../../package-structure-code/python-package-structure.md:121 +#, fuzzy +msgid "Don't include tests in your package wheel" +msgstr "**テストスイートのデータセットをパッケージに含めないでください**" + +#: ../../package-structure-code/python-package-structure.md:123 +msgid "" +"Writing [tests](tests-intro) for your package is important; however, we " +"do not recommend including tests as part of your [package wheel](python-" +"wheel) by default. However, not including tests in your package " +"distribution will make it harder for people other than yourself to test " +"whether your package runs properly on their system. If you have a small " +"test suite (Python files + data), and think your users may want to run " +"tests locally on their systems, you can include tests by moving the " +"`tests/` directory into the **src/package** directory (see example " +"below)." msgstr "" #: ../../package-structure-code/python-package-structure.md:132 @@ -7313,3 +7438,72 @@ msgstr "" #~ "を持っていて、ユーザが自分のシステムでローカルにテストを実行したいと思う場合、`tests/` ディレクトリを " #~ "**src/package** ディレクトリに移動することでテストを含めることができます " #~ "(以下の例を参照してください)。" + +#~ msgid "" +#~ "Click here to read about our " +#~ "packaging documentation requirements. ::: " +#~ ":::{admonition} Example scientific packages " +#~ "that use src/package layout * Sourmash" +#~ " * bokeh * openscm * awkward *" +#~ " poliastro ::: (src-layout-test)= " +#~ "## The src/ layout and testing " +#~ "The benefit of using the src/package " +#~ "layout is that it ensures tests " +#~ "are run against the installed version" +#~ " of your package rather than the " +#~ "files in your package working directory." +#~ " If you run your tests on your" +#~ " files rather than the installed " +#~ "version of your package, you may " +#~ "be missing issues that users encounter" +#~ " when your package is installed. If" +#~ " tests/ are outside the src/package " +#~ "directory, they aren't included in the" +#~ " package's wheel. This makes your " +#~ "package size slightly smaller, which " +#~ "places a smaller storage burden on " +#~ "PyPI, and makes them faster to " +#~ "fetch. - Read more about reasons " +#~ "to use the src/package layout " +#~ ":::{admonition} How Python discovers and " +#~ "prioritizes importing modules By default, " +#~ "Python adds a module in your " +#~ "current working directory to the front" +#~ " of the Python module search path." +#~ " This means that if you run " +#~ "your tests in your package's working " +#~ "directory, using a flat layout, " +#~ "/package/module.py, Python will discover " +#~ "package/module.py file before it discovers " +#~ "the installed package. However, if your" +#~ " package lives in a src/ directory" +#~ " structure src/package, then it won't " +#~ "be added to the Python path by " +#~ "default. This means that when you " +#~ "import your package, Python will be " +#~ "forced to search the active environment" +#~ " (which has your package installed). " +#~ "Note: Python versions 3.11 and above " +#~ "have a path setting that can be" +#~ " adjusted to ensure the priority is" +#~ " to use installed packages first " +#~ "(e.g., PYTHONSAFEPATH). ::: ### Don't " +#~ "include tests in your package wheel " +#~ "Writing tests for your package is " +#~ "important; however, we do not recommend" +#~ " including tests as part of your " +#~ "package wheel by default. However, not" +#~ " including tests in your package " +#~ "distribution will make it harder for " +#~ "people other than yourself to test " +#~ "whether your package runs properly on" +#~ " their system. If you have a " +#~ "small test suite (Python files + " +#~ "data), and think your users may " +#~ "want to run tests locally on their" +#~ " systems, you can include tests by" +#~ " moving the tests/ directory into the" +#~ " src/package directory (see example below)." +#~ " ```bash src/ package/ tests/ docs/" +#~ msgstr "" + diff --git a/locales/ja/LC_MESSAGES/tests.po b/locales/ja/LC_MESSAGES/tests.po index 400e2215..7d8ff916 100644 --- a/locales/ja/LC_MESSAGES/tests.po +++ b/locales/ja/LC_MESSAGES/tests.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -20,7 +20,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" #: ../../tests/code-cov.md:1 msgid "Code coverage for your Python package test suite" @@ -48,64 +48,70 @@ msgid "" msgstr "良い習慣は、テストスイートの間に、コードのすべての行が少なくとも一度は実行されるようにすることです。これはあなたを助けます:" #: ../../tests/code-cov.md:13 -msgid "Identify untested parts of your codebase." +#, fuzzy +msgid "" +"**Identify untested parts:** Parts of your codebase that are not covered " +"by tests." msgstr "コードベースのテストされていない部分を特定します。" -#: ../../tests/code-cov.md:14 -msgid "Catch bugs that might otherwise go unnoticed." +#: ../../tests/code-cov.md:15 +#, fuzzy +msgid "**Catch bugs:** Bugs that might otherwise go unnoticed." msgstr "他の方法では気づかれないかもしれないバグをキャッチします。" -#: ../../tests/code-cov.md:15 -msgid "Build confidence in your software's stability." +#: ../../tests/code-cov.md:16 +#, fuzzy +msgid "**Build confidence:** Confidence in your software's stability." msgstr "ソフトウェアの安定性に自信を持てます。" -#: ../../tests/code-cov.md:17 +#: ../../tests/code-cov.md:18 msgid "Limitations of code coverage" msgstr "コードカバレッジの限界" -#: ../../tests/code-cov.md:19 +#: ../../tests/code-cov.md:20 msgid "While high code coverage is valuable, it has its limits:" msgstr "高いコードカバレッジは価値がありますが、それには限界があります:" -#: ../../tests/code-cov.md:21 +#: ../../tests/code-cov.md:22 msgid "" "**Difficult-to-test code:** Some parts of your code might be challenging " "to test, either due to complexity or limited resources." msgstr "**テストしにくいコード:** コードの中には、複雑さや限られたリソースのために、テストが難しい部分があるかもしれません。" -#: ../../tests/code-cov.md:23 +#: ../../tests/code-cov.md:24 +#, fuzzy msgid "" -"**Missed edge cases:** Running all lines of code doesn’t guarantee that " +"**Missed edge cases:** Running all lines of code doesn't guarantee that " "edge cases are handled correctly." msgstr "**見逃されたエッジケース:** すべてのコードを実行しても、エッジケースが正しく処理される保証はありません。" -#: ../../tests/code-cov.md:26 +#: ../../tests/code-cov.md:27 msgid "" "Ultimately, you should focus on how your package will be used and ensure " "your tests cover those scenarios adequately." msgstr "最終的には、パッケージがどのように使用されるかに焦点を当て、テストがそのシナリオを十分にカバーするようにしなければなりません。" -#: ../../tests/code-cov.md:29 +#: ../../tests/code-cov.md:30 msgid "Tools for analyzing Python package code coverage" msgstr "Pythonパッケージのコードカバレッジを分析するツール" -#: ../../tests/code-cov.md:31 +#: ../../tests/code-cov.md:32 #, fuzzy msgid "" "Some common services for analyzing code coverage are " "[codecov.io](https://about.codecov.io/) and " "[coveralls.io](https://coveralls.io/). These projects are free for open " -"source tools and will provide dashboards that tell you how much of your " -"codebase is covered during your tests. We recommend setting up an account" -" (on either CodeCov or Coveralls) and using it to keep track of your code" -" coverage." +"source tools and provide dashboards that show how much of your codebase " +"is covered during your tests. We recommend setting up an account (on " +"either CodeCov or Coveralls) and using it to keep track of your code " +"coverage." msgstr "" "コードカバレッジを分析するための一般的なサービスには、 [codecov.io](https://codecov.io/) と " "[coveralls.io](https://coveralls.io/) があります。 " "これらのプロジェクトはオープンソースのツールで無料であり、テスト中にコードベースがどの程度カバーされているかを示すダッシュボードを提供してくれます。" " (CodeCovまたはCoverallsで) アカウントを設定し、コード・カバレッジを追跡するために使用することをお勧めします。" -#: ../../tests/code-cov.md:33 +#: ../../tests/code-cov.md:39 #, python-format msgid "" "Screenshot of the code cov service - showing test coverage for the " @@ -118,33 +124,35 @@ msgstr "" "この画像は、パッケージモジュールのリストと、関連する行数およびテスト対象行の割合を示しています。 " "画像の上部には、評価対象のブランチとリポジトリへのパスが表示されています。" -#: ../../tests/code-cov.md:38 +#: ../../tests/code-cov.md:44 +#, fuzzy msgid "" "The CodeCov platform is a useful tool if you wish to track code coverage " -"visually. Using it, you can not only get the same summary information " -"that you can get with the **pytest-cov** extension. You can also see what" -" lines are covered by your tests and which are not. Code coverage is " -"useful for evaluating unit tests and/or how much of your package code is " -"\"covered\". It, however, will not evaluate things like integration tests" -" and end-to-end workflows." +"visually. Using it, you can get the same summary information that you can" +" get with the **pytest-cov** extension. You can also see what lines are " +"covered by your tests and which are not. Code coverage is useful for " +"evaluating [unit tests](test-types.md#unit-tests) and/or how much of your" +" package code is \"covered\". It, however, will not evaluate things like " +"[integration tests](test-types.md#integration-tests) and [end-to-end " +"workflows](test-types.md)." msgstr "" "CodeCovプラットフォームは、コードカバレッジを視覚的に追跡したい場合に便利なツールです。これを使えば、 **pytest-cov** " "拡張機能で得られるのと同じサマリー情報を得られるだけではありません。また、テストの対象になっているラインとそうでないラインを確認することもできます。コードカバレッジは、単体テストの評価や、パッケージのコードがどれだけ" " \"カバー\" されているかを評価するのに役立ちます。しかし、統合テストやエンドツーエンドのワークフローなどは評価されません。" -#: ../../tests/code-cov.md:43 +#: ../../tests/code-cov.md:56 msgid "Typing & MyPy coverage" msgstr "型 & MyPyのカバレッジ" -#: ../../tests/code-cov.md:44 +#: ../../tests/code-cov.md:57 msgid "You can also create and upload typing reports to CodeCov." msgstr "また、型レポートを作成し、CodeCovにアップロードすることもできます。" -#: ../../tests/code-cov.md:47 +#: ../../tests/code-cov.md:60 msgid "Exporting Local Coverage Reports" msgstr "ローカルカバレッジレポートのエクスポート" -#: ../../tests/code-cov.md:49 +#: ../../tests/code-cov.md:62 msgid "" "In addition to using services like CodeCov or Coveralls, you can generate" " local coverage reports directly using the **coverage.py** tool. This can" @@ -155,60 +163,82 @@ msgstr "" "ツールを使って直接ローカルカバレッジレポートを作成することもできます。 " "これは、オフラインでの使用や文書化のためにMarkdownやHTML形式でレポートを作成したい場合に特に便利です。" -#: ../../tests/code-cov.md:51 +#: ../../tests/code-cov.md:67 msgid "To generate a coverage report in **Markdown** format, run:" msgstr "カバレッジレポートを **Markdown** 形式で作成するには、以下を実行します:" -#: ../../tests/code-cov.md:56 +#: ../../tests/code-cov.md:73 +#, fuzzy msgid "" "This command will produce a Markdown-formatted coverage summary that you " -"can easily include in project documentation or share with your team." +"can include in project documentation or share with your team." msgstr "このコマンドはMarkdown形式のカバレッジサマリーを作成し、プロジェクトのドキュメントに簡単に記載したり、チームと共有したりすることができます。" -#: ../../tests/code-cov.md:58 +#: ../../tests/code-cov.md:76 msgid "" "To generate an HTML report that provides a detailed, interactive view of " "which lines are covered, use:" msgstr "どの行がカバーされているか、詳細でインタラクティブなビューを提供するHTMLレポートを生成するには、以下を使用します:" -#: ../../tests/code-cov.md:64 +#: ../../tests/code-cov.md:83 +#, fuzzy msgid "" -"The generated HTML report will be saved in a directory named htmlcov by " -"default. Open the index.html file in your browser to explore your " +"The generated HTML report will be saved in a directory named `htmlcov` by" +" default. Open the `index.html` file in your browser to explore your " "coverage results." msgstr "生成されたHTMLレポートは、デフォルトでhtmlcovというディレクトリに保存されます。index.htmlファイルをブラウザで開き、カバレッジ結果をご覧ください。" -#: ../../tests/code-cov.md:66 +#: ../../tests/code-cov.md:87 msgid "" "These local reports are an excellent way to quickly review coverage " "without setting up an external service." msgstr "このようなローカルレポートは、外部サービスを立ち上げることなくカバレッジを素早く確認する優れた方法です。" -#: ../../tests/index.md:73 +#: ../../tests/code-cov.md:90 ../../tests/run-tests-nox.md:168 +#: ../../tests/run-tests.md:332 ../../tests/test-types.md:346 +#: ../../tests/write-tests.md:136 +#, fuzzy +msgid "Next steps" +msgstr "単体テスト" + +#: ../../tests/code-cov.md:92 +msgid "" +"Writing meaningful tests is the foundation of useful coverage. See [Write" +" tests](write-tests.md) and [Test types](test-types.md) to learn more " +"about developing better test suites. Learn how to run your tests both " +"[locally](run-tests.md) and in [continuous integration](tests-ci.md)." +msgstr "" + +#: ../../tests/index.md:70 msgid "Intro" msgstr "イントロ" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 msgid "Write tests" msgstr "テストを書く" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 msgid "Test types" msgstr "テストの種類" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 msgid "Run tests locally" msgstr "ローカルでテストを実行する" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 ../../tests/run-tests-nox.md:7 +#, fuzzy +msgid "Run tests with Nox" +msgstr "オンラインテストを実行する" + +#: ../../tests/index.md:70 msgid "Run tests online (using CI)" msgstr "オンラインでテストを実行する(CIを使用する)" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 msgid "Code coverage" msgstr "コードカバレッジ" -#: ../../tests/index.md:73 +#: ../../tests/index.md:70 msgid "Create & Run Tests" msgstr "テストの作成と実行" @@ -217,149 +247,188 @@ msgid "Tests and data for your Python package" msgstr "Pythonパッケージのテストとデータ" #: ../../tests/index.md:4 +#, fuzzy msgid "" -"Tests are an important part of your Python package because they provide a" -" set of checks that ensure that your package is functioning how you " -"expect it to." +"Adding tests to your package provides a set of checks that ensure that " +"its functioning how you expect it to." msgstr "" "テストは Python " "パッケージの重要な一部です。なぜなら、テストはパッケージが期待通りに動作しているかどうかを確認するための一連のチェック機能を提供するからです。" -#: ../../tests/index.md:8 +#: ../../tests/index.md:7 +#, fuzzy msgid "" -"In this section, you will learn more about the importance of writing " -"tests for your Python package and how you can set up infrastructure to " -"run your tests both locally and on GitHub." +"In this section, you will learn about the importance of writing tests for" +" your Python package, different [types of tests that you should consider" +"](test-types) and how you can set up infrastructure to run your tests " +"both [locally](run-tests) and [on GitHub](tests-ci)." msgstr "" "このセクションでは、Python パッケージのテストを書くことの重要性と、ローカルと GitHub " "の両方でテストを実行するためのインフラストラクチャの設定方法について学びます。" -#: ../../tests/index.md:20 +#: ../../tests/index.md:16 msgid "✨ Why write tests ✨" msgstr "✨テストを書く理由✨" -#: ../../tests/index.md:25 +#: ../../tests/index.md:21 +#, fuzzy msgid "" -"Learn more about the art of writing tests for your Python package. Learn " -"about why you should write tests and how they can help you and potential " -"contributors to your project." +"Learn about the importance of writing tests for your Python package and " +"how they help you and potential contributors." msgstr "" "Python パッケージのテストを書く技術についてもっと学びましょう。 " "なぜテストを書く必要があるのか、そしてテストがどのようにあなたやあなたのプロジェクトへの将来の貢献者の助けになるのかを学びましょう。" -#: ../../tests/index.md:32 +#: ../../tests/index.md:25 msgid "✨ Types of tests ✨" msgstr "✨テストの種類✨" -#: ../../tests/index.md:37 +#: ../../tests/index.md:30 msgid "" -"There are three general types of tests that you can write for your Python" -" package: unit tests, integration tests and end-to-end (or functional) " -"tests. Learn about all three." +"Get to know the three test types: unit, integration, and end-to-end " +"tests. Learn when and how to use each." msgstr "" -"Python パッケージで書くことのできるテストには、ユニットテスト、統合テスト、エンドツーエンドテスト (あるいは機能テスト) の 3 " -"種類があります。 この 3 つについて学びましょう。" -#: ../../tests/index.md:43 +#: ../../tests/index.md:34 msgid "✨ Run tests locally ✨" msgstr "✨ローカルでテストを実行する✨" +#: ../../tests/index.md:39 +msgid "" +"Learn about testing tools like pytest, nox, and tox to run tests across " +"different Python versions on your computer. And explore examples of using" +" Hatch with UV as a task runner to run tests across Python versions." +msgstr "" + +#: ../../tests/index.md:43 +#, fuzzy +msgid "✨ Run tests locally (using nox) ✨" +msgstr "✨オンラインでテストを実行する(CIを使用する)✨" + #: ../../tests/index.md:48 msgid "" -"If you expect your users to use your package across different versions of" -" Python, then using an automation tool such as nox to run your tests is " -"useful. Learn about the various tools that you can use to run your tests " -"across python versions here." +"Nox is a python powered task runner that can be used to run tests. Learn " +"how to use nox to run tests." msgstr "" -"もしユーザがあなたのパッケージを異なるバージョンの Python で使うことを想定しているなら、テストを実行するために nox " -"のような自動化ツールを使うと便利です。 Python " -"のバージョンにまたがってテストを実行するために使える様々なツールについては、こちらを参照してください。" -#: ../../tests/index.md:54 +#: ../../tests/index.md:51 msgid "✨ Run tests online (using CI) ✨" msgstr "✨オンラインでテストを実行する(CIを使用する)✨" -#: ../../tests/index.md:59 +#: ../../tests/index.md:56 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." +"Set up continuous integration with GitHub Actions to run tests across " +"Python versions and operating systems." msgstr "" -"GitHub Actionsのような継続的インテグレーションプラットフォームは、Python " -"のバージョンやオペレーティングシステムの違いを問わずテストを実行するのに便利です。 " -"継続的インテグレーションで実行するテストの設定については、こちらを参照してください。" -#: ../../tests/index.md:70 -msgid "Graphic showing the elements of the packaging process." -msgstr "パッケージング工程の要素を示すグラフィック。" +#: ../../tests/index.md:60 +#, fuzzy +msgid "✨ Code coverage ✨" +msgstr "コードカバレッジ" + +#: ../../tests/index.md:65 +msgid "" +"Measure how much of your package code runs during tests. Learn to " +"generate local reports and visualize coverage online." +msgstr "" -#: ../../tests/run-tests.md:6 -msgid "Run Python package tests" -msgstr "Pythonパッケージテストの実行" +#: ../../tests/run-tests.md:7 +#, fuzzy +msgid "Run tests for your Python package" +msgstr "Pythonパッケージのテストを書く" -#: ../../tests/run-tests.md:8 +#: ../../tests/run-tests.md:9 msgid "" -"Running your tests is important to ensure that your package is working as" -" expected. It's good practice to consider that tests will run on your " -"computer and your users' computers that may be running a different Python" -" version and operating systems. Think about the following when running " -"your tests:" +"Running your tests across different Python versions and operating systems" +" is critical to ensuring your package works for your users. Your users " +"may be running different versions of Python and operating systems than " +"you are." msgstr "" -"テストを実行することは、パッケージが期待通りに動作していることを確認するために重要です。 テストは、あなたのコンピュータと、Python " -"のバージョンやオペレーティングシステムが異なるユーザのコンピュータで実行されることを考慮するのがよい習慣です。 " -"テストを実行する際には、以下のことを考慮してください:" -#: ../../tests/run-tests.md:11 +#: ../../tests/run-tests.md:13 msgid "" -"Run your test suite in a matrix of environments that represent the Python" -" versions and operating systems your users are likely to have." -msgstr "テストスイートは、Python のバージョンとユーザーが使用する可能性のあるオペレーティングシステムを表す環境のマトリックスで実行します。" +"This page teaches you how to run tests locally in isolated environments " +"and across multiple Python versions. You'll learn about two main " +"automation tools: [**Hatch**](https://hatch.pypa.io/) and " +"[**Nox**](https://nox.thea.codes/en/stable/index.html). In the next " +"lesson, you will learn about running your tests online in [continuous " +"integration (CI)](tests-ci)." +msgstr "" -#: ../../tests/run-tests.md:12 +#: ../../tests/run-tests.md:20 +#, fuzzy +msgid "Why run tests across multiple environments?" +msgstr "隔離された環境でのテストの実行" + +#: ../../tests/run-tests.md:22 msgid "" -"Running your tests in an isolated environment provides confidence in the " -"tests and their reproducibility. This ensures that tests do not pass " -"randomly due to your computer's specific setup. For instance, you might " -"have unexpectedly installed dependencies on your local system that are " -"not declared in your package's dependency list. This oversight could lead" -" to issues when others try to install or run your package on their " -"computers." +"When you develop a package on your computer, it works in one specific " +"environment: your Python version, your operating system, and your " +"installed dependencies. Your users, however, will run your code in many " +"different environments. By running your tests across multiple Python " +"versions and operating systems, you catch compatibility issues before " +"users do." msgstr "" -"隔離された環境でテストを実行することで、テストとその再現性に自信を持つことができます。 " -"これにより、あなたのコンピュータの設定によってテストがランダムにパスすることがなくなります。 " -"たとえば、あなたのパッケージの依存関係リストで宣言されていない依存関係を、予期せずローカルシステムにインストールしてしまったかもしれません。 " -"このような見落としは、他の人があなたのパッケージを自分のコン ピュータにインストールしたり実行しようとしたときに、問題につながる可能性 " -"があります。" -#: ../../tests/run-tests.md:14 +#: ../../tests/run-tests.md:28 +msgid "" +"Additionally, running tests in isolated environments ensures that your " +"tests pass because of your code, not because of unexpected dependencies " +"installed on your computer. This gives you confidence that your package " +"will work when others install it." +msgstr "" + +#: ../../tests/run-tests.md:33 msgid "" "On this page, you will learn about the tools that you can use to both run" " tests in isolated environments and across Python versions." msgstr "このページでは、隔離された環境でテストを実行したり、Python のバージョンを越えてテストを実行したりするために使えるツールについて学びます。" -#: ../../tests/run-tests.md:19 +#: ../../tests/run-tests.md:37 +msgid "**Related pages:**" +msgstr "" + +#: ../../tests/run-tests.md:39 +msgid "[Write tests](write-tests.md) for best practices on writing test suites" +msgstr "" + +#: ../../tests/run-tests.md:41 +#, fuzzy +msgid "" +"[Test types](test-types.md) to understand unit, integration, and end-to-" +"end tests" +msgstr "ユニットテスト、統合テスト、エンドツーエンドテストの比較" + +#: ../../tests/run-tests.md:43 +msgid "[Run tests online with CI](tests-ci.md) for GitHub Actions setup" +msgstr "" + +#: ../../tests/run-tests.md:44 +msgid "[Code coverage](code-cov.md) to measure how much code your tests cover" +msgstr "" + +#: ../../tests/run-tests.md:48 #, fuzzy msgid "Tools to run your tests" msgstr "テストを実行するためのツール" -#: ../../tests/run-tests.md:21 +#: ../../tests/run-tests.md:50 +#, fuzzy msgid "" -"There are three categories of tools that will make is easier to setup and" +"There are three categories of tools that will make it easier to setup and" " run your tests in various environments:" msgstr "さまざまな環境でのテストのセットアップと実行を容易にするツールには、3つのカテゴリーがあります:" -#: ../../tests/run-tests.md:24 +#: ../../tests/run-tests.md:53 +#, fuzzy msgid "" -"A **test framework**, is a package that provides a particular syntax and " -"set of tools for _both writing and running your tests_. Some test " -"frameworks also have plugins that add additional features such as " -"evaluating how much of your code the tests cover. Below you will learn " -"about the **pytest** framework which is one of the most commonly used " -"Python testing frameworks in the scientific ecosystem. Testing frameworks" -" are essential but they only serve to run your tests. These frameworks " -"don't provide a way to easily run tests across Python versions without " -"the aid of additional automation tools." +"**Testing framework (pytest):** Provides the syntax and tools for writing" +" and running your tests. Learn more from the [pytest " +"documentation](https://docs.pytest.org/). Below you will learn about " +"pytest, the most commonly used testing framework in the scientific Python" +" ecosystem. Testing frameworks are essential for running tests, but they " +"don't provide an easy way to run tests across Python versions or in " +"isolated environments—that's where automation tools come in." msgstr "" "**テストフレームワーク** とは、テストを書いたり実行したりするための特定の構文やツールのセットを提供するパッケージのことです。 " "いくつかのテストフレームワークにはプラグインがあり、テストがカバーするコードの範囲を評価するなどの機能を追加することができます。 " @@ -367,112 +436,99 @@ msgstr "" "フレームワークについて学びます。 テストフレームワークは必要不可欠ですが、テストを実行するためだけのものです。 " "これらのフレームワークは、追加の自動化ツールの助けを借りずに Python のバージョンをまたいだテストを簡単に実行する方法は提供しません。" -#: ../../tests/run-tests.md:25 -msgid "" -"**Automation tools** allow you to automate running workflows such as " -"tests in specific ways using user-defined commands. For instance it's " -"useful to be able to run tests across different Python versions with a " -"single command. Tools such as " -"[**nox**](https://nox.thea.codes/en/stable/index.html) and " -"[**tox**](https://tox.wiki/en/latest/index.html) also allow you to run " -"tests across Python versions. However, it will be difficult to test your " -"build on different operating systems using only nox and tox - this is " -"where continuous integration (CI) comes into play." -msgstr "" -"**自動化ツール** を使うと、ユーザー定義のコマンドを使って、テストのようなワークフローを特定の方法で実行することを自動化できます。 " -"例えば、1つのコマンドで異なるPythonのバージョンにまたがってテストを実行できると便利です。 " -"[**nox**](https://nox.thea.codes/en/stable/index.html) や " -"[**tox**](https://tox.wiki/en/latest/index.html) " -"のようなツールも、Pythonのバージョンをまたいでテストを実行できます。 " -"しかし、noxとtoxだけを使って異なるオペレーティングシステムでビルドをテストするのは難しいでしょう - " -"ここで継続的インテグレーション(CI)の出番です。" - -#: ../../tests/run-tests.md:26 -msgid "" -"**Continuous Integration (CI):** is the last tool that you'll need to run" -" your tests. CI will not only allow you to replicate any automated builds" -" you create using nox or tox to run your package in different Python " -"environments. It will also allow you to run your tests on different " -"operating systems (Windows, Mac and Linux). [We discuss using CI to run " -"tests here](tests-ci)." -msgstr "" -"**継続的インテグレーション (CI):** は、テストを実行するために必要な最後のツールです。 CI は、nox や tox " -"を使って作成した自動ビルドを複製して、異なる Python 環境でパッケージを実行できるようにするだけではありません。 " -"また、異なるオペレーティングシステム（Windows、Mac、Linux）でテストを実行することもできます。 " -"[テストを実行するためにCIを使うことについては、ここで説明します](tests-ci) 。" +#: ../../tests/run-tests.md:61 +msgid "" +"**Automation tools (Nox, Tox, Hatch):** Allow you to run tests in " +"isolated environments and across multiple Python versions with a single " +"command. We focus on [**Hatch**](https://hatch.pypa.io/) and " +"[**Nox**](https://nox.thea.codes/) below. These tools create virtual " +"environments automatically and ensure your tests run consistently. " +"However, they typically only test on your local operating system." +msgstr "" -#: ../../tests/run-tests.md:28 -msgid "Table: Testing & Automation Tool" -msgstr "テーブル: テスト＆自動化ツール" +#: ../../tests/run-tests.md:69 +msgid "" +"**Continuous Integration (CI):** Runs your tests online across different " +"operating systems (Windows, Mac, and Linux) and Python versions. CI " +"integrates with platforms like GitHub Actions to automatically test every" +" pull request and code change." +msgstr "" -#: ../../tests/run-tests.md:35 -msgid "Features" -msgstr "機能" +#: ../../tests/run-tests.md:74 +msgid "[Learn about CI here](ci-cd)." +msgstr "" -#: ../../tests/run-tests.md:36 -msgid "Testing Framework (pytest)" +#: ../../tests/run-tests.md:76 +msgid "Quick comparison: what each tool does" +msgstr "" + +#: ../../tests/run-tests.md:78 +#, fuzzy +msgid "**Testing Framework (pytest):**" msgstr "テストフレームワーク (pytest)" -#: ../../tests/run-tests.md:37 -msgid "Test Runner (Tox)" -msgstr "テストランナー (Tox)" +#: ../../tests/run-tests.md:80 +msgid "Runs your tests locally in your current Python environment" +msgstr "" + +#: ../../tests/run-tests.md:81 +msgid "Provides the core syntax for writing tests (assertions, fixtures, etc.)" +msgstr "" + +#: ../../tests/run-tests.md:83 +msgid "Can be extended with plugins (like pytest-cov for coverage)" +msgstr "" -#: ../../tests/run-tests.md:38 -msgid "Automation Tools (Nox)" +#: ../../tests/run-tests.md:85 +#, fuzzy +msgid "**Automation Tools (Nox, Tox, Hatch):**" msgstr "自動化ツール（Nox）" -#: ../../tests/run-tests.md:39 -msgid "Continuous Integration (GitHub Actions)" -msgstr "継続的インテグレーション（GitHub Actions）" +#: ../../tests/run-tests.md:87 +#, fuzzy +msgid "Run tests locally across multiple Python versions" +msgstr "Pythonのバージョンにまたがってテストを実行する" -#: ../../tests/run-tests.md:40 -msgid "Run Tests Locally" -msgstr "ローカルでテストを実行する" +#: ../../tests/run-tests.md:88 +msgid "Create and manage isolated virtual environments automatically" +msgstr "" -#: ../../tests/run-tests.md:41 ../../tests/run-tests.md:42 -#: ../../tests/run-tests.md:43 ../../tests/run-tests.md:49 -#: ../../tests/run-tests.md:52 ../../tests/run-tests.md:53 -#: ../../tests/run-tests.md:54 ../../tests/run-tests.md:57 -#: ../../tests/run-tests.md:58 ../../tests/run-tests.md:59 -#: ../../tests/run-tests.md:64 ../../tests/run-tests.md:68 -#: ../../tests/run-tests.md:69 -msgid "" -msgstr "" - -#: ../../tests/run-tests.md:44 ../../tests/run-tests.md:46 -#: ../../tests/run-tests.md:47 ../../tests/run-tests.md:48 -#: ../../tests/run-tests.md:51 ../../tests/run-tests.md:56 -#: ../../tests/run-tests.md:61 ../../tests/run-tests.md:62 -#: ../../tests/run-tests.md:63 ../../tests/run-tests.md:66 -#: ../../tests/run-tests.md:67 -msgid "" -msgstr "" - -#: ../../tests/run-tests.md:45 -msgid "Run Tests Online" -msgstr "オンラインテストを実行する" +#: ../../tests/run-tests.md:89 +msgid "Can automate other tasks like building documentation" +msgstr "" -#: ../../tests/run-tests.md:50 -msgid "Run Tests Across Python Versions" -msgstr "Pythonのバージョンにまたがってテストを実行する" +#: ../../tests/run-tests.md:90 +msgid "Make it easy to reproduce test environments" +msgstr "" -#: ../../tests/run-tests.md:55 -msgid "Run Tests In Isolated Environments" -msgstr "隔離された環境でのテストの実行" +#: ../../tests/run-tests.md:92 +#, fuzzy +msgid "**Continuous Integration (GitHub Actions):**" +msgstr "継続的インテグレーション（GitHub Actions）" -#: ../../tests/run-tests.md:60 -msgid "Run Tests Across Operating Systems (Windows, MacOS, Linux)" +#: ../../tests/run-tests.md:94 +msgid "Runs tests online automatically for every pull request" +msgstr "" + +#: ../../tests/run-tests.md:95 +#, fuzzy +msgid "Tests across different operating systems (Windows, Mac, Linux)" msgstr "オペレーティングシステム（Windows、MacOS、Linux）にまたがるテストの実行" -#: ../../tests/run-tests.md:65 -msgid "Use for other automation tasks (e.g. building docs)" -msgstr "その他の自動化タスクに使用する（ドキュメントの作成など）" +#: ../../tests/run-tests.md:96 +#, fuzzy +msgid "Tests across multiple Python versions in parallel" +msgstr "Pythonのバージョンにまたがってテストを実行する" + +#: ../../tests/run-tests.md:97 +msgid "Can automate deployments, releases, and other workflows" +msgstr "" -#: ../../tests/run-tests.md:73 +#: ../../tests/run-tests.md:99 msgid "What testing framework / package should I use to run tests?" msgstr "テストを実行するには、どのテストフレームワーク/パッケージを使用すればよいですか？" -#: ../../tests/run-tests.md:75 +#: ../../tests/run-tests.md:101 msgid "" "We recommend using `Pytest` to build and run your package tests. Pytest " "is the most common testing tool used in the Python ecosystem." @@ -480,7 +536,7 @@ msgstr "" "パッケージテストのビルドと実行には `Pytest` を使うことを推奨します。 Pytest は Python " "のエコシステムで最もよく使われているテストツールです。" -#: ../../tests/run-tests.md:77 +#: ../../tests/run-tests.md:103 msgid "" "[The Pytest package](https://docs.pytest.org/en/latest/) also has a " "number of extensions that can be used to add functionality such as:" @@ -488,7 +544,7 @@ msgstr "" "[Pytestパッケージ](https://docs.pytest.org/en/latest/) " "には、以下のような機能を追加するために使用できる多くの拡張機能もあります：" -#: ../../tests/run-tests.md:80 +#: ../../tests/run-tests.md:106 #, fuzzy msgid "" "[pytest-cov](https://pytest-cov.readthedocs.io/en/latest/) allows you to " @@ -500,16 +556,15 @@ msgstr "" "を使うと、テスト中にパッケージのコードカバレッジを分析し、 [codecov](https://codecov.io/) " "にアップロードできるレポートを生成することができます。" -#: ../../tests/run-tests.md:82 ../../tests/run-tests.md:174 -#: ../../tests/test-types.md:14 ../../tests/tests-ci.md:7 +#: ../../tests/run-tests.md:108 ../../tests/tests-ci.md:7 msgid "Todo" msgstr "Todo" -#: ../../tests/run-tests.md:83 +#: ../../tests/run-tests.md:109 msgid "Learn more about code coverage here. (add link)" msgstr "コードカバレッジについてはこちらをご覧ください。 (リンクを追加)" -#: ../../tests/run-tests.md:87 +#: ../../tests/run-tests.md:113 msgid "" "Your editor or IDE may add additional convenience for running tests, " "setting breakpoints, and toggling the `–no-cov` flag. Check your editor's" @@ -518,19 +573,19 @@ msgstr "" "お使いのエディタや IDE には、テストを実行したり、ブレークポイントを設定したり、 `-no-cov` " "フラグを切り替えたりするための便利な機能が追加されているかもしれません。 詳しくはエディタのドキュメントを参照してください。" -#: ../../tests/run-tests.md:90 +#: ../../tests/run-tests.md:116 msgid "Run tests using pytest" msgstr "pytest を使ってテストを実行する" -#: ../../tests/run-tests.md:92 +#: ../../tests/run-tests.md:118 msgid "If you are using **pytest**, you can run your tests locally by calling:" msgstr "**pytest** を使用している場合、テストをローカルで実行することができます:" -#: ../../tests/run-tests.md:95 +#: ../../tests/run-tests.md:121 msgid "`pytest`" msgstr "`pytest`" -#: ../../tests/run-tests.md:97 +#: ../../tests/run-tests.md:123 msgid "" "Or if you want to run a specific test file - let's call this file " "\"`test_module.py`\" - you can run:" @@ -538,19 +593,20 @@ msgstr "" "また、特定のテストファイル - このファイルを \"`test_module.py`\" と呼ぶことにします - " "を実行したい場合は、次のようにします:" -#: ../../tests/run-tests.md:99 +#: ../../tests/run-tests.md:125 msgid "`pytest test_module.py`" msgstr "`pytest test_module.py`" -#: ../../tests/run-tests.md:101 +#: ../../tests/run-tests.md:127 +#, fuzzy msgid "" -"Learn more from the [get started docs](https://docs.pytest.org/en/7.1.x" -"/getting-started.html)." +"Learn more about pytest [here](https://docs.pytest.org/en/stable/getting-" +"started.html)." msgstr "" "詳しくは [ドキュメントスタートガイド](https://docs.pytest.org/en/7.1.x/getting-" "started.html) をご覧ください。" -#: ../../tests/run-tests.md:103 +#: ../../tests/run-tests.md:129 msgid "" "Running pytest on your computer is going to run your tests in whatever " "Python environment you currently have activated. This means that tests " @@ -560,29 +616,30 @@ msgstr "" "あなたのコンピュータで pytest を実行すると、現在有効になっている Python 環境でテストが実行されます。 " "つまり、テストは単一のバージョンのPythonで、ローカルで実行しているオペレーティングシステム上でのみ実行されます。" -#: ../../tests/run-tests.md:108 +#: ../../tests/run-tests.md:134 msgid "" "An automation tool can simplify the process of running tests in various " "Python environments." msgstr "自動化ツールは、様々な Python 環境でテストを実行するプロセスを単純化することができます。" -#: ../../tests/run-tests.md:111 +#: ../../tests/run-tests.md:137 msgid "Tests across operating systems" msgstr "オペレーティングシステムをまたいだテスト" -#: ../../tests/run-tests.md:112 +#: ../../tests/run-tests.md:138 +#, fuzzy msgid "" -"If you want to run your tests across different operating systems you can " -"[continuous integration. Learn more here](tests-ci)." +"If you want to run your tests on different operating systems you can use " +"continuous integration. [Learn more here](tests-ci)." msgstr "" "異なるオペレーティングシステム間でテストを実行したい場合は、 [継続的インテグレーション。 詳細はこちら](tests-ci) " "を使用することができます。" -#: ../../tests/run-tests.md:115 +#: ../../tests/run-tests.md:141 msgid "Tools to automate running your tests" msgstr "テストの実行を自動化するツール" -#: ../../tests/run-tests.md:117 +#: ../../tests/run-tests.md:143 msgid "" "To run tests on various Python versions or in various specific " "environments with a single command, you can use an automation tool such " @@ -594,24 +651,34 @@ msgstr "" "のような自動化ツールを使うことができます。 `nox` も `tox` も、隔離された仮想環境を作成することができます。 これにより、複数の環境や" " Python のバージョンをまたいだテストを簡単に実行することができます。" -#: ../../tests/run-tests.md:120 +#: ../../tests/run-tests.md:146 msgid "" -"We will focus on [Nox](https://nox.thea.codes/) in this guide. `nox` is a" -" Python-based automation tool that builds upon the features of both " -"`make` and `tox`. `nox` is designed to simplify and streamline testing " -"and development workflows. Everything that you do with `nox` can be " -"implemented using a Python-based interface." +"We will focus on Hatch on this page as Hatch is the default tool that we " +"use in our [tutorials](create-pure-python-package) and for our [Python " +"package template](https://github.com/pyOpenSci/pyos-package-template)." +msgstr "" + +#: ../../tests/run-tests.md:149 +#, fuzzy +msgid "" +"If you are not a hatch fan, then [Nox](https://nox.thea.codes/) is an " +"alternative tool that we cover in the next lesson. `nox` is a Python-" +"based automation tool that builds upon the features of both `make` and " +"`tox`. `nox` is designed to simplify and streamline testing and " +"development workflows. Everything that you do with `nox` can be " +"implemented using a Python-based interface. You will learn more about " +"using nox [here](run-tests-nox)." msgstr "" "このガイドでは、 [Nox](https://nox.thea.codes/) に焦点を当てます。 `nox` は Python " "ベースの自動化ツールで、 `make` と `tox` の機能をベースにしています。 `nox` " "はテストと開発のワークフローを簡素化し、効率化するように設計されています。 `nox` " "で行うことはすべて、Pythonベースのインターフェースを使って実装することができます。" -#: ../../tests/run-tests.md:122 +#: ../../tests/run-tests.md:151 msgid "Other automation tools you'll see in the wild" msgstr "その他の自動化ツール" -#: ../../tests/run-tests.md:125 +#: ../../tests/run-tests.md:154 msgid "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** is an " "automation tool that supports common steps such as building " @@ -620,104 +687,341 @@ msgstr "" "**[Tox](https://tox.wiki/en/latest/index.html#useful-links)** " "は自動化ツールで、ドキュメントのビルドや、Pythonの様々なバージョン間でのテストの実行など、一般的なステップをサポートしています。" -#: ../../tests/run-tests.md:127 -msgid "" -"**[Hatch](https://github.com/pypa/hatch)** is a modern end-to-end " -"packaging tool that works with the popular build backend called " -"hatchling. `hatch` offers a `tox`-like setup where you can run tests " -"locally using different Python versions. If you are using `hatch` to " -"support your packaging workflow, you may want to also use its testing " -"capabilities rather than using `nox`." -msgstr "" -"**[Hatch](https://github.com/pypa/hatch)** " -"は、hatchlingと呼ばれる人気のあるビルドバックエンドで動作する最新のエンドツーエンドパッケージングツールです。 `hatch` は " -"`tox` のようなセットアップを提供し、異なる Python バージョンを使ってローカルでテストを実行することができます。 " -"パッケージングのワークフローをサポートするために `hatch` を使っているのであれば、 `nox` を使うよりも `hatch` " -"のテスト機能を使った方が良いかもしれない。" - -#: ../../tests/run-tests.md:129 +#: ../../tests/run-tests.md:159 +#, fuzzy msgid "" -"[**make:**](https://www.gnu.org/software/make/manual/make.html) Some " -"developers use Make, which is a build automation tool, for running tests " -"due to its versatility; it's not tied to a specific language and can be " -"used to run various build processes. However, Make's unique syntax and " -"approach can make it more challenging to learn, particularly if you're " -"not already familiar with it. Make also won't manage environments for you" -" like **nox** will do." +"**[Make](https://www.gnu.org/software/make/manual/make.html)** is a build" +" automation tool that some developers use for running tests due to its " +"versatility. However, Make's unique syntax can be challenging to learn, " +"and it won't manage environments for you like Hatch and Nox do." msgstr "" "[**make:**](https://www.gnu.org/software/make/manual/make.html) " "ビルド自動化ツールであるMakeは汎用性が高いため、テストの実行に使う開発者もいます; " "特定の言語に縛られることなく、さまざまなビルドプロセスを実行するために使うことができます。しかし、Makeのユニークな構文とアプローチは、特にあなたがまだMakeに慣れていない場合、習得を難しくする可能性があります。Makeはまた、" " **nox** がやってくれるような環境管理もしてくれません。" -#: ../../tests/run-tests.md:136 -msgid "Run tests across Python versions with nox" -msgstr "noxでPythonのバージョンにまたがってテストを実行する" +#: ../../tests/run-tests.md:166 +#, fuzzy +msgid "Run tests with Hatch" +msgstr "pytest を使ってテストを実行する" -#: ../../tests/run-tests.md:138 -msgid "**Nox** is a great automation tool to learn because it:" +#: ../../tests/run-tests.md:168 +msgid "" +"**Hatch** is a modern Python packaging and environment manager that " +"integrates test running capabilities directly into your `pyproject.toml`." +" Unlike Nox (which uses a separate `noxfile.py`), Hatch keeps all your " +"project configuration in one place, making it ideal if you're already " +"using Hatch for packaging workflows." +msgstr "" + +#: ../../tests/run-tests.md:174 +msgid "Why Hatch for testing?" +msgstr "" + +#: ../../tests/run-tests.md:176 +msgid "Configuration lives in `pyproject.toml` alongside your project metadata" +msgstr "" + +#: ../../tests/run-tests.md:178 +msgid "Integrates seamlessly with Hatch's packaging and build workflows" +msgstr "" + +#: ../../tests/run-tests.md:179 +msgid "No separate Python file needed (unlike Nox)" +msgstr "" + +#: ../../tests/run-tests.md:180 +msgid "Easy to share standardized test environments across your team" +msgstr "" + +#: ../../tests/run-tests.md:182 +#, fuzzy +msgid "Setting up Hatch environments" +msgstr "テスト環境" + +#: ../../tests/run-tests.md:184 +msgid "" +"Hatch environments are defined in your `pyproject.toml`. Rather than " +"duplicating dependencies, use `dependency-groups` to reference your test " +"dependencies:" +msgstr "" + +#: ../../tests/run-tests.md:205 +msgid "" +"This approach keeps your test dependencies in one place and avoids " +"duplication. For a complete example, see our [packaging template " +"tutorial](https://www.pyopensci.org/tutorials/create-python-package.html)" +" which shows a full `pyproject.toml` configuration." +msgstr "" + +#: ../../tests/run-tests.md:210 +msgid "Running tests with Hatch" +msgstr "" + +#: ../../tests/run-tests.md:212 +msgid "" +"Once you've defined your test environment, you can run tests with simple " +"commands:" +msgstr "" + +#: ../../tests/run-tests.md:215 +#, fuzzy +msgid "**List available environments:**" +msgstr "テスト環境" + +#: ../../tests/run-tests.md:221 +msgid "**Run pytest in the test environment:**" +msgstr "" + +#: ../../tests/run-tests.md:228 +#, fuzzy +msgid "Testing across Python versions" +msgstr "Pythonのバージョンにまたがってテストを実行する" + +#: ../../tests/run-tests.md:230 +msgid "" +"To test across multiple Python versions, define a matrix in your " +"`pyproject.toml`:" +msgstr "" + +#: ../../tests/run-tests.md:249 +msgid "Then run all versions with a single command:" +msgstr "" + +#: ../../tests/run-tests.md:255 +msgid "" +"Hatch will automatically run your tests on Python 3.10, 3.11, and 3.12. " +"If you only want to test a specific Python version:" +msgstr "" + +#: ../../tests/run-tests.md:262 +msgid "Using Hatch in GitHub Actions" +msgstr "" + +#: ../../tests/run-tests.md:264 +msgid "Hatch integrates well with CI/CD. Here's a minimal GitHub Actions setup:" +msgstr "" + +#: ../../tests/run-tests.md:288 +msgid "" +"Since all of your test dependencies are declared in the `dependency-" +"group` table of your `pyproject.toml`, your CI environment is " +"reproducible and consistent with the environments that you are using for " +"local testing." +msgstr "" + +#: ../../tests/run-tests.md:292 +msgid "Nox vs Hatch: choosing the right tool" +msgstr "" + +#: ../../tests/run-tests.md:294 +msgid "" +"Both Hatch and Nox are excellent automation tools / task runners for " +"running tests across Python versions. Here's how they compare to help you" +" decide which fits your workflow:" +msgstr "" + +#: ../../tests/run-tests.md:298 +msgid "Hatch" +msgstr "" + +#: ../../tests/run-tests.md:300 +msgid "" +"**Configuration:** Hatch uses a `declarative` configuration approach. You" +" tell it what goes into an environment and that empowers Hatch to create " +"the environment for you. All configuration settings live in your " +"`pyproject.toml` alongside your project metadata" +msgstr "" + +#: ../../tests/run-tests.md:302 +msgid "" +"**Integration:** Hatch is package management tool that also has an " +"integrated automation / task runner. Using Hatch means you are using the " +"same tool for all of your packaging and automation needs." +msgstr "" + +#: ../../tests/run-tests.md:303 +msgid "" +"**Learning curve:** Easier if you prefer declarative configuration over a" +" code based workflow" +msgstr "" + +#: ../../tests/run-tests.md:304 +msgid "" +"**packaging scope** Hatch is better for simpler workflows that focus on " +"testing and packaging. If you have more complex builds or are creating a " +"non pure python package you might prefer Nox. The scientific Python " +"development guide has more details on this." +msgstr "" + +#: ../../tests/run-tests.md:305 +msgid "" +"**Best for:** Teams using Hatch for packaging, or those who want " +"standardized configuration in one place" +msgstr "" + +#: ../../tests/run-tests.md:308 +msgid "Nox" +msgstr "" + +#: ../../tests/run-tests.md:310 +msgid "**Configuration:** Python-driven via `noxfile.py` for maximum flexibility" +msgstr "" + +#: ../../tests/run-tests.md:311 +msgid "**Customization:** Great for complex workflows that need custom logic" +msgstr "" + +#: ../../tests/run-tests.md:312 +msgid "" +"**Learning curve:** Easier if you already know Python and want flexible " +"session control" +msgstr "" + +#: ../../tests/run-tests.md:314 +msgid "" +"**Best for:** Complex automation needs, building docs alongside tests, or" +" workflows that don't fit the standard model" +msgstr "" + +#: ../../tests/run-tests.md:317 +msgid "What we recommend" +msgstr "" + +#: ../../tests/run-tests.md:319 +msgid "" +"**If you're using Hatch for packaging:** Use Hatch for testing too. You " +"get everything in one place and one consistent tool." +msgstr "" + +#: ../../tests/run-tests.md:322 +msgid "" +"**If you need maximum flexibility:** Choose Nox. Its Python-driven " +"approach lets you implement almost any workflow." +msgstr "" + +#: ../../tests/run-tests.md:325 +msgid "" +"**If you're just starting out:** Start with Hatch. It's simpler to set up" +" and understand, and you can always switch to Nox later if you need to." +msgstr "" + +#: ../../tests/run-tests.md:328 +msgid "" +"**Both tools are good choices.** For a more comprehensive guide to using" +" Nox, see [Run tests with Nox](run-tests-nox.md) and the [Scientific " +"Python testing guide](https://scientific-python.org/tools/testing)." +msgstr "" + +#: ../../tests/run-tests.md:334 +msgid "" +"Now that you understand how to run tests locally across Python versions, " +"you can learn about [running tests automatically in GitHub Actions with " +"continuous integration](tests-ci). You can also review [test types](test-" +"types) and [write tests](write-tests) for your package." +msgstr "" + +#: ../../tests/run-tests-nox.md:9 +msgid "" +"**Nox** is a Python-based automation tool for running tests across " +"multiple Python versions and managing isolated test environments. If you " +"prefer Python-driven configuration over TOML, or need complex automation " +"workflows, Nox is an excellent choice." +msgstr "" + +#: ../../tests/run-tests-nox.md:14 +msgid "" +"For more information about Nox, see the [official Nox " +"documentation](https://nox.thea.codes/) or the [Scientific Python guide " +"to testing](https://scientific-python.org/tools/testing)." +msgstr "" + +#: ../../tests/run-tests-nox.md:18 +msgid "Why Nox?" +msgstr "" + +#: ../../tests/run-tests-nox.md:20 +#, fuzzy +msgid "**Nox** is a great automation tool because it:" msgstr "**Nox** は素晴らしい自動化ツールです:" -#: ../../tests/run-tests.md:140 -msgid "Is Python-based making it accessible if you already know Python and" +#: ../../tests/run-tests-nox.md:22 +#, fuzzy +msgid "Is Python-based, making it accessible if you already know Python" msgstr "Pythonベースですので、Pythonをすでに知っていれば利用しやすいです。" -#: ../../tests/run-tests.md:141 -msgid "Will create isolated environments to run workflows." +#: ../../tests/run-tests-nox.md:23 +#, fuzzy +msgid "Will create isolated environments to run workflows" msgstr "ワークフローを実行するための隔離された環境を構築します。" -#: ../../tests/run-tests.md:143 +#: ../../tests/run-tests-nox.md:24 +msgid "Supports complex, custom automation beyond standard testing" +msgstr "" + +#: ../../tests/run-tests-nox.md:25 +msgid "Is flexible and powerful for intricate build and test scenarios" +msgstr "" + +#: ../../tests/run-tests-nox.md:27 +#, fuzzy msgid "" "`nox` simplifies creating and managing testing environments. With `nox`, " -"you can set up virtual environments, and run tests across Python versions" -" using the environment manager of your choice with a single command." +"you can set up virtual environments and run tests across Python versions " +"using the environment manager of your choice with a single command." msgstr "" "`nox` はテスト環境の作成と管理を簡単にします。 `nox` を使うと、仮想環境をセットアップし、好きな環境マネージャを使って Python " "のバージョンをまたいだテストをコマンド一つで実行することができます。" -#: ../../tests/run-tests.md:148 -msgid "Nox Installations" +#: ../../tests/run-tests-nox.md:31 +msgid "Set up Nox" +msgstr "" + +#: ../../tests/run-tests-nox.md:33 +#, fuzzy +msgid "" +"To get started with Nox, you create a `noxfile.py` file at the root of " +"your project directory. You then define commands using Python functions." +msgstr "" +"noxを使い始めるには、プロジェクトディレクトリのルートに `noxfile.py` ファイルを作成します。 " +"そして、Pythonの関数を使ってコマンドを定義します。 以下にその例をいくつか挙ます。" + +#: ../../tests/run-tests-nox.md:37 +#, fuzzy +msgid "Nox installations" msgstr "Noxのインストール" -#: ../../tests/run-tests.md:150 +#: ../../tests/run-tests-nox.md:39 +#, fuzzy msgid "" -"When you install and use nox to run tests across different Python " -"versions, nox will create and manage individual `venv` environments for " -"each Python version that you specify in the nox function." +"When you install and use Nox to run tests across different Python " +"versions, Nox will create and manage individual `venv` environments for " +"each Python version that you specify in the Nox function. Nox will manage" +" each environment on its own." msgstr "" "異なる Python バージョン間でテストを実行するために nox をインストールして使用する場合、nox は nox 関数で指定した " "Python バージョンごとに個別の `venv` 環境を作成して管理します。" -#: ../../tests/run-tests.md:152 -msgid "Nox will manage each environment on its own." -msgstr "Noxはそれぞれの環境を独自に管理します。" - -#: ../../tests/run-tests.md:154 +#: ../../tests/run-tests-nox.md:45 +#, fuzzy msgid "" "Nox can also be used for other development tasks such as building " "documentation, creating your package distribution, and testing " -"installations across both PyPI related environments (e.g. venv, " -"virtualenv) and `conda` (e.g. `conda-forge`)." +"installations across both PyPI-related environments (e.g., venv, " +"virtualenv) and `conda` (e.g., `conda-forge`)." msgstr "" "nox は、ドキュメントのビルド、パッケージ配布の作成、PyPI 関連の環境 (venv や virtualenv など) と `conda` " "(conda-forge` など) の両方にわたるインストールのテストなど、その他の開発作業にも使用できます。" -#: ../../tests/run-tests.md:158 -msgid "" -"To get started with nox, you create a `noxfile.py` file at the root of " -"your project directory. You then define commands using Python functions. " -"Some examples of that are below." -msgstr "" -"noxを使い始めるには、プロジェクトディレクトリのルートに `noxfile.py` ファイルを作成します。 " -"そして、Pythonの関数を使ってコマンドを定義します。 以下にその例をいくつか挙ます。" - -#: ../../tests/run-tests.md:162 -msgid "Test Environments" +#: ../../tests/run-tests-nox.md:50 +#, fuzzy +msgid "Test environments" msgstr "テスト環境" -#: ../../tests/run-tests.md:164 +#: ../../tests/run-tests-nox.md:52 +#, fuzzy msgid "" -"By default, `nox` uses the Python built in `venv` environment manager. A " +"By default, `nox` uses Python's built-in `venv` environment manager. A " "virtual environment (`venv`) is a self-contained Python environment that " "allows you to isolate and manage dependencies for different Python " "projects. It helps ensure that project-specific libraries and packages do" @@ -728,92 +1032,83 @@ msgstr "" " Python 環境で、異なる Python プロジェクトの依存関係を分離して管理することができます。 " "プロジェクト固有のライブラリやパッケージが互いに干渉しないようにし、クリーンで整理された開発環境を促進します。" -#: ../../tests/run-tests.md:166 -msgid "" -"An example of using nox to run tests in `venv` environments for Python " -"versions 3.9, 3.10, 3.11 and 3.12 is below." -msgstr "noxを使ってPythonバージョン3.9、3.10、3.11、3.12の `venv` 環境でテストを実行する例を以下に示します。" - -#: ../../tests/run-tests.md:169 -msgid "" -"Note that for the code below to work, you need to have all 4 versions of " -"Python installed on your computer for `nox` to find." -msgstr "" -"以下のコードが動作するためには、 `nox` " -"が見つけることができる4つのバージョンのPythonがコンピュータにインストールされている必要があることに注意してください。" - -#: ../../tests/run-tests.md:172 +#: ../../tests/run-tests-nox.md:58 msgid "Nox with venv environments" msgstr "venv環境のnox" -#: ../../tests/run-tests.md:175 -msgid "" -"TODO: add some tests above and show what the output would look like in " -"the examples below..." -msgstr "TODO: 上記のテストをいくつか追加し、以下の例で出力がどのようになるかを示す..." - -#: ../../tests/run-tests.md:178 +#: ../../tests/run-tests-nox.md:60 +#, fuzzy msgid "" -"Below is an example of setting up nox to run tests using `venv` which is " -"the built in environment manager that comes with base Python." +"Below is an example of setting up Nox to run tests using `venv`, which is" +" the built-in environment manager that comes with base Python." msgstr "以下は、Pythonに組み込まれている環境マネージャーである `venv` を使ってテストを実行するようにnoxをセットアップする例です。" -#: ../../tests/run-tests.md:180 +#: ../../tests/run-tests-nox.md:63 +#, fuzzy msgid "" -"Note that the example below assumes that you have [setup your " -"`pyproject.toml` to declare test dependencies in a way that pip can " -"understand](../package-structure-code/declare-dependencies.md). An " -"example of that setup is below." +"Note that the example below assumes that you have setup your " +"`pyproject.toml` to declare test dependencies using `project.optional-" +"dependencies`:" msgstr "" "以下の例では、 [pipが理解できる方法でテストの依存関係を宣言するように`pyproject.toml`をセットアップする" "](../package-structure-code/declare-dependencies.md) " "ことを前提としていることに注意してください。 そのセットアップの例を以下に示します。" -#: ../../tests/run-tests.md:201 +#: ../../tests/run-tests-nox.md:83 +#, fuzzy msgid "" -"If you have the above setup, then you can use " -"`session.install(\".[tests]\")` to install your test dependencies. Notice" -" that below one single nox session allows you to run your tests on 4 " -"different Python environments (Python 3.9, 3.10, 3.11, and 3.12)." +"With this setup, you can use `session.install(\".[tests]\")` to install " +"your test dependencies. Notice that below one single Nox session allows " +"you to run your tests on 4 different Python environments (Python 3.9, " +"3.10, 3.11, and 3.12)." msgstr "" "上記の設定ができていれば、 `session.install(\".[tests]\")` " "を使ってテストの依存関係をインストールすることができます。 以下のように、1つのnoxセッションで4つの異なるPython環境（Python " "3.9、3.10、3.11、3.12）でテストを実行できることに注意してください。" -#: ../../tests/run-tests.md:222 +#: ../../tests/run-tests-nox.md:89 +msgid "" +"For this to run you will need to have python3.9, python3.10, python3.11, " +"and python3.12 installed on your computer. Otherwise nox will skip " +"running tests for whatever versions are missing." +msgstr "" + +#: ../../tests/run-tests-nox.md:107 +#, fuzzy msgid "" -"Above you create a nox session in the form of a function with a " +"Above you create a Nox session in the form of a function with a " "`@nox.session` decorator. Notice that within the decorator you declare " -"the versions of python that you wish to run." +"the versions of Python that you wish to run." msgstr "" "上の例では、 `@nox.session` デコレーターを使って関数の形で nox セッションを作成しています。 デコレータの中で、実行したい " "python のバージョンを宣言していることに注意してください。" -#: ../../tests/run-tests.md:226 +#: ../../tests/run-tests-nox.md:111 +#, fuzzy msgid "" -"To run the above you'd execute the following command, specifying which " +"To run the above, you'd execute the following command, specifying which " "session with `--session` (sometimes shortened to `-s`). Your function " -"above is called test, therefore the session name is test." +"above is called `test`, therefore the session name is `test`:" msgstr "" "上記を実行するには、 `--session` （ `-s` " "と短縮されることもある）でセッションを指定し、以下のコマンドを実行します。上記の関数はtestという名前なので、セッション名はtestです。" -#: ../../tests/run-tests.md:234 +#: ../../tests/run-tests-nox.md:119 msgid "Nox with conda / mamba" msgstr "conda / mamba による nox" -#: ../../tests/run-tests.md:236 +#: ../../tests/run-tests-nox.md:121 +#, fuzzy msgid "" -"Below is an example for setting up nox to use mamba (or conda) for your " -"environment manager. Note that unlike venv, conda can automatically " -"install the various versions of Python that you need. You won't need to " -"install all four Python versions if you use conda/mamba, like you do with" -" `venv`." +"Below is an example for setting up Nox to use mamba (or conda) for your " +"environment manager. Unlike venv, conda can automatically install the " +"various versions of Python that you need. You won't need to install all " +"four Python versions if you use conda/mamba, like you do with `venv`." msgstr "" "以下は、noxが環境マネージャーにmamba（またはconda）を使うように設定する例です。venvと違って、condaは必要なPythonの様々なバージョンを自動的にインストールできることに注意してください。conda/mambaを使う場合は、" " `venv` のように4つのPythonバージョンをインストールする必要はありません。" -#: ../../tests/run-tests.md:242 +#: ../../tests/run-tests-nox.md:127 msgid "" "For `conda` to work with `nox`, you will need to ensure that either " "`conda` or `mamba` is installed on your computer." @@ -821,16 +1116,50 @@ msgstr "" "`nox` で `conda` を動作させるには、コンピュータに `conda` か `mamba` " "のどちらかがインストールされていることを確認する必要があります。" -#: ../../tests/run-tests.md:264 +#: ../../tests/run-tests-nox.md:150 msgid "To run the above session you'd use:" msgstr "上記のセッションを実行するには、次のようにします:" +#: ../../tests/run-tests-nox.md:156 +msgid "Hatch vs Nox" +msgstr "" + +#: ../../tests/run-tests-nox.md:158 +msgid "" +"If you're trying to decide between Hatch and Nox, see the [comparison and" +" recommendations on the main testing page](run-tests.md)." +msgstr "" + +#: ../../tests/run-tests-nox.md:161 +msgid "In summary" +msgstr "" + +#: ../../tests/run-tests-nox.md:163 +msgid "" +"**Choose Hatch** if you're already using Hatch for packaging and want " +"everything in one place" +msgstr "" + +#: ../../tests/run-tests-nox.md:165 +msgid "" +"**Choose Nox** if you need maximum flexibility, prefer Python-driven " +"configuration, or need complex automation workflows" +msgstr "" + +#: ../../tests/run-tests-nox.md:170 +msgid "" +"Now that you understand how to run tests locally with Nox, you can learn " +"about [running tests automatically with continuous integration](tests-ci)" +" or [running tests with Hatch](run-tests.md)." +msgstr "" + #: ../../tests/test-types.md:1 msgid "Test Types for Python packages" msgstr "Pythonパッケージのテストタイプ" #: ../../tests/test-types.md:3 -msgid "Three types of tests: Unit, Integration & Functional Tests" +#, fuzzy +msgid "Three types of tests: unit, integration, and functional tests" msgstr "3種類のテスト: 単体テスト、統合テスト、機能テスト" #: ../../tests/test-types.md:5 @@ -839,37 +1168,27 @@ msgid "" "creating your test suite:" msgstr "テストスイートを作成する際に考慮したいテストには、さまざまなタイプがあります:" -#: ../../tests/test-types.md:8 +#: ../../tests/test-types.md:8 ../../tests/test-types.md:15 msgid "Unit tests" msgstr "単体テスト" -#: ../../tests/test-types.md:9 -msgid "Integration" -msgstr "統合" +#: ../../tests/test-types.md:9 ../../tests/test-types.md:93 +msgid "Integration tests" +msgstr "統合テスト" #: ../../tests/test-types.md:10 -msgid "End-to-end (also known as Functional) tests" +#, fuzzy +msgid "End-to-end (also known as functional) tests" msgstr "エンドツーエンド(機能テストとも呼ばれる)テスト" #: ../../tests/test-types.md:12 +#, fuzzy msgid "" "Each type of test has a different purpose. Here, you will learn about all" -" three types of tests." +" three types of tests by working through simple examples." msgstr "それぞれのテストには異なる目的があります。 ここでは、3種類のテストすべてについて学びます。" -#: ../../tests/test-types.md:15 -msgid "" -"I think this page would be stronger if we did have some examples from our" -" package here: https://github.com/pyOpenSci/pyosPackage" -msgstr "" -"私たちのパッケージからの例があれば、このページはもっと強くなると思います: " -"https://github.com/pyOpenSci/pyosPackage " - -#: ../../tests/test-types.md:20 -msgid "Unit Tests" -msgstr "単体テスト" - -#: ../../tests/test-types.md:22 +#: ../../tests/test-types.md:17 msgid "" "A unit test involves testing individual components or units of code in " "isolation to ensure that they work correctly. The goal of unit testing is" @@ -877,49 +1196,61 @@ msgid "" "method level, performs its intended task correctly." msgstr "単体テストは、個々のコンポーネントやコードの単位を分離してテストし、それらが正しく動作することを確認するものです。単体テストの目的は、ソフトウェアの各部分、通常は関数やメソッドのレベルが、意図したタスクを正しく実行することを検証することです。" -#: ../../tests/test-types.md:24 +#: ../../tests/test-types.md:22 +#, fuzzy msgid "" "Unit tests can be compared to examining each piece of your puzzle to " -"ensure parts of it are not broken. If all of the pieces of your puzzle " -"don’t fit together, you will never complete it. Similarly, when working " -"with code, tests ensure that each function, attribute, class, method " -"works properly when isolated." +"ensure parts or subsections of it are not broken. If all of the pieces of" +" that section of your puzzle don't fit together, you will never complete " +"it. Similarly, when working with code, tests ensure that each function, " +"attribute, class, and method works properly when isolated." msgstr "単体テストは、パズルの各パーツが壊れていないかどうかを調べることに例えることができます。パズルのピースがすべて合わなければ、完成することはありません。同様に、コードを扱う場合、テストは各関数、プロパティ、クラス、メソッドが分離されたときに正しく機能することを保証します。" -#: ../../tests/test-types.md:26 +#: ../../tests/test-types.md:28 +#, fuzzy msgid "" -"**Unit test example:** Pretend that you have a function that converts a " -"temperature value from Celsius to Fahrenheit. A test for that function " -"might ensure that when provided with a value in Celsius, the function " -"returns the correct value in degrees Fahrenheit. That function is a unit " -"test. It checks a single unit (function) in your code." +"**Unit test example:** Suppose you have a function that adds two numbers " +"together. A unit test for that function ensures that when provided with " +"two numbers, it returns the correct sum. This is a unit test because it " +"checks a single unit (function) in isolation." msgstr "" "**ユニットテスト例:** " "温度値を摂氏から華氏に変換する関数があるとします。その関数のテストは、摂氏の値が提供されたとき、その関数が正しい華氏の値を返すことを保証するかもしれません。この関数はユニットテストです。これは、コード内の1つのユニット(関数)をチェックします。" -#: ../../tests/test-types.md:44 +#: ../../tests/test-types.md:54 msgid "" "Example unit test for the above function. You'd run this test using the " "`pytest` command in your **tests/** directory." msgstr "上記の関数のユニットテスト例。このテストは、 **tests/** ディレクトリの `pytest` コマンドを使って実行します。" -#: ../../tests/test-types.md:65 ../../tests/test-types.md:115 +#: ../../tests/test-types.md:76 +msgid "" +"Notice that the tests above don't just test one case where numbers are " +"added together. Instead, they test multiple scenarios: adding positive " +"numbers, adding a negative number, and adding zero. This helps ensure " +"that the `add_numbers` function behaves correctly in different situations" +" and is the beginning of thinking about programming defensively." +msgstr "" + +#: ../../tests/test-types.md:83 +msgid "" +"You can run this test from your terminal using `pytest " +"tests/test_math_utils.py`." +msgstr "" + +#: ../../tests/test-types.md:86 ../../tests/test-types.md:215 msgid "" "image of puzzle pieces that all fit together nicely. The puzzle pieces " "are colorful - purple, green and teal." msgstr "パズルのピースがうまく組み合わさったような画像です。パズルのピースは紫色、緑色、鴨の羽色とカラフルです。" -#: ../../tests/test-types.md:69 +#: ../../tests/test-types.md:90 msgid "" "Your unit tests should ensure each part of your code works as expected on" " its own." msgstr "ユニットテストでは、コードの各部分がそれ自体で期待通りに動作することを確認する必要があります。" -#: ../../tests/test-types.md:72 -msgid "Integration tests" -msgstr "統合テスト" - -#: ../../tests/test-types.md:74 +#: ../../tests/test-types.md:95 msgid "" "Integration tests involve testing how parts of your package work together" " or integrate. Integration tests can be compared to connecting a bunch of" @@ -927,23 +1258,34 @@ msgid "" "on how different pieces of your code fit and work together." msgstr "統合テストでは、パッケージの各パーツがどのように連動するか、あるいは統合されるかをテストします。統合テストは、パズルのピースをつなげて全体像を作るようなものです。統合テストは、コードのさまざまな部分がどのように適合し、連携して動作するかに焦点を当てます。" -#: ../../tests/test-types.md:76 +#: ../../tests/test-types.md:100 msgid "" -"For example, if you had a series of steps that collected temperature data" -" in a spreadsheet, converted it from degrees celsius to Fahrenheit and " -"then provided an average temperature for a particular time period. An " -"integration test would ensure that all parts of that workflow behaved as " -"expected." -msgstr "例えば、スプレッドシートに温度データを収集し、摂氏から華氏に変換し、特定の期間の平均温度を提供する一連のステップがあったとします。統合テストは、そのワークフローのすべての部分が期待通りに動作することを保証します。" +"For example, suppose you have functions that convert temperatures and " +"calculate statistics. An integration test would ensure that these " +"functions work together correctly in a workflow where you convert " +"temperatures and then analyze them." +msgstr "" + +#: ../../tests/test-types.md:178 +msgid "" +"Here's an integration test that checks how the conversion and statistics " +"functions work together:" +msgstr "" -#: ../../tests/test-types.md:107 +#: ../../tests/test-types.md:204 +msgid "" +"This integration test verifies that the conversion and averaging " +"functions work together as expected in a real workflow." +msgstr "" + +#: ../../tests/test-types.md:207 msgid "" "image of two puzzle pieces with some missing parts. The puzzle pieces are" " purple teal yellow and blue. The shapes of each piece don’t fit " "together." msgstr "パズルのピースが2つあり、一部欠けている画像です。パズルのピースは紫・鴨の羽色・黄色・青色。 それぞれのピースの形が合いません。" -#: ../../tests/test-types.md:112 +#: ../../tests/test-types.md:212 msgid "" "If puzzle pieces have missing ends, they can’t work together with other " "elements in the puzzle. The same is true with individual functions, " @@ -951,92 +1293,220 @@ msgid "" "individually and together to perform certain sets of tasks." msgstr "パズルのピースの両端が欠けていると、パズルの他の要素と連動することができません。ソフトウェアの個々の関数、メソッド、クラスについても同様です。コードは、ある一連のタスクを実行するために、個々に、そして一緒に働く必要があります。" -#: ../../tests/test-types.md:120 +#: ../../tests/test-types.md:220 msgid "" "Your integration tests should ensure that parts of your code that are " "expected to work together, do so as expected." msgstr "統合テストは、コードの一部が連携して動作することが期待されており、期待通りに動作することを保証するものでなければなりません。" -#: ../../tests/test-types.md:124 +#: ../../tests/test-types.md:224 msgid "End-to-end (functional) tests" msgstr "エンドツーエンド(機能)テスト" -#: ../../tests/test-types.md:126 +#: ../../tests/test-types.md:226 +#, fuzzy msgid "" "End-to-end tests (also referred to as functional tests) in Python are " "like comprehensive checklists for your software. They simulate real user " -"end-to-end workflows to make sure the code base supports real life " -"applications and use-cases from start to finish. These tests help catch " -"issues that might not show up in smaller tests and ensure your entire " -"application or program behaves correctly. Think of them as a way to give " -"your software a final check before it's put into action, making sure it's" -" ready to deliver a smooth experience to its users." +"workflows to make sure the code base supports real-life applications and " +"use-cases from start to finish. These tests help catch issues that might " +"not show up in smaller tests and ensure your entire application behaves " +"correctly. Think of them as a way to give your software a final check " +"before it's put into action, making sure it's ready to deliver a smooth " +"user experience." msgstr "" "Python " "におけるエンドツーエンドのテスト（機能テストとも呼ばれる）は、ソフトウェアの包括的なチェックリストのようなものです。実際のユーザーのエンドツーエンドのワークフローをシミュレートし、コードベースが実際のアプリケーションやユースケースを最初から最後までサポートすることを確認します。これらのテストは、小規模なテストでは表示されないかもしれない問題をキャッチし、アプリケーションやプログラム全体が正しく動作することを確認するのに役立ちます。ソフトウェアを実用化する前に最終チェックを行い、ユーザーにスムーズなエクスペリエンスを提供する準備ができていることを確認する方法だと考えてください。" -#: ../../tests/test-types.md:128 +#: ../../tests/test-types.md:235 msgid "Image of a completed puzzle showing a daisy" msgstr "デイジーを描いたパズルの完成イメージ" -#: ../../tests/test-types.md:133 +#: ../../tests/test-types.md:240 +#, fuzzy msgid "" -"End-to-end or functional tests represent an entire workflow that you " -"expect your package to support." +"End-to-end or functional tests represent an entire workflow that your " +"package supports." msgstr "エンドツーエンドテストまたは機能テストは、パッケージがサポートすることを期待するワークフロー全体を表します。" -#: ../../tests/test-types.md:137 +#: ../../tests/test-types.md:244 +msgid "" +"**End-to-end test example:** Let's say your package opens and " +"processes/converts temperature data from Celsius to Fahrenheit and then " +"calculates the average temperature. An end-to-end test would simulate " +"this entire workflow, ensuring that the package correctly handles the " +"input temperature data and returns a summary average value. An end-to-end" +" test would provide sample data, run the entire workflow, and verify that" +" the final output is correct." +msgstr "" + +#: ../../tests/test-types.md:274 +msgid "" +"This end-to-end test exercises the entire user workflow: providing sample" +" data, converting and averaging it, and verifying the output is correct." +msgstr "" + +#: ../../tests/test-types.md:278 +#, fuzzy msgid "" -"End-to-end test also test how a program runs from start to finish. A " -"tutorial that you add to your documentation that runs in CI in an " -"isolated environment is another example of an end-to-end test." +"End-to-end tests also verify how a program runs from start to finish. A " +"tutorial that you add to your documentation and run in CI is another " +"example of an end-to-end test. For example, a Jupyter (`.ipynb`) notebook" +" or `.md` file with embedded code that demonstrates a complete user " +"workflow." msgstr "エンドツーエンドのテストも、プログラムが最初から最後までどのように実行されるかをテストします。ドキュメントに追加するチュートリアルは、分離された環境のCIで実行され、エンドツーエンドのテストのもう一つの例です。" -#: ../../tests/test-types.md:140 +#: ../../tests/test-types.md:285 +#, fuzzy msgid "" "For scientific packages, creating short tutorials that highlight core " "workflows that your package supports, that are run when your " -"documentation is built could also serve as end-to-end tests." +"documentation is built, could also serve as end-to-end tests." msgstr "科学的なパッケージの場合、パッケージがサポートする中核的なワークフローを強調する短いチュートリアルを作成し、ドキュメントのビルド時に実行することで、エンドツーエンドのテストを兼ねることができます。" -#: ../../tests/test-types.md:143 -msgid "Comparing unit, integration and end-to-end tests" +#: ../../tests/test-types.md:290 +msgid "When to use which test type" +msgstr "" + +#: ../../tests/test-types.md:292 +msgid "" +"If you’re new to testing, start with unit tests. They are the simplest to" +" write, fastest to run, and easiest to debug. As your package grows, you " +"can then add integration and end-to-end tests where they add the most " +"value." +msgstr "" + +#: ../../tests/test-types.md:294 +msgid "Start by writing unit tests" +msgstr "" + +#: ../../tests/test-types.md:296 +msgid "Are you testing a single function, method, or class in isolation?" +msgstr "" + +#: ../../tests/test-types.md:298 +msgid "→ Yes: Write a [unit test](test-types.md#unit-tests)." +msgstr "" + +#: ../../tests/test-types.md:300 +msgid "Example: Check that add_numbers(2, 3) returns 5" +msgstr "" + +#: ../../tests/test-types.md:301 +msgid "Unit tests don’t rely on other parts of your code" +msgstr "" + +#: ../../tests/test-types.md:302 +msgid "These tests form the foundation of your test suite" +msgstr "" + +#: ../../tests/test-types.md:303 +msgid "If something breaks, unit tests make it easy to find where" +msgstr "" + +#: ../../tests/test-types.md:305 +#, fuzzy +msgid "Add integration tests next" +msgstr "統合テスト" + +#: ../../tests/test-types.md:307 +msgid "Are you testing how multiple components work together?" +msgstr "" + +#: ../../tests/test-types.md:309 +msgid "→ **Yes:** Write [integration tests](test-types.md#integration-tests)." +msgstr "" + +#: ../../tests/test-types.md:311 +msgid "Example: Converting temperatures and then computing their average" +msgstr "" + +#: ../../tests/test-types.md:312 +msgid "Integration tests assume individual pieces already work" +msgstr "" + +#: ../../tests/test-types.md:313 +msgid "These tests verify that components interact correctly" +msgstr "" + +#: ../../tests/test-types.md:315 +msgid "Use end-to-end tests for core workflows" +msgstr "" + +#: ../../tests/test-types.md:317 +msgid "Are you testing a complete, realistic user workflow from start to finish?" +msgstr "" + +#: ../../tests/test-types.md:319 +msgid "" +"→ **Yes:** Use an [end-to-end test](test-types.md#end-to-end-functional-" +"tests)." +msgstr "" + +#: ../../tests/test-types.md:321 +msgid "Example: Run a full data-processing workflow a user would follow" +msgstr "" + +#: ../../tests/test-types.md:322 +msgid "These tests often mirror examples in your documentation" +msgstr "" + +#: ../../tests/test-types.md:323 +msgid "Use them sparingly for the most important workflows." +msgstr "" + +#: ../../tests/test-types.md:324 +msgid "Tutorials run during documentation builds can serve as end-to-end tests." +msgstr "" + +#: ../../tests/test-types.md:326 +#, fuzzy +msgid "Comparing unit, integration, and end-to-end tests" msgstr "ユニットテスト、統合テスト、エンドツーエンドテストの比較" -#: ../../tests/test-types.md:145 +#: ../../tests/test-types.md:328 +#, fuzzy msgid "" "Unit tests, integration tests, and end-to-end tests have complementary " -"advantages and disadvantages. The fine-grained nature of unit tests make " -"them well-suited for isolating where errors are occurring. However, unit " -"tests are not useful for verifying that different sections of code work " +"advantages and disadvantages. The fine-grained nature of unit tests makes" +" them well-suited for isolating where errors are occurring. However, unit" +" tests are not useful for verifying that different sections of code work " "together." msgstr "" "単体テスト、統合テスト、エンドツーエンドテストには、それぞれ相補的な長所と短所があります。 " "単体テストは、そのきめ細かな性質から、どこでエラーが発生しているかを切り分けるのに適しています。 " "しかし、ユニットテストは、コードの異なるセクションが連携して動作することを検証するのには役に立ちません。" -#: ../../tests/test-types.md:147 +#: ../../tests/test-types.md:334 msgid "" -"Integration and end-to-end tests verify that the different portions of " -"the program work together, but are less well-suited for isolating where " -"errors are occurring. For example, when you refactor your code, it is " -"possible that that your end-to-end tests will break. But if the refactor " -"didn't introduce new behavior to your existing code, then you can rely on" -" your unit tests to continue to pass, testing the original functionality " -"of your code." -msgstr "統合テストとエンドツーエンドテストは、プログラムのさまざまな部分が連携して動作することを検証しますが、どこでエラーが発生しているかを切り分けるにはあまり適していません。例えば、コードをリファクタリングすると、エンドツーエンドのテストが壊れる可能性があります。しかし、リファクタリングによって既存のコードに新しい動作が導入されなかったのであれば、コードの元の機能をテストするユニットテストがパスし続けることに頼ることができます。" +"Integration and end-to-end tests verify that different portions of the " +"program work together, but are less valuable for immediately isolating " +"exactly where errors are occurring." +msgstr "" + +#: ../../tests/test-types.md:338 +msgid "Tests don't have to be perfect" +msgstr "" -#: ../../tests/test-types.md:152 +#: ../../tests/test-types.md:339 +#, fuzzy msgid "" "It is important to note that you don't need to spend energy worrying " -"about the specifics surrounding the different types of tests. When you " -"begin to work on your test suite, consider what your package does and how" -" you may need to test parts of your package. Bring familiar with the " -"different types of tests can provides a framework to help you think about" -" writing tests and how different types of tests can complement each " +"about the specifics of test types. When you begin to work on your test " +"suite, consider what your package does and how you may need to test parts" +" of it. Being familiar with different test types provides a framework to " +"help you think about writing tests and how they can complement each " "other." msgstr "重要なのは、さまざまな種類のテストにまつわる詳細について心配することにエネルギーを費やす必要はないということです。テストスイートの作成に取りかかるときには、パッケージが何をするのか、そしてパッケージの一部をどのようにテストする必要があるのかを考えてください。さまざまな種類のテストに慣れ親しむことは、テストの書き方や、さまざまな種類のテストが互いにどのように補完し合えるかを考える際のフレームワークとなります。" +#: ../../tests/test-types.md:348 +msgid "" +"Now that you understand test types, learn how to [write effective tests" +"](write-tests) for your package. Then explore how to [run tests locally" +"](run-tests) and in [continuous integration](tests-ci). You can also " +"learn about tracking test coverage using tools like [CodeCov](code-cov)." +msgstr "" + #: ../../tests/tests-ci.md:1 msgid "Run tests with Continuous Integration" msgstr "継続的インテグレーションによるテストの実行" @@ -1113,56 +1583,60 @@ msgid "Write tests for your Python package" msgstr "Pythonパッケージのテストを書く" #: ../../tests/write-tests.md:3 +#, fuzzy msgid "" -"Writing code that tests your package code, also known as test suites, is " -"important for you as a maintainer, your users, and package contributors. " -"Test suites consist of sets of functions, methods, and classes that are " -"written with the intention of making sure a specific part of your code " -"works as you expected it to." +"**Writing code** that tests your package code, also known as test suites," +" is important for you as a maintainer, your users, and package " +"contributors. Test suites consist of sets of functions, methods, and " +"classes that are written with the intention of making sure a specific " +"part of your code works as you expected it to." msgstr "" "パッケージのコードをテストするコードを書くことは、テスト・スイートとしても知られています。 " "テスト・スイートは、関数、メソッド、クラスのセットで構成され、コードの特定の部分が期待通りに動作することを確認することを意図して書かれます。" -#: ../../tests/write-tests.md:7 +#: ../../tests/write-tests.md:9 msgid "Why write tests for your package?" msgstr "なぜパッケージのテストを書くのか？" -#: ../../tests/write-tests.md:9 +#: ../../tests/write-tests.md:11 +#, fuzzy msgid "" -"Tests act as a safety net for code changes. They help you spot and " -"rectify bugs before they affect users. Tests also instill confidence that" -" code alterations from contributors won't breaking existing " -"functionality." +"Tests act as a safety net for code changes. They help you identify and " +"fix bugs before they affect users. Tests also instill confidence that " +"code changes from contributors won't break existing functionality." msgstr "" "テストはコード変更のセーフティネットとして機能します。 バグがユーザーに影響を与える前に発見し、修正するのに役立ちます。 " "テストはまた、貢献者によるコード改変が既存の機能を壊さないという確信を与えます。" -#: ../../tests/write-tests.md:13 +#: ../../tests/write-tests.md:15 msgid "Writing tests for your Python package is important because:" msgstr "Pythonパッケージのテストを書くことは重要です:" -#: ../../tests/write-tests.md:15 +#: ../../tests/write-tests.md:17 +#, fuzzy msgid "" -"**Catch Mistakes:** Tests are a safety net. When you make changes or add " +"**Catch mistakes:** Tests are a safety net. When you make changes or add " "new features to your package, tests can quickly tell you if you " "accidentally broke something that was working fine before." msgstr "" "**キャッチミス:** " "テストはセーフティネットです。パッケージに変更を加えたり、新機能を追加したりした場合、テストによって、以前は問題なく動作していたものを誤って壊してしまったかどうかをすぐに知ることができます。" -#: ../../tests/write-tests.md:16 +#: ../../tests/write-tests.md:20 +#, fuzzy msgid "" -"**Save Time:** Imagine you have a magic button that can automatically " +"**Save time:** Imagine you have a magic button that can automatically " "check if your package is still working properly. Tests are like that " -"magic button! They can run all those checks for you saving you time." +"magic button! They can run all those checks for you, saving you time." msgstr "" "**時間を節約する:** " "あなたのパッケージがまだ正常に動作しているかどうかを自動的にチェックできる魔法のボタンがあるとしましょう。テストは魔法のボタンのようなものです！ " "あなたの時間を節約するために、すべてのチェックを実行してくれます。" -#: ../../tests/write-tests.md:17 +#: ../../tests/write-tests.md:23 +#, fuzzy msgid "" -"**Easier Collaboration:** If you're working with others, or have outside " +"**Easier collaboration:** If you're working with others or have outside " "contributors, tests help everyone stay on the same page. Your tests " "explain how your package is supposed to work, making it easier for others" " to understand and contribute to your project." @@ -1170,36 +1644,39 @@ msgstr "" "**より容易なコラボレーション:** " "他の人と一緒に仕事をしていたり、外部の協力者がいる場合、テストは全員が同じページにとどまるのに役立ちます。テストは、パッケージがどのように動作するかを説明し、他の人が理解しやすくし、プロジェクトに貢献しやすくします。" -#: ../../tests/write-tests.md:18 +#: ../../tests/write-tests.md:27 +#, fuzzy msgid "" -"**Fearless Refactoring:** Refactoring means making improvements to your " +"**Fearless refactoring:** Refactoring means making improvements to your " "code structure without changing its behavior. Tests empower you to make " -"these changes as if you break something, test failures will let you know." +"these changes; if you break something, test failures will let you know." msgstr "" "**大胆不敵なリファクタリング:** リファクタリングとは、コードの振る舞いを変えることなく、コード構造を改善することです。 " "テストは、あなたが何かを壊した場合、テストの失敗があなたに知らせてくれるので、このような変更を行う力を与えてくれます。" -#: ../../tests/write-tests.md:19 +#: ../../tests/write-tests.md:30 +#, fuzzy msgid "" "**Documentation:** Tests serve as technical examples of how to use your " -"package. This can be helpful for a new technical contributor that wants " -"to contribute code to your package. They can look at your tests to " +"package. This can be helpful for new technical contributors who want to " +"contribute code to your package. They can look at your tests to " "understand how parts of your code functionality fits together." msgstr "" "**文書化:** テストは、あなたのパッケージの使い方の技術的な例となります。 " "これは、あなたのパッケージにコードを提供しようとする新しい技術的貢献者にとって役に立ちます。 " "彼らはあなたのテストを見て、コードの機能の一部がどのように組み合わされているかを理解することができます。" -#: ../../tests/write-tests.md:20 +#: ../../tests/write-tests.md:34 +#, fuzzy msgid "" -"**Long-Term ease of maintenance:** As your package evolves, tests ensure " +"**Long-term ease of maintenance:** As your package evolves, tests ensure " "that your code continues to behave as expected, even as you make changes " "over time. Thus you are helping your future self when writing tests." msgstr "" "**長期的なメンテナンスの容易さ:** " "パッケージが進化するにつれて、テストは、時間の経過とともに変更を加えても、コードが期待通りに動作し続けることを保証します。こうして、テストを書くときに将来の自分を助けることになります。" -#: ../../tests/write-tests.md:21 +#: ../../tests/write-tests.md:38 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 " @@ -1211,11 +1688,11 @@ msgstr "" "フレームワークでテストを実行することで、あなたや貢献者がコードベースに変更を加えるたびに、コードベースの問題や変更点をキャッチすることができます。" " これにより、あなたのソフトウェアが期待通りに動作することが保証されます。" -#: ../../tests/write-tests.md:23 +#: ../../tests/write-tests.md:44 msgid "Tests for user edge cases" msgstr "ユーザーエッジケースのテスト" -#: ../../tests/write-tests.md:25 +#: ../../tests/write-tests.md:46 msgid "" "Edge cases refer to unexpected or \"outlier\" ways that some users may " "use your package. Tests enable you to address various edge cases that " @@ -1229,7 +1706,7 @@ msgstr "" "`dataframe` を期待したのに、ユーザがnumpyの `array` を提供した場合、何が起こるでしょうか？ " "あなたのコードは、このような状況を丁寧に処理し、明確なフィードバックを提供していますか？それとも、原因不明の失敗でユーザーをイライラさせたままにしていますか？" -#: ../../tests/write-tests.md:33 +#: ../../tests/write-tests.md:55 msgid "" "For a good introduction to testing, see [this Software Carpentry " "lesson](https://swcarpentry.github.io/python-novice-" @@ -1238,44 +1715,44 @@ msgstr "" "テストの入門書としては、 [このSoftware Carpentryのレッスン](https://swcarpentry.github.io" "/python-novice-inflammation/10-defensive.html) を参照してください。" -#: ../../tests/write-tests.md:41 -msgid "" -"Imagine you're working on a puzzle where each puzzle piece represents a " -"function, method, class or attribute in your Python package that you want" -" other people to be able to use. Would you want to give someone a puzzle " -"that has missing pieces or pieces that don't fit together? Providing " -"people with the right puzzle pieces that work together can be compared to" -" writing tests for your Python package." -msgstr "" -"パズルのピースが、あなたのPythonパッケージの関数、メソッド、クラス、属性を表しているとしましょう。 " -"そしてあなたは他の人に使ってもらいたいと思っています。 ピースが欠けていたり、ピースが合わなかったりするパズルを誰かに渡したいと思いますか？ " -"パズルのピースを正しく組み合わせて提供することは、Python パッケージのテストを書くことに例えることができます。" - -#: ../../tests/write-tests.md:44 +#: ../../tests/write-tests.md:59 msgid "Test examples" msgstr "テスト例" -#: ../../tests/write-tests.md:47 -msgid "" -"Let’s say you have a Python function that adds two numbers a and b " -"together." +#: ../../tests/write-tests.md:62 +#, fuzzy +msgid "Let's say you have a Python function that adds two numbers together." msgstr "例えば、2つの数値aとbを足し合わせるPython関数があるとしましょう。" -#: ../../tests/write-tests.md:54 +#: ../../tests/write-tests.md:84 msgid "" "A test to ensure that function runs as you might expect when provided " "with different numbers might look like this:" msgstr "異なる数値が与えられたときに、その関数が期待通りに実行されることを確認するテストは次のようになります:" -#: ../../tests/write-tests.md:72 -msgid "🧩🐍" -msgstr "🧩🐍" - -#: ../../tests/write-tests.md:74 -msgid "How do I know what type of tests to write?" +#: ../../tests/write-tests.md:103 +#, fuzzy +msgid "🧩🐍 How do you know what type of tests to write?" msgstr "どのような種類のテストを書けばいいのか、どうすればわかりますか？" -#: ../../tests/write-tests.md:77 +#: ../../tests/write-tests.md:105 +#, fuzzy +msgid "As you begin to write tests for your package, you should consider:" +msgstr "なぜパッケージのテストを書くのか？" + +#: ../../tests/write-tests.md:107 +msgid "" +"there are [three types of tests Test Types for Python Packages](test-" +"types.md) that can help guide your development." +msgstr "" + +#: ../../tests/write-tests.md:108 +msgid "" +"your tests should consider how a user might use (and misuse!) your " +"package." +msgstr "" + +#: ../../tests/write-tests.md:111 #, fuzzy msgid "" "This section has been adapted from [a presentation by Nick " @@ -1284,13 +1761,12 @@ msgstr "" "このセクションは、 [Nick Murphyのプレゼンテーション](https://zenodo.org/record/8185113) " "から引用しました。" -#: ../../tests/write-tests.md:80 -msgid "" -"At this point, you may be wondering - what should you be testing in your " -"package? Below are a few examples:" +#: ../../tests/write-tests.md:115 +#, fuzzy +msgid "But, what should you be testing in your package? Below are a few examples:" msgstr "この時点で、あなたは疑問に思うかもしれません-あなたのパッケージで何をテストすべきか？ 以下にいくつか例を挙げます:" -#: ../../tests/write-tests.md:82 +#: ../../tests/write-tests.md:118 msgid "" "**Test some typical cases:** Test that the package functions as you " "expect it to when users use it. For instance, if your package is supposed" @@ -1300,32 +1776,316 @@ msgstr "" "**いくつかの典型的なケースをテスト:** " "パッケージが、ユーザーが使用したときに期待通りに機能することをテストします。例えば、パッケージが2つの数値を足すことになっている場合、その2つの数値を足した結果が正しいかどうかをテストします。" -#: ../../tests/write-tests.md:84 +#: ../../tests/write-tests.md:123 +#, fuzzy msgid "" "**Test special cases:** Sometimes there are special or outlier cases. For" " instance, if a function performs a specific calculation that may become " -"problematic closer to the value = 0, test it with the input of both 0 and" +"problematic closer to the value of 0, test it with the input of both 0 " +"and nearby values." msgstr "" "**特別なケースをテストする:** " "時には特殊なケースや異常なケースもあります。例えば、ある関数が特定の計算を実行し、その計算が値=0に近いほど問題になる可能性がある場合、その関数の入力を0と" -#: ../../tests/write-tests.md:86 -msgid "" -"**Test at and near the expected boundaries:** If a function requires a " -"value that is greater than or equal to 1, make sure that the function " -"still works with both the values 1 and less than one and 1.001 as well " -"(something close to the constraint value).." -msgstr "" -"**予想される境界線とその付近でテストする:** 関数が1以上の値を必要とする場合、この関数が、1と1未満と1.001の両方の値 " -"(制約値に近い値) でも動作することを確認してください。" - -#: ../../tests/write-tests.md:88 +#: ../../tests/write-tests.md:128 +#, fuzzy msgid "" -"**Test that code fails correctly:** If a function requires a value " -"greater than or equal to 1, then test at 0.999. Make sure that the " -"function fails gracefully when given unexpected values and help and that " -"the user can easily understand why if failed (provides a useful error " -"message)." +"**Test at and near expected boundaries:** If a function requires a value " +"that is greater than or equal to 1, make sure that the function still " +"works with the values 1 and 0.999, as well as 1.001 (values close to the " +"constraint). Make sure that the function fails gracefully when given " +"unexpected values and that the user can easily understand why it failed " +"by providing a useful error message." msgstr "" "**コードが正しく失敗するかテストする** 関数が1以上の値を必要とする場合は、0.999でテストします。 " "予期しない値やヘルプが与えられたときに、関数が差し障り無く失敗し、ユーザが失敗した理由を簡単に理解できるようにします(有用なエラーメッセージを提供します)。" + +#: ../../tests/write-tests.md:138 +msgid "" +"Now that you understand what and why to test, explore the [three types of" +" tests](test-types.md) (unit, integration, and end-to-end) to determine " +"which style of tests best fits your package. Then, learn how to [run your" +" tests locally](run-tests.md) and [in continuous integration](tests-" +"ci.md). Finally, track your progress with [code coverage](code-cov.md) " +"metrics." +msgstr "" + +#~ msgid "" +#~ "There are three general types of " +#~ "tests that you can write for your" +#~ " Python package: unit tests, integration" +#~ " tests and end-to-end (or " +#~ "functional) tests. Learn about all " +#~ "three." +#~ msgstr "" +#~ "Python パッケージで書くことのできるテストには、ユニットテスト、統合テスト、エンドツーエンドテスト " +#~ "(あるいは機能テスト) の 3 種類があります。 この 3 " +#~ "つについて学びましょう。" + +#~ msgid "" +#~ "If you expect your users to use" +#~ " your package across different versions " +#~ "of Python, then using an automation " +#~ "tool such as nox to run your " +#~ "tests is useful. Learn about the " +#~ "various tools that you can use to" +#~ " run your tests across python " +#~ "versions here." +#~ msgstr "" +#~ "もしユーザがあなたのパッケージを異なるバージョンの Python " +#~ "で使うことを想定しているなら、テストを実行するために nox のような自動化ツールを使うと便利です。 " +#~ "Python のバージョンにまたがってテストを実行するために使える様々なツールについては、こちらを参照してください。" + +#~ 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 "" +#~ "GitHub Actionsのような継続的インテグレーションプラットフォームは、Python " +#~ "のバージョンやオペレーティングシステムの違いを問わずテストを実行するのに便利です。 " +#~ "継続的インテグレーションで実行するテストの設定については、こちらを参照してください。" + +#~ msgid "Graphic showing the elements of the packaging process." +#~ msgstr "パッケージング工程の要素を示すグラフィック。" + +#~ msgid "Run Python package tests" +#~ msgstr "Pythonパッケージテストの実行" + +#~ msgid "" +#~ "Running your tests is important to " +#~ "ensure that your package is working " +#~ "as expected. It's good practice to " +#~ "consider that tests will run on " +#~ "your computer and your users' computers" +#~ " that may be running a different " +#~ "Python version and operating systems. " +#~ "Think about the following when running" +#~ " your tests:" +#~ msgstr "" +#~ "テストを実行することは、パッケージが期待通りに動作していることを確認するために重要です。 " +#~ "テストは、あなたのコンピュータと、Python " +#~ "のバージョンやオペレーティングシステムが異なるユーザのコンピュータで実行されることを考慮するのがよい習慣です。 " +#~ "テストを実行する際には、以下のことを考慮してください:" + +#~ msgid "" +#~ "Run your test suite in a matrix" +#~ " of environments that represent the " +#~ "Python versions and operating systems " +#~ "your users are likely to have." +#~ msgstr "テストスイートは、Python のバージョンとユーザーが使用する可能性のあるオペレーティングシステムを表す環境のマトリックスで実行します。" + +#~ msgid "" +#~ "Running your tests in an isolated " +#~ "environment provides confidence in the " +#~ "tests and their reproducibility. This " +#~ "ensures that tests do not pass " +#~ "randomly due to your computer's specific" +#~ " setup. For instance, you might have" +#~ " unexpectedly installed dependencies on " +#~ "your local system that are not " +#~ "declared in your package's dependency " +#~ "list. This oversight could lead to " +#~ "issues when others try to install " +#~ "or run your package on their " +#~ "computers." +#~ msgstr "" +#~ "隔離された環境でテストを実行することで、テストとその再現性に自信を持つことができます。 " +#~ "これにより、あなたのコンピュータの設定によってテストがランダムにパスすることがなくなります。 " +#~ "たとえば、あなたのパッケージの依存関係リストで宣言されていない依存関係を、予期せずローカルシステムにインストールしてしまったかもしれません。" +#~ " このような見落としは、他の人があなたのパッケージを自分のコン " +#~ "ピュータにインストールしたり実行しようとしたときに、問題につながる可能性 があります。" + +#~ msgid "" +#~ "**Automation tools** allow you to " +#~ "automate running workflows such as tests" +#~ " in specific ways using user-defined" +#~ " commands. For instance it's useful " +#~ "to be able to run tests across " +#~ "different Python versions with a single" +#~ " command. Tools such as " +#~ "[**nox**](https://nox.thea.codes/en/stable/index.html) and " +#~ "[**tox**](https://tox.wiki/en/latest/index.html) also " +#~ "allow you to run tests across " +#~ "Python versions. However, it will be " +#~ "difficult to test your build on " +#~ "different operating systems using only " +#~ "nox and tox - this is where " +#~ "continuous integration (CI) comes into " +#~ "play." +#~ msgstr "" +#~ "**自動化ツール** " +#~ "を使うと、ユーザー定義のコマンドを使って、テストのようなワークフローを特定の方法で実行することを自動化できます。 " +#~ "例えば、1つのコマンドで異なるPythonのバージョンにまたがってテストを実行できると便利です。 " +#~ "[**nox**](https://nox.thea.codes/en/stable/index.html) や " +#~ "[**tox**](https://tox.wiki/en/latest/index.html) " +#~ "のようなツールも、Pythonのバージョンをまたいでテストを実行できます。 " +#~ "しかし、noxとtoxだけを使って異なるオペレーティングシステムでビルドをテストするのは難しいでしょう - " +#~ "ここで継続的インテグレーション(CI)の出番です。" + +#~ msgid "" +#~ "**Continuous Integration (CI):** is the " +#~ "last tool that you'll need to run" +#~ " your tests. CI will not only " +#~ "allow you to replicate any automated " +#~ "builds you create using nox or tox" +#~ " to run your package in different " +#~ "Python environments. It will also allow" +#~ " you to run your tests on " +#~ "different operating systems (Windows, Mac " +#~ "and Linux). [We discuss using CI " +#~ "to run tests here](tests-ci)." +#~ msgstr "" +#~ "**継続的インテグレーション (CI):** は、テストを実行するために必要な最後のツールです。 CI" +#~ " は、nox や tox を使って作成した自動ビルドを複製して、異なる Python" +#~ " 環境でパッケージを実行できるようにするだけではありません。 " +#~ "また、異なるオペレーティングシステム（Windows、Mac、Linux）でテストを実行することもできます。 " +#~ "[テストを実行するためにCIを使うことについては、ここで説明します](tests-ci) 。" + +#~ msgid "Table: Testing & Automation Tool" +#~ msgstr "テーブル: テスト＆自動化ツール" + +#~ msgid "Features" +#~ msgstr "機能" + +#~ msgid "Test Runner (Tox)" +#~ msgstr "テストランナー (Tox)" + +#~ msgid "Run Tests Locally" +#~ msgstr "ローカルでテストを実行する" + +#~ msgid "" +#~ msgstr "" + +#~ msgid "" +#~ msgstr "" + +#~ msgid "Use for other automation tasks (e.g. building docs)" +#~ msgstr "その他の自動化タスクに使用する（ドキュメントの作成など）" + +#~ msgid "" +#~ "**[Hatch](https://github.com/pypa/hatch)** is a " +#~ "modern end-to-end packaging tool " +#~ "that works with the popular build " +#~ "backend called hatchling. `hatch` offers " +#~ "a `tox`-like setup where you can " +#~ "run tests locally using different Python" +#~ " versions. If you are using `hatch`" +#~ " to support your packaging workflow, " +#~ "you may want to also use its " +#~ "testing capabilities rather than using " +#~ "`nox`." +#~ msgstr "" +#~ "**[Hatch](https://github.com/pypa/hatch)** " +#~ "は、hatchlingと呼ばれる人気のあるビルドバックエンドで動作する最新のエンドツーエンドパッケージングツールです。 " +#~ "`hatch` は `tox` のようなセットアップを提供し、異なる Python " +#~ "バージョンを使ってローカルでテストを実行することができます。 パッケージングのワークフローをサポートするために " +#~ "`hatch` を使っているのであれば、 `nox` を使うよりも `hatch` " +#~ "のテスト機能を使った方が良いかもしれない。" + +#~ msgid "Run tests across Python versions with nox" +#~ msgstr "noxでPythonのバージョンにまたがってテストを実行する" + +#~ msgid "Nox will manage each environment on its own." +#~ msgstr "Noxはそれぞれの環境を独自に管理します。" + +#~ msgid "" +#~ "An example of using nox to run " +#~ "tests in `venv` environments for Python" +#~ " versions 3.9, 3.10, 3.11 and 3.12" +#~ " is below." +#~ msgstr "noxを使ってPythonバージョン3.9、3.10、3.11、3.12の `venv` 環境でテストを実行する例を以下に示します。" + +#~ msgid "" +#~ "Note that for the code below to" +#~ " work, you need to have all 4" +#~ " versions of Python installed on your" +#~ " computer for `nox` to find." +#~ msgstr "" +#~ "以下のコードが動作するためには、 `nox` " +#~ "が見つけることができる4つのバージョンのPythonがコンピュータにインストールされている必要があることに注意してください。" + +#~ msgid "" +#~ "TODO: add some tests above and " +#~ "show what the output would look " +#~ "like in the examples below..." +#~ msgstr "TODO: 上記のテストをいくつか追加し、以下の例で出力がどのようになるかを示す..." + +#~ msgid "Integration" +#~ msgstr "統合" + +#~ msgid "" +#~ "I think this page would be " +#~ "stronger if we did have some " +#~ "examples from our package here: " +#~ "https://github.com/pyOpenSci/pyosPackage" +#~ msgstr "" +#~ "私たちのパッケージからの例があれば、このページはもっと強くなると思います: " +#~ "https://github.com/pyOpenSci/pyosPackage " + +#~ msgid "" +#~ "For example, if you had a series" +#~ " of steps that collected temperature " +#~ "data in a spreadsheet, converted it " +#~ "from degrees celsius to Fahrenheit and" +#~ " then provided an average temperature " +#~ "for a particular time period. An " +#~ "integration test would ensure that all" +#~ " parts of that workflow behaved as" +#~ " expected." +#~ msgstr "例えば、スプレッドシートに温度データを収集し、摂氏から華氏に変換し、特定の期間の平均温度を提供する一連のステップがあったとします。統合テストは、そのワークフローのすべての部分が期待通りに動作することを保証します。" + +#~ msgid "" +#~ "Integration and end-to-end tests " +#~ "verify that the different portions of" +#~ " the program work together, but are" +#~ " less well-suited for isolating where" +#~ " errors are occurring. For example, " +#~ "when you refactor your code, it is" +#~ " possible that that your end-to-" +#~ "end tests will break. But if the" +#~ " refactor didn't introduce new behavior " +#~ "to your existing code, then you " +#~ "can rely on your unit tests to " +#~ "continue to pass, testing the original" +#~ " functionality of your code." +#~ msgstr "統合テストとエンドツーエンドテストは、プログラムのさまざまな部分が連携して動作することを検証しますが、どこでエラーが発生しているかを切り分けるにはあまり適していません。例えば、コードをリファクタリングすると、エンドツーエンドのテストが壊れる可能性があります。しかし、リファクタリングによって既存のコードに新しい動作が導入されなかったのであれば、コードの元の機能をテストするユニットテストがパスし続けることに頼ることができます。" + +#~ msgid "" +#~ "Imagine you're working on a puzzle " +#~ "where each puzzle piece represents a " +#~ "function, method, class or attribute in" +#~ " your Python package that you want" +#~ " other people to be able to " +#~ "use. Would you want to give " +#~ "someone a puzzle that has missing " +#~ "pieces or pieces that don't fit " +#~ "together? Providing people with the " +#~ "right puzzle pieces that work together" +#~ " can be compared to writing tests " +#~ "for your Python package." +#~ msgstr "" +#~ "パズルのピースが、あなたのPythonパッケージの関数、メソッド、クラス、属性を表しているとしましょう。 " +#~ "そしてあなたは他の人に使ってもらいたいと思っています。 " +#~ "ピースが欠けていたり、ピースが合わなかったりするパズルを誰かに渡したいと思いますか？ " +#~ "パズルのピースを正しく組み合わせて提供することは、Python パッケージのテストを書くことに例えることができます。" + +#~ msgid "🧩🐍" +#~ msgstr "🧩🐍" + +#~ msgid "" +#~ "**Test at and near the expected " +#~ "boundaries:** If a function requires a" +#~ " value that is greater than or " +#~ "equal to 1, make sure that the " +#~ "function still works with both the " +#~ "values 1 and less than one and " +#~ "1.001 as well (something close to " +#~ "the constraint value).." +#~ msgstr "" +#~ "**予想される境界線とその付近でテストする:** 関数が1以上の値を必要とする場合、この関数が、1と1未満と1.001の両方の値" +#~ " (制約値に近い値) でも動作することを確認してください。" + diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index 0116d482..29506c53 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -21,7 +21,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" #: ../../tutorials/add-license-coc.md:6 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" @@ -53,7 +53,7 @@ msgid "Learning objectives" msgstr "学習目標" #: ../../tutorials/add-license-coc.md:17 ../../tutorials/add-readme.md:17 -#: ../../tutorials/pyproject-toml.md:27 +#: ../../tutorials/pyproject-toml.md:30 msgid "In this lesson you will learn:" msgstr "このレッスンで学ぶこと:" @@ -103,20 +103,21 @@ msgstr "メタデータが設定されている `pyproject.toml` データでそ #: ../../tutorials/add-license-coc.md:31 #, fuzzy msgid "" -"By adding this metadata to your `pyproject.toml` file, the choice of " -"license will be included in your package's metadata which is used to " -"populate your package's PyPI landing page. The `LICENSE` file is also " -"used in your GitHub repository's landing page interface." +"By adding this metadata to your [pyproject.toml](pyproject-toml) file, " +"the choice of license will be included in your package's metadata which " +"is used to populate your package's PyPI landing page. The `LICENSE` file " +"is also used in your GitHub repository's landing page interface, and " +"makes its way into your distributions." msgstr "" "`LICENSE` ファイルを `pyproject.toml` ファイルに追加することで、 `LICENSE` " "がパッケージのメタデータに含まれるようになります。 `LICENSE` は GitHub " "リポジトリのランディングページのインターフェイスでも使用されます。" -#: ../../tutorials/add-license-coc.md:33 +#: ../../tutorials/add-license-coc.md:36 msgid "What license should you use?" msgstr "どのライセンスを使うべきか？" -#: ../../tutorials/add-license-coc.md:35 +#: ../../tutorials/add-license-coc.md:38 #, fuzzy msgid "" "We suggest that you use a permissive license that accommodates the other " @@ -130,11 +131,11 @@ msgstr "" "[choosealicense.com](https://choosealicense.com/) で一般的に推奨されているライセンスである " "MIT を使ってください。" -#: ../../tutorials/add-license-coc.md:38 +#: ../../tutorials/add-license-coc.md:41 msgid "Licenses for the scientific Python ecosystem" msgstr "科学的Pythonエコシステムのためのライセンス" -#: ../../tutorials/add-license-coc.md:39 +#: ../../tutorials/add-license-coc.md:42 msgid "" "[We discuss licenses for the scientific Python ecosystem in more detail " "here in our guidebook.](../documentation/repository-files/license-files)" @@ -142,11 +143,11 @@ msgstr "" "[科学的Pythonエコシステムのライセンスについては、ガイドブックで詳しく説明しています](../documentation" "/repository-files/license-files)" -#: ../../tutorials/add-license-coc.md:42 +#: ../../tutorials/add-license-coc.md:45 msgid "Where should the `LICENSE` file live" msgstr "`LICENSE` ファイルはどこに置くべきか" -#: ../../tutorials/add-license-coc.md:44 +#: ../../tutorials/add-license-coc.md:47 msgid "" "Your `LICENSE` file should be placed at the root of your package's " "repository. When you add the `LICENSE` at the root, GitHub will " @@ -156,13 +157,13 @@ msgstr "" "`LICENSE` ファイルは、パッケージのリポジトリのルートに置く必要があります。 ルートに `LICENSE` を追加すると、GitHub " "が魔法のごとく自動的にそれを検出し、GitHub リポジトリ内の `LICENSE` ファイルへの直接リンクをユーザーに提供します。" -#: ../../tutorials/add-license-coc.md:50 +#: ../../tutorials/add-license-coc.md:53 msgid "" "Image showing the GitHub repository for SunPy an accepted pyOpenSci " "package." msgstr "pyOpenSci パッケージに採用された SunPy 用のGitHubリポジトリを示す画像。" -#: ../../tutorials/add-license-coc.md:52 +#: ../../tutorials/add-license-coc.md:55 msgid "" "Notice at the top of the README portion of the GitHub landing page, there" " are three tabs directly linking to the `README` file which is visible, " @@ -174,15 +175,15 @@ msgstr "" "ファイル、そしてSunPyが使用するライセンスを指定するタブの3つに直接リンクしていることに注目してください。 " "これらのファイルは標準的な命名規則を使ってプロジェクトディレクトリのルートに置かれているため、GitHubによって発見されます。" -#: ../../tutorials/add-license-coc.md:59 +#: ../../tutorials/add-license-coc.md:62 msgid "How to add a `LICENSE` file to your package directory" msgstr "パッケージディレクトリに `LICENSE` ファイルを追加する方法" -#: ../../tutorials/add-license-coc.md:61 +#: ../../tutorials/add-license-coc.md:64 msgid "There are several ways to add a `LICENSE` file:" msgstr "`LICENSE` ファイルを追加するにはいくつかの方法があります:" -#: ../../tutorials/add-license-coc.md:63 +#: ../../tutorials/add-license-coc.md:66 msgid "" "When you create a new repository on GitHub, it will ask you if you wish " "to add a `LICENSE` file at that time. If you select yes, it will create " @@ -191,7 +192,7 @@ msgstr "" "GitHub で新しいリポジトリを作成すると、そのときに `LICENSE` ファイルを追加するかどうかを尋ねられます。 yes " "を選ぶと、ファイルを作成してくれます。" -#: ../../tutorials/add-license-coc.md:64 +#: ../../tutorials/add-license-coc.md:67 msgid "" "You can add a `LICENSE` through the GitHub gui following the [ instructions " @@ -203,23 +204,23 @@ msgstr "" "your-project-for-healthy-contributions/adding-a-license-to-a-repository) " "に従って追加することができます。" -#: ../../tutorials/add-license-coc.md:65 +#: ../../tutorials/add-license-coc.md:68 msgid "You can add the file manually as we are doing in this lesson." msgstr "このレッスンで行っているように、手動でファイルを追加することもできます。" -#: ../../tutorials/add-license-coc.md:68 +#: ../../tutorials/add-license-coc.md:71 msgid "If you completed the past lessons including" msgstr "以下を含む過去のレッスンを修了した場合" -#: ../../tutorials/add-license-coc.md:70 +#: ../../tutorials/add-license-coc.md:73 msgid "[Making your code installable](create-python-package.md) and" msgstr "[コードをインストール可能にする](create-python-package.md) と" -#: ../../tutorials/add-license-coc.md:71 +#: ../../tutorials/add-license-coc.md:74 msgid "[publishing your package to PyPI](publish-pypi.md)" msgstr "[PyPIへのパッケージの公開](publish-pypi.md)" -#: ../../tutorials/add-license-coc.md:73 +#: ../../tutorials/add-license-coc.md:76 msgid "" "then you already have a `LICENSE` file containing text for the MIT " "license in your Python package. Thus you can skip to the next section of " @@ -228,17 +229,17 @@ msgstr "" "は、Python パッケージの中に MIT ライセンスのテキストを含む `LICENSE` ファイルが既にあるということです。 " "従って、このチュートリアルの次のセクションの `CODE_OF_CONDUCT` の追加に進むことができます。" -#: ../../tutorials/add-license-coc.md:75 +#: ../../tutorials/add-license-coc.md:78 msgid "" "If you don't yet have a `LICENSE` file in your directory, then continue " "reading." msgstr "あなたのディレクトリにまだ `LICENSE` ファイルがない場合は、このまま読み進めてください。" -#: ../../tutorials/add-license-coc.md:78 +#: ../../tutorials/add-license-coc.md:81 msgid "How to add a `LICENSE` to your package - the manual way" msgstr "パッケージに `LICENSE` を追加する方法 - 手動の方法" -#: ../../tutorials/add-license-coc.md:80 +#: ../../tutorials/add-license-coc.md:83 msgid "" "If you don't already have a `LICENSE` file, and you are not yet using a " "platform such as GitHub or GitLab, then you can create a `LICENSE` file " @@ -247,39 +248,39 @@ msgstr "" "まだ `LICENSE` ファイルがなく、GitHub や GitLab などのプラットフォームを使っていない場合は、次のようにして " "`LICENSE` ファイルを作成します。" -#: ../../tutorials/add-license-coc.md:82 +#: ../../tutorials/add-license-coc.md:85 msgid "Create a new file called `LICENSE`. If you are using shell you can type:" msgstr "`LICENSE` という新しいファイルを作成します。 シェルを使っている場合は:" -#: ../../tutorials/add-license-coc.md:89 +#: ../../tutorials/add-license-coc.md:92 msgid "Go to [choosealicense.com](https://choosealicense.com/)" msgstr "[choosealicense.com](https://choosealicense.com/) へ。" -#: ../../tutorials/add-license-coc.md:90 +#: ../../tutorials/add-license-coc.md:93 msgid "Select permissive license" msgstr "寛容なライセンスを選択する" -#: ../../tutorials/add-license-coc.md:91 +#: ../../tutorials/add-license-coc.md:94 msgid "" "It will suggest that you use the [MIT " "license](https://choosealicense.com/licenses/mit/)." msgstr "[MITライセンス](https://choosealicense.com/licenses/mit/) を使用するよう提案されます。" -#: ../../tutorials/add-license-coc.md:92 +#: ../../tutorials/add-license-coc.md:95 msgid "" "Copy the license text that it provides into your `LICENSE` file that you " "created above." msgstr "そのライセンステキストを、上記で作成した `LICENSE` ファイルにコピーしてください。" -#: ../../tutorials/add-license-coc.md:93 +#: ../../tutorials/add-license-coc.md:96 msgid "Save your file. You're all done!" msgstr "ファイルを保存します。これで完了です！" -#: ../../tutorials/add-license-coc.md:95 +#: ../../tutorials/add-license-coc.md:98 msgid "An overview of licenses in the scientific Python ecosystem" msgstr "科学的Pythonエコシステムにおけるライセンスの概要" -#: ../../tutorials/add-license-coc.md:98 +#: ../../tutorials/add-license-coc.md:101 msgid "" "In the pyOpenSci [packaging guidebook](../documentation/repository-files" "/license-files), we provide an overview of licenses in the scientific " @@ -291,7 +292,7 @@ msgstr "" "files) では、科学的Pythonエコシステムにおけるライセンスの概要を提供します。 " "なぜライセンスファイルが重要なのか、どのライセンスファイルが科学ソフトウェアに最もよく使われるのか、正しいライセンスを選択する方法についてレビューします。" -#: ../../tutorials/add-license-coc.md:100 +#: ../../tutorials/add-license-coc.md:103 msgid "" "If you want a broad overview of why licenses are important for protecting" " open source software, [check out this blog post that overviews the legal" @@ -310,13 +311,13 @@ msgstr "GitHubのインターフェイス内に `LICENSE` ファイルを追加 msgid "Add license: new GitHub repository" msgstr "ライセンスの追加: 新しいGitHubリポジトリ" -#: ../../tutorials/add-license-coc.md:111 +#: ../../tutorials/add-license-coc.md:114 msgid "" "When you create a new GitHub repository you can add a `LICENSE` file " "through the GitHub interface." msgstr "GitHub リポジトリを新規作成する際に、GitHub インターフェースから `LICENSE` ファイルを追加することができます。" -#: ../../tutorials/add-license-coc.md:116 +#: ../../tutorials/add-license-coc.md:119 msgid "" "Screenshot of the create new repository interface that GitHub provides. " "The elements of this are the owner and repository name for the new repo. " @@ -332,7 +333,7 @@ msgstr "" "READMEチェックボックスがあり、空白のReadmeファイルを追加してくれます。 " "一番下には、.gitignoreファイルを追加する行と、ライセンスを選択する行があります。" -#: ../../tutorials/add-license-coc.md:118 +#: ../../tutorials/add-license-coc.md:121 msgid "" "Image showing the GitHub interface that allows you to add a `LICENSE` and" " `README` file when you create a new repository." @@ -342,7 +343,7 @@ msgstr "新規リポジトリ作成時に `LICENSE` と `README` ファイルを msgid "Add `LICENSE`: Existing GitHub repository" msgstr "`LICENSE` を追加する: 既存のGitHubリポジトリ" -#: ../../tutorials/add-license-coc.md:124 +#: ../../tutorials/add-license-coc.md:127 msgid "" "If you already have a GitHub repository for your package, then you can " "add a `LICENSE` using the GitHub interface by adding a new file to the " @@ -351,7 +352,7 @@ msgstr "" "パッケージ用のGitHubリポジトリが既にある場合は、GitHubのインターフェースで新しいファイルを追加することで `LICENSE` " "ファイルを追加できます。" -#: ../../tutorials/add-license-coc.md:126 +#: ../../tutorials/add-license-coc.md:129 msgid "" "Follow the instructions to select and add a license to your repository on" " the [GitHub LICENSE page](https://docs.github.com/en/communities" @@ -362,7 +363,7 @@ msgstr "" "your-project-for-healthy-contributions/adding-a-license-to-a-repository) " "の指示に従って、リポジトリにライセンスを選択し追加してください。" -#: ../../tutorials/add-license-coc.md:127 +#: ../../tutorials/add-license-coc.md:130 msgid "" "Once you have added your `LICENSE` file, be sure to sync your git local " "repository with the repository on GitHub.com. This means running `git " @@ -371,7 +372,7 @@ msgstr "" "`LICENSE`ファイルを追加したら、必ずローカルのgitリポジトリをGitHub.com上のリポジトリと同期してください。これは、`git " "pull`を実行してローカルブランチを更新することを意味します。" -#: ../../tutorials/add-license-coc.md:130 +#: ../../tutorials/add-license-coc.md:133 msgid "" "Image showing what the LICENSE file looks like in the GItHub interface. " "At the top you can see the actual license which in this image is BSD " @@ -384,13 +385,13 @@ msgstr "" "revised " "licenseです。そして、そのライセンスが何であるかと、そのライセンスに関連するパーミッションの両方を説明するテキストがあります。画像の下部には、ライセンスの実際のテキストがLICENSEファイルに表示されています。" -#: ../../tutorials/add-license-coc.md:132 +#: ../../tutorials/add-license-coc.md:135 msgid "" "You can view a summary of the `LICENSE` chosen on your project's GitHub " "landing page." msgstr "あなたのプロジェクトのGitHubのランディングページで、選ばれた `LICENSE` の概要を見ることができます。" -#: ../../tutorials/add-license-coc.md:139 +#: ../../tutorials/add-license-coc.md:142 msgid "" "Now you know how to add a `LICENSE` to your project. Next, you'll learn " "about the `CODE_OF_CONDUCT.md` file and how to add it to your package " @@ -399,43 +400,44 @@ msgstr "" "これで、プロジェクトに`LICENSE`を追加する方法がわかりました。 " "次は、`CODE_OF_CONDUCT.md`ファイルと、それをパッケージディレクトリに追加する方法を説明します。" -#: ../../tutorials/add-license-coc.md:144 +#: ../../tutorials/add-license-coc.md:147 msgid "What is a code of conduct file?" msgstr "code of conduct ファイルとは何ですか？" -#: ../../tutorials/add-license-coc.md:146 +#: ../../tutorials/add-license-coc.md:149 +#, fuzzy, python-brace-format msgid "" -"A `CODE_OF_CONDUCT` file is used to establish guidelines for how people " -"in your community interact." +"A `CODE_OF_CONDUCT` file is a {term}`Code of conduct` used to establish " +"guidelines for how people in your community interact." msgstr "`CODE_OF_CONDUCT` ファイルは、あなたのコミュニティの人々がどのように交流するかのガイドラインを確立するために使用されます。" -#: ../../tutorials/add-license-coc.md:148 +#: ../../tutorials/add-license-coc.md:152 msgid "" "This file is critical to supporting your community as it grows. The " "`CODE_OF_CONDUCT`:" msgstr "このファイルは、あなたのコミュニティが成長するのをサポートするために非常に重要です。 `CODE_OF_CONDUCT` は:" -#: ../../tutorials/add-license-coc.md:151 +#: ../../tutorials/add-license-coc.md:155 msgid "" "Establishes guidelines for how users and contributors interact with each " "other and you in your software repository." msgstr "ソフトウェアリポジトリにおいて、ユーザーやコントリビューターがどのように相互作用するかについてのガイドラインを確立します。" -#: ../../tutorials/add-license-coc.md:152 +#: ../../tutorials/add-license-coc.md:156 msgid "Identifies negative behaviors that you don't want in your interactions." msgstr "あなたが交流の中で望まない否定的な行動を特定します。" -#: ../../tutorials/add-license-coc.md:154 +#: ../../tutorials/add-license-coc.md:158 msgid "" "You can use your code of conduct as a tool that can be referenced when " "moderating challenging conversations." msgstr "行動規範は、困難な会話をモデレーティングする際に参照できるツールとして使うことができます。" -#: ../../tutorials/add-license-coc.md:156 +#: ../../tutorials/add-license-coc.md:160 msgid "What to put in your `CODE_OF_CONDUCT` file" msgstr "`CODE_OF_CONDUCT` ファイルに書くべきこと" -#: ../../tutorials/add-license-coc.md:158 +#: ../../tutorials/add-license-coc.md:162 msgid "" "If you are unsure of what language to add to your `CODE_OF_CONDUCT` file," " we suggest that you adopt the [contributor covenant " @@ -446,7 +448,7 @@ msgstr "" "language](https://www.contributor-" "covenant.org/version/2/1/code_of_conduct/) を出発点として採用することをお勧します。" -#: ../../tutorials/add-license-coc.md:161 +#: ../../tutorials/add-license-coc.md:165 msgid "" "![Contributor " "Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)" @@ -454,27 +456,27 @@ msgstr "" "![Contributor " "Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)" -#: ../../tutorials/add-license-coc.md:161 +#: ../../tutorials/add-license-coc.md:165 msgid "Contributor Covenant" msgstr "Contributor Covenant" -#: ../../tutorials/add-license-coc.md:163 +#: ../../tutorials/add-license-coc.md:167 msgid "" "The `CODE_OF_CONDUCT.md` should be placed at the root of your project " "directory, similar to the `LICENSE` file." msgstr "`CODE_OF_CONDUCT.md` は、 `LICENSE` ファイルと同様に、プロジェクトディレクトリのルートに置く必要があります。" -#: ../../tutorials/add-license-coc.md:165 +#: ../../tutorials/add-license-coc.md:169 msgid "How to add a `CODE_OF_CONDUCT` file to your package directory" msgstr "パッケージディレクトリに `CODE_OF_CONDUCT` ファイルを追加する方法。" -#: ../../tutorials/add-license-coc.md:167 +#: ../../tutorials/add-license-coc.md:171 msgid "" "Add a `CODE_OF_CONDUCT.md` file to the root of your repository if it " "doesn't already exist." msgstr "`CODE_OF_CONDUCT.md` ファイルがまだ存在しない場合は、リポジトリのルートに追加してください。" -#: ../../tutorials/add-license-coc.md:173 +#: ../../tutorials/add-license-coc.md:177 msgid "" "Visit the [contributor covenant website](https://www.contributor-" "covenant.org/) and add [the markdown version of their code of " @@ -490,15 +492,15 @@ msgstr "" "covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) を追加します。 " "プレースホルダーの情報は必ず記入してください。 本文をよく読み、内容を理解し、同意すること！" -#: ../../tutorials/add-license-coc.md:175 +#: ../../tutorials/add-license-coc.md:179 msgid "That's it - you've now added a code of conduct to your package directory." msgstr "これであなたのパッケージディレクトリに行動規範が追加されたことになります。" -#: ../../tutorials/add-license-coc.md:177 +#: ../../tutorials/add-license-coc.md:181 msgid "Additional Code of Conduct resources" msgstr "行動規範に関するその他のリソース" -#: ../../tutorials/add-license-coc.md:180 +#: ../../tutorials/add-license-coc.md:184 msgid "" "[ Guide: `CODE_OF_CONDUCT.md` " "files](https://docs.github.com/en/communities/setting-up-your-project-" @@ -508,7 +510,7 @@ msgstr "" "ファイル](https://docs.github.com/en/communities/setting-up-your-project-for-" "healthy-contributions/adding-a-code-of-conduct-to-your-project)" -#: ../../tutorials/add-license-coc.md:181 +#: ../../tutorials/add-license-coc.md:185 msgid "" "[pyOpenSci package guide `CODE_OF_CONDUCT.md` " "overview](https://www.pyopensci.org/python-package-guide/documentation" @@ -518,29 +520,29 @@ msgstr "" "/python-package-guide/documentation/repository-files/code-of-conduct-" "file.html)" -#: ../../tutorials/add-license-coc.md:184 ../../tutorials/add-readme.md:238 -#: ../../tutorials/publish-conda-forge.md:468 -#: ../../tutorials/pyproject-toml.md:690 +#: ../../tutorials/add-license-coc.md:188 ../../tutorials/add-readme.md:240 +#: ../../tutorials/publish-conda-forge.md:475 +#: ../../tutorials/pyproject-toml.md:699 msgid " Wrap up" msgstr " まとめ" -#: ../../tutorials/add-license-coc.md:186 +#: ../../tutorials/add-license-coc.md:190 msgid "In this lesson and the [last lesson](add-readme), you have added a:" msgstr "このレッスンと [最後のレッスンでは](add-readme), 以下を追加しました:" -#: ../../tutorials/add-license-coc.md:188 +#: ../../tutorials/add-license-coc.md:192 msgid "`README` file;" msgstr "`README` ファイル;" -#: ../../tutorials/add-license-coc.md:189 +#: ../../tutorials/add-license-coc.md:193 msgid "`LICENSE` file and a" msgstr "`LICENSE` ファイルと" -#: ../../tutorials/add-license-coc.md:190 +#: ../../tutorials/add-license-coc.md:194 msgid "`CODE_OF_CONDUCT` file." msgstr "`CODE_OF_CONDUCT` ファイル。" -#: ../../tutorials/add-license-coc.md:192 +#: ../../tutorials/add-license-coc.md:196 msgid "" "These are fundamental files needed for every scientific Python package " "repository. These files help users understand how to use your package and" @@ -549,12 +551,12 @@ msgstr "" "これらはすべての科学的なPythonパッケージリポジトリに必要な基本的なファイルです。 " "これらのファイルは、ユーザがあなたのパッケージの使い方を理解し、パッケージメンテナとやりとりするのに役立ちます。" -#: ../../tutorials/add-license-coc.md:196 -#: ../../tutorials/create-python-package.md:445 +#: ../../tutorials/add-license-coc.md:200 +#: ../../tutorials/create-python-package.md:455 msgid "In the upcoming lessons, you will:" msgstr "これからのレッスンでは、あなたは:" -#: ../../tutorials/add-license-coc.md:198 +#: ../../tutorials/add-license-coc.md:202 msgid "" "[Add more metadata to your `pyproject.toml` file](pyproject-toml) to " "support building and publishing your package on PyPI." @@ -562,30 +564,31 @@ msgstr "" "PyPI でのパッケージのビルドと公開をサポートするために [`pyproject.toml` ファイルにメタデータを追加します" "](pyproject-toml) 。" -#: ../../tutorials/add-license-coc.md:199 +#: ../../tutorials/add-license-coc.md:203 msgid "" "Publish a new version of your Python package to the test PyPI to preview " "the updated metadata landing page." msgstr "あなたのPythonパッケージの新しいバージョンをテストPyPIに公開して、更新されたメタデータランディングページをプレビューしてください。" -#: ../../tutorials/add-license-coc.md:204 -#: ../../tutorials/create-python-package.md:540 -#: ../../tutorials/publish-conda-forge.md:480 -#: ../../tutorials/publish-pypi.md:417 -#: ../../tutorials/trusted-publishing.md:344 +#: ../../tutorials/add-license-coc.md:208 +#: ../../tutorials/create-python-package.md:550 +#: ../../tutorials/publish-conda-forge.md:487 +#: ../../tutorials/publish-pypi.md:419 +#: ../../tutorials/trusted-publishing.md:347 msgid "Footnotes" msgstr "脚注" -#: ../../tutorials/add-license-coc.md:206 +#: ../../tutorials/add-license-coc.md:210 msgid "https://opensource.org/license/mit/" msgstr "https://opensource.org/license/mit/" -#: ../../tutorials/add-license-coc.md:207 +#: ../../tutorials/add-license-coc.md:211 msgid "https://opensource.org/license/bsd-3-clause/" msgstr "https://opensource.org/license/bsd-3-clause/" #: ../../tutorials/add-readme.md:6 -msgid "Add a README file to your Python package" +#, fuzzy, python-brace-format +msgid "Add a {term}`README` file to your {term}`Python package`" msgstr "PythonパッケージにREADMEファイルを追加する" #: ../../tutorials/add-readme.md:8 @@ -621,16 +624,17 @@ msgid "What is a README file?" msgstr "README ファイルとは何か？" #: ../../tutorials/add-readme.md:25 +#, fuzzy, python-brace-format msgid "" -"The `README.md` file is a markdown file located at the root of your " -"project directory that helps a user understand:" +"The `README.md` file is the project's {term}`README` and is located at " +"the root of your project directory. It helps a user understand:" msgstr "`README.md` ファイルはプロジェクトディレクトリのルートにあるマークダウンファイルで、ユーザーの理解を助けるものです:" -#: ../../tutorials/add-readme.md:28 +#: ../../tutorials/add-readme.md:29 msgid "You package's name" msgstr "パッケージ名" -#: ../../tutorials/add-readme.md:29 +#: ../../tutorials/add-readme.md:30 msgid "" "What the package does. Your README file should clearly state the " "problem(s) that your software is designed to solve and its target " @@ -639,23 +643,23 @@ msgstr "" "パッケージが何をするのか。 " "READMEファイルには、あなたのソフトウェアが解決するために設計された(複数の)問題と、その対象読者を明確に記述してください。" -#: ../../tutorials/add-readme.md:30 +#: ../../tutorials/add-readme.md:31 msgid "The current development \"state\" of the package (through badges)" msgstr "パッケージの現在の開発 \"状態\" （バッジを通して）" -#: ../../tutorials/add-readme.md:31 +#: ../../tutorials/add-readme.md:32 msgid "How to get started with using your package." msgstr "パッケージの使い始め方" -#: ../../tutorials/add-readme.md:32 +#: ../../tutorials/add-readme.md:33 msgid "How to contribute to your package" msgstr "パッケージに貢献する方法" -#: ../../tutorials/add-readme.md:33 +#: ../../tutorials/add-readme.md:34 msgid "How to cite your package" msgstr "パッケージの引用方法" -#: ../../tutorials/add-readme.md:35 +#: ../../tutorials/add-readme.md:36 msgid "" "Your **README.md** file is important as it is often the first thing that " "someone sees before they install your package. The README file is also " @@ -664,7 +668,7 @@ msgstr "" "**README.md** ファイルは、誰かがあなたのパッケージをインストールする前に、最初に目にすることが多いので重要です。 " "READMEファイルはPyPIのランディングページに入力するためにも使われます。" -#: ../../tutorials/add-readme.md:37 +#: ../../tutorials/add-readme.md:38 msgid "" "Note that there is no specific content structure for README files. " "However, this tutorial outlines the sections that we suggest that you " @@ -673,63 +677,63 @@ msgstr "" "READMEファイルには特定のコンテンツ構造はないことに注意してください。 " "しかし、このチュートリアルでは、READMEファイルに含めることを推奨するセクションの概要を説明します。" -#: ../../tutorials/add-readme.md:41 +#: ../../tutorials/add-readme.md:42 msgid "Create a README.md file for your package" msgstr "パッケージの README.md ファイルを作成する" -#: ../../tutorials/add-readme.md:43 +#: ../../tutorials/add-readme.md:44 msgid "It's time to add a `README.md` file to your project directory." msgstr "`README.md` ファイルをプロジェクト・ディレクトリに追加しましょう。" -#: ../../tutorials/add-readme.md:45 +#: ../../tutorials/add-readme.md:46 msgid "Step 0: Create a README file" msgstr "ステップ0: READMEファイルの作成" -#: ../../tutorials/add-readme.md:46 +#: ../../tutorials/add-readme.md:47 msgid "" "To get started, if you don't already have a README.md file in your " "project directory, create one." msgstr "まず、プロジェクトディレクトリにまだREADME.mdファイルがない場合は、作成してください。" -#: ../../tutorials/add-readme.md:49 +#: ../../tutorials/add-readme.md:50 msgid "If you created your project directory from" msgstr "以下からプロジェクトディレクトリを作成した場合" -#: ../../tutorials/add-readme.md:51 +#: ../../tutorials/add-readme.md:52 msgid "a GitHub repository online" msgstr "オンラインのGitHubリポジトリ" -#: ../../tutorials/add-readme.md:52 +#: ../../tutorials/add-readme.md:53 msgid "using `hatch init`" msgstr "`hatch init` を使用する。" -#: ../../tutorials/add-readme.md:54 +#: ../../tutorials/add-readme.md:55 msgid "Then you may already have a README.MD file in your project directory." msgstr "その場合、プロジェクトディレクトリに README.MD ファイルが既にあるかもしれません。" -#: ../../tutorials/add-readme.md:60 +#: ../../tutorials/add-readme.md:61 msgid "Step 1: Add the name of your package as the README title" msgstr "ステップ1: READMEのタイトルにパッケージ名を追加する" -#: ../../tutorials/add-readme.md:62 +#: ../../tutorials/add-readme.md:63 msgid "At the top of the `README.md` file, add the name of your package." msgstr "`README.md` ファイルの先頭に、パッケージ名を追加します。" -#: ../../tutorials/add-readme.md:64 +#: ../../tutorials/add-readme.md:65 msgid "" "If you are using markdown it should be a header 1 (H1) tag which is " "denoted with a single `#` sign." msgstr "マークダウンを使用している場合は、 `#` 記号1つで示されるヘッダー1 (H1) タグでなければなりません。" -#: ../../tutorials/add-readme.md:66 +#: ../../tutorials/add-readme.md:67 msgid "`# Package-title-here`" msgstr "`# Package-title-here`" -#: ../../tutorials/add-readme.md:68 +#: ../../tutorials/add-readme.md:69 msgid "Step 2: add badges to the top of your README file" msgstr "ステップ2: READMEファイルの先頭にバッジを追加する" -#: ../../tutorials/add-readme.md:70 +#: ../../tutorials/add-readme.md:71 msgid "" "It's common for maintainers to add badges to the top of their README " "files. Badges allow you and your package users to track things like:" @@ -737,21 +741,21 @@ msgstr "" "メンテナが README ファイルの先頭にバッジを追加するのはよくあることです。 " "バッジをつけることで、あなたとあなたのパッケージのユーザは以下のようなことを追跡できるようになります:" -#: ../../tutorials/add-readme.md:72 +#: ../../tutorials/add-readme.md:73 msgid "Broken documentation and test builds." msgstr "ドキュメントとテストビルドが壊れています。" -#: ../../tutorials/add-readme.md:73 +#: ../../tutorials/add-readme.md:74 msgid "Versions of your package that are on PyPI and conda." msgstr "PyPIとcondaにあるあなたのパッケージのバージョン。" -#: ../../tutorials/add-readme.md:74 +#: ../../tutorials/add-readme.md:75 msgid "" "Whether your package has been reviewed and vetted by an organization such" " as pyOpenSci and/or JOSS." msgstr "あなたのパッケージがpyOpenSciやJOSSのような組織によってレビューされ、審査されたかどうか。" -#: ../../tutorials/add-readme.md:76 +#: ../../tutorials/add-readme.md:77 msgid "" "If you have already published your package to pypi.org you can use " "[shields.io to create a package version badge](https://shields.io/badges" @@ -762,77 +766,78 @@ msgstr "" "[shields.ioでパッケージのバージョンバッジを作成](https://shields.io/badges/py-pi-version) " "することができます。 このバッジは、あなたが新しいバージョンのパッケージをPyPIにリリースすると動的に更新されます。" -#: ../../tutorials/add-readme.md:78 +#: ../../tutorials/add-readme.md:79 msgid "" "If not, you can leave the top empty for now and add badges to your README" " at a later point as they make sense." msgstr "そうでない場合は、今のところ上部を空にしておいて、後でREADMEにバッジを追加することができます。" -#: ../../tutorials/add-readme.md:80 +#: ../../tutorials/add-readme.md:81 msgid "Step 3: Add a description of what your package does" msgstr "ステップ 3: パッケージの説明を追加する" -#: ../../tutorials/add-readme.md:82 +#: ../../tutorials/add-readme.md:83 msgid "" "Below the badges (if you have them), add a section of text that provides " "an easy-to-understand overview of what your package does." msgstr "バッジの下に（バッジがある場合）、あなたのパッケージが何をするのかをわかりやすく説明するテキストのセクションを追加します。" -#: ../../tutorials/add-readme.md:86 +#: ../../tutorials/add-readme.md:87 msgid "Keep this section short." msgstr "このセクションは短めにしてください。" -#: ../../tutorials/add-readme.md:87 +#: ../../tutorials/add-readme.md:88 msgid "Try to avoid jargon." msgstr "専門用語はなるべく避けてください。" -#: ../../tutorials/add-readme.md:88 +#: ../../tutorials/add-readme.md:89 msgid "" "Define technical terms that you use to make the description accessible to" " more people." msgstr "説明をより多くの人が理解できるように、使用する専門用語を定義します。" -#: ../../tutorials/add-readme.md:90 +#: ../../tutorials/add-readme.md:91 msgid "" "Remember that the more people understand what your package does, the more" " people will use it." msgstr "あなたのパッケージが何をするものなのか、より多くの人が理解すればするほど、より多くの人がそれを使うようになることを忘れないでください。" -#: ../../tutorials/add-readme.md:92 +#: ../../tutorials/add-readme.md:93 msgid "Step 4: Add package installation instructions" msgstr "ステップ4: パッケージのインストール方法を追加する" -#: ../../tutorials/add-readme.md:94 +#: ../../tutorials/add-readme.md:95 msgid "Next, add instructions that tell users how to install your package." msgstr "次に、ユーザーにパッケージのインストール方法を説明するインストラクションを追加します。" -#: ../../tutorials/add-readme.md:96 +#: ../../tutorials/add-readme.md:97 +#, fuzzy, python-brace-format msgid "" -"For example, can they use pip to install your package? `python -m pip " -"install packagename`" +"For example, can they use {term}`pip` to install your package? `python -m" +" pip install packagename`" msgstr "" "例えば、彼らはあなたのパッケージをインストールするためにpipを使うことができますか？ `python -m pip install " "packagename`" -#: ../../tutorials/add-readme.md:99 +#: ../../tutorials/add-readme.md:100 msgid "or conda?" msgstr "それともconda？" -#: ../../tutorials/add-readme.md:101 +#: ../../tutorials/add-readme.md:102 msgid "`conda install -c conda-forge packagename`." msgstr "conda install -c conda-forge packagename`." -#: ../../tutorials/add-readme.md:103 +#: ../../tutorials/add-readme.md:104 msgid "" "If you haven't yet published your package to pypi.org then you can skip " "this section and come back and add these instructions later." msgstr "まだパッケージをpypi.orgに公開していない場合は、このセクションを読み飛ばして、後でこれらの説明を追加してください。" -#: ../../tutorials/add-readme.md:107 +#: ../../tutorials/add-readme.md:108 msgid "Step 5: Any additional setup" msgstr "ステップ5：追加設定" -#: ../../tutorials/add-readme.md:109 +#: ../../tutorials/add-readme.md:110 msgid "" "In some cases, your package users may need to manually install other " "tools in order to use your package. If that is the case, be sure to add a" @@ -841,31 +846,31 @@ msgstr "" "場合によっては、あなたのパッケージを使用するために、あなたのパッケージのユーザーが他のツールを手動でインストールする必要があるかもしれません。 " "その場合は、READMEファイルに追加セットアップのセクションを追加してください。" -#: ../../tutorials/add-readme.md:114 +#: ../../tutorials/add-readme.md:115 msgid "" "Here, briefly document (or link to documentation for) any additional " "setup that is required to use your package. This might include:" msgstr "ここで、あなたのパッケージを使うために必要な追加設定を簡単に文書化 (または文書へのリンク) をしてください。これには以下が含まれます:" -#: ../../tutorials/add-readme.md:118 +#: ../../tutorials/add-readme.md:119 msgid "authentication information, if it is applicable to your package." msgstr "認証情報、あなたのパッケージに適用される場合。" -#: ../../tutorials/add-readme.md:119 +#: ../../tutorials/add-readme.md:120 msgid "additional tool installations, such as GDAL." msgstr "GDALのような追加ツールのインストール。" -#: ../../tutorials/add-readme.md:122 +#: ../../tutorials/add-readme.md:123 msgid "" "Many packages won't need an additional setup section in their README. In " "that case you can always skip this section." msgstr "多くのパッケージでは、READMEに追加のセットアップセクションは必要ありません。 その場合、このセクションはいつでも読み飛ばすことができます。" -#: ../../tutorials/add-readme.md:127 +#: ../../tutorials/add-readme.md:128 msgid "Step 6: Add a get started section" msgstr "ステップ6: スタートセクションの追加" -#: ../../tutorials/add-readme.md:129 +#: ../../tutorials/add-readme.md:130 msgid "" "Next add a get-started section. Within this section, add a small code " "example that demonstrates importing and using some of the functionality " @@ -874,33 +879,33 @@ msgstr "" "次に、get-started セクションを追加します。 " "このセクションに、パッケージの機能の一部をインポートして使用することを示す、小さなコード例を追加します。" -#: ../../tutorials/add-readme.md:132 +#: ../../tutorials/add-readme.md:133 msgid "Provide a fully functional code snippet if possible" msgstr "可能であれば、完全に機能するコードスニペットを提供してください。" -#: ../../tutorials/add-readme.md:135 +#: ../../tutorials/add-readme.md:136 msgid "" "It is important to try to make the code examples that you provide your " "users as useful as possible." msgstr "ユーザーに提供するコード例は、できるだけ役立つものにするよう努めることが重要です。" -#: ../../tutorials/add-readme.md:137 +#: ../../tutorials/add-readme.md:138 msgid "" "Be sure to provide a copy/paste code example that will work as-is when " "pasted into a Jupyter Notebook or .py file if that is possible." msgstr "可能であれば、Jupyter Notebookや.pyファイルに貼り付けてもそのまま動作するようなコピー＆ペーストのコード例を必ず提示してください。" -#: ../../tutorials/add-readme.md:139 +#: ../../tutorials/add-readme.md:140 msgid "" "If there are tokens and other steps needed to run your package, be sure " "to be clear about what those steps are." msgstr "あなたのパッケージを実行するために必要なトークンや他のステップがある場合、それらのステップが何であるかを明確にするようにしてください。" -#: ../../tutorials/add-readme.md:142 +#: ../../tutorials/add-readme.md:143 msgid "For the pyosPackage, a short get started demo might look like this:" msgstr "pyosPackageの場合、簡単に始めるデモは次のようになります:" -#: ../../tutorials/add-readme.md:150 +#: ../../tutorials/add-readme.md:151 msgid "" "Or it could simply be a link to a getting started tutorial that you have " "created. If you don't have this yet, you can leave it empty for the time " @@ -909,17 +914,17 @@ msgstr "" "あるいは、あなたが作成したチュートリアルへのリンクでもかまいません。 " "まだチュートリアルをお持ちでない場合は、当分の間、空欄のままにしておいてください。" -#: ../../tutorials/add-readme.md:153 +#: ../../tutorials/add-readme.md:154 msgid "" "This would also be a great place to add links to tutorials that help " "users understand how to use your package for common workflows." msgstr "また、一般的なワークフローでのパッケージの使い方を理解するのに役立つチュートリアルへのリンクを追加するのにも最適な場所です。" -#: ../../tutorials/add-readme.md:158 +#: ../../tutorials/add-readme.md:159 msgid "Step 7: Community section" msgstr "ステップ7: コミュニティセクション" -#: ../../tutorials/add-readme.md:160 +#: ../../tutorials/add-readme.md:161 msgid "" "The community section of your README file is a place to include " "information for users who may want to engage with your project. This " @@ -928,49 +933,50 @@ msgstr "" "READMEファイルのコミュニティセクションは、あなたのプロジェクトに参加したいユーザーのための情報を含める場所です。 この参加は、おそらく " "GitHub や GitLab のようなプラットフォームで行われるでしょう。" -#: ../../tutorials/add-readme.md:162 +#: ../../tutorials/add-readme.md:163 +#, fuzzy msgid "" "In the community section, you will add links to your contributing guide " -"and `CODE_OF_CONDUCT.md`. You will create a [`CODE_OF_CONDUCT.md` file in" -" the next lesson](add-license-coc)." +"and `CODE_OF_CONDUCT.md`. You will create a code of conduct file in the " +"[next lesson](add-license-coc)." msgstr "" "コミュニティセクションでは、あなたの貢献ガイドと `CODE_OF_CONDUCT.md` へのリンクを追加します。 [次のレッスンでは " "`CODE_OF_CONDUCT.md` ファイル](add-license-coc) を作成することになります。" -#: ../../tutorials/add-readme.md:165 +#: ../../tutorials/add-readme.md:167 msgid "" "As your package grows you may also have a link to a development guide " "that contributors and your maintainer team will follow. The development " "guide outlines how to perform maintenance tasks such as:" msgstr "パッケージが大きくなるにつれて、貢献者やメンテナチームが従う開発ガイドへのリンクを持つこともできます。この開発ガイドには、次のようなメンテナンス作業の方法が概説されています:" -#: ../../tutorials/add-readme.md:168 +#: ../../tutorials/add-readme.md:170 msgid "running tests" msgstr "テストの実行" -#: ../../tutorials/add-readme.md:169 +#: ../../tutorials/add-readme.md:171 msgid "making package releases" msgstr "パッケージのリリース" -#: ../../tutorials/add-readme.md:170 +#: ../../tutorials/add-readme.md:172 msgid "building documentation" msgstr "ドキュメントの作成" -#: ../../tutorials/add-readme.md:171 +#: ../../tutorials/add-readme.md:173 msgid "and more." msgstr "などなど。" -#: ../../tutorials/add-readme.md:175 +#: ../../tutorials/add-readme.md:177 msgid "Step 8: Citation information" msgstr "ステップ8: 引用情報" -#: ../../tutorials/add-readme.md:177 +#: ../../tutorials/add-readme.md:179 msgid "" "Finally it is important to let users know how to cite your package. You " "can communicate citation information in a few different ways." msgstr "最後に、ユーザーにあなたのパッケージの引用方法を知らせることが重要です。 引用情報を伝える方法はいくつかあります。" -#: ../../tutorials/add-readme.md:180 +#: ../../tutorials/add-readme.md:182 msgid "" "You can use a tool such as zenodo to create a DOI and associated citation" " information for your package if it is hosted on a platform such as " @@ -981,7 +987,7 @@ msgstr "" " [この短いチュートリアルで、その設定をチェックしてみましょう。](https://coderefinery.github.io/github-" "without-command-line/doi/)" -#: ../../tutorials/add-readme.md:184 +#: ../../tutorials/add-readme.md:186 msgid "" "Alternatively if you send your package through a peer review process such" " as the [one lead by pyOpenSci](https://www.pyopensci.org/about-peer-" @@ -997,15 +1003,15 @@ msgstr "" "Softwareとの提携により](https://www.pyopensci.org/about-peer-review/index.html) " "相互参照DOIを得ることができます。" -#: ../../tutorials/add-readme.md:188 +#: ../../tutorials/add-readme.md:190 msgid "The finished README file" msgstr "完成したREADMEファイル" -#: ../../tutorials/add-readme.md:190 +#: ../../tutorials/add-readme.md:192 msgid "Your finished `README.md` file should look something like this:" msgstr "完成した `README.md` ファイルは次のようになるはずです:" -#: ../../tutorials/add-readme.md:240 +#: ../../tutorials/add-readme.md:242 msgid "" "It's important to consider the information that a new user or contributor" " might need when creating your `README.md` file. While there is no " @@ -1018,7 +1024,7 @@ msgstr "" "完璧なテンプレートは存在しないが、上記はこれから始めようとしているあなたへの推奨事項です。 " "あなたがパッケージをさらに開発し、コミュニティがあなたのパッケージを使い始めるにつれて、このファイルに他の要素を追加する必要性が出てくるかもしれません。" -#: ../../tutorials/add-readme.md:246 +#: ../../tutorials/add-readme.md:248 msgid "" "In the [next lesson](add-license-coc.md), you will add a LICENSE file to " "your Python package. A license file is critical as it tells users how " @@ -1027,39 +1033,42 @@ msgstr "" "[次のレッスン](add-license-coc.md) では、 LICENSEファイルをPythonパッケージに追加します。 " "ライセンスファイルは、ユーザーがあなたのパッケージを合法的にどのように使うことができるのか（そして使うことができないのか）を示す重要なものです。また:" -#: ../../tutorials/add-readme.md:250 +#: ../../tutorials/add-readme.md:252 msgid "Builds trust with your users" msgstr "ユーザーとの信頼関係を築く" -#: ../../tutorials/add-readme.md:251 +#: ../../tutorials/add-readme.md:253 msgid "Discourages misuse of your package and associated code" msgstr "パッケージと関連コードの悪用を防ぐ" -#: ../../tutorials/command-line-reference.md:6 ../../tutorials/intro.md:61 +#: ../../tutorials/command-line-reference.md:6 ../../tutorials/intro.md:63 msgid "Command Line Reference Guide" msgstr "コマンドラインリファレンスガイド" #: ../../tutorials/command-line-reference.md:9 +#, fuzzy msgid "" "**What these tables are:** These tables summarize the command line inputs" -" (e.g., `pipx install hatch`, `hatch build`) necessary to complete all " -"steps in the package creation process, from installing Hatch to " -"publishing the package on PyPI and conda-forge." +" (e.g., `pipx install hatch`, `hatch build` or `python -m build`) " +"necessary to complete all steps in the package creation process, from " +"installing [Hatch](get-to-know-hatch) to publishing the package on [PyPI" +"](publish-pypi) and conda-forge." msgstr "" "**これらの表は何であるか:** これらの表は、Hatch のインストールから PyPI や conda-forge " "でのパッケージの公開まで、パッケージ作成プロセスのすべてのステップを完了するために必要なコマンドライン入力 (e.g., `pipx " "install hatch`, `hatch build`) をまとめたものです。" -#: ../../tutorials/command-line-reference.md:11 +#: ../../tutorials/command-line-reference.md:14 +#, fuzzy, python-brace-format msgid "" -"**What these tables are not:** These tables do not cover the manual/non-" -"automated steps (e.g., create PyPI account, create PyPI API token) you " -"have to complete throughout the package creation process." +"**What these tables are not:** These tables do not cover the manual or " +"non-automated steps (e.g., create a PyPI account, create a {term}`API " +"token`) you have to complete throughout the package creation process." msgstr "" "**これらの表は何でないか:** これらの表は、パッケージの作成プロセスを通して完了しなければならない手動/非自動ステップ " "(PyPIアカウントの作成、PyPI APIトークンの作成など) をカバーしていません。" -#: ../../tutorials/command-line-reference.md:13 +#: ../../tutorials/command-line-reference.md:18 msgid "" "**Operating system note:** The current iteration of this guide has been " "tested on the Windows OS only. Many commands are Windows-specific. OS-" @@ -1072,19 +1081,19 @@ msgstr "" "[COMMAND_DESCRIPTION] (Windows) のように括弧をつけて表示されます。 " "macOSとLinuxに対応するコマンドは今後追加されます。" -#: ../../tutorials/command-line-reference.md:16 +#: ../../tutorials/command-line-reference.md:21 msgid "Environment Setup" msgstr "環境設定" -#: ../../tutorials/command-line-reference.md:38 +#: ../../tutorials/command-line-reference.md:43 msgid "Package Development" msgstr "パッケージ開発" -#: ../../tutorials/command-line-reference.md:57 +#: ../../tutorials/command-line-reference.md:62 msgid "Package Publishing" msgstr "パッケージパブリッシング" -#: ../../tutorials/command-line-reference.md:76 +#: ../../tutorials/command-line-reference.md:81 msgid "Versions and Environments" msgstr "バージョンと環境" @@ -1099,61 +1108,63 @@ msgid "About this lesson" msgstr "このレッスンについて" #: ../../tutorials/create-python-package.md:13 +#, python-brace-format msgid "" "This lesson uses the pyOpenSci Python package copier template to create a" -" Python package quickly. Your package will be installable both locally " -"and remotely from a website such as GitHub (or GitLab) into a Python " -"environment." +" {term}`Python package` quickly. Your package will be installable both " +"locally and remotely from a website such as GitHub (or GitLab) into a " +"Python environment." msgstr "" -#: ../../tutorials/create-python-package.md:16 -#: ../../tutorials/setup-py-to-pyproject-toml.md:21 +#: ../../tutorials/create-python-package.md:18 +#: ../../tutorials/setup-py-to-pyproject-toml.md:23 #, fuzzy msgid "In this lesson, you will learn:" msgstr "このレッスンで学ぶこと:" -#: ../../tutorials/create-python-package.md:18 +#: ../../tutorials/create-python-package.md:20 #, fuzzy msgid "" "How to make your code installable into any Python environment, both " "locally and from GitHub" msgstr "ローカルとGitHubの両方で、あなたのコードをあらゆるPython環境にインストール可能にする方法" -#: ../../tutorials/create-python-package.md:19 +#: ../../tutorials/create-python-package.md:21 #, fuzzy msgid "" -"How to update a `pyproject.toml` file, which contains the metadata needed" -" to build, install, and publish your package." +"How to update a [pyproject.toml file](pyproject-toml), which contains the" +" metadata needed to build, install, and publish your package." msgstr "最後のレッスンでは、パッケージのビルドに必要なコア要素を含む、素のpyproject.tomlファイルを作成しました:" -#: ../../tutorials/create-python-package.md:20 +#: ../../tutorials/create-python-package.md:23 +#, fuzzy, python-brace-format msgid "" -"How to declare a [build backend](build_backends) which will be used to " -"[build](build-package) and install your package" +"How to declare a {term}`Build backend` which will be used to [build" +"](build-package) and install your package" msgstr "" "パッケージの [ビルド](build-package) とインストールに使用する [ビルドバックエンド](build_backends) " "を宣言する方法" -#: ../../tutorials/create-python-package.md:21 +#: ../../tutorials/create-python-package.md:25 msgid "How to install your package in editable mode for interactive development" msgstr "インタラクティブな開発のために編集可能モードでパッケージをインストールする方法" -#: ../../tutorials/create-python-package.md:24 +#: ../../tutorials/create-python-package.md:28 msgid "**What you need to complete this lesson**" msgstr "**このレッスンを完了するために必要なもの**" -#: ../../tutorials/create-python-package.md:26 +#: ../../tutorials/create-python-package.md:30 #, fuzzy msgid "" "To complete this lesson, you will need a local Python environment and " "shell on your computer. You will need to have " -"[Copier](https://copier.readthedocs.io/en/stable/) and [Hatch installed" +"[Copier](https://copier.readthedocs.io/en/stable/) and [Hatch installed" "](get-to-know-hatch) to complete the lesson successfully." msgstr "" "このレッスンを完了するには、あなたのコンピュータにローカルのPython環境とシェルが必要です。　[Hatchのインストール](get-to-" "know-hatch) も必要です。" -#: ../../tutorials/create-python-package.md:30 +#: ../../tutorials/create-python-package.md:35 #, fuzzy msgid "" "If you are using Windows or are not familiar with Shell, you may want to " @@ -1166,7 +1177,7 @@ msgstr "" "をチェックアウトすることをお勧めします。 " "Windowsユーザーは、Shellやgitに関連するステップのためにツールを設定する必要があるでしょう。" -#: ../../tutorials/create-python-package.md:36 +#: ../../tutorials/create-python-package.md:41 msgid "" "This diagram has two smaller boxes with arrows pointing to the right to a" " Python environment. The small boxes read your-package and pip install " @@ -1179,7 +1190,7 @@ msgstr "" "Matplotlib、NumPy、Pandas、Xarray、GeoPandasなどのコアパッケージとともに、your-" "packageがリストアップされています。" -#: ../../tutorials/create-python-package.md:38 +#: ../../tutorials/create-python-package.md:43 #, fuzzy msgid "" "In a [previous lesson, you learned what a Python package is](intro). " @@ -1193,12 +1204,12 @@ msgstr "" "あなたのコードをインストール可能にすることは、公開可能なPythonパッケージを作成するための最初のステップです。 " "あなたのコードがインストール可能になると、それはPythonパッケージとなり、あなたのコンピュータ上の任意のPython環境に追加し、PandasやGeoPandasなどのパッケージをインポートするのと同じ方法でインポートすることができます。あなたのコードがGitHubやGitLabにあるなら、そこから直接インストールすることもできます。" -#: ../../tutorials/create-python-package.md:44 +#: ../../tutorials/create-python-package.md:49 #, fuzzy msgid "Create your Python package" msgstr "Pythonパッケージを作成しましょう！" -#: ../../tutorials/create-python-package.md:46 +#: ../../tutorials/create-python-package.md:51 msgid "" "Below, you will create a pure Python package using the [pyOpenSci copier " "template](https://github.com/pyOpenSci/pyos-package-template). Our " @@ -1208,15 +1219,15 @@ msgid "" "`pyproject.toml`)." msgstr "" -#: ../../tutorials/create-python-package.md:48 +#: ../../tutorials/create-python-package.md:53 msgid "Step 1: Set Up the Package Directory Structure" msgstr "ステップ1: パッケージのディレクトリ構造を設定する" -#: ../../tutorials/create-python-package.md:50 +#: ../../tutorials/create-python-package.md:55 msgid "Open your shell or preferred terminal." msgstr "シェルまたはお好みのターミナルを開きます。" -#: ../../tutorials/create-python-package.md:51 +#: ../../tutorials/create-python-package.md:56 #, fuzzy msgid "" "Use the shell `cd` command to navigate in your shell to the location " @@ -1224,22 +1235,22 @@ msgid "" "package directory structure for you" msgstr "シェルで `cd` コマンドを使い、パッケージのディレクトリを置く場所に移動します。 Hatchがパッケージディレクトリを作成してくれます。" -#: ../../tutorials/create-python-package.md:52 +#: ../../tutorials/create-python-package.md:57 msgid "Choose a name for your package. The name should:" msgstr "パッケージの名前を決めてください。 名前は以下のようにします:" -#: ../../tutorials/create-python-package.md:53 +#: ../../tutorials/create-python-package.md:58 msgid "Have no spaces (*Required*)" msgstr "スペースがない (*必須*)" -#: ../../tutorials/create-python-package.md:54 +#: ../../tutorials/create-python-package.md:59 #, fuzzy msgid "" "Use all lowercase characters (*Recommended*). For this tutorial, we will " "use `pyospackage`." msgstr "すべて小文字を使用 (*推奨*)。 このチュートリアルでは `pyospackage` を使用します。" -#: ../../tutorials/create-python-package.md:55 +#: ../../tutorials/create-python-package.md:60 #, fuzzy msgid "" "Only use letters and the characters _ or - in the name. This means that " @@ -1250,20 +1261,20 @@ msgstr "" "のみを使用してください。これは、`pyos*package`という名前は使えないことを意味します。しかし、 `pyos_package` または " "`pyos-package` という名前であれば、どちらでも構いません。" -#: ../../tutorials/create-python-package.md:57 +#: ../../tutorials/create-python-package.md:62 msgid "" "In your terminal, **run the command below**. This will begin a series of " "prompts that will ask you questions and help you to customize your Python" " package." msgstr "" -#: ../../tutorials/create-python-package.md:63 +#: ../../tutorials/create-python-package.md:68 msgid "" "After running the command above, the template will walk you through a " "series of questions." msgstr "" -#: ../../tutorials/create-python-package.md:65 +#: ../../tutorials/create-python-package.md:70 msgid "" "Note that when you reach the prompt \"Do you want to answer one more " "question, and skip the rest, using the default values?\" you can choose " @@ -1272,20 +1283,20 @@ msgid "" "for you to use." msgstr "" -#: ../../tutorials/create-python-package.md:67 +#: ../../tutorials/create-python-package.md:72 msgid "" "After this question, the template will ask you for your preferred GitHub " "username and will then create a package with basic tests, documentation, " "and GitHub configuration setup for you." msgstr "" -#: ../../tutorials/create-python-package.md:88 +#: ../../tutorials/create-python-package.md:93 msgid "" "The template will then begin to copy files into the directory that used " -"above. (`.` means current working directory" +"above. (`.` means current working directory.)" msgstr "" -#: ../../tutorials/create-python-package.md:96 +#: ../../tutorials/create-python-package.md:101 #, fuzzy msgid "The final package structure will look like this:" msgstr "最終的なプロジェクトのディレクトリ構造は以下のようになるはずです:" @@ -1294,101 +1305,102 @@ msgstr "最終的なプロジェクトのディレクトリ構造は以下のよ msgid "A full package with tests, docs, and GitHub infrastructure" msgstr "テスト、ドキュメント、GitHubインフラストラクチャを備えた完全なパッケージ" -#: ../../tutorials/create-python-package.md:114 +#: ../../tutorials/create-python-package.md:119 msgid "" "If you use the \"bells and whistles\" default option when working through" " the template prompts, our template will create a complete package setup " -"with GitHub CI actions, typing, tests, environments , and more using " +"with GitHub CI actions, typing, tests, environments, and more using " "Hatch. If you customize the entire package, then you can select what " "platform you wish to host it on (GitHub vs GitLab), whether you want " "typing, what documentation engine you want to use, and more." msgstr "" -#: ../../tutorials/create-python-package.md:118 +#: ../../tutorials/create-python-package.md:123 #, fuzzy -msgid "The resulting package directory looks like this" +msgid "The resulting package directory looks like this:" msgstr "プロジェクトディレクトリはこのようになっているはずです:" -#: ../../tutorials/create-python-package.md:141 +#: ../../tutorials/create-python-package.md:146 msgid "The default tools that your package uses are:" msgstr "パッケージが使用するデフォルトのツールは以下の通りです:" -#: ../../tutorials/create-python-package.md:143 +#: ../../tutorials/create-python-package.md:148 msgid "" "[Sphinx](https://www.pyopensci.org/python-package-guide/documentation" "/hosting-tools/sphinx-python-package-documentation-tools.html) with the " -"pydata_sphinx_theme for documentation" +"PyData Sphinx Theme for documentation" msgstr "" -#: ../../tutorials/create-python-package.md:144 +#: ../../tutorials/create-python-package.md:149 msgid "pytest for testing" msgstr "テスト用のpytest" -#: ../../tutorials/create-python-package.md:145 +#: ../../tutorials/create-python-package.md:150 #, fuzzy msgid "Hatch for environment setup" msgstr "Hatchと環境" -#: ../../tutorials/create-python-package.md:147 +#: ../../tutorials/create-python-package.md:152 msgid "" "**Full customization** If you want to customize any elements of your " "package setup, choose `No, I want to fully customize the template.`. " "This will allow you to select:" msgstr "" -#: ../../tutorials/create-python-package.md:150 -msgid "sphinx vs [mkdocs](https://www.mkdocs.org/) vs no documentation" +#: ../../tutorials/create-python-package.md:155 +#, fuzzy +msgid "Sphinx vs [MkDocs](https://www.mkdocs.org/) vs no documentation" msgstr "sphinx vs [mkdocs](https://www.mkdocs.org/) vs ドキュメントなし" -#: ../../tutorials/create-python-package.md:151 +#: ../../tutorials/create-python-package.md:156 #, fuzzy msgid "GitHub vs GitLab" msgstr "GitHub & GitLab vs. Git" -#: ../../tutorials/create-python-package.md:152 +#: ../../tutorials/create-python-package.md:157 msgid "VCS versioning" msgstr "VCSバージョン管理" -#: ../../tutorials/create-python-package.md:153 +#: ../../tutorials/create-python-package.md:158 #, fuzzy msgid "and more" msgstr "などなど。" -#: ../../tutorials/create-python-package.md:156 +#: ../../tutorials/create-python-package.md:161 #, fuzzy msgid "Step 2: Explore the existing module in your package" msgstr "ステップ 2: パッケージにモジュールを追加する" -#: ../../tutorials/create-python-package.md:158 -#, fuzzy +#: ../../tutorials/create-python-package.md:163 +#, fuzzy, python-brace-format msgid "" -"A Python module refers to a `.py` file containing the code that you want " -"your package to access and run. Within the `pyospackage` subdirectory, " -"you have an example.py module that you can use to test out your package " -"quickly." +"A {term}`Module` refers to a `.py` file containing the code that you want" +" your package to access and run. Within the `pyospackage` subdirectory, " +"you have an `example.py` module that you can use to test out your package" +" quickly." msgstr "" "Python モジュールとは、パッケージにアクセスさせ、実行させたいコードを含む `.py` ファイルを指します。 `pyospackage` " "サブディレクトリに、少なくとも1つのPythonモジュール (.py ファイル) を追加します。" -#: ../../tutorials/create-python-package.md:160 +#: ../../tutorials/create-python-package.md:167 msgid "Notice that the code in the example.py module, has a few features:" msgstr "example.pyモジュールのコードには、いくつかの機能があることに注意してください:" -#: ../../tutorials/create-python-package.md:162 +#: ../../tutorials/create-python-package.md:169 msgid "It has a [numpy-style docstring](numpy-docstring)" msgstr "これは [numpyスタイルのdocstring](numpy-docstring) を持っています。" -#: ../../tutorials/create-python-package.md:163 +#: ../../tutorials/create-python-package.md:170 msgid "It uses [typing](type-hints)" msgstr "[typing](type-hints) を使用します。" -#: ../../tutorials/create-python-package.md:164 +#: ../../tutorials/create-python-package.md:171 msgid "" "At the top of the module, there is a docstring explaining what the module" " does." msgstr "" -#: ../../tutorials/create-python-package.md:166 +#: ../../tutorials/create-python-package.md:173 #, fuzzy msgid "" "Python supports different docstring formats. The most popular formats for" @@ -1401,26 +1413,26 @@ msgstr "" "Docstring[^numpydoc]、Google Style Docstring[^googledoc]、Epytext Style " "Docstring[^epytextdoc]です。" -#: ../../tutorials/create-python-package.md:168 +#: ../../tutorials/create-python-package.md:175 msgid "**pyOpenSci recommends using the NumPy Docstring convention.**" msgstr "**pyOpenSciは、NumPyのDocstring規約を使用することを推奨します。**" -#: ../../tutorials/create-python-package.md:170 +#: ../../tutorials/create-python-package.md:177 msgid "" "[Learn more about docstrings here](api-docstrings) for an overview of " "both topics." msgstr "" -#: ../../tutorials/create-python-package.md:199 +#: ../../tutorials/create-python-package.md:206 msgid "Python modules and the `__init__.py` file" msgstr "Pythonモジュールと `__init__.py` ファイル" -#: ../../tutorials/create-python-package.md:203 +#: ../../tutorials/create-python-package.md:210 #, fuzzy msgid "The word module refers to a `.py` file containing Python code." msgstr "モジュールという言葉を目にしたとき、私たちはPythonのコードを含む `.py` ファイルを指しています。" -#: ../../tutorials/create-python-package.md:205 +#: ../../tutorials/create-python-package.md:212 msgid "" "The `__init__.py` allows Python to recognize that a directory contains " "at least one module that may be imported and used in your code. A package" @@ -1429,31 +1441,32 @@ msgstr "" "`__init__.py` は、Pythonがディレクトリに少なくとも1つのモジュールが含まれていることを認識できるようにします。 " "パッケージは複数のモジュール [^python-modules] を持つことができます。" -#: ../../tutorials/create-python-package.md:210 +#: ../../tutorials/create-python-package.md:217 #, fuzzy msgid "Step 3: Optional -- Add code to your module" msgstr "ステップ3: モジュールにコードを追加する" -#: ../../tutorials/create-python-package.md:212 +#: ../../tutorials/create-python-package.md:219 msgid "" "If you want, add a second function to the `example.py` module. It can be " "a simple function. For example, write a second function that multiplies " "numbers." msgstr "" -#: ../../tutorials/create-python-package.md:215 +#: ../../tutorials/create-python-package.md:222 #, fuzzy msgid "Step 4: Check out the metadata in your `pyproject.toml` file" msgstr "ステップ 4: `pyproject.toml` ファイルのメタデータを修正する" -#: ../../tutorials/create-python-package.md:217 +#: ../../tutorials/create-python-package.md:224 msgid "" -"A `pyproject.toml` file stores metadata that provides instructions to " -"various tools interacting with it, including Hatch, which will build your" -" package. You can also specify metadata for your package." +"A [pyproject.toml](pyproject-toml) file stores metadata that provides " +"instructions to various tools interacting with it, including [Hatch](get-" +"to-know-hatch), which will build your package. You can also specify " +"metadata for your package." msgstr "" -#: ../../tutorials/create-python-package.md:219 +#: ../../tutorials/create-python-package.md:229 #, fuzzy msgid "" "You will learn more about the `pyproject.toml` format in the [next lesson" @@ -1463,27 +1476,27 @@ msgstr "" "`pyproject.toml` フォーマットについては、 [このファイルにメタデータや情報を追加する次のレッスン](pyproject-" "toml.md) で詳しく学びます。" -#: ../../tutorials/create-python-package.md:222 +#: ../../tutorials/create-python-package.md:232 msgid "" -"The metadata in your generated pyproject.toml is already setup for you " +"The metadata in your generated `pyproject.toml` is already setup for you " "using the information you provided the copier template above." msgstr "" -#: ../../tutorials/create-python-package.md:224 +#: ../../tutorials/create-python-package.md:234 msgid "Brief overview of the TOML file" msgstr "TOMLファイルの概要" -#: ../../tutorials/create-python-package.md:227 +#: ../../tutorials/create-python-package.md:237 msgid "" "[The TOML format](https://toml.io/en/) consists of tables and variables. " "Tables are sections of information denoted by square brackets:" msgstr "[TOMLフォーマット](https://toml.io/en/) は表と変数で構成されます。 表は角括弧で示される情報のセクションです:" -#: ../../tutorials/create-python-package.md:229 +#: ../../tutorials/create-python-package.md:239 msgid "`[this-is-a-table]`." msgstr "`[this-is-a-table]`." -#: ../../tutorials/create-python-package.md:231 +#: ../../tutorials/create-python-package.md:241 #, fuzzy msgid "" "Tables can contain variables within them defined by a variable name and " @@ -1493,16 +1506,17 @@ msgstr "" "テーブルには、変数名と `=` 記号で定義された変数を入れることができます。 例えば、`build-system` " "テーブルは以下の2(つの)変数を保持することが多いです:" -#: ../../tutorials/create-python-package.md:234 +#: ../../tutorials/create-python-package.md:244 +#, fuzzy msgid "" "`requires = `, which tells a build tool what tools it needs to install " "prior to building your package. In this case " -"[hatchling](https://pypi.org/project/hatchling/)" +"[hatchling](https://pypi.org/project/hatchling/)." msgstr "" "`requires=` は、ビルドツールに対して、パッケージをビルドする前にインス トールする必要があるツールを指示します。 この場合 " "[hatchling](https://pypi.org/project/hatchling/)" -#: ../../tutorials/create-python-package.md:236 +#: ../../tutorials/create-python-package.md:246 msgid "" "`build-backend = `, which is used to define the specific build-backend " "name, (in this example we are using `hatchling.build`)." @@ -1510,13 +1524,13 @@ msgstr "" "`build-backend = ` 、これは、特定のビルドバックエンド名を定義するために使われます、(この例では、 " "`hatchling.build` を使用しています)。" -#: ../../tutorials/create-python-package.md:245 +#: ../../tutorials/create-python-package.md:255 msgid "" "TOML organizes data structures, defining relationships within a " "configuration file." msgstr "TOMLはデータ構造を整理し、設定ファイル内の関係を定義します。" -#: ../../tutorials/create-python-package.md:248 +#: ../../tutorials/create-python-package.md:258 #, fuzzy msgid "[Learn more about the pyproject.toml format here.](pyprojecttoml-metadata)" msgstr "" @@ -1524,30 +1538,30 @@ msgstr "" "metadata)[pyproject.tomlフォーマットの詳細はこちら。](../package-structure-code" "/pyproject-toml-python-package-metadata)" -#: ../../tutorials/create-python-package.md:251 +#: ../../tutorials/create-python-package.md:261 msgid "" "Open up the `pyproject.toml` file that Hatch created in your favorite " "text editor. It should look something like the example below." msgstr "Hatchが作成した `pyproject.toml` ファイルをお好みのテキストエディタで開いてください。 下の例のようになるはずです。" -#: ../../tutorials/create-python-package.md:252 +#: ../../tutorials/create-python-package.md:262 msgid "" "Make sure the package version, package name, and author name look " "correct. The email is optional." msgstr "" -#: ../../tutorials/create-python-package.md:290 +#: ../../tutorials/create-python-package.md:300 msgid "" "At the bottom of the template-generated `pyproject.toml` file, you will " "see a section that defines Hatch environments. We will cover Hatch " "environments in a later lesson." msgstr "" -#: ../../tutorials/create-python-package.md:292 +#: ../../tutorials/create-python-package.md:302 msgid "The bare minimum needed in a pyproject.toml file" msgstr "pyproject.tomlファイルに最低限必要なもの" -#: ../../tutorials/create-python-package.md:295 +#: ../../tutorials/create-python-package.md:305 #, fuzzy msgid "" "The core information that you need in a `pyproject.toml` file to publish " @@ -1558,47 +1572,47 @@ msgstr "" "PyPIで公開するために `pyproject.toml` ファイルに必要な情報は、 **パッケージ名** と **バージョン** です。 " "しかし、 `pyproject.toml` ファイルの早い段階でメタデータを具体化することをお勧めします。" -#: ../../tutorials/create-python-package.md:297 +#: ../../tutorials/create-python-package.md:307 #, fuzzy msgid "" "Once you have your project metadata in the `pyproject.toml` file, you " "will rarely update it." msgstr "一度pyproject.tomlファイルにプロジェクトのメタデータがあれば、それを更新することはほとんどありません。次のレッスンでは、このファイルにさらにメタデータと構造を追加します。" -#: ../../tutorials/create-python-package.md:301 +#: ../../tutorials/create-python-package.md:311 msgid "Step 5: Install your package locally" msgstr "ステップ 5: パッケージをローカルにインストールする" -#: ../../tutorials/create-python-package.md:303 +#: ../../tutorials/create-python-package.md:313 #, fuzzy msgid "At this point, you should have:" msgstr "この時点であなたは以下を持っているはずです:" -#: ../../tutorials/create-python-package.md:305 +#: ../../tutorials/create-python-package.md:315 msgid "A project directory structure with a `pyproject.toml` file at the root" msgstr "`pyproject.toml` ファイルをルートに持つプロジェクトのディレクトリ構造" -#: ../../tutorials/create-python-package.md:306 +#: ../../tutorials/create-python-package.md:316 msgid "A package directory containing an empty `__init__.py` file and" msgstr "空の `__init__.py` ファイルを含むパッケージ・ディレクトリと" -#: ../../tutorials/create-python-package.md:307 +#: ../../tutorials/create-python-package.md:317 #, fuzzy msgid "At least one Python module (e.g. `example.py`)" msgstr "少なくとも1つのPythonモジュール (e.g. `add_numbers.py`)" -#: ../../tutorials/create-python-package.md:309 +#: ../../tutorials/create-python-package.md:319 msgid "You are now ready to install (and build) your Python package!" msgstr "これで Python パッケージをインストール（ビルド）する準備ができました！" -#: ../../tutorials/create-python-package.md:311 +#: ../../tutorials/create-python-package.md:321 #, fuzzy msgid "" "While you can do this using Hatch, we will use pip for this lesson, so " "you can see how to install your tool into your preferred environment." msgstr "hatchを使ってもできますが、このレッスンではpipを使います、そうすれば、あなたの好みの環境にツールをインストールする方法を見ることができます。" -#: ../../tutorials/create-python-package.md:313 +#: ../../tutorials/create-python-package.md:323 #, fuzzy msgid "" "First, open your preferred shell (Windows users may use something like " @@ -1608,38 +1622,38 @@ msgstr "" "まず、お好みのシェルを開き (Windowsユーザーはgitbashのようなものを使っているかもしれません) " "、まだプロジェクトディレクトリにいなければ、 `cd` してください。" -#: ../../tutorials/create-python-package.md:314 +#: ../../tutorials/create-python-package.md:324 msgid "Activate the Python environment that you wish to use." msgstr "使用したいPython環境をアクティブにします。" -#: ../../tutorials/create-python-package.md:315 +#: ../../tutorials/create-python-package.md:325 msgid "Run `python -m pip install -e .`" msgstr "`python -m pip install -e .` を実行します。" -#: ../../tutorials/create-python-package.md:317 -#: ../../tutorials/create-python-package.md:550 -#: ../../tutorials/create-python-package.md:557 -#: ../../tutorials/get-to-know-hatch.md:197 ../../tutorials/intro.md:242 -#: ../../tutorials/publish-pypi.md:9 ../../tutorials/publish-pypi.md:183 -#: ../../tutorials/publish-pypi.md:356 ../../tutorials/pyproject-toml.md:735 +#: ../../tutorials/create-python-package.md:327 +#: ../../tutorials/create-python-package.md:560 +#: ../../tutorials/create-python-package.md:567 +#: ../../tutorials/get-to-know-hatch.md:199 ../../tutorials/intro.md:246 +#: ../../tutorials/publish-pypi.md:9 ../../tutorials/publish-pypi.md:185 +#: ../../tutorials/publish-pypi.md:358 ../../tutorials/pyproject-toml.md:744 msgid "Todo" msgstr "Todo" -#: ../../tutorials/create-python-package.md:318 +#: ../../tutorials/create-python-package.md:328 msgid "Add this back in when the lesson is published" msgstr "レッスンが公開されたら、これを追加してください。" -#: ../../tutorials/create-python-package.md:319 +#: ../../tutorials/create-python-package.md:329 msgid "" "Activate the Python environment that you wish to use. If you need help " "with working with virtual environments check out this lesson (add link)." msgstr "使用したいPython環境をアクティブにします。 仮想環境での作業で助けが必要な場合は、このレッスンをチェックしてください（リンクを追加）。" -#: ../../tutorials/create-python-package.md:345 +#: ../../tutorials/create-python-package.md:355 msgid "What does `python -m pip install -e .` do?" msgstr "`python -m pip install -e .` は何をしているのか？" -#: ../../tutorials/create-python-package.md:348 +#: ../../tutorials/create-python-package.md:358 #, fuzzy msgid "" "`python -m pip install -e .` installs your package into the current " @@ -1655,21 +1669,21 @@ msgstr "" " 編集可能モードの重要な注意点のひとつは、コードを更新するたびに、そのコードが更新されるということです、 " "その場合、Pythonを再起動する必要があるかもしれません。" -#: ../../tutorials/create-python-package.md:353 +#: ../../tutorials/create-python-package.md:363 msgid "" "If you wish to install the package regularly (not in editable mode) you " "can use:" msgstr "(編集可能モードではなく) 定期的にパッケージをインストールしたい場合は、次のようにします:" -#: ../../tutorials/create-python-package.md:356 +#: ../../tutorials/create-python-package.md:366 msgid "`python -m pip install . `" msgstr "`python -m pip install . `" -#: ../../tutorials/create-python-package.md:358 +#: ../../tutorials/create-python-package.md:368 msgid "**Using `python -m` when calling `pip`**" msgstr "**`pip` を呼び出す際に `python -m` を使用する**" -#: ../../tutorials/create-python-package.md:360 +#: ../../tutorials/create-python-package.md:370 msgid "" "Above, you use`python -m` to call the version of pip installed into your " "current active environment. `python -m` is important to ensure that you " @@ -1678,7 +1692,7 @@ msgstr "" "上記では、 `python -m` を使用して、現在アクティブな環境にインストールされている pip のバージョンを呼び出します。 `python" " -m` は、現在の環境にインストールされているバージョンの pip を呼び出していることを確認するために重要です。" -#: ../../tutorials/create-python-package.md:364 +#: ../../tutorials/create-python-package.md:374 msgid "" "IMPORTANT: pip can also be used to install packages from PyPI. However, " "in this case, you are telling pip to install your package from a local " @@ -1689,11 +1703,11 @@ msgstr "" "重要: " "pipはPyPIからパッケージをインストールするためにも使用できます。しかし、この場合、`.`を使用してローカルフォルダからパッケージをインストールするようpipに指示しています。`.`の代わりにコンピュータ上のプロジェクトディレクトリへのパスを指定することもできます。`.`はpipに現在の作業ディレクトリを使用するよう指示します。" -#: ../../tutorials/create-python-package.md:367 +#: ../../tutorials/create-python-package.md:377 msgid "Look for pyospackage in your environment" msgstr "あなたの環境でpyospackageを探す" -#: ../../tutorials/create-python-package.md:369 +#: ../../tutorials/create-python-package.md:379 #, fuzzy msgid "" "Once you have installed your package, you can view it in your current " @@ -1703,7 +1717,7 @@ msgstr "" "パッケージをインストールしたら、現在の環境でそれを見ることができます。 `venv` または `conda` を使用している場合、 `pip` " "list で現在インストールされているパッケージを確認することができます。" -#: ../../tutorials/create-python-package.md:373 +#: ../../tutorials/create-python-package.md:383 #, fuzzy msgid "" "Note that because `pyospackage` is installed in editable mode (`-e`), pip" @@ -1712,11 +1726,11 @@ msgstr "" "pyospackageは編集可能モード (`-e`) " "でインストールされるため、pipはプロジェクトのコードへのディレクトリパスを表示することに注意してください。" -#: ../../tutorials/create-python-package.md:401 +#: ../../tutorials/create-python-package.md:411 msgid "Step 6: Test out your new package" msgstr "ステップ 6: 新しいパッケージをテストする" -#: ../../tutorials/create-python-package.md:403 +#: ../../tutorials/create-python-package.md:413 msgid "" "After installing your package, type “python” at the command prompt in " "your chosen terminal to start a Python session in your active Python " @@ -1725,36 +1739,36 @@ msgstr "" "パッケージをインストールした後、選択したターミナルのコマンドプロンプトで“python”と入力して、アクティブなPython環境でPythonセッションを開始します。パッケージをインストールしたら、選択したターミナルのコマンドプロンプトで" " \"python\" と入力し、アクティブなPython環境でPythonセッションを開始します。" -#: ../../tutorials/create-python-package.md:406 +#: ../../tutorials/create-python-package.md:416 #, fuzzy msgid "You can now import your package and access the `add_numbers` function." msgstr "これでパッケージをインポートして `add_num` 関数にアクセスできます。" -#: ../../tutorials/create-python-package.md:418 +#: ../../tutorials/create-python-package.md:428 msgid "Installing packages from GitHub" msgstr "GitHubからパッケージをインストールする" -#: ../../tutorials/create-python-package.md:420 +#: ../../tutorials/create-python-package.md:430 msgid "" "If you wish to share your code without publishing to PyPI you can always " "install packages directly from GitHub using the syntax:" msgstr "PyPIに公開せずにコードを共有したい場合は、いつでも構文を使ってGitHubから直接パッケージをインストールできます:" -#: ../../tutorials/create-python-package.md:427 +#: ../../tutorials/create-python-package.md:437 msgid "To make your package GitHub installable, you can:" msgstr "GitHubのパッケージをインストール可能にするには、次のようにします:" -#: ../../tutorials/create-python-package.md:429 +#: ../../tutorials/create-python-package.md:439 msgid "Create a new GitHub repository" msgstr "新しいGitHubリポジトリを作成する" -#: ../../tutorials/create-python-package.md:430 +#: ../../tutorials/create-python-package.md:440 msgid "" "Push the contents of the project directory that you created above, to " "GitHub" msgstr "上記で作成したプロジェクトディレクトリの内容をGitHubにプッシュします" -#: ../../tutorials/create-python-package.md:431 +#: ../../tutorials/create-python-package.md:441 msgid "" "Finally install the package from GitHub using the command above. When you" " use the command above, don't forget to substitute the user, repo, and " @@ -1763,34 +1777,34 @@ msgstr "" "最後に、上記のコマンドを使ってGitHubからパッケージをインストールします。 " "上記のコマンドを使用する際は、user、repo、branch_or_tag を特定の値に置き換えることをお忘れなく。" -#: ../../tutorials/create-python-package.md:433 +#: ../../tutorials/create-python-package.md:443 msgid "" "For instance below you install the pyospackage from the main branch of " "the pyOpenSci repository." msgstr "例えば、以下のようにpyOpenSciリポジトリのmainブランチからpyospackageをインストールします。" -#: ../../tutorials/create-python-package.md:436 +#: ../../tutorials/create-python-package.md:446 msgid "`python -m pip install git+https://github.com/user/repo.git@branch_or_tag`" msgstr "`python -m pip install git+https://github.com/user/repo.git@branch_or_tag`" -#: ../../tutorials/create-python-package.md:440 +#: ../../tutorials/create-python-package.md:450 msgid "Congratulations! You created your first Python package" msgstr "おめでとうございます！ あなたは最初のPythonパッケージを作成しました" -#: ../../tutorials/create-python-package.md:442 +#: ../../tutorials/create-python-package.md:452 #, fuzzy msgid "" "You have now created a Python package that you can install into any " "Python environment." msgstr "やったね！ これでどんなPython環境にもインストールできるPythonパッケージができました。" -#: ../../tutorials/create-python-package.md:447 +#: ../../tutorials/create-python-package.md:457 msgid "" "Add a [README file](add-readme.md) and [LICENSE](add-license-coc.md) to " "your package" msgstr "[READMEファイル](add-readme.md) と [LICENSE](add-license-coc.md) をパッケージに追加する。" -#: ../../tutorials/create-python-package.md:448 +#: ../../tutorials/create-python-package.md:458 msgid "" "[Add more metadata to your `pyproject.toml`](pyproject-toml.md) file to " "support PyPI publication." @@ -1798,7 +1812,7 @@ msgstr "" "PyPI での公開をサポートするために [ `pyproject.toml` ファイルにメタデータを追加します。](pyproject-" "toml.md)" -#: ../../tutorials/create-python-package.md:449 +#: ../../tutorials/create-python-package.md:459 msgid "" "[Learn how to build your package distribution](publish-pypi) files " "(**sdist** and **wheel**) and publish to **test PyPI**." @@ -1806,43 +1820,43 @@ msgstr "" "[パッケージ配布ファイルをビルド](publish-pypi) して (**sdist** と **wheel**) 、 **test " "PyPI** に公開する方法を学びます。" -#: ../../tutorials/create-python-package.md:450 +#: ../../tutorials/create-python-package.md:460 msgid "" "Finally you will learn how to [publish to **conda-forge**](publish-conda-" "forge) from **PyPI**." msgstr "**PyPI** から [**conda-forge**](publish-conda-forge) に公開する方法を学んでください。" -#: ../../tutorials/create-python-package.md:454 +#: ../../tutorials/create-python-package.md:464 msgid "About the Python package directory structure" msgstr "Pythonパッケージのディレクトリ構造について" -#: ../../tutorials/create-python-package.md:456 +#: ../../tutorials/create-python-package.md:466 msgid "" "To make your Python code installable you need to create a specific " "directory structure with the following elements:" msgstr "Pythonコードをインストール可能にするには、以下の要素を含む特定のディレクトリ構造を作成する必要があります:" -#: ../../tutorials/create-python-package.md:458 +#: ../../tutorials/create-python-package.md:468 msgid "A `pyproject.toml` file." msgstr "`pyproject.toml` ファイル。" -#: ../../tutorials/create-python-package.md:459 +#: ../../tutorials/create-python-package.md:469 msgid "A specific directory structure." msgstr "特定のディレクトリ構造。" -#: ../../tutorials/create-python-package.md:460 +#: ../../tutorials/create-python-package.md:470 msgid "Some code." msgstr "いくつかのコード。" -#: ../../tutorials/create-python-package.md:461 +#: ../../tutorials/create-python-package.md:471 msgid "An `__init__.py` file in your code directory." msgstr "コードディレクトリの `__init__.py` ファイル。" -#: ../../tutorials/create-python-package.md:463 +#: ../../tutorials/create-python-package.md:473 msgid "The directory structure you'll create in this lesson will look like this:" msgstr "このレッスンで作成するディレクトリ構造は次のようになります:" -#: ../../tutorials/create-python-package.md:478 +#: ../../tutorials/create-python-package.md:488 msgid "" "Diagram showing the basic steps to creating an installable package. There" " are 4 boxes with arrows pointing towards the right. The boxes read, your" @@ -1853,7 +1867,7 @@ msgstr "" "ボックスは、あなたのコード、パッケージ構造の作成、pyproject.tomlへのメタデータの追加、およびpip " "installパッケージを読み込みます。" -#: ../../tutorials/create-python-package.md:480 +#: ../../tutorials/create-python-package.md:490 #, fuzzy msgid "" "Once you have the basic items of a Python package (code, metadata and a " @@ -1861,15 +1875,15 @@ msgid "" "environment on your computer." msgstr "やったね！ これでどんなPython環境にもインストールできるPythonパッケージができました。" -#: ../../tutorials/create-python-package.md:483 +#: ../../tutorials/create-python-package.md:493 msgid "About the basic package directory structure" msgstr "基本パッケージのディレクトリ構造について" -#: ../../tutorials/create-python-package.md:485 +#: ../../tutorials/create-python-package.md:495 msgid "Notice a few things about the above layout:" msgstr "上記のレイアウトについて、いくつかの点に注目してください:" -#: ../../tutorials/create-python-package.md:487 +#: ../../tutorials/create-python-package.md:497 msgid "" "Your package code lives within a `src/packagename` directory. We suggest " "that you use `src` (short for **source code**) directory as it [ensures " @@ -1883,7 +1897,7 @@ msgstr "" "structure.html#the-src-layout-and-testing) `src`（ **source code** " "の略）ディレクトリを使用することをお勧めします。" -#: ../../tutorials/create-python-package.md:488 +#: ../../tutorials/create-python-package.md:498 msgid "" "Within the `src` directory you have a package directory called " "`pyospackage`. Use the name of your package for that directory name. This" @@ -1893,7 +1907,7 @@ msgstr "" "`src` ディレクトリの中に `pyospackage` というパッケージディレクトリがあります。 ディレクトリ名にはパッケージ名を使用します。" " これは、インストール後にPythonコードでパッケージをインポートする際の名前になります。" -#: ../../tutorials/create-python-package.md:489 +#: ../../tutorials/create-python-package.md:499 msgid "" "In your package directory, you have an `__init__.py` file and all of your" " Python modules. You will learn more about the `__init__.py` file below." @@ -1901,11 +1915,11 @@ msgstr "" "パッケージディレクトリには `__init__.py` ファイルと Python モジュールがあります。以下に `__init__.py` " "ファイルについて詳しく説明します。" -#: ../../tutorials/create-python-package.md:490 +#: ../../tutorials/create-python-package.md:500 msgid "The `pyproject.toml` file lives at the root directory of your package." msgstr "`pyproject.toml` ファイルはパッケージのルートディレクトリにあります。" -#: ../../tutorials/create-python-package.md:491 +#: ../../tutorials/create-python-package.md:501 msgid "" "The name of the root directory for the package is **pyospackage** which " "is the name of the package. This is not a requirement but you will often " @@ -1915,11 +1929,11 @@ msgstr "" "パッケージのルートディレクトリの名前は、パッケージ名である **pyospackage** です。これは必須ではありませんが、GitHub / " "GitLabのリポジトリ名とルートディレクトリ名がパッケージ名と同じであることをよく見かけます。" -#: ../../tutorials/create-python-package.md:493 +#: ../../tutorials/create-python-package.md:503 msgid "What is an `__init__.py` file?" msgstr "`__init__.py` ファイルとは何ですか？" -#: ../../tutorials/create-python-package.md:495 +#: ../../tutorials/create-python-package.md:505 msgid "" "The `__init__.py` file tells Python that a directory should be treated as" " a Python package. As such, a directory with an `__init__.py` file can be" @@ -1930,32 +1944,32 @@ msgstr "" "このように、`__init__.py` ファイルがあるディレクトリは Python に直接インポートすることができます。 Python " "に認識させるために `__init__.py` ファイルにコードを記述する必要はありません; 空であることもあります。" -#: ../../tutorials/create-python-package.md:499 +#: ../../tutorials/create-python-package.md:509 msgid "" "For example, following the file structure example above which has an " "`__init__.py` file within it, you can run:" msgstr "例えば、 `__init__.py` ファイルを持つ上記のファイル構造の例に従って、次のように実行します:" -#: ../../tutorials/create-python-package.md:505 -#: ../../tutorials/pyproject-toml.md:53 +#: ../../tutorials/create-python-package.md:515 +#: ../../tutorials/pyproject-toml.md:56 msgid "What is a pyproject.toml file?" msgstr "pyproject.tomlファイルとは何ですか？" -#: ../../tutorials/create-python-package.md:507 +#: ../../tutorials/create-python-package.md:517 msgid "The **pyproject.toml** file is:" msgstr "**pyproject.toml** ファイルは:" -#: ../../tutorials/create-python-package.md:509 +#: ../../tutorials/create-python-package.md:519 msgid "" "Where you define your project's metadata (including its name, authors, " "license, etc)" msgstr "プロジェクトのメタデータ (名前、作者、ライセンスなど) を定義します。" -#: ../../tutorials/create-python-package.md:510 +#: ../../tutorials/create-python-package.md:520 msgid "Where you define dependencies (the packages that it depends on)" msgstr "依存関係 (依存するパッケージ) を定義します。" -#: ../../tutorials/create-python-package.md:511 +#: ../../tutorials/create-python-package.md:521 msgid "" "Used to specify and configure what build backend you want to use to " "[build your package](../package-structure-code/python-package-" @@ -1964,7 +1978,7 @@ msgstr "" "[パッケージのビルド](../package-structure-code/python-package-distribution-files-" "sdist-wheel) に使用するビルドバックエンドを指定し、設定します。" -#: ../../tutorials/create-python-package.md:513 +#: ../../tutorials/create-python-package.md:523 msgid "" "After the `__init__.py` and `pyproject.toml` files have been added, your " "package can be built and distributed as an installable Python package " @@ -1977,19 +1991,19 @@ msgstr "" "`pyproject.toml` " "ファイルには、パッケージをインストールするために、以下のようないくつかの基本的な項目が定義されている必要があることに注意してください:" -#: ../../tutorials/create-python-package.md:519 +#: ../../tutorials/create-python-package.md:529 msgid "The `build-backend` that you want to use," msgstr "使用したい `build-backend` を指定します、" -#: ../../tutorials/create-python-package.md:520 +#: ../../tutorials/create-python-package.md:530 msgid "The project `name` and `version`." msgstr "プロジェクトの `name` と `version` を指定する。" -#: ../../tutorials/create-python-package.md:522 +#: ../../tutorials/create-python-package.md:532 msgid "Why the pyproject.toml file is important" msgstr "pyproject.tomlファイルが重要な理由" -#: ../../tutorials/create-python-package.md:525 +#: ../../tutorials/create-python-package.md:535 #, fuzzy msgid "" "The `pyproject.toml` file replaces some of the functionality of both the " @@ -1999,7 +2013,7 @@ msgstr "" "`pyproject.toml` ファイルは `setup.py` ファイルと `setup.cfg` ファイルの機能の一部を置き換えます。 " "`pyproject.toml` がないパッケージをpipインストールしようとすると、以下のエラーが発生します:" -#: ../../tutorials/create-python-package.md:535 +#: ../../tutorials/create-python-package.md:545 #, fuzzy msgid "" "If your project already has a `setup.py` file, Hatch can be used to " @@ -2008,7 +2022,7 @@ msgstr "" "プロジェクトが既に `setup.py` ファイルを定義している場合、ハッチを使用して自動的に `pyproject.toml` " "を作成することができます。" -#: ../../tutorials/create-python-package.md:536 +#: ../../tutorials/create-python-package.md:546 #, fuzzy msgid "" "See [Using Hatch to Migrate setup.py to a pyproject.toml](setup-py-to-" @@ -2017,13 +2031,13 @@ msgstr "" "[Hatchを使ってsetup.pyをpyproject.tomlに移行する ](setup-py-to-pyproject-toml.md) " "を参照" -#: ../../tutorials/create-python-package.md:551 +#: ../../tutorials/create-python-package.md:561 msgid "" "Is it clear where to add commands? Bash vs. Python console Bash vs. Zsh " "is different" msgstr "コマンドを追加する場所は明確ですか？ BashとPythonのコンソールの違い BashとZshの違い" -#: ../../tutorials/create-python-package.md:553 +#: ../../tutorials/create-python-package.md:563 msgid "" "ADD: note about what makes something \"package worthy\", with a common " "misconception being that a package should be production-ready code that's" @@ -2034,12 +2048,12 @@ msgstr "" "追加: 何をもって \"パッケージに値する\" とするのかについて、 " "一般的な誤解は、パッケージは幅広いオーディエンスにとって価値のある、生産可能なコードであるべきだというものです。これはPythonに蔓延している誤解ではないかもしれませんが、パッケージがどのようなもので構成されるかを簡単に説明することは役に立つでしょう。" -#: ../../tutorials/create-python-package.md:554 +#: ../../tutorials/create-python-package.md:564 #, fuzzy msgid "They can use a codespace to complete this lesson too." msgstr "**このレッスンを完了するために必要なもの**" -#: ../../tutorials/create-python-package.md:558 +#: ../../tutorials/create-python-package.md:568 msgid "" "When this lesson exists, uncomment this admonition You will learn how to " "automate defining a package version using git tags in the version and " @@ -2048,23 +2062,23 @@ msgstr "" "このレッスンが存在する場合、この戒めのコメントを解除します。 このレッスンでは、git " "タグを使ってパッケージのバージョン定義を自動化する方法と、パッケージのリリースについて学びます。" -#: ../../tutorials/create-python-package.md:542 +#: ../../tutorials/create-python-package.md:552 msgid "[Carpentries shell lesson](https://swcarpentry.github.io/shell-novice/)" msgstr "[Carpentries shell lesson](https://swcarpentry.github.io/shell-novice/)" -#: ../../tutorials/create-python-package.md:546 +#: ../../tutorials/create-python-package.md:556 msgid "[Numpy style docs](https://numpydoc.readthedocs.io/en/latest/format.html)" msgstr "[Numpy style docs](https://numpydoc.readthedocs.io/en/latest/format.html)" -#: ../../tutorials/create-python-package.md:545 +#: ../../tutorials/create-python-package.md:555 msgid "[Google docstring style](https://google.github.io/styleguide/pyguide.html)" msgstr "[Google docstring style](https://google.github.io/styleguide/pyguide.html)" -#: ../../tutorials/create-python-package.md:547 +#: ../../tutorials/create-python-package.md:557 msgid "[epydoc](https://epydoc.sourceforge.net/epytext.html)" msgstr "[epydoc](https://epydoc.sourceforge.net/epytext.html)" -#: ../../tutorials/create-python-package.md:544 +#: ../../tutorials/create-python-package.md:554 msgid "" "[Python module " "docs](https://docs.python.org/3/tutorial/modules.html#packages)" @@ -2112,128 +2126,129 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:23 msgid "" "Welcome to your shiny new package! This page will help you get started " -"with using Hatch to run tests, build and check your package, and build " -"your documentation." +"with using [Hatch](get-to-know-hatch) to run tests, build and check your " +"package, and build your documentation." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:25 +#: ../../tutorials/develop-python-package-hatch.md:27 +#, python-brace-format msgid "" -"To begin, have a look at the `pyproject.toml` file in your package " -"directory. This file contains the configuration for your package. This " -"file is written using a .toml format. [You can learn more about toml " -"here.](https://www.pyopensci.org/python-package-guide/package-structure-" -"code/pyproject-toml-python-package-metadata.html) Here's the TL&DR:" +"To begin, have a look at the [pyproject.toml](pyproject-toml) file in " +"your package directory. This file contains the configuration for your " +"package and is written using {term}`TOML` format. Here's the TL&DR:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:27 +#: ../../tutorials/develop-python-package-hatch.md:31 msgid "Each `[]` section in the toml file is called a table." msgstr "tomlファイルの各 `[]` セクションはテーブルと呼ばれます。" -#: ../../tutorials/develop-python-package-hatch.md:28 +#: ../../tutorials/develop-python-package-hatch.md:32 msgid "You can nest tables with double brackets like this`[[]]`" msgstr "このように二重括弧`[[]]`でテーブルをネストできます" -#: ../../tutorials/develop-python-package-hatch.md:29 +#: ../../tutorials/develop-python-package-hatch.md:33 msgid "" "Tables contain information about a certain thing that you want to " "configure." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:32 +#: ../../tutorials/develop-python-package-hatch.md:36 msgid "" "You can configure Hatch to use UV by default for environment management. " "UV is a package manager built in Rust. It is fast and will significantly " "speed up environment creation." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:34 +#: ../../tutorials/develop-python-package-hatch.md:38 msgid "" "To use UV with Hatch, configure Hatch in the \"tools\" section of your " "`pyproject.toml` file." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:42 +#: ../../tutorials/develop-python-package-hatch.md:46 msgid "" "Using Hatch for developing, building, and maintaining your pure Python " "package" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:44 +#: ../../tutorials/develop-python-package-hatch.md:48 +#, python-brace-format msgid "" -"In the pyOpenSci Python package template, we have set up Hatch " -"environments. You will notice at the bottom of the file, a [hatch " -"environment](https://hatch.pypa.io/1.13/environment/) section, that looks" -" like this:" +"In the pyOpenSci Python package template, we have set up {term}`Hatch " +"environment` definitions. You will notice at the bottom of the file, a " +"[hatch environment](https://hatch.pypa.io/1.13/environment/) section, " +"that looks like this:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:52 +#: ../../tutorials/develop-python-package-hatch.md:59 msgid "" "Hatch allows you to configure and run environments and scripts similar to" " a workflow tool like tox or nox." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:55 +#: ../../tutorials/develop-python-package-hatch.md:62 msgid "" "Hatch defaults to using `venv` to manage environments. However, you can " "configure it to use other environment tools, such as conda or mamba." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:57 +#: ../../tutorials/develop-python-package-hatch.md:64 msgid "" "[Read the hatch documentation to learn more about environments. " "](https://hatch.pypa.io/1.13/tutorials/environment/basic-usage/)" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:61 +#: ../../tutorials/develop-python-package-hatch.md:68 msgid "" "Below is the Hatch environment used to build and test your package. " "Anytime you see: `tool.hatch.envs.test`, it tells Hatch:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:64 +#: ../../tutorials/develop-python-package-hatch.md:71 msgid "" "\"Hey, Hatch, this is the definition for an environment.`test` is the " "name of the environment that I want you to create.\"" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:66 +#: ../../tutorials/develop-python-package-hatch.md:73 msgid "So `tool.hatch.envs.build` will create an environment called `build`." msgstr "つまり `tool.hatch.envs.build` は `build` という環境を作成します。" -#: ../../tutorials/develop-python-package-hatch.md:68 +#: ../../tutorials/develop-python-package-hatch.md:75 msgid "" "Below the environment \"declaration,\" you can see the definition of what" " should be in that environment." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:70 +#: ../../tutorials/develop-python-package-hatch.md:77 #, fuzzy msgid "A Hatch environment to build your package" msgstr "パッケージのインストール" -#: ../../tutorials/develop-python-package-hatch.md:72 +#: ../../tutorials/develop-python-package-hatch.md:79 +#, python-brace-format msgid "" -"Below is a Hatch environment definition that you will find in your [new " -"project's pyproject.toml file](create-python-package). It is set up to " -"[build your package's](build-package) distribution files ([source " -"distribution](python-source-distribution) and [wheel](python-wheel))." +"Below is a Hatch environment definition that you will find in your new " +"project's [pyproject.toml](pyproject-toml) file. It is set up to build " +"your package's {term}`Distribution files` ({term}`Source distribution " +"(sdist)` and {term}`Wheel (.whl)`)." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:74 +#: ../../tutorials/develop-python-package-hatch.md:84 +#, python-brace-format msgid "" -"Notice that the environment definition declares two dependencies: `pip` " -"and `twine`, which the environment needs to run successfully. This " -"declaration is similar to declaring dependencies for your package at the " -"top of your `pyproject.toml`. This section tells Hatch to create a new " -"VENV with pip and twine installed." +"Notice that the environment definition declares two {term}`Dependencies`:" +" `pip` and `twine`, which the environment needs to run successfully. This" +" declaration is similar to declaring dependencies for your package at the" +" top of your [pyproject.toml](pyproject-toml)." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:86 +#: ../../tutorials/develop-python-package-hatch.md:99 #, fuzzy msgid "Hatch will install your package in editable mode by default" msgstr "インタラクティブな開発のために編集可能モードでパッケージをインストールする方法" -#: ../../tutorials/develop-python-package-hatch.md:87 +#: ../../tutorials/develop-python-package-hatch.md:100 msgid "" "Notice the `detached = True` flag at the bottom of the environment. By " "default, hatch will install your package in editable mode into any " @@ -2241,145 +2256,148 @@ msgid "" "package into the environment." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:91 +#: ../../tutorials/develop-python-package-hatch.md:104 msgid "Hatch scripts" msgstr "Hatchスクリプト" -#: ../../tutorials/develop-python-package-hatch.md:93 -msgid "Hatch supports defining scripts that run in specific Hatch environments." +#: ../../tutorials/develop-python-package-hatch.md:106 +#, fuzzy, python-brace-format +msgid "" +"Hatch supports defining {term}`Script (Hatch)` commands that run in " +"specific Hatch environments." msgstr "Hatchは特定のHatch環境で実行されるスクリプトの定義をサポートしています。" -#: ../../tutorials/develop-python-package-hatch.md:95 +#: ../../tutorials/develop-python-package-hatch.md:109 msgid "" "Above, you have defined a new environment called 'build' that Hatch will " "create as a virtual environment (venv). Because `detached = True` in that" " environment, Hatch won't install your package into it." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:97 +#: ../../tutorials/develop-python-package-hatch.md:111 msgid "" "You can then use that environment to run \"scripts\". The definition " "below tells Hatch to run the following scripts in the build environment." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:99 +#: ../../tutorials/develop-python-package-hatch.md:113 msgid "`[tool.hatch.envs.build.scripts]`" msgstr "`[tool.hatch.envs.build.scripts]`" -#: ../../tutorials/develop-python-package-hatch.md:101 +#: ../../tutorials/develop-python-package-hatch.md:115 msgid "You define this `scripts` to run using the following syntax, where:" msgstr "この `scripts` を実行するために次の構文を使用して定義します:" -#: ../../tutorials/develop-python-package-hatch.md:103 +#: ../../tutorials/develop-python-package-hatch.md:117 msgid "`tool.hatch`: Alerts Hatch that this table is for Hatch to use" msgstr "`tool.hatch`: このテーブルがHatch用であることをHatchに通知します" -#: ../../tutorials/develop-python-package-hatch.md:104 +#: ../../tutorials/develop-python-package-hatch.md:118 msgid "`envs.build`: Use the defined build environment." msgstr "`envs.build`: 定義されたビルド環境を使用します。" -#: ../../tutorials/develop-python-package-hatch.md:105 +#: ../../tutorials/develop-python-package-hatch.md:119 msgid "" "`scripts`: Define what scripts to run. In this case, Hatch will run shell" " scripts." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:108 +#: ../../tutorials/develop-python-package-hatch.md:122 msgid "" "Below is the `build.scripts` table that defines 3 shell commands to be " "run:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:110 +#: ../../tutorials/develop-python-package-hatch.md:124 msgid "`pip check` # verifies your dependencies" msgstr "`pip check` # 依存関係を検証します" -#: ../../tutorials/develop-python-package-hatch.md:111 +#: ../../tutorials/develop-python-package-hatch.md:125 #, fuzzy msgid "`hatch build --clean` # build your packages distribution files." msgstr "ステップ 2: パッケージのsdistとwheelディストリビューションをビルドする" -#: ../../tutorials/develop-python-package-hatch.md:112 +#: ../../tutorials/develop-python-package-hatch.md:126 msgid "" "`twine check dist/*` # use twine to check that your package's sdist " "(source distribution) is ok." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:126 +#: ../../tutorials/develop-python-package-hatch.md:140 msgid "" "Hatch, by default, will install your package in editable mode into any " "virtual environment (venv) that it creates. If `detached=True` is set, " "then it will skip that step." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:129 +#: ../../tutorials/develop-python-package-hatch.md:143 #, fuzzy msgid "Running the build script" msgstr "テストの実行" -#: ../../tutorials/develop-python-package-hatch.md:131 +#: ../../tutorials/develop-python-package-hatch.md:145 msgid "You can run the build script and build your package like this:" msgstr "ビルドスクリプトを実行し、次のようにパッケージをビルドできます:" -#: ../../tutorials/develop-python-package-hatch.md:133 +#: ../../tutorials/develop-python-package-hatch.md:147 msgid "`hatch run build:check`" msgstr "`hatch run build:check`" -#: ../../tutorials/develop-python-package-hatch.md:135 +#: ../../tutorials/develop-python-package-hatch.md:149 msgid "" "This step updates the build environment and then builds and checks the " "output distributions of your package." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:137 +#: ../../tutorials/develop-python-package-hatch.md:151 msgid "You can enter the build environment in your shell to check it out:" msgstr "シェルでビルド環境に入って確認できます:" -#: ../../tutorials/develop-python-package-hatch.md:143 +#: ../../tutorials/develop-python-package-hatch.md:157 msgid "If you run `pip list` in the environment, twine will be there:" msgstr "環境で `pip list` を実行すると、twineが入っています:" -#: ../../tutorials/develop-python-package-hatch.md:149 -#: ../../tutorials/develop-python-package-hatch.md:207 +#: ../../tutorials/develop-python-package-hatch.md:163 +#: ../../tutorials/develop-python-package-hatch.md:221 #, fuzzy msgid "To leave the environment use:" msgstr "環境設定" -#: ../../tutorials/develop-python-package-hatch.md:155 +#: ../../tutorials/develop-python-package-hatch.md:169 #, fuzzy msgid "Hatch, testing, and matrix environments" msgstr "Hatchと環境" -#: ../../tutorials/develop-python-package-hatch.md:157 +#: ../../tutorials/develop-python-package-hatch.md:171 msgid "" "It's always helpful to run your tests on the Python versions that you " "expect your users to be using. In this section, you'll explore the test " "environment setup in the pyOpenSci template package." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:159 +#: ../../tutorials/develop-python-package-hatch.md:173 msgid "Below, you see the Hatch environment test table." msgstr "以下に、Hatch環境テストテーブルが表示されます。" -#: ../../tutorials/develop-python-package-hatch.md:161 +#: ../../tutorials/develop-python-package-hatch.md:175 msgid "" "Similar to the above build environment, the environment below defines the" " dependencies that Hatch needs to install into the test environment " "(required to run your tests)." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:175 +#: ../../tutorials/develop-python-package-hatch.md:189 msgid "Your test environment has a matrix associated with it" msgstr "テスト環境にはマトリックスが関連付けられています" -#: ../../tutorials/develop-python-package-hatch.md:177 +#: ../../tutorials/develop-python-package-hatch.md:191 msgid "" "If the environment has a matrix associated with it, that tells Hatch to " "run the tests across different Python versions. Below, you are running " "tests on versions 3.10 through 3.13." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:180 +#: ../../tutorials/develop-python-package-hatch.md:194 msgid "" "Hatch by default will install Python [using " "UV](https://docs.astral.sh/uv/guides/install-python/) both when you " @@ -2387,7 +2405,7 @@ msgid "" " below" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:188 +#: ../../tutorials/develop-python-package-hatch.md:202 msgid "" "In your project, if you run `hatch shell test`, you will see the output " "below. This means that because there is a matrix of Python versions to " @@ -2395,56 +2413,56 @@ msgid "" "you want to use." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:201 +#: ../../tutorials/develop-python-package-hatch.md:215 msgid "" "Pick the Python test environment that you want to use and enter it, like " "this (this will open Python 3.13):" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:213 +#: ../../tutorials/develop-python-package-hatch.md:227 #, fuzzy msgid "Hatch scripts for tests" msgstr "`hatch publish -r test` を実行します" -#: ../../tutorials/develop-python-package-hatch.md:215 +#: ../../tutorials/develop-python-package-hatch.md:229 msgid "" "In that same tests section, you will see a `tool.hatch.envs.test.scripts`" " section. Similar to what you saw above with the build steps, this is " "where the \"script\" to run your tests is defined." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:218 +#: ../../tutorials/develop-python-package-hatch.md:232 msgid "" "Notice that below, the script has a script called `run`. And that script " "runs pytest with a set of arguments, including generating code coverage." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:225 +#: ../../tutorials/develop-python-package-hatch.md:239 msgid "To run this script in your terminal, use the syntax:" msgstr "ターミナルでこのスクリプトを実行するには、次の構文を使用します:" -#: ../../tutorials/develop-python-package-hatch.md:227 +#: ../../tutorials/develop-python-package-hatch.md:241 msgid "`hatch run test:run`" msgstr "`hatch run test:run`" -#: ../../tutorials/develop-python-package-hatch.md:229 +#: ../../tutorials/develop-python-package-hatch.md:243 #, fuzzy msgid "Reminder" msgstr "おすすめ" -#: ../../tutorials/develop-python-package-hatch.md:232 +#: ../../tutorials/develop-python-package-hatch.md:246 msgid "" "`hatch run`: this calls hatch and tells it that it will be running a " "command" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:233 +#: ../../tutorials/develop-python-package-hatch.md:247 msgid "" "`test:run` defines the environment you want it to run (`test`) in this " "case, and the script is defined as `run`" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:236 +#: ../../tutorials/develop-python-package-hatch.md:250 msgid "" "If you have a matrix setup for tests, then it will both install the " "needed Python version using UV and run your tests in each version of the " @@ -2453,35 +2471,35 @@ msgid "" "version listed in the matrix table." msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:266 +#: ../../tutorials/develop-python-package-hatch.md:280 msgid "Build your documentation with Hatch environments" msgstr "Hatch環境でドキュメントをビルドする" -#: ../../tutorials/develop-python-package-hatch.md:268 +#: ../../tutorials/develop-python-package-hatch.md:282 msgid "" "Finally, you can build and serve your documentation using hatch. To build" " a static HTML version of the docs run:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:271 +#: ../../tutorials/develop-python-package-hatch.md:285 msgid "`hatch run docs:build`" msgstr "`hatch run docs:build`" -#: ../../tutorials/develop-python-package-hatch.md:273 +#: ../../tutorials/develop-python-package-hatch.md:287 msgid "" "To run a local server with your docs updated as you update your markdown " "files, run:" msgstr "" -#: ../../tutorials/develop-python-package-hatch.md:275 +#: ../../tutorials/develop-python-package-hatch.md:289 msgid "`hatch run docs:serve`" msgstr "`hatch run docs:serve`" -#: ../../tutorials/develop-python-package-hatch.md:277 +#: ../../tutorials/develop-python-package-hatch.md:291 msgid "To stop serving the docs use:" msgstr "ドキュメントの提供を停止するには:" -#: ../../tutorials/develop-python-package-hatch.md:279 +#: ../../tutorials/develop-python-package-hatch.md:293 msgid "mac: ctrl + c windows:" msgstr "mac: ctrl + c windows:" @@ -2490,9 +2508,9 @@ msgid "Get to Know Hatch" msgstr "Hatchを知る" #: ../../tutorials/get-to-know-hatch.md:8 +#, fuzzy msgid "" -"Our Python packaging tutorials use the tool " -"[Hatch](https://hatch.pypa.io/latest/). While there are [many great " +"Our Python packaging tutorials use Hatch. While there are [many great " "packaging tools](/package-structure-code/python-package-build-tools) out " "there, we have selected Hatch because:" msgstr "" @@ -2508,9 +2526,10 @@ msgid "" msgstr "高品質なPythonパッケージを作成するために必要なステップのほとんどをサポートするエンドツーエンドのツールです。Hatchを使えば、初心者は覚えるツールが少なくて済みます。" #: ../../tutorials/get-to-know-hatch.md:16 +#, fuzzy, python-brace-format msgid "" -"It supports different build back-ends if you ever need to compile code in" -" other languages." +"It supports different {term}`Build backend` options if you ever need to " +"compile code in other languages." msgstr "他の言語のコードをコンパイルする必要がある場合は、異なるビルドバックエンドをサポートします。" #: ../../tutorials/get-to-know-hatch.md:18 @@ -2611,9 +2630,9 @@ msgstr "" "[Hatchのインストールドキュメント](https://hatch.pypa.io/latest/install/) をご覧ください。" #: ../../tutorials/get-to-know-hatch.md:75 +#, fuzzy, python-brace-format msgid "" -"Hatch can also be installed directly using " -"[pip](https://hatch.pypa.io/latest/install/#pip) or " +"Hatch can also be installed directly using {term}`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." @@ -2622,13 +2641,13 @@ msgstr "" "[conda](https://hatch.pypa.io/latest/install/#conda) " "を使って直接インストールすることもできる。WindowsとMac用のHatchインストーラーが最も簡単で効率的であることがわかりましたので、上記の指示に従うことをお勧めします。" -#: ../../tutorials/get-to-know-hatch.md:79 +#: ../../tutorials/get-to-know-hatch.md:80 msgid "" "Our Linux users have found success installing Hatch with pipx if they " "already use apt install." msgstr "私たちのLinuxユーザーは、すでにapt installを使っている場合、pipxを使ってHatchをインストールすることに成功しています。" -#: ../../tutorials/get-to-know-hatch.md:82 +#: ../../tutorials/get-to-know-hatch.md:83 msgid "" "Both approaches (using a graphical installer on Windows/Mac and pipx) " "ensure that you have Hatch installed globally. A global install means " @@ -2638,28 +2657,28 @@ msgstr "" "どちらのアプローチ（Windows/Macでグラフィカルインストーラを使う方法とpipxを使う方法）も、Hatchがグローバルにインストールされていることを保証します。" " グローバルインストールとは、コンピュータ上の全てのPython環境でHatchが利用できることを意味します。" -#: ../../tutorials/get-to-know-hatch.md:87 +#: ../../tutorials/get-to-know-hatch.md:88 msgid "Check that hatch installed correctly" msgstr "hatchが正しく取り付けられているか確認します" -#: ../../tutorials/get-to-know-hatch.md:89 +#: ../../tutorials/get-to-know-hatch.md:90 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 "上記のインストール手順が完了したら、ターミナルを開き、以下のコマンドを使用してHatchが正しくインストールされたことを確認してください:" -#: ../../tutorials/get-to-know-hatch.md:97 +#: ../../tutorials/get-to-know-hatch.md:98 msgid "" "*Note the version number output of `hatch --version` will likely be " "different from the output above in this tutorial.*" msgstr "* `hatch --version` で出力されるバージョン番号は、このチュートリアルの上記の出力とは異なる可能性が高いことに注意してください。*" -#: ../../tutorials/get-to-know-hatch.md:100 +#: ../../tutorials/get-to-know-hatch.md:101 msgid "Configure Hatch" msgstr "Hatchの設定" -#: ../../tutorials/get-to-know-hatch.md:102 +#: ../../tutorials/get-to-know-hatch.md:103 msgid "" "Once you have installed Hatch, you can customize its configuration. This " "includes setting the default name and setup for every package you create." @@ -2669,7 +2688,7 @@ msgstr "" "これには、作成するすべてのパッケージにデフォルト名とセットアップを設定することも含まれます。 " "このステップは必須ではありませんが、行うことをお勧めします。" -#: ../../tutorials/get-to-know-hatch.md:106 +#: ../../tutorials/get-to-know-hatch.md:107 msgid "" "Hatch stores your configuration in a [`config.toml` " "file](https://hatch.pypa.io/latest/config/project-templates/)." @@ -2677,7 +2696,7 @@ msgstr "" "Hatchは設定を [`config.toml`ファイル](https://hatch.pypa.io/latest/config" "/project-templates/) に保存します。" -#: ../../tutorials/get-to-know-hatch.md:108 +#: ../../tutorials/get-to-know-hatch.md:109 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 " @@ -2686,54 +2705,56 @@ msgstr "" "コマンドラインから `config.toml` ファイルを更新することができます, " "初めて使う場合は、テキストエディタで見て更新する方が簡単かもしれません。" -#: ../../tutorials/get-to-know-hatch.md:112 +#: ../../tutorials/get-to-know-hatch.md:113 msgid "Step 1: Open and Edit Your `config.toml` File" msgstr "ステップ 1: `config.toml` ファイルを開いて編集する" -#: ../../tutorials/get-to-know-hatch.md:114 +#: ../../tutorials/get-to-know-hatch.md:115 msgid "" "To open the config file in your file browser, run the following command " "in your shell:" msgstr "ファイルブラウザで設定ファイルを開くには、シェルで以下のコマンドを実行します:" -#: ../../tutorials/get-to-know-hatch.md:117 +#: ../../tutorials/get-to-know-hatch.md:118 msgid "`hatch config explore`" msgstr "`hatch config explore`" -#: ../../tutorials/get-to-know-hatch.md:119 +#: ../../tutorials/get-to-know-hatch.md:120 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." msgstr "ディレクトリウィンドウが開き、ファイルをダブルクリックして好きなテキストエディタで開くことができます。" -#: ../../tutorials/get-to-know-hatch.md:122 +#: ../../tutorials/get-to-know-hatch.md:123 msgid "" "You can also retrieve the location of the Hatch config file by running " "the following command in your shell:" msgstr "シェルで以下のコマンドを実行すれば、Hatchのコンフィグファイルの場所を取得することもできます:" -#: ../../tutorials/get-to-know-hatch.md:130 +#: ../../tutorials/get-to-know-hatch.md:131 msgid "Step 2 - update your email and name" msgstr "ステップ2 - Eメールと名前を更新する" -#: ../../tutorials/get-to-know-hatch.md:132 +#: ../../tutorials/get-to-know-hatch.md:133 +#, fuzzy 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." +"[pyproject.toml](pyproject-toml) metadata files that you create using " +"Hatch." msgstr "" "ファイルを開いたら、 `config.toml` ファイルの[template]テーブルをあなたの名前とEメールで更新します。 " "この情報は、Hatchを使用して作成した `pyproject.toml` メタデータファイルに使用されます。" -#: ../../tutorials/get-to-know-hatch.md:142 +#: ../../tutorials/get-to-know-hatch.md:144 msgid "Step 3" msgstr "ステップ3" -#: ../../tutorials/get-to-know-hatch.md:144 +#: ../../tutorials/get-to-know-hatch.md:146 msgid "Next, set tests to false in the `[template.plugins.default]` table." msgstr "次に、 `[template.plugins.default]` テーブルでtestsをfalseに設定します。" -#: ../../tutorials/get-to-know-hatch.md:146 +#: ../../tutorials/get-to-know-hatch.md:148 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 " @@ -2743,11 +2764,11 @@ msgstr "" "テストは重要ですが、Hatchのtests設定を `true` にすると、より複雑な `pyproject.toml` " "ファイルが作成されます。この初心者向けチュートリアルシリーズではこの機能を使う必要はありませんが、後のチュートリアルで紹介します。" -#: ../../tutorials/get-to-know-hatch.md:151 +#: ../../tutorials/get-to-know-hatch.md:153 msgid "Your `config.toml` file should look something like the one below." msgstr "あなたの `config.toml` ファイルは以下のようになるはずです。" -#: ../../tutorials/get-to-know-hatch.md:189 +#: ../../tutorials/get-to-know-hatch.md:191 #, fuzzy msgid "" "Also notice that the default license option is MIT. While we will discuss" @@ -2760,31 +2781,31 @@ msgstr "" "MITライセンスは [choosealicense.com](https://www.choosealicense.com) " "が推奨する寛容なライセンスです、そしてこのチュートリアルシリーズではこれを使用します。" -#: ../../tutorials/get-to-know-hatch.md:195 +#: ../../tutorials/get-to-know-hatch.md:197 msgid "You are of course welcome to select another license." msgstr "もちろん、他のライセンスを選択することも歓迎します。" -#: ../../tutorials/get-to-know-hatch.md:198 +#: ../../tutorials/get-to-know-hatch.md:200 msgid "" "I think we'd need the SPDX license options here if they want to chose " "bsd-3 for instance" msgstr "例えばbsd-3を選びたいのであれば、SPDXライセンスのオプションが必要だと思います。" -#: ../../tutorials/get-to-know-hatch.md:201 +#: ../../tutorials/get-to-know-hatch.md:203 msgid "Step 4: Close the config file and run `hatch config show`" msgstr "ステップ4: 設定ファイルを閉じて、 `hatch config show` を実行します。" -#: ../../tutorials/get-to-know-hatch.md:203 +#: ../../tutorials/get-to-know-hatch.md:205 msgid "" "Once you have completed the steps above run the following command in your" " shell." msgstr "上記の手順が完了したら、シェルで以下のコマンドを実行します。" -#: ../../tutorials/get-to-know-hatch.md:205 +#: ../../tutorials/get-to-know-hatch.md:207 msgid "`hatch config show`" msgstr "`hatch config show`" -#: ../../tutorials/get-to-know-hatch.md:207 +#: ../../tutorials/get-to-know-hatch.md:209 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 " @@ -2793,21 +2814,21 @@ msgstr "" "`hatch config show` はシェルの `config.toml` ファイルの内容を出力します。 " "値を見て、あなたの名前とEメールが設定されていることを確認してください。また、 `tests=false` であることを確認すること。" -#: ../../tutorials/get-to-know-hatch.md:211 +#: ../../tutorials/get-to-know-hatch.md:213 msgid "Hatch features" msgstr "Hatchの特徴" -#: ../../tutorials/get-to-know-hatch.md:213 +#: ../../tutorials/get-to-know-hatch.md:215 msgid "" "Hatch offers a suite of features that will make creating, publishing and " "maintaining your Python package easier." msgstr "Hatchは、Pythonパッケージの作成、公開、保守を容易にする一連の機能を提供します。" -#: ../../tutorials/get-to-know-hatch.md:216 +#: ../../tutorials/get-to-know-hatch.md:218 msgid "Comparison to other tools" msgstr "他のツールとの比較" -#: ../../tutorials/get-to-know-hatch.md:218 +#: ../../tutorials/get-to-know-hatch.md:220 msgid "" "[We compared Hatch to several of the other popular packaging tools in the" " ecosystem including flit, pdm and poetry. Learn more here](package-" @@ -2816,15 +2837,15 @@ msgstr "" "[私たちはHatchを、flit、pdm、poetryなど、エコシステムで人気のある他のパッケージングツールと比較しました。 詳細はこちら" "](package-features)" -#: ../../tutorials/get-to-know-hatch.md:221 +#: ../../tutorials/get-to-know-hatch.md:223 msgid "[More on Hatch here](hatch)" msgstr "[Hatchの詳細はこちら](hatch)" -#: ../../tutorials/get-to-know-hatch.md:223 +#: ../../tutorials/get-to-know-hatch.md:225 msgid "A few features that Hatch offers" msgstr "Hatchが提供するいくつかの機能" -#: ../../tutorials/get-to-know-hatch.md:225 +#: ../../tutorials/get-to-know-hatch.md:227 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 " @@ -2834,89 +2855,93 @@ msgstr "" "ファイルに変換します。 ([Hatchを使用してsetup.pyをpyproject.tomlに移行する](setup-py-to-" "pyproject-toml.md ) を参照)" -#: ../../tutorials/get-to-know-hatch.md:227 +#: ../../tutorials/get-to-know-hatch.md:229 msgid "" "It will help you by storing configuration information for publishing to " "PyPI after you've entered it once." msgstr "PyPIに公開するための設定情報を、一度入力した後に保存してくれます。" -#: ../../tutorials/get-to-know-hatch.md:229 +#: ../../tutorials/get-to-know-hatch.md:231 msgid "Use `hatch -h` to see all of the available commands." msgstr "利用可能なコマンドをすべて表示するには、 `hatch -h` を使用します。" -#: ../../tutorials/get-to-know-hatch.md:231 +#: ../../tutorials/get-to-know-hatch.md:233 msgid "What's next" msgstr "次のレッスン" -#: ../../tutorials/get-to-know-hatch.md:233 +#: ../../tutorials/get-to-know-hatch.md:235 msgid "" "In the next lesson you'll learn how to package and make your code " "installable using Hatch." msgstr "次のレッスンでは、Hatchを使ってコードをパッケージ化し、インストール可能にする方法を学びます。" -#: ../../tutorials/intro.md:33 ../../tutorials/setup-py-to-pyproject-toml.md:30 +#: ../../tutorials/intro.md:34 ../../tutorials/setup-py-to-pyproject-toml.md:36 msgid "Get to know Hatch" msgstr "Hatchを知る" -#: ../../tutorials/intro.md:33 +#: ../../tutorials/intro.md:34 ../../tutorials/run-python-scripts-hatch.md:8 +msgid "Run standalone Python scripts with Hatch" +msgstr "" + +#: ../../tutorials/intro.md:34 msgid "Python Packaging Tutorial Setup" msgstr "Pythonパッケージングチュートリアルのセットアップ" -#: ../../tutorials/intro.md:40 ../../tutorials/intro.md:87 +#: ../../tutorials/intro.md:42 ../../tutorials/intro.md:89 msgid "What is a Python package?" msgstr "Pythonパッケージとは何ですか？" -#: ../../tutorials/intro.md:40 +#: ../../tutorials/intro.md:42 #, fuzzy msgid "Create a Python package" msgstr "なぜPythonパッケージを作るのか？" -#: ../../tutorials/intro.md:40 +#: ../../tutorials/intro.md:42 msgid "Publish to PyPI" msgstr "PyPIに公開する" -#: ../../tutorials/intro.md:40 +#: ../../tutorials/intro.md:42 msgid "Publish to conda-forge" msgstr "conda-forgeに公開する" -#: ../../tutorials/intro.md:40 +#: ../../tutorials/intro.md:42 msgid "Publish using GitHub Actions and Trusted Publishing" msgstr "" -#: ../../tutorials/intro.md:40 +#: ../../tutorials/intro.md:42 msgid "Create and publish a Python Package" msgstr "Pythonパッケージの作成と公開" -#: ../../tutorials/intro.md:51 +#: ../../tutorials/intro.md:53 #, fuzzy msgid "Develop package (Hatch environments)" msgstr "Pythonのパッケージと環境" -#: ../../tutorials/intro.md:51 +#: ../../tutorials/intro.md:53 msgid "Add README file" msgstr "README ファイルを追加する" -#: ../../tutorials/intro.md:51 +#: ../../tutorials/intro.md:53 msgid "Add a license & code of conduct" msgstr "ライセンスと行動規範の追加" -#: ../../tutorials/intro.md:51 +#: ../../tutorials/intro.md:53 msgid "Update metadata in pyproject.toml" msgstr "pyproject.tomlのメタデータを更新する" -#: ../../tutorials/intro.md:51 +#: ../../tutorials/intro.md:53 msgid "Project information files & metadata" msgstr "プロジェクト情報ファイルとメタデータ" -#: ../../tutorials/intro.md:61 +#: ../../tutorials/intro.md:63 msgid "Reference Guides" msgstr "リファレンスガイド" -#: ../../tutorials/intro.md:68 +#: ../../tutorials/intro.md:70 msgid "Migrate setup.py to a pyproject.toml using Hatch" msgstr "Hatchを使ってsetup.pyをpyproject.tomlに移行する" -#: ../../tutorials/intro.md:68 +#: ../../tutorials/intro.md:70 msgid "Hatch for Existing Packages" msgstr "既存パッケージ用Hatch" @@ -2929,10 +2954,11 @@ msgid "_A start to finish beginner-friendly tutorial_" msgstr "_初心者にやさしいチュートリアル_" #: ../../tutorials/intro.md:11 +#, fuzzy, python-brace-format msgid "" "Welcome to the pyOpenSci Python packaging tutorial series. The lessons on" " the upcoming pages walk you through the core steps needed to create a " -"Python package." +"{term}`Python package`." msgstr "" "pyOpenSci Pythonパッケージングチュートリアルシリーズへようこそ。 " "これからのページのレッスンは、Pythonパッケージを作成するために必要なコアステップを説明します。" @@ -2947,7 +2973,7 @@ msgstr "" "パッケージングチュートリアルのレッスンを示す図。Pythonパッケージとは何か、コードをpipでインストール可能にする、パッケージをPyPIに公開する、READMEとLICENSEファイルを追加する、PyPI用のメタデータを追加する、最後にconda" " forgeに公開する、の6つです。" -#: ../../tutorials/intro.md:19 ../../tutorials/trusted-publishing.md:255 +#: ../../tutorials/intro.md:19 ../../tutorials/trusted-publishing.md:258 msgid "" "This lesson is the first in a series of lessons to help you get started " "with Python packaging." @@ -2968,72 +2994,73 @@ msgstr "" "しかし、Pythonパッケージの作成に関わるステップをよりよく理解することに興味があるのであれば、このコンテンツはまだ価値があるでしょう。" #: ../../tutorials/intro.md:29 +#, fuzzy msgid "" "In this series you will learn about the core elements that you need to " -"publish your package to the [Python Package Index " -"(PyPI)](https://pypi.org/)." +"publish your package to [PyPI](publish-pypi)." msgstr "" "このシリーズでは、 [Python Package Index (PyPI)](https://pypi.org/) " "にパッケージを公開するために必要なコアな要素について学びます。" -#: ../../tutorials/intro.md:31 +#: ../../tutorials/intro.md:32 msgid "" "In the second series, you will learn about infrastructure and " "documentation needed to support package maintenance." msgstr "第2シリーズでは、パッケージのメンテナンスをサポートするために必要なインフラとドキュメントについて学びます。" -#: ../../tutorials/intro.md:75 ../../tutorials/publish-conda-forge.md:20 -#: ../../tutorials/publish-pypi.md:20 ../../tutorials/pyproject-toml.md:24 -#: ../../tutorials/setup-py-to-pyproject-toml.md:18 +#: ../../tutorials/intro.md:77 ../../tutorials/publish-conda-forge.md:22 +#: ../../tutorials/publish-pypi.md:20 ../../tutorials/pyproject-toml.md:27 +#: ../../tutorials/setup-py-to-pyproject-toml.md:20 #: ../../tutorials/trusted-publishing.md:13 msgid "Learning Objectives" msgstr "学習目標" -#: ../../tutorials/intro.md:77 +#: ../../tutorials/intro.md:79 msgid "" "This lesson introduces you to the basic components of a Python package. " "After reading this lesson you will:" msgstr "このレッスンでは Python パッケージの基本的な構成要素を紹介します。 このレッスンを読めば、次のことがわかります:" -#: ../../tutorials/intro.md:80 +#: ../../tutorials/intro.md:82 msgid "Understand what a Python package is" msgstr "Pythonパッケージとは何かを理解する" -#: ../../tutorials/intro.md:81 +#: ../../tutorials/intro.md:83 msgid "Be able to list the 5 core components of a Python package" msgstr "Pythonパッケージの5つのコアコンポーネントを列挙できます" -#: ../../tutorials/intro.md:82 +#: ../../tutorials/intro.md:84 msgid "" "Be able to explain the difference between generalizable code and code " "that supports a specific scientific application" msgstr "一般化可能なコードと特定の科学的アプリケーションをサポートするコードの違いを説明できます。" -#: ../../tutorials/intro.md:89 +#: ../../tutorials/intro.md:91 msgid "" "At a high level, you can think about a Python package as a toolbox that " "you can use to perform various tasks." msgstr "高レベルでは、Pythonパッケージは、様々なタスクを実行するために使用できるツールボックスと考えることができます。" -#: ../../tutorials/intro.md:92 +#: ../../tutorials/intro.md:94 +#, fuzzy, python-brace-format msgid "" "A Python package is basically a directory with a specific file structure." -" Within the package directory structure, there are modules which are " -"files that end in `.py` (the same extension you'd see in a Python " -"script). These modules allow you to group and structure your Python code." -" Each module contains functions and classes, that you can think about as " -"the tools in your toolbox." +" Within the package directory structure, there are {term}`Module` objects" +" which are files that end in `.py` (the same extension you'd see in a " +"Python script). These modules allow you to group and structure your " +"Python code. Each module contains functions and classes, that you can " +"think about as the tools in your toolbox." msgstr "" "Pythonパッケージは基本的に特定のファイル構造を持つディレクトリです。 パッケージのディレクトリ構造の中に、`.py` " "で終わるファイル(Pythonスクリプトで見られるのと同じ拡張子)のモジュールがあります。これらのモジュールによって、Pythonコードをグループ化し、構造化することができます。各モジュールには関数とクラスが含まれており、それらはあなたの道具箱の中の道具だと考えることができます。" -#: ../../tutorials/intro.md:101 +#: ../../tutorials/intro.md:103 msgid "" "Diagram showing a sketch of a toolbox filled with different tools " "including a hammer and a saw." msgstr "ハンマーやノコギリなど、さまざまな工具が入った工具箱のスケッチを示す図。" -#: ../../tutorials/intro.md:103 +#: ../../tutorials/intro.md:105 msgid "" "You can think about a package as a toolbox filled with coding tools. A " "tool may be a function or a class. Each tool does a specific thing well." @@ -3041,11 +3068,11 @@ msgstr "" "パッケージとは、コーディングツールが詰まった道具箱のようなものだと考えることができます。 ツールは関数かもしれないし、クラスかもしれません。 " "それぞれのツールは特定のことをよくします。" -#: ../../tutorials/intro.md:108 +#: ../../tutorials/intro.md:110 msgid "Python packages are installable" msgstr "Pythonパッケージはインストール可能" -#: ../../tutorials/intro.md:110 +#: ../../tutorials/intro.md:112 msgid "" "A package is installable, which means that you can add the functionality " "within the package's code to any Python environment and import that " @@ -3053,7 +3080,7 @@ msgid "" "as NumPy or Matplotlib." msgstr "パッケージはインストール可能で、パッケージのコード内の機能をどのPython環境にも追加でき、NumPyやMatplotlibのような科学的なPythonのコアパッケージをインポートするように、その機能をインポートできます。" -#: ../../tutorials/intro.md:119 +#: ../../tutorials/intro.md:121 msgid "" "Installing a package into an environment makes it easier to manage and " "reuse your code across different projects. Structuring your code as a " @@ -3061,15 +3088,15 @@ msgid "" "the toolbox you've created and let others build with it." msgstr "パッケージを環境にインストールすることで、異なるプロジェクト間でのコードの管理と再利用が容易になる。あなたのコードをパッケージとして構造化することは、あなたが作成したツールボックスのツールを共有し、他の人がそれを使って構築できるようにするために必要な最初のステップです。" -#: ../../tutorials/intro.md:124 +#: ../../tutorials/intro.md:126 msgid "Why create a Python package?" msgstr "なぜPythonパッケージを作るのか？" -#: ../../tutorials/intro.md:126 +#: ../../tutorials/intro.md:128 msgid "You might create a Python package because you want to:" msgstr "Pythonパッケージを作りたいから作るかもしれません:" -#: ../../tutorials/intro.md:128 +#: ../../tutorials/intro.md:130 msgid "" "**Use your code across different projects:** At its most basic level, " "creating a package allows you to install your code into a Python " @@ -3080,16 +3107,17 @@ msgstr "" "最も基本的なレベルでは、パッケージを作成することで、あなたのコードをPython環境にインストールすることができます。 " "これにより、ローカルとクラウドの両方のワークフローに関数やクラスをインポートすることができます。" -#: ../../tutorials/intro.md:129 +#: ../../tutorials/intro.md:131 +#, fuzzy, python-brace-format msgid "" "**Share your code:** If you publish a package on a public repository such" -" as PyPI or conda, your package can be installed on any machine using pip" -" or conda with a single command." +" as PyPI or conda-forge, your package can be installed on any machine " +"using {term}`pip` or conda with a single command." msgstr "" "**Share your code:** PyPIやcondaのような公開リポジトリでパッケージを公開する場合、 " "あなたのパッケージは、pipやcondaを使ってどのマシンにもコマンドひとつでインストールできます。" -#: ../../tutorials/intro.md:130 +#: ../../tutorials/intro.md:134 msgid "" "**Build community around your code:** Packages make it easier for " "multiple people to work on the same project (particularly when published " @@ -3104,7 +3132,7 @@ msgstr "" "のようなバージョン管理システムを使えば、コードベースへの長期的な変更を追跡するのがさらに簡単になる。 " "issueやプルリクエストのようなツールは、外部のユーザーがバグ修正に貢献したり、コードベースへの変更を受け入れるためのレビュープロセスを確立したりすることを容易にします。" -#: ../../tutorials/intro.md:131 +#: ../../tutorials/intro.md:135 msgid "" "**Organize your code:** Packages can be used to organize large code " "projects, dividing them into smaller, more manageable components. This " @@ -3114,29 +3142,29 @@ msgstr "" "**コードを整理する:** パッケージは、大規模なコード・プロジェクトを整理し、より小さく管理しやすいコンポーネントに分割するために使用できます。" " この構造は、コードベースを維持する上でも、理解しやすくする上でも役立ちます。" -#: ../../tutorials/intro.md:133 +#: ../../tutorials/intro.md:137 msgid "What to consider before you create a package" msgstr "パッケージを作成する前に考慮すべきこと" -#: ../../tutorials/intro.md:135 +#: ../../tutorials/intro.md:139 msgid "" "Creating a Python package that others use takes considerable time and " "effort. Before you begin, think about your goals including:" msgstr "他の人が使うPythonパッケージを作るには、かなりの時間と労力がかかります。 始める前に、以下のような目標について考えてください:" -#: ../../tutorials/intro.md:138 +#: ../../tutorials/intro.md:142 msgid "Who you think will use your package" msgstr "あなたのパッケージを利用すると思われる人" -#: ../../tutorials/intro.md:139 +#: ../../tutorials/intro.md:143 msgid "How people might use your package and on what data (if data are relevant)" msgstr "人々があなたのパッケージをどのように使うか、またどのようなデータについて使うか（データが関連する場合）" -#: ../../tutorials/intro.md:140 +#: ../../tutorials/intro.md:144 msgid "Whether you have time to add things such as documentation and tests" msgstr "ドキュメントやテストなどを追加する時間があるかどうか" -#: ../../tutorials/intro.md:141 +#: ../../tutorials/intro.md:145 msgid "" "How long you might be able to maintain it: remember that once people " "begin using your package they will depend on your maintainer team to " @@ -3145,21 +3173,21 @@ msgstr "" "メンテナンスできる可能性のある期間: " "いったん人々があなたのパッケージを使い始めると、彼らはそれを更新し、バグを修正し、質問に答えるために、あなたのメンテナチームに依存することになることを忘れないでください。" -#: ../../tutorials/intro.md:143 +#: ../../tutorials/intro.md:147 msgid "" "Before creating a user-facing package, it's important to consider all of " "the above." msgstr "ユーザー向けのパッケージを作成する前に、上記のすべてを考慮することが重要です。" -#: ../../tutorials/intro.md:145 +#: ../../tutorials/intro.md:149 msgid "The elements of a Python package" msgstr "Pythonパッケージの要素" -#: ../../tutorials/intro.md:149 ../../tutorials/intro.md:227 +#: ../../tutorials/intro.md:153 ../../tutorials/intro.md:231 msgid "Diagram showing .. more here if this stays." msgstr "図......これが残ればもっとここに。" -#: ../../tutorials/intro.md:151 +#: ../../tutorials/intro.md:155 msgid "" "The elements of a Python package include code, documentation, tests, an " "OSI-approved license and infrastructure. Maintainers are at the core " @@ -3169,17 +3197,17 @@ msgstr "" "Pythonパッケージの要素には、コード、ドキュメント、テスト、OSIが承認したライセンス、インフラが含まれます。 " "メインテナーは、バグを修正し、ユーザーの懸念に対処しながら、すべてが機能し、最新であることを確認する中核を担っています。" -#: ../../tutorials/intro.md:157 +#: ../../tutorials/intro.md:161 msgid "The core elements of Python package include:" msgstr "Pythonパッケージの核となる要素は以下の通りです:" -#: ../../tutorials/intro.md:159 +#: ../../tutorials/intro.md:163 msgid "" "**Code:** Functions and classes that provide functionality for a user of " "your package" msgstr "**コード:** パッケージのユーザーに機能を提供する関数とクラス" -#: ../../tutorials/intro.md:160 +#: ../../tutorials/intro.md:164 msgid "" "**Documentation:** Installation instructions, tutorials, and examples " "that both help users get started using your package and contributors and " @@ -3188,13 +3216,13 @@ msgstr "" "**ドキュメンテーション:** " "インストール手順、チュートリアル、サンプルは、ユーザがあなたのパッケージを使い始めるのを助け、貢献者やメンテナがバグを修正し、パッケージを保守するのを助けます。" -#: ../../tutorials/intro.md:161 +#: ../../tutorials/intro.md:165 msgid "" "Contributor Documentation in the form of a **CONTRIBUTING.md** file is " "useful to help people to contribute to your package." msgstr "**CONTRIBUTING.md** ファイル形式の貢献者ドキュメンテーションは、人々があなたのパッケージに貢献するのを助けるのに便利です。" -#: ../../tutorials/intro.md:162 +#: ../../tutorials/intro.md:166 msgid "" "Development Documentation helps both maintainers and contributors " "understand how to maintain a package's infrastructure." @@ -3202,14 +3230,14 @@ msgstr "" "Development Documentation " "は、メンテナと貢献者の両方が、パッケージのインフラストラクチャをどのように保守するかを理解するのに役立ちます。" -#: ../../tutorials/intro.md:163 +#: ../../tutorials/intro.md:167 msgid "" "**Tests:** that make sure your code works as it should and makes it " "easier for you and others to contribute to, modify and update the code in" " the future" msgstr "**テスト:** これは、あなたのコードが本来の機能を発揮し、あなたや他の人が貢献しやすくなるようにするものです、 将来的にコードを修正更新します" -#: ../../tutorials/intro.md:164 +#: ../../tutorials/intro.md:168 #, fuzzy msgid "" "**License:** An open source license, or license that is [OSI " @@ -3220,7 +3248,7 @@ msgstr "" "**ライセンス:** オープンソースライセンス、あるいは [OSI認可](https://opensource.org/licenses/) " "ライセンスとは、他の人があなたのパッケージを使うことを許可するライセンスのことです。また、パッケージの要素をどのように再利用できるか、また再利用できないかに関する法的な方向性も示しています。" -#: ../../tutorials/intro.md:165 +#: ../../tutorials/intro.md:169 msgid "" "**Infrastructure** that automates updates, publication workflows and runs" " test suites. Infrastructure includes a suite of things such as platforms" @@ -3231,11 +3259,11 @@ msgstr "" "**インフラ** 更新、公開ワークフロー、テストスイートの実行を自動化します。 " "インフラストラクチャーには、GitHubやGitLabのようなプラットフォーム、noxやtoxのようなローカルでテストやツールを実行するツール、パッケージメンテナンスのステップを自動化する継続的インテグレーションなど、一連のものが含まれます。" -#: ../../tutorials/intro.md:167 +#: ../../tutorials/intro.md:171 msgid "What pyOpenSci looks for in a package" msgstr "pyOpenSciがパッケージで探すもの" -#: ../../tutorials/intro.md:170 +#: ../../tutorials/intro.md:174 msgid "" "pyOpenSci performs an [initial set of editor " "checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-" @@ -3247,11 +3275,11 @@ msgstr "" "/software-peer-review/how-to/editor-in-chief-guide.html#editor-checklist-" "template) を行います。 これらのチェックは、パッケージを作成する際に、パッケージが持つべきものの基準として役に立つかもしれません。" -#: ../../tutorials/intro.md:176 +#: ../../tutorials/intro.md:180 msgid "Packages are more than just code - Infrastructure" msgstr "パッケージは単なるコードではありません - インフラストラクチャー" -#: ../../tutorials/intro.md:178 +#: ../../tutorials/intro.md:182 msgid "" "A package in any language is more than just code. If you expect other " "people to use your package, besides yourself, you should consider not " @@ -3261,11 +3289,11 @@ msgstr "" "どの言語でも、パッケージは単なるコードではありません。 " "自分以外の人があなたのパッケージを使うことを期待するのであれば、高品質のコードを書くだけでなく、パッケージが有用なコミュニティリソースとなるための様々な要素も考慮すべきです。" -#: ../../tutorials/intro.md:183 +#: ../../tutorials/intro.md:187 msgid "Version control and storing your package on GitHub or GitLab" msgstr "GitHubまたはGitLabでのバージョン管理とパッケージの保存" -#: ../../tutorials/intro.md:185 +#: ../../tutorials/intro.md:189 msgid "" "Most Python packages live in an online version control platform such as " "GitHub or GitLab. GitHub and GitLab both run [git](https://git-scm.com/) " @@ -3278,7 +3306,7 @@ msgstr "" "GitHubとGitLabはどちらもバージョン管理のために [git](https://git-scm.com/) を実行しています。 " "ソフトウェアをバージョン管理下に置くことは、時間の経過に伴う変更を追跡する一方で、コードベースへの変更が予期せず何かを壊してしまった場合に、履歴をさかのぼって変更を取り消すことができるからです。" -#: ../../tutorials/intro.md:190 +#: ../../tutorials/intro.md:194 msgid "" "By publishing your package on GitHub or GitLab, you are making your code " "public facing. This means that others can both see your code and also " @@ -3288,11 +3316,11 @@ msgstr "" "あなたのパッケージをGitHubやGitLabで公開することで、あなたはコードを公開することになります。 " "これは、他の人があなたのコードを見ることができ、プルリクエスト(GitHub)/マージリクエスト(GitLab)/コードレビューワークフローを使って貢献することもできることを意味します。" -#: ../../tutorials/intro.md:192 +#: ../../tutorials/intro.md:196 msgid "GitHub & GitLab vs. Git" msgstr "GitHub & GitLab vs. Git" -#: ../../tutorials/intro.md:195 +#: ../../tutorials/intro.md:199 msgid "" "GitHub and GitLab are online (cloud) platforms that run `git` (version " "control software) on the backend. Running git locally on your computer " @@ -3303,35 +3331,35 @@ msgstr "" "プラットフォームです。 コンピュータ上でローカルに git を実行すると、GitHub や GitLab にファイルをアップロード (`git " "push`) したりダウンロード (`git pull`) したりすることができます。" -#: ../../tutorials/intro.md:200 +#: ../../tutorials/intro.md:204 msgid "Issues or Ticket Trackers" msgstr "issue かチケットトラッカー" -#: ../../tutorials/intro.md:202 +#: ../../tutorials/intro.md:206 msgid "" "GitHub and GitLab also both offer community features such as issues that " "allow:" msgstr "GitHubとGitLabは、どちらもissueのようなコミュニティ機能を提供しています：" -#: ../../tutorials/intro.md:204 +#: ../../tutorials/intro.md:208 msgid "you to communicate with your maintainers and contributor community" msgstr "メンテナや貢献者コミュニティとのコミュニケーション" -#: ../../tutorials/intro.md:205 +#: ../../tutorials/intro.md:209 msgid "users to report bugs, ask questions and request new features" msgstr "ユーザーによるバグ報告、質問、新機能のリクエスト" -#: ../../tutorials/intro.md:206 +#: ../../tutorials/intro.md:210 msgid "" "you to publicly keep track of enhancements and features you want to work " "on for your package." msgstr "あなたのパッケージのために取り組みたい機能強化や機能を公的に追跡することができます。" -#: ../../tutorials/intro.md:208 +#: ../../tutorials/intro.md:212 msgid "Continuous integration and continuous deployment" msgstr "継続的インテグレーションと継続的デプロイメント" -#: ../../tutorials/intro.md:210 +#: ../../tutorials/intro.md:214 msgid "" "GitHub and GitLab also provide continuous integration and continuous " "deployment (CI/CD). Continuous integration (CI) refers to a platform that" @@ -3343,29 +3371,29 @@ msgstr "" " とは、特定のイベントが発生したときに特定のジョブを自動的に実行するプラットフォームのことを指し、継続的デプロイメント " "(CD)とは、実行や構築だけでなく、最終的なアウトプットをどこかに公開することを指すCIの拡張です。" -#: ../../tutorials/intro.md:212 +#: ../../tutorials/intro.md:216 msgid "**An example of Continuous integration:**" msgstr "**継続的インテグレーションの例:**" -#: ../../tutorials/intro.md:214 +#: ../../tutorials/intro.md:218 msgid "" "When someone submits a change to your code, your tests will run across " "different operating systems and the code will be checked for format " "issues." msgstr "誰かがあなたのコードに変更を加えた場合、あなたのテストは異なるオペレーティングシステム上で実行され、コードはフォーマットの問題がないかチェックされます。" -#: ../../tutorials/intro.md:216 +#: ../../tutorials/intro.md:220 msgid "**An example of Continuous deployment:**" msgstr "**継続的デプロイの例:**" -#: ../../tutorials/intro.md:218 +#: ../../tutorials/intro.md:222 msgid "" "When you are ready to release your package to PyPI, a continuous " "deployment operation might be triggered on release to publish your " "package to PyPI." msgstr "PyPIにパッケージをリリースする準備ができたら、リリース時に継続的デプロイ操作をトリガーしてパッケージをPyPIに公開することがあります。" -#: ../../tutorials/intro.md:220 +#: ../../tutorials/intro.md:224 msgid "" "Integrated CI/CD will help you maintain your software, ensuring that " "changes to the code don't break things unexpectedly. They can also help " @@ -3375,15 +3403,15 @@ msgstr "" "統合されたCI/CDは、コードの変更が予期せぬ事態を引き起こさないよう、ソフトウェアの保守を支援します。 " "また、コードに新しい変更が加えられるたびに、コードのスタイルや書式の一貫性を維持するのにも役立ちます。" -#: ../../tutorials/intro.md:229 +#: ../../tutorials/intro.md:233 msgid "The lifecycle of a scientific Python package." msgstr "科学的Pythonパッケージのライフサイクル。" -#: ../../tutorials/intro.md:232 +#: ../../tutorials/intro.md:236 msgid "When should you turn your code into a Python package?" msgstr "あなたのコードをPythonパッケージにするタイミングは？" -#: ../../tutorials/intro.md:234 +#: ../../tutorials/intro.md:238 msgid "" "You may be wondering, what types of code should become a Python package " "that is both on GitHub and published to PyPI and/or conda-forge." @@ -3391,11 +3419,11 @@ msgstr "" "どのようなコードをPythonのパッケージにして、GitHubに置き、PyPIやconda-" "forgeに公開すればいいのか、疑問に思うかもしれません。" -#: ../../tutorials/intro.md:236 +#: ../../tutorials/intro.md:240 msgid "There are a few use cases to consider:" msgstr "考慮すべき使用例がいくつかあります:" -#: ../../tutorials/intro.md:238 +#: ../../tutorials/intro.md:242 msgid "" "**Creating a basic package for yourself:** Sometimes you want create a " "package for your own personal use. This might mean making your code " @@ -3407,7 +3435,7 @@ msgstr "" "**自分用の基本パッケージを作ります:** 個人的に使用するためにパッケージを作成したいこともあるでしょう。 " "これは、コードをローカルにpipでインストールできるようにすることを意味するかもしれませんし、GitHubに公開したいと思うかもしれません。その場合、他の人があなたのコードを使うことを期待していないので、パッケージを更新する必要がある場合に、あなた自身と将来の自分のためのドキュメントしか用意できないかもしれません。" -#: ../../tutorials/intro.md:240 +#: ../../tutorials/intro.md:244 msgid "" "An example of this type of package might be a set of functions that you " "write that are useful across several of your projects. It could be useful" @@ -3416,11 +3444,11 @@ msgstr "" "この種のパッケージの例としては、いくつかのプロジェクトにまたがって有用な関数のセットを書くことができます。 " "これらの機能をすべてのプロジェクトで利用できれば便利でしょう。" -#: ../../tutorials/intro.md:243 +#: ../../tutorials/intro.md:247 msgid "LINK to pip installable lesson when it's published - it's in review now" msgstr "レッスンが公開されたら、pipでインストールできるようにリンクします - 審査中になります" -#: ../../tutorials/intro.md:246 +#: ../../tutorials/intro.md:250 msgid "" "**Creating a package for the community:** In other cases, you may create " "some code that you soon realize might also be useful to not just you, but" @@ -3436,7 +3464,7 @@ msgstr "" "その場合は、パッケージを作成してGitHubで公開し、他のユーザーもそれを使うかもしれないので、CI/CDパイプラインや課題トラッカーなどのGitHubのインフラを利用することも検討できるでしょう。あなたのパッケージを他の人たちにも使ってもらいたいので、LICENSE情報、ユーザーや貢献者のための文書、テストも含めておきたいです。" " このタイプのパッケージはPyPIに公開されることが多いです。" -#: ../../tutorials/intro.md:249 +#: ../../tutorials/intro.md:253 msgid "" "For example, all of the [pyOpenSci packages](https://www.pyopensci.org" "/python-packages.html) are public facing with an intended audience beyond" @@ -3445,11 +3473,11 @@ msgstr "" "例えば、すべての [pyOpenSciパッケージ](https://www.pyopensci.org/python-packages.html)" " は、メンテナ以外の読者を想定して公開されています。" -#: ../../tutorials/intro.md:251 +#: ../../tutorials/intro.md:255 msgid "Packages that you expect others to use should be well-scoped" msgstr "他の人が使用することを想定しているパッケージは、十分なスコープを持つべきです。" -#: ../../tutorials/intro.md:253 +#: ../../tutorials/intro.md:257 msgid "" "Ideally the code in your Python package is focused on a specific theme or" " use case. This theme is important as it's a way to scope the content of " @@ -3458,7 +3486,7 @@ msgstr "" "Pythonパッケージのコードは、特定のテーマやユースケースにフォーカスしているのが理想的です。 " "このテーマは、パッケージの内容に幅を持たせる方法として重要です。" -#: ../../tutorials/intro.md:255 +#: ../../tutorials/intro.md:259 msgid "" "It can be tricky to decide when your code becomes something that might be" " more broadly useful to others. But one question you can ask yourself is " @@ -3469,11 +3497,11 @@ msgstr "" "自分のコードが、いつ他の人に広く役立つものになるかを決めるのは、難しいことです。 " "しかし、自分自身に問いかけることができる質問が一つあります。それは、あなたのコードは特定の研究プロジェクトのために書かれたものですか？あるいは、あなたのドメインにおける複数のプロジェクトにまたがるより広範な応用が可能でしょうか？" -#: ../../tutorials/intro.md:257 +#: ../../tutorials/intro.md:261 msgid "How does this relate to code for a research project?" msgstr "研究プロジェクトのコードとの関連は？" -#: ../../tutorials/intro.md:260 +#: ../../tutorials/intro.md:264 #, fuzzy msgid "" "A [Research Compendium](https://book.the-turing-way.org/reproducible-" @@ -3486,7 +3514,7 @@ msgstr "" "research/compendia.html) とは、特定の研究プロジェクトをサポートするコード、データ、文書を整理したものです。 " "研究で使用された方法、データ、分析の包括的な記録を提供することで、研究の再現性と透明性を高めることを目的としています。" -#: ../../tutorials/intro.md:265 +#: ../../tutorials/intro.md:269 msgid "" "A Python package is a collection of modules that can be used to perform a" " specific set of tasks. These tasks should be applicable to numerous " @@ -3497,7 +3525,7 @@ msgstr "" "これらのタスクは、数多くのワークフローに適用できるはずです。 そのため、Pythonパッケージは、特定のプロジェクトをサポートするResearch" " Compendiumよりも汎用性が高いです。" -#: ../../tutorials/intro.md:270 +#: ../../tutorials/intro.md:274 msgid "" "[Read about `Good enough practices in scientific " "computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005510)" @@ -3505,7 +3533,7 @@ msgstr "" "[`科学的コンピューティングにおける十分なプラクティス` " "について読む](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005510)" -#: ../../tutorials/intro.md:271 +#: ../../tutorials/intro.md:275 msgid "" "[Learn more about research compendia (also called repo-packs) in this " "blog post.](https://lorenabarba.com/blog/how-repro-packs-can-save-your-" @@ -3515,11 +3543,11 @@ msgstr "" "については、こちらのブログ記事で詳しくご紹介しています。](https://lorenabarba.com/blog/how-repro-" "packs-can-save-your-future-self/)" -#: ../../tutorials/intro.md:274 +#: ../../tutorials/intro.md:278 msgid "Below are a few examples well scoped pyOpenSci packages:" msgstr "以下はよくスコープされたpyOpenSciパッケージの例です:" -#: ../../tutorials/intro.md:276 +#: ../../tutorials/intro.md:280 msgid "" "[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): is a package " "designed to work with annotating animal vocalizations and bioacoustics " @@ -3530,7 +3558,7 @@ msgstr "" "[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): " "は、動物の発声や生物音響データの注釈付けを行うために設計されたパッケージです。このパッケージは、ユーザー固有の研究ワークフローに関連する特定の個々の研究アプリケーションに焦点を当てるのではなく、科学者がさまざまなタイプの生体音響データを処理するのを支援します。" -#: ../../tutorials/intro.md:277 +#: ../../tutorials/intro.md:281 msgid "" "[Pandera](https://www.union.ai/pandera) is another more broadly used " "Python package. Pandera supports data testing and thus also has a broader" @@ -3539,21 +3567,21 @@ msgstr "" "[Pandera](https://www.union.ai/pandera) もまた、より広く使われているPythonパッケージです。 " "Panderaはデータの検査をサポートしているため、広範な研究用途にも使用できます。" -#: ../../tutorials/intro.md:279 +#: ../../tutorials/intro.md:283 msgid "Matplotlib as an example" msgstr "例としてのMatplotlib" -#: ../../tutorials/intro.md:281 +#: ../../tutorials/intro.md:285 msgid "" "At the larger end of the user spectrum, Matplotlib is a great example. " "Matplotlib does one thing really well:" msgstr "大規模なユーザーでは、Matplotlibが良い例です。 Matplotlibは一つのことをとてもよくやってくれます:" -#: ../../tutorials/intro.md:284 +#: ../../tutorials/intro.md:288 msgid "_It creates visual plots of data._" msgstr "_データの視覚的なプロットを作成します。_" -#: ../../tutorials/intro.md:286 +#: ../../tutorials/intro.md:290 msgid "" "Thousands of people use Matplotlib for different plotting applications " "using different types of data. While few scientific packages will have " @@ -3563,17 +3591,17 @@ msgstr "" "Matplotlibは、何千人もの人々が、様々な種類のデータを使った様々なプロットアプリケーションに利用しています。 " "Matplotlibのような広範なアプリケーションと大規模なユーザーベースを持つ科学パッケージはほとんどないでしょうが、自分のパッケージが何をするのかを調べるという考え方は依然として重要です。" -#: ../../tutorials/intro.md:292 +#: ../../tutorials/intro.md:296 msgid "Code should also be clean & readable & documented" msgstr "コードはまた、クリーンで読みやすく、文書化されていなければなりません。" -#: ../../tutorials/intro.md:294 +#: ../../tutorials/intro.md:298 msgid "" "The code in your package should also be clean, readable, and well " "documented." msgstr "パッケージ内のコードもまた、クリーンで読みやすく、十分に文書化されていなければなりません。" -#: ../../tutorials/intro.md:296 +#: ../../tutorials/intro.md:300 msgid "" "**Clean code:** Clean code refers to code that uses expressive variable " "names, is concise and doesn't repeat itself. You can learn about best " @@ -3582,7 +3610,7 @@ msgstr "" "**クリーンコード:** " "クリーンなコードとは、表現力豊かな変数名を使い、簡潔で、繰り返しのないコードを指す。きれいなコードのためのベストプラクティスについては、今後のpyOpenSciチュートリアルで学ぶことができます。" -#: ../../tutorials/intro.md:300 +#: ../../tutorials/intro.md:304 msgid "" "**Readable code:** readable code is code written with a consistent style." " You can use linters and code formatters such as black and flake8 to " @@ -3595,7 +3623,7 @@ msgstr "" " [コードフォーマッタの詳細はこちらです。](../package-structure-code/code-style-linting-" "format)" -#: ../../tutorials/intro.md:304 +#: ../../tutorials/intro.md:308 msgid "" "**Documented code:** documented code is written using docstrings that " "help a user understand both what the functions and methods in your code " @@ -3608,15 +3636,15 @@ msgstr "" " [docstringsについては、こちらのガイドで詳しく説明しています。](../documentation/write-user-" "documentation/document-your-code-api-docstrings)" -#: ../../tutorials/intro.md:308 +#: ../../tutorials/intro.md:312 msgid "Making your package installable - publishing to PyPI & conda-forge" msgstr "パッケージをインストール可能にします - PyPIとconda-forgeに公開します" -#: ../../tutorials/intro.md:310 +#: ../../tutorials/intro.md:314 msgid "Python packages and environments" msgstr "Pythonのパッケージと環境" -#: ../../tutorials/intro.md:312 +#: ../../tutorials/intro.md:316 msgid "" "You can install a Python package into a Python environment in the same " "way you might install NumPy or Pandas. Installing your package into an " @@ -3626,7 +3654,7 @@ msgstr "" "NumPyやPandasをインストールするのと同じように、PythonパッケージをPython環境にインストールすることができます。 " "パッケージを環境にインストールすることで、特定のPython環境を有効にして実行したコードからそのパッケージにアクセスできるようになります。" -#: ../../tutorials/intro.md:318 +#: ../../tutorials/intro.md:322 msgid "" "Diagram showing the steps associated with creating a package and then " "installing it. The first arrow says your package and the second says pip " @@ -3639,7 +3667,7 @@ msgstr "" "packageと書かれています。2つ目の矢印は、PandasやNumPyなどのいくつかのパッケージがすでにインストールされているPython環境を表すボックスにつながります。あなたのパッケージも、pip" " installしたときに同じ環境にインストールされます。" -#: ../../tutorials/intro.md:320 +#: ../../tutorials/intro.md:324 msgid "" "You don't have to publish to PyPI to make your code installable. With the" " correct file structure and project metadata you can make your code " @@ -3652,11 +3680,11 @@ msgstr "" "正しいファイル構造とプロジェクトのメタデータがあれば、PyPIに公開することなく、コードをローカルにインストールし、作業中のプロジェクトに使用することができます。" " PyPIへの公開は、自分のコードを公開し、他の人と共有したいときに便利です。" -#: ../../tutorials/intro.md:327 +#: ../../tutorials/intro.md:331 msgid "Publishing a package to PyPI / Conda-Forge" msgstr "PyPI / Conda-Forgeへのパッケージの公開" -#: ../../tutorials/intro.md:329 +#: ../../tutorials/intro.md:333 msgid "" "If you want to make your package directly installable without having to " "download the code to your computer locally then you need to publish it in" @@ -3665,13 +3693,13 @@ msgstr "" "コードをローカルにダウンロードすることなく、パッケージを直接インストールできるようにしたい場合は、 **PyPI** や **conda-" "forge** のようなリポジトリで公開する必要があります。" -#: ../../tutorials/intro.md:333 +#: ../../tutorials/intro.md:337 msgid "" "Learn [how to publish your package to PyPI in this tutorial.](publish-" "pypi.md)" msgstr "[このチュートリアルでは、パッケージをPyPIに公開する方法](publish-pypi.md) を学びます。" -#: ../../tutorials/intro.md:335 +#: ../../tutorials/intro.md:339 msgid "" "Then you can create a conda-forge recipe using the " "[Grayskull](https://github.com/conda/grayskull) tool. You can then submit" @@ -3680,13 +3708,13 @@ msgstr "" "その後、 [Grayskull](https://github.com/conda/grayskull) ツールを使ってconda-" "forgeレシピを作成することができます。 このレシピをconda-forgeに投稿することができます。" -#: ../../tutorials/intro.md:337 +#: ../../tutorials/intro.md:341 msgid "" "[You will learn more about the conda-forge publication process here" ".](publish-conda-forge.md)" msgstr "[conda-forgeの公開プロセスについてはこちらをご覧ください。](publish-conda-forge.md)" -#: ../../tutorials/intro.md:340 +#: ../../tutorials/intro.md:344 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" @@ -3700,7 +3728,7 @@ msgstr "" "ハイレベルなパッケージングのワークフローを示すグラフィックです。左側には、コード、メタデータ、テストが入ったグラフィックがあります。ドキュメンテーションやデータは、通常、パッケージホイールの配布物には掲載されないため、そのボックスの下にあります。右の矢印は、ビルド配布ファイルのボックスに移動します。このボックスは、TestPyPIか本物のPyPIのどちらかに公開するように導きます" "。PyPIからconda-forgeに接続し、ディストリビューションをPyPIからconda-forgeに送る自動ビルドを行うことができます。" -#: ../../tutorials/intro.md:342 +#: ../../tutorials/intro.md:346 msgid "" "In the image above, you can see the steps associated with publishing your" " package on PyPI and conda-forge. PyPI supports [sdist](#python-source-" @@ -3718,11 +3746,11 @@ msgstr "" "forgeレシピリポジトリでprを開きます。このプロセスについては、 [conda-forgeのレッスン](/tutorials/publish-" "conda-forge) で詳しく学びます。" -#: ../../tutorials/intro.md:346 +#: ../../tutorials/intro.md:350 msgid "Yay, your package has users! Now what?" msgstr "やった、あなたのパッケージにはユーザーがいます! さて、どうしますか？" -#: ../../tutorials/intro.md:348 +#: ../../tutorials/intro.md:352 msgid "" "As the community using your package grows, you may also find yourself " "managing users, contributors, and others who want to interact with your " @@ -3734,11 +3762,11 @@ msgstr "" "あなたのパッケージを使うコミュニティが大きくなるにつれて、あなたはユーザーや貢献者、その他あなたのパッケージと交流したい人たちを管理することになるかもしれません。開発に飛び込む前に、これらすべてを考慮することが重要です。" " コミュニティーの中にユーザーベースができれば、人々はあなたのコードに依存するようになり、その使い方の指示を必要とするようになります。" -#: ../../tutorials/intro.md:350 +#: ../../tutorials/intro.md:354 msgid "To support your community, you'll want to add things like:" msgstr "コミュニティをサポートするために、以下のようなものを追加したいです:" -#: ../../tutorials/intro.md:352 +#: ../../tutorials/intro.md:356 msgid "" "[a development guide that documents your maintainer workflow process " "](/documentation/repository-files/development-guide.md)" @@ -3746,7 +3774,7 @@ msgstr "" "[メンテナーのワークフロープロセスを文書化した開発ガイド](/documentation/repository-files" "/development-guide.md)" -#: ../../tutorials/intro.md:353 +#: ../../tutorials/intro.md:357 msgid "" "[a code of conduct to defines community interaction standards and " "expectations](/documentation/repository-files/code-of-conduct-file.md)" @@ -3754,7 +3782,7 @@ msgstr "" "[コミュニティとの交流の基準と期待を定める行動規範](/documentation/repository-files/code-of-" "conduct-file.md)" -#: ../../tutorials/intro.md:354 +#: ../../tutorials/intro.md:358 msgid "" "[a contributing guide that helps users understand expectations associated" " with making contributions to your project](/documentation/repository-" @@ -3763,11 +3791,11 @@ msgstr "" "[プロジェクトに貢献する際にユーザーが期待されることを理解するのに役立つ貢献ガイド](/documentation/repository-" "files/contributing-file.md)" -#: ../../tutorials/intro.md:356 +#: ../../tutorials/intro.md:360 msgid "Support for contributors and maintainers" msgstr "コントリビューターとメンテナーのサポート" -#: ../../tutorials/intro.md:358 +#: ../../tutorials/intro.md:362 msgid "" "If you intend for others to use and contribute to your code, consider who" " will maintain it over time. You will want a **contributing and " @@ -3780,7 +3808,7 @@ msgstr "" " **貢献と開発** ガイドと、コミュニティの交流があなたにとっても貢献者やメンテナチームにとっても健全であり続けるようにするための " "**行動規範** が欲しいでしょう。" -#: ../../tutorials/intro.md:360 +#: ../../tutorials/intro.md:364 msgid "" "The elements above are also important for future maintenance of your " "package. In the case that you are no long able to maintain it or simply " @@ -3790,11 +3818,11 @@ msgstr "" "上記の要素は、今後のパッケージのメンテナンスにおいても重要です。 " "メンテナンスができなくなった場合、あるいは単に追加的な助けが欲しい場合、開発、そしてドキュメントの貢献は、新しいメンテナへの参加を支援します。" -#: ../../tutorials/intro.md:365 +#: ../../tutorials/intro.md:369 msgid "What's next?" msgstr "次のレッスン" -#: ../../tutorials/intro.md:367 +#: ../../tutorials/intro.md:371 msgid "" "In future lessons you will learn more about the infrastructure around a " "published Python package that makes it both easier to maintain, easier " @@ -3803,7 +3831,7 @@ msgid "" "Python package." msgstr "今後のレッスンでは、公開された、メンテナンスが容易になり、他の人が貢献しやすくなり、他の科学者が使いやすくなるPythonパッケージのインフラについて学びます。しかし、まずはPythonパッケージを公開するという最初のゴールに到達してもらいたいと思います。" -#: ../../tutorials/intro.md:369 +#: ../../tutorials/intro.md:373 msgid "" "In this next lesson you will learn how to create a basic installable " "Python package. Make your code pip installable " @@ -3837,21 +3865,22 @@ msgid "How to add a `README` and `LICENSE` file to your package" msgstr "パッケージに `README` と `LICENSE` ファイルを追加する方法" #: ../../tutorials/publish-conda-forge.md:13 +#, fuzzy msgid "" -"How to setup your `pyproject.toml` file with all of the metadata that " -"PyPI requires and also metadata that will be helpful for users to find " -"your package." +"How to setup your [pyproject.toml](pyproject-toml) file with all of the " +"metadata that PyPI requires and also metadata that will be helpful for " +"users to find your package." msgstr "" "どのように `pyproject.toml` ファイルに PyPI " "が要求するすべてのメタデータと、ユーザがあなたのパッケージを見つけるのに役立つメタデータをセットアップするかです。" -#: ../../tutorials/publish-conda-forge.md:15 +#: ../../tutorials/publish-conda-forge.md:17 msgid "" "If you have gone through all of the above lessons, you are now ready to " "publish your package on conda-forge." msgstr "上記のレッスンをすべて終えたなら、conda-forgeでパッケージを公開する準備が整いました。" -#: ../../tutorials/publish-conda-forge.md:18 +#: ../../tutorials/publish-conda-forge.md:20 msgid "" "**IMPORTANT:** Please do not practice publishing your package to conda-" "forge. You should only publish to conda-forge when you have a package on " @@ -3860,38 +3889,39 @@ msgstr "" "**重要:** パッケージをconda-forgeに公開する練習はしないでください。 conda-" "forgeに公開するのは、pypi.orgにメンテナンスする予定のパッケージがあるときだけにしてください。" -#: ../../tutorials/publish-conda-forge.md:24 ../../tutorials/publish-pypi.md:24 +#: ../../tutorials/publish-conda-forge.md:26 ../../tutorials/publish-pypi.md:24 msgid "In this lesson you will learn how to:" msgstr "このレッスンで学ぶこと:" -#: ../../tutorials/publish-conda-forge.md:26 +#: ../../tutorials/publish-conda-forge.md:28 msgid "Create a conda-forge yaml recipe for your package using Grayskull" msgstr "Grayskullを使用してパッケージのconda-forge yamlレシピを作成します。" -#: ../../tutorials/publish-conda-forge.md:27 +#: ../../tutorials/publish-conda-forge.md:29 msgid "" "Submit the recipe (yaml file) to the conda-forge staged recipes " "repository as a pull request" msgstr "レシピ(yamlファイル)をconda-forge staged recipesリポジトリにプルリクエストとして提出します。" -#: ../../tutorials/publish-conda-forge.md:28 +#: ../../tutorials/publish-conda-forge.md:30 msgid "" "Maintain your conda-forge package by creating new releases for your " "package on PyPI" msgstr "PyPIでパッケージの新しいリリースを作成することで、conda-forgeパッケージを維持します。" -#: ../../tutorials/publish-conda-forge.md:31 +#: ../../tutorials/publish-conda-forge.md:33 +#, fuzzy, python-brace-format msgid "" "Once your package is on PyPI you can then easily publish it to conda-" "forge using the [grayskull](https://conda.github.io/grayskull/) tool. You" " do not need to build the package specifically for conda, conda-forge " -"will build from your PyPI source distribution file (sdist)." +"will build from your PyPI {term}`Source distribution (sdist)` file." msgstr "" "パッケージがPyPIに登録されたら、 [grayskull](https://conda.github.io/grayskull/) " "ツールを使って簡単にconda-forgeに公開することができます。conda専用のパッケージをビルドする必要はない、conda-" "forgeはPyPIのソース配布ファイル (sdist) からビルドします。" -#: ../../tutorials/publish-conda-forge.md:38 +#: ../../tutorials/publish-conda-forge.md:41 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 " @@ -3904,23 +3934,24 @@ msgstr "" "forgeへの公開の流れを示す画像です。あなたのコードをPyPIが受け付ける配布ファイル(sdistとwheel)に変換します。そして、両方のディストリビューションを公開しているPyPIリポジトリへの矢印があります" "。PyPIからconda-forgeのレシピを作成し、conda-forgeに公開することができます。" -#: ../../tutorials/publish-conda-forge.md:40 +#: ../../tutorials/publish-conda-forge.md:43 +#, fuzzy, python-brace-format 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." +"Once you have published both package distributions (the {term}`Source " +"distribution (sdist)` and the {term}`Wheel (.whl)`) 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 "" "両方のパッケージ配布(ソース配布とホイール)をPyPIに公開したら、次にconda-forgeに公開します。conda-" "forgeでパッケージをビルドするには、PyPIでのソース配布が必要です。conda-" "forgeに公開するためにパッケージをリビルドする必要はありません。" -#: ../../tutorials/publish-conda-forge.md:43 +#: ../../tutorials/publish-conda-forge.md:50 msgid "What is conda-forge?" msgstr "conda-forgeとは何ですか？" -#: ../../tutorials/publish-conda-forge.md:45 +#: ../../tutorials/publish-conda-forge.md:52 msgid "" "conda is an open source package and environment management tool that can " "be used to install tools from the different channels on Anaconda.org." @@ -3928,7 +3959,7 @@ msgstr "" "conda はオープンソースのパッケージと環境管理ツールで、Anaconda.org " "のさまざまなチャンネルからツールをインストールするために使用できます。" -#: ../../tutorials/publish-conda-forge.md:48 +#: ../../tutorials/publish-conda-forge.md:55 msgid "" "You can think about a channel as a specific location where a group of " "packages are stored and can be installed from using a command such as " @@ -3949,11 +3980,11 @@ msgstr "" "recipesのGitHubリポジトリ](https://github.com/conda-forge/staged-recipes) " "での技術レビューに合格しなければなりません。" -#: ../../tutorials/publish-conda-forge.md:51 +#: ../../tutorials/publish-conda-forge.md:58 msgid "[Learn more about conda channels here.](#about-conda)" msgstr "[condaチャンネルについて詳しくはこちら。](#about-conda)" -#: ../../tutorials/publish-conda-forge.md:55 +#: ../../tutorials/publish-conda-forge.md:62 msgid "" "Graphic with the title Python package repositories. Below it says " "anything hosted on PyPI can be installed using pip install. Packaging " @@ -3971,7 +4002,7 @@ msgstr "" "チームによって管理されているものです。 その下にPyPIサーバーという行があります。 PyPI - 誰でもPyPIに公開することができます、と " "test PyPI (PyPIをテストするためのテストベッドサーバ)。" -#: ../../tutorials/publish-conda-forge.md:57 +#: ../../tutorials/publish-conda-forge.md:64 msgid "" "Conda channels represent various repositories that you can install " "packages from. Because conda-forge is community maintained, anyone can " @@ -3984,11 +4015,11 @@ msgstr "" "誰でもPyPIにパッケージを投稿し、PyPIをテストすることができます。 conda-forge とは異なり、PyPI " "に投稿されたパッケージを手動でチェックすることはありません。" -#: ../../tutorials/publish-conda-forge.md:60 +#: ../../tutorials/publish-conda-forge.md:67 msgid "Why publish to conda-forge" msgstr "conda-forgeに公開する理由" -#: ../../tutorials/publish-conda-forge.md:62 +#: ../../tutorials/publish-conda-forge.md:69 msgid "" "There are many users, especially in the scientific Python ecosystem that " "use conda as their primary package manager / environment tool. Thus, " @@ -4001,11 +4032,11 @@ msgstr "" "したがって、conda-forgeチャンネルでこれらのユーザーがパッケージを利用できるようにすることは有用です。 場合によっては、conda-" "forge上のパッケージは、pipとcondaを混ぜてインストールする際に起こりうる依存関係の衝突を最小限に抑えることができます。これは空間生態系にとって特に重要です。" -#: ../../tutorials/publish-conda-forge.md:64 +#: ../../tutorials/publish-conda-forge.md:71 msgid "How publishing to conda-forge works" msgstr "conda-forgeへの公開の仕組み" -#: ../../tutorials/publish-conda-forge.md:66 +#: ../../tutorials/publish-conda-forge.md:73 msgid "" "Once you have built and published your package to PyPI, you have " "everything that you need to publish to conda-forge. There is no " @@ -4014,7 +4045,7 @@ msgstr "" "パッケージをビルドしてPyPIに公開したら、conda-forgeに公開するために必要なものはすべて揃っています。 conda-" "forgeに公開するための追加のビルドステップは必要ありません。" -#: ../../tutorials/publish-conda-forge.md:68 +#: ../../tutorials/publish-conda-forge.md:75 msgid "" "Conda-forge will build your package from the source distribution which " "you [published to PyPI in the previous lesson](publish-pypi) using the " @@ -4023,17 +4054,17 @@ msgstr "" "Conda-forgeは、 [前のレッスンでPyPIに公開した](publish-pypi) " "ソースディストリビューションから、以下で作成するレシピを使ってパッケージをビルドします。" -#: ../../tutorials/publish-conda-forge.md:70 +#: ../../tutorials/publish-conda-forge.md:77 msgid "Conda-forge publication steps" msgstr "Conda-forgeの公開手順" -#: ../../tutorials/publish-conda-forge.md:73 +#: ../../tutorials/publish-conda-forge.md:80 msgid "" "Image showing the steps associated with publishing to conda-forge. Check " "out the caption below for a detailed description." msgstr "conda-forgeへの公開に関連する手順を示す画像です。 詳しい説明は以下のキャプションをご覧ください。" -#: ../../tutorials/publish-conda-forge.md:75 +#: ../../tutorials/publish-conda-forge.md:82 msgid "" "The steps for publishing to conda-forge begin with publishing your Python" " package to PyPI. Once you have published to PyPI you can then create a " @@ -4046,15 +4077,15 @@ msgstr "" "recipesリポジトリに投稿してレビューを受けることができます。 レシピが承認されると、あなたのパッケージはconda-" "forge上のリポジトリ（フィードストックと呼ばれます）に登録されます。" -#: ../../tutorials/publish-conda-forge.md:78 +#: ../../tutorials/publish-conda-forge.md:85 msgid "The steps to publish to conda-forge are:" msgstr "conda-forgeに公開する手順は以下の通りです:" -#: ../../tutorials/publish-conda-forge.md:80 +#: ../../tutorials/publish-conda-forge.md:87 msgid "Publish your Python package distribution files (sdist & wheel) to PyPI" msgstr "Pythonパッケージの配布ファイル (sdistとwheel) をPyPIに公開する" -#: ../../tutorials/publish-conda-forge.md:81 +#: ../../tutorials/publish-conda-forge.md:88 msgid "" "Create a conda-forge recipe, which is a yaml file with instructions on " "how to build your package on conda-forge, using the grayskull[^grayskull]" @@ -4063,7 +4094,7 @@ msgstr "" "これは、 grayskull[^grayskull] パッケージを使用して、conda-" "forge上でパッケージをビルドする方法を説明したyamlファイルです。" -#: ../../tutorials/publish-conda-forge.md:82 +#: ../../tutorials/publish-conda-forge.md:89 msgid "" "Submit the recipe (yaml file) to the conda-forge staged recipes " "repository as a pull request for review. [Click here for an example " @@ -4075,7 +4106,7 @@ msgstr "" "[pyOpenSciからの投稿例はこちらをクリックしてください](https://github.com/conda-forge/staged-" "recipes/pull/25173)" -#: ../../tutorials/publish-conda-forge.md:84 +#: ../../tutorials/publish-conda-forge.md:91 msgid "" "Once someone from the conda-forge team reviews your pull request, you may" " need to make some changes. Eventually the pull request will be approved " @@ -4084,27 +4115,27 @@ msgstr "" "conda-" "forgeチームの誰かがあなたのプルリクエストをレビューしたら、いくつかの変更が必要になるかもしれません。最終的にプルリクエストは承認され、マージされます。" -#: ../../tutorials/publish-conda-forge.md:86 +#: ../../tutorials/publish-conda-forge.md:93 msgid "" "Once your recipe is accepted and merged on conda-forge, users can install" " your package using:" msgstr "あなたのレシピがconda-forgeで承認され、マージされると、ユーザーはあなたのパッケージをインストールできます:" -#: ../../tutorials/publish-conda-forge.md:88 +#: ../../tutorials/publish-conda-forge.md:95 msgid "`conda install -c conda-forge your-package`" msgstr "`conda install -c conda-forge your-package`" -#: ../../tutorials/publish-conda-forge.md:90 +#: ../../tutorials/publish-conda-forge.md:97 msgid "" "You only create the recipe once. Once the recipe is accepted and merged, " "you only need to maintain the repository." msgstr "レシピを作成するのは一度だけです。 レシピが受け入れられマージされたら、リポジトリを管理するだけです。" -#: ../../tutorials/publish-conda-forge.md:92 +#: ../../tutorials/publish-conda-forge.md:99 msgid "Maintaining a conda-forge package" msgstr "conda-forge パッケージのメンテナンス" -#: ../../tutorials/publish-conda-forge.md:94 +#: ../../tutorials/publish-conda-forge.md:101 msgid "" "Once your package is on conda-forge, the repository will track release " "activity on the package's PyPI repository. Any time you make a new PyPI " @@ -4115,25 +4146,25 @@ msgstr "" "新しいソースディストリビューションで新しい PyPI リリースを作成すると、conda-forge はあなたの conda-forge " "リポジトリ（フィードストックとも呼ばれます）をビルドして更新します。" -#: ../../tutorials/publish-conda-forge.md:96 +#: ../../tutorials/publish-conda-forge.md:103 msgid "" "When the update is processed, the friendly conda-forge bot will create a " "new pull request with an updated distribution recipe in your feedstock." msgstr "アップデートが処理されると、フレンドリーなconda-forgeボットがフィードストックの配布レシピを更新した新しいプルリクエストを作成します。" -#: ../../tutorials/publish-conda-forge.md:98 +#: ../../tutorials/publish-conda-forge.md:105 msgid "" "You can review that pull request and then merge it once all of the " "continuous integration tests pass." msgstr "そのプルリクエストをレビューし、継続的インテグレーションのテストがすべてパスしたら、それをマージすることができます。" -#: ../../tutorials/publish-conda-forge.md:100 +#: ../../tutorials/publish-conda-forge.md:107 msgid "" " How to Publish your package" " on conda-forge" msgstr " conda-forgeでパッケージを公開する方法" -#: ../../tutorials/publish-conda-forge.md:102 +#: ../../tutorials/publish-conda-forge.md:109 msgid "" "It's time to add your package to the conda-forge channel. Remember that " "your package needs to be on PyPI before the steps below will work. And " @@ -4143,19 +4174,19 @@ msgstr "" "以下の手順が動作する前に、あなたのパッケージがPyPI上にある必要があることを覚えておいてください。また、conda-" "forgeを管理しているチームはすべてボランティアであることを忘れないでください。" -#: ../../tutorials/publish-conda-forge.md:105 +#: ../../tutorials/publish-conda-forge.md:112 msgid "" "Be sure that your package is on PyPI.org (not test.pypi.org) before you " "attempt to publish to conda-forge." msgstr "conda-forgeに公開する前に、あなたのパッケージが（test.pypi.orgではなく）PyPI.orgにあることを確認してください。" -#: ../../tutorials/publish-conda-forge.md:108 +#: ../../tutorials/publish-conda-forge.md:115 msgid "" "Only submit your package to conda-forge if you intend to maintain it over" " time." msgstr "パッケージをconda-forgeに投稿するのは、長期的にメンテナンスするつもりである場合だけにしてください。" -#: ../../tutorials/publish-conda-forge.md:111 +#: ../../tutorials/publish-conda-forge.md:118 msgid "" "Note - this is a tutorial aimed to help you get your package onto conda-" "forge. The official conda documentation for this processed [is " @@ -4165,11 +4196,11 @@ msgstr "" "forgeに載せる手助けをすることを目的としています。この処理に関するcondaの公式ドキュメントは [こちら](https://conda-" "forge.org/docs/maintainer/adding_pkgs.html) 。" -#: ../../tutorials/publish-conda-forge.md:113 +#: ../../tutorials/publish-conda-forge.md:120 msgid "Step 1: Install grayskull" msgstr "ステップ1: grayskullをインストールする" -#: ../../tutorials/publish-conda-forge.md:115 +#: ../../tutorials/publish-conda-forge.md:122 msgid "" "First, [install " "grayskull](https://conda.github.io/grayskull/user_guide.html). You can " @@ -4179,17 +4210,17 @@ msgstr "" "[grayskullをインストールします](https://conda.github.io/grayskull/user_guide.html) " "。 pip を使用してインストールできます:" -#: ../../tutorials/publish-conda-forge.md:121 +#: ../../tutorials/publish-conda-forge.md:128 msgid "or conda" msgstr "それともconda" -#: ../../tutorials/publish-conda-forge.md:127 +#: ../../tutorials/publish-conda-forge.md:134 msgid "" "To run this command, use the same shell / terminal that you have been " "using to run hatch commands in the previous tutorials." msgstr "このコマンドを実行するには、前のチュートリアルでhatchコマンドを実行するのに使ったのと同じシェル/ターミナルを使います。" -#: ../../tutorials/publish-conda-forge.md:132 +#: ../../tutorials/publish-conda-forge.md:139 msgid "" "You can also install grayskull using pipx[^pipx]. pipx is a tool that " "allows you to install commonly used tools that you might want to have " @@ -4199,17 +4230,17 @@ msgstr "" "pipx[^pipx] を使用してgrayskullをインストールすることもできます。 " "pipxは、作成したPython環境すべてにパッケージをインストールするのではなく、複数のPython環境で利用できるようにしたい、よく使われるツールをインストールできるツールです。" -#: ../../tutorials/publish-conda-forge.md:135 +#: ../../tutorials/publish-conda-forge.md:142 msgid "Step 2: Fork and clone the conda-forge staged-recipes repository" msgstr "ステップ 2: conda-forge staged-recipes リポジトリをフォークしてクローンします。" -#: ../../tutorials/publish-conda-forge.md:137 +#: ../../tutorials/publish-conda-forge.md:144 msgid "" "Next, open your shell and `cd` to a location where you want to clone the " "**conda-forge/staged-recipes** repository." msgstr "次に、シェルを開き、 **conda-forge/staged-recipes** リポジトリをクローンしたい場所に `cd` します。" -#: ../../tutorials/publish-conda-forge.md:138 +#: ../../tutorials/publish-conda-forge.md:145 msgid "" "fork and clone the [conda-forge/staged-recipes GitHub " "repository](https://github.com/conda-forge/staged-recipes)." @@ -4217,21 +4248,21 @@ msgstr "" "[conda-forge/staged-recipes GitHubリポジトリ](https://github.com/conda-forge" "/staged-recipes) をフォークしてクローンしてください。" -#: ../../tutorials/publish-conda-forge.md:139 +#: ../../tutorials/publish-conda-forge.md:146 msgid "" "Create a new branch in your fork rather than submitting from the main " "branch of your fork. We suggest naming the branch your package's name." msgstr "フォークのメインブランチから投稿するのではなく、フォークに新しいブランチを作成してください。ブランチにパッケージ名をつけることをお勧めします。" -#: ../../tutorials/publish-conda-forge.md:141 +#: ../../tutorials/publish-conda-forge.md:148 msgid "`git checkout -b your-package-name `" msgstr "`git checkout -b your-package-name `" -#: ../../tutorials/publish-conda-forge.md:143 +#: ../../tutorials/publish-conda-forge.md:150 msgid "In bash, `cd` into the `staged-recipes/recipes` folder" msgstr "bashで `cd` を `staged-recipes/recipes` フォルダに入れる。" -#: ../../tutorials/publish-conda-forge.md:151 +#: ../../tutorials/publish-conda-forge.md:158 msgid "" "Next, create a new branch in your `conda-forge/staged-recipes` cloned " "repository. You might want to make that branch the same name as your " @@ -4240,69 +4271,69 @@ msgstr "" "次に、クローンした `conda-forge/staged-recipes` リポジトリに新しいブランチを作成します。 " "そのブランチを、あなたのパッケージと同じ名前にしたいかもしれません。" -#: ../../tutorials/publish-conda-forge.md:162 +#: ../../tutorials/publish-conda-forge.md:169 msgid "Step 3: Create your conda-forge recipe" msgstr "ステップ3: conda-forgeレシピの作成" -#: ../../tutorials/publish-conda-forge.md:164 +#: ../../tutorials/publish-conda-forge.md:171 msgid "Next, navigate to the recipes directory" msgstr "次に、レシピディレクトリに移動します。" -#: ../../tutorials/publish-conda-forge.md:166 +#: ../../tutorials/publish-conda-forge.md:173 msgid "" "If you run `ls` here, you will notice there is an example directory with " "an example recipe for you to look at." msgstr "ここで `ls` を実行すると、レシピ例のあるexampleディレクトリがあることに気づくでしょう。" -#: ../../tutorials/publish-conda-forge.md:178 +#: ../../tutorials/publish-conda-forge.md:185 msgid "Next, run `grayskull pypi your-package-name` to generate a recipe." msgstr "次に、 `grayskull pypi your-package-name` を実行してレシピを生成します。" -#: ../../tutorials/publish-conda-forge.md:222 +#: ../../tutorials/publish-conda-forge.md:229 msgid "" "Grayskull will pull metadata about your package from PyPI. It does not " "use your local installation of the package." msgstr "Grayskull はあなたのパッケージのメタデータを PyPI から取得します。ローカルにインストールしたパッケージは使用しません。" -#: ../../tutorials/publish-conda-forge.md:223 +#: ../../tutorials/publish-conda-forge.md:230 msgid "" "An internet connection is needed to run the `grayskull pypi your-package-" "name` step." msgstr "`grayskull pypi your-package-name` のステップを実行するにはインターネット接続が必要です。" -#: ../../tutorials/publish-conda-forge.md:226 +#: ../../tutorials/publish-conda-forge.md:233 msgid "" "When you run grayskull, it will grab the latest distribution of your " "package from PyPI and will use that to create a new recipe." msgstr "grayskullを実行すると、PyPIからあなたのパッケージの最新のディストリビューションを取得し、それを使って新しいレシピを作成します。" -#: ../../tutorials/publish-conda-forge.md:228 +#: ../../tutorials/publish-conda-forge.md:235 msgid "" "The recipe will be saved in a directory named after your package's name, " "wherever you run the command." msgstr "レシピは、コマンドを実行した場所の、あなたのパッケージ名にちなんだ名前のディレクトリに保存されます。" -#: ../../tutorials/publish-conda-forge.md:230 +#: ../../tutorials/publish-conda-forge.md:237 msgid "`recipes/packagename/meta.yaml`" msgstr "`recipes/packagename/meta.yaml`" -#: ../../tutorials/publish-conda-forge.md:232 +#: ../../tutorials/publish-conda-forge.md:239 msgid "" "At the very bottom of the grayskull output, it will also tell you where " "it saved the recipe file." msgstr "grayskull 出力の一番下にある、レシピファイルの保存場所も教えてくれます。" -#: ../../tutorials/publish-conda-forge.md:235 +#: ../../tutorials/publish-conda-forge.md:242 msgid "" "Open the meta.yaml file. The finished `meta.yaml` file that grayskull " "creates should look like the example below:" msgstr "meta.yaml ファイルを開きます。 grayskullが作成する完成した `meta.yaml` ファイルは、以下の例のようになるはずです:" -#: ../../tutorials/publish-conda-forge.md:282 +#: ../../tutorials/publish-conda-forge.md:289 msgid "Step 3b: Bug fix - add a home url to the about: section" msgstr "ステップ 3b: バグフィクス - about:セクションにホームURLを追加します" -#: ../../tutorials/publish-conda-forge.md:284 +#: ../../tutorials/publish-conda-forge.md:291 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 " @@ -4314,19 +4345,19 @@ msgstr "" "forge linter bot から [エラーメッセージが表示されます](https://github.com/conda-forge" "/staged-recipes/pull/25173#issuecomment-1917916528) 。" -#: ../../tutorials/publish-conda-forge.md:298 +#: ../../tutorials/publish-conda-forge.md:305 msgid "to fix this, open your meta.yaml file in your favorite text editor." msgstr "これを修正するには、meta.yamlファイルをお好みのテキストエディタで開いてください。" -#: ../../tutorials/publish-conda-forge.md:299 +#: ../../tutorials/publish-conda-forge.md:306 msgid "and add a home: element to the about section" msgstr "そして、aboutセクションに home: 要素を追加します" -#: ../../tutorials/publish-conda-forge.md:301 +#: ../../tutorials/publish-conda-forge.md:308 msgid "The about section will look like this after you create your recipe." msgstr "レシピを作成すると、aboutセクションはこのようになります。" -#: ../../tutorials/publish-conda-forge.md:311 +#: ../../tutorials/publish-conda-forge.md:318 msgid "" "Below you add a home: element. If you have a project home page / website " "you can use that url. Otherwise, you can also use your PyPI landing page." @@ -4334,11 +4365,11 @@ msgstr "" "以下で home: element " "を追加します。プロジェクトのホームページやウェブサイトがあれば、そのURLを使うことができます。そうでなければ、PyPIのランディングページを使うこともできます。" -#: ../../tutorials/publish-conda-forge.md:322 +#: ../../tutorials/publish-conda-forge.md:329 msgid "Step 4: tests for conda-forge" msgstr "ステップ 4: conda-forgeのテスト" -#: ../../tutorials/publish-conda-forge.md:324 +#: ../../tutorials/publish-conda-forge.md:331 msgid "" "Next, have a look at the tests section in your **meta.yaml** file. At a " "minimum you should import your package or the main modules associated " @@ -4347,35 +4378,35 @@ msgstr "" "次に、 **meta.yaml** ファイルのtestsセクションを見てください。 " "最低限、自分のパッケージか、そのパッケージに関連する主要なモジュールをインポートして `pip check` を実行する必要があります。" -#: ../../tutorials/publish-conda-forge.md:326 +#: ../../tutorials/publish-conda-forge.md:333 msgid "" "`pip check` will ensure that your package installs properly with all of " "the proper dependencies." msgstr "`pip check` は、あなたのパッケージが適切な依存関係をすべて持って正しくインストールされることを保証します。" -#: ../../tutorials/publish-conda-forge.md:338 +#: ../../tutorials/publish-conda-forge.md:345 msgid "" "If you have more advanced tests that you wish to run, you can add them " "here. However, you can also simply leave the tests section as it is." msgstr "さらに高度なテストを実施したい場合は、ここに追加することができます。 しかし、テストセクションをそのままにしておくこともできます。" -#: ../../tutorials/publish-conda-forge.md:340 +#: ../../tutorials/publish-conda-forge.md:347 msgid "Step 4: Submit a pull request to the staged-recipes repository" msgstr "ステップ 4: staged-recipesリポジトリにプルリクエストを提出します" -#: ../../tutorials/publish-conda-forge.md:342 +#: ../../tutorials/publish-conda-forge.md:349 msgid "" "Once you have completed all of the above, you are ready to open up a pull" " request in the `conda-forge/staged-recipes repository`." msgstr "上記がすべて完了したら、 `conda-forge/staged-recipes repository` でプルリクエストを開く準備ができました。" -#: ../../tutorials/publish-conda-forge.md:344 +#: ../../tutorials/publish-conda-forge.md:351 msgid "" "Submit a pull request from your fork/branch of the staged-recipes " "repository." msgstr "staged-recipesリポジトリのフォーク/ブランチからプルリクエストを提出してください。" -#: ../../tutorials/publish-conda-forge.md:345 +#: ../../tutorials/publish-conda-forge.md:352 msgid "" "Remember that the conda-forge maintainers are volunteers. Be patient for " "someone to respond and supportive in your communication with them." @@ -4387,25 +4418,25 @@ msgstr "" msgid "Conda-forge checklist help" msgstr "Conda-forgeチェックリストヘルプ" -#: ../../tutorials/publish-conda-forge.md:351 +#: ../../tutorials/publish-conda-forge.md:358 msgid "Conda-forge Staged-recipes Pull Request Checklist" msgstr "Conda-forge Staged-recipes プルリクエストチェックリスト" -#: ../../tutorials/publish-conda-forge.md:353 +#: ../../tutorials/publish-conda-forge.md:360 msgid "" "When you submit your package to conda-forge, the pull request template " "includes a list of checks that you want to ensure you have covered." msgstr "conda-forgeにパッケージを投稿する際、プルリクエストテンプレートには、あなたが確実にカバーしたいチェックリストが含まれています。" -#: ../../tutorials/publish-conda-forge.md:355 +#: ../../tutorials/publish-conda-forge.md:362 msgid "Below we break down each element of that list." msgstr "以下では、そのリストの各要素を分解します。" -#: ../../tutorials/publish-conda-forge.md:357 +#: ../../tutorials/publish-conda-forge.md:364 msgid "Pull request template checklist tips" msgstr "プルリクエストテンプレートのチェックリストのヒント" -#: ../../tutorials/publish-conda-forge.md:360 +#: ../../tutorials/publish-conda-forge.md:367 msgid "" "-[x] Title of this PR is meaningful: e.g. \"Adding my_nifty_package\", " "not \"updated meta.yaml\"." @@ -4413,7 +4444,7 @@ msgstr "" "-[x] このPRのタイトルは意味があります: 例 \"updated meta.yaml\" ではなく \"Adding " "my_nifty_package\" 。" -#: ../../tutorials/publish-conda-forge.md:362 +#: ../../tutorials/publish-conda-forge.md:369 msgid "" "**Translation:** Make sure that your pull request title is specific. We " "suggest something like: `Add recipe for `" @@ -4421,7 +4452,7 @@ msgstr "" "**翻訳:** プルリクエストのタイトルが具体的であることを確認してください。 我々は次のようなものを提案します: ` のレシピを追加`" -#: ../../tutorials/publish-conda-forge.md:365 +#: ../../tutorials/publish-conda-forge.md:372 msgid "" "-[x] License file is packaged (see [here](https://github.com/conda-forge" "/staged-" @@ -4433,7 +4464,7 @@ msgstr "" "recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73" " を参照)) 。" -#: ../../tutorials/publish-conda-forge.md:367 +#: ../../tutorials/publish-conda-forge.md:374 msgid "" "**Translation:** You should have a LICENSE file included in your " "package's source distribution. If you have followed the pyOpenSci " @@ -4447,11 +4478,11 @@ msgstr "" "build` を実行すると、conda-forge がパッケージのビルドに使用する出力 [ソースディストリビューションファイル(tar.gz " "ファイル) ](python-source-distribution) にそのファイルがバンドルされます。" -#: ../../tutorials/publish-conda-forge.md:369 +#: ../../tutorials/publish-conda-forge.md:376 msgid "[x] Source is from official source." msgstr "[x] ソースは公式ソースより。" -#: ../../tutorials/publish-conda-forge.md:371 +#: ../../tutorials/publish-conda-forge.md:378 msgid "" "**Translation:** If your package is on PyPI as you learned in the " "[previous lesson on publishing your Python package](publish-pypi) then " @@ -4462,7 +4493,7 @@ msgstr "" "で学んだように、あなたのパッケージがPyPI上にあるのであれば、問題はありません。 conda-" "forgeはディストリビューションを既知のリポジトリに公開することを推奨します。" -#: ../../tutorials/publish-conda-forge.md:373 +#: ../../tutorials/publish-conda-forge.md:380 msgid "" "-[x] Package does not vendor other packages. (If a package uses the " "source of another package, they should be separate packages or the " @@ -4471,7 +4502,7 @@ msgstr "" "-[x] パッケージは他のパッケージをベンダリングしません。 " "(あるパッケージが他のパッケージのソースを使用している場合、これらは別々のパッケージにするか、すべてのパッケージのライセンスをパッケージ化する必要があります)。" -#: ../../tutorials/publish-conda-forge.md:375 +#: ../../tutorials/publish-conda-forge.md:382 msgid "" "**Translation:** If the code base in your package is your own and it all " "shares the same LICENSE then you are in good shape. If you have code " @@ -4482,13 +4513,13 @@ msgstr "" "**翻訳:** " "あなたのパッケージのコードベースがあなた自身のものであり、それがすべて同じライセンスを共有しているのであれば、問題はありません。他のパッケージから取得したコードがある場合は、そのコードを宣言し、異なる場合はそのライセンスも含める必要があるかもしれません。これらのチュートリアルに従ったのであれば、あなたはベンダーのコードを持っていません。" -#: ../../tutorials/publish-conda-forge.md:377 +#: ../../tutorials/publish-conda-forge.md:384 msgid "" "-[x] If static libraries are linked in, the license of the static library" " is packaged." msgstr "-[x] スタティックライブラリーがリンクされている場合、スタティックライブラリーのライセンスがパッケージされます。" -#: ../../tutorials/publish-conda-forge.md:379 +#: ../../tutorials/publish-conda-forge.md:386 msgid "" "-[x] Package does not ship static libraries. If static libraries are " "needed, [follow CFEP-18](https://github.com/conda-" @@ -4497,7 +4528,7 @@ msgstr "" "-[x] パッケージには静的ライブラリは同梱されていません。静的ライブラリーが必要な場合、 [CFEP-18 " "に従います](https://github.com/conda-forge/cfep/blob/main/cfep-18.md)." -#: ../../tutorials/publish-conda-forge.md:381 +#: ../../tutorials/publish-conda-forge.md:388 msgid "" "**Translation:** A static library refers to a copy of a package built " "into your package. If your package is a pure Python package, then you can" @@ -4507,21 +4538,21 @@ msgstr "" "**翻訳:** " "スタティックライブラリーは、パッケージに組み込まれたパッケージのコピーを指します。もしあなたのパッケージが純粋なPythonパッケージであれば、スタティックライブラリが同梱されていないことを確認してください。" -#: ../../tutorials/publish-conda-forge.md:383 +#: ../../tutorials/publish-conda-forge.md:390 msgid "" "The pyOpenSci tutorials are all pure Python and as such do not use static" " libraries in a linked or shipped (included in the package distribution) " "format." msgstr "pyOpenSciチュートリアルはすべて純粋なPythonであり、リンクされた、あるいは出荷された(パッケージ配布に含まれる)形式の静的ライブラリは使用しません。" -#: ../../tutorials/publish-conda-forge.md:385 +#: ../../tutorials/publish-conda-forge.md:392 msgid "" "If your package has a more complex build that includes links to " "extensions written in other languages such as C++, then be sure to " "include the proper licenses for those extensions in your metadata." msgstr "あなたのパッケージが、C++のような他の言語で書かれた拡張機能へのリンクを含む、より複雑なビルドを持つ場合は、メタデータにそれらの拡張機能の適切なライセンスを含めるようにしてください。" -#: ../../tutorials/publish-conda-forge.md:390 +#: ../../tutorials/publish-conda-forge.md:397 msgid "" "If you want to learn more about static libraries, then [this " "overview](https://pypackaging-" @@ -4532,11 +4563,11 @@ msgstr "" "native.github.io/background/compilation_concepts/#shared-vs-static-" "libraries) が役に立つかもしれません。" -#: ../../tutorials/publish-conda-forge.md:393 +#: ../../tutorials/publish-conda-forge.md:400 msgid "-[ ] Build number is 0." msgstr "-[ ] ビルド番号は0。" -#: ../../tutorials/publish-conda-forge.md:395 +#: ../../tutorials/publish-conda-forge.md:402 msgid "" "**Translation:** The build number in your recipe is right below the " "source location of your package's source distribution. `number: 0` is " @@ -4545,7 +4576,7 @@ msgstr "" "**翻訳:** レシピのビルド番号は、パッケージのソース配布場所のすぐ下にあります。 `number: 0` " "は、レシピのそのセクションに表示されるべきものです。" -#: ../../tutorials/publish-conda-forge.md:408 +#: ../../tutorials/publish-conda-forge.md:415 msgid "" "[x] A tarball (`url`) rather than a repo (e.g. `git_url`) is used in your" " recipe (see [here](https://conda-" @@ -4554,7 +4585,7 @@ msgstr "" "[x] レシピでは、リポジトリ (例 `git_url` ) ではなく、tarball (`url`) を使用します。 (詳細は " "[こちら](https://conda-forge.org/docs/maintainer/adding_pkgs.html))。" -#: ../../tutorials/publish-conda-forge.md:410 +#: ../../tutorials/publish-conda-forge.md:417 msgid "" "**Translation:** Here conda wants you to provide a link to the source " "distribution on PyPI rather than a link to your GitHub repository " @@ -4567,13 +4598,13 @@ msgstr "" " `url:` セクションがあり、tar.gzで終わるPyPIのURLを提供していることに注意してください。これは、conda-" "forgeが使用するソースディストリビューションへのリンクです。" -#: ../../tutorials/publish-conda-forge.md:416 +#: ../../tutorials/publish-conda-forge.md:423 msgid "" "[x] GitHub users listed in the maintainer section have posted a comment " "confirming they are willing to be listed there." msgstr "[x] GitHubのメンテナセクションに掲載されているユーザーは、掲載の意思を確認するコメントを投稿しています。" -#: ../../tutorials/publish-conda-forge.md:418 +#: ../../tutorials/publish-conda-forge.md:425 msgid "" "**Translation** Once you have submitted your recipe, be sure that all " "maintainers listed in your recipe respond acknowledging that they are ok " @@ -4583,7 +4614,7 @@ msgstr "" "**Translation** レシピを提出したら、レシピに記載されているすべてのメンテナが、あなたのパッケージの conda-forge " "バージョンのメンテナとして記載されても構わないという返事をすることを確認してください。" -#: ../../tutorials/publish-conda-forge.md:420 +#: ../../tutorials/publish-conda-forge.md:427 msgid "" "[x] When in trouble, please check our [knowledge base " "documentation](https://conda-" @@ -4592,7 +4623,7 @@ msgstr "" "[x] 問題が発生した場合は、チームに問い合わせる前に [ナレッジベースのドキュメント](https://conda-" "forge.org/docs/maintainer/knowledge_base.html) を確認してください。" -#: ../../tutorials/publish-conda-forge.md:422 +#: ../../tutorials/publish-conda-forge.md:429 msgid "" "**Translation** The conda team are volunteers who spend their time " "supporting our community. Please try to troubleshoot on your own first " @@ -4601,13 +4632,13 @@ msgstr "" "**翻訳** コンダチームはボランティアで、私たちのコミュニティをサポートするために時間を費やしています。 " "彼らに助けを求める前に、まずは自分でトラブルシューティングを試みてください。" -#: ../../tutorials/publish-conda-forge.md:424 +#: ../../tutorials/publish-conda-forge.md:431 msgid "" "This is also why we don't suggest you publish to conda-forge as a " "practice run." msgstr "これが、練習としてconda-forgeに公開することをお勧めしない理由でもあります。" -#: ../../tutorials/publish-conda-forge.md:428 +#: ../../tutorials/publish-conda-forge.md:435 msgid "" "Once you create your pull request, a suite of CI actions will run that " "build and test the build of your package. A conda-forge maintainer will " @@ -4616,13 +4647,13 @@ msgstr "" "プルリクエストを作成すると、一連のCIアクションがビルドを実行し、パッケージのビルドをテストします。 conda-" "forgeのメンテナーは、あなたのレシピを良い状態にしてマージするためにあなたと協力します。" -#: ../../tutorials/publish-conda-forge.md:432 +#: ../../tutorials/publish-conda-forge.md:439 msgid "" "Image showing the 5 CI tasks that will run against your package in the " "GitHub interface after you'ce created a pull request." msgstr "プルリクエストを作成した後、GitHubのインターフェイスであなたのパッケージに対して実行される5つのCIタスクを示す画像。" -#: ../../tutorials/publish-conda-forge.md:434 +#: ../../tutorials/publish-conda-forge.md:441 msgid "" "Wait until all of the CI steps in your pull request have run. At that " "point your pull request is ready for review by a conda-forge maintainer." @@ -4630,7 +4661,7 @@ msgstr "" "プルリクエストのCIステップがすべて実行されるまで待ちます。 この時点で、あなたのプルリクエストはconda-" "forgeのメンテナによるレビューの準備が整いました。" -#: ../../tutorials/publish-conda-forge.md:437 +#: ../../tutorials/publish-conda-forge.md:444 msgid "" "In some cases getting all of the checks to run successfully in CI might " "take a bit of work. If you are struggling to get your recipe to build " @@ -4639,15 +4670,15 @@ msgstr "" "場合によっては、CIですべてのチェックを成功させるには、少し手間がかかるかもしれません。 レシピがうまくビルドできない場合は、conda-" "forge メンテナチームに助けを求めてください。" -#: ../../tutorials/publish-conda-forge.md:439 +#: ../../tutorials/publish-conda-forge.md:446 msgid "Please be patient and wait for them to respond." msgstr "辛抱強く返答を待ってください。" -#: ../../tutorials/publish-conda-forge.md:441 +#: ../../tutorials/publish-conda-forge.md:448 msgid "conda-forge staged recipes and CI failures" msgstr "conda-forgeのステージレシピとCIの失敗" -#: ../../tutorials/publish-conda-forge.md:444 +#: ../../tutorials/publish-conda-forge.md:451 msgid "" "If your package is a pure Python package that can be installed on any " "type of computer (Windows, mac, linux) and has no architecture " @@ -4659,7 +4690,7 @@ msgstr "" "Pythonまたはアーキテクチャの要求がないパッケージとして知られています) 、conda-forgeチームはLinux " "CI用のテストのみがパスすることを要求します。" -#: ../../tutorials/publish-conda-forge.md:446 +#: ../../tutorials/publish-conda-forge.md:453 msgid "" "So if tests for Windows and MAC OS fail, that is to be expected. In this " "case, don't worry about failing tests, the maintainer team can help you " @@ -4668,7 +4699,7 @@ msgstr "" "そのため、WindowsとMAC OSのテストが失敗したとしても、それは予想されることです。 " "この場合、テストの失敗を心配する必要はありません。メンテナチームが、あなたのパッケージが公開されるよう手助けしてくれます。" -#: ../../tutorials/publish-conda-forge.md:449 +#: ../../tutorials/publish-conda-forge.md:456 msgid "" "Once you have submitted your recipe, you can wait for the CI build to " "pass. If it's not passing, and you aren't sure why, a conda-forge " @@ -4677,7 +4708,7 @@ msgstr "" "レシピを提出したら、CIビルドが通過するのを待つことができます。 もしそれが通らず、その理由がわからない場合は、conda-" "forgeのメンテナーが解決してくれるでしょう。" -#: ../../tutorials/publish-conda-forge.md:451 +#: ../../tutorials/publish-conda-forge.md:458 msgid "" "Once your recipe is built and merged, the conda team will create a new " "package repository for you similar to [this one for the GemGIS " @@ -4687,7 +4718,7 @@ msgstr "" "[GemGISパッケージ用のリポジトリ](https://github.com/conda-forge/gemgis-feedstock) " "と同じような新しいパッケージリポジトリを作成します。" -#: ../../tutorials/publish-conda-forge.md:453 +#: ../../tutorials/publish-conda-forge.md:460 msgid "" " Congratulations - you " "have added your package to conda-forge. おめでとう - パッケージをconda-" "forgeに追加しました。" -#: ../../tutorials/publish-conda-forge.md:455 +#: ../../tutorials/publish-conda-forge.md:462 msgid "" "The last part of this process is maintaining the repository. We cover " "that next." msgstr "このプロセスの最後の部分は、リポジトリの管理です。次はそれを取り上げます。" -#: ../../tutorials/publish-conda-forge.md:458 +#: ../../tutorials/publish-conda-forge.md:465 msgid "Maintaining your conda-forge feedstock" msgstr "conda-forgeフィードストックのメンテナンス" -#: ../../tutorials/publish-conda-forge.md:460 +#: ../../tutorials/publish-conda-forge.md:467 msgid "" "Every time you create a new release on PyPI, the conda-forge bots will " "recognize the release and will rebuild the newly released version of your" @@ -4715,7 +4746,7 @@ msgstr "" "PyPIで新しいリリースを作成するたびに、conda-" "forgeボットはそのリリースを認識し、新しくリリースされたバージョンのパッケージをリビルドします。このプロセスには1-2日かかることがありますので、気長にお待ちください。" -#: ../../tutorials/publish-conda-forge.md:462 +#: ../../tutorials/publish-conda-forge.md:469 msgid "" "Once the conda-forge build is complete, all of the maintainers of your " "conda-forge feedstock will get a ping on GitHub that a new pull request " @@ -4724,7 +4755,7 @@ msgstr "" "conda-forgeのビルドが完了すると、 conda-forge feedstock " "の全メンテナにGitHubで新しいプルリクエストが開かれたことが通知されます。" -#: ../../tutorials/publish-conda-forge.md:464 +#: ../../tutorials/publish-conda-forge.md:471 msgid "" "Review the pull request. If all tests are passing, you can merge it. " "Shortly after merging your pull request, the conda-forge release will be " @@ -4733,39 +4764,39 @@ msgstr "" "プルリクエストを確認します。すべてのテストがパスすれば、マージできます。あなたのプルリクエストをマージした直後に、conda-forge " "リリースが利用可能になり、ユーザーはインストールできるようになります:" -#: ../../tutorials/publish-conda-forge.md:466 +#: ../../tutorials/publish-conda-forge.md:473 msgid "`conda install -c conda-forge yourpackage`" msgstr "`conda install -c conda-forge yourpackage`" -#: ../../tutorials/publish-conda-forge.md:470 +#: ../../tutorials/publish-conda-forge.md:477 msgid "If you have walked through this entire tutorial series you will now:" msgstr "このチュートリアルシリーズを一通りご覧になった方なら、もうお分かりでしょう:" -#: ../../tutorials/publish-conda-forge.md:472 +#: ../../tutorials/publish-conda-forge.md:479 msgid "Understand [what a Python package is ](intro.md)" msgstr "[Pythonパッケージとは何か](intro.md) を理解する" -#: ../../tutorials/publish-conda-forge.md:473 +#: ../../tutorials/publish-conda-forge.md:480 msgid "" "Know how to [make your code installable](create-python-package.md) into " "Python environments" msgstr "[コードをPython環境にインストール可能にする方法](create-python-package.md) を知る" -#: ../../tutorials/publish-conda-forge.md:474 +#: ../../tutorials/publish-conda-forge.md:481 msgid "" "Know how to create a `pyproject.toml` file, a `README` file, and a " "`LICENSE` and code of conduct." msgstr "`pyproject.toml` ファイル、 `README` ファイル、 `LICENSE` と行動規範の作成方法を知っている。" -#: ../../tutorials/publish-conda-forge.md:475 +#: ../../tutorials/publish-conda-forge.md:482 msgid "Know how to [publish your package to PyPI](publish-pypi.md) and" msgstr "[パッケージをPyPIに公開する](publish-pypi.md) 方法と" -#: ../../tutorials/publish-conda-forge.md:476 +#: ../../tutorials/publish-conda-forge.md:483 msgid "Know how to publish your package to conda-forge" msgstr "パッケージをconda-forgeに公開する方法を知ります" -#: ../../tutorials/publish-conda-forge.md:478 +#: ../../tutorials/publish-conda-forge.md:485 msgid "" "The above are the basic steps that you need to take to create and publish" " a Python package. In a future tutorial series we will cover that basics " @@ -4774,11 +4805,11 @@ msgstr "" "以上が、Pythonパッケージを作成して公開するために必要な基本的な手順です。 " "今後のチュートリアルシリーズでは、パッケージのメンテナンスの基本について取り上げます。" -#: ../../tutorials/publish-conda-forge.md:482 +#: ../../tutorials/publish-conda-forge.md:489 msgid "[Grayskull blogpost](https://conda-forge.org/blog/2020/03/05/grayskull/)" msgstr "[Grayskull blogpost](https://conda-forge.org/blog/2020/03/05/grayskull/)" -#: ../../tutorials/publish-conda-forge.md:483 +#: ../../tutorials/publish-conda-forge.md:490 msgid "[Pipx documentation](https://pipx.pypa.io/stable/)" msgstr "[Pipx documentation](https://pipx.pypa.io/stable/)" @@ -4806,24 +4837,28 @@ msgid "How to make your code installable." msgstr "コードをインストール可能にします。" #: ../../tutorials/publish-pypi.md:26 -msgid "Build your package's source (sdist) and wheel distributions" -msgstr "パッケージのソース (sdist) とwheelディストリビューションをビルドします。" +#, python-brace-format +msgid "" +"Build your package's {term}`Source distribution (sdist)` and {term}`Wheel" +" (.whl)` {term}`Distribution files`" +msgstr "" -#: ../../tutorials/publish-pypi.md:27 +#: ../../tutorials/publish-pypi.md:28 msgid "Setup an account on TestPyPI (the process is similar for PyPI)" msgstr "TestPyPIにアカウントを設定する（PyPIでも同様の手順です）" -#: ../../tutorials/publish-pypi.md:28 +#: ../../tutorials/publish-pypi.md:29 msgid "Publish your package to TestPyPI and PyPI" msgstr "パッケージをTestPyPIとPyPIに公開する" -#: ../../tutorials/publish-pypi.md:30 +#: ../../tutorials/publish-pypi.md:31 +#, fuzzy msgid "" -"You will do all of your development work in this lesson using " -"[Hatch](https://hatch.pypa.io/latest/)." +"You will do all of your development work in this lesson using [Hatch" +"](get-to-know-hatch)." msgstr "このレッスンでは、すべての開発作業を [Hatch](https://hatch.pypa.io/latest/) を使って行います。" -#: ../../tutorials/publish-pypi.md:32 +#: ../../tutorials/publish-pypi.md:34 msgid "" "Once your package is on PyPI you can publish it to conda-forge (which is " "a channel on conda) using " @@ -4832,13 +4867,13 @@ msgstr "" "パッケージがPyPIに載ったら、 [Grayskull](https://conda.github.io/grayskull/) " "を使ってconda-forge (condaのチャンネルです) に公開できます。" -#: ../../tutorials/publish-pypi.md:35 +#: ../../tutorials/publish-pypi.md:37 msgid "" "You will learn how to publish to conda-forge in the [next lesson" "](publish-conda-forge)." msgstr "conda-forgeに公開する方法は [次のレッスン](publish-conda-forge) で学びます。" -#: ../../tutorials/publish-pypi.md:39 +#: ../../tutorials/publish-pypi.md:41 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" @@ -4855,7 +4890,7 @@ msgstr "" "。PyPIからconda-forgeに接続することで、PyPIからconda-" "forgeにディストリビューションを送る自動ビルドを行うことができるからです。" -#: ../../tutorials/publish-pypi.md:41 +#: ../../tutorials/publish-pypi.md:43 msgid "" "You need to build your Python package in order to publish it to PyPI (or " "Conda). The build process organizes your code and metadata into a " @@ -4865,17 +4900,17 @@ msgstr "" "PythonパッケージをPyPI（またはConda）に公開するには、ビルドする必要があります。ビルドプロセスは、あなたのコードとメタデータをPyPIにアップロードできる配布フォーマットに整理し、その後ユーザーがダウンロードしてインストールできるようにします。" " " -#: ../../tutorials/publish-pypi.md:44 +#: ../../tutorials/publish-pypi.md:46 msgid "TestPyPI vs PyPI" msgstr "TestPyPI vs PyPI" -#: ../../tutorials/publish-pypi.md:46 +#: ../../tutorials/publish-pypi.md:48 msgid "" "There are two repositories associated with PyPI to which you can upload " "your Python package." msgstr "PyPIには、Pythonパッケージをアップロードできる2つのリポジトリがあります。" -#: ../../tutorials/publish-pypi.md:49 +#: ../../tutorials/publish-pypi.md:51 msgid "" "**[TestPyPI](https://test.pypi.org):** TestPyPI is a package repository " "provided by PyPI that you can use for testing that your package can be " @@ -4886,7 +4921,7 @@ msgstr "" "**[TestPyPI](https://test.pypi.org):** " "TestPyPIはPyPIが提供するパッケージリポジトリで、あなたのパッケージが正しくアップロード、ダウンロード、インストールできるかをテストするために使用できます。これは、実際のPyPIサービスに不完全なパッケージを公開することなく、パッケージを公開する方法を学び、練習するのに最適な場所です。" -#: ../../tutorials/publish-pypi.md:50 +#: ../../tutorials/publish-pypi.md:52 msgid "" "**[PyPI](https://pypi.org):** This is the live, production PyPI " "repository where you can officially publish your Python package, and from" @@ -4900,17 +4935,17 @@ msgstr "" "PyPIにパッケージを公開するのは、それが他の人に使われる準備ができたとき、そして/またはそれがあなたが保守するパッケージになると確信したときだけにしてください。" " PyPIはPythonパッケージの公開方法を学ぶ練習の場ではありません。" -#: ../../tutorials/publish-pypi.md:52 +#: ../../tutorials/publish-pypi.md:54 msgid "" "The steps for publishing on TestPyPI vs. PyPI are similar with the " "exception of a different url. We will point out where they differ." msgstr "TestPyPIとPyPIで公開する手順は、URLが異なることを除いて似ています。両者の相違点を指摘します。" -#: ../../tutorials/publish-pypi.md:55 +#: ../../tutorials/publish-pypi.md:57 msgid "4 Steps for publishing a Python package on TestPyPI (or PyPI)" msgstr "TestPyPI (またはPyPI)でPythonパッケージを公開するための4つのステップ" -#: ../../tutorials/publish-pypi.md:57 +#: ../../tutorials/publish-pypi.md:59 msgid "" "In this lesson you will learn how to publish your package to TestPyPI " "using [Hatch](https://hatch.pypa.io/latest/). There are 4 things that you" @@ -4920,39 +4955,41 @@ msgstr "" "を使ってパッケージをTestPyPIに公開する方法を学びます。 Pythonパッケージを公開するために必要なことは4つあります: " "TestPyPIでは。必要なのは:" -#: ../../tutorials/publish-pypi.md:62 +#: ../../tutorials/publish-pypi.md:64 msgid "**Create a package development environment**" msgstr "**パッケージ開発環境の構築**" -#: ../../tutorials/publish-pypi.md:63 +#: ../../tutorials/publish-pypi.md:65 +#, fuzzy, python-brace-format msgid "" "[**Build your package using `hatch build`**](../package-structure-code" "/python-package-distribution-files-sdist-wheel). Building a package is " "the process of turning your code into two types of distribution files: " "sdist and wheel. The wheel distribution file is particularly important " -"for users who will `pip install` your package." +"for users who will use {term}`pip` to install your package." msgstr "" "[**`hatch build` を使ってパッケージをビルドします**](../package-structure-code/python-" "package-distribution-files-sdist-wheel)。 " "パッケージのビルドは、コードを2種類の配布ファイルに変換するプロセスです: sdistとwheel。wheel配布ファイルは、あなたのパッケージを" " `pip install` するユーザーにとって特に重要です。" -#: ../../tutorials/publish-pypi.md:64 +#: ../../tutorials/publish-pypi.md:66 +#, fuzzy, python-brace-format msgid "" "**Create an account on TestPyPI (or PyPI)**: You will need to create a " -"TestPyPI account and associated token which provides permissions for you " -"to upload your package. When you later publish your package to PyPI, you " -"will need a separate PyPI account and token." +"TestPyPI account and associated {term}`API token` which provides " +"permissions for you to upload your package. When you later publish your " +"package to PyPI, you will need a separate PyPI account and token." msgstr "" "**TestPyPI (またはPyPI)でアカウントを作成します**: " "TestPyPIアカウントと、パッケージをアップロードするためのパーミッションを提供する関連トークンを作成する必要があります。 " "後でパッケージをPyPIに公開するときは、別のPyPIアカウントとトークンが必要になります。" -#: ../../tutorials/publish-pypi.md:65 +#: ../../tutorials/publish-pypi.md:67 msgid "**Publish to TestPyPI using `hatch publish`**" msgstr "** `hatch publish` を使用してTestPyPIにパブリッシュする**" -#: ../../tutorials/publish-pypi.md:67 +#: ../../tutorials/publish-pypi.md:69 #, fuzzy msgid "" "In a [future lesson](trusted-publishing), you will learn how to create an" @@ -4962,11 +4999,11 @@ msgstr "" "今後のレッスンでは、GitHub リリースを作成するたびにパッケージの更新版を PyPI に公開する、自動化された GitHub Actions " "のワークフローを作成する方法を学びます。" -#: ../../tutorials/publish-pypi.md:69 +#: ../../tutorials/publish-pypi.md:71 msgid "Learn more about building Python packages in our guide" msgstr "Pythonパッケージのビルドについては、ガイドを参照してください。" -#: ../../tutorials/publish-pypi.md:73 +#: ../../tutorials/publish-pypi.md:75 msgid "" "[Learn more about what building a Python package is](../package-" "structure-code/python-package-distribution-files-sdist-wheel)" @@ -4974,13 +5011,13 @@ msgstr "" "[Pythonパッケージのビルドについてもっと知る](../package-structure-code/python-package-" "distribution-files-sdist-wheel)" -#: ../../tutorials/publish-pypi.md:74 +#: ../../tutorials/publish-pypi.md:76 msgid "" "[Learn more about the package distribution file that PyPI needs called " "the wheel](#python-wheel)" msgstr "[PyPIが必要とするwheelと呼ばれるパッケージ配布ファイルについての詳細はこちら](#python-wheel)" -#: ../../tutorials/publish-pypi.md:75 +#: ../../tutorials/publish-pypi.md:77 msgid "" "[Learn more about the package distribution file that conda-forge will " "need on PyPI called the sdist (source distribution)](#python-source-" @@ -4989,26 +5026,26 @@ msgstr "" "[PyPIでconda-forgeが必要とするsdist (ソースディストリビューション) " "と呼ばれるパッケージ配布ファイルについてはこちらを参照してください](#python-source-distribution)" -#: ../../tutorials/publish-pypi.md:78 +#: ../../tutorials/publish-pypi.md:80 msgid "Step 1: Create a Python package development environment" msgstr "ステップ1: Pythonパッケージ開発環境の構築" -#: ../../tutorials/publish-pypi.md:80 +#: ../../tutorials/publish-pypi.md:82 msgid "" "The first step in building your package is to create a development " "environment. The Python environment will contain all of the dependencies " "needed to both install and work on your package." msgstr "パッケージ構築の最初のステップは、開発環境を作ることだ。Python環境には、あなたのパッケージのインストールと作業の両方に必要な依存関係がすべて含まれています。" -#: ../../tutorials/publish-pypi.md:82 +#: ../../tutorials/publish-pypi.md:84 msgid "Use Hatch to create your environment." msgstr "Hatchを使って環境を整えましょう。" -#: ../../tutorials/publish-pypi.md:90 +#: ../../tutorials/publish-pypi.md:92 msgid "Then view all of the current environments that hatch has access to:" msgstr "次に、Hatchがアクセスできる現在の環境をすべて表示します:" -#: ../../tutorials/publish-pypi.md:102 +#: ../../tutorials/publish-pypi.md:104 msgid "" "Then activate the environment. Note that when you call a shell from a " "Hatch environment, it will automatically install your package into the " @@ -5017,19 +5054,19 @@ msgstr "" "そして環境をアクティブにします。 " "Hatch環境からシェルを呼び出すと、開発モードまたは編集可能モードで、あなたのパッケージが自動的に環境にインストールされることに注意してください。" -#: ../../tutorials/publish-pypi.md:112 +#: ../../tutorials/publish-pypi.md:114 msgid "View what's in the environment using `pip list`:" msgstr "`pip list` を使って環境にあるものを見ます:" -#: ../../tutorials/publish-pypi.md:128 +#: ../../tutorials/publish-pypi.md:130 msgid "At any time you can exit the environment using `exit`." msgstr "いつでも `exit` を使って環境を終了することができます。" -#: ../../tutorials/publish-pypi.md:142 +#: ../../tutorials/publish-pypi.md:144 msgid "Hatch and environments" msgstr "Hatchと環境" -#: ../../tutorials/publish-pypi.md:144 +#: ../../tutorials/publish-pypi.md:146 msgid "" "Behind the scenes when hatch creates a new virtual environment, by " "default it uses venv[^venv] which is the default environment management " @@ -5038,15 +5075,15 @@ msgstr "" "hatchが新しい仮想環境を作るときの裏側では、デフォルトではPythonのインストールに付属しているデフォルトの環境管理ツールである " "venv[^venv] を使います。" -#: ../../tutorials/publish-pypi.md:147 +#: ../../tutorials/publish-pypi.md:149 msgid "Hatch will:" msgstr "Hatch は:" -#: ../../tutorials/publish-pypi.md:149 +#: ../../tutorials/publish-pypi.md:151 msgid "Create a new virtualenv (venv) that is located on your computer." msgstr "コンピュータ上に新しい仮想環境 (venv) を作成します。" -#: ../../tutorials/publish-pypi.md:150 +#: ../../tutorials/publish-pypi.md:152 msgid "" "Install your package into the environment in editable mode (similar to " "`python -m pip install -e`). This means it installs both your project and" @@ -5055,11 +5092,11 @@ msgstr "" "編集可能モードでパッケージを環境にインストールします ( `python -m pip install -e` と同様) 。 " "これは、pyproject.tomlファイルで宣言されているように、あなたのプロジェクトとプロジェクトの依存関係の両方をインストールすることを意味します。" -#: ../../tutorials/publish-pypi.md:152 +#: ../../tutorials/publish-pypi.md:154 msgid "Step 2: Build your package's sdist and wheel distributions" msgstr "ステップ 2: パッケージのsdistとwheelディストリビューションをビルドする" -#: ../../tutorials/publish-pypi.md:154 +#: ../../tutorials/publish-pypi.md:156 msgid "" "Once you have your development environment setup, you are ready to build " "your package using Hatch. Remember that building is the process of " @@ -5068,7 +5105,7 @@ msgstr "" "開発環境のセットアップが完了したら、Hatchを使ってパッケージをビルドする準備ができました。 " "ビルドとは、Pythonパッケージのファイル構造を2つの配布ファイルにするプロセスであることを覚えておいてください:" -#: ../../tutorials/publish-pypi.md:156 +#: ../../tutorials/publish-pypi.md:158 msgid "" "The [wheel distribution](#python-wheel) is a pre-built version of your " "package. It useful for users as it can be directly installed using a tool" @@ -5077,7 +5114,7 @@ msgstr "" "[wheelディストリビューション](#python-wheel) は、あなたのパッケージのビルド済みバージョンです。 `pip` " "などのツールを使って直接インストールできるので、ユーザーにとっては便利です。このファイルの拡張子は `.whl` です。" -#: ../../tutorials/publish-pypi.md:157 +#: ../../tutorials/publish-pypi.md:159 msgid "" "The [source distribution](#python-source-distribution) contains the files" " that make up your package in an unbuilt format. This file will have the " @@ -5086,7 +5123,7 @@ msgstr "" "[ソースディストリビューション](#python-source-distribution) " "には、あなたのパッケージを構成するファイルが、ビルドされていない状態で含まれています。 このファイルの拡張子は `.tar.gz` となります。" -#: ../../tutorials/publish-pypi.md:159 +#: ../../tutorials/publish-pypi.md:161 #, fuzzy msgid "" "You will use Hatch as a **Front end** tool that builds your package's " @@ -5100,15 +5137,15 @@ msgstr "" "[hatchling](https://hatch.pypa.io/latest/) ビルドバックエンドを使用するのは、 [前のレッスン" "](create-python-package)でpyproject.tomlファイルで宣言したからです。" -#: ../../tutorials/publish-pypi.md:163 +#: ../../tutorials/publish-pypi.md:165 msgid "To build your package run `hatch build`:" msgstr "パッケージをビルドするには `hatch build` を実行します:" -#: ../../tutorials/publish-pypi.md:174 +#: ../../tutorials/publish-pypi.md:176 msgid "Learn more about building a Python package" msgstr "Pythonパッケージのビルドについて" -#: ../../tutorials/publish-pypi.md:176 +#: ../../tutorials/publish-pypi.md:178 msgid "" "You can learn more about building in the [build page of our packaging " "guide](../package-structure-code/python-package-distribution-files-sdist-" @@ -5117,7 +5154,7 @@ msgstr "" "ビルドについては、 [パッケージングガイドのビルドのページ](../package-structure-code/python-package-" "distribution-files-sdist-wheel) で詳しく説明しています。" -#: ../../tutorials/publish-pypi.md:180 +#: ../../tutorials/publish-pypi.md:182 msgid "" "The sdist is important if you wish to [publish your package to conda-" "forge](publish-conda-forge). You will learn about this in a later lesson." @@ -5125,7 +5162,7 @@ msgstr "" "sdistは、conda-forgeにパッケージを [公開する場合に重要です](publish-conda-forge) " "。これについては後のレッスンで学びます。" -#: ../../tutorials/publish-pypi.md:184 +#: ../../tutorials/publish-pypi.md:186 msgid "" "➜ hatch build ────────────────────────────────────── sdist " "────────────────────────────────────── dist/pyospackage-0.1.tar.gz " @@ -5139,7 +5176,7 @@ msgstr "" "────────────────────────────────────── dist/pyospackage-0.1-py3-none-" "any.whl" -#: ../../tutorials/publish-pypi.md:191 +#: ../../tutorials/publish-pypi.md:193 msgid "" " Congratulations - " "you've created your Python package distribution files " -#: ../../tutorials/publish-pypi.md:193 +#: ../../tutorials/publish-pypi.md:195 msgid "" "You've now built your Python package and created your package " "distribution files. The next step is to setup your account on TestPyPI so" @@ -5158,11 +5195,11 @@ msgstr "" "これで Python " "パッケージをビルドし、パッケージ配布ファイルを作成しました。次のステップは、TestPyPIのアカウントをセットアップして、パッケージを公開できるようにすることです。" -#: ../../tutorials/publish-pypi.md:196 +#: ../../tutorials/publish-pypi.md:198 msgid "Step 3. Setup your TestPyPI account" msgstr "ステップ 3. TestPyPIアカウントをセットアップする" -#: ../../tutorials/publish-pypi.md:198 +#: ../../tutorials/publish-pypi.md:200 msgid "" "Next, you'll setup an account on TestPyPI. Remember that you are using " "TestPyPI here instead of the real PyPI as a way to safely learn how to " @@ -5172,11 +5209,11 @@ msgstr "" "次に、TestPyPIのアカウントをセットアップします。 TestPyPIは本物のPyPIではなく、パッケージが準備できる前に誤ってパッケージを " "\"リリース\" することなく、安全にパッケージを公開する方法を学ぶ方法として使用していることを忘れないでください。" -#: ../../tutorials/publish-pypi.md:202 +#: ../../tutorials/publish-pypi.md:204 msgid "TestPyPI vs. PyPI" msgstr "TestPyPI vs. PyPI" -#: ../../tutorials/publish-pypi.md:203 +#: ../../tutorials/publish-pypi.md:205 msgid "" "If you have a package that you are confident belongs on PyPI, all of the " "steps below will also work for you. When you publish using Hatch, you " @@ -5187,13 +5224,13 @@ msgstr "" "を使って公開する場合、TestPyPI に公開する `hatch publish -r test` ではなく、直接 PyPI に公開する " "`hatch publish` を呼び出します。" -#: ../../tutorials/publish-pypi.md:206 +#: ../../tutorials/publish-pypi.md:208 msgid "" "[Open up a web browser and go to the TestPyPI " "website](https://test.pypi.org/)." msgstr "[ウェブブラウザを開き、TestPyPIのウェブサイトにアクセスする](https://test.pypi.org/)." -#: ../../tutorials/publish-pypi.md:207 +#: ../../tutorials/publish-pypi.md:209 msgid "" "[Create an account](https://test.pypi.org/account/register/) if you don't" " already have one. Be sure to store your password in a safe place!" @@ -5202,11 +5239,11 @@ msgstr "" "[アカウントを作成してください。](https://test.pypi.org/account/register/) " "パスワードは必ず安全な場所に保管してください！" -#: ../../tutorials/publish-pypi.md:208 +#: ../../tutorials/publish-pypi.md:210 msgid "Once you have an account setup, login to it." msgstr "アカウントを設定したら、ログインしてください。" -#: ../../tutorials/publish-pypi.md:209 +#: ../../tutorials/publish-pypi.md:211 msgid "" "Search on [https://test.pypi.org/](https://test.pypi.org/) (and also on " "[https://pypi.org/](https://pypi.org/)) to ensure that the package name " @@ -5219,21 +5256,21 @@ msgstr "" "、選択したパッケージ名がすでに存在しないことを確認してください。 " "テスト用のpyosPackageを使う場合は、一意であることを保証するために、パッケージ名の最後に自分の名前かGitHubのユーザー名を追加することをお勧めします。" -#: ../../tutorials/publish-pypi.md:211 +#: ../../tutorials/publish-pypi.md:213 msgid "Example: `pyosPackage_yourNameHere`." msgstr "例: `pyosPackage_yourNameHere`." -#: ../../tutorials/publish-pypi.md:213 +#: ../../tutorials/publish-pypi.md:215 msgid "" "How to rename your Python package if the name is already taken in (test) " "PyPI" msgstr "" -#: ../../tutorials/publish-pypi.md:217 +#: ../../tutorials/publish-pypi.md:219 msgid "Required" msgstr "要件" -#: ../../tutorials/publish-pypi.md:219 +#: ../../tutorials/publish-pypi.md:221 msgid "" "Search your publishing location(s) to make sure your new name isn't taken" " ([TestPyPI](https://test.pypi.org/), [PyPI](https://pypi.org/), [conda-" @@ -5243,7 +5280,7 @@ msgstr "" "([TestPyPI](https://test.pypi.org/), [PyPI](https://pypi.org/), [conda-" "forge](https://conda-forge.org/packages/))" -#: ../../tutorials/publish-pypi.md:220 +#: ../../tutorials/publish-pypi.md:222 msgid "" "Update the project name in your pyproject.toml file (e.g. `name = " "\"pyospackage_yourNameHere\"`)" @@ -5251,39 +5288,39 @@ msgstr "" "pyproject.toml ファイルのプロジェクト名を更新します (e.g. `name = " "\"pyospackage_yourNameHere\"`)" -#: ../../tutorials/publish-pypi.md:221 +#: ../../tutorials/publish-pypi.md:223 msgid "" "Update the module folder name to be the same (e.g. " "`src/pyospackage_yourNameHere`)" msgstr "モジュールフォルダ名を同じに更新します (例: `src/pyospackage_yourNameHere`)" -#: ../../tutorials/publish-pypi.md:222 +#: ../../tutorials/publish-pypi.md:224 msgid "Rebuild your project (`hatch build`)" msgstr "プロジェクトの再ビルド (`hatch build`)" -#: ../../tutorials/publish-pypi.md:223 +#: ../../tutorials/publish-pypi.md:225 msgid "Publish your package to capture the name (continue this tutorial!)" msgstr "パッケージを公開して名前を取得する(このチュートリアルを続けましょう!)" -#: ../../tutorials/publish-pypi.md:225 +#: ../../tutorials/publish-pypi.md:227 msgid "Recommended" msgstr "おすすめ" -#: ../../tutorials/publish-pypi.md:227 +#: ../../tutorials/publish-pypi.md:229 msgid "Update the GitHub repository name to align with the new package name" msgstr "GitHubリポジトリ名を新しいパッケージ名に合わせて更新します" -#: ../../tutorials/publish-pypi.md:228 +#: ../../tutorials/publish-pypi.md:230 msgid "" "Update your local project folder to match the new package name (e.g. " "`pyospackage_yourNameHere/src`)" msgstr "ローカルのプロジェクトフォルダを新しいパッケージ名に合わせて更新します (例: `pyospackage_yourNameHere/src` ）。" -#: ../../tutorials/publish-pypi.md:229 +#: ../../tutorials/publish-pypi.md:231 msgid "Update mentions of your repository name in other files (e.g. `README.md`)" msgstr "他のファイル (例えば `README.md` ) のリポジトリ名の記述を更新します。" -#: ../../tutorials/publish-pypi.md:233 +#: ../../tutorials/publish-pypi.md:235 msgid "" "This is a screenshot of the TestPyPI website. At the top in the search " "bar, you can see the search for pyosPackage. The search return says there" @@ -5292,18 +5329,18 @@ msgstr "" "これはTestPyPIのウェブサイトのスクリーンショットです。 検索バーの一番上にpyosPackageの検索があります。pyosPackage " "の検索結果はありませんでした。 probpackageのことですか？" -#: ../../tutorials/publish-pypi.md:235 +#: ../../tutorials/publish-pypi.md:237 msgid "" "Before you try to upload to TestPyPI, check to see if the name of your " "package is already taken. You can do that using the search box at the top" " of the TestPyPI website." msgstr "TestPyPIにアップロードしようとする前に、あなたのパッケージの名前がすでに使われていないか確認してください。TestPyPIのウェブサイトの上部にある検索ボックスを使って検索することができます。" -#: ../../tutorials/publish-pypi.md:239 +#: ../../tutorials/publish-pypi.md:241 msgid "Setup 2-factor (2FA) authentication" msgstr "2ファクタ (2FA) 認証の設定" -#: ../../tutorials/publish-pypi.md:241 +#: ../../tutorials/publish-pypi.md:243 msgid "" "2-factor authentication is a secure login process that allows you to use " "a backup device that only you can access to validate that the person " @@ -5312,7 +5349,7 @@ msgid "" "account." msgstr "2要素認証とは、自分だけがアクセスできるバックアップデバイスを使用して、ログインする人が本当に自分であることを確認できる安全なログインプロセスです。他人がパスワードにアクセスし、あなたのアカウントにログインできるようにするパスワードフィッシングの問題に対処します。" -#: ../../tutorials/publish-pypi.md:244 +#: ../../tutorials/publish-pypi.md:246 msgid "" "This matters on PyPI because someone could login to your account and " "upload a version of your package that has security issues. These issues " @@ -5322,17 +5359,17 @@ msgstr "" "なぜなら、誰かがあなたのアカウントにログインして、セキュリティ上の問題があるバージョンのパッケージをアップロードする可能性があるからです。 " "これらの問題は、そのバージョンのパッケージをダウンロードしてインストールする際に、すべてのユーザーに影響を与えます。" -#: ../../tutorials/publish-pypi.md:246 +#: ../../tutorials/publish-pypi.md:248 msgid "" "2-factor authentication is required for PyPI authentication as of 1 " "January 2024." msgstr "2024年1月1日からPyPI認証に2要素認証が必要になりました。" -#: ../../tutorials/publish-pypi.md:250 +#: ../../tutorials/publish-pypi.md:252 msgid "Step 4. Create a package upload token" msgstr "ステップ4. パッケージアップロードトークンを作成する" -#: ../../tutorials/publish-pypi.md:252 +#: ../../tutorials/publish-pypi.md:254 msgid "" "To upload your package to TestPyPI (or PyPI), you will need to create a " "token for your account first, and should then create a package-specific " @@ -5342,11 +5379,11 @@ msgstr "" "パッケージをTestPyPI (またはPyPI) にアップロードするには、まず自分のアカウントのトークンを作成する必要があります。 " "(以前にこのステップを完了した場合は、パッケージを再度アップロードするときにトークンを再利用できます。)" -#: ../../tutorials/publish-pypi.md:254 +#: ../../tutorials/publish-pypi.md:256 msgid "Why create package-specific tokens?" msgstr "なぜパッケージ固有のトークンを作るのか？" -#: ../../tutorials/publish-pypi.md:256 +#: ../../tutorials/publish-pypi.md:258 msgid "" "It's ideal to create a package-specific token. When you create an " "account-wide token this allows anyone with access to the account to then " @@ -5359,61 +5396,61 @@ msgstr "" " (またはPyPI) のすべてのプロジェクトにアクセスできるようになります。 " "パッケージ固有のトークンを作成することで、トークンのスコープを特定のパッケージのみに限定することができます。これは、特にパッケージ開発で他の人と共同作業する場合に、安全な設定方法です。" -#: ../../tutorials/publish-pypi.md:259 +#: ../../tutorials/publish-pypi.md:261 #, fuzzy msgid "Follow the steps below to create your token" msgstr "以下の手順に従ってトークンを作成してください。" -#: ../../tutorials/publish-pypi.md:261 +#: ../../tutorials/publish-pypi.md:263 msgid "Login to TestPyPI and go to your account settings" msgstr "TestPyPIにログインし、アカウント設定に進みます。" -#: ../../tutorials/publish-pypi.md:262 +#: ../../tutorials/publish-pypi.md:264 msgid "Scroll down to the **API tokens** section" msgstr "**APIトークン** のセクションまでスクロールダウンしてください" -#: ../../tutorials/publish-pypi.md:263 +#: ../../tutorials/publish-pypi.md:265 msgid "Click on the **Add API Token** button" msgstr "**APIトークンの追加** ボタンをクリックしてください" -#: ../../tutorials/publish-pypi.md:264 +#: ../../tutorials/publish-pypi.md:266 msgid "" "If you are new to using TestPyPI and don't have any packages there yet, " "OR if you have other packages on TestPyPI but are uploading a new " "package, you will need to create an account-wide token." msgstr "TestPyPIを使うのが初めてで、まだパッケージを持っていない場合、またはTestPyPIに他のパッケージを持っていて、新しいパッケージをアップロードする場合、アカウントワイドトークンを作成する必要があります。" -#: ../../tutorials/publish-pypi.md:265 +#: ../../tutorials/publish-pypi.md:267 msgid "" "When you create your token, be sure to copy the token value and store it " "in a secure place before closing that browser." msgstr "トークンを作成したら、ブラウザを閉じる前に必ずトークンの値をコピーし、安全な場所に保管してください。" -#: ../../tutorials/publish-pypi.md:267 +#: ../../tutorials/publish-pypi.md:269 msgid "Your token should look something like this:" msgstr "あなたのトークンは次のようになるはずです:" -#: ../../tutorials/publish-pypi.md:269 +#: ../../tutorials/publish-pypi.md:271 msgid "`pypi-abunchofrandomcharactershere...`" msgstr "`pypi-abunchofrandomcharactershere...`" -#: ../../tutorials/publish-pypi.md:271 +#: ../../tutorials/publish-pypi.md:273 msgid "It should start with `pypi` followed by a dash and a bunch of characters." msgstr "`pypi` で始まり、ダッシュとたくさんの文字が続くはずです。" -#: ../../tutorials/publish-pypi.md:273 +#: ../../tutorials/publish-pypi.md:275 msgid "Upload to TestPyPI using Hatch" msgstr "Hatchを使用してTestPyPIにアップロードする" -#: ../../tutorials/publish-pypi.md:275 +#: ../../tutorials/publish-pypi.md:277 msgid "Once you have your token, you are ready to publish to TestPyPI." msgstr "トークンを取得したら、TestPyPIに公開する準備ができました。" -#: ../../tutorials/publish-pypi.md:278 +#: ../../tutorials/publish-pypi.md:280 msgid "Run `hatch publish -r test`" msgstr "`hatch publish -r test` を実行します" -#: ../../tutorials/publish-pypi.md:280 +#: ../../tutorials/publish-pypi.md:282 msgid "" "`-r` stands for repository. In this case because you are publishing to " "TestPyPI you will use `-r test`. Hatch will then ask for a username and " @@ -5422,17 +5459,17 @@ msgstr "" "`-r` はリポジトリを意味します。この場合、TestPyPIに公開するため、 `-r test` を使用します。 " "その後、Hatchはユーザー名と認証情報を要求します。" -#: ../../tutorials/publish-pypi.md:282 +#: ../../tutorials/publish-pypi.md:284 msgid "" "Add the word `__token__` for your username. This tells TestPyPI that you " "are using a token value rather than a username." msgstr "ユーザー名には `__token__` を追加してください。これはTestPyPIに、ユーザ名ではなくトークンの値を使用していることを伝えます。" -#: ../../tutorials/publish-pypi.md:283 +#: ../../tutorials/publish-pypi.md:285 msgid "Paste your TestPyPI token value in at the `Enter your credentials` prompt:" msgstr "`Enter your credentials` プロンプトで TestPyPI トークンの値を貼り付けます:" -#: ../../tutorials/publish-pypi.md:294 +#: ../../tutorials/publish-pypi.md:296 msgid "" "If your credentials are valid, and you have already run `hatch build` and" " thus have your 2 distribution files in a `dist/` directory then Hatch " @@ -5441,24 +5478,24 @@ msgstr "" "あなたの認証情報が有効で、すでに `hatch build` を実行し、2つの配布ファイルが `dist/` ディレクトリにあれば、Hatch " "はあなたのパッケージを TestPyPI に公開します。" -#: ../../tutorials/publish-pypi.md:298 +#: ../../tutorials/publish-pypi.md:300 msgid "" "Hatch also has a caching system so once you enter your credentials it " "will remember them." msgstr "Hatchにはキャッシュシステムもあり、一度入力した認証情報は記憶されます。" -#: ../../tutorials/publish-pypi.md:301 +#: ../../tutorials/publish-pypi.md:303 msgid "Install your package from TestPyPI" msgstr "TestPyPIからパッケージをインストールする" -#: ../../tutorials/publish-pypi.md:303 +#: ../../tutorials/publish-pypi.md:305 msgid "" "Once your package upload is complete, you can install it from TestPyPI. " "You can find the installation instructions on the TestPyPI landing page " "for your newly uploaded package." msgstr "パッケージのアップロードが完了したら、TestPyPIからインストールできます。新しくアップロードしたパッケージのTestPyPIランディングページにインストール手順があります。" -#: ../../tutorials/publish-pypi.md:308 +#: ../../tutorials/publish-pypi.md:310 msgid "" "A screenshot of the TestPyPI page for pyosPackage. It says pyosPackage " "0.1.0 at the top with the pip install instructions below. The landing " @@ -5468,7 +5505,7 @@ msgstr "" "0.1.0と書いてあり、その下にpipのインストール方法が書いてあります。 " "パッケージのランディングページには、パッケージのREADMEファイルからの情報があります。" -#: ../../tutorials/publish-pypi.md:310 +#: ../../tutorials/publish-pypi.md:312 msgid "" "This is an example landing page for the pyosPackage that was just " "uploaded. Notice at the top of the page there are instructions for how to" @@ -5479,7 +5516,7 @@ msgstr "" "ページの一番上に、TestPyPIからパッケージをインストールする方法の説明があります。 " "そのコードをコピーし、それを使ってTestPyPIからパッケージをローカルにインストールするだけです。" -#: ../../tutorials/publish-pypi.md:313 +#: ../../tutorials/publish-pypi.md:315 msgid "" "As an example, [check out our pyOpenSci pyosPackage landing page on " "TestPyPI](https://test.pypi.org/project/pyosPackage/). Notice that the " @@ -5490,11 +5527,11 @@ msgstr "" "pyosPackageランディングページをご覧ください](https://test.pypi.org/project/pyosPackage/) " "。 このページには、現在のパッケージのバージョンに関する情報と、次のようなインストール手順が記載されていることに注意してください:" -#: ../../tutorials/publish-pypi.md:317 +#: ../../tutorials/publish-pypi.md:319 msgid "`python -m pip install -i https://test.pypi.org/simple/ pyosPackage`" msgstr "`python -m pip install -i https://test.pypi.org/simple/ pyosPackage`" -#: ../../tutorials/publish-pypi.md:320 +#: ../../tutorials/publish-pypi.md:322 msgid "" "Publishing to TestPyPI vs PyPI While you can install from TestPyPI it's " "not recommended that you publish to TestPyPI as a permanent way to " @@ -5507,17 +5544,17 @@ msgstr "" "TestPyPIへの公開 vs PyPI " "TestPyPIからインストールすることはできますが、パッケージをインストールする恒久的な方法としてTestPyPIに公開することはお勧めしません。なぜなら、TestPyPIは時間が経つとアカウントを削除するかもしれないからです。TestPyPIは、パッケージを公開し、インストールプロセスをテストする方法を学ぶのに最適な場所です。しかし、最終的なゴールは、ワークフローを把握し、パッケージがデプロイできる状態になったら、PyPIに公開することです。" -#: ../../tutorials/publish-pypi.md:324 +#: ../../tutorials/publish-pypi.md:326 msgid "Time to install your package" msgstr "パッケージのインストール" -#: ../../tutorials/publish-pypi.md:326 +#: ../../tutorials/publish-pypi.md:328 msgid "" "On your computer, activate the development environment that you wish to " "install your newly published package in." msgstr "お使いのコンピューターで、新しく公開するパッケージをインストールする開発環境をアクティブにします。" -#: ../../tutorials/publish-pypi.md:328 +#: ../../tutorials/publish-pypi.md:330 msgid "Run the installation instructions for your package from TestPyPI." msgstr "TestPyPIからパッケージのインストール手順を実行します。" @@ -5529,11 +5566,11 @@ msgstr "Conda" msgid "venv Mac / Linux" msgstr "venv Mac / Linux" -#: ../../tutorials/publish-pypi.md:352 +#: ../../tutorials/publish-pypi.md:354 msgid "The value of end-to-end tools like hatch, flit and poetry" msgstr "hatch、flit、poetryといったエンドツーエンドツールの価値" -#: ../../tutorials/publish-pypi.md:353 +#: ../../tutorials/publish-pypi.md:355 msgid "" "In this lesson you are using Hatch and hatchling to create, build and " "publish your Python package. [Click here to learn about other packaging " @@ -5544,7 +5581,7 @@ msgstr "" "[エコシステム内の他のパッケージングツールについては、こちらをクリックしてください。](../package-structure-code" "/python-package-build-tools.md)" -#: ../../tutorials/publish-pypi.md:357 +#: ../../tutorials/publish-pypi.md:359 msgid "" "teach them to setup trusted publisher for actions... in the actions " "lesson https://pypi.org/help/#twofa" @@ -5552,7 +5589,7 @@ msgstr "" "actionsのレッスン https://pypi.org/help/#twofa " "で、信頼できるactionsのパブリッシャーを設定することを教えます..." -#: ../../tutorials/publish-pypi.md:360 +#: ../../tutorials/publish-pypi.md:362 msgid "" "from PyPI: https://pypi.org/help/#apitoken - You can create a token for " "an entire PyPI account, in which case, the token will work for all " @@ -5563,17 +5600,17 @@ msgstr "" "PyPIアカウント全体に対してトークンを作成することができ、その場合、トークンはそのアカウントに関連付けられているすべてのプロジェクトで動作します。" " また、トークンの範囲を特定のプロジェクトに限定することもできます。" -#: ../../tutorials/publish-pypi.md:363 +#: ../../tutorials/publish-pypi.md:365 msgid "Package-specific token vs trusted publisher" msgstr "パッケージ固有のトークンと信頼できるパブリッシャー" -#: ../../tutorials/publish-pypi.md:365 +#: ../../tutorials/publish-pypi.md:367 msgid "" "For long run maintenance of your package, you have two options related to" " PyPI publication." msgstr "パッケージの長期的なメンテナンスのために、PyPI公開に関する2つのオプションがあります。" -#: ../../tutorials/publish-pypi.md:368 +#: ../../tutorials/publish-pypi.md:370 msgid "" "You can create a package-specific token which you will use to publish " "your package (manually) to PyPI. This is a great option if you don't wish" @@ -5582,7 +5619,7 @@ msgstr "" "PyPIにパッケージを (手動で) " "公開する際に使用する、パッケージ固有のトークンを作成することができます。これはPyPI公開のワークフローを自動化したくない場合に最適なオプションです。" -#: ../../tutorials/publish-pypi.md:369 +#: ../../tutorials/publish-pypi.md:371 msgid "" "You can also create an automated publication workflow on GitHub using " "GitHub Actions. This is a great way to make the publication process " @@ -5596,26 +5633,26 @@ msgstr "" "この場合、トークンのことは気にせず、リリース時にパッケージを公開する GitHub Actionsを設定することをお勧めします。 " "その後、PyPIで \"trusted publisher\" ワークフローを作成することができます。" -#: ../../tutorials/publish-pypi.md:371 +#: ../../tutorials/publish-pypi.md:373 #, fuzzy msgid "Trusted Publishing" msgstr "パッケージパブリッシング" -#: ../../tutorials/publish-pypi.md:374 +#: ../../tutorials/publish-pypi.md:376 msgid "" "While publishing from GitHub Action is possible using tokens, we " "recommend the _Trusted Publishing_ approach as it also confers " "significant security and usability benefits." msgstr "" -#: ../../tutorials/publish-pypi.md:376 +#: ../../tutorials/publish-pypi.md:378 msgid "" "On the usability front, when Trusted Publishing is enabled, users no " "longer need to manually create API tokens on PyPI and store them in the " "GitHub release workflow." msgstr "" -#: ../../tutorials/publish-pypi.md:378 +#: ../../tutorials/publish-pypi.md:380 msgid "" "On the security front, Trusted Publishing reduces a risk related to the " "API token being long lived: with API tokens, as soon as an attacker gets " @@ -5625,70 +5662,70 @@ msgid "" "problem by minting very short lived tokens which expire automatically." msgstr "" -#: ../../tutorials/publish-pypi.md:380 +#: ../../tutorials/publish-pypi.md:382 msgid "" "For these benefits, it is recommended that users use _only_ the GitHub " "Actions release workflow to publish packages." msgstr "" -#: ../../tutorials/publish-pypi.md:383 +#: ../../tutorials/publish-pypi.md:385 msgid "" "You will learn how to create the automated trusted publisher workflow in " "a followup lesson." msgstr "自動化された信頼できるパブリッシャーワークフローの作成方法については、次のレッスンで学びます。" -#: ../../tutorials/publish-pypi.md:385 +#: ../../tutorials/publish-pypi.md:387 msgid "OPTIONAL: If you want to use a manual token-based publication workflow" msgstr "オプション: 手動トークンベースの発行ワークフローを使用する場合" -#: ../../tutorials/publish-pypi.md:387 +#: ../../tutorials/publish-pypi.md:389 msgid "" "If you plan to use your token regularly to publish to PyPI, we strongly " "recommend going through the above steps again to create a token specific " "to your new package." msgstr "トークンを定期的に使ってPyPIに公開する予定がある場合、新しいパッケージに固有のトークンを作成するために、上記の手順をもう一度行うことを強くお勧めします。" -#: ../../tutorials/publish-pypi.md:390 +#: ../../tutorials/publish-pypi.md:392 msgid "To do this:" msgstr "そのためには:" -#: ../../tutorials/publish-pypi.md:391 +#: ../../tutorials/publish-pypi.md:393 msgid "Go to TestPyPI." msgstr "TestPyPIに行きます。" -#: ../../tutorials/publish-pypi.md:392 +#: ../../tutorials/publish-pypi.md:394 msgid "Navigate to the \"Your Projects\" section of your account" msgstr "アカウントの \"Your Projects\" セクションに移動します" -#: ../../tutorials/publish-pypi.md:393 +#: ../../tutorials/publish-pypi.md:395 msgid "" "Click on the manage button for the project that you wish to add a token " "for" msgstr "トークンを追加したいプロジェクトの管理ボタンをクリックします" -#: ../../tutorials/publish-pypi.md:394 +#: ../../tutorials/publish-pypi.md:396 msgid "Go to settings" msgstr "設定に進む" -#: ../../tutorials/publish-pypi.md:395 +#: ../../tutorials/publish-pypi.md:397 msgid "Click on \"Create a token for your-package-name-here\"" msgstr "\"パッケージ名のトークンを作成する\" をクリックします" -#: ../../tutorials/publish-pypi.md:396 +#: ../../tutorials/publish-pypi.md:398 msgid "" "Create the token and follow the steps above publish your package using " "the repository specific token." msgstr "トークンを作成し、上記の手順に従って、リポジトリ固有のトークンを使用してパッケージを公開します。" -#: ../../tutorials/publish-pypi.md:398 +#: ../../tutorials/publish-pypi.md:400 msgid "And you're all done!" msgstr "そして、すべて終わりました！" -#: ../../tutorials/publish-pypi.md:400 +#: ../../tutorials/publish-pypi.md:402 msgid "Trusted Publishing instead of token-based publication" msgstr "" -#: ../../tutorials/publish-pypi.md:403 +#: ../../tutorials/publish-pypi.md:405 msgid "" "Trusted Publishing will generate short lived tokens, scoped to the " "project, on demand, only when a specific release workflows gets " @@ -5696,11 +5733,11 @@ msgid "" "with storing credentials in files/GitHub secrets." msgstr "" -#: ../../tutorials/publish-pypi.md:409 +#: ../../tutorials/publish-pypi.md:411 msgid "You have published your package to TestPyPI!" msgstr "あなたはTestPyPIにパッケージを公開しました!" -#: ../../tutorials/publish-pypi.md:411 +#: ../../tutorials/publish-pypi.md:413 msgid "" "Congratulations. You have now successfully published your package to " "TestPyPI. If you have a package that is ready for real-world use on the " @@ -5710,7 +5747,7 @@ msgstr "" "おめでとうございます。これで、TestPyPIへのパッケージの公開が成功しました。実際のPyPIで利用できる準備が整ったパッケージがあれば、同じ手順で" " (上記の違いはありますが) PyPIに公開することができます。" -#: ../../tutorials/publish-pypi.md:413 +#: ../../tutorials/publish-pypi.md:415 msgid "" "Once you publish on PyPI, you can then easily add your package to the " "conda-forge ecosystem using the [grayskull](https://conda-" @@ -5720,11 +5757,11 @@ msgstr "" "forge.org/blog/posts/2020-03-05-grayskull/) ツールを使って簡単にconda-" "forgeエコシステムにパッケージを追加できます。" -#: ../../tutorials/publish-pypi.md:415 +#: ../../tutorials/publish-pypi.md:417 msgid "You will learn how to do that in the next lesson." msgstr "その方法は次のレッスンで学習します。" -#: ../../tutorials/publish-pypi.md:419 +#: ../../tutorials/publish-pypi.md:421 msgid "https://docs.python.org/3/library/venv.html" msgstr "https://docs.python.org/3/library/venv.html" @@ -5733,37 +5770,38 @@ msgid "Make your Python package PyPI ready - pyproject.toml" msgstr "PythonパッケージをPyPIに対応させる - pyproject.toml" #: ../../tutorials/pyproject-toml.md:8 +#, fuzzy msgid "" "In [the installable code lesson](create-python-package), you learned how " "to add the bare minimum information to a `pyproject.toml` file to make it" -" installable. You then learned how to [publish a bare minimum version of " -"your package to PyPI](publish-pypi.md)." +" installable. You then learned how to publish a bare minimum version of " +"your package to [PyPI](publish-pypi)." msgstr "" "[インストール可能なコードのレッスン](create-python-package) では、 `pyproject.toml` " "ファイルに最低限の情報を追加してインストール可能にする方法を学びました。その後、 [PyPIにパッケージの最小限のバージョンを公開する" "](publish-pypi.md) 方法を学びました。" -#: ../../tutorials/pyproject-toml.md:10 +#: ../../tutorials/pyproject-toml.md:13 msgid "Following that you learned how to add a:" msgstr "それに続いて、あなたは以下の追加方法を学びました:" -#: ../../tutorials/pyproject-toml.md:11 +#: ../../tutorials/pyproject-toml.md:14 msgid "[README.md](add-readme)" msgstr "[README.md](add-readme)" -#: ../../tutorials/pyproject-toml.md:12 +#: ../../tutorials/pyproject-toml.md:15 msgid "[LICENSE](add-license-coc) and" msgstr "[LICENSE](add-license-coc) と" -#: ../../tutorials/pyproject-toml.md:13 +#: ../../tutorials/pyproject-toml.md:16 msgid "[CODE_OF_CONDUCT](add-coc)" msgstr "[CODE_OF_CONDUCT](add-coc)" -#: ../../tutorials/pyproject-toml.md:15 +#: ../../tutorials/pyproject-toml.md:18 msgid "to the root of your project directory." msgstr "プロジェクトディレクトリのルートに。" -#: ../../tutorials/pyproject-toml.md:17 +#: ../../tutorials/pyproject-toml.md:20 msgid "" "To enhance the visibility of your package on PyPI and provide more " "information about its compatibility with Python versions, project " @@ -5775,19 +5813,19 @@ msgstr "" "のバージョンとの互換性、プロジェクトの開発状況、プロジェクトのメンテナーについてより多くの情報を提供するために、 `pyproject.toml`" " ファイルに追加のメタデータを追加する必要があります。このレッスンでは、そのプロセスについて説明します。" -#: ../../tutorials/pyproject-toml.md:29 +#: ../../tutorials/pyproject-toml.md:32 msgid "" "More about the `pyproject.toml` file and how it's used to store different" " types of metadata about your package" msgstr "`pyproject.toml` ファイルの詳細と、パッケージに関するさまざまな種類のメタデータを格納するためにどのように使用されるかについて" -#: ../../tutorials/pyproject-toml.md:30 +#: ../../tutorials/pyproject-toml.md:33 msgid "" "How to declare information (metadata) about your project to help users " "find and understand it on PyPI." msgstr "ユーザーがPyPIでプロジェクトを見つけ、理解しやすくするために、プロジェクトに関する情報 (メタデータ) を宣言する方法。" -#: ../../tutorials/pyproject-toml.md:32 +#: ../../tutorials/pyproject-toml.md:35 msgid "" "If you wish to learn more about the `pyproject.toml` format, [check out " "this page. ](../package-structure-code/pyproject-toml-python-package-" @@ -5800,25 +5838,25 @@ msgstr "" msgid "Click for lesson takeaways" msgstr "レッスンのポイントはこちら" -#: ../../tutorials/pyproject-toml.md:39 +#: ../../tutorials/pyproject-toml.md:42 msgid "When creating your pyproject.toml file, consider the following:" msgstr "pyproject.tomlファイルを作成する際、以下を考慮してください:" -#: ../../tutorials/pyproject-toml.md:41 +#: ../../tutorials/pyproject-toml.md:44 msgid "" "There are only two required metadata tables that you need to install and " "publish your Python package:" msgstr "Python パッケージをインストールして公開するために必要なメタデータテーブルは 2 つだけです:" -#: ../../tutorials/pyproject-toml.md:42 +#: ../../tutorials/pyproject-toml.md:45 msgid "**[build-system]**" msgstr "**[build-system]**" -#: ../../tutorials/pyproject-toml.md:43 +#: ../../tutorials/pyproject-toml.md:46 msgid "**[project]**." msgstr "**[project]**." -#: ../../tutorials/pyproject-toml.md:44 +#: ../../tutorials/pyproject-toml.md:47 msgid "" "The **[project]** table stores your package's metadata. Within the " "**[project]** table, There are only two _required_ fields:" @@ -5826,15 +5864,15 @@ msgstr "" "**[project]** テーブルには、パッケージのメタデータが格納されます。 **[project]** テーブルの中で、 _必須_ " "フィールドは2つだけです:" -#: ../../tutorials/pyproject-toml.md:45 +#: ../../tutorials/pyproject-toml.md:48 msgid "**name=**" msgstr "**name=**" -#: ../../tutorials/pyproject-toml.md:46 +#: ../../tutorials/pyproject-toml.md:49 msgid "**version=**" msgstr "**version=**" -#: ../../tutorials/pyproject-toml.md:47 +#: ../../tutorials/pyproject-toml.md:50 msgid "" "You should add more metadata to the `[project]` table as it will make it " "easier for users to find your project on PyPI. And it will also make it " @@ -5843,7 +5881,7 @@ msgstr "" "ユーザーがPyPIであなたのプロジェクトを見つけやすくなるので、 `[project]` " "テーブルにもっとメタデータを追加するべきです。また、インストーラがあなたのパッケージのインストール方法を理解しやすくなります。" -#: ../../tutorials/pyproject-toml.md:48 +#: ../../tutorials/pyproject-toml.md:51 msgid "" "When you are adding classifiers to the **[project]** table, only use " "valid values from [PyPI's classifier " @@ -5854,7 +5892,7 @@ msgstr "" "[PyPIの分類ページ](https://PyPI.org/classifiers/) にある有効な値のみを使用してください。 " "ここで無効な値を指定すると、パッケージをビルドするときやPyPIに公開するときにエラーが発生します。" -#: ../../tutorials/pyproject-toml.md:49 +#: ../../tutorials/pyproject-toml.md:52 msgid "" "There is no specific order for tables in the `pyproject.toml` file. " "However, fields need to be placed within the correct tables. For example " @@ -5863,36 +5901,35 @@ msgstr "" "`pyproject.toml` ファイル内のテーブルには特定の順番はありません。 しかし、フィールドは正しいテーブルに配置する必要があります。 " "例えば `requires =` は常に **[build-system]** テーブルにある必要があります。" -#: ../../tutorials/pyproject-toml.md:50 +#: ../../tutorials/pyproject-toml.md:53 msgid "" "We suggest that you include your **[build-system]** table at the top of " "your `pyproject.toml` file." msgstr "**[build-system]** テーブルを `pyproject.toml` ファイルの先頭に含めることをお勧めします。" -#: ../../tutorials/pyproject-toml.md:55 +#: ../../tutorials/pyproject-toml.md:58 msgid "" "The `pyproject.toml` file is a human and machine-readable file that " "serves as the primary configuration file for your Python package." msgstr "`pyproject.toml` ファイルは人間や機械が読めるファイルで、Pythonパッケージの主要な設定ファイルとして機能します。" -#: ../../tutorials/pyproject-toml.md:59 +#: ../../tutorials/pyproject-toml.md:63 msgid "" "[Building your package](build-package) is the step that created the " "distribution files that are required for you to publish to PyPI." msgstr "[パッケージのビルド](build-package) は、PyPIに公開するために必要な配布ファイルを作成するステップです。" -#: ../../tutorials/pyproject-toml.md:63 +#: ../../tutorials/pyproject-toml.md:67 msgid "About the .toml format" msgstr ".toml フォーマットについて" -#: ../../tutorials/pyproject-toml.md:65 +#: ../../tutorials/pyproject-toml.md:69 +#, fuzzy, python-brace-format msgid "" -"The **pyproject.toml** file is written in [TOML (Tom's Obvious, Minimal " -"Language) format](https://toml.io/en/). TOML is an easy-to-read structure" -" that is based on key/value pairs. Each section in the **pyproject.toml**" -" file contains a `[table identifier]`. The TOML format can be compared to" -" other structured formats such as`.json`. However, the TOML format was " -"designed to be easier to read for humans." +"The **pyproject.toml** file is written in {term}`TOML` format. TOML is an" +" easy-to-read structure that is based on key/value pairs. Each section in" +" the **pyproject.toml** file contains a `[table identifier]`. The TOML " +"format can be compared to other structured formats such as `.json`." msgstr "" "**pyproject.toml** ファイルは [TOML (Tom's Obvious, Minimal Language) " "format](https://toml.io/en/) で書かれています。TOMLは、キーと値のペアに基づいた読みやすい構造です。 " @@ -5900,13 +5937,13 @@ msgstr "" "が含まれています。TOMLフォーマットは、 `.json` " "などの他の構造化フォーマットと比較することができます。しかし、TOMLフォーマットは人間が読みやすいように設計されています。" -#: ../../tutorials/pyproject-toml.md:67 +#: ../../tutorials/pyproject-toml.md:74 msgid "" "Below you can see the `[build-system]` table. Within that table there are" " two required key/value pairs." msgstr "以下に `[build-system]` テーブルを示す。そのテーブルの中には、2つのキーと値のペアが必要です。" -#: ../../tutorials/pyproject-toml.md:70 +#: ../../tutorials/pyproject-toml.md:77 msgid "" "`requires =` is the key and the value is `[\"hatchling\"]` within the " "`[build-system]` array specified by square brackets `[]`." @@ -5914,46 +5951,48 @@ msgstr "" "`requires =` がキーで、値は角括弧 `[]` で指定された `[build-system]` 配列内の " "`[\"hatchling\"]` です。" -#: ../../tutorials/pyproject-toml.md:80 +#: ../../tutorials/pyproject-toml.md:87 msgid "What is the pyproject.toml used for?" msgstr "pyproject.tomlは何に使うのですか？" -#: ../../tutorials/pyproject-toml.md:82 +#: ../../tutorials/pyproject-toml.md:89 msgid "The pyproject.toml file tells your build tool:" msgstr "pyproject.tomlファイルは、ビルドツールに次のように指示します:" -#: ../../tutorials/pyproject-toml.md:84 +#: ../../tutorials/pyproject-toml.md:91 +#, fuzzy, python-brace-format msgid "" -"What build backend to use to build your package (we are using `hatchling`" -" in this tutorial but there are [many others to choose from](/package-" -"structure-code/python-package-build-tools))." +"What {term}`Build backend` to use to build your package (we are using " +"{term}`Hatchling` in this tutorial but there are [many others to choose " +"from](/package-structure-code/python-package-build-tools))." msgstr "" "パッケージのビルドに使用するビルドバックエンド (このチュートリアルでは `hatchling` を使用していますが、 [他にも多くの選択肢" "](/package-structure-code/python-package-build-tools) があります)。" -#: ../../tutorials/pyproject-toml.md:85 +#: ../../tutorials/pyproject-toml.md:94 msgid "How and where to retrieve your package's version:" msgstr "パッケージのバージョンの取得方法と場所:" -#: ../../tutorials/pyproject-toml.md:86 +#: ../../tutorials/pyproject-toml.md:95 msgid "**statically** where you declare the version `version = \"0.1.0\"` or" msgstr "**静的** ここで、バージョン `version = \"0.1.0\"` または" -#: ../../tutorials/pyproject-toml.md:87 +#: ../../tutorials/pyproject-toml.md:96 msgid "" "**dynamically** where the tool looks to the most recent tag in your " "history to determine the current version." msgstr "**動的** このツールは、現在のバージョンを決定するために、履歴の最新のタグを検索します。" -#: ../../tutorials/pyproject-toml.md:88 -msgid "What dependencies your package needs" +#: ../../tutorials/pyproject-toml.md:97 +#, fuzzy, python-brace-format +msgid "What {term}`Dependencies` your package needs" msgstr "パッケージが必要とする依存関係" -#: ../../tutorials/pyproject-toml.md:89 +#: ../../tutorials/pyproject-toml.md:98 msgid "What versions of Python your package supports (important for your users)." msgstr "パッケージがサポートするPythonのバージョン (ユーザーにとって重要）。" -#: ../../tutorials/pyproject-toml.md:91 +#: ../../tutorials/pyproject-toml.md:100 msgid "" "The `pyproject.toml` file also makes it easy for anyone browsing your " "GitHub repository to quickly understand your package's structure such as:" @@ -5961,23 +6000,23 @@ msgstr "" "また、 `pyproject.toml` ファイルを使うことで、GitHub " "リポジトリを閲覧している人が次のようなパッケージの構造をすぐに理解できるようになります:" -#: ../../tutorials/pyproject-toml.md:94 +#: ../../tutorials/pyproject-toml.md:103 msgid "How your package is built," msgstr "パッケージの作り方、" -#: ../../tutorials/pyproject-toml.md:95 +#: ../../tutorials/pyproject-toml.md:104 msgid "What Python versions and operating systems it supports" msgstr "サポートするPythonのバージョンとオペレーティングシステム" -#: ../../tutorials/pyproject-toml.md:96 +#: ../../tutorials/pyproject-toml.md:105 msgid "What it does," msgstr "何をするのか？" -#: ../../tutorials/pyproject-toml.md:97 +#: ../../tutorials/pyproject-toml.md:106 msgid "Who maintains it" msgstr "誰がメンテナンスするのか" -#: ../../tutorials/pyproject-toml.md:99 +#: ../../tutorials/pyproject-toml.md:108 msgid "" "Finally, the pyproject.toml file is also often used to configure tools " "such as static type checkers (e.g. mypy) and code formatters/linters " @@ -5986,7 +6025,7 @@ msgstr "" "最後に、pyproject.tomlファイルは、静的タイプチェッカー (mypyなど) やコードフォーマッタ/リンタ (blackやruffなど)" " のようなツールを設定するためにもよく使われます。" -#: ../../tutorials/pyproject-toml.md:102 +#: ../../tutorials/pyproject-toml.md:111 msgid "" "Check out the [PyPA " "documentation](https://packaging.python.org/en/latest/tutorials" @@ -5997,7 +6036,7 @@ msgstr "" "[PyPAのドキュメント](https://packaging.python.org/en/latest/tutorials/packaging-" "projects/#choosing-a-build-backend) をチェックしてください。" -#: ../../tutorials/pyproject-toml.md:104 +#: ../../tutorials/pyproject-toml.md:113 msgid "" "Note that some build tools may deviate in how they store project " "metadata. As such you may want to refer to their documentation if you " @@ -6008,11 +6047,11 @@ msgstr "" "ビルドツールによっては、プロジェクトのメタデータを保存する方法が異なる場合があります。そのため、Hatch " "とhatchling以外のツールを使用する場合は、それらのドキュメントを参照することをお勧めします。このチュートリアルでは、PyPAのルールとガイドラインに準拠したツールであるhatchlingとhatchを選択しました。" -#: ../../tutorials/pyproject-toml.md:108 +#: ../../tutorials/pyproject-toml.md:117 msgid "How is pyproject.toml metadata used?" msgstr "pyproject.tomlのメタデータはどのように使用されますか？" -#: ../../tutorials/pyproject-toml.md:110 +#: ../../tutorials/pyproject-toml.md:119 msgid "" "The pyproject.toml file is the file that your build tool uses to populate" " a `METADATA` that is included in your Python distribution files that get" @@ -6024,7 +6063,7 @@ msgstr "" "を生成するためにビルドツールが使用するファイルです。 この `METADATA` ファイルは、PyPI によってあなたのパッケージの PyPI " "ランディングページに入力され、そこで公開されている何万ものパッケージの中からユーザをフィルタリングするのに使われます。" -#: ../../tutorials/pyproject-toml.md:113 +#: ../../tutorials/pyproject-toml.md:122 msgid "" "Image showing the left side bar of PyPI for the package xclim. The " "section at the top says Classifier. Below there is a list of items " @@ -6035,7 +6074,7 @@ msgstr "" "xclimパッケージのPyPI左サイドバーの画像です。一番上のセクションにはClassifierとあります。その下に、開発状況、対象読者、ライセンス、自然言語、オペレーティングシステム、プログラミング言語、トピックなどの項目があります。" " これらの各セクションの下には、さまざまな分類オプションがあります。 \" width=\"300px\">" -#: ../../tutorials/pyproject-toml.md:118 +#: ../../tutorials/pyproject-toml.md:127 msgid "" "When you add the classifier section to your pyproject.toml and your " "package is built, the build tool organizes the metadata into a format " @@ -6046,11 +6085,11 @@ msgstr "" "pyproject.tomlにclassifierセクションを追加してパッケージがビルドされると、ビルドツールはメタデータをPyPIが理解できる形式に整理し、PyPIのランディングページに表示します。" " これらの分類子により、ユーザはサポートするpythonのバージョンやカテゴリなどでパッケージをソートすることもできます。" -#: ../../tutorials/pyproject-toml.md:124 +#: ../../tutorials/pyproject-toml.md:133 msgid "A more in-depth overview of pyproject.toml files" msgstr "pyproject.tomlファイルのより詳細な概要" -#: ../../tutorials/pyproject-toml.md:126 +#: ../../tutorials/pyproject-toml.md:135 msgid "" "[Our guidebook page has a more in depth overview of this file" "](../package-structure-code/pyproject-toml-python-package-metadata/)" @@ -6058,31 +6097,31 @@ msgstr "" "[ガイドブックページでは、このファイルについてより詳しく説明しています](../package-structure-code/pyproject-" "toml-python-package-metadata/)" -#: ../../tutorials/pyproject-toml.md:129 +#: ../../tutorials/pyproject-toml.md:138 msgid "How to update your pyproject.toml file" msgstr "pyproject.tomlファイルを更新する方法" -#: ../../tutorials/pyproject-toml.md:131 +#: ../../tutorials/pyproject-toml.md:140 msgid "" "In the last lesson, you created a bare-bones pyproject.toml file that " "contained the core elements needed to build your package:" msgstr "最後のレッスンでは、パッケージのビルドに必要なコア要素を含む、素のpyproject.tomlファイルを作成しました:" -#: ../../tutorials/pyproject-toml.md:135 +#: ../../tutorials/pyproject-toml.md:144 msgid "" "A `[build-system]` table where you defined your project's backend build " "tool (`hatchling`)" msgstr "プロジェクトのバックエンドビルドツールを定義した `[build-system]` テーブル (`hatchling`)" -#: ../../tutorials/pyproject-toml.md:136 +#: ../../tutorials/pyproject-toml.md:145 msgid "A `[project]` table where you defined your project's version and name." msgstr "プロジェクトのバージョンと名前を定義した `[project]` テーブル。" -#: ../../tutorials/pyproject-toml.md:138 +#: ../../tutorials/pyproject-toml.md:147 msgid "The `pyproject.toml` file that you created, looked like this:" msgstr "あなたが作成した `pyproject.toml` ファイルは次のようなものです:" -#: ../../tutorials/pyproject-toml.md:150 +#: ../../tutorials/pyproject-toml.md:159 msgid "" "Your next step is to add additional recommended metadata fields that will" " both help users find your package on PyPI and also better describe the " @@ -6095,19 +6134,19 @@ msgstr "" "一度このメタデータを追加すれば、もう二度と追加する必要はありません。 " "これらのメタデータ・フィールドが定期的に更新されるのは、あなたが次のようなことをしたときだけです:" -#: ../../tutorials/pyproject-toml.md:153 +#: ../../tutorials/pyproject-toml.md:162 msgid "drop a package dependency" msgstr "パッケージ依存の削除" -#: ../../tutorials/pyproject-toml.md:154 +#: ../../tutorials/pyproject-toml.md:163 msgid "modify what Python versions your package supports." msgstr "パッケージがサポートしているPythonのバージョンを変更します。" -#: ../../tutorials/pyproject-toml.md:156 +#: ../../tutorials/pyproject-toml.md:165 msgid "More on hatchling" msgstr "Hatchlingの詳細" -#: ../../tutorials/pyproject-toml.md:159 +#: ../../tutorials/pyproject-toml.md:168 msgid "" "The documentation for the hatchling back-end is " "[here](https://hatch.pypa.io/latest/config/metadata/)" @@ -6115,11 +6154,11 @@ msgstr "" "Hatchlingのバックエンドのドキュメントは " "[こちら](https://hatch.pypa.io/latest/config/metadata/) です。" -#: ../../tutorials/pyproject-toml.md:162 +#: ../../tutorials/pyproject-toml.md:171 msgid "Step 1: Add Author, maintainer and project description" msgstr "ステップ1: 作者、メンテナ、プロジェクトの説明を追加する" -#: ../../tutorials/pyproject-toml.md:164 +#: ../../tutorials/pyproject-toml.md:173 msgid "" "After completing the [installable code tutorial](create-python-package), " "you should have a pyproject.toml file with a project name and a version " @@ -6128,40 +6167,40 @@ msgstr "" "[インストール可能なコードのチュートリアル](create-python-package) を完了すると、 `[project]` " "テーブルにプロジェクト名とバージョンを持つpyproject.tomlファイルができるはずです。" -#: ../../tutorials/pyproject-toml.md:172 +#: ../../tutorials/pyproject-toml.md:181 msgid "Add the following to your table:" msgstr "テーブルに以下を追加します:" -#: ../../tutorials/pyproject-toml.md:174 +#: ../../tutorials/pyproject-toml.md:183 msgid "" "A **description** of your package. This should be a single line and " "should briefly describe the goal of your package using non technical " "terms if as all possible!" msgstr "パッケージの**説明** これは1行で、可能な限り専門用語を使わず、あなたのパッケージの目標を簡潔に記述してください！" -#: ../../tutorials/pyproject-toml.md:175 +#: ../../tutorials/pyproject-toml.md:184 msgid "package **authors**" msgstr "パッケージ **著者**" -#: ../../tutorials/pyproject-toml.md:176 +#: ../../tutorials/pyproject-toml.md:185 msgid "package **maintainers**" msgstr "パッケージ **メンテナー**" -#: ../../tutorials/pyproject-toml.md:178 +#: ../../tutorials/pyproject-toml.md:187 msgid "The `description` is just a string like the other values you've set:" msgstr "`description` は、設定した他の値と同じように単なる文字列です:" -#: ../../tutorials/pyproject-toml.md:189 +#: ../../tutorials/pyproject-toml.md:198 msgid "" "When you add authors and maintainers you need to use a format that will " "look like a Python list with a dictionary within it:" msgstr "作者とメンテナを追加するときは、Pythonのリストに辞書を追加したような書式を使う必要があります:" -#: ../../tutorials/pyproject-toml.md:203 +#: ../../tutorials/pyproject-toml.md:212 msgid "Author names & emails" msgstr "著者名とEメール" -#: ../../tutorials/pyproject-toml.md:207 +#: ../../tutorials/pyproject-toml.md:216 msgid "" "There is a quirk with PyPI for authors that have names but not emails in " "the pyproject.toml. If you are missing the email for one or more authors " @@ -6170,17 +6209,17 @@ msgstr "" "PyPIには、pyproject.tomlに名前があってもメールがない作者のための癖があります。 " "もし、1人以上の作者やメンテナのEメールが見つからない場合は、次のようにしてください:" -#: ../../tutorials/pyproject-toml.md:216 +#: ../../tutorials/pyproject-toml.md:225 msgid "" "Then we suggest that you only provide names in your list of names to " "ensure that everything renders properly on your PyPI page - like this:" msgstr "PyPIページですべてが正しく表示されるようにするために、名前のリストには名前のみを入力することをお勧めします - このように:" -#: ../../tutorials/pyproject-toml.md:225 +#: ../../tutorials/pyproject-toml.md:234 msgid "don't have emails for everyone, we suggest that you only add names." msgstr "全員のEメールを持っていない場合は、名前だけを追加することをお勧めします。" -#: ../../tutorials/pyproject-toml.md:228 +#: ../../tutorials/pyproject-toml.md:237 msgid "" "Your `pyproject.toml` file now should look like the example below. It is " "OK if you only have 1 author and the same author is also maintainer of " @@ -6195,25 +6234,25 @@ msgid "" "source?" msgstr "さらに詳しく: オープンソースにおける作者とメンテナの違いは？" -#: ../../tutorials/pyproject-toml.md:256 +#: ../../tutorials/pyproject-toml.md:265 msgid "" "When adding maintainers and authors, you may want to think about the " "difference between the two." msgstr "メンテナと著者を追加する際には、この2つの違いについて考えてみるとよいでしょう。" -#: ../../tutorials/pyproject-toml.md:258 +#: ../../tutorials/pyproject-toml.md:267 msgid "Authors generally include people who:" msgstr "著者には一般的に以下のような人々が含まれます:" -#: ../../tutorials/pyproject-toml.md:259 +#: ../../tutorials/pyproject-toml.md:268 msgid "originally created / designed developed the package and" msgstr "もともとパッケージを作成 / デザイン開発して" -#: ../../tutorials/pyproject-toml.md:260 +#: ../../tutorials/pyproject-toml.md:269 msgid "people who add new functionality to the package." msgstr "パッケージに新しい機能を追加する人たち。" -#: ../../tutorials/pyproject-toml.md:262 +#: ../../tutorials/pyproject-toml.md:271 msgid "" "Whereas maintainers are the people that are currently, actively working " "on the project. It is often the case that there is overlap in authors and" @@ -6222,7 +6261,7 @@ msgstr "" "一方、メンテナーは、現在、積極的にプロジェクトに取り組んでいる人々です。 作者とメンテナーが重なることはよくあることです。 " "そのため、これらのリストは似たり寄ったりかもしれません。" -#: ../../tutorials/pyproject-toml.md:264 +#: ../../tutorials/pyproject-toml.md:273 msgid "" "A good example of when the lists might diverge is sometimes you have a " "package where an initial author developed it and then stepped down as a " @@ -6230,24 +6269,24 @@ msgid "" "considered an author but no longer actively maintains the package." msgstr "リストが分岐する可能性のある良い例としては、最初の作者が開発したパッケージが、他のことに移るためにメンテナを降りる場合があります。この人物は引き続き作者とみなされるかもしれないが、もはやそのパッケージを積極的に保守することはありません。" -#: ../../tutorials/pyproject-toml.md:266 +#: ../../tutorials/pyproject-toml.md:275 msgid "" "It is important to note that there are many ways to define author vs " "maintainer and we don't prescribe a single approach in this tutorial." msgstr "重要なのは、作者とメンテナを定義する方法はたくさんあるということです、そして、このチュートリアルでは、単一のアプローチを推奨するものではありません。" -#: ../../tutorials/pyproject-toml.md:268 +#: ../../tutorials/pyproject-toml.md:277 msgid "" "However, we encourage you to consider carefully, for PyPI publication, " "who you want to have listed as authors and maintainers on your PyPI " "landing page." msgstr "しかし、PyPIで公開する際には、PyPIのランディングページに作者やメンテナとして誰を掲載するか、慎重に検討することをお勧めします。" -#: ../../tutorials/pyproject-toml.md:272 +#: ../../tutorials/pyproject-toml.md:281 msgid "Step 2: Add README and license" msgstr "ステップ2: READMEとライセンスの追加" -#: ../../tutorials/pyproject-toml.md:274 +#: ../../tutorials/pyproject-toml.md:283 #, fuzzy msgid "" "In the previous lessons, you added both a [README.md](add-readme) file " @@ -6259,7 +6298,7 @@ msgstr "" "前のレッスンでは、 [README.md](add-readme) ファイルと [LICENSE](add-license-coc) " "の両方をパッケージリポジトリーに追加しました。これらのファイルを手に入れたら、以下の例に従ってpyproject.tomlファイルにリンクとして追加します。" -#: ../../tutorials/pyproject-toml.md:303 +#: ../../tutorials/pyproject-toml.md:312 msgid "" "The license entry in your pyproject.toml file must use the [license " "expression syntax](https://packaging.python.org/en/latest/specifications" @@ -6270,13 +6309,13 @@ msgid "" "license-expressions/), either version 2.2 or a later compatible version." msgstr "" -#: ../../tutorials/pyproject-toml.md:305 +#: ../../tutorials/pyproject-toml.md:314 msgid "" "If you have multiple licenses, or a custom license, you can also express " "these using a license expression." msgstr "" -#: ../../tutorials/pyproject-toml.md:307 +#: ../../tutorials/pyproject-toml.md:316 msgid "" "If you want to distribute license files, or other files containing legal " "information, with your package, you can include these using the " @@ -6284,11 +6323,11 @@ msgid "" "pyproject-toml/#license-files) entry, but this is not required." msgstr "" -#: ../../tutorials/pyproject-toml.md:309 +#: ../../tutorials/pyproject-toml.md:318 msgid "Step 3: Specify Python version with `requires-python`" msgstr "ステップ 3: `requires-python` でPythonのバージョンを指定します" -#: ../../tutorials/pyproject-toml.md:311 +#: ../../tutorials/pyproject-toml.md:320 msgid "" "Add the `requires-python` field to your `pyproject.toml` `[project]` " "table. The `requires-python` field helps pip identify which Python " @@ -6308,12 +6347,12 @@ msgstr "" "metadata/#core-metadata-requires-python) では、 `requires-python` " "をバージョン指定の文字列として定義している。ほとんどのプロジェクトは、そのパッケージがサポートする最も古いPythonのバージョンを指定します。いくつかの高度なケースでは、どの将来のPythonバージョンがサポートされるかを示す上限が設定されます。" -#: ../../tutorials/pyproject-toml.md:316 +#: ../../tutorials/pyproject-toml.md:325 #, fuzzy msgid "But how do I figure out which Python versions I should support?" msgstr "パッケージがサポートしているPythonのバージョンを変更します。" -#: ../../tutorials/pyproject-toml.md:318 +#: ../../tutorials/pyproject-toml.md:327 msgid "" "Good question. The Python developer guide provides a [status " "page](https://devguide.python.org/versions/) (and a handy visualization) " @@ -6322,14 +6361,14 @@ msgid "" "602](https://peps.python.org/pep-0602/)." msgstr "" -#: ../../tutorials/pyproject-toml.md:320 +#: ../../tutorials/pyproject-toml.md:329 msgid "" "We recommend that you use the latest Python release in the **bugfix** " "phase. If your Python release is in the **security** phase, we recommend " "migrating to a newer version of Python." msgstr "" -#: ../../tutorials/pyproject-toml.md:322 +#: ../../tutorials/pyproject-toml.md:331 msgid "" "[SPEC 0](https://scientific-python.org/specs/spec-0000/) of the " "Scientific Python project suggests a common schedule for dependencies, " @@ -6337,11 +6376,11 @@ msgid "" " project." msgstr "" -#: ../../tutorials/pyproject-toml.md:351 +#: ../../tutorials/pyproject-toml.md:360 msgid "Step 4: Specify Dependencies" msgstr "ステップ4: 依存関係の指定" -#: ../../tutorials/pyproject-toml.md:353 +#: ../../tutorials/pyproject-toml.md:362 msgid "" "Next add your dependencies table to the project table. The `dependencies " "=` section contains a list (or array in the toml language) of the Python " @@ -6353,11 +6392,11 @@ msgstr "" "セクションには、あなたのパッケージがPython環境で正しく動作するために必要なPythonパッケージのリスト（toml言語では配列）を記述します。" " 上記の `[build-system]` の表に記載されている要件と同様です:" -#: ../../tutorials/pyproject-toml.md:361 +#: ../../tutorials/pyproject-toml.md:370 msgid "dependencies are added in an array (similar to a Python list) structure." msgstr "依存関係は配列（Pythonのリストに似ている）構造で追加されます。" -#: ../../tutorials/pyproject-toml.md:367 +#: ../../tutorials/pyproject-toml.md:376 msgid "" "A dependency can be limited to specific versions using a **version " "specifier.** If the dependency has no version specifier after the " @@ -6372,7 +6411,7 @@ msgstr "" "コードは時間の経過とともに変化し、バグが修正され、APIが変更されます。そのため、コードを書いた依存関係がどのバージョンと互換性があるのかを明確にしておくことは良いことです" " - あなたが今年書いたパッケージは、おそらくnumpy v0.0.1とは互換性がありません！" -#: ../../tutorials/pyproject-toml.md:371 +#: ../../tutorials/pyproject-toml.md:380 msgid "" "[Learn more about various ways to specify ranges of package versions " "here.](https://packaging.python.org/en/latest/specifications/version-" @@ -6381,7 +6420,7 @@ msgstr "" "[パッケージバージョンの範囲を指定する様々な方法については、こちらをご覧ください。](https://packaging.python.org/en/latest/specifications" "/version-specifiers/#id5)" -#: ../../tutorials/pyproject-toml.md:373 +#: ../../tutorials/pyproject-toml.md:382 msgid "" "The most common version specifier is a **lower bound,** allowing any " "version higher than the specified version. Ideally you should set this to" @@ -6393,11 +6432,11 @@ msgstr "" "で、指定されたバージョンより上位のバージョンを許可します。理想的には、あなたのパッケージとまだ互換性のある最も低いバージョンに設定すべきですが、実際には新しいパッケージの場合、パッケージが書かれた時点での最新バージョンに設定されることがよくあります" " [^lowerbound] 。" -#: ../../tutorials/pyproject-toml.md:378 +#: ../../tutorials/pyproject-toml.md:387 msgid "Lower bounds look like this:" msgstr "下限は次のようになります:" -#: ../../tutorials/pyproject-toml.md:384 +#: ../../tutorials/pyproject-toml.md:393 msgid "" "Commas are used to separate individual dependencies, and each package in " "your `dependencies` section can use different types of version " @@ -6406,25 +6445,25 @@ msgstr "" "カンマは、個々の依存関係を区切るために使用します、 そして、`dependencies` " "セクションの各パッケージは異なるタイプのバージョン指定子を使うことができます:" -#: ../../tutorials/pyproject-toml.md:395 +#: ../../tutorials/pyproject-toml.md:404 msgid "Your `pyproject.toml` file will now look like this:" msgstr "これで `pyproject.toml` ファイルは次のようになります:" -#: ../../tutorials/pyproject-toml.md:425 +#: ../../tutorials/pyproject-toml.md:434 msgid "Pin dependencies with caution" msgstr "依存関係のピン止めは慎重に" -#: ../../tutorials/pyproject-toml.md:426 +#: ../../tutorials/pyproject-toml.md:435 msgid "" "\"Pinning\" a dependency means setting it to a specific version, like " "this:" msgstr "依存関係を \"Pinning\" することは、次のように特定のバージョンに設定することを意味します:" -#: ../../tutorials/pyproject-toml.md:428 +#: ../../tutorials/pyproject-toml.md:437 msgid "`numpy == 1.0`." msgstr "`numpy == 1.0` 。" -#: ../../tutorials/pyproject-toml.md:430 +#: ../../tutorials/pyproject-toml.md:439 msgid "" "If you are building a library package that other developers will depend " "upon, you must be cautious before pinning to a precise dependency " @@ -6440,13 +6479,13 @@ msgstr "" "なぜなら、ユーザーはあなたのパッケージをさまざまな環境にインストールするからです。特定のバージョンに固定された依存関係は、Python環境の解決をより困難にします。" " そのため、依存関係を特定のバージョンに固定するのは、どうしても必要な場合に限られます。" -#: ../../tutorials/pyproject-toml.md:438 +#: ../../tutorials/pyproject-toml.md:447 msgid "" "Similarly, you should be cautious when specifying an upper bound on a " "package. These two specifications are equivalent:" msgstr "同様に、パッケージの上限を指定する場合にも注意が必要です。これら2つの仕様は同等です:" -#: ../../tutorials/pyproject-toml.md:446 +#: ../../tutorials/pyproject-toml.md:455 msgid "" "One build tool that you should be aware of that pins dependencies to an " "upper bound by default is Poetry. [Read more about how to safely add " @@ -6455,11 +6494,11 @@ msgstr "" "依存関係をデフォルトで上限値に固定するビルドツールとして知っておくべきもののひとつに、Poetryがあります。 " "[Poetryで依存関係を安全に追加する方法については、こちらをお読みください。](challenges-with-poetry)" -#: ../../tutorials/pyproject-toml.md:449 +#: ../../tutorials/pyproject-toml.md:458 msgid "Step 5: Add PyPI classifiers" msgstr "ステップ5: PyPI classifiersを追加する" -#: ../../tutorials/pyproject-toml.md:451 +#: ../../tutorials/pyproject-toml.md:460 msgid "" "Next you will add classifiers to your `pyproject.toml` file. The value " "for each classifier that you add to your `pyproject.toml` file must come " @@ -6471,11 +6510,11 @@ msgstr "" "[ここにあるPyPIで認められている分類子](https://PyPI.org/classifiers/) " "の一覧から選ぶ必要があります。スペルや書式に逸脱があると、PyPIに公開するときに問題が発生します。" -#: ../../tutorials/pyproject-toml.md:453 +#: ../../tutorials/pyproject-toml.md:462 msgid "What happens when you use incorrect classifiers?" msgstr "間違った分類子を使うとどうなりますか？" -#: ../../tutorials/pyproject-toml.md:456 +#: ../../tutorials/pyproject-toml.md:465 msgid "" "If you do not [use standard classifier " "values](https://PyPI.org/classifiers/), when you try to publish your " @@ -6486,33 +6525,33 @@ msgstr "" "PyPIでパッケージを公開しようとすると拒否されます。 最初のトライでPyPIに拒否されても心配しないでください！ " "それは私たち全員に起こったことです。" -#: ../../tutorials/pyproject-toml.md:459 +#: ../../tutorials/pyproject-toml.md:468 msgid "Review that list and add items below to your `pyproject.toml` file:" msgstr "そのリストを見て、以下の項目を `pyproject.toml` ファイルに追加します:" -#: ../../tutorials/pyproject-toml.md:461 +#: ../../tutorials/pyproject-toml.md:470 msgid "development status" msgstr "開発状況" -#: ../../tutorials/pyproject-toml.md:462 +#: ../../tutorials/pyproject-toml.md:471 msgid "intended audiences" msgstr "対象読者" -#: ../../tutorials/pyproject-toml.md:463 +#: ../../tutorials/pyproject-toml.md:472 msgid "topic" msgstr "トピック" -#: ../../tutorials/pyproject-toml.md:464 +#: ../../tutorials/pyproject-toml.md:473 msgid "programming language support" msgstr "プログラミング言語サポート" -#: ../../tutorials/pyproject-toml.md:466 +#: ../../tutorials/pyproject-toml.md:475 msgid "" "The classifier key should look something like the example below. A few " "notes:" msgstr "classifierのキーは、下の例のようになるはずです。 いくつか注意点があります:" -#: ../../tutorials/pyproject-toml.md:468 +#: ../../tutorials/pyproject-toml.md:477 #, fuzzy msgid "" "Your classifier values might be different depending upon your intended " @@ -6522,13 +6561,13 @@ msgstr "" "分類器の値は、パッケージに選択したライセンスによって異なる場合があります、 あなたの意図する読者、パッケージの開発状況とサポートしている " "Python のバージョンです。" -#: ../../tutorials/pyproject-toml.md:469 +#: ../../tutorials/pyproject-toml.md:478 msgid "" "You can add as many classifiers as you wish as long as you use the " "[designated PyPI classifier values](https://PyPI.org/classifiers/)." msgstr "[指定されたPyPIの分類子の値](https://PyPI.org/classifiers/) を使う限り、好きなだけ分類子を追加できます。" -#: ../../tutorials/pyproject-toml.md:508 +#: ../../tutorials/pyproject-toml.md:517 msgid "" "Note that while classifiers are not required in your `pyproject.toml` " "file, they will help users find your package. As such we strongly " @@ -6537,21 +6576,21 @@ msgstr "" "分類子は `pyproject.toml` " "ファイルでは必須ではありませんが、ユーザーがあなたのパッケージを見つけるのに役立つことに注意してください。そのため、追加することを強くお勧めします。" -#: ../../tutorials/pyproject-toml.md:510 +#: ../../tutorials/pyproject-toml.md:519 msgid "Step 6: Add the `[project.urls]` table" msgstr "ステップ 6: `[project.urls]` テーブルを追加する" -#: ../../tutorials/pyproject-toml.md:512 +#: ../../tutorials/pyproject-toml.md:521 msgid "Finally, add the project.urls table to your pyproject.toml file." msgstr "最後に、pyproject.tomlファイルにproject.urlsテーブルを追加します。" -#: ../../tutorials/pyproject-toml.md:514 +#: ../../tutorials/pyproject-toml.md:523 msgid "" "`project.urls` contains links that are relevant for your project. You " "might want to include:" msgstr "`project.urls` には、プロジェクトに関連するリンクが含まれています。以下を含めるとよいでしょう:" -#: ../../tutorials/pyproject-toml.md:516 +#: ../../tutorials/pyproject-toml.md:525 msgid "" "**Homepage:** A link to your published documentation for your project. If" " you are working through this tutorial, then you may not have this link " @@ -6560,18 +6599,18 @@ msgstr "" "**ホームページ:** プロジェクトの公開ドキュメントへのリンク。 " "このチュートリアルを進めているのであれば、このリンクはまだ持っていないかもしれません。 大丈夫、当分は飛ばしてもいいです。" -#: ../../tutorials/pyproject-toml.md:517 +#: ../../tutorials/pyproject-toml.md:526 #, fuzzy msgid "" "**Bug reports:** a link to your issues/discussions or wherever you want " "users to report bugs." msgstr "**バグ報告:** 課題 / ディスカッションへのリンク、またはユーザーがバグを報告できる場所です。" -#: ../../tutorials/pyproject-toml.md:518 +#: ../../tutorials/pyproject-toml.md:527 msgid "**Source:** the GitHub / GitLab link for your project." msgstr "**ソース:** プロジェクトのGitHub / GitLabリンク。" -#: ../../tutorials/pyproject-toml.md:563 +#: ../../tutorials/pyproject-toml.md:572 msgid "" "There are many other urls that you can add here. Check out the [README " "file here for an overview](https://github.com/patrick91/links-demo)." @@ -6580,11 +6619,11 @@ msgstr "" "[概要についてはこちらのREADMEファイル](https://github.com/patrick91/links-demo) " "をチェックしてください。" -#: ../../tutorials/pyproject-toml.md:566 +#: ../../tutorials/pyproject-toml.md:575 msgid "Putting it all together - your completed pyproject.toml file" msgstr "すべてをまとめます - 完成したpyproject.tomlファイル" -#: ../../tutorials/pyproject-toml.md:568 +#: ../../tutorials/pyproject-toml.md:577 msgid "" "Below is an example of a complete `pyproject.toml` file that is commented" " with all of the sections we discussed above." @@ -6594,48 +6633,48 @@ msgstr "以下は、上で説明したすべてのセクションがコメント msgid "Appendix - Click for a fully commented pyproject.toml file" msgstr "付録 - 完全にコメントされたpyproject.tomlファイルを見るにはクリックしてください" -#: ../../tutorials/pyproject-toml.md:617 +#: ../../tutorials/pyproject-toml.md:626 msgid "" "Below is a fully commented pyproject.toml file if you want to use it for " "reference." msgstr "参考にしたいのであれば、以下は、完全にコメントされたpyproject.tomlファイルです。" -#: ../../tutorials/pyproject-toml.md:683 +#: ../../tutorials/pyproject-toml.md:692 msgid "Example `pyproject.toml` files" msgstr "例 `pyproject.toml` ファイル" -#: ../../tutorials/pyproject-toml.md:685 +#: ../../tutorials/pyproject-toml.md:694 msgid "" "Below are some examples of `pyproject.toml` files from various packages " "in the scientific and pyOpenSci ecosystem." msgstr "以下は、scientificとpyOpenSciエコシステムの様々なパッケージの `pyproject.toml` ファイルの例です。" -#: ../../tutorials/pyproject-toml.md:686 +#: ../../tutorials/pyproject-toml.md:695 msgid "" "[PyPA's fully documented example pyproject.toml " "file](https://github.com/pypa/sampleproject/blob/main/pyproject.toml)" msgstr "[PyPAの完全に文書化されたサンプルpyproject.tomlファイル](https://github.com/pypa/sampleproject/blob/main/pyproject.toml)" -#: ../../tutorials/pyproject-toml.md:687 +#: ../../tutorials/pyproject-toml.md:696 msgid "" "[taxpasta has a nicely organized pyproject.toml file and is a pyOpenSci " "approved " "package](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a53dd49ad77e4cf143573/pyproject.toml)" msgstr "[taxpastaはきれいに整理されたpyproject.tomlファイルを持っており、pyOpenSci承認パッケージです](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a53dd49ad77e4cf143573/pyproject.toml)" -#: ../../tutorials/pyproject-toml.md:693 +#: ../../tutorials/pyproject-toml.md:702 msgid "At this point you've created:" msgstr "この時点であなたは以下を作成しました:" -#: ../../tutorials/pyproject-toml.md:695 +#: ../../tutorials/pyproject-toml.md:704 msgid "A [README.md](add-readme) file for your package" msgstr "パッケージの [README.md](add-readme) ファイル" -#: ../../tutorials/pyproject-toml.md:696 +#: ../../tutorials/pyproject-toml.md:705 msgid "A [CODE_OF_CONDUCT.md](add-coc) file to support your user community" msgstr "ユーザーコミュニティをサポートする [CODE_OF_CONDUCT.md](add-coc) ファイル" -#: ../../tutorials/pyproject-toml.md:697 +#: ../../tutorials/pyproject-toml.md:706 msgid "" "And a [LICENSE](add-license-coc) file which provides legal boundaries " "around how people can and can't use your software" @@ -6643,17 +6682,17 @@ msgstr "" "[LICENSE](add-license-coc) " "ファイルは、人々があなたのソフトウェアをどのように使用できるか、また使用できないかに関する法的な境界線を提供します。" -#: ../../tutorials/pyproject-toml.md:699 +#: ../../tutorials/pyproject-toml.md:708 msgid "" "You also learned [how to publish your package to (test)PyPI](publish-" "pypi)." msgstr "また、 [パッケージを(test)PyPIに公開する方法](publish-pypi) も学びました。" -#: ../../tutorials/pyproject-toml.md:701 +#: ../../tutorials/pyproject-toml.md:710 msgid "Publish a new version of your package to PyPI" msgstr "新しいバージョンのパッケージをPyPIに公開する" -#: ../../tutorials/pyproject-toml.md:703 +#: ../../tutorials/pyproject-toml.md:712 msgid "" "You are now ready to publish a new version of your Python package to " "(test) PyPI. When you do this you will see that the landing page for your" @@ -6662,11 +6701,11 @@ msgstr "" "これで、Pythonパッケージの新しいバージョンを(test)PyPIに公開する準備ができました。 " "そうすると、パッケージのランディングページに、より多くの情報が掲載されていることがわかります。" -#: ../../tutorials/pyproject-toml.md:705 +#: ../../tutorials/pyproject-toml.md:714 msgid "Try to republish now." msgstr "今すぐ再公開を試みます。" -#: ../../tutorials/pyproject-toml.md:707 +#: ../../tutorials/pyproject-toml.md:716 msgid "" "First, update the version of your package in your pyproject toml file. " "Below version is updated from `0.1` to `0.1.1`." @@ -6674,28 +6713,28 @@ msgstr "" "まず、pyprojectのtomlファイルでパッケージのバージョンを更新します。以下のバージョンが `0.1` から `0.1.1` " "に更新されました。" -#: ../../tutorials/pyproject-toml.md:720 +#: ../../tutorials/pyproject-toml.md:729 msgid "Now use hatch to publish the new version of your package to test.PyPI.org." msgstr "次に hatch を使って、新しいバージョンのパッケージを test.PyPI.org に公開します。" -#: ../../tutorials/pyproject-toml.md:727 +#: ../../tutorials/pyproject-toml.md:736 msgid "Next (optional) step - publishing to conda-forge" msgstr "次のステップ(オプション) - conda-forgeに公開します。" -#: ../../tutorials/pyproject-toml.md:729 +#: ../../tutorials/pyproject-toml.md:738 msgid "" "You now have all of the skills that you need to publish your package to " "PyPI." msgstr "これであなたのパッケージをPyPIに公開するために必要なスキルはすべて揃いました。" -#: ../../tutorials/pyproject-toml.md:732 +#: ../../tutorials/pyproject-toml.md:741 msgid "" "If you also want to publish your package on conda-forge (which is a " "channel within the conda ecosystem), you will learn how to do that in the" " next lesson." msgstr "あなたのパッケージを(condaエコシステム内のチャンネルである)conda-forgeで公開したい場合 、 その方法は次のレッスンで学びます。" -#: ../../tutorials/pyproject-toml.md:736 +#: ../../tutorials/pyproject-toml.md:745 msgid "" "Really good resources from jeremiah " "https://daniel.feldroy.com/posts/2023-08-pypi-project-urls-cheatsheet " @@ -6704,7 +6743,7 @@ msgstr "" "jeremiah からの本当に良い情報源 https://daniel.feldroy.com/posts/2023-08-pypi-" "project-urls-cheatsheet が役に立ちます (リンク先のデモはなおさら)。" -#: ../../tutorials/pyproject-toml.md:376 +#: ../../tutorials/pyproject-toml.md:385 msgid "" "Some packaging tools will do this for you when you add a dependency using" " their cli interface. For example [`poetry add`](https://python-" @@ -6718,6 +6757,226 @@ msgstr "" "指定子で最新バージョンを追加し、 [`pdm add`](https://pdm-" "project.org/latest/reference/cli/#add) は `>=` 指定子で最新バージョンを追加します。" +#: ../../tutorials/run-python-scripts-hatch.md:10 +msgid "" +"Python supports inline metadata for scripts (a feature added in 2024). " +"This makes it possible to run standalone scripts with dependencies and " +"Python versions managed automatically." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:14 +#, python-brace-format +msgid "" +"Many tools support this workflow, including PDM, [Hatch](get-to-know-" +"hatch), and {term}`uv`. In this tutorial, we focus on Hatch and UV. The " +"same metadata format can also be used with other tools." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:22 +msgid "" +"[Hatch: How to run Python scripts](https://hatch.pypa.io/latest/how-" +"to/run/python-scripts/)" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:23 +msgid "" +"[uv: Running " +"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-" +"script)" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:26 +msgid "How to create a reproducible script" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:28 +#, python-brace-format +msgid "" +"Sometimes you want to share or run a single script without creating a " +"full {term}`Python package`. To do this, you can use inline script " +"metadata. This format lets you specify dependencies and Python versions " +"at the top of your script in a comment block." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:34 +msgid "" +"When you add metadata at the top of a script, Hatch (or PDM or uv) will " +"use that metadata to:" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:37 +#, fuzzy +msgid "Create an isolated virtual Python environment for that script." +msgstr "使用したいPython環境をアクティブにします。" + +#: ../../tutorials/run-python-scripts-hatch.md:38 +#, python-brace-format +msgid "" +"Install the {term}`Dependencies` listed in the script into that " +"environment." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:39 +msgid "Use the required Python version that you specify in the metadata." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:41 +msgid "" +"This approach is useful for workflows that you want to make reproducible," +" but that do not need to become full Python packages." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:44 +#, fuzzy +msgid "Why use Hatch for scripts?" +msgstr "Hatchスクリプト" + +#: ../../tutorials/run-python-scripts-hatch.md:46 +msgid "" +"Inline metadata helps you make scripts reproducible. Anyone can run your " +"script without manually creating a new environment or guessing which " +"dependencies it needs. Hatch takes care of installing dependencies and " +"using the correct Python version." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:51 +msgid "How to add inline metadata to your script" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:53 +msgid "" +"You will use Hatch in this example, but you can also use uv if that is " +"your preferred tool." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:56 +#, python-brace-format +msgid "" +"First, create a new file named `script.py` with the block below at the " +"top. The metadata block starts with `# /// script` and ends with `# ///`." +" Everything in between must be {term}`TOML` metadata written as comments." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:60 +msgid "" +"In the example below, the script requires Python 3.11 or newer, and NumPy" +" is declared as a dependency." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:81 +msgid "Run the script with Hatch" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:83 +msgid "" +"Open your terminal and change to the directory where `script.py` lives. " +"Then run:" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:90 +msgid "" +"On first run, Hatch will create an environment and install dependencies. " +"On later runs, Hatch will reuse that environment so startup is faster." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:94 +msgid "" +"The environment name is based on the script path. If you move the script " +"to a new location, Hatch will treat it as a new script environment." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:98 +msgid "Optional: configure script environment behavior" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:100 +msgid "" +"You can control script-specific Hatch behavior in the same metadata " +"block. For example, to use `pip` instead of `uv` as the installer:" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:113 +msgid "Run the same script with uv" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:115 +msgid "If you prefer uv, you can run the same inline-metadata script with:" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:121 +msgid "" +"The same `# /// script` metadata block works with uv, including " +"`requires-python` and `dependencies`." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:124 +msgid "" +"For more on using uv to run scripts, see the guide: [Running scripts with" +" uv](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:128 +msgid "When to use scripts vs. packages" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:130 +msgid "You may be wondering when to use scripts versus creating a package." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:132 +msgid "This depends on your use case. Scripts are often useful when:" +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:134 +msgid "You have one small task, or a specific workflow that is not generalizable." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:135 +msgid "" +"Your workflow is still evolving, but you want to run it in a reproducible" +" environment." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:137 +msgid "You want reproducible dependencies quickly." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:138 +msgid "You are sharing a single file with collaborators." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:140 +#, fuzzy +msgid "Create a full package when:" +msgstr "なぜPythonパッケージを作るのか？" + +#: ../../tutorials/run-python-scripts-hatch.md:142 +msgid "You are building reusable modules for multiple projects." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:143 +msgid "You need tests, documentation, releases, and long-term maintenance." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:144 +msgid "Your codebase is growing beyond one or two scripts." +msgstr "" + +#: ../../tutorials/run-python-scripts-hatch.md:148 +#, fuzzy +msgid "[Get to know Hatch](get-to-know-hatch.md)" +msgstr "詳しくは [Hatch](get-to-know-hatch.md) を知るをご覧ください。" + +#: ../../tutorials/run-python-scripts-hatch.md:149 +#, fuzzy +msgid "[Create a Python package](create-python-package.md)" +msgstr "[コードをインストール可能にする](create-python-package)" + +#: ../../tutorials/run-python-scripts-hatch.md:150 +#, fuzzy +msgid "[Command line reference guide](command-line-reference.md)" +msgstr "コマンドラインリファレンスガイド" + #: ../../tutorials/setup-py-to-pyproject-toml.md:7 msgid "Using Hatch to Migrate setup.py to a pyproject.toml" msgstr "Hatchを使ってsetup.pyをpyproject.tomlに移行する" @@ -6725,22 +6984,23 @@ msgstr "Hatchを使ってsetup.pyをpyproject.tomlに移行する" #: ../../tutorials/setup-py-to-pyproject-toml.md:9 #, fuzzy msgid "" -"Hatch can be useful for generating your project's `pyproject.toml` file " -"if your project already has a `setup.py` file." +"[Hatch](get-to-know-hatch) can be useful for generating your project's " +"[pyproject.toml](pyproject-toml) file if your project already has a " +"`setup.py` file." msgstr "プロジェクトに既に `setup.py` がある場合、Hatchはプロジェクトの `pyproject.toml` を生成するのに便利です。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:11 +#: ../../tutorials/setup-py-to-pyproject-toml.md:13 msgid "Note" msgstr "注釈" -#: ../../tutorials/setup-py-to-pyproject-toml.md:14 +#: ../../tutorials/setup-py-to-pyproject-toml.md:16 #, fuzzy msgid "" "This step is not necessary and is only helpful if your project already " "has a `setup.py` file defined." msgstr "このステップは必要なく、プロジェクトに既に `setup.py` ファイルが定義されている場合にのみ有用です。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:15 +#: ../../tutorials/setup-py-to-pyproject-toml.md:17 #, fuzzy msgid "" "If your project does not already define a `setup.py` see [Make your " @@ -6749,7 +7009,7 @@ msgstr "" "プロジェクトで `setup.py` が定義されていない場合は、 [Python コードをインストール可能にする](installable-" "code.md) を参照してください。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:23 +#: ../../tutorials/setup-py-to-pyproject-toml.md:25 msgid "" "The process of using Hatch to transition to using `pyproject.toml` for " "projects that already have a `setup.py` defined." @@ -6757,56 +7017,57 @@ msgstr "" "すでに `setup.py` が定義されているプロジェクトで `pyproject.toml` を使用するように移行するために Hatch " "を使用するプロセスです。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:26 +#: ../../tutorials/setup-py-to-pyproject-toml.md:28 msgid "What is Hatch?" msgstr "Hatchとは何か？" -#: ../../tutorials/setup-py-to-pyproject-toml.md:28 +#: ../../tutorials/setup-py-to-pyproject-toml.md:30 +#, fuzzy, python-brace-format msgid "" "Hatch is a Python package manager designed to streamline the process of " "creating, managing, and distributing Python packages. It provides a " "convenient CLI (Command-Line Interface) for tasks such as creating new " -"projects, managing dependencies, building distributions, and publishing " -"packages to repositories like PyPI." +"projects, managing {term}`Dependencies`, building distributions, and " +"publishing packages to repositories like [PyPI](publish-pypi)." msgstr "" "HatchはPythonパッケージマネージャで、Pythonパッケージの作成、管理、配布のプロセスを効率化するように設計されています。 " "新しいプロジェクトの作成、依存関係の管理、ディストリビューションのビルド、PyPI " "のようなリポジトリへのパッケージの公開といったタスクのための便利な CLI (Command-Line Interface) を提供します。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:34 +#: ../../tutorials/setup-py-to-pyproject-toml.md:40 #, fuzzy msgid "See [Get to know Hatch](get-to-know-hatch) for more information." msgstr "詳しくは [Hatch](get-to-know-hatch.md) を知るをご覧ください。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:37 +#: ../../tutorials/setup-py-to-pyproject-toml.md:43 msgid "Prerequisites" msgstr "前提条件" -#: ../../tutorials/setup-py-to-pyproject-toml.md:39 +#: ../../tutorials/setup-py-to-pyproject-toml.md:45 msgid "" "Before we begin, ensure that you have Hatch installed on your system. You" " can install it via pip:" msgstr "始める前に、システムにHatchがインストールされていることを確認してください。pipでインストールできます:" -#: ../../tutorials/setup-py-to-pyproject-toml.md:45 +#: ../../tutorials/setup-py-to-pyproject-toml.md:51 msgid "Sample Directory Tree" msgstr "サンプルディレクトリツリー" -#: ../../tutorials/setup-py-to-pyproject-toml.md:47 +#: ../../tutorials/setup-py-to-pyproject-toml.md:53 msgid "" "Let's take a look at a sample directory tree structure before and after " "using `hatch init`:" msgstr "それでは、 `hatch init` を使う前と後のディレクトリツリー構造のサンプルを見てみましょう: " -#: ../../tutorials/setup-py-to-pyproject-toml.md:49 +#: ../../tutorials/setup-py-to-pyproject-toml.md:55 msgid "Before `hatch init`" msgstr "`hatch init` 前" -#: ../../tutorials/setup-py-to-pyproject-toml.md:65 +#: ../../tutorials/setup-py-to-pyproject-toml.md:71 msgid "After `hatch init`" msgstr "`hatch init` 後" -#: ../../tutorials/setup-py-to-pyproject-toml.md:83 +#: ../../tutorials/setup-py-to-pyproject-toml.md:89 msgid "" "As you can see, the main change after running `hatch init` is the " "addition of the `pyproject.toml` file in the project directory." @@ -6814,30 +7075,30 @@ msgstr "" "ご覧のように、 `hatch init` を実行した後の主な変化は、プロジェクトディレクトリに `pyproject.toml` " "ファイルが追加されたことです。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:85 +#: ../../tutorials/setup-py-to-pyproject-toml.md:91 msgid "Step-by-Step Guide" msgstr "ステップバイステップガイド" -#: ../../tutorials/setup-py-to-pyproject-toml.md:87 +#: ../../tutorials/setup-py-to-pyproject-toml.md:93 msgid "" "Now, let's walk through the steps to use Hatch to create a " "`pyproject.toml` file for your project." msgstr "では、Hatchを使ってプロジェクトの `pyproject.toml` ファイルを作成する手順を説明しましょう。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:89 +#: ../../tutorials/setup-py-to-pyproject-toml.md:95 msgid "" "**Navigate to Your Project Directory**: Open your terminal or command " "prompt and navigate to the directory where your Python project is " "located." msgstr "**プロジェクトディレクトリに移動する**: ターミナルかコマンドプロンプトを開き、Pythonプロジェクトがあるディレクトリに移動します。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:91 +#: ../../tutorials/setup-py-to-pyproject-toml.md:97 msgid "" "**Initialize Hatch**: Run the following command to initialize Hatch in " "your project directory:" msgstr "**Hatchの初期化**: 以下のコマンドを実行し、プロジェクトディレクトリのHatchを初期化します:" -#: ../../tutorials/setup-py-to-pyproject-toml.md:97 +#: ../../tutorials/setup-py-to-pyproject-toml.md:103 #, fuzzy msgid "" "**Review and Customize**: After running the previous command, Hatch will " @@ -6854,7 +7115,7 @@ msgstr "" "`pyproject.toml` の詳細については [pyproject.toml](pyproject-toml.md) " "チュートリアルを参照してください)。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:99 +#: ../../tutorials/setup-py-to-pyproject-toml.md:105 #, fuzzy msgid "" "**Verify**: Verify that the `pyproject.toml` file accurately reflects " @@ -6864,7 +7125,7 @@ msgstr "" "**検証**: `pyproject.toml` ファイルがプロジェクト構成と依存関係を正確に反映していることを確認します。 " "必要であればファイルを手動で編集することもできますが、慎重を期して構文が正しいことを確認してください。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:101 +#: ../../tutorials/setup-py-to-pyproject-toml.md:107 msgid "" "**Delete setup.py**: Since we're migrating to using `pyproject.toml` " "exclusively, the `setup.py` file becomes unnecessary. You can safely " @@ -6873,7 +7134,7 @@ msgstr "" "**setup.py を削除する**: `pyproject.toml` のみを使用するように移行するので、 `setup.py` " "ファイルは不要になります。 プロジェクトディレクトリから安全に削除できます。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:103 +#: ../../tutorials/setup-py-to-pyproject-toml.md:109 msgid "" "**Test Build**: Before proceeding further, it's essential to ensure that " "your project builds successfully using only the `pyproject.toml` file. " @@ -6882,7 +7143,7 @@ msgstr "" "**テストビルド**: 先に進む前に、 `pyproject.toml` " "ファイルだけを使ってプロジェクトが正常にビルドされることを確認する必要がある。 以下のコマンドを実行してプロジェクトをビルドします:" -#: ../../tutorials/setup-py-to-pyproject-toml.md:109 +#: ../../tutorials/setup-py-to-pyproject-toml.md:115 msgid "" "This command will build your project based on the specifications in the " "`pyproject.toml` file. Make sure to check for any errors or warnings " @@ -6891,7 +7152,7 @@ msgstr "" "このコマンドは `pyproject.toml` ファイルの仕様に基づいてプロジェクトをビルドします。 " "ビルドの過程でエラーや警告がないか、必ず確認してください。" -#: ../../tutorials/setup-py-to-pyproject-toml.md:111 +#: ../../tutorials/setup-py-to-pyproject-toml.md:117 msgid "" "**Test Existing Functionality**: After successfully building your project" " with `pyproject.toml`, it's crucial to ensure that your project's " @@ -6934,7 +7195,8 @@ msgid "Automate building and publishing the package on GitHub Actions" msgstr "" #: ../../tutorials/trusted-publishing.md:19 -msgid "Configure PyPI Trusted Publishing for the project" +#, python-brace-format +msgid "Configure {term}`Trusted publishing` for the project" msgstr "" #: ../../tutorials/trusted-publishing.md:20 @@ -6961,14 +7223,14 @@ msgid "" "publishing of documentation, automate creation of web pages for the " "project, and even automate the release process. For this lesson, we will " "focus on using actions to release and publish your Python package " -"securely to PyPI." +"securely to [PyPI](publish-pypi)." msgstr "" -#: ../../tutorials/trusted-publishing.md:35 +#: ../../tutorials/trusted-publishing.md:36 msgid "Why Trusted Publishing Matters" msgstr "" -#: ../../tutorials/trusted-publishing.md:37 +#: ../../tutorials/trusted-publishing.md:38 msgid "" "If you are wondering why trusted publishing is so important, [check out " "this blog post:](https://www.pyopensci.org/blog/python-packaging-" @@ -6976,12 +7238,12 @@ msgid "" "you don't lock down your publishing workflows." msgstr "" -#: ../../tutorials/trusted-publishing.md:40 +#: ../../tutorials/trusted-publishing.md:41 #, fuzzy msgid "Step 0: Create a release workflow" msgstr "ステップ0: READMEファイルの作成" -#: ../../tutorials/trusted-publishing.md:42 +#: ../../tutorials/trusted-publishing.md:43 msgid "" "To get started, create a file named `release.yaml` under the " "`.github/workflows` directory of your project. If the `.github/workflows`" @@ -6990,11 +7252,11 @@ msgid "" "`.github/workflows` directory." msgstr "" -#: ../../tutorials/trusted-publishing.md:47 +#: ../../tutorials/trusted-publishing.md:48 msgid "Naming your workflow file" msgstr "" -#: ../../tutorials/trusted-publishing.md:50 +#: ../../tutorials/trusted-publishing.md:51 msgid "" "You can name the workflow file whatever you wish. We suggest using " "something simple and expressive like `release.yaml` so you, your future " @@ -7002,23 +7264,23 @@ msgid "" "workflow does." msgstr "" -#: ../../tutorials/trusted-publishing.md:55 +#: ../../tutorials/trusted-publishing.md:56 msgid "Step 1: Name the workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:57 +#: ../../tutorials/trusted-publishing.md:58 #, fuzzy msgid "At the top of the `release.yaml` file, type the following:" msgstr "`README.md` ファイルの先頭に、パッケージ名を追加します。" -#: ../../tutorials/trusted-publishing.md:63 +#: ../../tutorials/trusted-publishing.md:64 msgid "" "This provides a name to the workflow that you can use to quickly find all" " runs of this GitHub Action on the \"Actions\" tab in the GitHub " "repository." msgstr "" -#: ../../tutorials/trusted-publishing.md:67 +#: ../../tutorials/trusted-publishing.md:68 msgid "" "Graphic showing an example of a configured workflow for the release. On " "the top, in the red box labeled \"1\" you see the \"Actions\" tab of the " @@ -7029,7 +7291,7 @@ msgid "" "package." msgstr "" -#: ../../tutorials/trusted-publishing.md:69 +#: ../../tutorials/trusted-publishing.md:70 msgid "" "This image shows an example of a configured workflow for the release. On " "the top, in the red box labeled \"1\" you see the \"Actions\" tab of the " @@ -7039,11 +7301,11 @@ msgid "" "workflow, for the \"1.0\" and \"1.0.1\" releases of the package." msgstr "" -#: ../../tutorials/trusted-publishing.md:72 +#: ../../tutorials/trusted-publishing.md:73 msgid "Step 2: Add triggers to the workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:74 +#: ../../tutorials/trusted-publishing.md:75 msgid "" "Every GitHub Actions workflow runs when [certain " "conditions](https://docs.github.com/en/actions/reference/events-that-" @@ -7055,11 +7317,11 @@ msgid "" "and publish a release:" msgstr "" -#: ../../tutorials/trusted-publishing.md:86 +#: ../../tutorials/trusted-publishing.md:87 msgid "Step 3: Configure the jobs in the workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:88 +#: ../../tutorials/trusted-publishing.md:89 msgid "" "A GitHub Actions *workflow* file can contain multiple *jobs* that run " "independently; each job can also have multiple *steps.* When triggered, " @@ -7067,7 +7329,7 @@ msgid "" "that have conditional requirements)." msgstr "" -#: ../../tutorials/trusted-publishing.md:92 +#: ../../tutorials/trusted-publishing.md:93 msgid "" "Jobs and steps can also have [conditional " "logic](https://docs.github.com/en/actions/reference/workflow-syntax-for-" @@ -7077,24 +7339,24 @@ msgid "" " to test building the package every time you merge a new pull request." msgstr "" -#: ../../tutorials/trusted-publishing.md:95 +#: ../../tutorials/trusted-publishing.md:96 msgid "" "For a release job, you need to clone or check out the repository. You can" " use the `actions/checkout` action to check out the code. You then " -"install and use `hatch` to build your package." +"install and use [Hatch](get-to-know-hatch) to build your package." msgstr "" -#: ../../tutorials/trusted-publishing.md:98 +#: ../../tutorials/trusted-publishing.md:101 msgid "" "You also need to make sure to set up Hatch on the machine GitHub is using" " to run the workflow." msgstr "" -#: ../../tutorials/trusted-publishing.md:101 +#: ../../tutorials/trusted-publishing.md:104 msgid "A minimal job definition would look like this:" msgstr "" -#: ../../tutorials/trusted-publishing.md:121 +#: ../../tutorials/trusted-publishing.md:124 msgid "" "Notice that above, you provide a version for each action step. " "`action/checkout@v5` tells GitHub to use version 5 of the checkout " @@ -7102,30 +7364,30 @@ msgid "" "this case, the code will be used to build your package." msgstr "" -#: ../../tutorials/trusted-publishing.md:123 +#: ../../tutorials/trusted-publishing.md:126 msgid "" "Next, you will learn about a better way to secure (or \"harden\") your " "workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:125 +#: ../../tutorials/trusted-publishing.md:128 msgid "Step 4: Secure the GitHub Actions workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:127 +#: ../../tutorials/trusted-publishing.md:130 msgid "" "There are several improvements you can make to the GitHub Actions " "workflow you just configured to improve security and readability." msgstr "" -#: ../../tutorials/trusted-publishing.md:130 +#: ../../tutorials/trusted-publishing.md:133 msgid "" "First, we can give names to relevant steps in the process to increase the" " readability of the logs generated during the workflow run. This can be " "achieved using `name: ` lines." msgstr "" -#: ../../tutorials/trusted-publishing.md:134 +#: ../../tutorials/trusted-publishing.md:137 msgid "" "More importantly, each time you use an existing action (via `uses`) you " "should pin that action to a commit hash. Pinning your action ensures that" @@ -7135,24 +7397,24 @@ msgid "" "supply-chain-attack])." msgstr "" -#: ../../tutorials/trusted-publishing.md:141 +#: ../../tutorials/trusted-publishing.md:144 msgid "" "Enabling Dependabot[^dependabot] in the repository will ensure that your " "actions stay up to date. The dependabot tool will open pull requests that" " update your action versions at whatever frequency you want." msgstr "" -#: ../../tutorials/trusted-publishing.md:146 +#: ../../tutorials/trusted-publishing.md:149 msgid "Thus, the workflow that you should use should be similar to:" msgstr "" -#: ../../tutorials/trusted-publishing.md:154 +#: ../../tutorials/trusted-publishing.md:157 msgid "" "Now, you can commit the `.github/workflows/release.yaml` file to the " "repository and push to GitHub." msgstr "" -#: ../../tutorials/trusted-publishing.md:156 +#: ../../tutorials/trusted-publishing.md:159 msgid "" "At this point, if you create a new release for your project on GitHub, " "the configured workflow should run and build a wheel for you. " @@ -7160,29 +7422,29 @@ msgid "" "deleted at the end of the workflow run." msgstr "" -#: ../../tutorials/trusted-publishing.md:160 +#: ../../tutorials/trusted-publishing.md:163 msgid "Step 5: Upload the built artifact to GitHub Artifacts" msgstr "" -#: ../../tutorials/trusted-publishing.md:162 +#: ../../tutorials/trusted-publishing.md:165 msgid "" "You need to add one more step to the job definition to be able to access " "the wheel. You will upload it to the artifacts temporary area[^github-" "artifacts]. Add the following to the `release.yaml` file:" msgstr "" -#: ../../tutorials/trusted-publishing.md:172 +#: ../../tutorials/trusted-publishing.md:175 msgid "Upload artifacts parameters" msgstr "" -#: ../../tutorials/trusted-publishing.md:175 +#: ../../tutorials/trusted-publishing.md:178 msgid "" "Above, you have configured the artifact to be deleted after 1 day. The " "artifacts storage on GitHub actions is temporary; users should not " "download your package from the GitHub artifacts." msgstr "" -#: ../../tutorials/trusted-publishing.md:178 +#: ../../tutorials/trusted-publishing.md:181 msgid "" "You have also configured the release job to error if the `dist/` " "directory does not exist. This means that `hatch build` (from the " @@ -7190,68 +7452,68 @@ msgid "" "release." msgstr "" -#: ../../tutorials/trusted-publishing.md:183 +#: ../../tutorials/trusted-publishing.md:186 msgid "" "At this point, if you push the `release.yaml` to GitHub and create a new " "release, the GitHub Actions job will:" msgstr "" -#: ../../tutorials/trusted-publishing.md:186 +#: ../../tutorials/trusted-publishing.md:189 msgid "run," msgstr "" -#: ../../tutorials/trusted-publishing.md:187 +#: ../../tutorials/trusted-publishing.md:190 msgid "clone your repository," msgstr "" -#: ../../tutorials/trusted-publishing.md:188 +#: ../../tutorials/trusted-publishing.md:191 #, fuzzy msgid "install and set up Hatch," msgstr "Hatchのインストール" -#: ../../tutorials/trusted-publishing.md:189 +#: ../../tutorials/trusted-publishing.md:192 #, fuzzy msgid "build your package and" msgstr "パッケージをビルドするには `hatch build` を実行します:" -#: ../../tutorials/trusted-publishing.md:190 +#: ../../tutorials/trusted-publishing.md:193 msgid "upload your package as an archive to the artifacts storage." msgstr "" -#: ../../tutorials/trusted-publishing.md:193 +#: ../../tutorials/trusted-publishing.md:196 msgid "" "Graphic showing an example of a release workflow that has just finished " "running. Each step in the log is matched to one step in the workflow " "definition." msgstr "" -#: ../../tutorials/trusted-publishing.md:195 +#: ../../tutorials/trusted-publishing.md:198 msgid "" "This figure shows an example of a release workflow that has just finished" " running. Each step in the log is matched to one step in the workflow " "definition." msgstr "" -#: ../../tutorials/trusted-publishing.md:198 +#: ../../tutorials/trusted-publishing.md:201 msgid "" "At the bottom of the workflow run page on GitHub, you should see a " "section for the artifacts produced during runtime and uploaded to this " "storage area:" msgstr "" -#: ../../tutorials/trusted-publishing.md:202 +#: ../../tutorials/trusted-publishing.md:205 msgid "" "Graphic showing an example of an artifact produced by the release " "workflow." msgstr "" -#: ../../tutorials/trusted-publishing.md:204 +#: ../../tutorials/trusted-publishing.md:207 msgid "" "This figure shows the artifact produced by the above release workflow. It" " is now marked as expired since the workflow ran more than a day ago." msgstr "" -#: ../../tutorials/trusted-publishing.md:207 +#: ../../tutorials/trusted-publishing.md:210 msgid "" "You can download the artifact (before it expires), unzip it, and install " "the wheel contained within. However, this should only be done if you want" @@ -7259,11 +7521,11 @@ msgid "" "using trusted publishing." msgstr "" -#: ../../tutorials/trusted-publishing.md:212 +#: ../../tutorials/trusted-publishing.md:215 msgid "Configure automatic publishing to PyPI" msgstr "" -#: ../../tutorials/trusted-publishing.md:214 +#: ../../tutorials/trusted-publishing.md:217 msgid "" "The job you configured above using GitHub Actions builds your package " "using your code. You still need to upload it to PyPI. You could upload " @@ -7272,56 +7534,56 @@ msgid "" "we uploaded the artifact to the temporary storage." msgstr "" -#: ../../tutorials/trusted-publishing.md:220 +#: ../../tutorials/trusted-publishing.md:223 msgid "" "In the new job, you will download the package from there and upload it to" " PyPI. Since the `build` job does nothing else, there is no possibility " "that the package could get compromised before the release." msgstr "" -#: ../../tutorials/trusted-publishing.md:224 +#: ../../tutorials/trusted-publishing.md:227 msgid "Step 1: Add the upload job" msgstr "" -#: ../../tutorials/trusted-publishing.md:226 +#: ../../tutorials/trusted-publishing.md:229 msgid "" "In the `release.yaml` file, add the following new job, after the job " "defined in the previous section:" msgstr "" -#: ../../tutorials/trusted-publishing.md:235 +#: ../../tutorials/trusted-publishing.md:238 msgid "Make sure to change the URL" msgstr "" -#: ../../tutorials/trusted-publishing.md:237 +#: ../../tutorials/trusted-publishing.md:240 msgid "Remember to change the `url:` value to the URL for your package on PyPI!" msgstr "" -#: ../../tutorials/trusted-publishing.md:240 +#: ../../tutorials/trusted-publishing.md:243 msgid "This job has two steps:" msgstr "" -#: ../../tutorials/trusted-publishing.md:242 +#: ../../tutorials/trusted-publishing.md:245 msgid "" "It uses `download-artifact` to download the artifacts built in the " "previous job" msgstr "" -#: ../../tutorials/trusted-publishing.md:244 +#: ../../tutorials/trusted-publishing.md:247 msgid "It uses `gh-action-pypi-publish` to publish the package to PyPI." msgstr "" -#: ../../tutorials/trusted-publishing.md:246 +#: ../../tutorials/trusted-publishing.md:249 msgid "" "You are almost there!! Now, you just need to enable trusted publishing " "for your project on PyPI. And then, your work is done!" msgstr "" -#: ../../tutorials/trusted-publishing.md:249 +#: ../../tutorials/trusted-publishing.md:252 msgid "Step 2: Enable trusted publishing on PyPI" msgstr "" -#: ../../tutorials/trusted-publishing.md:253 +#: ../../tutorials/trusted-publishing.md:256 msgid "" "Diagram showing PyPI's trusted publisher workflow: Step 1 builds " "distribution files via GitHub, Step 2 uses a trusted environment (PyPI), " @@ -7329,7 +7591,7 @@ msgid "" "connecting GitHub Action to Python Package Index." msgstr "" -#: ../../tutorials/trusted-publishing.md:258 +#: ../../tutorials/trusted-publishing.md:261 msgid "" "Before trusted publishing was created, in order to upload to PyPI from " "GitHub actions you would have needed to add the username and password as " @@ -7342,7 +7604,7 @@ msgid "" "credentials." msgstr "" -#: ../../tutorials/trusted-publishing.md:266 +#: ../../tutorials/trusted-publishing.md:269 msgid "" "To prevent these incidents and improve supply chain security, developers " "created [Trusted Publishing](https://docs.pypi.org/trusted-publishers/). " @@ -7351,17 +7613,17 @@ msgid "" "Actions) that is allowed to publish the package." msgstr "" -#: ../../tutorials/trusted-publishing.md:271 +#: ../../tutorials/trusted-publishing.md:274 msgid "" "You do not need to enter a token or password value in a trusted publisher" " workflow. It's a secure connection between your" msgstr "" -#: ../../tutorials/trusted-publishing.md:274 +#: ../../tutorials/trusted-publishing.md:277 msgid "Trusted Publishing outside of GitHub Actions" msgstr "" -#: ../../tutorials/trusted-publishing.md:277 +#: ../../tutorials/trusted-publishing.md:280 msgid "" "Trusted Publishing supports other automation platforms, beyond GitHub " "Actions. It is also possible to configure a trusted publisher for " @@ -7369,7 +7631,7 @@ msgid "" " advanced uses, out of scope for this lesson." msgstr "" -#: ../../tutorials/trusted-publishing.md:283 +#: ../../tutorials/trusted-publishing.md:286 msgid "" "For this lesson, we will focus on configuring a trusted publisher for a " "project that already exists on PyPI. If you completed the [lesson about " @@ -7377,90 +7639,90 @@ msgid "" "already created." msgstr "" -#: ../../tutorials/trusted-publishing.md:285 +#: ../../tutorials/trusted-publishing.md:288 msgid "" "This setup step needs to be performed only once for the project. Future " "releases will only run the GitHub Actions workflow we are configuring in " "`release.yaml`." msgstr "" -#: ../../tutorials/trusted-publishing.md:288 +#: ../../tutorials/trusted-publishing.md:291 msgid "" "On the [\"Your projects\" page on " "PyPI](https://pypi.org/manage/projects/), click \"Manage\" on any project" " you want to configure." msgstr "" -#: ../../tutorials/trusted-publishing.md:292 +#: ../../tutorials/trusted-publishing.md:295 msgid "" "Graphic showing a screenshot of the \"Your projects\" page on PyPI. The " "\"Manage\" button for one of the projects is highlighted." msgstr "" -#: ../../tutorials/trusted-publishing.md:294 +#: ../../tutorials/trusted-publishing.md:297 msgid "" "This image shows several projects. The \"Manage\" button is highlighted " "for one of the projects, the one we want to configure trusted publishing " "for." msgstr "" -#: ../../tutorials/trusted-publishing.md:297 +#: ../../tutorials/trusted-publishing.md:300 msgid "Then click \"Publishing\" in the project's sidebar." msgstr "" -#: ../../tutorials/trusted-publishing.md:300 +#: ../../tutorials/trusted-publishing.md:303 msgid "" "Graphic showing the management page for one project. The \"Publishing\" " "link in the sidebar is highlighted." msgstr "" -#: ../../tutorials/trusted-publishing.md:302 +#: ../../tutorials/trusted-publishing.md:305 msgid "" "Once clicking on the \"Manage\" button we got to the project's page. In " "the sidebar, we have the \"publishing\" option, as highlighted here." msgstr "" -#: ../../tutorials/trusted-publishing.md:306 +#: ../../tutorials/trusted-publishing.md:309 msgid "" "This will take you to the publisher configuration page for the project. " "Trusted publishers can be configured via the forms here. Fill in the " "GitHub form with the following information:" msgstr "" -#: ../../tutorials/trusted-publishing.md:310 +#: ../../tutorials/trusted-publishing.md:313 msgid "" "Owner: the GitHub organization name for the organization that owns the " "project. If this is your personal project, then use your GitHub username " "here." msgstr "" -#: ../../tutorials/trusted-publishing.md:312 +#: ../../tutorials/trusted-publishing.md:315 msgid "Repository name: the name of the repository that contains the project." msgstr "" -#: ../../tutorials/trusted-publishing.md:313 +#: ../../tutorials/trusted-publishing.md:316 msgid "" "Workflow name: Should be `release.yaml` if you followed this guide, it is" " the workflow we just configured." msgstr "" -#: ../../tutorials/trusted-publishing.md:315 +#: ../../tutorials/trusted-publishing.md:318 msgid "" "Environment name: Should be `pypi`, as that is what we configured in " "`release.yaml`." msgstr "" -#: ../../tutorials/trusted-publishing.md:318 +#: ../../tutorials/trusted-publishing.md:321 msgid "" "Once you fill in this form and click \"Add\" the publisher is configured " "and can be used to publish new releases of your package." msgstr "" -#: ../../tutorials/trusted-publishing.md:321 +#: ../../tutorials/trusted-publishing.md:324 msgid "Fully hardened GitHub Actions release workflow" msgstr "" -#: ../../tutorials/trusted-publishing.md:323 +#: ../../tutorials/trusted-publishing.md:326 msgid "" "For better security, it is also recommended to control the permissions of" " the GitHub token used within each job of the workflow. The permissions " @@ -7468,24 +7730,24 @@ msgid "" "that configures trusted publishing and also does this is the following:" msgstr "" -#: ../../tutorials/trusted-publishing.md:333 +#: ../../tutorials/trusted-publishing.md:336 msgid "" "You can copy the above into your `release.yaml` file. You only need to " "update the `url:` field and configure trusted publishing on PyPI." msgstr "" -#: ../../tutorials/trusted-publishing.md:337 +#: ../../tutorials/trusted-publishing.md:340 msgid "" "The workflow above should be up to date with the current versions of " "GitHub actions. However, it's good to turn on Dependabot to update the " "action versions in the future." msgstr "" -#: ../../tutorials/trusted-publishing.md:340 +#: ../../tutorials/trusted-publishing.md:343 msgid "You have enabled trusted publishing for your project" msgstr "" -#: ../../tutorials/trusted-publishing.md:342 +#: ../../tutorials/trusted-publishing.md:345 msgid "" "Congratulations!! You have now configured your project to do secure " "releases when a new version is being tagged on GitHub. The workflow we " @@ -7498,23 +7760,23 @@ msgid "" " it securely." msgstr "" -#: ../../tutorials/trusted-publishing.md:346 +#: ../../tutorials/trusted-publishing.md:349 msgid "" msgstr "" -#: ../../tutorials/trusted-publishing.md:347 +#: ../../tutorials/trusted-publishing.md:350 msgid "" "" msgstr "" -#: ../../tutorials/trusted-publishing.md:348 +#: ../../tutorials/trusted-publishing.md:351 msgid "" "" msgstr "" -#: ../../tutorials/trusted-publishing.md:349 +#: ../../tutorials/trusted-publishing.md:352 msgid "" msgstr "" @@ -7817,3 +8079,142 @@ msgstr "" #~ msgid "license and" #~ msgstr "ライセンスと" + +#~ msgid "" +#~ "This lesson uses the pyOpenSci Python" +#~ " package copier template to create a" +#~ " Python package quickly. Your package " +#~ "will be installable both locally and " +#~ "remotely from a website such as " +#~ "GitHub (or GitLab) into a Python " +#~ "environment." +#~ msgstr "" + +#~ msgid "" +#~ "The template will then begin to " +#~ "copy files into the directory that " +#~ "used above. (`.` means current working" +#~ " directory" +#~ msgstr "" + +#~ msgid "" +#~ "If you use the \"bells and " +#~ "whistles\" default option when working " +#~ "through the template prompts, our " +#~ "template will create a complete package" +#~ " setup with GitHub CI actions, " +#~ "typing, tests, environments , and more" +#~ " using Hatch. If you customize the" +#~ " entire package, then you can select" +#~ " what platform you wish to host " +#~ "it on (GitHub vs GitLab), whether " +#~ "you want typing, what documentation " +#~ "engine you want to use, and more." +#~ msgstr "" + +#~ msgid "" +#~ "[Sphinx](https://www.pyopensci.org/python-package-" +#~ "guide/documentation/hosting-tools/sphinx-python-" +#~ "package-documentation-tools.html) with the " +#~ "pydata_sphinx_theme for documentation" +#~ msgstr "" + +#~ msgid "" +#~ "A `pyproject.toml` file stores metadata " +#~ "that provides instructions to various " +#~ "tools interacting with it, including " +#~ "Hatch, which will build your package." +#~ " You can also specify metadata for" +#~ " your package." +#~ msgstr "" + +#~ msgid "" +#~ "The metadata in your generated " +#~ "pyproject.toml is already setup for you" +#~ " using the information you provided " +#~ "the copier template above." +#~ msgstr "" + +#~ msgid "" +#~ "Welcome to your shiny new package! " +#~ "This page will help you get " +#~ "started with using Hatch to run " +#~ "tests, build and check your package, " +#~ "and build your documentation." +#~ msgstr "" + +#~ msgid "" +#~ "To begin, have a look at the " +#~ "`pyproject.toml` file in your package " +#~ "directory. This file contains the " +#~ "configuration for your package. This " +#~ "file is written using a .toml " +#~ "format. [You can learn more about " +#~ "toml here.](https://www.pyopensci.org/python-package-" +#~ "guide/package-structure-code/pyproject-toml-" +#~ "python-package-metadata.html) Here's the " +#~ "TL&DR:" +#~ msgstr "" + +#~ msgid "" +#~ "In the pyOpenSci Python package " +#~ "template, we have set up Hatch " +#~ "environments. You will notice at the " +#~ "bottom of the file, a [hatch " +#~ "environment](https://hatch.pypa.io/1.13/environment/) section," +#~ " that looks like this:" +#~ msgstr "" + +#~ msgid "" +#~ "Below is a Hatch environment definition" +#~ " that you will find in your " +#~ "[new project's pyproject.toml file](create-" +#~ "python-package). It is set up to " +#~ "[build your package's](build-package) " +#~ "distribution files ([source distribution](python-" +#~ "source-distribution) and [wheel](python-" +#~ "wheel))." +#~ msgstr "" + +#~ msgid "" +#~ "Notice that the environment definition " +#~ "declares two dependencies: `pip` and " +#~ "`twine`, which the environment needs to" +#~ " run successfully. This declaration is " +#~ "similar to declaring dependencies for " +#~ "your package at the top of your" +#~ " `pyproject.toml`. This section tells Hatch" +#~ " to create a new VENV with pip" +#~ " and twine installed." +#~ msgstr "" + +#~ msgid "Build your package's source (sdist) and wheel distributions" +#~ msgstr "パッケージのソース (sdist) とwheelディストリビューションをビルドします。" + +#~ msgid "Configure PyPI Trusted Publishing for the project" +#~ msgstr "" + +#~ msgid "" +#~ "GitHub Actions[^gha] is an infrastructure " +#~ "provided by GitHub to automate software" +#~ " workflows, straight from the GitHub " +#~ "repository of the project. You can " +#~ "configure automated testing for every " +#~ "pull request, automate publishing of " +#~ "documentation, automate creation of web " +#~ "pages for the project, and even " +#~ "automate the release process. For this" +#~ " lesson, we will focus on using " +#~ "actions to release and publish your " +#~ "Python package securely to PyPI." +#~ msgstr "" + +#~ msgid "" +#~ "For a release job, you need to " +#~ "clone or check out the repository. " +#~ "You can use the `actions/checkout` " +#~ "action to check out the code. You" +#~ " then install and use `hatch` to " +#~ "build your package." +#~ msgstr "" + From 6af97339d5bb8345828e088dc95449b60c00453e Mon Sep 17 00:00:00 2001 From: Felipe Moreno Date: Fri, 22 May 2026 12:24:15 -0700 Subject: [PATCH 2/3] update Portuguese translation --- locales/pt/LC_MESSAGES/TRANSLATING.po | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/locales/pt/LC_MESSAGES/TRANSLATING.po b/locales/pt/LC_MESSAGES/TRANSLATING.po index 796edfa2..bf7d90cf 100644 --- a/locales/pt/LC_MESSAGES/TRANSLATING.po +++ b/locales/pt/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: 2026-05-18 10:26-0700\n" +"POT-Creation-Date: 2026-05-22 12:19-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: pt\n" @@ -155,7 +155,7 @@ msgstr "" #: ../../TRANSLATING.md:60 msgid "" "To generate the translation files for a new language, add the language to" -" the `LANGUAGES` list in the `noxfile.py` configuration file. " +" the `LANGUAGES` list in the `conf.py` configuration file. " "[Nox](https://nox.thea.codes/en/stable/index.html) is the tool we use to " "manage the building of the guide and its translations." msgstr "" @@ -727,3 +727,14 @@ msgid "" "(translation-general) and channels for each of the languages we are " "working on (spanish-translation, japanese-translation, etc)." msgstr "" + +#~ msgid "" +#~ "To generate the translation files for" +#~ " a new language, add the language " +#~ "to the `LANGUAGES` list in the " +#~ "`noxfile.py` configuration file. " +#~ "[Nox](https://nox.thea.codes/en/stable/index.html) is the" +#~ " tool we use to manage the " +#~ "building of the guide and its " +#~ "translations." +#~ msgstr "" From 325983e30997aa000d5b1b469a641d3658c795d8 Mon Sep 17 00:00:00 2001 From: Felipe Moreno Date: Fri, 22 May 2026 12:24:59 -0700 Subject: [PATCH 3/3] linting files for Japanese translation --- locales/ja/LC_MESSAGES/TRANSLATING.po | 1 - locales/ja/LC_MESSAGES/documentation.po | 1 - locales/ja/LC_MESSAGES/index.po | 1 - locales/ja/LC_MESSAGES/package-structure-code.po | 1 - locales/ja/LC_MESSAGES/tests.po | 1 - locales/ja/LC_MESSAGES/tutorials.po | 1 - 6 files changed, 6 deletions(-) diff --git a/locales/ja/LC_MESSAGES/TRANSLATING.po b/locales/ja/LC_MESSAGES/TRANSLATING.po index 4fb15466..736ac16d 100644 --- a/locales/ja/LC_MESSAGES/TRANSLATING.po +++ b/locales/ja/LC_MESSAGES/TRANSLATING.po @@ -845,4 +845,3 @@ msgstr "" "、私たちのワークフロー、プロセス、ツールに関する一般的な質問用のチャンネル (translation-general) " "と、私たちが取り組んでいる各言語のチャンネル (spanish-translation、japanese-translationなど) " "があります。" - diff --git a/locales/ja/LC_MESSAGES/documentation.po b/locales/ja/LC_MESSAGES/documentation.po index a55a1c52..642125ff 100644 --- a/locales/ja/LC_MESSAGES/documentation.po +++ b/locales/ja/LC_MESSAGES/documentation.po @@ -3872,4 +3872,3 @@ msgstr "autodocは、あなたのコードの関数、クラス、メソッド #, fuzzy msgid "sphinx gallery for tutorials." msgstr "チュートリアルのためのsphinxギャラリー。" - diff --git a/locales/ja/LC_MESSAGES/index.po b/locales/ja/LC_MESSAGES/index.po index d2046544..c8408b56 100644 --- a/locales/ja/LC_MESSAGES/index.po +++ b/locales/ja/LC_MESSAGES/index.po @@ -595,4 +595,3 @@ msgstr "" #~ " - 飛んでいる人はこう言う。- " #~ "`反重力をインポートしました。薬箱の中のものも全部試しました。でもこれがpythonだと思う。地上の人はこう言っている。- " #~ "これで終わり？" - diff --git a/locales/ja/LC_MESSAGES/package-structure-code.po b/locales/ja/LC_MESSAGES/package-structure-code.po index defab535..36b720c9 100644 --- a/locales/ja/LC_MESSAGES/package-structure-code.po +++ b/locales/ja/LC_MESSAGES/package-structure-code.po @@ -7506,4 +7506,3 @@ msgstr "" #~ " src/package directory (see example below)." #~ " ```bash src/ package/ tests/ docs/" #~ msgstr "" - diff --git a/locales/ja/LC_MESSAGES/tests.po b/locales/ja/LC_MESSAGES/tests.po index 7d8ff916..554c1830 100644 --- a/locales/ja/LC_MESSAGES/tests.po +++ b/locales/ja/LC_MESSAGES/tests.po @@ -2088,4 +2088,3 @@ msgstr "" #~ msgstr "" #~ "**予想される境界線とその付近でテストする:** 関数が1以上の値を必要とする場合、この関数が、1と1未満と1.001の両方の値" #~ " (制約値に近い値) でも動作することを確認してください。" - diff --git a/locales/ja/LC_MESSAGES/tutorials.po b/locales/ja/LC_MESSAGES/tutorials.po index 29506c53..6df75054 100644 --- a/locales/ja/LC_MESSAGES/tutorials.po +++ b/locales/ja/LC_MESSAGES/tutorials.po @@ -8217,4 +8217,3 @@ msgstr "" #~ " then install and use `hatch` to " #~ "build your package." #~ msgstr "" -