From a933880dee17b19af66efe16774edf50e66adeb6 Mon Sep 17 00:00:00 2001 From: Roberto Date: Sat, 6 Jun 2026 19:18:42 -0700 Subject: [PATCH 1/5] docs: Portuguese translation for the first 1,000 lines in tutorials.po --- locales/pt/LC_MESSAGES/tutorials.po | 864 ++++++++++++++++++---------- 1 file changed, 564 insertions(+), 300 deletions(-) diff --git a/locales/pt/LC_MESSAGES/tutorials.po b/locales/pt/LC_MESSAGES/tutorials.po index 3568a33f..6617e944 100644 --- a/locales/pt/LC_MESSAGES/tutorials.po +++ b/locales/pt/LC_MESSAGES/tutorials.po @@ -22,315 +22,401 @@ msgstr "" #: ../../tutorials/add-license-coc.md:6 msgid "Add a `LICENSE` & `CODE_OF_CONDUCT` to your Python package" -msgstr "" +msgstr "Adicione uma `LICENSE` e um `CODE_OF_CONDUCT` ao seu pacote Python" #: ../../tutorials/add-license-coc.md:8 msgid "In the [previous lesson](add-readme) you:" -msgstr "" +msgstr "Na [lição anterior](add-readme) você:" #: ../../tutorials/add-license-coc.md:10 msgid "" -" " -"Created a basic `README.md` file for your scientific Python package" +" Created a " +"basic `README.md` file for your scientific Python package" msgstr "" +" Criou um " +"arquivo `README.md` básico para o seu pacote Python científico" #: ../../tutorials/add-license-coc.md:12 msgid "" -" " -"Learned about the core components that are useful to have in a `README` " -"file." +" Learned " +"about the core components that are useful to have in a `README` file." msgstr "" +" Aprendeu " +"sobre os componentes principais que são úteis ter em um arquivo `README`." #: ../../tutorials/add-license-coc.md:14 ../../tutorials/add-readme.md:15 msgid "Learning objectives" -msgstr "" +msgstr "Objetivos de aprendizagem" -#: ../../tutorials/add-license-coc.md:17 ../../tutorials/add-readme.md:17 -#: ../../tutorials/pyproject-toml.md:30 +#: ../../tutorials/add-license-coc.md:17 ../../tutorials/add-readme.md:17 ../../tutorials/pyproject-toml.md:30 msgid "In this lesson you will learn:" -msgstr "" +msgstr "Nesta lição você aprenderá:" #: ../../tutorials/add-license-coc.md:19 msgid "" "How to select a license and add a `LICENSE` file to your package " "repository, with a focus on the GitHub interface." msgstr "" +"Como selecionar uma licença e adicionar um arquivo `LICENSE` ao repositório " +"do seu pacote, com foco na interface do GitHub." #: ../../tutorials/add-license-coc.md:20 msgid "How to add a `CODE_OF_CONDUCT` file to your package repository." -msgstr "" +msgstr "Como adicionar um arquivo `CODE_OF_CONDUCT` ao repositório do seu pacote." #: ../../tutorials/add-license-coc.md:21 msgid "" -"How you can use the Contributors Covenant website to add generic language" -" as a starting place for your `CODE_OF_CONDUCT`." +"How you can use the Contributors Covenant website to add generic language " +"as a starting place for your `CODE_OF_CONDUCT`." msgstr "" +"Como você pode usar o site Contributors Covenant para adicionar uma " +"linguagem genérica como ponto de partida para o seu `CODE_OF_CONDUCT`." #: ../../tutorials/add-license-coc.md:24 msgid "What is a license?" -msgstr "" +msgstr "O que é uma licença?" #: ../../tutorials/add-license-coc.md:26 msgid "" "A license contains legal language about how users can use and reuse your " "software. To set the `LICENSE` for your project, you:" msgstr "" +"Uma licença contém linguagem jurídica sobre como os usuários podem usar e " +"reutilizar seu software. Para definir o `LICENSE` do seu projeto, você:" #: ../../tutorials/add-license-coc.md:28 msgid "" "Create a `LICENSE` file in your project directory that specifies the " "license that you choose for your package." msgstr "" +"Cria um arquivo `LICENSE` no diretório do projeto que especifica a licença " +"que você escolher para o seu pacote." #: ../../tutorials/add-license-coc.md:29 msgid "" "Describe your choice of license in your `pyproject.toml` data where " "metadata are set." msgstr "" +"Descreve sua escolha de licença nos dados do `pyproject.toml`, onde os " +"metadata são definidos." #: ../../tutorials/add-license-coc.md:31 msgid "" -"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." +"By adding this metadata to your [pyproject.toml](pyproject-toml) file,the " +"choice of license will be included in your package's metadatawhich 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 "" +"Ao adicionar esses metadata ao arquivo [pyproject.toml](pyproject-toml), a " +"escolha de licença será incluída nos metadata do seu pacote, que são usados " +"para popular a página do PyPI do seu pacote. O arquivo `LICENSE` também é " +"usado na interface da página inicial do repositório no GitHub e acaba sendo " +"incluído nas suas distribuições." #: ../../tutorials/add-license-coc.md:36 msgid "What license should you use?" -msgstr "" +msgstr "Qual licença você deve usar?" #: ../../tutorials/add-license-coc.md:38 msgid "" "We suggest that you use a permissive license that accommodates the other " -"most commonly used licenses in the scientific Python ecosystem (MIT[^mit]" -" and BSD-3-Clause[^bsd3]). If you are unsure, use MIT given it's the " +"most commonly used licenses in the scientific Python ecosystem (MIT[^mit] " +"and BSD-3-Clause[^bsd3]). If you are unsure, use MIT given it's the " "generally recommended license on " "[choosealicense.com](https://choosealicense.com/)." msgstr "" +"Sugerimos que você use uma licença permissiva que acomode as outras " +"licenças mais comumente usadas no ecossistema Python científico (MIT[^mit] " +"e BSD-3-Clause[^bsd3]). Se não tiver certeza, use MIT, pois é a licença " +"geralmente recomendada em [choosealicense.com](https://choosealicense.com/)." #: ../../tutorials/add-license-coc.md:41 msgid "Licenses for the scientific Python ecosystem" -msgstr "" +msgstr "Licenças para o ecossistema Python científico" #: ../../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)" msgstr "" +"[Discutimos licenças para o ecossistema Python científico com mais detalhes " +"aqui no nosso guia.](../documentation/repository-files/license-files)" #: ../../tutorials/add-license-coc.md:45 msgid "Where should the `LICENSE` file live" -msgstr "" +msgstr "Onde o arquivo `LICENSE` deve ficar" #: ../../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 " -"automagically discover it and provide users with a direct link to your " -"`LICENSE` file within your GitHub repository." +"automagically discover it and provide users with a direct link to " +"your`LICENSE` file within your GitHub repository." msgstr "" +"Seu arquivo `LICENSE` deve ficar na raiz do repositório do seu " +"pacote. Quando você adiciona o `LICENSE` na raiz, o GitHub o " +"descobrirá automaticamente e fornecerá aos usuários um link direto parao seu " +"arquivo `LICENSE` dentro do repositório no GitHub." #: ../../tutorials/add-license-coc.md:53 -msgid "" -"Image showing the GitHub repository for SunPy an accepted pyOpenSci " -"package." +msgid "Image showing the GitHub repository for SunPy an accepted pyOpenSci package." msgstr "" +"Imagem mostrando o repositório no GitHub do SunPy, um pacote " +"pyOpenSciaceito." #: ../../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, " -"the `CODE_OF_CONDUCT` file and one that specifies the license that SunPy " -"uses. These files are discovered by GitHub because they are placed in the" -" root of the project directory using standard naming conventions." +"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, the " +"`CODE_OF_CONDUCT` file and one that specifies the licensethat SunPy uses. " +"These files are discovered by GitHub because they areplaced in the root of " +"the project directory using standard naming conventions." msgstr "" +"Observe que na parte superior da seção README da página inicial do GitHub, " +"há três abas com links diretos para o arquivo `README`, que está visível, o " +"arquivo `CODE_OF_CONDUCT` e uma que especifica a licença usada pelo SunPy. " +"Esses arquivos são descobertos pelo GitHub porque estão na raiz do " +"diretório do projeto, seguindo convenções de nomenclatura padrão." #: ../../tutorials/add-license-coc.md:62 msgid "How to add a `LICENSE` file to your package directory" -msgstr "" +msgstr "Como adicionar um arquivo `LICENSE` ao diretório do seu pacote" #: ../../tutorials/add-license-coc.md:64 msgid "There are several ways to add a `LICENSE` file:" -msgstr "" +msgstr "Há várias maneiras de adicionar um arquivo `LICENSE`:" #: ../../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 " -"the file for you." +"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 the " +"file for you." msgstr "" +"Quando você cria um novo repositório no GitHub, ele perguntará se deseja " +"adicionar um arquivo `LICENSE` naquele momento. Se você selecionar sim, ele " +"criará o arquivo para você." #: ../../tutorials/add-license-coc.md:67 msgid "" -"You can add a `LICENSE` through the GitHub gui following the [ instructions " -"here](https://docs.github.com/en/communities/setting-up-your-project-for-" -"healthy-contributions/adding-a-license-to-a-repository)." +"You can add a `LICENSE` through the GitHub gui following the [ instructions " +"here](https://docs.github.com/en/communities/setting-up-your-project-for-hea" +"lthy-contributions/adding-a-license-to-a-repository)." msgstr "" +"Você pode adicionar um `LICENSE` pela GUI do GitHub seguindo as [ instruções " +"aqui](https://docs.github.com/en/communities/setting-up-your-project-for-hea" +"lthy-contributions/adding-a-license-to-a-repository)." #: ../../tutorials/add-license-coc.md:68 msgid "You can add the file manually as we are doing in this lesson." -msgstr "" +msgstr "Você pode adicionar o arquivo manualmente, como estamos fazendo nesta lição." #: ../../tutorials/add-license-coc.md:71 msgid "If you completed the past lessons including" -msgstr "" +msgstr "Se você concluiu as lições anteriores, incluindo" #: ../../tutorials/add-license-coc.md:73 msgid "[Making your code installable](create-python-package.md) and" -msgstr "" +msgstr "[Tornar seu código instalável](create-python-package.md) e" #: ../../tutorials/add-license-coc.md:74 msgid "[publishing your package to PyPI](publish-pypi.md)" -msgstr "" +msgstr "[publicar seu pacote no PyPI](publish-pypi.md)" #: ../../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 " -"this tutorial which walks you through adding a `CODE_OF_CONDUCT`." +"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 this " +"tutorial which walks you through adding a `CODE_OF_CONDUCT`." msgstr "" +"então você já tem um arquivo `LICENSE` contendo o texto da licença MIT no " +"seu pacote Python. Assim, você pode pular para a próxima seção deste " +"tutorial, que orienta a adicionar um `CODE_OF_CONDUCT`." #: ../../tutorials/add-license-coc.md:78 msgid "" "If you don't yet have a `LICENSE` file in your directory, then continue " "reading." msgstr "" +"Se você ainda não tem um arquivo `LICENSE` no seu diretório, continue lendo." #: ../../tutorials/add-license-coc.md:81 msgid "How to add a `LICENSE` to your package - the manual way" -msgstr "" +msgstr "Como adicionar um `LICENSE` ao seu pacote — a maneira manual" #: ../../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 " -"by" +"platform such as GitHub or GitLab, then you can create a `LICENSE` file by" msgstr "" +"Se você ainda não tem um arquivo `LICENSE` e ainda não usa uma plataforma " +"como GitHub ou GitLab, pode criar um arquivo `LICENSE`" #: ../../tutorials/add-license-coc.md:85 msgid "Create a new file called `LICENSE`. If you are using shell you can type:" -msgstr "" +msgstr "Crie um novo arquivo chamado `LICENSE`. Se estiver usando o shell, digite:" #: ../../tutorials/add-license-coc.md:92 msgid "Go to [choosealicense.com](https://choosealicense.com/)" -msgstr "" +msgstr "Acesse [choosealicense.com](https://choosealicense.com/)" #: ../../tutorials/add-license-coc.md:93 msgid "Select permissive license" -msgstr "" +msgstr "Selecione uma licença permissiva" #: ../../tutorials/add-license-coc.md:94 msgid "" "It will suggest that you use the [MIT " "license](https://choosealicense.com/licenses/mit/)." msgstr "" +"Irá sugerir que você use a [licença " +"MIT](https://choosealicense.com/licenses/mit/)." #: ../../tutorials/add-license-coc.md:95 msgid "" "Copy the license text that it provides into your `LICENSE` file that you " "created above." msgstr "" +"Copie o texto da licença fornecido para o arquivo `LICENSE` que você criou " +"acima." #: ../../tutorials/add-license-coc.md:96 msgid "Save your file. You're all done!" -msgstr "" +msgstr "Salve o arquivo. Pronto!" #: ../../tutorials/add-license-coc.md:98 msgid "An overview of licenses in the scientific Python ecosystem" -msgstr "" +msgstr "Uma visão geral das licenças no ecossistema Python científico" #: ../../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 " -"Python ecosystem. We review why license files are important, which ones " -"are most commonly used for scientific software and how to select the " -"correct license." +"In the pyOpenSci [packaging " +"guidebook](../documentation/repository-files/license-files), we provide an " +"overview of licenses in the scientific Python ecosystem. Wereview why " +"license files are important, which ones are most commonlyused for " +"scientific software and how to select the correct license." msgstr "" +"No [guia de empacotamento](../documentation/repository-files/license-files) " +"do pyOpenSci, fornecemos uma visão geral das licenças no ecossistema Python " +"científico. Revisamos por que os arquivos de licença são importantes, quais " +"são mais comumente usados para software científico e como selecionar a " +"licença correta." #: ../../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" -" side of things.](https://opensource.guide/legal/#just-give-me-the-tldr-" -"on-what-i-need-to-protect-my-project)" +"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 " +"side of " +"things.](https://opensource.guide/legal/#just-give-me-the-tldr-on-what-i-nee" +"d-to-protect-my-project)" msgstr "" +"Se quiser uma visão geral ampla de por que as licenças são importantes para " +"proteger software de código aberto, [confira esta postagem de blog que " +"apresenta o lado " +"jurídico.](https://opensource.guide/legal/#just-give-me-the-tldr-on-what-i-n" +"eed-to-protect-my-project)" #: ../../tutorials/add-license-coc.md msgid "Instructions for adding a `LICENSE` file within the GitHub interface" -msgstr "" +msgstr "Instruções para adicionar um arquivo `LICENSE` na interface do GitHub" #: ../../tutorials/add-license-coc.md msgid "Add license: new GitHub repository" -msgstr "" +msgstr "Adicionar licença: novo repositório no GitHub" #: ../../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 "" +"Quando você cria um novo repositório no GitHub, pode adicionar um arquivo " +"`LICENSE` pela interface do GitHub." #: ../../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. " -"Below that you can add a description of the repository. Below that you " -"can set it to be public or private. At the bottom of the interface there " -"is an Add a README checkbox where it will add a blank readme file for " -"you. At the very bottom there is a line to add a .gitignore file and " -"another to choose a license." -msgstr "" +"Screenshot of the create new repository interface that GitHub provides. The " +"elements of this are the owner and repository name for the new repo. Below " +"that you can add a description of the repository. Below that you can set it " +"to be public or private. At the bottom of the interface there is an Add a " +"README checkbox where it will add a blank readme file for you. At the very " +"bottom there is a line to add a.gitignore file and another to choose a " +"license." +msgstr "" +"Captura de tela da interface de criação de novo repositório do GitHub. Os " +"elementos são o proprietário e o nome do repositório para o novo repo. " +"Abaixo disso, você pode adicionar uma descrição do repositório. Mais " +"abaixo, pode definir como público ou privado. Na parte inferior da " +"interface há uma caixa de seleção Adicionar um README, que adicionaum " +"arquivo readme em branco para você. Na parte debaixo há uma linha para " +"adicionar um arquivo .gitignore e outra paraescolher uma licença." #: ../../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." +"Image showing the GitHub interface that allows you to add a `LICENSE` and " +"`README` file when you create a new repository." msgstr "" +"Imagem mostrando a interface do GitHub que permite adicionar um arquivo " +"`LICENSE` e um `README` ao criar um novo repositório." #: ../../tutorials/add-license-coc.md msgid "Add `LICENSE`: Existing GitHub repository" -msgstr "" +msgstr "Adicionar `LICENSE`: repositório GitHub existente" #: ../../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 " -"repository." +"If you already have a GitHub repository for your package, then you canadd a " +"`LICENSE` using the GitHub interface by adding a new file to therepository." msgstr "" +"Se você já tem um repositório no GitHub para o seu pacote, pode adicionar " +"um `LICENSE` pela interface do GitHub, criando um novo arquivo no " +"repositório." #: ../../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" -"/setting-up-your-project-for-healthy-contributions/adding-a-license-" -"to-a-repository) ." +"Follow the instructions to select and add a license to your repositoryon " +"the [GitHub LICENSE " +"page](https://docs.github.com/en/communities/setting-up-your-project-for-hea" +"lthy-contributions/adding-a-license-to-a-repository)." msgstr "" +"Siga as instruções para selecionar e adicionar uma licença ao seu " +"repositório na [página LICENSE do " +"GitHub](https://docs.github.com/en/communities/setting-up-your-project-for-h" +"ealthy-contributions/adding-a-license-to-a-repository)." #: ../../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 " -"pull` to update your local branch." +"repository with the repository on GitHub.com. This means running`git pull` " +"to update your local branch." msgstr "" +"Depois de adicionar o arquivo `LICENSE`, sincronize o repositório git local " +"com o repositório em GitHub.com. Isso significa executar `git pull` para " +"atualizar seu branch local." #: ../../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 " -"3-clause New or revised license. Then there is some text describing both " -"what the license is and the associated permissions for that specific " -"license. At the bottom of the image, the actual text for the license is " -"shown in the LICENSE file." +"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 3-clause " +"New or revised license. Then there is some text describing both what the " +"license is and the associated permissions forthat specific license. At the " +"bottom of the image, the actual text forthe license is shown in the LICENSE " +"file." msgstr "" +"Imagem mostrando como o arquivo LICENSE aparece na interface do GitHub. No " +"topo, você vê a licença em si — nesta imagem, BSD 3-clause New or revised " +"license. Em seguida, há um texto descrevendo o que é a licença e as " +"permissões associadas a ela. Na parte inferior da imagem,o texto completo " +"da licença é exibido no arquivo LICENSE." #: ../../tutorials/add-license-coc.md:135 msgid "" "You can view a summary of the `LICENSE` chosen on your project's GitHub " "landing page." msgstr "" +"Você pode ver um resumo do `LICENSE` escolhido na página inicial do GitHub " +"do seu projeto." #: ../../tutorials/add-license-coc.md:142 msgid "" @@ -338,10 +424,13 @@ msgid "" "about the `CODE_OF_CONDUCT.md` file and how to add it to your package " "directory." msgstr "" +"Agora você sabe como adicionar um `LICENSE` ao seu projeto. Em seguida, " +"aprenderá sobre o arquivo `CODE_OF_CONDUCT.md` e como adicioná-lo ao " +"diretório do seu pacote." #: ../../tutorials/add-license-coc.md:147 msgid "What is a code of conduct file?" -msgstr "" +msgstr "O que é um arquivo de código de conduta?" #: ../../tutorials/add-license-coc.md:149 #, python-brace-format @@ -349,465 +438,560 @@ msgid "" "A `CODE_OF_CONDUCT` file is a {term}`Code of conduct` used to establish " "guidelines for how people in your community interact." msgstr "" +<<<<<<< HEAD "Um arquivo CODE_OF_CONDUCT é um {term}`código de conduta` usado para estabelecer" "diretrizes sobre como as pessoas em sua comunidade interagem." +======= +"Um arquivo `CODE_OF_CONDUCT` é um {term}`Código de conduta` usado " +"para estabelecer diretrizes sobre como as pessoas da sua comunidade " +"interagem." +>>>>>>> 6913c90 (docs: Portuguese translation for the first 1,000 lines in tutorials.po) #: ../../tutorials/add-license-coc.md:152 msgid "" "This file is critical to supporting your community as it grows. The " "`CODE_OF_CONDUCT`:" msgstr "" +"Este arquivo é fundamental para apoiar sua comunidade conforme ela cresce. " +"O `CODE_OF_CONDUCT`:" #: ../../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 "" +"Estabelece diretrizes sobre como usuários e contribuidores interagem entre " +"si e com você no repositório do software." #: ../../tutorials/add-license-coc.md:156 msgid "Identifies negative behaviors that you don't want in your interactions." -msgstr "" +msgstr "Identifica comportamentos negativos que você não quer nas interações." #: ../../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." +"You can use your code of conduct as a tool that can be referenced " +"whenmoderating challenging conversations." msgstr "" +"Você pode usar seu código de conduta como ferramenta de referência ao " +"moderar conversas difíceis." #: ../../tutorials/add-license-coc.md:160 msgid "What to put in your `CODE_OF_CONDUCT` file" -msgstr "" +msgstr "O que incluir no seu arquivo `CODE_OF_CONDUCT`" #: ../../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 " -"language](https://www.contributor-" -"covenant.org/version/2/1/code_of_conduct/) as a starting place." +"If you are unsure of what language to add to your `CODE_OF_CONDUCT` file, " +"we suggest that you adopt the [contributor covenant " +"language](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)" +"asastartingplace." msgstr "" +"Se não souber que linguagem adicionar ao arquivo `CODE_OF_CONDUCT`, " +"sugerimos adotar a [linguagem do Contributors " +"Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)" +"como ponto de partida." #: ../../tutorials/add-license-coc.md:165 msgid "" "![Contributor " -"Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)" +"Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" +")" msgstr "" +"![Contributor " +"Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" +")" #: ../../tutorials/add-license-coc.md:165 msgid "Contributor Covenant" -msgstr "" +msgstr "Contributor Covenant" #: ../../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 "" +"O `CODE_OF_CONDUCT.md` deve ficar na raiz do diretório do projeto, assim " +"como o arquivo `LICENSE`." #: ../../tutorials/add-license-coc.md:169 msgid "How to add a `CODE_OF_CONDUCT` file to your package directory" -msgstr "" +msgstr "Como adicionar um arquivo `CODE_OF_CONDUCT` ao diretório do seu pacote" #: ../../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 "" +"Adicione um arquivo `CODE_OF_CONDUCT.md` na raiz do seu repositório, se ele " +"ainda não existir." #: ../../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 " -"conduct](https://www.contributor-" -"covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) to your " -"`CODE_OF_CONDUCT.md` file. Be sure to fill in any placeholder " -"information. Read the text closely to ensure you both understand it and " -"also agree with its contents!" -msgstr "" +"Visit the [contributor covenant " +"website](https://www.contributor-covenant.org/) and add [the markdown " +"version of their code of " +"conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/co" +"de_of_conduct.md)toyour`CODE_OF_CONDUCT.md`file.Besuretofillin any " +"placeholder information. Read the text closely to ensure you both " +"understand it and also agree with its contents!" +msgstr "" +"Visite o [site do Contributors " +"Covenant](https://www.contributor-covenant.org/) e adicione [a versão em " +"markdown do código de " +"conduta](https://www.contributor-covenant.org/version/2/1/code_of_conduct/co" +"de_of_conduct.md)ao seu arquivo `CODE_OF_CONDUCT.md`. Preencha qualquer " +"informação placeholder. Leia o texto com atenção para garantir que entende e " +"concorda com o conteúdo!" #: ../../tutorials/add-license-coc.md:179 msgid "That's it - you've now added a code of conduct to your package directory." -msgstr "" +msgstr "É isso — você adicionou um código de conduta ao diretório do seu pacote." #: ../../tutorials/add-license-coc.md:181 msgid "Additional Code of Conduct resources" -msgstr "" +msgstr "Recursos adicionais sobre código de conduta" #: ../../tutorials/add-license-coc.md:184 msgid "" "[ Guide: `CODE_OF_CONDUCT.md` " -"files](https://docs.github.com/en/communities/setting-up-your-project-" -"for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" +"files](https://docs.github.com/en/communities/setting-up-your-project-for-he" +"althy-contributions/adding-a-code-of-conduct-to-your-project)" msgstr "" +"[ Guia: arquivos " +"`CODE_OF_CONDUCT.md`](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:185 msgid "" "[pyOpenSci package guide `CODE_OF_CONDUCT.md` " -"overview](https://www.pyopensci.org/python-package-guide/documentation" -"/repository-files/code-of-conduct-file.html)" +"overview](https://www.pyopensci.org/python-package-guide/documentation/repos" +"itory-files/code-of-conduct-file.html)" msgstr "" +"[Visão geral do `CODE_OF_CONDUCT.md` no guia de pacotes do " +"pyOpenSci](https://www.pyopensci.org/python-package-guide/documentation/repo" +"sitory-files/code-of-conduct-file.html)" -#: ../../tutorials/add-license-coc.md:188 ../../tutorials/add-readme.md:240 -#: ../../tutorials/publish-conda-forge.md:475 -#: ../../tutorials/pyproject-toml.md:699 +#: ../../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 "" +msgstr " Encerramento" #: ../../tutorials/add-license-coc.md:190 msgid "In this lesson and the [last lesson](add-readme), you have added a:" -msgstr "" +msgstr "Nesta lição e na [lição anterior](add-readme), você adicionou um:" #: ../../tutorials/add-license-coc.md:192 msgid "`README` file;" -msgstr "" +msgstr "arquivo `README`;" #: ../../tutorials/add-license-coc.md:193 msgid "`LICENSE` file and a" -msgstr "" +msgstr "arquivo `LICENSE` e um" #: ../../tutorials/add-license-coc.md:194 msgid "`CODE_OF_CONDUCT` file." -msgstr "" +msgstr "arquivo `CODE_OF_CONDUCT`." #: ../../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" -" interact with package maintainers." +"These are fundamental files needed for every scientific Python " +"packagerepository. These files help users understand how to use your " +"package and interact with package maintainers." msgstr "" +"Esses são arquivos fundamentais para todo repositório de pacote " +"Python científico. Eles ajudam os usuários a entender como usar seu pacote e " +"interagir com os mantenedores(as) do pacote." -#: ../../tutorials/add-license-coc.md:200 -#: ../../tutorials/create-python-package.md:455 +#: ../../tutorials/add-license-coc.md:200 ../../tutorials/create-python-package.md:455 msgid "In the upcoming lessons, you will:" -msgstr "" +msgstr "Nas próximas lições, você irá:" #: ../../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." msgstr "" +"[Adicionar mais metadata ao arquivo `pyproject.toml`](pyproject-toml) para " +"apoiar o build e a publicação do seu pacote no PyPI." #: ../../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 "" +"Publicar uma nova versão do seu pacote Python no test PyPI para visualizar " +"a página de metadata atualizada." -#: ../../tutorials/add-license-coc.md:208 -#: ../../tutorials/create-python-package.md:550 -#: ../../tutorials/publish-conda-forge.md:487 -#: ../../tutorials/publish-pypi.md:419 +#: ../../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 "" +msgstr "Notas de rodapé" #: ../../tutorials/add-license-coc.md:210 msgid "https://opensource.org/license/mit/" -msgstr "" +msgstr "https://opensource.org/license/mit/" #: ../../tutorials/add-license-coc.md:211 msgid "https://opensource.org/license/bsd-3-clause/" -msgstr "" +msgstr "https://opensource.org/license/bsd-3-clause/" #: ../../tutorials/add-readme.md:6 #, python-brace-format msgid "Add a {term}`README` file to your {term}`Python package`" msgstr "" +"Adicione um arquivo {term}`README` ao seu {term}`pacote Python " +"`" #: ../../tutorials/add-readme.md:8 msgid "In the previous lessons you learned:" -msgstr "" +msgstr "Nas lições anteriores você aprendeu:" #: ../../tutorials/add-readme.md:10 msgid "[What a Python package is](intro.md)" -msgstr "" +msgstr "[O que é um pacote Python](intro.md)" #: ../../tutorials/add-readme.md:11 msgid "[How to make your code installable](create-python-package)" -msgstr "" +msgstr "[Como tornar seu código instalável](create-python-package)" #: ../../tutorials/add-readme.md:12 msgid "[How to publish your package to (test) PyPI](publish-pypi.md)" -msgstr "" +msgstr "[Como publicar seu pacote no (test) PyPI](publish-pypi.md)" #: ../../tutorials/add-readme.md:13 msgid "[How to publish your package to conda-forge](publish-conda-forge.md)" -msgstr "" +msgstr "[Como publicar seu pacote no conda-forge](publish-conda-forge.md)" #: ../../tutorials/add-readme.md:19 msgid "How to add a **README.md** file to your package." -msgstr "" +msgstr "Como adicionar um arquivo **README.md** ao seu pacote." #: ../../tutorials/add-readme.md:20 msgid "What the core elements of a **README.md** file are." -msgstr "" +msgstr "Quais são os elementos principais de um arquivo **README.md**." #: ../../tutorials/add-readme.md:23 msgid "What is a README file?" -msgstr "" +msgstr "O que é um arquivo README?" #: ../../tutorials/add-readme.md:25 #, python-brace-format msgid "" -"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:" +"The `README.md` file is the project's {term}`README` and is located atthe " +"root of your project directory. It helps a user understand:" msgstr "" +"O arquivo `README.md` é o {term}`README` do projeto e fica na raiz do " +"diretório do projeto. Ele ajuda o usuário a entender:" #: ../../tutorials/add-readme.md:29 msgid "You package's name" -msgstr "" +msgstr "O nome do seu pacote" #: ../../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 " -"audience." +"What the package does. Your README file should clearly state the problem(s) " +"that your software is designed to solve and its target audience." msgstr "" +"O que o pacote faz. Seu README deve deixar claro o(s) problema(s) que seu " +"software resolve e o público-alvo." #: ../../tutorials/add-readme.md:31 msgid "The current development \"state\" of the package (through badges)" -msgstr "" +msgstr "O \"estado\" atual de desenvolvimento do pacote (por meio de badges)" #: ../../tutorials/add-readme.md:32 msgid "How to get started with using your package." -msgstr "" +msgstr "Como começar a usar seu pacote." #: ../../tutorials/add-readme.md:33 msgid "How to contribute to your package" -msgstr "" +msgstr "Como contribuir para o seu pacote" #: ../../tutorials/add-readme.md:34 msgid "How to cite your package" -msgstr "" +msgstr "Como citar seu pacote" #: ../../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 " -"used to populate your PyPI landing page." +"someone sees before they install your package. The README file isalso used " +"to populate your PyPI landing page." msgstr "" +"Seu arquivo **README.md** é importante, pois costuma ser a primeira coisa " +"que alguém vê antes de instalar seu pacote. O README também é usado para " +"popular a página do PyPI." #: ../../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 " -"include in your README file." +"Note that there is no specific content structure for README files. However, " +"this tutorial outlines the sections that we suggest that you include in " +"your README file." msgstr "" +"Note que não há uma estrutura de conteúdo específica para arquivos README. " +"No entanto, este tutorial descreve as seções que sugerimos incluir no seu " +"README." #: ../../tutorials/add-readme.md:42 msgid "Create a README.md file for your package" -msgstr "" +msgstr "Crie um arquivo README.md para o seu pacote" #: ../../tutorials/add-readme.md:44 msgid "It's time to add a `README.md` file to your project directory." -msgstr "" +msgstr "É hora de adicionar um arquivo `README.md` ao diretório do seu projeto." #: ../../tutorials/add-readme.md:46 msgid "Step 0: Create a README file" -msgstr "" +msgstr "Passo 0: Crie um arquivo README" #: ../../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." +"To get started, if you don't already have a README.md file in your project " +"directory, create one." msgstr "" +"Para começar, se ainda não tiver um arquivo README.md no diretório do " +"projeto, crie um." #: ../../tutorials/add-readme.md:50 msgid "If you created your project directory from" -msgstr "" +msgstr "Se você criou o diretório do projeto a partir de" #: ../../tutorials/add-readme.md:52 msgid "a GitHub repository online" -msgstr "" +msgstr "um repositório no GitHub online" #: ../../tutorials/add-readme.md:53 msgid "using `hatch init`" -msgstr "" +msgstr "usando `hatch init`" #: ../../tutorials/add-readme.md:55 msgid "Then you may already have a README.MD file in your project directory." -msgstr "" +msgstr "Então você pode já ter um arquivo README.MD no diretório do projeto." #: ../../tutorials/add-readme.md:61 msgid "Step 1: Add the name of your package as the README title" -msgstr "" +msgstr "Passo 1: Adicione o nome do seu pacote como título do README" #: ../../tutorials/add-readme.md:63 msgid "At the top of the `README.md` file, add the name of your package." -msgstr "" +msgstr "No topo do arquivo `README.md`, adicione o nome do seu pacote." #: ../../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." +"If you are using markdown it should be a header 1 (H1) tag which is denoted " +"with a single `#` sign." msgstr "" +"Se estiver usando markdown, deve ser um título H1 (header 1), indicado com " +"um único `#`." #: ../../tutorials/add-readme.md:67 msgid "`# Package-title-here`" -msgstr "" +msgstr "`# Package-title-here`" #: ../../tutorials/add-readme.md:69 msgid "Step 2: add badges to the top of your README file" -msgstr "" +msgstr "Passo 2: adicione badges ao topo do seu arquivo README" #: ../../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:" +"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:" msgstr "" +"É comum os mantenedores adicionarem badges ao topo dos arquivos README. Os " +"badges permitem que você e os pessoas usuárias do pacote acompanhem coisas " +"como:" #: ../../tutorials/add-readme.md:73 msgid "Broken documentation and test builds." -msgstr "" +msgstr "Falhas em builds de documentação e testes." #: ../../tutorials/add-readme.md:74 msgid "Versions of your package that are on PyPI and conda." -msgstr "" +msgstr "Versões do seu pacote no PyPI e no conda." #: ../../tutorials/add-readme.md:75 msgid "" -"Whether your package has been reviewed and vetted by an organization such" -" as pyOpenSci and/or JOSS." +"Whether your package has been reviewed and vetted by an organization such " +"as pyOpenSci and/or JOSS." msgstr "" +"Se o seu pacote foi revisado e validado por uma organização como pyOpenSci " +"e/ou JOSS." #: ../../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" -"/py-pi-version). This badge will dynamically update as you release new " -"versions of your package to PyPI." +"[shields.io to create a package version " +"badge](https://shields.io/badges/py-pi-version). This badge will " +"dynamically update as you release new versions of your package to PyPI." msgstr "" +"Se você já publicou seu pacote em pypi.org, pode usar [shields.io para criar " +"um badge de versão do pacote](https://shields.io/badges/py-pi-version). " +"Esse badge será atualizado dinamicamente conforme você publica novas " +"versões do pacote no PyPI." #: ../../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." +"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 "" +"Caso contrário, pode deixar o topo vazio por enquanto e adicionar badges ao " +"README mais tarde, quando fizer sentido." #: ../../tutorials/add-readme.md:81 msgid "Step 3: Add a description of what your package does" -msgstr "" +msgstr "Passo 3: Adicione uma descrição do que seu pacote faz" #: ../../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." +"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 "" +"Abaixo dos badges (se houver), adicione um trecho de texto com uma visão " +"geral fácil de entender do que seu pacote faz." #: ../../tutorials/add-readme.md:87 msgid "Keep this section short." -msgstr "" +msgstr "Mantenha esta seção curta." #: ../../tutorials/add-readme.md:88 msgid "Try to avoid jargon." -msgstr "" +msgstr "Tente evitar jargão." #: ../../tutorials/add-readme.md:89 msgid "" -"Define technical terms that you use to make the description accessible to" -" more people." +"Define technical terms that you use to make the description accessibleto " +"more people." msgstr "" +"Defina termos técnicos que usar para tornar a descrição acessível a mais " +"pessoas." #: ../../tutorials/add-readme.md:91 msgid "" -"Remember that the more people understand what your package does, the more" -" people will use it." +"Remember that the more people understand what your package does, the more " +"people will use it." msgstr "" +"Lembre-se: quanto mais pessoas entenderem o que seu pacote faz, mais " +"pessoas o usarão." #: ../../tutorials/add-readme.md:93 msgid "Step 4: Add package installation instructions" -msgstr "" +msgstr "Passo 4: Adicione instruções de instalação do pacote" #: ../../tutorials/add-readme.md:95 msgid "Next, add instructions that tell users how to install your package." msgstr "" +"Em seguida, adicione instruções que expliquem aos usuários como instalar seu " +"pacote." #: ../../tutorials/add-readme.md:97 #, python-brace-format msgid "" -"For example, can they use {term}`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 "" +"Por exemplo, dá para instalar o pacote com {term}`pip`? `python -m " +"pip install packagename`" #: ../../tutorials/add-readme.md:100 msgid "or conda?" -msgstr "" +msgstr "ou conda?" #: ../../tutorials/add-readme.md:102 msgid "`conda install -c conda-forge packagename`." -msgstr "" +msgstr "`conda install -c conda-forge packagename`." #: ../../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 "" +"Se você ainda não publicou seu pacote em pypi.org, pode pular esta seção e " +"voltar depois para adicionar essas instruções." #: ../../tutorials/add-readme.md:108 msgid "Step 5: Any additional setup" -msgstr "" +msgstr "Passo 5: Configuração adicional" #: ../../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" -" section on additional setup to your README file." +"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 section " +"on additional setup to your README file." msgstr "" +"Em alguns casos, os usuários do pacote podem precisar " +"instalar manualmente outras ferramentas para usá-lo. Nesse caso, adicione " +"uma seção sobre configuração adicional ao README." #: ../../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:" +"Here, briefly document (or link to documentation for) any additional setup " +"that is required to use your package. This might include:" msgstr "" +"Aqui, documente brevemente (ou inclua um link para documentação " +"sobre) qualquer configuração adicional necessária para usar seu " +"pacote. Isso pode incluir:" #: ../../tutorials/add-readme.md:119 msgid "authentication information, if it is applicable to your package." -msgstr "" +msgstr "informações de autenticação, se aplicável ao seu pacote." #: ../../tutorials/add-readme.md:120 msgid "additional tool installations, such as GDAL." -msgstr "" +msgstr "instalação de ferramentas adicionais, como GDAL." #: ../../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 "" +"Muitos pacotes não precisam de uma seção de configuração adicional " +"no README. Nesse caso, você sempre pode pular esta seção." #: ../../tutorials/add-readme.md:128 msgid "Step 6: Add a get started section" -msgstr "" +msgstr "Passo 6: Adicione uma seção de primeiros passos" #: ../../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 " -"in your package." +"example that demonstrates importing and using some of the functionality in " +"your package." msgstr "" +"Em seguida, adicione uma seção de primeiros passos. Nela, inclua um pequeno " +"exemplo de código que demonstre o import e o uso de alguma funcionalidade " +"do seu pacote." #: ../../tutorials/add-readme.md:133 msgid "Provide a fully functional code snippet if possible" -msgstr "" +msgstr "Forneça um trecho de código totalmente funcional, se possível" #: ../../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." +"It is important to try to make the code examples that you provide yourusers " +"as useful as possible." msgstr "" +"É importante tentar tornar os exemplos de código que você fornece aos " +"usuários o mais úteis possível." #: ../../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." +"Be sure to provide a copy/paste code example that will work as-is " +"whenpasted into a Jupyter Notebook or .py file if that is possible." msgstr "" +"Forneça um exemplo de código para copiar/colar que funcione como está " +"quando colado em um Jupyter Notebook ou arquivo .py, se isso for possível." #: ../../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." +"If there are tokens and other steps needed to run your package, be sure to " +"be clear about what those steps are." msgstr "" +"Se forem necessários tokens e outras etapas para executar seu pacote, deixe " +"claras quais são." #: ../../tutorials/add-readme.md:143 msgid "For the pyosPackage, a short get started demo might look like this:" msgstr "" +"Para o pyosPackage, uma demonstração curta de primeiros passos pode ficar " +"assim:" #: ../../tutorials/add-readme.md:151 msgid "" @@ -815,169 +999,219 @@ msgid "" "created. If you don't have this yet, you can leave it empty for the time " "being." msgstr "" +"Ou pode ser simplesmente um link para um tutorial de primeiros passos que " +"você criou. Se ainda não tiver isso, pode deixar em branco por enquanto." #: ../../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." +"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 "" +"Este também seria um ótimo lugar para adicionar links para tutoriais que " +"ajudem os usuários a entender como usar seu pacote em workflows comuns." #: ../../tutorials/add-readme.md:159 msgid "Step 7: Community section" -msgstr "" +msgstr "Passo 7: Seção de comunidade" #: ../../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 " -"engagement will likely happen on a platform like GitHub or GitLab." +"The community section of your README file is a place to include information " +"for users who may want to engage with your project. This engagement will " +"likely happen on a platform like GitHub or GitLab." msgstr "" +"A seção de comunidade do README é o lugar para incluir informações para " +"usuários que queiram se envolver com o projeto. Esse engajamento " +"provavelmente acontecerá em uma plataforma como GitHub ou GitLab." #: ../../tutorials/add-readme.md:163 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 file in the " -"[next lesson](add-license-coc)." +"In the community section, you will add links to your contributing guide and " +"`CODE_OF_CONDUCT.md`. You will create a code of conduct filein the [next " +"lesson](add-license-coc)." msgstr "" +"Na seção de comunidade, você adicionará links para o guia de contribuição e " +"para o `CODE_OF_CONDUCT.md`. Você criará um arquivo de código de conduta na " +"[próxima lição](add-license-coc)." #: ../../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:" +"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 "" +"Conforme seu pacote cresce, você também pode ter um link para um guia de " +"desenvolvimento que contribuidores e a equipe de mantenedores seguirão. O " +"guia de desenvolvimento descreve como realizar tarefas de manutenção, como:" #: ../../tutorials/add-readme.md:170 msgid "running tests" -msgstr "" +msgstr "executar testes" #: ../../tutorials/add-readme.md:171 msgid "making package releases" -msgstr "" +msgstr "fazer releases do pacote" #: ../../tutorials/add-readme.md:172 msgid "building documentation" -msgstr "" +msgstr "gerar documentação" #: ../../tutorials/add-readme.md:173 msgid "and more." -msgstr "" +msgstr "e mais." #: ../../tutorials/add-readme.md:177 msgid "Step 8: Citation information" -msgstr "" +msgstr "Passo 8: Informações de citação" #: ../../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." +"Finally it is important to let users know how to cite your package. You can " +"communicate citation information in a few different ways." msgstr "" +"Por fim, é importante informar aos usuários como citar seu pacote. Você " +"pode comunicar informações de citação de algumas formas diferentes." #: ../../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 " -"GitHub. [Check out this short tutorial that covers setting that " +"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 GitHub. " +"[Check out this short tutorial that covers setting that " "up.](https://coderefinery.github.io/github-without-command-line/doi/)" msgstr "" +"Você pode usar uma ferramenta como o zenodo para criar um DOI e informações " +"de citação associadas ao seu pacote se ele estiver hospedado em uma " +"plataforma como o GitHub. [Confira este tutorial curto que explica como " +"configurar " +"isso.](https://coderefinery.github.io/github-without-command-line/doi/)" #: ../../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-" -"review/index.html). After being accepted by pyOpenSci, if your package is" -" in scope, you can be accepted by the Journal of Open Source Software and" -" get a cross-ref DOI through [our partnership with the Journal of Open " -"Source Software.](https://www.pyopensci.org/about-peer-review/index.html)" -msgstr "" +"Alternatively if you send your package through a peer review process such " +"as the [one lead by " +"pyOpenSci](https://www.pyopensci.org/about-peer-review/index.html). After " +"being accepted by pyOpenSci, if your package is in scope, you can be " +"accepted by the Journal of Open Source Software and get a cross-ref DOI " +"through [our partnership with the Journal of Open " +"SourceSoftware.](https://www.pyopensci.org/about-peer-review/index.html)" +msgstr "" +"Alternativamente, se você submeter seu pacote a um processo de revisão por " +"pares, como [o liderado pelo " +"pyOpenSci](https://www.pyopensci.org/about-peer-review/index.html). Depois " +"de aceito pelo pyOpenSci, se seu pacote estiver no escopo, você pode ser " +"aceito pelo Journal of Open Source Software e obter um DOI cross-ref por " +"meio da [nossa parceria com o Journal of Open " +"SourceSoftware.](https://www.pyopensci.org/about-peer-review/index.html)" #: ../../tutorials/add-readme.md:190 msgid "The finished README file" -msgstr "" +msgstr "O README finalizado" #: ../../tutorials/add-readme.md:192 msgid "Your finished `README.md` file should look something like this:" -msgstr "" +msgstr "Seu arquivo `README.md` finalizado deve ficar parecido com isto:" #: ../../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 " -"perfect template, above is a set of recommendations as you are just " -"getting started. You may find the need for other elements to be added to " -"this file as you further develop your package and as a community begins " -"to use your package." +"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 perfect " +"template, above is a set of recommendations as youare just getting started. " +"You may find the need for other elements to be added to this file as you " +"further develop your package and as a community begins to use your package." msgstr "" +"É importante considerar as informações que um novo usuário ou contribuidor " +"pode precisar ao criar seu arquivo `README.md`. Embora não exista um " +"template perfeito, acima está um conjunto de recomendações para quando você " +"está começando. Você pode precisar adicionar outros elementos a este " +"arquivo conforme desenvolve mais o pacote e uma comunidade começa a usá-lo." #: ../../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 " -"they legally can (and can't) use your package. It also:" +"your Python package. A license file is critical as it tells users how they " +"legally can (and can't) use your package. It also:" msgstr "" +"Na [próxima lição](add-license-coc.md), você adicionará um arquivo LICENSE " +"ao seu pacote Python. Um arquivo de licença é fundamental, pois informa aos " +"usuários como podem (e não podem) usar seu pacote legalmente. Ele também:" #: ../../tutorials/add-readme.md:252 msgid "Builds trust with your users" -msgstr "" +msgstr "Gera confiança com seus usuários" #: ../../tutorials/add-readme.md:253 msgid "Discourages misuse of your package and associated code" -msgstr "" +msgstr "Desencoraja o uso indevido do seu pacote e do código associado" #: ../../tutorials/command-line-reference.md:6 ../../tutorials/intro.md:63 msgid "Command Line Reference Guide" -msgstr "" +msgstr "Guia de referência da linha de comando" #: ../../tutorials/command-line-reference.md:9 msgid "" -"**What these tables are:** These tables summarize the command line inputs" -" (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." +"**What these tables are:** These tables summarize the command line inputs " +"(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 "" +"**O que são estas tabelas:** Estas tabelas resumem as entradas de linha de " +"comando (por exemplo, `pipx install hatch`, `hatch build` ou `python -m " +"build`) necessárias para concluir todas as etapas do processo de criação de " +"pacote, desde a instalação do [Hatch](get-to-know-hatch) até a publicação " +"do pacote no [PyPI](publish-pypi) e no conda-forge." #: ../../tutorials/command-line-reference.md:14 #, python-brace-format msgid "" -"**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 " +"**What these tables are not:** These tables do not cover the manual " +"ornon-automated steps (e.g., create a PyPI account, create a {term}`API " "token`) you have to complete throughout the package creation process." msgstr "" +"**O que estas tabelas não são:** Estas tabelas não cobrem as etapas manuais " +"ou não automatizadas (por exemplo, criar uma conta no PyPI, criar um " +"{term}`API token`) que você precisa concluir ao longo do processo de " +"criação do pacote." #: ../../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-" -"specific commands are indicated with parentheses after the description of" -" the command, e.g., [COMMAND_DESCRIPTION] (Windows). Corresponding " -"commands for macOS and Linux will be added in the future." +"tested on the Windows OS only. Many commands are Windows-specific. " +"OS-specific commands are indicated with parentheses after the description " +"of the command, e.g., [COMMAND_DESCRIPTION] (Windows). Corresponding " +"commands for macOS and Linux will be added inthe future." msgstr "" +"**Nota sobre sistema operacional:** A versão atual deste guia foi testada " +"apenas no Windows. Muitos comandos são específicos do Windows. Comandos " +"específicos por SO são indicados com parênteses após a descrição do " +"comando, por exemplo, [DESCRIÇÃO_DO_COMANDO] (Windows). Os comandos " +"correspondentes para macOS e Linux serão adicionados no futuro." #: ../../tutorials/command-line-reference.md:21 msgid "Environment Setup" -msgstr "" +msgstr "Configuração do ambiente" #: ../../tutorials/command-line-reference.md:43 msgid "Package Development" -msgstr "" +msgstr "Desenvolvimento do pacote" #: ../../tutorials/command-line-reference.md:62 msgid "Package Publishing" -msgstr "" +msgstr "Publicação do pacote" #: ../../tutorials/command-line-reference.md:81 msgid "Versions and Environments" -msgstr "" +msgstr "Versões e ambientes" #: ../../tutorials/create-python-package.md:7 msgid "Create a pure Python package" -msgstr "" +msgstr "Crie um pacote Python puro" -#: ../../tutorials/create-python-package.md:9 -#: ../../tutorials/develop-python-package-hatch.md:9 +#: ../../tutorials/create-python-package.md:9 ../../tutorials/develop-python-package-hatch.md:9 msgid "About this lesson" -msgstr "" +msgstr "Sobre esta lição" + + #: ../../tutorials/create-python-package.md:13 #, python-brace-format @@ -2570,15 +2804,15 @@ msgstr "" #: ../../tutorials/intro.md:42 ../../tutorials/intro.md:89 msgid "What is a Python package?" -msgstr "" +msgstr "O que é um pacote Python?" #: ../../tutorials/intro.md:42 msgid "Create a Python package" -msgstr "" +msgstr "Crie um pacote Python" #: ../../tutorials/intro.md:42 msgid "Publish to PyPI" -msgstr "" +msgstr "Publique no PyPI" #: ../../tutorials/intro.md:42 msgid "Publish to conda-forge" @@ -2626,19 +2860,22 @@ msgstr "" #: ../../tutorials/intro.md:7 msgid "Python packaging 101" -msgstr "" +msgstr "Python Packaging 101" #: ../../tutorials/intro.md:9 msgid "_A start to finish beginner-friendly tutorial_" -msgstr "" +msgstr "_Um tutorial para iniciantes, do começo ao fim_" #: ../../tutorials/intro.md:11 #, python-brace-format msgid "" -"Welcome to the pyOpenSci Python packaging tutorial series. The lessons on" +"Welcome to the pyOpenSci Python packaging tutorial se ries. The lessons on" " the upcoming pages walk you through the core steps needed to create a " "{term}`Python package`." msgstr "" +"Bem-vindo à série de tutoriais de packaging em Python " +"da pyOpenSci. As lições nas próximas páginas vão guiá‑lo(a) pelos " +"passos essenciais para criar um {term}`pacote Python`. #: ../../tutorials/intro.md:17 msgid "" @@ -2647,16 +2884,21 @@ msgid "" "package to PyPI, add a README and LICENSE file, add metadata for PyPI and" " finally publish to conda forge." msgstr "" +"Diagrama mostrando as lições do nosso tutorial de empacotamento. " +Existem 6 ao todo: o que é um pacote Python, tornar o código instalável com pip, " +publicar seu pacote no PyPI, adicionar arquivos README e LICENSE, adicionar " +"metadados para o PyPI e, por fim, publicar no conda‑forge. [pyopensci](https://www.pyopensci.org/learn.html)" #: ../../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." -msgstr "" +msgstr "Esta lição é a primeira de uma série de lições para ajudar você a " +"começar com o empacotamento em Python." #: ../../tutorials/intro.md:22 msgid "Who are these tutorials for?" -msgstr "" +msgstr "Para quem são estes tutoriais?" #: ../../tutorials/intro.md:24 msgid "" @@ -2665,51 +2907,62 @@ msgid "" "still be valuable if you are interested in better understanding the steps" " involved in creating a Python package." msgstr "" +"O conteúdo desta série de tutoriais é adequado para iniciantes e " +"parte do pressuposto de que você ainda não criou um pacote Python antes. " +"No entanto, o conteúdo ainda será útil se você estiver interessado em entender " +"melhor as etapas envolvidas na criação de um pacote Python." #: ../../tutorials/intro.md:29 msgid "" "In this series you will learn about the core elements that you need to " "publish your package to [PyPI](publish-pypi)." -msgstr "" +msgstr "Nesta série, você aprenderá sobre os elementos essenciais " +"de que precisa para publicar seu pacote no [PyPI](publish-pypi)." #: ../../tutorials/intro.md:32 msgid "" "In the second series, you will learn about infrastructure and " "documentation needed to support package maintenance." -msgstr "" +msgstr "Na segunda série, você aprenderá sobre a infraestrutura e a " +"documentação necessárias para dar suporte à manutenção do pacote." #: ../../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 "" +msgstr "Objetivos de aprendizagem" #: ../../tutorials/intro.md:79 msgid "" "This lesson introduces you to the basic components of a Python package. " "After reading this lesson you will:" -msgstr "" +msgstr "Esta lição apresenta os componentes básicos de um pacote Python. " +"Depois de ler esta lição, você será capaz de:" #: ../../tutorials/intro.md:82 msgid "Understand what a Python package is" -msgstr "" +msgstr "Entender o que é um pacote Python" #: ../../tutorials/intro.md:83 msgid "Be able to list the 5 core components of a Python package" -msgstr "" +msgstr "Ser capaz de listar os 5 componentes centrais de um pacote Python" #: ../../tutorials/intro.md:84 msgid "" "Be able to explain the difference between generalizable code and code " "that supports a specific scientific application" msgstr "" +"Ser capaz de explicar a diferença entre código generalizável e " +"código que dá suporte a uma aplicação científica específica" #: ../../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 "" +"Em um nível geral, você pode pensar em um pacote Python como uma " +"caixa de ferramentas que pode ser usada para realizar diversas tarefas." #: ../../tutorials/intro.md:94 #, python-brace-format @@ -2721,22 +2974,33 @@ msgid "" "Python code. Each module contains functions and classes, that you can " "think about as the tools in your toolbox." msgstr "" +"Um pacote Python é basicamente um diretório com uma estrutura de arquivos específica. " +"Dentro da estrutura de diretórios do pacote, há objetos {term}`Module`, " +que são arquivos que terminam em `.py` (a mesma extensão que você vê em um script Python). " +"Esses módulos permitem agrupar e organizar o seu código Python. " +"Cada módulo contém funções e classes, que você pode imaginar como as " +"ferramentas dentro da sua caixa de ferramentas." #: ../../tutorials/intro.md:103 msgid "" "Diagram showing a sketch of a toolbox filled with different tools " "including a hammer and a saw." msgstr "" +"Diagrama mostrando um esboço de uma caixa de ferramentas " +"cheia de diferentes ferramentas, incluindo um martelo e um serrote." #: ../../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." msgstr "" +"Você pode pensar em um pacote como uma caixa de ferramentas cheia de " +"ferramentas de código. Cada ferramenta pode ser uma função ou uma classe. " +"Cada ferramenta faz bem uma coisa específica." #: ../../tutorials/intro.md:110 msgid "Python packages are installable" -msgstr "" +msgstr "Pacotes Python são instaláveis" #: ../../tutorials/intro.md:112 msgid "" From 5fb8c1e1fbd01bb32a27bd1e21d40526adeb677c Mon Sep 17 00:00:00 2001 From: Roberto Date: Sun, 7 Jun 2026 12:17:26 -0700 Subject: [PATCH 2/5] docs: Portuguese translation for the first 2nd 1,000 lines in tutorials.po --- locales/pt/LC_MESSAGES/tutorials.po | 567 ++++++++++++++++++---------- 1 file changed, 365 insertions(+), 202 deletions(-) diff --git a/locales/pt/LC_MESSAGES/tutorials.po b/locales/pt/LC_MESSAGES/tutorials.po index 6617e944..9a18e127 100644 --- a/locales/pt/LC_MESSAGES/tutorials.po +++ b/locales/pt/LC_MESSAGES/tutorials.po @@ -1213,155 +1213,205 @@ msgstr "Sobre esta lição" -#: ../../tutorials/create-python-package.md:13 +##: ../../tutorials/create-python-package.md:13 #, python-brace-format msgid "" -"This lesson uses the pyOpenSci Python package copier template to create a" -" {term}`Python package` quickly. Your package will be installable both " +"This lesson uses the pyOpenSci Python package copier template to create a " +"{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 "" +"Esta lição usa o template copier de pacote Python do pyOpenSci para criar " +"um {term}`pacote Python ` rapidamente. Seu pacote será " +"instalável localmente e remotamente a partir de um site como GitHub (ou " +"GitLab) em um ambiente Python." -#: ../../tutorials/create-python-package.md:18 -#: ../../tutorials/setup-py-to-pyproject-toml.md:23 +#: ../../tutorials/create-python-package.md:18 ../../tutorials/setup-py-to-pyproject-toml.md:23 msgid "In this lesson, you will learn:" -msgstr "" +msgstr "Nesta lição, você aprenderá:" #: ../../tutorials/create-python-package.md:20 msgid "" -"How to make your code installable into any Python environment, both " -"locally and from GitHub" +"How to make your code installable into any Python environment, both locally " +"and from GitHub" msgstr "" +"Como tornar seu código instalável em qualquer ambiente Python, localmente e " +"a partir do GitHub" #: ../../tutorials/create-python-package.md:21 msgid "" -"How to update a [pyproject.toml file](pyproject-toml), 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 "" +"Como atualizar um [arquivo pyproject.toml](pyproject-toml), que contém os " +"metadata necessários para fazer build, instalar e publicar seu pacote." #: ../../tutorials/create-python-package.md:23 #, python-brace-format msgid "" -"How to declare a {term}`Build backend` 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 "" +"Como declarar um {term}`backend de construção ` que será " +"usado para fazer [build](build-package) e instalar seu pacote" #: ../../tutorials/create-python-package.md:25 msgid "How to install your package in editable mode for interactive development" -msgstr "" +msgstr "Como instalar seu pacote em modo editável para desenvolvimento interativo" #: ../../tutorials/create-python-package.md:28 msgid "**What you need to complete this lesson**" -msgstr "" +msgstr "**O que você precisa para concluir esta lição**" #: ../../tutorials/create-python-package.md:30 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" -"](get-to-know-hatch) to complete the lesson successfully." +"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](get-to-know-hatch) to complete the lesson successfully." msgstr "" +"Para concluir esta lição, você precisará de um ambiente Python local e de um " +"shell no seu computador. Será necessário ter o " +"[Copier](https://copier.readthedocs.io/en/stable/) e o [Hatch " +"instalado](get-to-know-hatch) para concluir a lição com sucesso." #: ../../tutorials/create-python-package.md:35 msgid "" "If you are using Windows or are not familiar with Shell, you may want to " -"check out the Carpentries shell lesson[^shell-lesson]. Windows users will" -" likely need to configure a tool such as " -"[gitbash](https://gitforwindows.org/) for any Shell and git-related " -"steps." +"check out the Carpentries shell lesson[^shell-lesson]. Windows users will " +"likely need to configure a tool such as " +"[gitbash](https://gitforwindows.org/) for any Shell and git-related steps." msgstr "" +"Se você usa Windows ou não está familiarizado com Shell, pode querer " +"conferir a lição de shell da Carpentries[^shell-lesson]. Usuários de " +"Windows provavelmente precisarão configurar uma ferramenta como " +"[gitbash](https://gitforwindows.org/) para qualquer etapa relacionada a " +"Shell e git." #: ../../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 " -"package. The environment box on the right reads - your Python " -"environment. It them lists your-package along with a few other core " -"packages such as Matplotlib, NumPy, Pandas, Xarray and GeoPandas." +"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 " +"package. The environment box on the right reads - your Python environment. " +"It them lists your-package along with a few other core packages such as " +"Matplotlib, NumPy, Pandas, Xarray and GeoPandas." msgstr "" +"Este diagrama tem duas caixas menores com setas apontando para a direita em " +"direção a um ambiente Python. As caixas pequenas mostram seu-pacote e pip " +"install pacote. A caixa do ambiente à direita diz — seu ambiente Python. Em " +"seguida, lista seu-pacote junto com alguns outros pacotes principais, como " +"Matplotlib, NumPy, Pandas, Xarray e GeoPandas." #: ../../tutorials/create-python-package.md:43 msgid "" "In a [previous lesson, you learned what a Python package is](intro). " -"Creating a Python package allows you to install your code into any Python" -" environment on your computer. You can then import it into workflows in " -"the same way that you might import a package such as Pandas or GeoPandas." -" If you push your code to GitHub or GitLab, you can also install it " -"directly from there. [Scroll to the bottom of the page to learn more " -"about the basic elements of a Python package.](package-overview)." -msgstr "" +"Creating a Python package allows you to install your code into any Python " +"environment on your computer. You can then import it into workflows in the " +"same way that you might import a package such as Pandas or GeoPandas. If " +"you push your code to GitHub or GitLab, you can also install it directly " +"from there. [Scroll to the bottom of the page to learn more about the basic " +"elements of a Python package.](package-overview)." +msgstr "" +"Em uma [lição anterior, você aprendeu o que é um pacote Python](intro). " +"Criar um pacote Python permite instalar seu código em qualquer ambiente " +"Python no seu computador. Em seguida, você pode importá-lo em workflows da " +"mesma forma que importaria um pacote como Pandas ou GeoPandas. Se você " +"enviar seu código para GitHub ou GitLab, também pode instalá-lo diretamente " +"de lá. [Role até o final da página para saber mais sobre os elementos " +"básicos de um pacote Python.](package-overview)." #: ../../tutorials/create-python-package.md:49 msgid "Create your Python package" -msgstr "" +msgstr "Crie seu pacote Python" #: ../../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 " -"template uses Hatch as the default packaging tool. At the bottom of this " -"lesson, you'll learn more about the basics of the Python package " -"directory structure, and associated key files (`__init__.py` and " +"template](https://github.com/pyOpenSci/pyos-package-template). Our template " +"uses Hatch as the default packaging tool. At the bottom of this lesson, " +"you'll learn more about the basics of the Python package directory " +"structure, and associated key files (`__init__.py` and `pyproject.toml`)." +msgstr "" +"Abaixo, você criará um pacote Python puro usando o [template copier " +"dopyOpenSci](https://github.com/pyOpenSci/pyos-package-template). Nosso " +"template usa Hatch como ferramenta de empacotamento padrão. No final desta " +"lição, você aprenderá mais sobre o básico da estrutura de diretórios de um " +"pacote Python e os arquivos principais associados (`__init__.py` e " "`pyproject.toml`)." -msgstr "" #: ../../tutorials/create-python-package.md:53 msgid "Step 1: Set Up the Package Directory Structure" -msgstr "" +msgstr "Passo 1: Configure a estrutura de diretórios do pacote" #: ../../tutorials/create-python-package.md:55 msgid "Open your shell or preferred terminal." -msgstr "" +msgstr "Abra seu shell ou terminal preferido." #: ../../tutorials/create-python-package.md:56 msgid "" -"Use the shell `cd` command to navigate in your shell to the location " -"where you'd like your package to live. Our template will create the " -"package directory structure for you" +"Use the shell `cd` command to navigate in your shell to the location where " +"you'd like your package to live. Our template will create the package " +"directory structure for you" msgstr "" +"Use o comando `cd` do shell para navegar até o local onde você quer que seu " +"pacote fique. Nosso template criará a estrutura de diretórios do pacote para " +"você" #: ../../tutorials/create-python-package.md:57 msgid "Choose a name for your package. The name should:" -msgstr "" +msgstr "Escolha um nome para seu pacote. O nome deve:" #: ../../tutorials/create-python-package.md:58 msgid "Have no spaces (*Required*)" -msgstr "" +msgstr "Não ter espaços (*Obrigatório*)" #: ../../tutorials/create-python-package.md:59 msgid "" "Use all lowercase characters (*Recommended*). For this tutorial, we will " "use `pyospackage`." msgstr "" +"Usar apenas letras minúsculas (*Recomendado*). Para este tutorial, usaremos " +"`pyospackage`." #: ../../tutorials/create-python-package.md:60 msgid "" -"Only use letters and the characters _ or - in the name. This means that " -"the name `pyos*package` is not an acceptable name. However, the names " +"Only use letters and the characters _ or - in the name. This means that the " +"name `pyos*package` is not an acceptable name. However, the names " "`pyos_package` or `pyos-package` are both OK." msgstr "" +"Use apenas letras e os caracteres _ ou - no nome. Isso significa que o nome " +"`pyos*package` não é aceitável. Porém, os nomes `pyos_package` " +"ou`pyos-package` estão OK." #: ../../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." +"prompts that will ask you questions and help you to customize your Python " +"package." msgstr "" +"No seu terminal, **execute o comando abaixo**. Isso iniciará uma série de " +"prompts que farão perguntas e ajudarão você a personalizar seu pacote Python." #: ../../tutorials/create-python-package.md:68 msgid "" "After running the command above, the template will walk you through a " "series of questions." msgstr "" +"Depois de executar o comando acima, o template guiará você por uma série de " +"perguntas." #: ../../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 " -"Yes, but with a minimal setup to create the most basic version" -" of your package that contains documentation, tests and a example module " -"for you to use." +"Yes, but with a minimal setup to create the most basic version " +"of your package that contains documentation, tests and a example module for " +"you to use." msgstr "" +"Observe que, quando chegar ao prompt \"Do you want to answer one more " +"question, and skip the rest, using the default values?\", você pode escolher " +"Yes, but with a minimal setup para criar a versão mais básica do " +"seu pacote, contendo documentação, testes e um example module para você usar." #: ../../tutorials/create-python-package.md:72 msgid "" @@ -1369,502 +1419,615 @@ msgid "" "username and will then create a package with basic tests, documentation, " "and GitHub configuration setup for you." msgstr "" +"Após essa pergunta, o template pedirá seu nome de usuário do GitHub " +"preferido e criará um pacote com testes básicos, documentação e " +"configuração do GitHub para você." #: ../../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.)" msgstr "" +"O template então começará a copiar arquivos para o diretório usado acima. " +"(`.` significa diretório de trabalho atual.)" #: ../../tutorials/create-python-package.md:101 msgid "The final package structure will look like this:" -msgstr "" +msgstr "A estrutura final do pacote ficará assim:" #: ../../tutorials/create-python-package.md msgid "A full package with tests, docs, and GitHub infrastructure" -msgstr "" +msgstr "Um pacote completo com testes, docs e infraestrutura do GitHub" #: ../../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 " -"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." +"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 canselect 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 "" +"Se você usar a opção padrão \"bells and whistles\" ao responder aos prompts " +"do template, nosso template criará uma configuração completa do pacote com " +"GitHub CI Actions, typing, testes, ambientes e mais usando o Hatch. Se " +"você personalizar o pacote inteiro, poderá selecionar em qual plataforma " +"deseja hospedá-lo (GitHub vs GitLab), caso queira typing, qual engine de " +"documentação quer usar, e mais." #: ../../tutorials/create-python-package.md:123 msgid "The resulting package directory looks like this:" -msgstr "" +msgstr "O diretório do pacote resultante fica assim:" #: ../../tutorials/create-python-package.md:146 msgid "The default tools that your package uses are:" -msgstr "" +msgstr "As ferramentas padrão que seu pacote usa são:" #: ../../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" +"[Sphinx](https://www.pyopensci.org/python-package-guide/documentation/hostin" +"g-tools/sphinx-python-package-documentation-tools.html)withthePyDataSphinxTh" +"emefordocumentation" msgstr "" +"[Sphinx](https://www.pyopensci.org/python-package-guide/documentation/hostin" +"g-tools/sphinx-python-package-documentation-tools.html) com o PyData Sphinx " +"Theme para documentação" #: ../../tutorials/create-python-package.md:149 msgid "pytest for testing" -msgstr "" +msgstr "pytest para testes" #: ../../tutorials/create-python-package.md:150 msgid "Hatch for environment setup" -msgstr "" +msgstr "Hatch para configuração de ambiente" #: ../../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:" +"package setup, choose `No, I want to fully customize the template.`. This " +"will allow you to select:" msgstr "" +"**Personalização completa** Se você quiser personalizar qualquer elemento " +"da configuração do seu pacote, escolha `No, I want to fully customize the " +"template.`. Isso permitirá que você selecione:" #: ../../tutorials/create-python-package.md:155 msgid "Sphinx vs [MkDocs](https://www.mkdocs.org/) vs no documentation" -msgstr "" +msgstr "Sphinx vs [MkDocs](https://www.mkdocs.org/) vs sem documentação" #: ../../tutorials/create-python-package.md:156 msgid "GitHub vs GitLab" -msgstr "" +msgstr "GitHub vs GitLab" #: ../../tutorials/create-python-package.md:157 msgid "VCS versioning" -msgstr "" +msgstr "versionamento VCS" #: ../../tutorials/create-python-package.md:158 msgid "and more" -msgstr "" +msgstr "e mais" #: ../../tutorials/create-python-package.md:161 msgid "Step 2: Explore the existing module in your package" -msgstr "" +msgstr "Passo 2: Explore o módulo existente no seu pacote" #: ../../tutorials/create-python-package.md:163 #, python-brace-format msgid "" -"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." +"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 testout your package " +"quickly." msgstr "" +"Um {term}`módulo ` refere-se a um arquivo `.py` contendo o código " +"que você quer que seu pacote acesse e execute. No subdiretório " +"`pyospackage`, você tem um module `example.py` que pode usar para testar " +"seu pacote rapidamente." #: ../../tutorials/create-python-package.md:167 msgid "Notice that the code in the example.py module, has a few features:" -msgstr "" +msgstr "Observe que o código no module example.py tem algumas características:" #: ../../tutorials/create-python-package.md:169 msgid "It has a [numpy-style docstring](numpy-docstring)" -msgstr "" +msgstr "Ele tem uma [numpy-style docstring](numpy-docstring)" #: ../../tutorials/create-python-package.md:170 msgid "It uses [typing](type-hints)" -msgstr "" +msgstr "Ele usa [typing](type-hints)" #: ../../tutorials/create-python-package.md:171 msgid "" -"At the top of the module, there is a docstring explaining what the module" -" does." -msgstr "" +"At the top of the module, there is a docstring explaining what the module " +"does." +msgstr "No topo do module, há uma docstring explicando o que o module faz." #: ../../tutorials/create-python-package.md:173 msgid "" -"Python supports different docstring formats. The most popular formats for" -" documenting Python objects are NumPy Style Docstring[^numpydoc], Google " -"Style Docstring[^googledoc], and the Epytext Style " -"Docstrings[^epytextdoc]." +"Python supports different docstring formats. The most popular formats for " +"documenting Python objects are NumPy Style Docstring[^numpydoc], Google " +"Style Docstring[^googledoc], and the Epytext Style Docstrings[^epytextdoc]." msgstr "" +"Python suporta diferentes formatos de docstring. Os formatos mais populares " +"para documentar objetos Python são NumPy Style Docstring[^numpydoc], Google " +"Style Docstring[^googledoc] e Epytext Style Docstrings[^epytextdoc]." #: ../../tutorials/create-python-package.md:175 msgid "**pyOpenSci recommends using the NumPy Docstring convention.**" -msgstr "" +msgstr "**A pyOpenSci recomenda usar a convenção NumPy Docstring.**" #: ../../tutorials/create-python-package.md:177 msgid "" -"[Learn more about docstrings here](api-docstrings) for an overview of " -"both topics." +"[Learn more about docstrings here](api-docstrings) for an overview of both " +"topics." msgstr "" +"[Saiba mais sobre docstrings aqui](api-docstrings) para uma visão geral de " +"ambos os tópicos." #: ../../tutorials/create-python-package.md:206 msgid "Python modules and the `__init__.py` file" -msgstr "" +msgstr "Módulos Python e o arquivo `__init__.py`" #: ../../tutorials/create-python-package.md:210 msgid "The word module refers to a `.py` file containing Python code." -msgstr "" +msgstr "A palavra módulo refere-se a um arquivo `.py` contendo código Python." #: ../../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" -" can have multiple modules[^python-modules]." +"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 can " +"have multiple modules[^python-modules]." msgstr "" +"O `__init__.py` permite que o Python reconheça que um diretório contém pelo " +"menos um módulo que pode ser importado e usado no seu código. Um pacote " +"pode ter vários módulos[^python-modules]." #: ../../tutorials/create-python-package.md:217 msgid "Step 3: Optional -- Add code to your module" -msgstr "" +msgstr "Passo 3: Opcional -- Adicione código ao seu módulo" #: ../../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 " +"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 "" +"Se quiser, adicione uma segunda função ao módulo `example.py`. Pode ser " +"uma função simples. Por exemplo, escreva uma segunda função que " +"multiplique números." #: ../../tutorials/create-python-package.md:222 msgid "Step 4: Check out the metadata in your `pyproject.toml` file" -msgstr "" +msgstr "Passo 4: Confira o metadata no seu arquivo `pyproject.toml`" #: ../../tutorials/create-python-package.md:224 msgid "" "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." +"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 "" +"Um arquivo [pyproject.toml](pyproject-toml) armazena metadata que fornece " +"instruções a várias ferramentas que interagem com ele, incluindo " +"[Hatch](get-to-know-hatch), que fará o build do seu pacote. Você também pode " +"especificar metadata para o seu pacote." #: ../../tutorials/create-python-package.md:229 msgid "" -"You will learn more about the `pyproject.toml` format in the [next lesson" -" when you add additional metadata/information to this file.](pyproject-" -"toml.md)" +"You will learn more about the `pyproject.toml` format in the [next lesson " +"when you add additional metadata/information to this " +"file.](pyproject-toml.md)" msgstr "" +"Você aprenderá mais sobre o formato `pyproject.toml` na [próxima lição, " +"quando adicionar metadata/informações adicionais a este " +"arquivo.](pyproject-toml.md)" #: ../../tutorials/create-python-package.md:232 msgid "" "The metadata in your generated `pyproject.toml` is already setup for you " "using the information you provided the copier template above." msgstr "" +"O metadata no seu `pyproject.toml` gerado já está configurado para você com " +"as informações que você forneceu ao copiar o template acima." #: ../../tutorials/create-python-package.md:234 msgid "Brief overview of the TOML file" -msgstr "" +msgstr "Visão geral breve do arquivo TOML" #: ../../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 "" +"[O formato TOML](https://toml.io/en/) consiste em tabelas e " +"variáveis. Tabelas são seções de informação indicadas por colchetes:" #: ../../tutorials/create-python-package.md:239 msgid "`[this-is-a-table]`." -msgstr "" +msgstr "`[this-is-a-table]`." #: ../../tutorials/create-python-package.md:241 msgid "" -"Tables can contain variables within them defined by a variable name and " -"an `=` sign. For instance, a `build-system` table most often holds two " -"(2) variables:" +"Tables can contain variables within them defined by a variable name and an " +"`=` sign. For instance, a `build-system` table most often holdstwo (2) " +"variables:" msgstr "" +"Tabelas podem conter variáveis definidas por um nome de variável e um sinal " +"de `=`. Por exemplo, uma tabela `build-system` geralmente contém duas (2) " +"variáveis:" #: ../../tutorials/create-python-package.md:244 msgid "" -"`requires = `, which tells a build tool what tools it needs to install " -"prior to building your package. In this case " +"`requires = `, which tells a build tool what tools it needs to installprior " +"to building your package. In this case " "[hatchling](https://pypi.org/project/hatchling/)." msgstr "" +"`requires = `, que informa a uma ferramenta de build quais ferramentas ela " +"precisa instalar antes de fazer o build do seu pacote. Neste caso, " +"[hatchling](https://pypi.org/project/hatchling/)." #: ../../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`)." +"`build-backend = `, which is used to define the specific build-backendname, " +"(in this example we are using `hatchling.build`)." msgstr "" +"`build-backend = `, que é usado para definir o nome específico do " +"build-backend (neste exemplo estamos usando `hatchling.build`)." #: ../../tutorials/create-python-package.md:255 msgid "" "TOML organizes data structures, defining relationships within a " "configuration file." msgstr "" +"TOML organiza estruturas de dados, definindo relacionamentos dentro de um " +"arquivo de configuração." #: ../../tutorials/create-python-package.md:258 msgid "[Learn more about the pyproject.toml format here.](pyprojecttoml-metadata)" -msgstr "" +msgstr "[Saiba mais sobre o formato pyproject.toml aqui.](pyprojecttoml-metadata)" #: ../../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." +"Open up the `pyproject.toml` file that Hatch created in your favorite text " +"editor. It should look something like the example below." msgstr "" +"Abra o arquivo `pyproject.toml` que o Hatch criou no seu editor de texto " +"favorito. Ele deve parecer algo como o exemplo abaixo." #: ../../tutorials/create-python-package.md:262 msgid "" -"Make sure the package version, package name, and author name look " -"correct. The email is optional." +"Make sure the package version, package name, and author name look correct. " +"The email is optional." msgstr "" +"Verifique se a versão do pacote, o nome do pacote e o nome do autor estão " +"corretos. O e-mail é opcional." #: ../../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." +"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 "" +"Na parte inferior do arquivo `pyproject.toml` gerado pelo template, você " +"verá uma seção que define ambientes Hatch. Abordaremos ambientes Hatch " +"em uma lição posterior." #: ../../tutorials/create-python-package.md:302 msgid "The bare minimum needed in a pyproject.toml file" -msgstr "" +msgstr "O mínimo necessário em um arquivo pyproject.toml" #: ../../tutorials/create-python-package.md:305 msgid "" -"The core information that you need in a `pyproject.toml` file to publish " -"on PyPI is your **package's name** and the **version**. However, we " -"suggest that you flesh out your metadata early on in the `pyproject.toml`" -" file." +"The core information that you need in a `pyproject.toml` file to publish on " +"PyPI is your **package's name** and the **version**. However, we suggest " +"that you flesh out your metadata early on in the `pyproject.toml` file." msgstr "" +"As informações essenciais que você precisa em um arquivo `pyproject.toml` " +"para publicar no PyPI são o **nome do pacote** e a **versão**. Porém, " +"sugerimos que você preencha seu metadata logo no início no arquivo " +"`pyproject.toml`." #: ../../tutorials/create-python-package.md:307 msgid "" -"Once you have your project metadata in the `pyproject.toml` file, you " -"will rarely update it." +"Once you have your project metadata in the `pyproject.toml` file, you will " +"rarely update it." msgstr "" +"Depois que você tiver o metadata do projeto no arquivo `pyproject.toml`, " +"raramente precisará atualizá-lo." #: ../../tutorials/create-python-package.md:311 msgid "Step 5: Install your package locally" -msgstr "" +msgstr "Passo 5: Instale seu pacote localmente" #: ../../tutorials/create-python-package.md:313 msgid "At this point, you should have:" -msgstr "" +msgstr "Neste ponto, você deve ter:" #: ../../tutorials/create-python-package.md:315 msgid "A project directory structure with a `pyproject.toml` file at the root" msgstr "" +"Uma estrutura de diretório de projeto com um arquivo `pyproject.toml` na " +"raiz" #: ../../tutorials/create-python-package.md:316 msgid "A package directory containing an empty `__init__.py` file and" -msgstr "" +msgstr "Um diretório de pacote contendo um arquivo `__init__.py` vazio e" #: ../../tutorials/create-python-package.md:317 msgid "At least one Python module (e.g. `example.py`)" -msgstr "" +msgstr "Pelo menos um Python module (por exemplo, `example.py`)" #: ../../tutorials/create-python-package.md:319 msgid "You are now ready to install (and build) your Python package!" -msgstr "" +msgstr "Agora você está pronto para instalar (e fazer o build) do seu pacote Python!" #: ../../tutorials/create-python-package.md:321 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." +"While you can do this using Hatch, we will use pip for this lesson, soyou " +"can see how to install your tool into your preferred environment." msgstr "" +"Embora você possa fazer isso usando Hatch, usaremos pip nesta lição, para " +"que você veja como instalar sua ferramenta no ambiente de sua " +"preferência." #: ../../tutorials/create-python-package.md:323 msgid "" -"First, open your preferred shell (Windows users may use something like " -"GitBash) and `cd` into your project directory if you are not already " +"First, open your preferred shell (Windows users may use something " +"likeGitBash) and `cd` into your project directory if you are not already " "there." msgstr "" +"Primeiro, abra seu shell preferido (usuários do Windows podem usar algo " +"como GitBash) e use `cd` para ir ao diretório do projeto, se ainda não " +"estiver lá." #: ../../tutorials/create-python-package.md:324 msgid "Activate the Python environment that you wish to use." -msgstr "" +msgstr "Ative o ambiente Python que deseja usar." #: ../../tutorials/create-python-package.md:325 msgid "Run `python -m pip install -e .`" -msgstr "" +msgstr "Execute `python -m pip install -e .`" -#: ../../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 +#: ../../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 "" +msgstr "Todo" #: ../../tutorials/create-python-package.md:328 msgid "Add this back in when the lesson is published" -msgstr "" +msgstr "Adicionar isso de volta quando a lição for publicada" #: ../../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)." +"Activate the Python environment that you wish to use. If you need helpwith " +"working with virtual environments check out this lesson (add link)." msgstr "" +"Ative o ambiente Python que deseja usar. Se precisar de ajuda para " +"trabalhar com ambiente virtual, confira esta lição (adicionar link)." #: ../../tutorials/create-python-package.md:355 msgid "What does `python -m pip install -e .` do?" -msgstr "" +msgstr "O que `python -m pip install -e .` faz?" #: ../../tutorials/create-python-package.md:358 msgid "" -"`python -m pip install -e .` installs your package into the current " -"active Python environment in **editable mode** (`-e`). Installing your " -"package in editable mode, allows you to work on your code and then test " -"the updates interactively in your favorite Python interface. One " -"important caveat of editable mode is that every time you update your " -"code, you need to restart Python." +"`python -m pip install -e .` installs your package into the current active " +"Python environment in **editable mode** (`-e`). Installing yourpackage in " +"editable mode, allows you to work on your code and thentest the updates " +"interactively in your favorite Python interface. One important caveat of " +"editable mode is that every time you update your code, you need to restart " +"Python." msgstr "" +"`python -m pip install -e .` instala seu pacote no ambiente Python ativo " +"atual em **modo editável** (`-e`). Instalar seu pacote em modo editável " +"permite que você trabalhe no seu código e teste as atualizações de forma " +"interativa na sua interface Python favorita. Uma ressalva importante do modo " +"editável é que, sempre que atualizar seu código, você precisa reiniciar o " +"Python." #: ../../tutorials/create-python-package.md:363 msgid "" -"If you wish to install the package regularly (not in editable mode) you " -"can use:" +"If you wish to install the package regularly (not in editable mode) you can " +"use:" msgstr "" +"Se quiser instalar o pacote normalmente (não em modo editável), você pode " +"usar:" #: ../../tutorials/create-python-package.md:366 msgid "`python -m pip install . `" -msgstr "" +msgstr "`python -m pip install . `" #: ../../tutorials/create-python-package.md:368 msgid "**Using `python -m` when calling `pip`**" -msgstr "" +msgstr "**Usando `python -m` ao chamar `pip`**" #: ../../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 " -"are calling the version of pip installed in your current environment." +"current active environment. `python -m` is important to ensure that you are " +"calling the version of pip installed in your current environment." msgstr "" +"Acima, você usa`python -m` para chamar a versão do pip instalada no seu " +"ambiente ativo atual. `python -m` é importante para garantir que você " +"está chamando a versão do pip instalada no seu ambiente atual." #: ../../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 " -"folder by using the `.`. You could also specify a path to the project " -"directory on your computer instead of the `.` which tells pip to use the " -"current working directory." +"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 folder " +"by using the `.`. You could also specify a path tothe project directory on " +"your computer instead of the `.` which tells pip to use the current working " +"directory." msgstr "" +"IMPORTANTE: pip também pode ser usado para instalar pacotes do PyPI. Porém, " +"neste caso, você está dizendo ao pip para instalar seu pacote apartir de " +"uma pasta local usando o `.`. Você também poderia especificar um caminho " +"para o diretório do projeto no seu computador em vez do `.`, que informa ao " +"pip para usar o diretório de trabalho atual." #: ../../tutorials/create-python-package.md:377 msgid "Look for pyospackage in your environment" -msgstr "" +msgstr "Procure pyospackage no seu ambiente" #: ../../tutorials/create-python-package.md:379 msgid "" "Once you have installed your package, you can view it in your current " -"environment. If you are using `venv` or `conda`, `pip` list will return a" -" list of packages in the current active environment." +"environment. If you are using `venv` or `conda`, `pip` list will return a " +"list of packages in the current active environment." msgstr "" +"Depois de instalar seu pacote, você pode visualizá-lo no seu ambiente " +"atual. Se estiver usando `venv` ou `conda`, `pip list` retornará uma lista " +"de pacotes no ambiente ativo atual." #: ../../tutorials/create-python-package.md:383 msgid "" -"Note that because `pyospackage` is installed in editable mode (`-e`), pip" -" will show you the directory path to your project's code" +"Note that because `pyospackage` is installed in editable mode (`-e`), pip " +"will show you the directory path to your project's code" msgstr "" +"Observe que, como `pyospackage` está instalado em modo editável (`-e`), o " +"pip mostrará o caminho do diretório para o código do seu projeto" #: ../../tutorials/create-python-package.md:411 msgid "Step 6: Test out your new package" -msgstr "" +msgstr "Passo 6: Teste seu novo pacote" #: ../../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 " +"After installing your package, type “python” at the command promptin " +"your chosen terminal to start a Python session in your activePython " "environment." msgstr "" +"Depois de instalar seu pacote, digite \"python\" no prompt de comando no " +"terminal escolhido para iniciar uma sessão Python no seu ambiente Python " +"ativo." #: ../../tutorials/create-python-package.md:416 msgid "You can now import your package and access the `add_numbers` function." -msgstr "" +msgstr "Agora você pode importar seu pacote e acessar a função `add_numbers`." #: ../../tutorials/create-python-package.md:428 msgid "Installing packages from GitHub" -msgstr "" +msgstr "Instalando pacotes do GitHub" #: ../../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 "" +"Se quiser compartilhar seu código sem publicar no PyPI, você sempre pode " +"instalar pacotes diretamente do GitHub usando a sintaxe:" #: ../../tutorials/create-python-package.md:437 msgid "To make your package GitHub installable, you can:" -msgstr "" +msgstr "Para tornar seu pacote instalável pelo GitHub, você pode:" #: ../../tutorials/create-python-package.md:439 msgid "Create a new GitHub repository" -msgstr "" +msgstr "Criar um novo repositório do GitHub" #: ../../tutorials/create-python-package.md:440 -msgid "" -"Push the contents of the project directory that you created above, to " -"GitHub" +msgid "Push the contents of the project directory that you created above, to GitHub" msgstr "" +"Fazer push do conteúdo do diretório do projeto que você criou acima para o " +"GitHub" #: ../../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 " +"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 " "branch_or_tag with your specific values." msgstr "" +"Por fim, instale o pacote do GitHub usando o comando acima. Ao usar " +"o comando acima, não se esqueça de substituir user, repo e " +"branch_or_tag pelos seus valores específicos." #: ../../tutorials/create-python-package.md:443 msgid "" -"For instance below you install the pyospackage from the main branch of " -"the pyOpenSci repository." +"For instance below you install the pyospackage from the main branch ofthe " +"pyOpenSci repository." msgstr "" +"Por exemplo, abaixo você instala o pyospackage da branch main do repositório " +"da pyOpenSci." #: ../../tutorials/create-python-package.md:446 msgid "`python -m pip install git+https://github.com/user/repo.git@branch_or_tag`" -msgstr "" +msgstr "`python -m pip install git+https://github.com/user/repo.git@branch_or_tag`" #: ../../tutorials/create-python-package.md:450 msgid "Congratulations! You created your first Python package" -msgstr "" +msgstr "Parabéns! Você criou seu primeiro pacote Python" #: ../../tutorials/create-python-package.md:452 msgid "" -"You have now created a Python package that you can install into any " -"Python environment." +"You have now created a Python package that you can install into any Python " +"environment." msgstr "" +"Agora você criou um pacote Python que pode instalar em qualquer " +"ambiente Python." #: ../../tutorials/create-python-package.md:457 msgid "" "Add a [README file](add-readme.md) and [LICENSE](add-license-coc.md) to " "your package" msgstr "" +"Adicione um [README file](add-readme.md) e [LICENSE](add-license-coc.md) ao " +"seu pacote" #: ../../tutorials/create-python-package.md:458 msgid "" "[Add more metadata to your `pyproject.toml`](pyproject-toml.md) file to " "support PyPI publication." msgstr "" +"[Adicione mais metadata ao seu `pyproject.toml`](pyproject-toml.md) para " +"suportar a publicação no PyPI." #: ../../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**." msgstr "" +"[Aprenda a fazer o build dos arquivos de distribuição do seu " +"pacote](publish-pypi) (**sdist** e **wheel**) e publicar no **test PyPI**." #: ../../tutorials/create-python-package.md:460 msgid "" -"Finally you will learn how to [publish to **conda-forge**](publish-conda-" -"forge) from **PyPI**." +"Finally you will learn how to [publish to " +"**conda-forge**](publish-conda-forge) from **PyPI**." msgstr "" +"Por fim, você aprenderá a [publicar no " +"**conda-forge**](publish-conda-forge) a partir do **PyPI**." #: ../../tutorials/create-python-package.md:464 msgid "About the Python package directory structure" -msgstr "" +msgstr "Sobre a estrutura de diretório de um pacote Python" #: ../../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 "" +"Para tornar seu código Python instalável, você precisa criar uma estrutura " +"de diretório específica com os seguintes elementos:" #: ../../tutorials/create-python-package.md:468 msgid "A `pyproject.toml` file." -msgstr "" +msgstr "Um arquivo `pyproject.toml`." #: ../../tutorials/create-python-package.md:469 msgid "A specific directory structure." -msgstr "" +msgstr "Uma estrutura de diretório específica." #: ../../tutorials/create-python-package.md:470 msgid "Some code." -msgstr "" +msgstr "Algum código." #: ../../tutorials/create-python-package.md:471 msgid "An `__init__.py` file in your code directory." -msgstr "" +msgstr "Um arquivo `__init__.py` no diretório do seu código." #: ../../tutorials/create-python-package.md:473 msgid "The directory structure you'll create in this lesson will look like this:" -msgstr "" +msgstr "A estrutura de diretório que você criará nesta lição ficará assim:" #: ../../tutorials/create-python-package.md:488 msgid "" From b34d86587ae62fa69e66f248e70f0024fae4e0ba Mon Sep 17 00:00:00 2001 From: Roberto Date: Tue, 9 Jun 2026 22:00:16 -0700 Subject: [PATCH 3/5] docs: Portuguese translation of the next 2,000 lines --- locales/pt/LC_MESSAGES/tutorials.po | 1368 +++++++++++++++++---------- 1 file changed, 888 insertions(+), 480 deletions(-) diff --git a/locales/pt/LC_MESSAGES/tutorials.po b/locales/pt/LC_MESSAGES/tutorials.po index 9a18e127..fad519b2 100644 --- a/locales/pt/LC_MESSAGES/tutorials.po +++ b/locales/pt/LC_MESSAGES/tutorials.po @@ -438,14 +438,9 @@ msgid "" "A `CODE_OF_CONDUCT` file is a {term}`Code of conduct` used to establish " "guidelines for how people in your community interact." msgstr "" -<<<<<<< HEAD -"Um arquivo CODE_OF_CONDUCT é um {term}`código de conduta` usado para estabelecer" -"diretrizes sobre como as pessoas em sua comunidade interagem." -======= "Um arquivo `CODE_OF_CONDUCT` é um {term}`Código de conduta` usado " "para estabelecer diretrizes sobre como as pessoas da sua comunidade " "interagem." ->>>>>>> 6913c90 (docs: Portuguese translation for the first 1,000 lines in tutorials.po) #: ../../tutorials/add-license-coc.md:152 msgid "" @@ -2031,11 +2026,15 @@ msgstr "A estrutura de diretório que você criará nesta lição ficará assim: #: ../../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" -" code, create package structure, add metadata to pyproject.toml and pip " +"Diagram showing the basic steps to creating an installable package. There " +"are 4 boxes with arrows pointing towards the right. The boxes read, your " +"code, create package structure, add metadata to pyproject.toml and pip " "install package." msgstr "" +"Diagrama mostrando os passos básicos para criar um pacote instalável. Há 4 " +"caixas com setas apontando para a direita. As caixas dizem: seu código, " +"criar estrutura do pacote, adicionar metadata ao pyproject.toml e pip " +"install pacote." #: ../../tutorials/create-python-package.md:490 msgid "" @@ -2043,152 +2042,201 @@ msgid "" "file structure), you can `pip install` your package into any Python " "environment on your computer." msgstr "" +"Depois que você tiver os itens básicos de um pacote Python (código, " +"metadata e uma estrutura de arquivos), você pode `pip install` seu pacote " +"em qualquer Python environment no seu computador." #: ../../tutorials/create-python-package.md:493 msgid "About the basic package directory structure" -msgstr "" +msgstr "Sobre a estrutura básica de diretório do pacote" #: ../../tutorials/create-python-package.md:495 msgid "Notice a few things about the above layout:" -msgstr "" +msgstr "Observe algumas coisas sobre o layout acima:" #: ../../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 " -"that you are running tests on the installed version of your " -"code](https://www.pyopensci.org/python-package-guide/package-structure-" -"code/python-package-structure.html#the-src-layout-and-testing)." -msgstr "" +"that you use `src` (short for **source code**) directory as it[ensures that " +"you are running tests on the installed version of " +"yourcode](https://www.pyopensci.org/python-package-guide/package-structure-c" +"ode/python-package-structure.html#the-src-layout-and-testing)." +msgstr "" +"O código do seu pacote fica dentro de um diretório " +"`src/packagename`. Sugerimos que você use o diretório `src` (abreviação de " +"**source code**) porque [garante que você está executando testes na versão " +"instalada do seu " +"código](https://www.pyopensci.org/python-package-guide/package-structure-cod" +"e/python-package-structure.html#the-src-layout-and-testing)." #: ../../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" -" will be the name for importing your package in Python code once " -"installed." +"`pyospackage`. Use the name of your package for that directory name. This " +"will be the name for importing your package in Python code once installed." msgstr "" +"Dentro do diretório `src`, você tem um diretório de pacote chamado " +"`pyospackage`. Use o nome do seu pacote para esse diretório. Este será o " +"nome para importar seu pacote no código Python depois de instalado." #: ../../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." +"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." msgstr "" +"No diretório do seu pacote, você tem um arquivo `__init__.py` e todos os " +"seus Python modules. Você aprenderá mais sobre o arquivo `__init__.py` " +"abaixo." #: ../../tutorials/create-python-package.md:500 msgid "The `pyproject.toml` file lives at the root directory of your package." -msgstr "" +msgstr "O arquivo `pyproject.toml` fica no diretório raiz do seu pacote." #: ../../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 " -"see that the GitHub / GitLab repository and the root directory name are " -"the same as the package name." +"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 see " +"that the GitHub / GitLab repository and the root directory name are the " +"same as the package name." msgstr "" +"O nome do diretório raiz do pacote é **pyospackage**, que é o nome " +"do pacote. Isso não é obrigatório, mas você verá com frequência que o " +"repositório do GitHub / GitLab e o nome do diretório raiz são os mesmos que o " +"nome do pacote." #: ../../tutorials/create-python-package.md:503 msgid "What is an `__init__.py` file?" -msgstr "" +msgstr "O que é um arquivo `__init__.py`?" #: ../../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" -" imported directly into Python. The `__init__.py` file does not need to " +"The `__init__.py` file tells Python that a directory should be treatedas a " +"Python package. As such, a directory with an `__init__.py`file can be " +"imported directly into Python. The `__init__.py` file doesnot need to " "contain any code in order for Python to recognize it; it can be empty." msgstr "" +"O arquivo `__init__.py` informa ao Python que um diretório deve ser tratado " +"como um pacote Python. Assim, um diretório com um arquivo `__init__.py` " +"pode ser importado diretamente no Python. O arquivo `__init__.py` não " +"precisa conter nenhum código para o Python reconhecê-lo; ele pode estar " +"vazio." #: ../../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 "" +"Por exemplo, seguindo o exemplo de estrutura de arquivos acima, que tem um " +"arquivo `__init__.py` dentro dele, você pode executar:" -#: ../../tutorials/create-python-package.md:515 -#: ../../tutorials/pyproject-toml.md:56 +#: ../../tutorials/create-python-package.md:515 ../../tutorials/pyproject-toml.md:56 msgid "What is a pyproject.toml file?" -msgstr "" +msgstr "O que é um arquivo pyproject.toml?" #: ../../tutorials/create-python-package.md:517 msgid "The **pyproject.toml** file is:" -msgstr "" +msgstr "O arquivo **pyproject.toml** é:" #: ../../tutorials/create-python-package.md:519 msgid "" -"Where you define your project's metadata (including its name, authors, " -"license, etc)" +"Where you define your project's metadata (including its name, " +"authors,license, etc)" msgstr "" +"Onde você define o metadata do seu projeto (incluindo nome, autores, " +"license, etc.)" #: ../../tutorials/create-python-package.md:520 msgid "Where you define dependencies (the packages that it depends on)" -msgstr "" +msgstr "Onde você define dependências (os pacotes dos quais ele depende)" #: ../../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-" -"distribution-files-sdist-wheel)." +"Used to specify and configure what build backend you want to use to [build " +"your " +"package](../package-structure-code/python-package-distribution-files-sdist-w" +"heel)." msgstr "" +"Usado para especificar e configurar qual build backend você quer usar para " +"[fazer o build do seu " +"pacote](../package-structure-code/python-package-distribution-files-sdist-wh" +"eel)." #: ../../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 " -"using tools such as pip. Note that the `pyproject.toml` file needs to " -"have a few basic items defined for the package to be installable " -"including:" +"package can be built and distributed as an installable Python package using " +"tools such as pip. Note that the `pyproject.toml` file needs to have a few " +"basic items defined for the package to be installable including:" msgstr "" +"Depois que os arquivos `__init__.py` e `pyproject.toml` forem adicionados, " +"seu pacote pode ser construído e distribuído como um pacote Python " +"instalável usando ferramentas como pip. Observe que o arquivo " +"`pyproject.toml` precisa ter alguns itens básicos definidos para o pacote " +"ser instalável, incluindo:" #: ../../tutorials/create-python-package.md:529 msgid "The `build-backend` that you want to use," -msgstr "" +msgstr "O `build-backend` que você quer usar," #: ../../tutorials/create-python-package.md:530 msgid "The project `name` and `version`." -msgstr "" +msgstr "O `name` e a `version` do projeto." #: ../../tutorials/create-python-package.md:532 msgid "Why the pyproject.toml file is important" -msgstr "" +msgstr "Por que o arquivo pyproject.toml é importante" #: ../../tutorials/create-python-package.md:535 msgid "" "The `pyproject.toml` file replaces some of the functionality of both the " -"`setup.py` file and `setup.cfg` files. If you try to pip install a " -"package with no `pyproject.toml`, you will get the following error:" +"`setup.py` file and `setup.cfg` files. If you try to pip install apackage " +"with no `pyproject.toml`, you will get the following error:" msgstr "" +"O arquivo `pyproject.toml` substitui parte da funcionalidade dos arquivos " +"`setup.py` e `setup.cfg`. Se você tentar pip install um pacote sem " +"`pyproject.toml`, receberá o seguinte erro:" #: ../../tutorials/create-python-package.md:545 msgid "" "If your project already has a `setup.py` file, Hatch can be used to " "automatically create a `pyproject.toml`." msgstr "" +"Se o seu projeto já tiver um arquivo `setup.py`, o Hatch pode ser usado " +"para criar automaticamente um `pyproject.toml`." #: ../../tutorials/create-python-package.md:546 msgid "" -"See [Using Hatch to Migrate setup.py to a pyproject.toml](setup-py-to-" -"pyproject-toml.md)" +"See [Using Hatch to Migrate setup.py to a " +"pyproject.toml](setup-py-to-pyproject-toml.md)" msgstr "" +"Veja [Using Hatch to Migrate setup.py to a " +"pyproject.toml](setup-py-to-pyproject-toml.md)" #: ../../tutorials/create-python-package.md:561 msgid "" -"Is it clear where to add commands? Bash vs. Python console Bash vs. Zsh " -"is different" +"Is it clear where to add commands? Bash vs. Python console Bash vs. Zsh is " +"different" msgstr "" +"Está claro onde adicionar comandos? Bash vs. console Python Bash vs. Zsh é " +"diferente" #: ../../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" -" valuable to a broad audience. This may not be a pervasive misconception " -"in Python, but a quick break-out with an explanation of what a package " -"can consist of would be helpful." +"ADD: note about what makes something \"package worthy\", with a " +"commonmisconception being that a package should be production-ready code " +"that's valuable to a broad audience. This may not be a pervasive " +"misconception in Python, but a quick break-out with an explanation of what " +"a package can consist of would be helpful." msgstr "" +"ADICIONAR: nota sobre o que torna algo \"package worthy\", com um equívoco " +"comum de que um pacote deve ser código pronto para produção valioso para um " +"público amplo. Isso pode não ser um equívoco generalizado em Python, mas um " +"break-out rápido com uma explicação do que um pacote pode consistir seria " +"útil." #: ../../tutorials/create-python-package.md:564 msgid "They can use a codespace to complete this lesson too." -msgstr "" +msgstr "Eles também podem usar um codespace para completar esta lição." #: ../../tutorials/create-python-package.md:568 msgid "" @@ -2196,192 +2244,250 @@ msgid "" "automate defining a package version using git tags in the version and " "release your package lesson." msgstr "" +"Quando esta lição existir, descomente esta admonition. Você aprenderá " +"a automatizar a definição da versão de um pacote usando git tags na lição de " +"versionar e lançar seu pacote." #: ../../tutorials/create-python-package.md:552 msgid "[Carpentries shell lesson](https://swcarpentry.github.io/shell-novice/)" -msgstr "" +msgstr "[Carpentries shell lesson](https://swcarpentry.github.io/shell-novice/)" #: ../../tutorials/create-python-package.md:556 msgid "[Numpy style docs](https://numpydoc.readthedocs.io/en/latest/format.html)" -msgstr "" +msgstr "[Numpy style docs](https://numpydoc.readthedocs.io/en/latest/format.html)" #: ../../tutorials/create-python-package.md:555 msgid "[Google docstring style](https://google.github.io/styleguide/pyguide.html)" -msgstr "" +msgstr "[Google docstring style](https://google.github.io/styleguide/pyguide.html)" #: ../../tutorials/create-python-package.md:557 msgid "[epydoc](https://epydoc.sourceforge.net/epytext.html)" -msgstr "" +msgstr "[epydoc](https://epydoc.sourceforge.net/epytext.html)" #: ../../tutorials/create-python-package.md:554 msgid "" "[Python module " "docs](https://docs.python.org/3/tutorial/modules.html#packages)" msgstr "" +"[Python module " +"docs](https://docs.python.org/3/tutorial/modules.html#packages)" #: ../../tutorials/develop-python-package-hatch.md:7 msgid "Use Hatch environments with your pure Python package" -msgstr "" +msgstr "Use ambientes Hatch com seu pacote puro Python" #: ../../tutorials/develop-python-package-hatch.md:13 msgid "" -"[In a previous lesson](create-pure-python-package), you learned how to " -"create a Python package using the pyOpenSci copier template. In this " -"lesson, you'll learn how to manage and use the Hatch environments set up " -"by de **What you need to complete this lesson**" +"[In a previous lesson](create-pure-python-package), you learned how " +"tocreate a Python package using the pyOpenSci copier template. In " +"thislesson, you'll learn how to manage and use the Hatch environments set " +"up by de **What you need to complete this lesson**" msgstr "" +"[Em uma lição anterior](create-pure-python-package), você aprendeu a criar " +"um pacote Python usando o copier template da pyOpenSci. Nesta lição, você " +"aprenderá a gerenciar e usar os ambientes Hatch configurados no **O que " +"você precisa para completar esta lição**" #: ../../tutorials/develop-python-package-hatch.md:16 msgid "" -"To complete this lesson, you will need a local Python environment and " -"shell on your computer. You will need to have created a package using " -"our pyOpenSci copier template. You should also have [Hatch installed" -"](get-to-know-hatch)." +"To complete this lesson, you will need a local Python environment and shell " +"on your computer. You will need to have created a package usingour " +"pyOpenSci copier template. You should also have [Hatch " +"installed](get-to-know-hatch)." msgstr "" +"Para completar esta lição, você precisará de um Python environment local e " +"shell no seu computador. Você precisará ter criado um pacote usando nosso " +"copier template da pyOpenSci. Você também deve ter " +"[Hatch instalado](get-to-know-hatch)." #: ../../tutorials/develop-python-package-hatch.md:20 msgid "" "If you are using Windows or are not familiar with Shell, you may want to " -"check out the [Carpentries shell lesson](https://swcarpentry.github.io" -"/shell-novice/). Windows users will likely need to configure a tool such " -"as [GitBash](https://gitforwindows.org/) for any Shell and git-related " -"steps." +"check out the [Carpentries shell " +"lesson](https://swcarpentry.github.io/shell-novice/). Windows users will " +"likely need to configure a tool such as " +"[GitBash](https://gitforwindows.org/) for any Shell and git-related steps." msgstr "" +"Se estiver usando Windows ou não estiver familiarizado com Shell, " +"pode querer conferir a [Carpentries shell " +"lesson](https://swcarpentry.github.io/shell-novice/). Usuários do Windows " +"provavelmente precisarão configurar uma ferramenta como " +"[GitBash](https://gitforwindows.org/) para qualquer passo relacionado a " +"Shell e git." #: ../../tutorials/develop-python-package-hatch.md:23 msgid "" -"Welcome to your shiny new package! This page will help you get started " -"with using [Hatch](get-to-know-hatch) to run tests, build and check your " +"Welcome to your shiny new package! This page will help you get startedwith " +"using [Hatch](get-to-know-hatch) to run tests, build and check your " "package, and build your documentation." msgstr "" +"Boas-vindas ao seu novo pacote! Esta página ajudará você a começar a usar " +"[Hatch](get-to-know-hatch) para executar testes, fazer o build e verificar " +"seu pacote e construir sua documentação." #: ../../tutorials/develop-python-package-hatch.md:27 #, python-brace-format msgid "" -"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:" +"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 "" +"Para começar, dê uma olhada no arquivo [pyproject.toml](pyproject-toml) no " +"diretório do seu pacote. Este arquivo contém a configuração do seu pacote e " +"é escrito no formato {term}`TOML`. Aqui vai o TL&DR:" #: ../../tutorials/develop-python-package-hatch.md:31 msgid "Each `[]` section in the toml file is called a table." -msgstr "" +msgstr "Cada seção `[]` no arquivo toml é chamada de tabela." #: ../../tutorials/develop-python-package-hatch.md:32 msgid "You can nest tables with double brackets like this`[[]]`" -msgstr "" +msgstr "Você pode aninhar tabelas com colchetes duplos assim`[[]]`" #: ../../tutorials/develop-python-package-hatch.md:33 -msgid "" -"Tables contain information about a certain thing that you want to " -"configure." -msgstr "" +msgid "Tables contain information about a certain thing that you want to configure." +msgstr "Tabelas contêm informações sobre algo que você quer configurar." #: ../../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." +"You can configure Hatch to use UV by default for environment management. UV " +"is a package manager built in Rust. It is fast and willsignificantly speed " +"up environment creation." msgstr "" +"Você pode configurar o Hatch para usar UV por padrão para gerenciamento de " +"ambiente. UV é um gerenciador de pacotes construído em Rust. É rápido e " +"acelerará significativamente a criação de ambientes." #: ../../tutorials/develop-python-package-hatch.md:38 msgid "" -"To use UV with Hatch, configure Hatch in the \"tools\" section of your " -"`pyproject.toml` file." +"To use UV with Hatch, configure Hatch in the \"tools\" section of " +"your`pyproject.toml` file." msgstr "" +"Para usar UV com Hatch, configure o Hatch na seção \"tools\" do seu arquivo " +"`pyproject.toml`." #: ../../tutorials/develop-python-package-hatch.md:46 msgid "" -"Using Hatch for developing, building, and maintaining your pure Python " -"package" -msgstr "" +"Using Hatch for developing, building, and maintaining your pure " +"Pythonpackage" +msgstr "Usando Hatch para desenvolver, fazer o build, e manter seu pacote Python puro" #: ../../tutorials/develop-python-package-hatch.md:48 #, python-brace-format msgid "" "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:" +"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 "" +"No template de pacote Python da pyOpenSci, configuramos definições " +"de{term}`Hatch environment`. Você notará na parte inferior do arquivo uma " +"seção [hatch environment](https://hatch.pypa.io/1.13/environment/), que se " +"parece com isto:" #: ../../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." +"Hatch allows you to configure and run environments and scripts similarto a " +"workflow tool like tox or nox." msgstr "" +"Hatch permite que você configure e execute ambientes e scripts de forma " +"semelhante a uma ferramenta de workflow como tox ou nox." #: ../../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 "" +"Hatch usa `venv` por padrão para gerenciar ambientes. Porém, você pode " +"configurá-lo para usar outras ferramentas de ambiente, como conda ou " +"mamba." #: ../../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 "" +"[Leia a documentação do Hatch para saber mais sobre ambientes. " +"](https://hatch.pypa.io/1.13/tutorials/environment/basic-usage/)" #: ../../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:" +"Below is the Hatch environment used to build and test your package. Anytime " +"you see: `tool.hatch.envs.test`, it tells Hatch:" msgstr "" +"Abaixo está o ambiente Hatch usado para fazer o build e testar seu " +"pacote. Sempre que você vir: `tool.hatch.envs.test`, isso informa ao Hatch:" #: ../../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.\"" +"\"Hey, Hatch, this is the definition for an environment.`test` is the name " +"of the environment that I want you to create.\"" msgstr "" +"\"Ei, Hatch, esta é a definição de um ambiente. `test` é o nome do " +"ambiente que quero que você crie.\"" #: ../../tutorials/develop-python-package-hatch.md:73 msgid "So `tool.hatch.envs.build` will create an environment called `build`." -msgstr "" +msgstr "Então `tool.hatch.envs.build` criará um ambiente chamado `build`." #: ../../tutorials/develop-python-package-hatch.md:75 msgid "" -"Below the environment \"declaration,\" you can see the definition of what" -" should be in that environment." +"Below the environment \"declaration,\" you can see the definition of what " +"should be in that environment." msgstr "" +"Abaixo da \"declaração\" do ambiente, você pode ver a definição do que " +"deve estar nesse ambiente." #: ../../tutorials/develop-python-package-hatch.md:77 msgid "A Hatch environment to build your package" -msgstr "" +msgstr "Um ambiente Hatch para fazer o build do seu pacote" #: ../../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](pyproject-toml) file. It is set up to build " -"your package's {term}`Distribution files` ({term}`Source distribution " +"Below is a Hatch environment definition that you will find in your " +"newproject's [pyproject.toml](pyproject-toml) file. It is set up to " +"buildyour package's {term}`Distribution files` ({term}`Source distribution " "(sdist)` and {term}`Wheel (.whl)`)." msgstr "" +"Abaixo está uma definição de ambiente Hatch que você encontrará no " +"arquivo [pyproject.toml](pyproject-toml) do seu novo projeto. Ela " +"está configurada para fazer o build dos {term}`arquivos de " +"distribuição` do seu pacote ({term}`distribuição fonte " +"(sdist)` e {term}`Wheel (.whl)`)." #: ../../tutorials/develop-python-package-hatch.md:84 #, python-brace-format msgid "" -"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)." +"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 "" +"Observe que a definição do ambiente declara duas {term}`dependências " +"`: `pip` e `twine`, que o ambiente precisa para executar " +"com sucesso. Esta declaração é semelhante a declarar dependencies para o " +"seu pacote no topo do seu [pyproject.toml](pyproject-toml)." #: ../../tutorials/develop-python-package-hatch.md:99 msgid "Hatch will install your package in editable mode by default" -msgstr "" +msgstr "Hatch instalará seu pacote em modo editável por padrão" #: ../../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 " +"Notice the `detached = True` flag at the bottom of the environment. " +"Bydefault, hatch will install your package in editable mode into any " "environment it creates. `detached=True` tells it not to install your " "package into the environment." msgstr "" +"Observe a flag `detached = True` na parte inferior do ambiente. " +"Por padrão, o Hatch instalará seu pacote em modo editável em qualquer " +"ambiente que criar. `detached=True` informa para não instalar seu pacote " +"no ambiente." #: ../../tutorials/develop-python-package-hatch.md:104 msgid "Hatch scripts" -msgstr "" +msgstr "Hatch scripts" #: ../../tutorials/develop-python-package-hatch.md:106 #, python-brace-format @@ -2389,103 +2495,121 @@ msgid "" "Hatch supports defining {term}`Script (Hatch)` commands that run in " "specific Hatch environments." msgstr "" +"Hatch suporta a definição de comandos {term}`Script (Hatch)` que executam " +"em ambientes Hatch específicos." #: ../../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." +"create as a virtual environment (venv). Because `detached = True`in that " +"environment, Hatch won't install your package into it." msgstr "" +"Acima, você definiu um novo ambiente chamado 'build' que o Hatch criará " +"como um ambiente virtual (venv). Como `detached = True` nesse " +"ambiente, o Hatch não instalará seu pacote nele." #: ../../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." +"You can then use that environment to run \"scripts\". The definition below " +"tells Hatch to run the following scripts in the build environment." msgstr "" +"Você pode então usar esse ambiente para executar \"scripts\". A definição " +"abaixo informa ao Hatch para executar os seguintes scripts no ambiente " +"build." #: ../../tutorials/develop-python-package-hatch.md:113 msgid "`[tool.hatch.envs.build.scripts]`" -msgstr "" +msgstr "`[tool.hatch.envs.build.scripts]`" #: ../../tutorials/develop-python-package-hatch.md:115 msgid "You define this `scripts` to run using the following syntax, where:" -msgstr "" +msgstr "Você define este `scripts` para executar usando a seguinte sintaxe, onde:" #: ../../tutorials/develop-python-package-hatch.md:117 msgid "`tool.hatch`: Alerts Hatch that this table is for Hatch to use" -msgstr "" +msgstr "`tool.hatch`: Alerta o Hatch de que esta tabela é para o Hatch usar" #: ../../tutorials/develop-python-package-hatch.md:118 msgid "`envs.build`: Use the defined build environment." -msgstr "" +msgstr "`envs.build`: Use o ambiente build definido." #: ../../tutorials/develop-python-package-hatch.md:119 msgid "" -"`scripts`: Define what scripts to run. In this case, Hatch will run shell" -" scripts." +"`scripts`: Define what scripts to run. In this case, Hatch will run shell " +"scripts." msgstr "" +"`scripts`: Defina quais scripts executar. Neste caso, o Hatch executará " +"shell scripts." #: ../../tutorials/develop-python-package-hatch.md:122 -msgid "" -"Below is the `build.scripts` table that defines 3 shell commands to be " -"run:" +msgid "Below is the `build.scripts` table that defines 3 shell commands to berun:" msgstr "" +"Abaixo está a tabela `build.scripts` que define 3 comandos shell a serem " +"executados:" #: ../../tutorials/develop-python-package-hatch.md:124 msgid "`pip check` # verifies your dependencies" -msgstr "" +msgstr "`pip check` # verifica suas dependencies" #: ../../tutorials/develop-python-package-hatch.md:125 msgid "`hatch build --clean` # build your packages distribution files." msgstr "" +"`hatch build --clean` # faz o build dos arquivos de distribuição do seu " +"pacote." #: ../../tutorials/develop-python-package-hatch.md:126 msgid "" -"`twine check dist/*` # use twine to check that your package's sdist " -"(source distribution) is ok." +"`twine check dist/*` # use twine to check that your package's sdist (source " +"distribution) is ok." msgstr "" +"`twine check dist/*` # usa twine para verificar se o sdist (source " +"distribution) do seu pacote está ok." #: ../../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." +"Hatch, by default, will install your package in editable mode into " +"anyvirtual environment (venv) that it creates. If `detached=True` is " +"set,then it will skip that step." msgstr "" +"Hatch, por padrão, instalará seu pacote em modo editável em qualquer " +"ambiente virtual (venv) que criar. Se `detached=True` estiver definido, " +"ele pulará essa etapa." #: ../../tutorials/develop-python-package-hatch.md:143 msgid "Running the build script" -msgstr "" +msgstr "Executando o build script" #: ../../tutorials/develop-python-package-hatch.md:145 msgid "You can run the build script and build your package like this:" -msgstr "" +msgstr "Você pode executar o build script e fazer o build do seu pacote assim:" #: ../../tutorials/develop-python-package-hatch.md:147 msgid "`hatch run build:check`" -msgstr "" +msgstr "`hatch run build:check`" #: ../../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." +"This step updates the build environment and then builds and checks " +"theoutput distributions of your package." msgstr "" +"Esta etapa atualiza o ambiente build e então faz o build e verifica as " +"distribuições de saída do seu pacote." #: ../../tutorials/develop-python-package-hatch.md:151 msgid "You can enter the build environment in your shell to check it out:" -msgstr "" +msgstr "Você pode entrar no ambiente build no seu shell para conferir:" #: ../../tutorials/develop-python-package-hatch.md:157 msgid "If you run `pip list` in the environment, twine will be there:" -msgstr "" +msgstr "Se executar `pip list` no ambiente, o twine estará lá:" -#: ../../tutorials/develop-python-package-hatch.md:163 -#: ../../tutorials/develop-python-package-hatch.md:221 +#: ../../tutorials/develop-python-package-hatch.md:163 ../../tutorials/develop-python-package-hatch.md:221 msgid "To leave the environment use:" -msgstr "" +msgstr "Para sair do ambiente, use:" #: ../../tutorials/develop-python-package-hatch.md:169 msgid "Hatch, testing, and matrix environments" -msgstr "" +msgstr "Hatch, testes, e ambientes matriz" #: ../../tutorials/develop-python-package-hatch.md:171 msgid "" @@ -2493,136 +2617,167 @@ msgid "" "expect your users to be using. In this section, you'll explore the test " "environment setup in the pyOpenSci template package." msgstr "" +"É sempre útil executar seus testes nas versões do Python que você espera " +"que seus usuários estejam usando. Nesta seção, você explorará a configuração " +"do ambiente de teste no pacote template da pyOpenSci." #: ../../tutorials/develop-python-package-hatch.md:173 msgid "Below, you see the Hatch environment test table." -msgstr "" +msgstr "Abaixo, você vê a tabela do ambiente Hatch test." #: ../../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)." +"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 "" +"Semelhante ao ambiente build acima, o ambiente abaixo define as " +"dependencies que o Hatch precisa instalar no ambiente de teste " +"(necessárias para executar seus testes)." #: ../../tutorials/develop-python-package-hatch.md:189 msgid "Your test environment has a matrix associated with it" -msgstr "" +msgstr "Seu ambiente de teste tem uma matriz associada a ele" #: ../../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." +"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 "" +"Se o ambiente tiver uma matriz associada, isso informa ao Hatch para " +"executar os testes em diferentes versões do Python. Abaixo, você está " +"executando testes nas versões 3.10 a 3.13." #: ../../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 " -"install Hatch and also when you declare a matrix environment like the one" -" below" +"UV](https://docs.astral.sh/uv/guides/install-python/) both when you install " +"Hatch and also when you declare a matrix environment like the one below" msgstr "" +"Hatch, por padrão, instalará Python [usando " +"UV](https://docs.astral.sh/uv/guides/install-python/) tanto quando você " +"instala o Hatch quanto quando declara um ambiente matriz como o abaixo" #: ../../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 " -"choose from, you need to select the environment with the Python version " -"you want to use." +"choose from, you need to select the environment with the Python version you " +"want to use." msgstr "" +"No seu projeto, se executar `hatch shell test`, verá a saída abaixo. Isso " +"significa que, como há uma matriz de versões do Python para escolher, você " +"precisa selecionar o ambiente com a versão do Python que deseja usar." #: ../../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 "" +"Escolha o ambiente de teste Python que deseja usar e entre nele, assim " +"(isso abrirá o Python 3.13):" #: ../../tutorials/develop-python-package-hatch.md:227 msgid "Hatch scripts for tests" -msgstr "" +msgstr "Hatch scripts para testes" #: ../../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." +"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 "" +"Na mesma seção de testes, você verá uma seção " +"`tool.hatch.envs.test.scripts`. Semelhante ao que você viu acima com as " +"etapas de build, é aqui que o \"script\" para executar seus testes é definido." #: ../../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 "" +"Observe que abaixo o script tem um script chamado `run`. E esse " +"scriptexecuta pytest com um conjunto de argumentos, incluindo geração de " +"code coverage." #: ../../tutorials/develop-python-package-hatch.md:239 msgid "To run this script in your terminal, use the syntax:" -msgstr "" +msgstr "Para executar este script no seu terminal, use a sintaxe:" #: ../../tutorials/develop-python-package-hatch.md:241 msgid "`hatch run test:run`" -msgstr "" +msgstr "`hatch run test:run`" #: ../../tutorials/develop-python-package-hatch.md:243 msgid "Reminder" -msgstr "" +msgstr "Lembrete" #: ../../tutorials/develop-python-package-hatch.md:246 -msgid "" -"`hatch run`: this calls hatch and tells it that it will be running a " -"command" -msgstr "" +msgid "`hatch run`: this calls hatch and tells it that it will be running a command" +msgstr "`hatch run`: isso chama o Hatch e informa que ele executará um comando" #: ../../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`" +"`test:run` defines the environment you want it to run (`test`) in thiscase, " +"and the script is defined as `run`" msgstr "" +"`test:run` define o ambiente em que você quer que execute (`test`) neste " +"caso, e o script é definido como `run`" #: ../../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 " -"Python environment. In this case, since there are four Python versions in" -" the environment, your tests will be run four times, once in each Python " -"version listed in the matrix table." +"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 Python " +"environment. In this case, since there are four Python versions in the " +"environment, your tests will be run four times, once in each Python version " +"listed in the matrix table." msgstr "" +"Se você tiver uma matriz configurada para testes, ela instalará a versão " +"necessária do Python usando UV e executará seus testes em cada versão do " +"ambiente Python. Neste caso, como há quatro versões do Python no " +"ambiente, seus testes serão executados quatro vezes, uma em cada versão " +"do Python listada na tabela matrix." #: ../../tutorials/develop-python-package-hatch.md:280 msgid "Build your documentation with Hatch environments" -msgstr "" +msgstr "Construa sua documentação com um ambiente Hatch" #: ../../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:" +"Finally, you can build and serve your documentation using hatch. To build a " +"static HTML version of the docs run:" msgstr "" +"Por fim, você pode fazer o build e servir sua documentação usando o Hatch. " +"Para gerar uma versão HTML estática da documentação, execute:" #: ../../tutorials/develop-python-package-hatch.md:285 msgid "`hatch run docs:build`" -msgstr "" +msgstr "`hatch run docs:build`" #: ../../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 "" +"Para executar um servidor local com a documentação atualizada conforme você " +"modifica seus arquivos markdown, execute:" #: ../../tutorials/develop-python-package-hatch.md:289 msgid "`hatch run docs:serve`" -msgstr "" +msgstr "`hatch run docs:serve`" #: ../../tutorials/develop-python-package-hatch.md:291 msgid "To stop serving the docs use:" -msgstr "" +msgstr "Para parar de servir a documentação, use:" #: ../../tutorials/develop-python-package-hatch.md:293 msgid "mac: ctrl + c windows:" -msgstr "" +msgstr "mac: ctrl + c windows:" #: ../../tutorials/get-to-know-hatch.md:6 msgid "Get to Know Hatch" -msgstr "" +msgstr "Conheça o Hatch" #: ../../tutorials/get-to-know-hatch.md:8 msgid "" @@ -2630,13 +2785,20 @@ msgid "" "packaging tools](/package-structure-code/python-package-build-tools) out " "there, we have selected Hatch because:" msgstr "" +"Nossos tutoriais de empacotamento Python usam o Hatch. Embora existam " +"[muitas ferramentas excelentes de " +"empacotamento](/package-structure-code/python-package-build-tools), " +"escolhemos o Hatch porque:" #: ../../tutorials/get-to-know-hatch.md:13 msgid "" -"It is an end-to-end tool that supports most of the steps required to " -"create a quality Python package. Beginners will have fewer tools to learn" -" if they use Hatch." +"It is an end-to-end tool that supports most of the steps required to create " +"a quality Python package. Beginners will have fewer tools to learn if they " +"use Hatch." msgstr "" +"É uma ferramenta ponta a ponta que suporta a maioria das etapas necessárias " +"para criar um pacote Python de qualidade. Iniciantes terão menos ferramentas " +"para aprender se usarem o Hatch." #: ../../tutorials/get-to-know-hatch.md:16 #, python-brace-format @@ -2644,326 +2806,400 @@ msgid "" "It supports different {term}`Build backend` options if you ever need to " "compile code in other languages." msgstr "" +"Ele suporta diferentes opções de {term}`backend de construção ` caso você precise compilar código em outras linguagens." #: ../../tutorials/get-to-know-hatch.md:18 msgid "" "As a community, pyOpenSci has decided that Hatch is a user-friendly tool " "that supports many different scientific Python use cases." msgstr "" +"Como comunidade, a pyOpenSci decidiu que o Hatch é uma ferramenta amigável " +"que suporta muitos casos de uso diferentes do Python científico." #: ../../tutorials/get-to-know-hatch.md:21 msgid "" -"In this tutorial, you will install and get to know Hatch a bit more " -"before starting to use it." +"In this tutorial, you will install and get to know Hatch a bit more before " +"starting to use it." msgstr "" +"Neste tutorial, você instalará e conhecerá um pouco mais o Hatch antes de " +"começar a usá-lo." #: ../../tutorials/get-to-know-hatch.md:24 msgid "You need two things to successfully complete this tutorial:" -msgstr "" +msgstr "Você precisa de duas coisas para concluir este tutorial com sucesso:" #: ../../tutorials/get-to-know-hatch.md:26 msgid "You need Python installed." -msgstr "" +msgstr "Você precisa ter o Python instalado." #: ../../tutorials/get-to-know-hatch.md:27 msgid "You need Hatch installed." -msgstr "" +msgstr "Você precisa ter o Hatch instalado." #: ../../tutorials/get-to-know-hatch.md:30 msgid "" -"If you don't already have Python installed on your computer, Hatch will " -"do it for you when you install Hatch." +"If you don't already have Python installed on your computer, Hatch will do " +"it for you when you install Hatch." msgstr "" +"Se você ainda não tiver o Python instalado no seu computador, o Hatch fará " +"isso por você quando você instalar o Hatch." #: ../../tutorials/get-to-know-hatch.md:34 msgid "Install Hatch" -msgstr "" +msgstr "Instalar o Hatch" #: ../../tutorials/get-to-know-hatch.md:36 msgid "" "To begin, follow the operating-system-specific instructions below to " "install Hatch." msgstr "" +"Para começar, siga as instruções específicas do seu sistema operacional " +"abaixo para instalar o Hatch." #: ../../tutorials/get-to-know-hatch.md msgid "MAC" -msgstr "" +msgstr "MAC" #: ../../tutorials/get-to-know-hatch.md:43 msgid "" "Follow the instructions " "[here](https://hatch.pypa.io/latest/install/#installers)." -msgstr "" +msgstr "Siga as instruções [aqui](https://hatch.pypa.io/latest/install/#installers)." #: ../../tutorials/get-to-know-hatch.md:45 msgid "" -"Download the latest GUI installer for MAC [hatch-" -"universal.pkg](https://github.com/pypa/hatch/releases/latest/download" +"Download the latest GUI installer for MAC " +"[hatch-universal.pkg](https://github.com/pypa/hatch/releases/latest/download" "/hatch-universal.pkg)." msgstr "" +"Baixe o instalador GUI mais recente para MAC " +"[hatch-universal.pkg](https://github.com/pypa/hatch/releases/latest/download" +"/hatch-universal.pkg)." #: ../../tutorials/get-to-know-hatch.md:46 msgid "Run the installer and follow the setup instructions." -msgstr "" +msgstr "Execute o instalador e siga as instruções de instalação." #: ../../tutorials/get-to-know-hatch.md:47 msgid "If your terminal is open, then restart it." -msgstr "" +msgstr "Se o seu terminal estiver aberto, reinicie-o." #: ../../tutorials/get-to-know-hatch.md msgid "Windows" -msgstr "" +msgstr "Windows" #: ../../tutorials/get-to-know-hatch.md:53 msgid "" "In your browser, download the correct `.msi` file for your system: " -"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch-x64.msi)" +"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch" +"-x64.msi)" msgstr "" +"No seu navegador, baixe o arquivo `.msi` correto para o seu sistema: " +"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch" +"-x64.msi)" #: ../../tutorials/get-to-know-hatch.md:55 msgid "Run your downloaded installer file and follow the on-screen instructions." -msgstr "" +msgstr "Execute o arquivo instalador baixado e siga as instruções na tela." #: ../../tutorials/get-to-know-hatch.md msgid "Linux" -msgstr "" +msgstr "Linux" #: ../../tutorials/get-to-know-hatch.md:61 msgid "" -"We suggest that you install Hatch using pipx on Linux. however, if you " -"prefer another method, check out the [Hatch installation " +"We suggest that you install Hatch using pipx on Linux. however, if " +"youprefer another method, check out the [Hatch installation " "documentation](https://hatch.pypa.io/latest/install/) for other methods." msgstr "" +"Sugerimos que você instale o Hatch usando pipx no Linux. No entanto, se " +"preferir outro método, consulte a [documentação de instalação do " +"Hatch](https://hatch.pypa.io/latest/install/) para outras opções." #: ../../tutorials/get-to-know-hatch.md:75 #, python-brace-format msgid "" "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 " +"[conda](https://hatch.pypa.io/latest/install/#conda). We encourage youto " +"follow the instructions above because we have found that the Hatch " "installers for Windows and Mac are the easiest and most efficient." msgstr "" +"O Hatch também pode ser instalado diretamente usando {term}`pip` ou " +"[conda](https://hatch.pypa.io/latest/install/#conda). Recomendamos que você " +"siga as instruções acima, pois descobrimos que os instaladores do Hatch para " +"Windows e Mac são os mais fáceis e eficientes." #: ../../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 "" +"Nossos usuários Linux tiveram sucesso instalando o Hatch com pipx se já " +"usam apt install." #: ../../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 " -"that Hatch is available across all of your Python environments on your " -"computer." +"ensure that you have Hatch installed globally. A global install means that " +"Hatch is available across all of your Python environments on yourcomputer." msgstr "" +"Ambas as abordagens (usar um instalador gráfico no Windows/Mac e " +"pipx) garantem que você tenha o Hatch instalado globalmente. Uma instalação " +"global significa que o Hatch fica disponível em todos os seus ambientes " +"Python no computador." #: ../../tutorials/get-to-know-hatch.md:88 msgid "Check that hatch installed correctly" -msgstr "" +msgstr "Verifique se o Hatch foi instalado corretamente" #: ../../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 " +"Once you have completed the installation instructions above, you can open " +"your terminal, and make sure that Hatch installed correctly usingthe " "command below:" msgstr "" +"Depois de concluir as instruções de instalação acima, abra o terminal e " +"verifique se o Hatch foi instalado corretamente usando o comando abaixo:" #: ../../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 "" +"*Observe que o número de versão exibido por `hatch --version` provavelmente " +"será diferente do mostrado acima neste tutorial.*" #: ../../tutorials/get-to-know-hatch.md:101 msgid "Configure Hatch" -msgstr "" +msgstr "Configurar o Hatch" #: ../../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." -" While this step is not required, we suggest that you do it." +"includes setting the default name and setup for every package youcreate. " +"While this step is not required, we suggest that you do it." msgstr "" +"Depois de instalar o Hatch, você pode personalizar sua configuração. Isso " +"inclui definir o nome padrão e a configuração de cada pacote que você criar. " +"Embora esta etapa não seja obrigatória, recomendamos que você a faça." #: ../../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/)." msgstr "" +"O Hatch armazena sua configuração em um [arquivo " +"`config.toml`](https://hatch.pypa.io/latest/config/project-templates/)." #: ../../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 " -"using it for the first time." +"might be easier to look at and update it in a text editor if you are using " +"it for the first time." msgstr "" +"Embora você possa atualizar o arquivo `config.toml` pela linha de comando, " +"pode ser mais fácil visualizá-lo e editá-lo em um editor de texto se for a " +"primeira vez que o usa." #: ../../tutorials/get-to-know-hatch.md:113 msgid "Step 1: Open and Edit Your `config.toml` File" -msgstr "" +msgstr "Etapa 1: Abrir e editar seu arquivo `config.toml`" #: ../../tutorials/get-to-know-hatch.md:115 msgid "" -"To open the config file in your file browser, run the following command " -"in your shell:" +"To open the config file in your file browser, run the following command in " +"your shell:" msgstr "" +"Para abrir o arquivo de configuração no explorador de arquivos, execute o " +"seguinte comando no shell:" #: ../../tutorials/get-to-know-hatch.md:118 msgid "`hatch config explore`" -msgstr "" +msgstr "`hatch config explore`" #: ../../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." +"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 "" +"Isso abrirá uma janela de diretório que permite clicar duas vezes no " +"arquivo e abri-lo no seu editor de texto favorito." #: ../../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:" +"You can also retrieve the location of the Hatch config file by runningthe " +"following command in your shell:" msgstr "" +"Você também pode obter a localização do arquivo de configuração do Hatch " +"executando o seguinte comando no shell:" #: ../../tutorials/get-to-know-hatch.md:131 msgid "Step 2 - update your email and name" -msgstr "" +msgstr "Etapa 2 - atualize seu e-mail e nome" #: ../../tutorials/get-to-know-hatch.md:133 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](pyproject-toml) metadata files that you create using " -"Hatch." +"[pyproject.toml](pyproject-toml) metadata files that you create using Hatch." msgstr "" +"Com o arquivo aberto, atualize a tabela [template] do arquivo `config.toml` " +"com seu nome e e-mail. Essas informações serão usadas em quaisquer arquivos " +"de metadata [pyproject.toml](pyproject-toml) que você criar usando o Hatch." #: ../../tutorials/get-to-know-hatch.md:144 msgid "Step 3" -msgstr "" +msgstr "Etapa 3" #: ../../tutorials/get-to-know-hatch.md:146 msgid "Next, set tests to false in the `[template.plugins.default]` table." -msgstr "" +msgstr "Em seguida, defina `tests` como `false` na tabela `[template.plugins.default]`." #: ../../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 " -"to use this feature in this beginner friendly tutorial series but we will" -" introduce it in later tutorials." +"While tests are important, setting the tests configuration in Hatch " +"to`true` will create a more complex `pyproject.toml` file. You won't need " +"to use this feature in this beginner friendly tutorial series butwe will " +"introduce it in later tutorials." msgstr "" +"Embora testes sejam importantes, definir a configuração de `tests` no Hatch " +"como `true` criará um arquivo `pyproject.toml` mais complexo. Você não " +"precisará usar esse recurso nesta série de tutoriais para iniciantes, mas o " +"apresentaremos em tutoriais posteriores." #: ../../tutorials/get-to-know-hatch.md:153 msgid "Your `config.toml` file should look something like the one below." -msgstr "" +msgstr "Seu arquivo `config.toml` deve ficar parecido com o exemplo abaixo." #: ../../tutorials/get-to-know-hatch.md:191 msgid "" -"Also notice that the default license option is MIT. While we will discuss" -" license in more detail in a later lesson, the MIT license is the " +"Also notice that the default license option is MIT. While we will discuss " +"license in more detail in a later lesson, the MIT license is the " "recommended permissive license from " -"[choosealicense.com](https://choosealicense.com/) and as such we will use" -" it for this tutorial series." +"[choosealicense.com](https://choosealicense.com/) and as such we will use " +"it for this tutorial series." msgstr "" +"Observe também que a opção de `license` padrão é MIT. Embora abordemos " +"`license` com mais detalhes em uma lição posterior, a `license` MIT é a " +"`permissive license` recomendada por " +"[choosealicense.com](https://choosealicense.com/) e, por isso, a usaremos " +"nesta série de tutoriais." #: ../../tutorials/get-to-know-hatch.md:197 msgid "You are of course welcome to select another license." -msgstr "" +msgstr "Você pode, claro, escolher outra `license`." #: ../../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" +"I think we'd need the SPDX license options here if they want to chose bsd-3 " +"for instance" msgstr "" +"Acho que precisaríamos das opções de `license` SPDX aqui se quisessem " +"escolher bsd-3, por exemplo" #: ../../tutorials/get-to-know-hatch.md:203 msgid "Step 4: Close the config file and run `hatch config show`" -msgstr "" +msgstr "Etapa 4: Feche o arquivo de configuração e execute `hatch config show`" #: ../../tutorials/get-to-know-hatch.md:205 msgid "" -"Once you have completed the steps above run the following command in your" -" shell." -msgstr "" +"Once you have completed the steps above run the following command in your " +"shell." +msgstr "Depois de concluir as etapas acima, execute o seguinte comando no shell." #: ../../tutorials/get-to-know-hatch.md:207 msgid "`hatch config show`" -msgstr "" +msgstr "`hatch config show`" #: ../../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 " -"is set. Also make sure that `tests=false`." +"`hatch config show` will print out the contents of your `config.toml` file " +"in your shell. Look at the values and ensure that your name, email is set. " +"Also make sure that `tests=false`." msgstr "" +"`hatch config show` exibirá o conteúdo do seu arquivo `config.toml` " +"no shell. Verifique os valores e confirme que seu nome e e-mail estão " +"definidos. Certifique-se também de que `tests=false`." #: ../../tutorials/get-to-know-hatch.md:213 msgid "Hatch features" -msgstr "" +msgstr "Recursos do Hatch" #: ../../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 "" +"O Hatch oferece um conjunto de recursos que facilitam a criação, publicação " +"e manutenção do seu pacote Python." #: ../../tutorials/get-to-know-hatch.md:218 msgid "Comparison to other tools" -msgstr "" +msgstr "Comparação com outras ferramentas" #: ../../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-" -"features)" +"[We compared Hatch to several of the other popular packaging tools in the " +"ecosystem including flit, pdm and poetry. Learn more here](package-features)" msgstr "" +"[Comparamos o Hatch a várias outras ferramentas populares de empacotamento " +"do ecossistema, incluindo flit, pdm e poetry. Saiba " +"mais aqui](package-features)" #: ../../tutorials/get-to-know-hatch.md:223 msgid "[More on Hatch here](hatch)" -msgstr "" +msgstr "[Mais sobre o Hatch aqui](hatch)" #: ../../tutorials/get-to-know-hatch.md:225 msgid "A few features that Hatch offers" -msgstr "" +msgstr "Alguns recursos que o Hatch oferece" #: ../../tutorials/get-to-know-hatch.md:227 msgid "" -"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " +"It will convert metadata stored in a `setup.py` or `setup.cfg` file toa " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" +"Ele converterá metadata armazenada em um arquivo `setup.py` ou `setup.cfg` " +"para um arquivo pyproject.toml para você (consulte [Migrating setup.py to " +"pyproject.toml using Hatch](setup-py-to-pyproject-toml.md ))" #: ../../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 "" +"Ele ajudará armazenando informações de configuração para publicação no PyPI " +"depois que você as informar uma vez." #: ../../tutorials/get-to-know-hatch.md:231 msgid "Use `hatch -h` to see all of the available commands." -msgstr "" +msgstr "Use `hatch -h` para ver todos os comandos disponíveis." #: ../../tutorials/get-to-know-hatch.md:233 msgid "What's next" -msgstr "" +msgstr "Próximos passos" #: ../../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 "" +"Na próxima lição você aprenderá como empacotar e tornar seu código " +"instalável usando o Hatch." #: ../../tutorials/intro.md:34 ../../tutorials/setup-py-to-pyproject-toml.md:36 msgid "Get to know Hatch" -msgstr "" +msgstr "Conheça o Hatch" #: ../../tutorials/intro.md:34 ../../tutorials/run-python-scripts-hatch.md:8 msgid "Run standalone Python scripts with Hatch" -msgstr "" +msgstr "Execute scripts Python independentes com o Hatch" #: ../../tutorials/intro.md:34 msgid "Python Packaging Tutorial Setup" -msgstr "" +msgstr "Configuração do tutorial de empacotamento Python" #: ../../tutorials/intro.md:42 ../../tutorials/intro.md:89 msgid "What is a Python package?" @@ -2979,47 +3215,47 @@ msgstr "Publique no PyPI" #: ../../tutorials/intro.md:42 msgid "Publish to conda-forge" -msgstr "" +msgstr "Publicar no conda-forge" #: ../../tutorials/intro.md:42 msgid "Publish using GitHub Actions and Trusted Publishing" -msgstr "" +msgstr "Publicar usando GitHub Actions e Trusted Publishing" #: ../../tutorials/intro.md:42 msgid "Create and publish a Python Package" -msgstr "" +msgstr "Criar e publicar um pacote Python" #: ../../tutorials/intro.md:53 msgid "Develop package (Hatch environments)" -msgstr "" +msgstr "Desenvolver pacote (ambientes Hatch)" #: ../../tutorials/intro.md:53 msgid "Add README file" -msgstr "" +msgstr "Adicionar arquivo README" #: ../../tutorials/intro.md:53 msgid "Add a license & code of conduct" -msgstr "Adicionar uma licença e um código de conduta" +msgstr "Adicionar uma license e code of conduct" #: ../../tutorials/intro.md:53 msgid "Update metadata in pyproject.toml" -msgstr "" +msgstr "Atualizar metadata no pyproject.toml" #: ../../tutorials/intro.md:53 msgid "Project information files & metadata" -msgstr "" +msgstr "Arquivos de informação do projeto e metadata" #: ../../tutorials/intro.md:63 msgid "Reference Guides" -msgstr "" +msgstr "Guias de referência" #: ../../tutorials/intro.md:70 msgid "Migrate setup.py to a pyproject.toml using Hatch" -msgstr "" +msgstr "Migrar setup.py para pyproject.toml usando o Hatch" #: ../../tutorials/intro.md:70 msgid "Hatch for Existing Packages" -msgstr "" +msgstr "Hatch para pacotes existentes" #: ../../tutorials/intro.md:7 msgid "Python packaging 101" @@ -3032,32 +3268,33 @@ msgstr "_Um tutorial para iniciantes, do começo ao fim_" #: ../../tutorials/intro.md:11 #, python-brace-format msgid "" -"Welcome to the pyOpenSci Python packaging tutorial se ries. The lessons on" -" the upcoming pages walk you through the core steps needed to create a " +"Welcome to the pyOpenSci Python packaging tutorial se ries. The lessons on " +"the upcoming pages walk you through the core steps needed to create a " "{term}`Python package`." msgstr "" -"Bem-vindo à série de tutoriais de packaging em Python " -"da pyOpenSci. As lições nas próximas páginas vão guiá‑lo(a) pelos " -"passos essenciais para criar um {term}`pacote Python`. +"Boas-vindas à série de tutoriais de empacotamento Python da pyOpenSci. As " +"lições nas próximas páginas vão orientar pelos passos essenciais para criar " +"um {term}`pacote Python `." #: ../../tutorials/intro.md:17 msgid "" -"Diagram showing the lessons in our packaging tutorial. There are 6 total " -"- what is a Python package, make code pip installable, publish your " -"package to PyPI, add a README and LICENSE file, add metadata for PyPI and" -" finally publish to conda forge." +"Diagram showing the lessons in our packaging tutorial. There are 6 total - " +"what is a Python package, make code pip installable, publish your package " +"to PyPI, add a README and LICENSE file, add metadata for PyPI and finally " +"publish to conda forge." msgstr "" -"Diagrama mostrando as lições do nosso tutorial de empacotamento. " -Existem 6 ao todo: o que é um pacote Python, tornar o código instalável com pip, " -publicar seu pacote no PyPI, adicionar arquivos README e LICENSE, adicionar " -"metadados para o PyPI e, por fim, publicar no conda‑forge. [pyopensci](https://www.pyopensci.org/learn.html)" +"Diagrama mostrando as lições do nosso tutorial de empacotamento. São 6 ao " +"todo: o que é um pacote Python, tornar o código instalável com pip, publicar " +"seu pacote no PyPI, adicionar arquivos README e LICENSE, adicionar metadata " +"para o PyPI e, por fim, publicar no conda-forge." #: ../../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." -msgstr "Esta lição é a primeira de uma série de lições para ajudar você a " -"começar com o empacotamento em Python." +msgstr "" +"Esta lição é a primeira de uma série de lições para ajudar você a começar " +"com o empacotamento em Python." #: ../../tutorials/intro.md:22 msgid "Who are these tutorials for?" @@ -3065,43 +3302,44 @@ msgstr "Para quem são estes tutoriais?" #: ../../tutorials/intro.md:24 msgid "" -"The content in this tutorial series is beginner friendly and assumes that" -" you have not created a Python package before. However, the content will " -"still be valuable if you are interested in better understanding the steps" -" involved in creating a Python package." +"The content in this tutorial series is beginner friendly and assumes that " +"you have not created a Python package before. However, the content will " +"still be valuable if you are interested in better understanding the steps " +"involved in creating a Python package." msgstr "" -"O conteúdo desta série de tutoriais é adequado para iniciantes e " -"parte do pressuposto de que você ainda não criou um pacote Python antes. " -"No entanto, o conteúdo ainda será útil se você estiver interessado em entender " -"melhor as etapas envolvidas na criação de um pacote Python." +"O conteúdo desta série de tutoriais é adequado para iniciantes e parte do " +"pressuposto de que você ainda não criou um pacote Python. No entanto, o " +"conteúdo ainda será útil se você estiver interessado(a) em entender melhor " +"as etapas envolvidas na criação de um pacote Python." #: ../../tutorials/intro.md:29 msgid "" -"In this series you will learn about the core elements that you need to " -"publish your package to [PyPI](publish-pypi)." -msgstr "Nesta série, você aprenderá sobre os elementos essenciais " -"de que precisa para publicar seu pacote no [PyPI](publish-pypi)." +"In this series you will learn about the core elements that you need " +"topublish your package to [PyPI](publish-pypi)." +msgstr "" +"Nesta série, você aprenderá sobre os elementos essenciais de que precisa " +"para publicar seu pacote no [PyPI](publish-pypi)." #: ../../tutorials/intro.md:32 msgid "" -"In the second series, you will learn about infrastructure and " -"documentation needed to support package maintenance." -msgstr "Na segunda série, você aprenderá sobre a infraestrutura e a " -"documentação necessárias para dar suporte à manutenção do pacote." +"In the second series, you will learn about infrastructure and documentation " +"needed to support package maintenance." +msgstr "" +"Na segunda série, você aprenderá sobre a infraestrutura e a documentação " +"necessárias para dar suporte à manutenção do pacote." -#: ../../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 +#: ../../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 "Objetivos de aprendizagem" +msgstr "Objetivos de Aprendizagem" #: ../../tutorials/intro.md:79 msgid "" "This lesson introduces you to the basic components of a Python package. " "After reading this lesson you will:" -msgstr "Esta lição apresenta os componentes básicos de um pacote Python. " -"Depois de ler esta lição, você será capaz de:" +msgstr "" +"Esta lição apresenta os componentes básicos de um pacote Python. Depois de " +"ler esta lição, você será capaz de:" #: ../../tutorials/intro.md:82 msgid "Understand what a Python package is" @@ -3113,49 +3351,49 @@ msgstr "Ser capaz de listar os 5 componentes centrais de um pacote Python" #: ../../tutorials/intro.md:84 msgid "" -"Be able to explain the difference between generalizable code and code " -"that supports a specific scientific application" +"Be able to explain the difference between generalizable code and code that " +"supports a specific scientific application" msgstr "" -"Ser capaz de explicar a diferença entre código generalizável e " -"código que dá suporte a uma aplicação científica específica" +"Ser capaz de explicar a diferença entre código generalizável e código que " +"dá suporte a uma aplicação científica específica" #: ../../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." +"At a high level, you can think about a Python package as a toolbox that you " +"can use to perform various tasks." msgstr "" -"Em um nível geral, você pode pensar em um pacote Python como uma " -"caixa de ferramentas que pode ser usada para realizar diversas tarefas." +"Em um nível geral, você pode pensar em um pacote Python como uma caixa de " +"ferramentas que pode ser usada para realizar diversas tarefas." #: ../../tutorials/intro.md:94 #, python-brace-format msgid "" -"A Python package is basically a directory with a specific file structure." -" 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." +"A Python package is basically a directory with a specific file structure. " +"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 "" -"Um pacote Python é basicamente um diretório com uma estrutura de arquivos específica. " -"Dentro da estrutura de diretórios do pacote, há objetos {term}`Module`, " -que são arquivos que terminam em `.py` (a mesma extensão que você vê em um script Python). " -"Esses módulos permitem agrupar e organizar o seu código Python. " -"Cada módulo contém funções e classes, que você pode imaginar como as " -"ferramentas dentro da sua caixa de ferramentas." +"Um pacote Python é basicamente um diretório com uma estrutura de arquivos " +"específica. Dentro da estrutura de diretórios do pacote, há objetos " +"{term}`módulo `, que são arquivos que terminam em `.py` (a mesma " +"extensão que você vê em um script Python). Esses módulos permitem agrupar e " +"organizar o seu código Python. Cada módulo contém funções e classes, que " +"você pode imaginar como as ferramentas dentro da sua caixa de ferramentas." #: ../../tutorials/intro.md:103 msgid "" -"Diagram showing a sketch of a toolbox filled with different tools " -"including a hammer and a saw." +"Diagram showing a sketch of a toolbox filled with different tools including " +"a hammer and a saw." msgstr "" -"Diagrama mostrando um esboço de uma caixa de ferramentas " -"cheia de diferentes ferramentas, incluindo um martelo e um serrote." +"Diagrama mostrando um esboço de uma caixa de ferramentas cheia de " +"diferentes ferramentas, incluindo um martelo e um serrote." #: ../../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." +"You can think about a package as a toolbox filled with coding tools. Atool " +"may be a function or a class. Each tool does a specific thing well." msgstr "" "Você pode pensar em um pacote como uma caixa de ferramentas cheia de " "ferramentas de código. Cada ferramenta pode ser uma função ou uma classe. " @@ -3169,147 +3407,197 @@ msgstr "Pacotes Python são instaláveis" 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 " -"functionality like you would import core scientific Python packages such " -"as NumPy or Matplotlib." +"functionality like you would import core scientific Pythonpackages such as " +"NumPy or Matplotlib." msgstr "" +"Um pacote é instalável, o que significa que você pode adicionar a " +"funcionalidade do código do pacote a qualquer ambiente Python e importar " +"essa funcionalidade como faria com pacotes científicos centrais do Python, " +"como NumPy ou Matplotlib." #: ../../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 " -"package is the first step you need to take so you can share the tools in " -"the toolbox you've created and let others build with it." +"Installing a package into an environment makes it easier to manage andreuse " +"your code across different projects. Structuring your code asa package is " +"the first step you need to take so you can share the tools in the toolbox " +"you've created and let others build with it." msgstr "" +"Instalar um pacote em um ambiente facilita gerenciar e reutilizar seu código " +"em projetos diferentes. Estruturar seu código como um pacote é o primeiro " +"passo que você precisa dar para compartilhar as ferramentas da caixa de " +"ferramentas que criou e permitir que outras pessoas construam com elas." #: ../../tutorials/intro.md:126 msgid "Why create a Python package?" -msgstr "" +msgstr "Por que criar um pacote Python?" #: ../../tutorials/intro.md:128 msgid "You might create a Python package because you want to:" -msgstr "" +msgstr "Você pode criar um pacote Python porque deseja:" #: ../../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 " -"environment. This allows you to then import functions and classes into " -"any workflows both locally and in the cloud." +"environment. This allows you to then import functions and classes intoany " +"workflows both locally and in the cloud." msgstr "" +"**Usar seu código em projetos diferentes:** No nível mais básico, criar um " +"pacote permite instalar seu código em um ambiente Python. Isso permite " +"importar funções e classes em quaisquer workflows, tanto localmente " +"quanto na nuvem." #: ../../tutorials/intro.md:131 #, python-brace-format msgid "" -"**Share your code:** If you publish a package on a public repository such" -" as PyPI or conda-forge, your package can be installed on any machine " -"using {term}`pip` or conda with a single command." +"**Share your code:** If you publish a package on a public repository such " +"as PyPI or conda-forge, your package can be installed on any machine using " +"{term}`pip` or conda with a single command." msgstr "" +"**Compartilhar seu código:** Se você publicar um pacote em um repositório " +"público como PyPI ou conda-forge, seu pacote pode ser instalado em qualquer " +"máquina usando {term}`pip` ou conda com um único comando." #: ../../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 " -"on GitHub). A version control system such as git (the system used by " -"GitHub), further makes it easier to track changes to the codebase over " -"time. Tools such as issues and pull requests make it easier for outside " -"users to contribute bug fixes and to establish review processes for " -"accepting changes to the code base." -msgstr "" +"**Build community around your code:** Packages make it easier for multiple " +"people to work on the same project (particularly when published on GitHub). " +"A version control system such as git (the systemused by GitHub), further " +"makes it easier to track changes to thecodebase over time. Tools such as " +"issues and pull requests make it easier for outside users to contribute bug " +"fixes and to establish review processes for accepting changes to the code " +"base." +msgstr "" +"**Construir comunidade em torno do seu código:** pacotes facilitam " +"que várias pessoas trabalhem no mesmo projeto (especialmente quando " +"publicado no GitHub). Um sistema de controle de versão como git (o sistema " +"usado pelo GitHub) também facilita acompanhar mudanças na base de código ao " +"longo do tempo. Ferramentas como `issues` e `pull requests` facilitam que " +"usuários externos contribuam com correções de bugs e estabeleçam processos " +"de revisão para aceitar mudanças na base de código." #: ../../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 " -"structure can help with both maintaining the codebase and with making it " -"easier to understand." +"projects, dividing them into smaller, more manageable components. " +"Thisstructure can help with both maintaining the codebase and with making " +"it easier to understand." msgstr "" +"**Organizar seu código:** pacotes podem ser usados para organizar grandes " +"projetos de código, dividindo-os em componentes menores e mais gerenciáveis. " +"Essa estrutura ajuda tanto na manutenção da base de código quanto na " +"compreensão dela." #: ../../tutorials/intro.md:137 msgid "What to consider before you create a package" -msgstr "" +msgstr "O que considerar antes de criar um pacote" #: ../../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 "" +"Criar um pacote Python que outras pessoas usem exige tempo e esforço " +"consideráveis. Antes de começar, pense nos seus objetivos, incluindo:" #: ../../tutorials/intro.md:142 msgid "Who you think will use your package" -msgstr "" +msgstr "Quem você acha que usará seu pacote" #: ../../tutorials/intro.md:143 msgid "How people might use your package and on what data (if data are relevant)" msgstr "" +"Como as pessoas podem usar seu pacote e com quais dados (se dados forem " +"relevantes)" #: ../../tutorials/intro.md:144 msgid "Whether you have time to add things such as documentation and tests" -msgstr "" +msgstr "Se você tem tempo para adicionar coisas como documentação e testes" #: ../../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 " -"update it, fix bugs and answer questions." +"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 update it, " +"fix bugs and answer questions." msgstr "" +"Por quanto tempo você poderá mantê-lo: lembre-se de que, quando as pessoas " +"começarem a usar seu pacote, elas dependerão da sua equipe de mantenedores " +"para atualizá-lo, corrigir bugs e responder perguntas." #: ../../tutorials/intro.md:147 msgid "" "Before creating a user-facing package, it's important to consider all of " "the above." msgstr "" +"Antes de criar um pacote voltado para usuários, é importante considerar " +"tudo acima." #: ../../tutorials/intro.md:149 msgid "The elements of a Python package" -msgstr "" +msgstr "Os elementos de um pacote Python" #: ../../tutorials/intro.md:153 ../../tutorials/intro.md:231 msgid "Diagram showing .. more here if this stays." -msgstr "" +msgstr "Diagrama mostrando .. mais aqui se isto permanecer." #: ../../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 " -"making sure everything works and is up to date while fixing bugs and " -"addressing user concerns." +"OSI-approved license and infrastructure. Maintainers are at the core making " +"sure everything works and is up to date while fixing bugs and addressing " +"user concerns." msgstr "" +"Os elementos de um pacote Python incluem código, documentação, testes,uma " +"`license` aprovada pela OSI e infraestrutura. Os mantenedores estão no centro, " +"garantindo que tudo funcione e esteja atualizado, corrigindo bugs e " +"atendendo preocupações dos usuários." #: ../../tutorials/intro.md:161 msgid "The core elements of Python package include:" -msgstr "" +msgstr "Os elementos centrais de um pacote Python incluem:" #: ../../tutorials/intro.md:163 msgid "" "**Code:** Functions and classes that provide functionality for a user of " "your package" msgstr "" +"**Code:** Funções e classes que fornecem funcionalidade para um usuário " +"do seu pacote" #: ../../tutorials/intro.md:164 msgid "" -"**Documentation:** Installation instructions, tutorials, and examples " -"that both help users get started using your package and contributors and " +"**Documentation:** Installation instructions, tutorials, and examples that " +"both help users get started using your package and contributors and " "maintainers fix bugs and maintain the package." msgstr "" +"**Documentation:** Instruções de instalação, tutoriais e exemplos que " +"ajudam usuários a começar a usar seu pacote e contributors e mantenedores a " +"corrigir bugs e manter o pacote." #: ../../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." +"Contributor Documentation in the form of a **CONTRIBUTING.md** file " +"isuseful to help people to contribute to your package." msgstr "" +"Documentação para contributors na forma de um arquivo **CONTRIBUTING.md** é " +"útil para ajudar pessoas a contribuir com seu pacote." #: ../../tutorials/intro.md:166 msgid "" "Development Documentation helps both maintainers and contributors " "understand how to maintain a package's infrastructure." msgstr "" +"Documentação de desenvolvimento ajuda mantenedores e contribuidores a entender " +"como manter a infraestrutura de um pacote." #: ../../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" +"**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 codein the future" msgstr "" +"**Tests:** que garantem que seu código funciona como deveria e facilitam " +"que você e outras pessoas contribuam, modifiquem e atualizemo código no " +"futuro" #: ../../tutorials/intro.md:168 msgid "" @@ -3318,278 +3606,398 @@ msgid "" "allows others to use your package. It also provides legal direction " "regarding how elements of the package can and can't be reused." msgstr "" +"**License:** Uma open source `license`, ou `license` [aprovada pela " +"OSI](https://opensource.org/license/), permite que outras pessoas usem seu " +"pacote. Ela também fornece orientação legal sobre como os elementos do " +"pacote podem ou não ser reutilizados." #: ../../tutorials/intro.md:169 msgid "" -"**Infrastructure** that automates updates, publication workflows and runs" -" test suites. Infrastructure includes a suite of things such as platforms" -" like GitHub and GitLab, tools to run tests and tools locally such as nox" -" and tox and continuous integration that automates package maintenance " -"steps." +"**Infrastructure** that automates updates, publication workflows and runs " +"test suites. Infrastructure includes a suite of things such as platforms " +"like GitHub and GitLab, tools to run tests and tools locallysuch as nox and " +"tox and continuous integration that automates package maintenance steps." msgstr "" +"**Infrastructure** que automatiza atualizações, workflows de publicação e " +"executa suites de testes. A infraestrutura inclui um conjunto de coisas, " +"como plataformas como GitHub e GitLab, ferramentas para executar testes e " +"ferramentas locais como nox e tox, e integração contínua que automatiza " +"etapas de manutenção do pacote." #: ../../tutorials/intro.md:171 msgid "What pyOpenSci looks for in a package" -msgstr "" +msgstr "O que a pyOpenSci busca em um pacote" #: ../../tutorials/intro.md:174 msgid "" "pyOpenSci performs an [initial set of editor " -"checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-" -"chief-guide.html#editor-checklist-template) for any package submitted to " -"us for peer review. You may find these checks useful as you create your " -"package as a baseline for things that you package should have." +"checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chie" +"f-guide.html#editor-checklist-template)foranypackagesubmittedtousforpeerrevi" +"ew. You may find these checksuseful as you create yourpackageas a baseline " +"for things thatyou package should have." msgstr "" +"A pyOpenSci realiza um [conjunto inicial de verificações do " +"editor](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chie" +"f-guide.html#editor-checklist-template) para qualquer pacote enviado para " +"revisão por pares. Você pode achar essas verificações úteis ao criar seu " +"pacote como linha de base do que seu pacote deve ter." #: ../../tutorials/intro.md:180 msgid "Packages are more than just code - Infrastructure" -msgstr "" +msgstr "Pacotes são mais do que apenas código - Infraestrutura" #: ../../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 " -"only writing high quality code, but also the various elements of a " -"package that make it a useful community resource." +"people to use your package, besides yourself, you should consider not only " +"writing high quality code, but also the various elements of a package that " +"make it a useful community resource." msgstr "" +"Um pacote em qualquer linguagem é mais do que apenas código. Se você espera " +"que outras pessoas usem seu pacote, além de você mesmo, considere não " +"apenas escrever código de alta qualidade, mas também os diversos elementos " +"de um pacote que o tornam um recurso útil para a comunidade." #: ../../tutorials/intro.md:187 msgid "Version control and storing your package on GitHub or GitLab" -msgstr "" +msgstr "Controle de versão e armazenamento do seu pacote no GitHub ou GitLab" #: ../../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/) " "for version control. Having your software under version control is " -"important because it allows you to both track changes over time while " -"also going back in history and undoing changes in the case that a change " -"to the code base unexpectedly breaks something." +"important because it allows you to both trackchanges over time while also " +"going back in history and undoing changesin the case that a change to the " +"code base unexpectedly breaks something." msgstr "" +"A maioria dos pacotes Python fica em uma plataforma online de controle de " +"versão como GitHub ou GitLab. GitHub e GitLab executam " +"[git](https://git-scm.com/) para controle de versão. Ter seu software sob " +"controle de versão é importante porque permite acompanhar mudanças ao longo " +"do tempo e também voltar no histórico e desfazer mudanças caso uma " +"alteração na base de código quebre algo inesperadamente." #: ../../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 " -"make contributions using a pull request (GitHub) / merge request (GitLab)" -" / code review workflow." +"public facing. This means that others can both see your code and also make " +"contributions using a pull request (GitHub) / merge request (GitLab) / code " +"review workflow." msgstr "" +"Ao publicar seu pacote no GitHub ou GitLab, você o torna público. " +"Isso significa que outras pessoas podem ver seu código e também contribuir " +"usando um pull request (GitHub) / merge request (GitLab) / workflow decode " +"review." #: ../../tutorials/intro.md:196 msgid "GitHub & GitLab vs. Git" -msgstr "" +msgstr "GitHub e GitLab vs. Git" #: ../../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 " -"allows you to upload (`git push`) and download (`git pull`) files to " -"GitHub and GitLab." +"GitHub and GitLab are online (cloud) platforms that run `git` " +"(versioncontrol software) on the backend. Running git locally on your " +"computerallows you to upload (`git push`) and download (`git pull`) files " +"to GitHub and GitLab." msgstr "" +"GitHub e GitLab são plataformas online (na nuvem) que executam `git` " +"(software de controle de versão) no backend. Executar git localmente no seu " +"computador permite enviar (`git push`) e baixar (`git pull`) arquivos para " +"GitHub e GitLab." #: ../../tutorials/intro.md:204 msgid "Issues or Ticket Trackers" -msgstr "" +msgstr "Issues ou rastreadores de tickets" #: ../../tutorials/intro.md:206 msgid "" "GitHub and GitLab also both offer community features such as issues that " "allow:" msgstr "" +"GitHub e GitLab também oferecem recursos de comunidade, como issues, que " +"permitem:" #: ../../tutorials/intro.md:208 msgid "you to communicate with your maintainers and contributor community" msgstr "" +"que você se comunique com sua equipe de mantenedores e a comunidade de " +"contribuidores" #: ../../tutorials/intro.md:209 msgid "users to report bugs, ask questions and request new features" -msgstr "" +msgstr "que usuários reportem bugs, façam perguntas e solicitem novos recursos" #: ../../tutorials/intro.md:210 msgid "" -"you to publicly keep track of enhancements and features you want to work " -"on for your package." +"you to publicly keep track of enhancements and features you want to work on " +"for your package." msgstr "" +"que você acompanhe publicamente melhorias e recursos que deseja desenvolver " +"para seu pacote." #: ../../tutorials/intro.md:212 msgid "Continuous integration and continuous deployment" -msgstr "" +msgstr "Integração contínua e implantação contínua" #: ../../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" -" automatically runs a specific job when a certain event occurs, whereas " +"deployment (CI/CD). Continuous integration (CI) refers to a platform that " +"automatically runs a specific job when a certain event occurs, whereas " "continuous deployment (CD) is an extension of CI that refers to not only " "running or building but also to publishing the final outputs somewhere." msgstr "" +"GitHub e GitLab também fornecem integração contínua e implantação contínua " +"(CI/CD). Integração contínua (CI) refere-se a uma plataforma que executa " +"automaticamente um job específico quando um determinado evento ocorre, " +"enquanto implantação contínua (CD) é uma extensão da CI que se refere não " +"apenas a executar ou fazer build, mas também a publicar os outputs finais " +"em algum lugar." #: ../../tutorials/intro.md:216 msgid "**An example of Continuous integration:**" -msgstr "" +msgstr "**Um exemplo de integração contínua:**" #: ../../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 " +"When someone submits a change to your code, your tests will run " +"acrossdifferent operating systems and the code will be checked for format " "issues." msgstr "" +"Quando alguém envia uma mudança no seu código, seus testes serão executados " +"em diferentes sistemas operacionais e o código será verificado quanto a " +"problemas de formatação." #: ../../tutorials/intro.md:220 msgid "**An example of Continuous deployment:**" -msgstr "" +msgstr "**Um exemplo de implantação contínua:**" #: ../../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." +"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 "" +"Quando você estiver pronto para fazer release do seu pacote no PyPI, uma " +"operação de implantação contínua pode ser acionada no release para publicar " +"seu pacote no PyPI." #: ../../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 " -"you maintain code style and format consistency for every new change to " -"your code." +"changes to the code don't break things unexpectedly. They can also help you " +"maintain code style and format consistency for every new change to your " +"code." msgstr "" +"CI/CD integrado ajudará você a manter seu software, garantindo que mudanças " +"no código não quebrem coisas inesperadamente. Também pode ajudar a manter " +"consistência de estilo e formatação do código a cada nova mudança." #: ../../tutorials/intro.md:233 msgid "The lifecycle of a scientific Python package." -msgstr "" +msgstr "O ciclo de vida de um pacote Python científico." #: ../../tutorials/intro.md:236 msgid "When should you turn your code into a Python package?" -msgstr "" +msgstr "Quando você deve transformar seu código em um pacote Python?" #: ../../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." msgstr "" +"Você pode estar se perguntando quais tipos de código devem se tornar um " +"pacote Python que esteja tanto no GitHub quanto publicado no PyPI e/ou " +"conda-forge." #: ../../tutorials/intro.md:240 msgid "There are a few use cases to consider:" -msgstr "" +msgstr "Há alguns casos de uso a considerar:" #: ../../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 " -"locally pip installable and you may also want to publish it to GitHub. In" -" that case you don't expect others to use your code, and as such you may " -"only have documentation for you and your future self if you need to " -"update the package." +"**Creating a basic package for yourself:** Sometimes you want create " +"apackage for your own personal use. This might mean making your code " +"locally pip installable and you may also want to publish it to GitHub.In " +"that case you don't expect others to use your code, and as such youmay only " +"have documentation for you and your future self if you need to update the " +"package." msgstr "" +"**Criar um pacote básico para você mesmo:** Às vezes você quer criar um " +"pacote para uso pessoal. Isso pode significar tornar seu código instalável " +"localmente com pip e também publicá-lo no GitHub. Nesse caso, você não " +"espera que outras pessoas usem seu código e, portanto, pode ter " +"documentação apenas para você e seu eu futuro, caso precise atualizar o " +"pacote." #: ../../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" -" to have those functions available to all of your projects." +"write that are useful across several of your projects. It could beuseful to " +"have those functions available to all of your projects." msgstr "" +"Um exemplo desse tipo de pacote pode ser um conjunto de funções que você " +"escreveu e que são úteis em vários dos seus projetos. Pode ser útil ter " +"essas funções disponíveis para todos os seus projetos." #: ../../tutorials/intro.md:247 msgid "LINK to pip installable lesson when it's published - it's in review now" msgstr "" +"LINK para a lição sobre pip installable quando for publicada - está " +"em revisão agora" #: ../../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" -" to other people as well. In that case, you might consider both creating " -"the package, publishing it on GitHub, and because other users may be " -"using it, you may make use of GitHub's infrastructure including CI/CD " -"pipelines and issue trackers. Because you want other people to use your " -"package, you will want to also include LICENSE information, documentation" -" for users and contributors and tests. This type of package is most often" -" published to PyPI." +"some code that you soon realize might also be useful to not just you, but " +"to other people as well. In that case, you might consider both creating the " +"package, publishing it on GitHub, and because other users may be using it, " +"you may make use of GitHub's infrastructure including CI/CD pipelines and " +"issue trackers. Because you want other people to use your package, you will " +"want to also include LICENSE information, documentation for users and " +"contributors and tests. This type of package is most often published to " +"PyPI." msgstr "" +"**Criar um pacote para a comunidade:** Em outros casos, você pode criar " +"código que logo percebe ser útil não só para você, mas também para outras " +"pessoas. Nesse caso, pode considerar criar o pacote, publicá-lo no GitHub " +"e, como outros usuários podem usá-lo, aproveitar a infraestrutura do " +"GitHub, incluindo pipelines de CI/CD e rastreadores de issues. Como você " +"quer que outras pessoas usem seu pacote, também incluirá informações de " +"LICENSE, documentação para usuários e contributors e testes. Esse tipo de " +"pacote costuma ser publicado no PyPI." #: ../../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" -" just the maintainers." +"For example, all of the [pyOpenSci " +"packages](https://www.pyopensci.org/python-packages.html) are public facing " +"with an intended audience beyond just the maintainers." msgstr "" +"Por exemplo, todos os [pacotes da " +"pyOpenSci](https://www.pyopensci.org/python-packages.html) são voltados " +"para o público, com audiência além dos mantenedores." #: ../../tutorials/intro.md:255 msgid "Packages that you expect others to use should be well-scoped" msgstr "" +"Pacotes que você espera que outras pessoas usem devem ter escopo bem " +"definido" #: ../../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 " +"Ideally the code in your Python package is focused on a specific themeor " +"use case. This theme is important as it's a way to scope the content of " "your package." msgstr "" +"Idealmente, o código do seu pacote Python está focado em um tema ou caso de " +"uso específico. Esse tema é importante, pois é uma forma de delimitar o " +"conteúdo do seu pacote." #: ../../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 " -"- is your code written specifically for a single research project? Or " -"could it have a broader application across multiple projects in your " -"domain?" +"It can be tricky to decide when your code becomes something that mightbe " +"more broadly useful to others. But one question you can ask yourself is - " +"is your code written specifically for a single research project? Or could " +"it have a broader application across multiple projects in your domain?" msgstr "" +"Pode ser difícil decidir quando seu código se torna algo que pode ser mais " +"amplamente útil para outras pessoas. Mas uma pergunta que você pode fazer " +"é: seu código foi escrito especificamente para um único projeto de " +"pesquisa? Ou poderia ter aplicação mais ampla em vários projetos do seu " +"domínio?" #: ../../tutorials/intro.md:261 msgid "How does this relate to code for a research project?" -msgstr "" +msgstr "Como isso se relaciona com código de um projeto de pesquisa?" #: ../../tutorials/intro.md:264 msgid "" -"A [Research Compendium](https://book.the-turing-way.org/reproducible-" -"research/compendia.html) is an organized set of code, data and " -"documentation that supports a specific research project. It aims to " -"enhance the reproducibility and transparency of research by providing a " -"comprehensive record of the methods, data, and analyses used in a study." +"A [Research " +"Compendium](https://book.the-turing-way.org/reproducible-research/compendia." +"html)isanorganizedsetofcode,dataanddocumentation that supports a " +"specificresearch project.It aims to enhance the reproducibility and " +"transparency of research byproviding acomprehensive record of the methods, " +"data, andanalyses used in a study." msgstr "" +"Um [Research " +"Compendium](https://book.the-turing-way.org/reproducible-research/compendia." +"html)é um conjunto organizado de código, dados e documentação que sustenta " +"um projeto de pesquisa específico. Ele visa aumentar a reprodutibilidade e a " +"transparência da pesquisa, fornecendo um registro abrangente dos métodos, " +"dados e análises usados em um estudo." #: ../../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 " -"workflows. As such a Python package is more generalizable than a Research" -" Compendium which supports a specific project." +"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 " +"workflows. As such a Python package is more generalizable than a Research " +"Compendium which supports a specific project." msgstr "" +"Um pacote Python é uma coleção de modules que podem ser usados para " +"executar um conjunto específico de tarefas. Essas tarefas devem ser " +"aplicáveis a muitos workflows. Assim, um pacote Python é mais " +"generalizável do que um Research Compendium, que sustenta um projeto " +"específico." #: ../../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)" +"computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journa" +"l.pcbi.1005510)" msgstr "" +"[Leia sobre `Good enough practices in scientific " +"computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journa" +"l.pcbi.1005510)" #: ../../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-" -"future-self/)" +"[Learn more about research compendia (also called repo-packs) in this blog " +"post.](https://lorenabarba.com/blog/how-repro-packs-can-save-your-future-sel" +"f/)" msgstr "" +"[Saiba mais sobre research compendia (também chamados de repo-packs) neste " +"post de " +"blog.](https://lorenabarba.com/blog/how-repro-packs-can-save-your-future-sel" +"f/)" #: ../../tutorials/intro.md:278 msgid "Below are a few examples well scoped pyOpenSci packages:" msgstr "" +"Abaixo estão alguns exemplos de pacotes da pyOpenSci com escopo bem " +"definido:" #: ../../tutorials/intro.md:280 msgid "" -"[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): is a package " -"designed to work with annotating animal vocalizations and bioacoustics " -"data. This package helps scientists process different types of " +"[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): is a " +"packagedesigned to work with annotating animal vocalizations and " +"bioacousticsdata. This package helps scientists process different types of " "bioacoustic data rather than focusing on a specific individual research " "application associated with a user-specific research workflow." msgstr "" +"[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): é um " +"pacote projetado para trabalhar com anotação de vocalizações animais e dados " +"de bioacústica. Este pacote ajuda cientistas a processar diferentes tipos " +"de dados bioacústicos, em vez de focar em uma aplicação de pesquisa " +"específica associada a um workflow de pesquisa de um usuário." #: ../../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" -" research application." +"[Pandera](https://www.union.ai/pandera) is another more broadly used Python " +"package. Pandera supports data testing and thus also has a broader research " +"application." msgstr "" +"[Pandera](https://www.union.ai/pandera) é outro pacote Python de uso mais " +"amplo. Pandera suporta testes de dados e, portanto, também tem aplicação de " +"pesquisa mais ampla." #: ../../tutorials/intro.md:283 msgid "Matplotlib as an example" -msgstr "" +msgstr "Matplotlib como exemplo" + + + + + #: ../../tutorials/intro.md:285 msgid "" From 5ca3511c4c164e29876832f8bad778a9151e7c3e Mon Sep 17 00:00:00 2001 From: Roberto Date: Tue, 23 Jun 2026 19:20:47 -0700 Subject: [PATCH 4/5] docs: final 4,000 lines of ttranslation to Portuguese. --- locales/pt/LC_MESSAGES/tutorials.po | 3494 ++++++++++++++++++--------- 1 file changed, 2347 insertions(+), 1147 deletions(-) diff --git a/locales/pt/LC_MESSAGES/tutorials.po b/locales/pt/LC_MESSAGES/tutorials.po index fad519b2..de7123ba 100644 --- a/locales/pt/LC_MESSAGES/tutorials.po +++ b/locales/pt/LC_MESSAGES/tutorials.po @@ -3997,35 +3997,39 @@ msgstr "Matplotlib como exemplo" - - #: ../../tutorials/intro.md:285 msgid "" -"At the larger end of the user spectrum, Matplotlib is a great example. " -"Matplotlib does one thing really well:" +"At the larger end of the user spectrum, Matplotlib is a great " +"example.Matplotlib does one thing really well:" msgstr "" +"No extremo maior do espectro de usuários, Matplotlib é um ótimo exemplo. " +"Matplotlib faz uma coisa muito bem:" #: ../../tutorials/intro.md:288 msgid "_It creates visual plots of data._" -msgstr "" +msgstr "_Ele cria gráficos visuais de dados._" #: ../../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 " -"the same broad application and large user base that Matplotlib has, the " -"idea of scoping out what your package does is still important." +"Thousands of people use Matplotlib for different plotting applicationsusing " +"different types of data. While few scientific packages will havethe same " +"broad application and large user base that Matplotlib has, the idea of " +"scoping out what your package does is still important." msgstr "" +"Milhares de pessoas usam Matplotlib para diferentes aplicações de plotagem " +"com diferentes tipos de dados. Embora poucos pacotes científicos tenham a " +"mesma aplicação ampla e base de usuários grande que Matplotlib, a ideia de " +"delimitar o que seu pacote faz ainda é importante." #: ../../tutorials/intro.md:296 msgid "Code should also be clean & readable & documented" -msgstr "" +msgstr "O código também deve ser limpo, legível e documentado" #: ../../tutorials/intro.md:298 msgid "" "The code in your package should also be clean, readable, and well " "documented." -msgstr "" +msgstr "O código do seu pacote também deve ser limpo, legível e bem documentado." #: ../../tutorials/intro.md:300 msgid "" @@ -4033,506 +4037,710 @@ msgid "" "names, is concise and doesn't repeat itself. You can learn about best " "practices for clean code in future pyOpenSci tutorials." msgstr "" +"**Clean code:** Clean code refere-se a código que usa nomes de variáveis " +"expressivos, é conciso e não se repete. Você pode aprender sobre boas " +"práticas de clean code em tutoriais futuros da pyOpenSci." #: ../../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 " -"ensure this consistency throughout your entire package. [Learn more about" -" code formatters here.](../package-structure-code/code-style-linting-" -"format)" +"**Readable code:** readable code is code written with a consistent style. " +"You can use linters and code formatters such as black and flake8 to ensure " +"this consistency throughout your entire package. [Learn more about code " +"formatters here.](../package-structure-code/code-style-linting-format)" msgstr "" +"**Readable code:** Readable code é código escrito com um estilo " +"consistente. Você pode usar linters e formatadores de código como black e " +"flake8 para garantir essa consistência em todo o pacote. [Saiba mais sobre " +"formatadores de código " +"aqui.](../package-structure-code/code-style-linting-format)" #: ../../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 " -"do and also what the input and output elements of each function are. [You" -" can learn more about docstrings in our guide, here.](../documentation" -"/write-user-documentation/document-your-code-api-docstrings)" +"**Documented code:** documented code is written using docstrings that help " +"a user understand both what the functions and methods in your code do and " +"also what the input and output elements of each function are. [You can " +"learn more about docstrings in our guide, " +"here.](../documentation/write-user-documentation/document-your-code-api-docs" +"trings)" msgstr "" +"**Documented code:** Documented code é escrito usando docstrings que ajudam " +"o usuário a entender tanto o que as funções e methods do seu código fazem " +"quanto quais são os elementos de input e output de cada função. [Você " +"pode saber mais sobre docstrings em nosso guia, " +"aqui.](../documentation/write-user-documentation/document-your-code-api-docs" +"trings)" #: ../../tutorials/intro.md:312 msgid "Making your package installable - publishing to PyPI & conda-forge" -msgstr "" +msgstr "Tornar seu pacote instalável - publicação no PyPI e conda-forge" #: ../../tutorials/intro.md:314 msgid "Python packages and environments" -msgstr "" +msgstr "Pacotes Python e ambientes" #: ../../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 " -"environment allows you to access it from any code run with that specific " +"You can install a Python package into a Python environment in the sameway " +"you might install NumPy or Pandas. Installing your package into " +"anenvironment allows you to access it from any code run with thatspecific " "Python environment activated." msgstr "" +"Você pode instalar um pacote Python em um ambiente Python da mesma forma " +"que instalaria NumPy ou Pandas. Instalar seu pacote em um ambiente permite " +"acessá-lo a partir de qualquer código executado com aquele ambiente Python " +"específico ativado." #: ../../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 " -"install package. The second arrow leads to a box that represents a Python" -" environment that already has some packages installed such as Pandas and " -"NumPy. Your package will also get installed into that same environment " -"when you pip install it." +"install package. The second arrow leads to a box that represents aPython " +"environment that already has some packages installed such as Pandas and " +"NumPy. Your package will also get installed into that same environment when " +"you pip install it." msgstr "" +"Diagrama mostrando as etapas associadas à criação de um pacote e depois à " +"sua instalação. A primeira seta diz seu pacote e a segunda diz pip install " +"pacote. A segunda seta leva a uma caixa que representaum ambiente Python " +"que já tem alguns pacotes instalados, como Pandas e NumPy. Seu pacote também " +"será instalado nesse mesmo ambiente quando você fizer pip install." #: ../../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 " -"installable locally on your computer and use it for projects that you are" -" working on without having to ever publish to PyPI. Publishing to PyPI is" -" useful when you want to make your code public-facing and share it with " +"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 " +"codeinstallable locally on your computer and use it for projects that you " +"are working on without having to ever publish to PyPI. Publishing to PyPI " +"is useful when you want to make your code public-facing and shareit with " "others." msgstr "" +"Você não precisa publicar no PyPI para tornar seu código instalável. Com a " +"estrutura de arquivos correta e metadata do projeto, você pode tornar seu " +"código instalável localmente no seu computador e usá-lo em projetos em que " +"está trabalhando sem precisar publicar no PyPI. Publicar no PyPI é útil " +"quando você quer tornar seu código público e compartilhá-lo com outras " +"pessoas." #: ../../tutorials/intro.md:331 msgid "Publishing a package to PyPI / Conda-Forge" -msgstr "" +msgstr "Publicar um pacote no PyPI / Conda-Forge" #: ../../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" -" a repository such as **PyPI** or **conda-forge**." +"download the code to your computer locally then you need to publishit in a " +"repository such as **PyPI** or **conda-forge**." msgstr "" +"Se você quer tornar seu pacote diretamente instalável sem precisar baixar o " +"código para o seu computador localmente, precisa publicá-lo em um " +"repositório como **PyPI** ou **conda-forge**." #: ../../tutorials/intro.md:337 msgid "" -"Learn [how to publish your package to PyPI in this tutorial.](publish-" -"pypi.md)" -msgstr "" +"Learn [how to publish your package to PyPI in this " +"tutorial.](publish-pypi.md)" +msgstr "Aprenda [como publicar seu pacote no PyPI neste tutorial.](publish-pypi.md)" #: ../../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" -" this recipe to conda-forge." +"[Grayskull](https://github.com/conda/grayskull) tool. You can then submit " +"this recipe to conda-forge." msgstr "" +"Depois você pode criar uma recipe do conda-forge usando a ferramenta " +"[Grayskull](https://github.com/conda/grayskull). Em seguida, envie essa " +"recipe para o conda-forge." #: ../../tutorials/intro.md:341 msgid "" -"[You will learn more about the conda-forge publication process here" -".](publish-conda-forge.md)" +"[You will learn more about the conda-forge publication process " +"here.](publish-conda-forge.md)" msgstr "" +"[Você aprenderá mais sobre o processo de publicação no conda-forge " +"aqui.](publish-conda-forge.md)" #: ../../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" -" package. Documentation and data are below that box because they aren't " +"Graphic showing the high level packaging workflow. On the left you seea " +"graphic with code, metadata and tests in it. Those items all go intoyour " +"package. Documentation and data are below that box because they aren't " "normally published in your packaging wheel distribution. An arrow to the " "right takes you to a build distribution files box. That box leads you to " "either publishing to TestPyPI or the real PyPI. From PyPI you can then " -"connect to conda-forge for an automated build that sends distributions " -"from PyPI to conda-forge." -msgstr "" +"connect to conda-forge for an automated build that sends distributions from " +"PyPI to conda-forge." +msgstr "" +"Gráfico mostrando o workflow de alto nível de empacotamento. À esquerda " +"você vê um gráfico com código, metadata e testes. Esses itens entram no seu " +"pacote. Documentação e dados ficam abaixo dessa caixa porque normalmente " +"não são publicados na wheel distribution do empacotamento. Uma seta à " +"direita leva a uma caixa de arquivos de build distribution. Essa caixa leva " +"à publicação no TestPyPI ou no PyPI real. A partir do PyPI, você pode " +"conectar ao conda-forge para um build automatizado que envia distributions " +"do PyPI para o conda-forge." #: ../../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-" -"distribution) and [wheel](#python-wheel) files. Once you are ready to " -"make your code publicly installable, you can publish it on PyPI. Once " -"your code is on PyPI it is straight forward to then publish to conda-" -"forge. You create a recipe using the Grayskull package and then you open " -"a pr in the conda-forge recipe repository. You will learn more about this" -" process in the [conda-forge lesson](/tutorials/publish-conda-forge)." -msgstr "" +"In the image above, you can see the steps associated with publishing your " +"package on PyPI and conda-forge. PyPI supports " +"[sdist](#python-source-distribution) and [wheel](#python-wheel) files.Once " +"you are ready to make your code publicly installable, you can publish it on " +"PyPI. Once your code is on PyPI it is straight forward to then publish to " +"conda-forge. You create a recipe using the Grayskull package and then you " +"open a pr in the conda-forge recipe repository. You will learn more about " +"this process in the [conda-forgelesson](/tutorials/publish-conda-forge)." +msgstr "" +"Na imagem acima, você pode ver as etapas associadas à publicação do seu " +"pacote no PyPI e conda-forge. O PyPI suporta arquivos " +"[sdist](#python-source-distribution) e [wheel](#python-wheel). Quando " +"estiver pronto para tornar seu código publicamente instalável, você pode " +"publicá-lo no PyPI. Depois que seu código estiver no PyPI, é simples " +"publicar no conda-forge. Você cria uma recipe usando o pacote Grayskull e " +"depois abre um pr no repositório de recipes do conda-forge. Você aprenderá " +"mais sobre esse processo na [lição do " +"conda-forge](/tutorials/publish-conda-forge)." #: ../../tutorials/intro.md:350 msgid "Yay, your package has users! Now what?" -msgstr "" +msgstr "Ótimo, seu pacote tem usuários! E agora?" #: ../../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 " -"package. It’s important to consider all this before you dive into " -"development. Once you have a user base in the community, people will " -"depend upon your code to work and will need direction regarding how to " -"use it." +"package. It’s important to consider all this before you dive into " +"development. Once you have a user base in the community, people will depend " +"upon your code to work and will need direction regarding how to use it." msgstr "" +"À medida que a comunidade que usa seu pacote cresce, você também pode se ver " +"gerenciando usuários, contributors e outras pessoas que querem interagir " +"com seu pacote. É importante considerar tudo isso antes de mergulhar no " +"desenvolvimento. Quando você tiver uma base de usuários na comunidade, as " +"pessoas dependerão do seu código funcionar e precisarão de orientação sobre " +"como usá-lo." #: ../../tutorials/intro.md:354 msgid "To support your community, you'll want to add things like:" -msgstr "" +msgstr "Para apoiar sua comunidade, você vai querer adicionar coisas como:" #: ../../tutorials/intro.md:356 msgid "" "[a development guide that documents your maintainer workflow process " "](/documentation/repository-files/development-guide.md)" msgstr "" +"[um guia de desenvolvimento que documenta seu processo de workflow de " +"mantenedor ](/documentation/repository-files/development-guide.md)" #: ../../tutorials/intro.md:357 msgid "" "[a code of conduct to defines community interaction standards and " "expectations](/documentation/repository-files/code-of-conduct-file.md)" msgstr "" +"[um code of conduct que define padrões e expectativas de interação da " +"comunidade](/documentation/repository-files/code-of-conduct-file.md)" #: ../../tutorials/intro.md:358 msgid "" -"[a contributing guide that helps users understand expectations associated" -" with making contributions to your project](/documentation/repository-" -"files/contributing-file.md)" +"[a contributing guide that helps users understand expectations associated " +"with making contributions to your " +"project](/documentation/repository-files/contributing-file.md)" msgstr "" +"[um guia de contribuição que ajuda usuários a entender expectativas " +"associadas a contribuições ao seu " +"projeto](/documentation/repository-files/contributing-file.md)" #: ../../tutorials/intro.md:360 msgid "Support for contributors and maintainers" -msgstr "" +msgstr "Suporte para contributors e mantenedores" #: ../../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 " +"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 " "development** guide to help new potential contributors get started with " -"contributing to your package, as well as a **code of conduct** to ensure " +"contributing to your package, as well as a **code of conduct** toensure " "community interactions remain healthy both for you and your contributors " "and maintainer team." msgstr "" +"Se você pretende que outras pessoas usem e contribuam com seu código, " +"considere quem o manterá ao longo do tempo. Você vai querer um **guia de " +"contribuição e desenvolvimento** para ajudar novos contributors potenciais " +"a começar a contribuir com seu pacote, além de um **code of conduct** para " +"garantir que as interações da comunidade permaneçam saudáveis tanto para " +"você quanto para seus contributors e equipe de mantenedores." #: ../../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 " -"want extra help, development, and contributing documentation will help " -"you onboard new maintainers." +"want extra help, development, and contributing documentation will help you " +"onboard new maintainers." msgstr "" +"Os elementos acima também são importantes para a manutenção futura do seu " +"pacote. Caso você não consiga mais mantê-lo ou simplesmente queira ajuda " +"extra, a documentação de desenvolvimento e contribuição ajudará você a " +"integrar novos maintainers." #: ../../tutorials/intro.md:369 msgid "What's next?" -msgstr "" +msgstr "Próximos passos" #: ../../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 " -"for others to contribute to and easier for other scientists to use. " -"However, first we want to get you to your initial goal of publishing a " -"Python package." +"published Python package that makes it both easier to maintain, easier for " +"others to contribute to and easier for other scientists to use. However, " +"first we want to get you to your initial goal of publishing a Python " +"package." msgstr "" +"Em lições futuras você aprenderá mais sobre a infraestrutura em torno de um " +"pacote Python publicado que facilita a manutenção, a contribuição de outras " +"pessoas e o uso por outros cientistas. No entanto, primeiro queremos " +"levá-lo ao seu objetivo inicial de publicarum pacote Python." #: ../../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 " +"In this next lesson you will learn how to create a basic installable Python " +"package. Make your code pip installable " msgstr "" +"Nessa próxima lição você aprenderá como criar um pacote Python básico " +"instalável. Torne seu código pip instalável " #: ../../tutorials/publish-conda-forge.md:6 msgid "Publish your Python package that is on PyPI to conda-forge" -msgstr "" +msgstr "Publique seu pacote Python que está no PyPI no conda-forge" #: ../../tutorials/publish-conda-forge.md:8 msgid "In the previous lessons, you've learned:" -msgstr "" +msgstr "Nas lições anteriores, você aprendeu:" #: ../../tutorials/publish-conda-forge.md:10 msgid "" -"How to [create the most basic version of a Python package](create-python-" -"package.md). This entailed making your code installable." +"How to [create the most basic version of a Python " +"package](create-python-package.md). This entailed making your code " +"installable." msgstr "" +"Como [criar a versão mais básica de um pacote " +"Python](create-python-package.md). Isso envolveu tornar seu código " +"instalável." #: ../../tutorials/publish-conda-forge.md:11 msgid "[How to publish your Python package to PyPI](publish-pypi)" -msgstr "" +msgstr "[Como publicar seu pacote Python no PyPI](publish-pypi)" #: ../../tutorials/publish-conda-forge.md:12 msgid "How to add a `README` and `LICENSE` file to your package" -msgstr "" +msgstr "Como adicionar arquivos `README` e `LICENSE` ao seu pacote" #: ../../tutorials/publish-conda-forge.md:13 msgid "" "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." +"metadata that PyPI requires and also metadata that will be helpfulfor users " +"to find your package." msgstr "" +"Como configurar seu arquivo [pyproject.toml](pyproject-toml) com toda a " +"metadata exigida pelo PyPI e também metadata que ajudará usuários a " +"encontrar seu pacote." #: ../../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 "" +"Se você passou por todas as lições acima, agora está pronto para publicar " +"seu pacote no conda-forge." #: ../../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 " -"pypi.org that you plan to maintain." +"**IMPORTANT:** Please do not practice publishing your package to " +"conda-forge. You should only publish to conda-forge when you have a package " +"on pypi.org that you plan to maintain." msgstr "" +"**IMPORTANTE:** Por favor, não pratique publicar seu pacote no conda-forge. " +"Você só deve publicar no conda-forge quando tiver um pacote no pypi.org que " +"planeja manter." #: ../../tutorials/publish-conda-forge.md:26 ../../tutorials/publish-pypi.md:24 msgid "In this lesson you will learn how to:" -msgstr "" +msgstr "Nesta lição você aprenderá como:" #: ../../tutorials/publish-conda-forge.md:28 msgid "Create a conda-forge yaml recipe for your package using Grayskull" -msgstr "" +msgstr "Criar uma recipe YAML do conda-forge para seu pacote usando Grayskull" #: ../../tutorials/publish-conda-forge.md:29 msgid "" -"Submit the recipe (yaml file) to the conda-forge staged recipes " -"repository as a pull request" +"Submit the recipe (yaml file) to the conda-forge staged recipes repository " +"as a pull request" msgstr "" +"Enviar a recipe (arquivo YAML) para o repositório staged recipes do " +"conda-forge como pull request" #: ../../tutorials/publish-conda-forge.md:30 msgid "" -"Maintain your conda-forge package by creating new releases for your " -"package on PyPI" +"Maintain your conda-forge package by creating new releases for your package " +"on PyPI" msgstr "" +"Manter seu pacote no conda-forge criando novos releases para seu pacote no " +"PyPI" #: ../../tutorials/publish-conda-forge.md:33 #, 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 {term}`Source distribution (sdist)` file." +"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 {term}`Source distribution (sdist)` file." msgstr "" +"Depois que seu pacote estiver no PyPI, você pode publicá-lo facilmente no " +"conda-forge usando a ferramenta " +"[grayskull](https://conda.github.io/grayskull/). Você não precisa fazer " +"build do pacote especificamente para conda; o conda-forge irá construir a " +"partir do arquivo {term}`distribuição fonte (sdist) ` do PyPI." #: ../../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 " -"it into distribution files (sdist and wheel) that PyPI accepts. Then " -"there is an arrow towards the PyPI repository where ou publish both " -"distributions. From PyPI if you create a conda-forge recipe you can then " -"publish to conda-forge." +"Image showing the progression of creating a Python package, building it and " +"then publishing to PyPI and conda-forge. You take your code andturn it into " +"distribution files (sdist and wheel) that PyPI accepts. Then there is an " +"arrow towards the PyPI repository where ou publish both distributions. From " +"PyPI if you create a conda-forge recipe you can then publish to conda-forge." msgstr "" +"Imagem mostrando a progressão de criar um pacote Python, fazer build " +"e publicar no PyPI e conda-forge. Você pega seu código e o transforma " +"em arquivos de distribuição (sdist e wheel) que o PyPI aceita. Depois há uma " +"seta em direção ao repositório PyPI, onde você publica ambas " +"as distribuições. A partir do PyPI, se você criar uma recipe do conda-forge, " +"pode publicar no conda-forge." #: ../../tutorials/publish-conda-forge.md:43 #, python-brace-format msgid "" "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 "" +"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 "" +"Depois que você publicou ambas as distribuições do pacote (a " +"{term}`distribuição fonte (sdist) ` e a " +"{term}`Wheel (.whl)`) no PyPI, pode publicar no conda-forge. O conda-forge " +"exige uma source distribution no PyPI para fazer build do seu pacote no " +"conda-forge. Você não precisa refazer o build do seu pacote para publicar no " +"conda-forge." #: ../../tutorials/publish-conda-forge.md:50 msgid "What is conda-forge?" -msgstr "" +msgstr "O que é conda-forge?" #: ../../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." +"conda is an open source package and environment management tool that can be " +"used to install tools from the different channels on Anaconda.org." msgstr "" +"conda é uma ferramenta open source de gerenciamento de pacotes e ambientes " +"que pode ser usada para instalar ferramentas de diferentes channels no " +"Anaconda.org." #: ../../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 " -"`conda install packagename`. In the case of conda channels, some of these" -" channels such as the `defaults` channel, is managed by Anaconda (the " -"company). Only Anaconda can decide what packages are available in the " +"`conda install packagename`. In the case of conda channels, some of these " +"channels such as the `defaults` channel, is managed by Anaconda (the " +"company). Only Anaconda can decide what packages are available inthe " "`defaults` channel. However, the conda-forge (and bioconda) channel are " -"community-managed channels. Anyone can submit a package to these channels" -" however they must pass a technical review in the [staged-recipes GitHub " -"repository](https://github.com/conda-forge/staged-recipes) to be " -"published." -msgstr "" +"community-managed channels. Anyone can submit a package tothese channels " +"however they must pass a technical review in the [staged-recipes GitHub " +"repository](https://github.com/conda-forge/staged-recipes) to be published." +msgstr "" +"Você pode pensar em um channel como um local específico onde um grupo de " +"pacotes é armazenado e pode ser instalado usando um comando como `conda " +"install packagename`. No caso de conda channels, alguns desses channels, " +"como o channel `defaults`, são gerenciados pela Anaconda (a empresa). " +"Somente a Anaconda decide quais pacotes estão disponíveis no channel " +"`defaults`. No entanto, os channels conda-forge (e bioconda)são gerenciados " +"pela comunidade. Qualquer pessoa pode submeter um pacote a esses channels, " +"porém ele precisa passar por uma revisão técnica no [repositório " +"staged-recipes no GitHub](https://github.com/conda-forge/staged-recipes) " +"para ser publicado." #: ../../tutorials/publish-conda-forge.md:58 msgid "[Learn more about conda channels here.](#about-conda)" -msgstr "" +msgstr "[Saiba mais sobre conda channels aqui.](#about-conda)" #: ../../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 " -"hosted on a conda channel can be installed using conda install. Below " -"that there are two rows. The top row says conda channels. Next to it are " -"three boxes one with conda-forge, community maintained; bioconda and then" -" default - managed by the Anaconda team. Below that there is a row that " -"says PyPI servers. PyPI - anyone can publish to PyPI and test PyPI (a " -"testbed server for you to practice)." -msgstr "" +"Graphic with the title Python package repositories. Below it says anything " +"hosted on PyPI can be installed using pip install. Packaging hosted on a " +"conda channel can be installed using conda install. Below that there are " +"two rows. The top row says conda channels. Next to it are three boxes one " +"with conda-forge, community maintained; bioconda and then default - managed " +"by the Anaconda team. Below that there is arow that says PyPI servers. PyPI " +"- anyone can publish to PyPI and testPyPI (a testbed server for you to " +"practice)." +msgstr "" +"Gráfico com o título Repositórios de pacote Pythons. Abaixo diz que " +"qualquer coisa hospedada no PyPI pode ser instalada usando pip install. " +"Packaging hospedado em um conda channel pode ser instalado usando conda " +"install. Abaixo há duas linhas. A linha superior diz conda channels. Ao " +"lado há três caixas: uma com conda-forge, mantido pela comunidade; " +"bioconda; e default — gerenciado pela equipe Anaconda. Abaixo há uma linha " +"que diz servidores PyPI. PyPI — qualquer pessoa pode publicar no PyPI e test " +"PyPI (um servidor de testes para você praticar)." #: ../../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 " -"submit a recipe there. PyPI is also a community maintained repository. " -"Anyone can submit a package to PyPI and test PyPI. Unlike conda-forge " -"there are no manual checks of packages submitted to PyPI." +"Conda channels represent various repositories that you can install packages " +"from. Because conda-forge is community maintained, anyone cansubmit a " +"recipe there. PyPI is also a community maintained repository.Anyone can " +"submit a package to PyPI and test PyPI. Unlike conda-forge there are no " +"manual checks of packages submitted to PyPI." msgstr "" +"Conda channels representam vários repositórios de onde você pode instalar " +"pacotes. Como o conda-forge é mantido pela comunidade, qualquer pessoa pode " +"submeter uma recipe lá. O PyPI também é um repositório mantido pela " +"comunidade. Qualquer pessoa pode submeter um pacote ao PyPI e ao test PyPI. " +"Diferentemente do conda-forge, não há verificações manuais de pacotes " +"submetidos ao PyPI." #: ../../tutorials/publish-conda-forge.md:67 msgid "Why publish to conda-forge" -msgstr "" +msgstr "Por que publicar no conda-forge" #: ../../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, " -"having packages available to these users on the conda-forge channel is " -"useful. In some cases packages on conda-forge can minimize dependency " -"conflicts that can occur when mixing installations using pip and conda. " -"This is particularly important for the spatial ecosystem." -msgstr "" +"use conda as their primary package manager / environment tool. Thus, having " +"packages available to these users on the conda-forge channel is useful. In " +"some cases packages on conda-forge can minimize dependency conflicts that " +"can occur when mixing installations using pip and conda. This is " +"particularly important for the spatial ecosystem." +msgstr "" +"Existem muitos usuários, especialmente no ecossistema científico Python, " +"que usam conda como seu gerenciador de pacotes / ferramenta deambientes " +"principal. Assim, ter pacotes disponíveis para esses usuários no channel " +"conda-forge é útil. Em alguns casos, pacotes no conda-forge podem minimizar " +"conflitos de dependências que podem ocorrer ao misturar instalações usando " +"pip e conda. Isso é particularmente importante para o ecossistema espacial." #: ../../tutorials/publish-conda-forge.md:71 msgid "How publishing to conda-forge works" -msgstr "" +msgstr "Como funciona a publicação no conda-forge" #: ../../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 " -"additional build step needed to publish to conda-forge." +"Once you have built and published your package to PyPI, you have everything " +"that you need to publish to conda-forge. There is no additional build step " +"needed to publish to conda-forge." msgstr "" +"Depois de fazer o build e publicar seu pacote no PyPI, você tem tudo o que " +"precisa para publicar no conda-forge. Não há etapa adicional de build " +"necessária para publicar no conda-forge." #: ../../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 " -"recipe that you will create below." +"Conda-forge will build your package from the source distribution whichyou " +"[published to PyPI in the previous lesson](publish-pypi) using therecipe " +"that you will create below." msgstr "" +"O conda-forge fará o build do seu pacote a partir da source distribution " +"que você [publicou no PyPI na lição anterior](publish-pypi), usando a " +"recipe que você criará abaixo." #: ../../tutorials/publish-conda-forge.md:77 msgid "Conda-forge publication steps" -msgstr "" +msgstr "Etapas de publicação no conda-forge" #: ../../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 "" +"Imagem mostrando as etapas associadas à publicação no conda-forge. Consulte " +"a legenda abaixo para uma descrição detalhada." #: ../../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 " -"yaml file recipe that can be submitted to the conda-forge staged recipes " -"repository for review. Once that recipe is accepted, your package will " -"get it's on repository (known as a feedstock) on conda-forge." -msgstr "" +"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 yaml " +"file recipe that can be submitted to the conda-forge staged recipes " +"repository for review. Once that recipe is accepted, your package will get " +"it's on repository (known as a feedstock) on conda-forge." +msgstr "" +"As etapas para publicar no conda-forge começam com a publicação do " +"seu pacote Python no PyPI. Depois de publicar no PyPI, você pode criar " +"um arquivo yaml de recipe que pode ser submetido ao repositório staged " +"recipes do conda-forge para revisão. Depois que essa recipe for aceita, seu " +"pacote terá seu próprio repositório (conhecido como feedstock) no " +"conda-forge." #: ../../tutorials/publish-conda-forge.md:85 msgid "The steps to publish to conda-forge are:" -msgstr "" +msgstr "As etapas para publicar no conda-forge são:" #: ../../tutorials/publish-conda-forge.md:87 msgid "Publish your Python package distribution files (sdist & wheel) to PyPI" msgstr "" +"Publique os arquivos de distribuição do seu pacote Python (sdist e wheel) " +"no PyPI" #: ../../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]" -" package." +"Create a conda-forge recipe, which is a yaml file with instructions onhow " +"to build your package on conda-forge, using the grayskull[^grayskull] " +"package." msgstr "" +"Crie uma recipe conda-forge, que é um arquivo yaml com instruções sobre " +"como fazer o build do seu pacote no conda-forge, usando o " +"pacote grayskull[^grayskull]." #: ../../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 " -"submission from pyOpenSci.](https://github.com/conda-forge/staged-" -"recipes/pull/25173)" +"Submit the recipe (yaml file) to the conda-forge staged recipes repository " +"as a pull request for review. [Click here for an example submission from " +"pyOpenSci.](https://github.com/conda-forge/staged-recipes/pull/25173)" msgstr "" +"Submeta a recipe (arquivo yaml) ao repositório staged recipes do " +"conda-forge como um pull request para revisão. [Clique aqui para ver um " +"exemplo de submissão do " +"pyOpenSci.](https://github.com/conda-forge/staged-recipes/pull/25173)" #: ../../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 " -"and merged." +"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 and " +"merged." msgstr "" +"Depois que alguém da equipe conda-forge revisar seu pull request, você pode " +"precisar fazer algumas alterações. Eventualmente o pull request será " +"aprovado e merged." #: ../../tutorials/publish-conda-forge.md:93 msgid "" -"Once your recipe is accepted and merged on conda-forge, users can install" -" your package using:" +"Once your recipe is accepted and merged on conda-forge, users can install " +"your package using:" msgstr "" +"Depois que sua recipe for aceita e merged no conda-forge, os usuários " +"poderão instalar seu pacote usando:" #: ../../tutorials/publish-conda-forge.md:95 msgid "`conda install -c conda-forge your-package`" -msgstr "" +msgstr "`conda install -c conda-forge your-package`" #: ../../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 "" +"Você cria a recipe apenas uma vez. Depois que a recipe for aceita e merged, " +"você só precisa manter o repositório." #: ../../tutorials/publish-conda-forge.md:99 msgid "Maintaining a conda-forge package" -msgstr "" +msgstr "Mantendo um pacote conda-forge" #: ../../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 " -"release with a new source distribution, conda-forge will build and update" -" your conda-forge repository (also known as a feedstock)." +"Once your package is on conda-forge, the repository will track " +"releaseactivity on the package's PyPI repository. Any time you make a new " +"PyPI release with a new source distribution, conda-forge will build and " +"update your conda-forge repository (also known as a feedstock)." msgstr "" +"Depois que seu pacote estiver no conda-forge, o repositório acompanhará a " +"atividade de release no repositório PyPI do pacote. Sempre que você fizer " +"um novo release no PyPI com uma nova source distribution, o conda-forge " +"fará o build e atualizará seu repositório conda-forge (também conhecido " +"como feedstock)." #: ../../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." +"When the update is processed, the friendly conda-forge bot will createa new " +"pull request with an updated distribution recipe in your feedstock." msgstr "" +"Quando a atualização for processada, o amigável bot conda-forge criará um " +"novo pull request com uma recipe de distribuição atualizada no seu " +"feedstock." #: ../../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 "" +"Você pode revisar esse pull request e depois fazer merge assim que todos os " +"testes de integração contínua passarem." #: ../../tutorials/publish-conda-forge.md:107 msgid "" -" How to Publish your package" -" on conda-forge" +" How to Publish your package on " +"conda-forge" msgstr "" +" Como publicar seu pacote no " +"conda-forge" #: ../../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 " -"also remember that the team managing conda-forge are all volunteers." +"your package needs to be on PyPI before the steps below will work. And also " +"remember that the team managing conda-forge are all volunteers." msgstr "" +"É hora de adicionar seu pacote ao channel conda-forge. Lembre-se de que seu " +"pacote precisa estar no PyPI antes que as etapas abaixo funcionem. E " +"lembre-se também de que a equipe que gerencia o conda-forge é formada por " +"voluntários." #: ../../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 "" +"Certifique-se de que seu pacote está no PyPI.org (não no test.pypi.org) " +"antes de tentar publicar no conda-forge." #: ../../tutorials/publish-conda-forge.md:115 msgid "" -"Only submit your package to conda-forge if you intend to maintain it over" -" time." +"Only submit your package to conda-forge if you intend to maintain it over " +"time." msgstr "" +"Submeta seu pacote ao conda-forge somente se você pretende mantê-lo ao longo " +"do tempo." #: ../../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 " +"Note - this is a tutorial aimed to help you get your package onto " +"conda-forge. The official conda documentation for this processed [is " "here](https://conda-forge.org/docs/maintainer/adding_pkgs.html)." msgstr "" +"Nota: este é um tutorial destinado a ajudá-lo a colocar seu pacote " +"no conda-forge. A documentação oficial do conda para esse processo [está " +"aqui](https://conda-forge.org/docs/maintainer/adding_pkgs.html)." #: ../../tutorials/publish-conda-forge.md:120 msgid "Step 1: Install grayskull" -msgstr "" +msgstr "Etapa 1: Instalar grayskull" #: ../../tutorials/publish-conda-forge.md:122 msgid "" "First, [install " -"grayskull](https://conda.github.io/grayskull/user_guide.html). You can " -"install it using either pip:" +"grayskull](https://conda.github.io/grayskull/user_guide.html). You " +"caninstall it using either pip:" msgstr "" +"Primeiro, [instale o " +"grayskull](https://conda.github.io/grayskull/user_guide.html). Você pode " +"instalá-lo usando pip:" #: ../../tutorials/publish-conda-forge.md:128 msgid "or conda" -msgstr "" +msgstr "ou conda" #: ../../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." +"To run this command, use the same shell / terminal that you have been using " +"to run hatch commands in the previous tutorials." msgstr "" +"Para executar este comando, use o mesmo shell / terminal que você usou para " +"executar comandos hatch nos tutoriais anteriores." #: ../../tutorials/publish-conda-forge.md:139 msgid "" @@ -4541,36 +4749,46 @@ msgid "" "available across multiple Python environments rather than installing the " "package into every Python environment that you create." msgstr "" +"Você também pode instalar o grayskull usando pipx[^pipx]. pipx é uma " +"ferramenta que permite instalar ferramentas comumente usadas que você pode " +"querer ter disponíveis em vários ambientes Python, em vez de instalar o " +"pacote em cada ambiente Python que você cria." #: ../../tutorials/publish-conda-forge.md:142 msgid "Step 2: Fork and clone the conda-forge staged-recipes repository" -msgstr "" +msgstr "Etapa 2: Fazer fork e clonar o repositório staged-recipes do conda-forge" #: ../../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 "" +"Em seguida, abra seu shell e `cd` para um local onde você quer clonar o " +"repositório **conda-forge/staged-recipes**." #: ../../tutorials/publish-conda-forge.md:145 msgid "" "fork and clone the [conda-forge/staged-recipes GitHub " "repository](https://github.com/conda-forge/staged-recipes)." msgstr "" +"faça fork e clone o [repositório conda-forge/staged-recipes no " +"GitHub](https://github.com/conda-forge/staged-recipes)." #: ../../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 "" +"Crie um novo branch no seu fork em vez de submeter a partir do branch main " +"do seu fork. Sugerimos nomear o branch com o nome do seu pacote." #: ../../tutorials/publish-conda-forge.md:148 msgid "`git checkout -b your-package-name `" -msgstr "" +msgstr "`git checkout -b your-package-name `" #: ../../tutorials/publish-conda-forge.md:150 msgid "In bash, `cd` into the `staged-recipes/recipes` folder" -msgstr "" +msgstr "No bash, `cd` para a pasta `staged-recipes/recipes`" #: ../../tutorials/publish-conda-forge.md:158 msgid "" @@ -4578,296 +4796,397 @@ msgid "" "repository. You might want to make that branch the same name as your " "package." msgstr "" +"Em seguida, crie um novo branch no repositório clonado " +"`conda-forge/staged-recipes`. Você pode querer que esse branch tenha o mesmo " +"nome do seu pacote." #: ../../tutorials/publish-conda-forge.md:169 msgid "Step 3: Create your conda-forge recipe" -msgstr "" +msgstr "Etapa 3: Criar sua recipe conda-forge" #: ../../tutorials/publish-conda-forge.md:171 msgid "Next, navigate to the recipes directory" -msgstr "" +msgstr "Em seguida, navegue até o diretório recipes" #: ../../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." +"If you run `ls` here, you will notice there is an example directory with an " +"example recipe for you to look at." msgstr "" +"Se você executar `ls` aqui, notará que há um diretório de exemplo com uma " +"recipe de exemplo para você consultar." #: ../../tutorials/publish-conda-forge.md:185 msgid "Next, run `grayskull pypi your-package-name` to generate a recipe." msgstr "" +"Em seguida, execute `grayskull pypi your-package-name` para gerar uma " +"recipe." #: ../../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." +"Grayskull will pull metadata about your package from PyPI. It does not use " +"your local installation of the package." msgstr "" +"O Grayskull buscará metadata sobre seu pacote no PyPI. Ele não usa " +"sua instalação local do pacote." #: ../../tutorials/publish-conda-forge.md:230 msgid "" -"An internet connection is needed to run the `grayskull pypi your-package-" -"name` step." +"An internet connection is needed to run the `grayskull pypi " +"your-package-name` step." msgstr "" +"Uma conexão com a internet é necessária para executar a etapa `grayskull " +"pypi your-package-name`." #: ../../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 "" +"Quando você executar grayskull, ele obterá a distribuição mais recente do " +"seu pacote no PyPI e usará isso para criar uma nova recipe." #: ../../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 "" +"A recipe será salva em um diretório nomeado com o nome do seu pacote, onde " +"quer que você execute o comando." #: ../../tutorials/publish-conda-forge.md:237 msgid "`recipes/packagename/meta.yaml`" -msgstr "" +msgstr "`recipes/packagename/meta.yaml`" #: ../../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." +"At the very bottom of the grayskull output, it will also tell you where it " +"saved the recipe file." msgstr "" +"Na parte inferior da saída do grayskull, ele também informará onde salvou o " +"arquivo de recipe." #: ../../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 "" +"Abra o arquivo meta.yaml. O arquivo `meta.yaml` final que o grayskull cria " +"deve se parecer com o exemplo abaixo:" #: ../../tutorials/publish-conda-forge.md:289 msgid "Step 3b: Bug fix - add a home url to the about: section" -msgstr "" +msgstr "Etapa 3b: Correção de bug — adicionar uma home url à seção about" #: ../../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 " -"receive an error message](https://github.com/conda-forge/staged-" -"recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" -" linter bot." +"There is currently a small bug in Grayskull where it doesn't populate the " +"home: element of the recipe. If you don't include this, [you will receive " +"an error " +"message](https://github.com/conda-forge/staged-recipes/pull/25173#issuecomme" +"nt-1917916528)fromthefriendlyconda-forgelinterbot." msgstr "" +"Atualmente há um pequeno bug no Grayskull em que ele não preenche o " +"elemento home: da recipe. Se você não incluir isso, [receberá uma mensagem " +"de " +"erro](https://github.com/conda-forge/staged-recipes/pull/25173#issuecomment-" +"1917916528)doamigávelbotlinter do conda-forge." #: ../../tutorials/publish-conda-forge.md:305 msgid "to fix this, open your meta.yaml file in your favorite text editor." msgstr "" +"para corrigir isso, abra seu arquivo meta.yaml no seu editor de texto " +"favorito." #: ../../tutorials/publish-conda-forge.md:306 msgid "and add a home: element to the about section" -msgstr "" +msgstr "e adicione um elemento home: à seção about" #: ../../tutorials/publish-conda-forge.md:308 msgid "The about section will look like this after you create your recipe." -msgstr "" +msgstr "A seção about ficará assim depois que você criar sua recipe." #: ../../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." msgstr "" +"Abaixo você adiciona um elemento home:. Se você tiver uma home page / " +"website do projeto, pode usar essa url. Caso contrário, você também pode " +"usar sua landing page no PyPI." #: ../../tutorials/publish-conda-forge.md:329 msgid "Step 4: tests for conda-forge" -msgstr "" +msgstr "Etapa 4: testes para conda-forge" #: ../../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 " -"with your package and run `pip check`." +"minimum you should import your package or the main modules associated with " +"your package and run `pip check`." msgstr "" +"Em seguida, dê uma olhada na seção tests do seu arquivo **meta.yaml**. No " +"mínimo, você deve importar seu pacote ou os principais modules associados " +"ao seu pacote e executar `pip check`." #: ../../tutorials/publish-conda-forge.md:333 msgid "" -"`pip check` will ensure that your package installs properly with all of " -"the proper dependencies." +"`pip check` will ensure that your package installs properly with all of the " +"proper dependencies." msgstr "" +"`pip check` garantirá que seu pacote seja instalado corretamente com todas " +"as dependências adequadas." #: ../../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." +"If you have more advanced tests that you wish to run, you can add themhere. " +"However, you can also simply leave the tests section as it is." msgstr "" +"Se você tiver testes mais avançados que deseja executar, pode adicioná-los " +"aqui. No entanto, você também pode simplesmente deixar a seção tests como " +"está." #: ../../tutorials/publish-conda-forge.md:347 msgid "Step 4: Submit a pull request to the staged-recipes repository" -msgstr "" +msgstr "Etapa 4: Submeter um pull request ao repositório staged-recipes" #: ../../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`." +"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 "" +"Depois de concluir tudo acima, você está pronto para abrir um pull request " +"no repositório `conda-forge/staged-recipes`." #: ../../tutorials/publish-conda-forge.md:351 msgid "" "Submit a pull request from your fork/branch of the staged-recipes " "repository." msgstr "" +"Submeta um pull request a partir do fork/branch do repositório " +"staged-recipes." #: ../../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." msgstr "" +"Lembre-se de que os maintainers do conda-forge são voluntários. Seja " +"paciente aguardando uma resposta e colaborativo na comunicação com eles." #: ../../tutorials/publish-conda-forge.md msgid "Conda-forge checklist help" -msgstr "" +msgstr "Ajuda com checklist do conda-forge" #: ../../tutorials/publish-conda-forge.md:358 msgid "Conda-forge Staged-recipes Pull Request Checklist" -msgstr "" +msgstr "Checklist de pull request do Staged-recipes conda-forge" #: ../../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." +"When you submit your package to conda-forge, the pull request " +"templateincludes a list of checks that you want to ensure you have covered." msgstr "" +"Quando você submete seu pacote ao conda-forge, o template de pull request " +"inclui uma lista de verificações que você deve garantir ter coberto." #: ../../tutorials/publish-conda-forge.md:362 msgid "Below we break down each element of that list." -msgstr "" +msgstr "Abaixo detalhamos cada elemento dessa lista." #: ../../tutorials/publish-conda-forge.md:364 msgid "Pull request template checklist tips" -msgstr "" +msgstr "Dicas do checklist do template de pull request" #: ../../tutorials/publish-conda-forge.md:367 msgid "" -"-[x] Title of this PR is meaningful: e.g. \"Adding my_nifty_package\", " -"not \"updated meta.yaml\"." +"-[x] Title of this PR is meaningful: e.g. \"Adding my_nifty_package\",not " +"\"updated meta.yaml\"." msgstr "" +"-[x] O título deste PR é significativo: por exemplo, \"Adding " +"my_nifty_package\", não \"updated meta.yaml\"." #: ../../tutorials/publish-conda-forge.md:369 msgid "" "**Translation:** Make sure that your pull request title is specific. We " "suggest something like: `Add recipe for `" msgstr "" +"**Tradução:** Certifique-se de que o título do seu pull request seja " +"específico. Sugerimos algo como: `Add recipe for `" #: ../../tutorials/publish-conda-forge.md:372 msgid "" -"-[x] License file is packaged (see [here](https://github.com/conda-forge" -"/staged-" -"recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73)" -" for an example)." +"-[x] License file is packaged (see " +"[here](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169" +"089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73)foranexample)." msgstr "" +"-[x] O arquivo LICENSE está incluído no pacote (veja " +"[aqui](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169" +"089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73)umexemplo)." #: ../../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 " -"tutorials then you already have a LICENSE file and are likely using the " -"MIT license. When you run `hatch build`, it will bundle that file into " -"the output [source distribution file (which is the tar.gz file)](python-" -"source-distribution) that conda-forge will use to build your package." +"**Translation:** You should have a LICENSE file included in your package's " +"source distribution. If you have followed the pyOpenSci tutorials then you " +"already have a LICENSE file and are likely using the MIT license. When you " +"run `hatch build`, it will bundle that file into the output [source " +"distribution file (which is the tar.gz file)](python-source-distribution) " +"that conda-forge will use to build your package." msgstr "" +"**Tradução:** Você deve ter um arquivo LICENSE incluído na source " +"distribution do seu pacote. Se você seguiu os tutoriais do pyOpenSci, já tem " +"um arquivo LICENSE e provavelmente está usando a licença MIT. Quando você " +"executar `hatch build`, ele incluirá esse arquivo na [source distribution " +"(que é o arquivo tar.gz)](python-source-distribution) que o conda-forge " +"usará para fazer o build do seu pacote." #: ../../tutorials/publish-conda-forge.md:376 msgid "[x] Source is from official source." -msgstr "" +msgstr "[x] A source é de uma fonte oficial." #: ../../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 " -"you are in good shape. conda-forge prefers that your distribution is " -"published to a known repository." +"**Translation:** If your package is on PyPI as you learned in the [previous " +"lesson on publishing your Python package](publish-pypi) thenyou are in good " +"shape. conda-forge prefers that your distribution is published to a known " +"repository." msgstr "" +"**Tradução:** Se seu pacote está no PyPI, como você aprendeu na " +"[lição anterior sobre publicar seu pacote Python](publish-pypi), você está " +"em boa forma. O conda-forge prefere que sua distribuição seja publicada em " +"um repositório conhecido." #: ../../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 " -"licenses of all packages need to be packaged)." +"-[x] Package does not vendor other packages. (If a package uses the source " +"of another package, they should be separate packages or the licenses of all " +"packages need to be packaged)." msgstr "" +"-[x] O pacote não inclui (vendor) outros pacotes. (Se um pacote usa o source " +"de outro pacote, eles devem ser pacotes separados ou as licenças de todos " +"os pacotes precisam ser incluídas)." #: ../../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 " -"taken from other packages then you may need to declare that and include " -"licenses for that code if it is different. If you followed these " -"tutorials then you do not have any vendored code." +"shares the same LICENSE then you are in good shape. If you have code taken " +"from other packages then you may need to declare that and include licenses " +"for that code if it is different. If you followed these tutorials then you " +"do not have any vendored code." msgstr "" +"**Tradução:** Se a base de código do seu pacote é sua e tudo compartilha a " +"mesma LICENSE, você está em boa forma. Se você tem código retirado de " +"outros pacotes, pode precisar declarar isso e incluir licenças para esse " +"código se for diferente. Se você seguiu estes tutoriais, não tem nenhum " +"código vendored." #: ../../tutorials/publish-conda-forge.md:384 msgid "" -"-[x] If static libraries are linked in, the license of the static library" -" is packaged." +"-[x] If static libraries are linked in, the license of the static library " +"is packaged." msgstr "" +"-[x] Se bibliotecas estáticas forem linkadas, a licença da biblioteca " +"estática está incluída no pacote." #: ../../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-" -"forge/cfep/blob/main/cfep-18.md)." +"needed, [follow " +"CFEP-18](https://github.com/conda-forge/cfep/blob/main/cfep-18.md)." msgstr "" +"-[x] O pacote não distribui bibliotecas estáticas. Se bibliotecas estáticas " +"forem necessárias, [siga o " +"CFEP-18](https://github.com/conda-forge/cfep/blob/main/cfep-18.md)." #: ../../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" -" check that your package does not ship static libraries as this does not " -"apply to you." +"**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 check " +"that your package does not ship static libraries as this does not apply to " +"you." msgstr "" +"**Tradução:** Uma biblioteca estática refere-se a uma cópia de um pacote " +"incorporada ao seu pacote. Se seu pacote é um pacote puro Python, você pode " +"marcar que seu pacote não distribui bibliotecas estáticas, pois isso não se " +"aplica a você." #: ../../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) " +"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 "" +"Os tutoriais do pyOpenSci são todos pure Python e, como tal, não usam " +"bibliotecas estáticas em formato linkado ou shipped (incluído na " +"distribuição do pacote)." #: ../../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." +"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 "" +"Se seu pacote tem um build mais complexo que inclui links para extensões " +"escritas em outras linguagens, como C++, certifique-se de incluir as " +"licenças adequadas para essas extensões no seu metadata." #: ../../tutorials/publish-conda-forge.md:397 msgid "" "If you want to learn more about static libraries, then [this " -"overview](https://pypackaging-" -"native.github.io/background/compilation_concepts/#shared-vs-static-" -"libraries) might help." +"overview](https://pypackaging-native.github.io/background/compilation_concep" +"ts/#shared-vs-static-libraries)mighthelp." msgstr "" +"Se você quiser saber mais sobre bibliotecas estáticas, [esta visão " +"geral](https://pypackaging-native.github.io/background/compilation_concepts/" +"#shared-vs-static-libraries)podeajudar." #: ../../tutorials/publish-conda-forge.md:400 msgid "-[ ] Build number is 0." -msgstr "" +msgstr "-[ ] O build number é 0." #: ../../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 " -"what you should see in that section of your recipe." +"**Translation:** The build number in your recipe is right below the source " +"location of your package's source distribution. `number: 0` is what you " +"should see in that section of your recipe." msgstr "" +"**Tradução:** O numero da sua build recipe fica logo abaixo da localização " +"da source distribution do seu pacote. `number: 0` é o que você deve ver " +"nessa seção da sua recipe." #: ../../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-" -"forge.org/docs/maintainer/adding_pkgs.html) for more details)." +"[x] A tarball (`url`) rather than a repo (e.g. `git_url`) is used in your " +"recipe (see " +"[here](https://conda-forge.org/docs/maintainer/adding_pkgs.html) for more " +"details)." msgstr "" +"[x] Um tarball (`url`) em vez de um repo (por exemplo, `git_url`) é usado " +"na sua recipe (veja " +"[aqui](https://conda-forge.org/docs/maintainer/adding_pkgs.html) mais " +"detalhes)." #: ../../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 " -"distribution. Notice above in the Source section of your recipe there is " -"a `url:` section that provides a PyPI url that ends in tar.gz. That is a " -"link to your source distribution that conda-forge will use." +"distribution. Notice above in the Source section of your recipe there is a " +"`url:` section that provides a PyPI url that ends in tar.gz. Thatis a link " +"to your source distribution that conda-forge will use." msgstr "" +"**Tradução:** Aqui o conda quer que você forneça um link para a " +"source distribution no PyPI em vez de um link para a distribuição do seu " +"repositório GitHub. Observe acima na seção Source da sua recipe que há uma " +"seção `url:` que fornece uma url do PyPI terminando em tar.gz. Esse é um " +"link para sua source distribution que o conda-forge usará." #: ../../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] Usuários do GitHub listados na seção maintainer postaram um comentário " +"confirmando que estão dispostos a ser listados lá." #: ../../tutorials/publish-conda-forge.md:425 msgid "" @@ -4876,45 +5195,64 @@ msgid "" "with being listed as a maintainer for the conda-forge version of your " "package." msgstr "" +"**Tradução** Depois de submeter sua recipe, certifique-se de que todos os " +"maintainers listados na sua recipe respondam confirmando que concordam em " +"ser listados como maintainer da versão conda-forge do seu package." #: ../../tutorials/publish-conda-forge.md:427 msgid "" "[x] When in trouble, please check our [knowledge base " -"documentation](https://conda-" -"forge.org/docs/maintainer/knowledge_base.html) before pinging a team." +"documentation](https://conda-forge.org/docs/maintainer/knowledge_base.html)b" +"eforepingingateam." msgstr "" +"[x] Em caso de problemas, consulte nossa [documentação da base de " +"conhecimento](https://conda-forge.org/docs/maintainer/knowledge_base.html)an" +"tesdemencionarumaequipe." #: ../../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 " -"before tagging one of them for help." +"supporting our community. Please try to troubleshoot on your own " +"firstbefore tagging one of them for help." msgstr "" +"**Tradução** A equipe conda são voluntários que dedicam seu tempo " +"para apoiar nossa comunidade. Tente resolver por conta própria antes " +"de marcar um deles para pedir ajuda." #: ../../tutorials/publish-conda-forge.md:431 msgid "" -"This is also why we don't suggest you publish to conda-forge as a " -"practice run." +"This is also why we don't suggest you publish to conda-forge as a practice " +"run." msgstr "" +"É por isso também que não sugerimos publicar no conda-forge como um " +"exercício de prática." #: ../../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 " -"work with you to get your recipe in good shape and merged." +"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 work with " +"you to get your recipe in good shape and merged." msgstr "" +"Depois de criar seu pull request, um conjunto de ações de CI será executado " +"que faz o build e testa o build do seu pacote. Um maintainer do conda-forge " +"trabalhará com você para deixar sua recipe em boa forma e fazer merge." #: ../../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." +"Image showing the 5 CI tasks that will run against your package in " +"the GitHub interface after you've created a pull request." msgstr "" +"Imagem mostrando as 5 tarefas de CI que serão executadas contra seu pacote " +"na interface do GitHub depois que você criar um pull request." #: ../../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." +"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." msgstr "" +"Aguarde até que todas as etapas de CI do seu pull request tenham sido " +"executadas. Nesse ponto, seu pull request está pronto para revisão por um " +"maintainer do conda-forge." #: ../../tutorials/publish-conda-forge.md:444 msgid "" @@ -4922,74 +5260,107 @@ msgid "" "take a bit of work. If you are struggling to get your recipe to build " "properly, you can ping the conda-forge maintainer team for help." msgstr "" +"Em alguns casos, fazer com que todas as verificações passem com sucesso no " +"CI pode exigir um pouco de trabalho. Se você estiver com dificuldade para " +"fazer sua recipe buildar corretamente, pode mencionara equipe de " +"maintainers do conda-forge para pedir ajuda." #: ../../tutorials/publish-conda-forge.md:446 msgid "Please be patient and wait for them to respond." -msgstr "" +msgstr "Seja paciente e aguarde a resposta deles." #: ../../tutorials/publish-conda-forge.md:448 msgid "conda-forge staged recipes and CI failures" -msgstr "" +msgstr "staged recipes do conda-forge e falhas de CI" #: ../../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 " -"requirements (known as noarch: Python or no architecture requirements) " -"then the conda-forge team only requires tests for Linux CI to pass." +"If your package is a pure Python package that can be installed on any type " +"of computer (Windows, mac, linux) and has no architecture requirements " +"(known as noarch: Python or no architecture requirements)then the " +"conda-forge team only requires tests for Linux CI to pass." msgstr "" +"Se seu pacote é um pure pacote Python que pode ser instalado em qualquer " +"tipo de computador (Windows, mac, linux) e não tem requisitosde arquitetura " +"(conhecido como noarch: Python ou sem requisitos de arquitetura), a equipe " +"conda-forge exige apenas que os testes de CI Linux passem." #: ../../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 " -"get your package published." +"case, don't worry about failing tests, the maintainer team can help you get " +"your package published." msgstr "" +"Então, se os testes para Windows e MAC OS falharem, isso é esperado. Nesse " +"caso, não se preocupe com testes falhando; a equipe de maintainers pode " +"ajudá-lo a publicar seu pacote." #: ../../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 " -"maintainer can likely help you figure things out." +"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 maintainer can " +"likely help you figure things out." msgstr "" +"Depois de submeter sua recipe, você pode aguardar o build de CI passar. Se " +"não estiver passando e você não souber por quê, um maintainer do " +"conda-forge provavelmente pode ajudá-lo a descobrir." #: ../../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 " +"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 " "package](https://github.com/conda-forge/gemgis-feedstock)." msgstr "" +"Depois que sua recipe for construida e merged, a equipe conda criará um novo " +"repositório de pacote para você, semelhante a [este do pacote " +"GemGIS](https://github.com/conda-forge/gemgis-feedstock)." #: ../../tutorials/publish-conda-forge.md:460 msgid "" -" Congratulations - you " -"have added your package to conda-forge." +" Congratulations - you have " +"added your package to conda-forge." msgstr "" +" Parabéns — você adicionou " +"seu pacote ao conda-forge." #: ../../tutorials/publish-conda-forge.md:462 msgid "" -"The last part of this process is maintaining the repository. We cover " -"that next." +"The last part of this process is maintaining the repository. We cover that " +"next." msgstr "" +"A última parte deste processo é manter o repositório. Cobrimos isso a " +"seguir." #: ../../tutorials/publish-conda-forge.md:465 msgid "Maintaining your conda-forge feedstock" -msgstr "" +msgstr "Mantendo seu feedstock conda-forge" + + + + + #: ../../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" -" package. This process may take a day or two to complete so be patient." +"Every time you create a new release on PyPI, the conda-forge bots " +"will recognize the release and will rebuild the newly released version of " +"your package. This process may take a day or two to complete so be patient." msgstr "" +"Toda vez que você criar um novo release no PyPI, os bots do conda-forge " +"reconhecerão o release e farão rebuild da versão recém-lançada do seu " +"pacote. Esse processo pode levar um ou dois dias para concluir, então seja " +"paciente." #: ../../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 " +"Once the conda-forge build is complete, all of the maintainers of " +"your conda-forge feedstock will get a ping on GitHub that a new pull request " "has been opened." msgstr "" +"Quando o build do conda-forge estiver concluído, todos os maintainers do " +"seu feedstock conda-forge receberão uma menção no GitHub informando que um " +"novo pull request foi aberto." #: ../../tutorials/publish-conda-forge.md:471 msgid "" @@ -4997,119 +5368,148 @@ msgid "" "Shortly after merging your pull request, the conda-forge release will be " "available for users to install:" msgstr "" +"Revise o pull request. Se todos os testes estiverem passando, você pode " +"fazer merge. Um pouco depois de fazer merge do seu pull request, o release " +"conda-forge estará disponível para os usuários instalarem:" #: ../../tutorials/publish-conda-forge.md:473 msgid "`conda install -c conda-forge yourpackage`" -msgstr "" +msgstr "`conda install -c conda-forge yourpackage`" #: ../../tutorials/publish-conda-forge.md:477 msgid "If you have walked through this entire tutorial series you will now:" -msgstr "" +msgstr "Se você percorreu toda esta série de tutoriais, agora você:" #: ../../tutorials/publish-conda-forge.md:479 msgid "Understand [what a Python package is ](intro.md)" -msgstr "" +msgstr "Entende [o que é um pacote Python ](intro.md)" #: ../../tutorials/publish-conda-forge.md:480 msgid "" "Know how to [make your code installable](create-python-package.md) into " "Python environments" msgstr "" +"Sabe como [tornar seu código instalável](create-python-package.md) em " +"ambientes Python" #: ../../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 "" +"Sabe como criar um arquivo `pyproject.toml`, um arquivo `README`, um " +"`LICENSE` e um code of conduct." #: ../../tutorials/publish-conda-forge.md:482 msgid "Know how to [publish your package to PyPI](publish-pypi.md) and" -msgstr "" +msgstr "Sabe como [publicar seu pacote no PyPI](publish-pypi.md) e" #: ../../tutorials/publish-conda-forge.md:483 msgid "Know how to publish your package to conda-forge" -msgstr "" +msgstr "Sabe como publicar seu pacote no conda-forge" #: ../../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 " -"of maintaining your package." +"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 of " +"maintaining your package." msgstr "" +"Os itens acima são as etapas básicas que você precisa seguir para criar e " +"publicar um pacote Python. Em uma futura série de tutoriais, cobriremos o " +"básico de manter seu pacote." #: ../../tutorials/publish-conda-forge.md:489 msgid "[Grayskull blogpost](https://conda-forge.org/blog/2020/03/05/grayskull/)" -msgstr "" +msgstr "[Post do blog Grayskull](https://conda-forge.org/blog/2020/03/05/grayskull/)" #: ../../tutorials/publish-conda-forge.md:490 msgid "[Pipx documentation](https://pipx.pypa.io/stable/)" -msgstr "" +msgstr "[Documentação do Pipx](https://pipx.pypa.io/stable/)" #: ../../tutorials/publish-pypi.md:7 msgid "Publish your Python package to PyPI" -msgstr "" +msgstr "Publique seu pacote Python no PyPI" #: ../../tutorials/publish-pypi.md:11 msgid "Make sure they add /dist to their .gitignore file. Where does that fit?" msgstr "" +"Certifique-se de que eles adicionem /dist ao arquivo .gitignore. Onde isso " +"se encaixa?" #: ../../tutorials/publish-pypi.md:15 msgid "In the previous Python packaging lessons, you've learned:" -msgstr "" +msgstr "Nas lições anteriores de empacotamento Python, você aprendeu:" #: ../../tutorials/publish-pypi.md:17 msgid "What a Python package is" -msgstr "" +msgstr "O que é um pacote Python" #: ../../tutorials/publish-pypi.md:18 msgid "How to make your code installable." -msgstr "" +msgstr "Como tornar seu código instalável." #: ../../tutorials/publish-pypi.md:26 #, python-brace-format msgid "" -"Build your package's {term}`Source distribution (sdist)` and {term}`Wheel" -" (.whl)` {term}`Distribution files`" +"Build your package's {term}`Source distribution (sdist)` and {term}`Wheel " +"(.whl)` {term}`Distribution files`" msgstr "" +"Fazer o build da {term}`distribuição fonte (sdist) ` e da {term}`Wheel(.whl)` {term}`arquivos de distribuição " +"` do seu pacote" #: ../../tutorials/publish-pypi.md:28 msgid "Setup an account on TestPyPI (the process is similar for PyPI)" -msgstr "" +msgstr "Criar uma conta no TestPyPI (o processo é semelhante para o PyPI)" #: ../../tutorials/publish-pypi.md:29 msgid "Publish your package to TestPyPI and PyPI" -msgstr "" +msgstr "Publicar seu pacote no TestPyPI e no PyPI" #: ../../tutorials/publish-pypi.md:31 msgid "" -"You will do all of your development work in this lesson using [Hatch" -"](get-to-know-hatch)." +"You will do all of your development work in this lesson using " +"[Hatch](get-to-know-hatch)." msgstr "" +"Você fará todo o trabalho de desenvolvimento nesta lição usando " +"[Hatch](get-to-know-hatch)." #: ../../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 " -"[Grayskull](https://conda.github.io/grayskull/)." +"Once your package is on PyPI you can publish it to conda-forge (which is a " +"channel on conda) using [Grayskull](https://conda.github.io/grayskull/)." msgstr "" +"Depois que seu pacote estiver no PyPI, você pode publicá-lo no conda-forge " +"(que é um channel no conda) usando " +"[Grayskull](https://conda.github.io/grayskull/)." #: ../../tutorials/publish-pypi.md:37 msgid "" -"You will learn how to publish to conda-forge in the [next lesson" -"](publish-conda-forge)." +"You will learn how to publish to conda-forge in the [next " +"lesson](publish-conda-forge)." msgstr "" +"Você aprenderá como publicar no conda-forge na [próxima " +"lição](publish-conda-forge)." #: ../../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" -" package. An arrow to the right takes you to a build distribution files " -"box. Another arrow to the right takes you to a publish to PyPI box which " -"has an arrow containing sdist and wheel that notes those files go to PyPI" -" for hosting. From PyPI is an arrow containing sdist since you can then " -"connect to conda-forge for an automated build that sends distributions " -"from PyPI to conda-forge." +"graphic with code, metadata and tests in it. Those items all go into your " +"package. An arrow to the right takes you to a build distribution files box. " +"Another arrow to the right takes you to a publish to PyPI box which has an " +"arrow containing sdist and wheel thatnotes those files go to PyPI for " +"hosting. From PyPI is an arrow containing sdist since you can then connect " +"to conda-forge for an automated build that sends distributions from PyPI to " +"conda-forge." msgstr "" +"Gráfico mostrando o workflow de alto nível de empacotamento. À esquerda " +"você vê um gráfico com code, metadata e tests. Esses itens entram no seu " +"pacote. Uma seta à direita leva a uma caixa build distribution files. Outra " +"seta à direita leva a uma caixa publish to PyPI, que tem uma seta contendo " +"sdist e wheel indicando que esses arquivos vão para o PyPI para hospedagem. " +"A partir do PyPI há uma setacontendo sdist, pois você pode então conectar " +"ao conda-forge para um build automatizado que envia distribuições do PyPI " +"para o conda-forge." #: ../../tutorials/publish-pypi.md:43 msgid "" @@ -5118,16 +5518,22 @@ msgid "" "distribution format that can be uploaded to PyPI and subsequently " "downloaded and installed by users." msgstr "" +"Você precisa fazer o build do seu pacote Python para publicá-lo no PyPI (ou " +"Conda). O processo de build organiza seu code e metadata em um formato de " +"distribuição que pode ser enviado ao PyPI e subsequentemente baixado e " +"instalado pelos usuários." #: ../../tutorials/publish-pypi.md:46 msgid "TestPyPI vs PyPI" -msgstr "" +msgstr "TestPyPI vs PyPI" #: ../../tutorials/publish-pypi.md:48 msgid "" "There are two repositories associated with PyPI to which you can upload " "your Python package." msgstr "" +"Existem dois repositórios associados ao PyPI para os quais você pode enviar " +"seu pacote Python." #: ../../tutorials/publish-pypi.md:51 msgid "" @@ -5137,94 +5543,131 @@ msgid "" "practice and learn how to publish a package without exposing your " "incomplete package on the real PyPI service." msgstr "" +"**[TestPyPI](https://test.pypi.org):** TestPyPI é um repositório de pacotes " +"fornecido pelo PyPI que você pode usar para testar se seu pacote pode ser " +"enviado, baixado e instalado corretamente. Este é um ótimo lugar para " +"praticar e aprender como publicar um pacote sem expor seu pacote incompleto " +"no serviço real do PyPI." #: ../../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" -" which users will get your package. IMPORTANT: Only publish your package " -"to PyPI when you are ready for it to be used by others and/or confident " -"that it will become a package that you will maintain. PyPI is not a place" -" to practice learning how to publish a Python package." +"**[PyPI](https://pypi.org):** This is the live, production PyPI repository " +"where you can officially publish your Python package, and from which users " +"will get your package. IMPORTANT: Only publish your package to PyPI when " +"you are ready for it to be used by others and/or confident that it will " +"become a package that you will maintain. PyPI is not a place to practice " +"learning how to publish a Python package." msgstr "" +"**[PyPI](https://pypi.org):** Este é o repositório PyPI de produção, ao " +"vivo, onde você pode publicar oficialmente seu pacote Python e de onde os " +"usuários obterão seu pacote. IMPORTANTE: Publique seu pacote no PyPI somente " +"quando estiver pronto para ser usado por outras pessoas e/ou confiante de " +"que se tornará um pacote que você manterá. O PyPI não é um lugar para " +"praticar aprender a publicar um pacote Python." #: ../../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 "" +"As etapas para publicar no TestPyPI vs. PyPI são semelhantes, com exceção " +"de uma url diferente. Indicaremos onde elas diferem." #: ../../tutorials/publish-pypi.md:57 msgid "4 Steps for publishing a Python package on TestPyPI (or PyPI)" -msgstr "" +msgstr "4 etapas para publicar um pacote Python no TestPyPI (ou PyPI)" #: ../../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" -" need to do to publish your Python package: to TestPyPI. You need to:" +"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 need to " +"do to publish your Python package: to TestPyPI. You need to:" msgstr "" +"Nesta lição você aprenderá como publicar seu pacote no TestPyPI " +"usando[Hatch](https://hatch.pypa.io/latest/). Há 4 coisas que você precisa " +"fazer para publicar seu pacote Python no TestPyPI. Você precisa:" #: ../../tutorials/publish-pypi.md:64 msgid "**Create a package development environment**" -msgstr "" +msgstr "**Criar um ambiente de desenvolvimento do pacote**" #: ../../tutorials/publish-pypi.md:65 #, 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 use {term}`pip` to install your package." +"[**Build your package using `hatch " +"build`**](../package-structure-code/python-package-distribution-files-sdist-" +"wheel).Building a packag 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 use {term}`pip` to install your " +"package." msgstr "" +"[**Fazer o build do seu pacote usando `hatch " +"build`**](../package-structure-code/python-package-distribution-files-sdist-" +"wheel).Fazer o build de um pacote é o processo de transformar seu code em dois " +"tipos de arquivos de distribuição: sdist e wheel. O arquivo de distribuição " +"wheel é particularmente importante para usuários que usarão {term}`pip` " +"para instalar seu pacote." #: ../../tutorials/publish-pypi.md:66 #, python-brace-format msgid "" -"**Create an account on TestPyPI (or PyPI)**: You will need to create a " -"TestPyPI account and associated {term}`API token` which provides " +"**Create an account on TestPyPI (or PyPI)**: You will need to create " +"a 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 "" +"**Criar uma conta no TestPyPI (ou PyPI)**: Você precisará criar uma conta " +"no TestPyPI e um {term}`API token` associado, que fornece permissões para " +"você enviar seu pacote. Quando publicar seu pacote no PyPI depois, " +"precisará de uma conta e token PyPI separados." #: ../../tutorials/publish-pypi.md:67 msgid "**Publish to TestPyPI using `hatch publish`**" -msgstr "" +msgstr "**Publicar no TestPyPI usando `hatch publish`**" #: ../../tutorials/publish-pypi.md:69 msgid "" -"In a [future lesson](trusted-publishing), you will learn how to create an" -" automated GitHub Actions workflow that publishes an updated version of " -"your package to PyPI every time you create a GitHub release." +"In a [future lesson](trusted-publishing), you will learn how to create an " +"automated GitHub Actions workflow that publishes an updated version of your " +"package to PyPI every time you create a GitHub release." msgstr "" +"Em uma [lição futura](trusted-publishing), você aprenderá como criar um " +"workflow automatizado de GitHub Actions que publica uma versão atualizada " +"do seu pacote no PyPI toda vez que você criar um release no GitHub." #: ../../tutorials/publish-pypi.md:71 msgid "Learn more about building Python packages in our guide" -msgstr "" +msgstr "Saiba mais sobre build de pacote Pythons no nosso guia" #: ../../tutorials/publish-pypi.md:75 msgid "" -"[Learn more about what building a Python package is](../package-" -"structure-code/python-package-distribution-files-sdist-wheel)" +"[Learn more about what building a Python package " +"is](../package-structure-code/python-package-distribution-files-sdist-wheel)" msgstr "" +"[Saiba mais sobre o que é fazer build de um pacote " +"Python](../package-structure-code/python-package-distribution-files-sdist-wh" +"eel)" #: ../../tutorials/publish-pypi.md:76 msgid "" -"[Learn more about the package distribution file that PyPI needs called " -"the wheel](#python-wheel)" +"[Learn more about the package distribution file that PyPI needs called the " +"wheel](#python-wheel)" msgstr "" +"[Saiba mais sobre o arquivo de distribuição do pacote que o PyPI precisa, " +"chamado wheel](#python-wheel)" #: ../../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-" -"distribution)" +"[Learn more about the package distribution file that conda-forge will need " +"on PyPI called the sdist (source distribution)](#python-source-distribution)" msgstr "" +"[Saiba mais sobre o arquivo de distribuição do pacote que o conda-forge " +"precisará no PyPI, chamado sdist (source " +"distribution)](#python-source-distribution)" #: ../../tutorials/publish-pypi.md:80 msgid "Step 1: Create a Python package development environment" -msgstr "" +msgstr "Etapa 1: Criar um ambiente de desenvolvimento de pacote Python" #: ../../tutorials/publish-pypi.md:82 msgid "" @@ -5232,110 +5675,145 @@ msgid "" "environment. The Python environment will contain all of the dependencies " "needed to both install and work on your package." msgstr "" +"A primeira etapa para fazer o build do seu pacote é criar um ambientede " +"desenvolvimento. O ambiente Python conterá todas as dependências " +"necessárias tanto para instalar quanto para trabalhar no seu pacote." #: ../../tutorials/publish-pypi.md:84 msgid "Use Hatch to create your environment." -msgstr "" +msgstr "Use o Hatch para criar seu ambiente." #: ../../tutorials/publish-pypi.md:92 msgid "Then view all of the current environments that hatch has access to:" msgstr "" +"Em seguida, visualize todos os ambientes atuais aos quais o hatch tem " +"acesso:" #: ../../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 " -"environment in development or editable mode." +"Then activate the environment. Note that when you call a shell from a Hatch " +"environment, it will automatically install your package into the environment " +"in development or editable mode." msgstr "" +"Depois ative o ambiente. Observe que quando você chama um shell de um " +"ambiente Hatch, ele instalará automaticamente seu pacote no ambiente em " +"modo de desenvolvimento ou editable." #: ../../tutorials/publish-pypi.md:114 msgid "View what's in the environment using `pip list`:" -msgstr "" +msgstr "Visualize o que há no ambiente usando `pip list`:" #: ../../tutorials/publish-pypi.md:130 msgid "At any time you can exit the environment using `exit`." -msgstr "" +msgstr "A qualquer momento você pode sair do ambiente usando `exit`." #: ../../tutorials/publish-pypi.md:144 msgid "Hatch and environments" -msgstr "" +msgstr "Hatch e ambientes" #: ../../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 " -"tool that comes with Python installations." +"Behind the scenes when hatch creates a new virtual environment, by default " +"it uses venv[^venv] which is the default environment management tool that " +"comes with Python installations." msgstr "" +"Nos bastidores, quando o hatch cria um novo virtual environment, por padrão " +"ele usa venv[^venv], que é a ferramenta padrão de gerenciamentode ambientes " +"que vem com instalações Python." #: ../../tutorials/publish-pypi.md:149 msgid "Hatch will:" -msgstr "" +msgstr "O Hatch irá:" #: ../../tutorials/publish-pypi.md:151 msgid "Create a new virtualenv (venv) that is located on your computer." -msgstr "" +msgstr "Criar um novo virtualenv (venv) localizado no seu computador." #: ../../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" -" your project's dependencies as declared in your pyproject.toml file." +"Install your package into the environment in editable mode (similar " +"to `python -m pip install -e`). This means it installs both your project and " +"your project's dependencies as declared in your pyproject.toml file." msgstr "" +"Instalar seu pacote no ambiente em modo editable (semelhante a `python-m " +"pip install -e`). Isso significa que instala tanto o seu projeto quanto as " +"dependências do projeto declaradas no seu arquivo pyproject.toml." #: ../../tutorials/publish-pypi.md:154 msgid "Step 2: Build your package's sdist and wheel distributions" -msgstr "" +msgstr "Etapa 2: Fazer o build das distribuições sdist e wheel do seu pacote" #: ../../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 " -"turning your Python package file structure into two distribution files:" +"your package using Hatch. Remember that building is the process of turning " +"your Python package file structure into two distribution files:" msgstr "" +"Depois de configurar seu ambiente de desenvolvimento, você está pronto para " +"fazer o build do seu pacote usando Hatch. Lembre-se de que build é o " +"processo de transformar a estrutura de arquivos do seu pacote Python em dois " +"arquivos de distribuição:" #: ../../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" -" such as `pip`. This file has the extension `.whl`." +"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 such as `pip`. This file has the extension `.whl`." msgstr "" +"A [distribuição wheel](#python-wheel) é uma versão pré-buildada do " +"seu package. É útil para usuários, pois pode ser instalada diretamente " +"usando uma ferramenta como `pip`. Este arquivo tem a extensão `.whl`." #: ../../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 " +"The [source distribution](#python-source-distribution) contains the files " +"that make up your package in an unbuilt format. This file will have the " "extension `.tar.gz`." msgstr "" +"A [source distribution](#python-source-distribution) contém os arquivos que " +"compõem seu pacote em formato não buildado. Este arquivo terá a extensão " +"`.tar.gz`." #: ../../tutorials/publish-pypi.md:161 msgid "" -"You will use Hatch as a **Front end** tool that builds your package's " -"sdist and wheel using the [hatchling](https://hatch.pypa.io/latest/) " -"build back-end. The hatchling build back-end is used because you declared" -" it in your pyproject.toml file in the [previous lesson](create-python-" -"package)." +"You will use Hatch as a **Front end** tool that builds your package's sdist " +"and wheel using the [hatchling](https://hatch.pypa.io/latest/) build " +"back-end. The hatchling build back-end is used because you declared it in " +"your pyproject.toml file in the [previous lesson](create-python-package)." msgstr "" +"Você usará o Hatch como ferramenta de **Front end** que faz o build do sdist " +"e wheel do seu pacote usando o build back-end " +"[hatchling](https://hatch.pypa.io/latest/). O build back-end hatchling é " +"usado porque você o declarou no seu arquivo pyproject.toml na " +"[lição anterior](create-python-package)." #: ../../tutorials/publish-pypi.md:165 msgid "To build your package run `hatch build`:" -msgstr "" +msgstr "Para fazer o build do seu pacote, execute `hatch build`:" #: ../../tutorials/publish-pypi.md:176 msgid "Learn more about building a Python package" -msgstr "" +msgstr "Saiba mais sobre build de pacote Python" #: ../../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-" -"wheel)." +"guide](../package-structure-code/python-package-distribution-files-sdist-whe" +"el)." msgstr "" +"Você pode saber mais sobre build na [página de build do nosso guia de " +"empacotamento](../package-structure-code/python-package-distribution-files-s" +"dist-wheel)." #: ../../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." +"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." msgstr "" +"O sdist é importante se você deseja [publicar seu pacote no " +"conda-forge](publish-conda-forge). Você aprenderá sobre isso em uma lição " +"posterior." #: ../../tutorials/publish-pypi.md:186 msgid "" @@ -5345,173 +5823,226 @@ msgid "" "────────────────────────────────────── dist/pyospackage-0.1-py3-none-" "any.whl" msgstr "" +"➜ hatch build ────────────────────────────────────── sdist " +"────────────────────────────────────── dist/pyospackage-0.1.tar.gz " +"────────────────────────────────────── wheel " +"────────────────────────────────────── dist/pyospackage-0.1-py3-none-" +"any.whl" #: ../../tutorials/publish-pypi.md:193 msgid "" -" Congratulations - " -"you've created your Python package distribution files " +" Congratulations - you've " +"created your Python package distribution files " msgstr "" +" Parabéns — você criou os " +"arquivos de distribuição do seu pacote Python " #: ../../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" -" you can publish your package." +"You've now built your Python package and created your package distribution " +"files. The next step is to setup your account on TestPyPIso you can publish " +"your package." msgstr "" +"Você fez o build do seu pacote Python e criou os arquivos de distribuição " +"do pacote. A próxima etapa é configurar sua conta no TestPyPI para publicar " +"seu pacote." #: ../../tutorials/publish-pypi.md:198 msgid "Step 3. Setup your TestPyPI account" -msgstr "" +msgstr "Etapa 3. Configure sua conta no TestPyPI" #: ../../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 " -"publish a package without accidentally \"releasing\" your package before " +"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 publish a package without accidentally \"releasing\" your package before " "it's ready." msgstr "" +"Em seguida, você configurará uma conta no TestPyPI. Lembre-se de que você " +"está usando o TestPyPI aqui em vez do PyPI real como forma de aprender com " +"segurança como publicar um pacote sem \"lançar\" acidentalmente seu pacote " +"antes que esteja pronto." #: ../../tutorials/publish-pypi.md:204 msgid "TestPyPI vs. PyPI" -msgstr "" +msgstr "TestPyPI vs. PyPI" #: ../../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 " -"will call `hatch publish` to publish directly to PyPI instead of `hatch " -"publish -r test` which publishes to TestPyPI." +"steps below will also work for you. When you publish using Hatch, you will " +"call `hatch publish` to publish directly to PyPI instead of `hatch publish " +"-r test` which publishes to TestPyPI." msgstr "" +"Se você tem um pacote sobre o qual está confiante de que pertence ao PyPI, " +"todas as etapas abaixo também funcionarão para você. Quando publicar usando " +"Hatch, você chamará `hatch publish` para publicar diretamente no PyPI em " +"vez de `hatch publish -r test`, que publica no TestPyPI." #: ../../tutorials/publish-pypi.md:208 msgid "" "[Open up a web browser and go to the TestPyPI " "website](https://test.pypi.org/)." -msgstr "" +msgstr "[Abra um navegador web e acesse o site do TestPyPI](https://test.pypi.org/)." #: ../../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!" +"[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!" msgstr "" +"[Crie uma conta](https://test.pypi.org/account/register/) se ainda não tiver " +"uma. Certifique-se de armazenar sua senha em um local seguro!" #: ../../tutorials/publish-pypi.md:210 msgid "Once you have an account setup, login to it." -msgstr "" +msgstr "Depois de configurar uma conta, faça login." #: ../../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 " "that you have selected doesn't already exist. If you are using our test " -"pyosPackage, then we suggest that you add your name or GitHub username to" -" the end of the package name to ensure it's unique." +"pyosPackage, then we suggest that you add your name or GitHub username to " +"the end of the package name to ensure it's unique." msgstr "" +"Pesquise em [https://test.pypi.org/](https://test.pypi.org/) (e também em " +"[https://pypi.org/](https://pypi.org/)) para garantir que o nome do package " +"que você selecionou ainda não existe. Se você estiver usando nosso " +"pyosPackage de teste, sugerimos adicionar seu nome ou nome de usuário do " +"GitHub ao final do nome do pacote para garantir queseja único." #: ../../tutorials/publish-pypi.md:213 msgid "Example: `pyosPackage_yourNameHere`." -msgstr "" +msgstr "Exemplo: `pyosPackage_yourNameHere`." #: ../../tutorials/publish-pypi.md:215 msgid "" "How to rename your Python package if the name is already taken in (test) " "PyPI" -msgstr "" +msgstr "Como renomear seu pacote Python se o nome já estiver em uso no (test)PyPI" #: ../../tutorials/publish-pypi.md:219 msgid "Required" -msgstr "" +msgstr "Obrigatório" #: ../../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-" -"forge](https://conda-forge.org/packages/))" +"Search your publishing location(s) to make sure your new name isn't taken " +"([TestPyPI](https://test.pypi.org/), [PyPI](https://pypi.org/), " +"[conda-forge](https://conda-forge.org/packages/))" msgstr "" +"Pesquise nos locais de publicação para garantir que seu novo nome não " +"esteja em uso ([TestPyPI](https://test.pypi.org/), " +"[PyPI](https://pypi.org/), [conda-forge](https://conda-forge.org/packages/))" #: ../../tutorials/publish-pypi.md:222 msgid "" "Update the project name in your pyproject.toml file (e.g. `name = " "\"pyospackage_yourNameHere\"`)" msgstr "" +"Atualize o nome do projeto no seu arquivo pyproject.toml (por exemplo,`name " +"= \"pyospackage_yourNameHere\"`)" #: ../../tutorials/publish-pypi.md:223 msgid "" "Update the module folder name to be the same (e.g. " "`src/pyospackage_yourNameHere`)" msgstr "" +"Atualize o nome da pasta do module para ser o mesmo (por exemplo, " +"`src/pyospackage_yourNameHere`)" #: ../../tutorials/publish-pypi.md:224 msgid "Rebuild your project (`hatch build`)" -msgstr "" +msgstr "Faça rebuild do seu projeto (`hatch build`)" #: ../../tutorials/publish-pypi.md:225 msgid "Publish your package to capture the name (continue this tutorial!)" -msgstr "" +msgstr "Publique seu pacote para reservar o nome (continue este tutorial!)" #: ../../tutorials/publish-pypi.md:227 msgid "Recommended" -msgstr "" +msgstr "Recomendado" #: ../../tutorials/publish-pypi.md:229 msgid "Update the GitHub repository name to align with the new package name" -msgstr "" +msgstr "Atualize o nome do repositório GitHub para alinhar com o novo nome do pacote" #: ../../tutorials/publish-pypi.md:230 msgid "" "Update your local project folder to match the new package name (e.g. " "`pyospackage_yourNameHere/src`)" msgstr "" +"Atualize a pasta local do projeto para corresponder ao novo nome do pacote " +"(por exemplo, `pyospackage_yourNameHere/src`)" #: ../../tutorials/publish-pypi.md:231 msgid "Update mentions of your repository name in other files (e.g. `README.md`)" msgstr "" +"Atualize menções ao nome do repositório em outros arquivos (por exemplo, " +"`README.md`)" #: ../../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" -" were no results for pyosPackage Did you mean probpackage" +"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 were " +"no results for pyosPackage Did you mean probpackage" msgstr "" +"Esta é uma captura de tela do site TestPyPI. No topo, na barra de pesquisa, " +"você pode ver a busca por pyosPackage. O resultado da pesquisa diz que não " +"houve resultados para pyosPackage. Você quis dizer probpackage" #: ../../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." +"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 "" +"Antes de tentar fazer upload para o TestPyPI, verifique se o nome do seu " +"pacote já está em uso. Você pode fazer isso usando a caixa de busca no topo " +"do site do TestPyPI." #: ../../tutorials/publish-pypi.md:241 msgid "Setup 2-factor (2FA) authentication" -msgstr "" +msgstr "Configurar autenticação de 2 fatores (2FA)" #: ../../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 " -"logging in is really you. It addresses the issue of password phishing " -"where someone else gains access to a password and can login to your " -"account." +"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 logging " +"in is really you. It addresses the issue of password phishing where someone " +"else gains access to a password and can login to your account." msgstr "" +"A autenticação de 2 fatores é um processo de login seguro que permite usar " +"um dispositivo de backup ao qual somente você tem acesso para validar que a " +"pessoa que está fazendo login é realmente você. Ela resolve o problema de " +"phishing de senhas, em que outra pessoa obtém acesso a uma senha e consegue " +"entrar na sua conta." #: ../../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 " -"will then impact all of your users when they download and install that " -"version of the package." +"This matters on PyPI because someone could login to your account and upload " +"a version of your package that has security issues. These issues will then " +"impact all of your users when they download and install that version of the " +"package." msgstr "" +"Isso importa no PyPI porque alguém poderia fazer login na sua conta e fazer " +"upload de uma versão do seu pacote com problemas de segurança. Esses " +"problemas afetarão todos os seus usuários quando eles baixarem e instalarem " +"essa versão do pacote." #: ../../tutorials/publish-pypi.md:248 msgid "" -"2-factor authentication is required for PyPI authentication as of 1 " -"January 2024." +"2-factor authentication is required for PyPI authentication as of 1 January " +"2024." msgstr "" +"A autenticação de 2 fatores é obrigatória para autenticação no PyPI a " +"partir de 1 de janeiro de 2024." #: ../../tutorials/publish-pypi.md:252 msgid "Step 4. Create a package upload token" -msgstr "" +msgstr "Passo 4. Criar um token de upload do pacote" #: ../../tutorials/publish-pypi.md:254 msgid "" @@ -5520,449 +6051,573 @@ msgid "" "token. (If you completed this step previously, you can reuse the tokens " "when you upload your package again.)" msgstr "" +"Para fazer upload do seu pacote para o TestPyPI (ou PyPI), você precisará " +"criar um token para a sua conta primeiro e, em seguida, criar um token " +"específico para o pacote. (Se você já concluiu esta etapa anteriormente, " +"pode reutilizar os tokens quando fizer upload do pacote novamente.)" #: ../../tutorials/publish-pypi.md:256 msgid "Why create package-specific tokens?" -msgstr "" +msgstr "Por que criar tokens específicos para o pacote?" #: ../../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 " -"access all of your TestPyPI (or PyPI) projects. By creating a package-" -"specific token, you are limiting the scope of the token to only your " -"specific package. This is just a safe way to set things up for you " +"access all of your TestPyPI (or PyPI) projects. By creating a " +"package-specific token, you are limiting the scope of the token to only " +"your specific package. This is just a safe way to set things up for you " "particularly if you are collaborating with others on package development." msgstr "" +"O ideal é criar um token específico para o pacote. Quando você cria um token " +"para toda a conta, isso permite que qualquer pessoa com acesso à conta acesse " +"todos os seus projetos no TestPyPI (ou PyPI). Ao criar um token específico " +"para o pacote, você limita o escopo do token apenas ao seu pacote. Essa é " +"uma forma segura de configurar tudo, especialmente se você estiver " +"colaborando com outras pessoas no desenvolvimento do pacote." #: ../../tutorials/publish-pypi.md:261 msgid "Follow the steps below to create your token" -msgstr "" +msgstr "Siga os passos abaixo para criar seu token" #: ../../tutorials/publish-pypi.md:263 msgid "Login to TestPyPI and go to your account settings" -msgstr "" +msgstr "Faça login no TestPyPI e acesse as configurações da sua conta" #: ../../tutorials/publish-pypi.md:264 msgid "Scroll down to the **API tokens** section" -msgstr "" +msgstr "Role até a seção **API tokens**" #: ../../tutorials/publish-pypi.md:265 msgid "Click on the **Add API Token** button" -msgstr "" +msgstr "Clique no botão **Add API Token**" #: ../../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." +"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 "" +"Se você é novo no TestPyPI e ainda não tem nenhum pacote lá, OU se você tem " +"outros pacotes no TestPyPI mas está fazendo upload de um pacote novo, será " +"necessário criar um token para toda a conta." #: ../../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." +"When you create your token, be sure to copy the token value and store it in " +"a secure place before closing that browser." msgstr "" +"Ao criar o token, copie o valor do token e armazene-o em um local seguro " +"antes de fechar o navegador." #: ../../tutorials/publish-pypi.md:269 msgid "Your token should look something like this:" -msgstr "" +msgstr "Seu token deve se parecer com algo assim:" #: ../../tutorials/publish-pypi.md:271 msgid "`pypi-abunchofrandomcharactershere...`" -msgstr "" +msgstr "`pypi-abunchofrandomcharactershere...`" #: ../../tutorials/publish-pypi.md:273 msgid "It should start with `pypi` followed by a dash and a bunch of characters." msgstr "" +"Ele deve começar com `pypi`, seguido de um hífen e uma sequência de " +"caracteres." #: ../../tutorials/publish-pypi.md:275 msgid "Upload to TestPyPI using Hatch" -msgstr "" +msgstr "Fazer upload para o TestPyPI usando Hatch" #: ../../tutorials/publish-pypi.md:277 msgid "Once you have your token, you are ready to publish to TestPyPI." -msgstr "" +msgstr "Depois de ter o token, você está pronto para publicar no TestPyPI." #: ../../tutorials/publish-pypi.md:280 msgid "Run `hatch publish -r test`" -msgstr "" +msgstr "Execute `hatch publish -r test`" #: ../../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 " +"`-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 " "credentials." msgstr "" +"`-r` significa repository. Neste caso, como você está publicando no " +"TestPyPI, usará `-r test`. O Hatch então pedirá um nome de usuário e " +"credenciais." #: ../../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 "" +"Digite a palavra `__token__` como nome de usuário. Isso informa ao TestPyPI " +"que você está usando um valor de token em vez de um nome de usuário." #: ../../tutorials/publish-pypi.md:285 msgid "Paste your TestPyPI token value in at the `Enter your credentials` prompt:" -msgstr "" +msgstr "Cole o valor do seu token do TestPyPI no prompt `Enter your credentials`:" #: ../../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 " -"will publish your package to TestPyPI." +"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 will " +"publish your package to TestPyPI." msgstr "" +"Se suas credenciais forem válidas e você já tiver executado `hatch build` " +"e, portanto, tiver seus 2 arquivos de distribuição em um diretório `dist/`, " +"o Hatch publicará seu pacote no TestPyPI." #: ../../tutorials/publish-pypi.md:300 msgid "" -"Hatch also has a caching system so once you enter your credentials it " -"will remember them." +"Hatch also has a caching system so once you enter your credentials it will " +"remember them." msgstr "" +"O Hatch também tem um sistema de cache, então depois que você inserir suas " +"credenciais, ele as lembrará." #: ../../tutorials/publish-pypi.md:303 msgid "Install your package from TestPyPI" -msgstr "" +msgstr "Instalar seu pacote a partir do TestPyPI" #: ../../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." +"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 "" +"Quando o upload do seu pacote estiver concluído, você pode " +"instalá-lo a partir do TestPyPI. Você encontra as instruções de instalação na " +"página inicial do TestPyPI do pacote que acabou de fazer upload." #: ../../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 " -"page of the package has information from the package's README file." +"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 page of the " +"package has information from the package's README file." msgstr "" +"Uma captura de tela da página do TestPyPI para pyosPackage. No topo aparece " +"pyosPackage 0.1.0 com as instruções de instalação via pip abaixo. A página " +"inicial do pacote exibe informações do arquivo README do pacote." #: ../../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" -" install the package from TestPyPI. You can simply copy that code and use" -" it to install your package from TestPyPI locally." +"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 install the " +"package from TestPyPI. You can simply copy that code and use it to install " +"your package from TestPyPI locally." msgstr "" +"Esta é uma página inicial de exemplo para o pyosPackage que acabou de ser " +"enviado. Observe que no topo da página há instruções de como instalar o " +"pacote a partir do TestPyPI. Você pode simplesmente copiar esse código e " +"usá-lo para instalar seu pacote localmente a partir do TestPyPI." #: ../../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 " -"page has information about the current package version and also " -"installation instructions as follows:" +"TestPyPI](https://test.pypi.org/project/pyosPackage/). Notice that the page " +"has information about the current package version and also installation " +"instructions as follows:" msgstr "" +"Como exemplo, [confira nossa página inicial do pyosPackage da pyOpenSci no " +"TestPyPI](https://test.pypi.org/project/pyosPackage/). Observe que a página " +"contém informações sobre a versão atual do pacote e também instruções de " +"instalação, como segue:" #: ../../tutorials/publish-pypi.md:319 msgid "`python -m pip install -i https://test.pypi.org/simple/ pyosPackage`" -msgstr "" +msgstr "`python -m pip install -i https://test.pypi.org/simple/ pyosPackage`" #: ../../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 " -"install your package. In fact, you cannot, because TestPyPI may delete " -"accounts after a time. TestPyPI is a perfect place to learn how to " -"publish your package and test the installation process. But your end goal" -" should be to publish to PyPI once you have figured out your workflow and" -" your package is ready to deploy." -msgstr "" +"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 install your " +"package. In fact, you cannot, because TestPyPI may delete accounts after a " +"time. TestPyPI is a perfect place to learn how to publish your package and " +"test the installation process. But your end goal should be to publish to " +"PyPI once you have figured out your workflow and your package is ready to " +"deploy." +msgstr "" +"Publicar no TestPyPI vs PyPI Embora você possa instalar a partir do " +"TestPyPI, não é recomendado publicar no TestPyPI como forma permanentede " +"instalar seu pacote. Na verdade, você não pode, porque o TestPyPI pode " +"excluir contas depois de algum tempo. O TestPyPI é um lugar perfeito para " +"aprender a publicar seu pacote e testar o processode instalação. Mas seu " +"objetivo final deve ser publicar no PyPI depois que você tiver definido seu " +"workflow e seu pacote estiver pronto para deploy." #: ../../tutorials/publish-pypi.md:326 msgid "Time to install your package" -msgstr "" +msgstr "Hora de instalar seu pacote" #: ../../tutorials/publish-pypi.md:328 msgid "" "On your computer, activate the development environment that you wish to " "install your newly published package in." msgstr "" +"No seu computador, ative o ambiente de desenvolvimento em que deseja " +"instalar o pacote recém-publicado." #: ../../tutorials/publish-pypi.md:330 msgid "Run the installation instructions for your package from TestPyPI." -msgstr "" +msgstr "Execute as instruções de instalação do seu pacote a partir do TestPyPI." #: ../../tutorials/publish-pypi.md msgid "Conda" -msgstr "" +msgstr "Conda" #: ../../tutorials/publish-pypi.md msgid "venv Mac / Linux" -msgstr "" +msgstr "venv Mac / Linux" #: ../../tutorials/publish-pypi.md:354 msgid "The value of end-to-end tools like hatch, flit and poetry" -msgstr "" +msgstr "O valor de ferramentas ponta a ponta como hatch, flit e poetry" #: ../../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 " -"tools in the ecosystem.](../package-structure-code/python-package-build-" -"tools.md)" +"tools in the " +"ecosystem.](../package-structure-code/python-package-build-tools.md)" msgstr "" +"Nesta lição você está usando Hatch e hatchling para criar, fazer build e " +"publicar seu pacote Python. [Clique aqui para saber mais sobre outras " +"ferramentas de empacotamento no " +"ecossistema.](../package-structure-code/python-package-build-tools.md)" #: ../../tutorials/publish-pypi.md:359 msgid "" -"teach them to setup trusted publisher for actions... in the actions " -"lesson https://pypi.org/help/#twofa" +"teach them to setup trusted publisher for actions... in the actions lesson " +"https://pypi.org/help/#twofa" msgstr "" +"ensinar a configurar trusted publisher para actions... na lição de actions " +"https://pypi.org/help/#twofa" #: ../../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 " -"projects associated with that account. Alternatively, you can limit a " -"token's scope to a specific project." +"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 projects " +"associated with that account. Alternatively, you can limit a token's scope " +"to a specific project." msgstr "" +"do PyPI: https://pypi.org/help/#apitoken - Você pode criar um token para " +"toda uma conta PyPI; nesse caso, o token funcionará para todos os projetos " +"associados a essa conta. Alternativamente, você pode limitar o escopo de um " +"token a um projeto específico." #: ../../tutorials/publish-pypi.md:365 msgid "Package-specific token vs trusted publisher" -msgstr "" +msgstr "Token específico do pacote vs trusted publisher" #: ../../tutorials/publish-pypi.md:367 msgid "" -"For long run maintenance of your package, you have two options related to" -" PyPI publication." +"For long run maintenance of your package, you have two options related to " +"PyPI publication." msgstr "" +"Para a manutenção de longo prazo do seu pacote, você tem duas opções " +"relacionadas à publicação no PyPI." #: ../../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" -" to automate your PyPI publication workflow." +"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 to " +"automate your PyPI publication workflow." msgstr "" +"Você pode criar um token específico do pacote que usará para publicar seu " +"pacote (manualmente) no PyPI. Essa é uma ótima opção se você não quiser " +"automatizar seu workflow de publicação no PyPI." #: ../../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 " -"easier and it also supports a growing maintainer team. In this case we " -"suggest you don't worry about the token and instead setup a specific " -"GitHub Actions that publishes your package when you make a release. You " -"can then create a \"trusted publisher\" workflow on PyPI." -msgstr "" +"GitHub Actions. This is a great way to make the publication process easier " +"and it also supports a growing maintainer team. In this case we suggest you " +"don't worry about the token and instead setup a specific GitHub Actions that " +"publishes your package when you make a release. You can then create a " +"\"trusted publisher\" workflow on PyPI." +msgstr "" +"Você também pode criar um workflow de publicação automatizado no GitHub " +"usando GitHub Actions. Essa é uma ótima forma de facilitar o processo de " +"publicação e também suporta uma equipe de mantenedores em crescimento. " +"Nesse caso, sugerimos que você não se preocupe com o token e, em vez disso, " +"configure um GitHub Actions específico que publique seu pacote quando você " +"fizer um release. Você pode então criar um workflow de \"trusted publisher\" " +"no PyPI." #: ../../tutorials/publish-pypi.md:373 msgid "Trusted Publishing" -msgstr "" +msgstr "Trusted Publishing" #: ../../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." +"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 "" +"Embora seja possível publicar a partir do GitHub Actions usando tokens, " +"recomendamos a abordagem _Trusted Publishing_, pois ela também oferece " +"benefícios significativos de segurança e usabilidade." #: ../../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." +"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 "" +"No aspecto de usabilidade, quando o Trusted Publishing está habilitado, os " +"usuários não precisam mais criar manualmente API tokensno PyPI e " +"armazená-los no workflow de release do GitHub." #: ../../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 " -"access to it, they can publish many packages and versions in your name " -"(depending on the scope of the token), until you discover the token " -"compromise and rotate the credential. Trusted Publishing avoids this " -"problem by minting very short lived tokens which expire automatically." -msgstr "" +"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 access " +"to it, they can publish many packages and versions in your name (depending " +"on the scope of the token), until you discover the token compromise and " +"rotate the credential. Trusted Publishing avoids this problem by minting " +"very short lived tokens which expire automatically." +msgstr "" +"No aspecto de segurança, o Trusted Publishing reduz um risco relacionado ao " +"fato de o API token ser de longa duração: com API tokens, assim que um " +"atacante obtém acesso a ele, pode publicar muitos packages e versões em seu " +"nome (dependendo do escopo do token), até que você descubra o " +"comprometimento do token e rotacione a credencial. O Trusted Publishing " +"evita esse problema ao gerar tokens de curta duração que expiram " +"automaticamente." #: ../../tutorials/publish-pypi.md:382 msgid "" -"For these benefits, it is recommended that users use _only_ the GitHub " -"Actions release workflow to publish packages." +"For these benefits, it is recommended that users use _only_ the " +"GitHub Actions release workflow to publish packages." msgstr "" +"Por esses benefícios, recomenda-se que os usuários usem _somente_ o " +"workflow de release do GitHub Actions para publicar pacotes." #: ../../tutorials/publish-pypi.md:385 msgid "" -"You will learn how to create the automated trusted publisher workflow in " -"a followup lesson." +"You will learn how to create the automated trusted publisher workflow in a " +"followup lesson." msgstr "" +"Você aprenderá a criar o workflow automatizado de trusted publisher em uma " +"lição seguinte." #: ../../tutorials/publish-pypi.md:387 msgid "OPTIONAL: If you want to use a manual token-based publication workflow" msgstr "" +"OPCIONAL: Se você quiser usar um workflow de publicação manual baseado em " +"token" #: ../../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." +"recommend going through the above steps again to create a token specific to " +"your new package." msgstr "" +"Se você planeja usar seu token regularmente para publicar no PyPI, " +"recomendamos fortemente repetir os passos acima para criar um token " +"específico para o seu novo pacote." #: ../../tutorials/publish-pypi.md:392 msgid "To do this:" -msgstr "" +msgstr "Para fazer isso:" #: ../../tutorials/publish-pypi.md:393 msgid "Go to TestPyPI." -msgstr "" +msgstr "Acesse o TestPyPI." #: ../../tutorials/publish-pypi.md:394 msgid "Navigate to the \"Your Projects\" section of your account" -msgstr "" +msgstr "Navegue até a seção \"Your Projects\" da sua conta" #: ../../tutorials/publish-pypi.md:395 -msgid "" -"Click on the manage button for the project that you wish to add a token " -"for" -msgstr "" +msgid "Click on the manage button for the project that you wish to add a token for" +msgstr "Clique no botão manage do projeto para o qual deseja adicionar um token" #: ../../tutorials/publish-pypi.md:396 msgid "Go to settings" -msgstr "" +msgstr "Acesse settings" #: ../../tutorials/publish-pypi.md:397 msgid "Click on \"Create a token for your-package-name-here\"" -msgstr "" +msgstr "Clique em \"Create a token for your-pacote-name-here\"" #: ../../tutorials/publish-pypi.md:398 msgid "" -"Create the token and follow the steps above publish your package using " -"the repository specific token." +"Create the token and follow the steps above publish your package using the " +"repository specific token." msgstr "" +"Crie o token e siga os passos acima para publicar seu pacote usando o token " +"específico do repository." #: ../../tutorials/publish-pypi.md:400 msgid "And you're all done!" -msgstr "" +msgstr "E pronto!" #: ../../tutorials/publish-pypi.md:402 msgid "Trusted Publishing instead of token-based publication" -msgstr "" +msgstr "Trusted Publishing em vez de publicação baseada em token" #: ../../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 " -"triggered. This solves all the security and usability issues associated " -"with storing credentials in files/GitHub secrets." +"Trusted Publishing will generate short lived tokens, scoped to the project, " +"on demand, only when a specific release workflows gets triggered. This " +"solves all the security and usability issues associated with storing " +"credentials in files/GitHub secrets." msgstr "" +"O Trusted Publishing gerará tokens de curta duração, com escopo no projeto, " +"sob demanda, somente quando um workflow de release específico for acionado. " +"Isso resolve todos os problemas de segurança e usabilidade associados ao " +"armazenamento de credenciais em arquivos/secrets do GitHub." #: ../../tutorials/publish-pypi.md:411 msgid "You have published your package to TestPyPI!" -msgstr "" +msgstr "Você publicou seu pacote no TestPyPI!" #: ../../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 " -"real PyPI, then you can follow the same steps (with the differences noted" -" above) to publish it on PyPI." +"real PyPI, then you can follow the same steps (with the differences noted " +"above) to publish it on PyPI." msgstr "" +"Parabéns. Você publicou com sucesso seu pacote no TestPyPI. Se você tem um " +"pacote pronto para uso no mundo real no PyPI de verdade, pode seguir os " +"mesmos passos (com as diferenças mencionadas acima) para publicá-lo no PyPI." #: ../../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-" -"forge.org/blog/posts/2020-03-05-grayskull/) tool." +"conda-forge ecosystem using the " +"[grayskull](https://conda-forge.org/blog/posts/2020-03-05-grayskull/) tool." msgstr "" +"Depois de publicar no PyPI, você pode adicionar facilmente seu pacote ao " +"ecossistema conda-forge usando a ferramenta " +"[grayskull](https://conda-forge.org/blog/posts/2020-03-05-grayskull/)." #: ../../tutorials/publish-pypi.md:417 msgid "You will learn how to do that in the next lesson." -msgstr "" +msgstr "Você aprenderá a fazer isso na próxima lição." #: ../../tutorials/publish-pypi.md:421 msgid "https://docs.python.org/3/library/venv.html" -msgstr "" +msgstr "https://docs.python.org/3/library/venv.html" #: ../../tutorials/pyproject-toml.md:6 msgid "Make your Python package PyPI ready - pyproject.toml" -msgstr "" +msgstr "Deixe seu pacote Python pronto para o PyPI - pyproject.toml" #: ../../tutorials/pyproject-toml.md:8 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)." +"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)." msgstr "" +"Na [lição de código instalável](create-python-package), você aprendeu a " +"adicionar as informações mínimas necessárias a um arquivo `pyproject.toml` " +"para torná-lo instalável. Em seguida, aprendeu a publicar uma versão mínima " +"do seu pacote no [PyPI](publish-pypi)." #: ../../tutorials/pyproject-toml.md:13 msgid "Following that you learned how to add a:" -msgstr "" +msgstr "Depois disso, você aprendeu a adicionar um:" #: ../../tutorials/pyproject-toml.md:14 msgid "[README.md](add-readme)" -msgstr "" +msgstr "[README.md](add-readme)" #: ../../tutorials/pyproject-toml.md:15 msgid "[LICENSE](add-license-coc) and" -msgstr "" +msgstr "[LICENSE](add-license-coc) e" #: ../../tutorials/pyproject-toml.md:16 msgid "[CODE_OF_CONDUCT](add-coc)" -msgstr "" +msgstr "[CODE_OF_CONDUCT](add-coc)" #: ../../tutorials/pyproject-toml.md:18 msgid "to the root of your project directory." -msgstr "" +msgstr "na raiz do diretório do seu projeto." #: ../../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 " -"development status, and project maintainers, you should add additional " -"metadata to your `pyproject.toml` file. This lesson will guide you " -"through the process." +"development status, and project maintainers, you should add " +"additional metadata to your `pyproject.toml` file. This lesson will guide " +"you through the process." msgstr "" +"Para aumentar a visibilidade do seu pacote no PyPI e fornecer mais " +"informações sobre sua compatibilidade com versões do Python, status " +"dedesenvolvimento do projeto e mantenedores, você deve adicionar metadata " +"adicional ao seu arquivo `pyproject.toml`. Esta lição guiará você pelo " +"processo." #: ../../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" +"More about the `pyproject.toml` file and how it's used to store different " +"types of metadata about your package" msgstr "" +"Mais sobre o arquivo `pyproject.toml` e como ele é usado para armazenar " +"diferentes tipos de metadata sobre o seu pacote" #: ../../tutorials/pyproject-toml.md:33 msgid "" -"How to declare information (metadata) about your project to help users " -"find and understand it on PyPI." +"How to declare information (metadata) about your project to help users find " +"and understand it on PyPI." msgstr "" +"Como declarar informações (metadata) sobre o seu projeto para ajudar os " +"usuários a encontrá-lo e entendê-lo no PyPI." #: ../../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-" -"metadata.md)" +"this page. " +"](../package-structure-code/pyproject-toml-python-package-metadata.md)" msgstr "" +"Se você quiser saber mais sobre o formato `pyproject.toml`, [confira esta " +"página.](../package-structure-code/pyproject-toml-python-package-metadata.md" +")" #: ../../tutorials/pyproject-toml.md msgid "Click for lesson takeaways" -msgstr "" +msgstr "Clique para ver os principais pontos da lição" #: ../../tutorials/pyproject-toml.md:42 msgid "When creating your pyproject.toml file, consider the following:" -msgstr "" +msgstr "Ao criar seu arquivo pyproject.toml, considere o seguinte:" #: ../../tutorials/pyproject-toml.md:44 msgid "" "There are only two required metadata tables that you need to install and " "publish your Python package:" msgstr "" +"Há apenas duas tabelas de metadata obrigatórias para instalar e publicar " +"seu pacote Python:" #: ../../tutorials/pyproject-toml.md:45 msgid "**[build-system]**" -msgstr "" +msgstr "**[build-system]**" #: ../../tutorials/pyproject-toml.md:46 msgid "**[project]**." -msgstr "" +msgstr "**[project]**." #: ../../tutorials/pyproject-toml.md:47 msgid "" "The **[project]** table stores your package's metadata. Within the " "**[project]** table, There are only two _required_ fields:" msgstr "" +"A tabela **[project]** armazena a metadata do seu pacote. Dentro da tabela " +"**[project]**, há apenas dois campos _obrigatórios_:" #: ../../tutorials/pyproject-toml.md:48 msgid "**name=**" -msgstr "" +msgstr "**name=**" #: ../../tutorials/pyproject-toml.md:49 msgid "**version=**" -msgstr "" +msgstr "**version=**" #: ../../tutorials/pyproject-toml.md:50 msgid "" @@ -5970,14 +6625,21 @@ msgid "" "easier for users to find your project on PyPI. And it will also make it " "easier for installers to understand how to install your package." msgstr "" +"Você deve adicionar mais metadata à tabela `[project]`, pois isso " +"facilitará para os usuários encontrarem seu projeto no PyPI. E também " +"facilitará para os instaladores entenderem como instalar seu pacote." #: ../../tutorials/pyproject-toml.md:51 msgid "" -"When you are adding classifiers to the **[project]** table, only use " -"valid values from [PyPI's classifier " -"page](https://PyPI.org/classifiers/). An invalid value here will raise an" -" error when you build and publish your package on PyPI." +"When you are adding classifiers to the **[project]** table, only use valid " +"values from [PyPI's classifier page](https://PyPI.org/classifiers/). An " +"invalid value here will raise an error when you build and publish your " +"package on PyPI." msgstr "" +"Ao adicionar classifiers à tabela **[project]**, use apenas valores válidos " +"da [página de classifiers do PyPI](https://PyPI.org/classifiers/). Um valor " +"inválido aqui gerará um erro quando você fizer build e publicar seu pacote " +"no PyPI." #: ../../tutorials/pyproject-toml.md:52 msgid "" @@ -5985,57 +6647,74 @@ msgid "" "However, fields need to be placed within the correct tables. For example " "`requires =` always need to be in the **[build-system]** table." msgstr "" +"Não há uma ordem específica para as tabelas no arquivo `pyproject.toml`. No " +"entanto, os campos precisam estar nas tabelas corretas. Por exemplo, " +"`requires =` sempre precisa estar na tabela **[build-system]**." #: ../../tutorials/pyproject-toml.md:53 msgid "" "We suggest that you include your **[build-system]** table at the top of " "your `pyproject.toml` file." msgstr "" +"Sugerimos que você inclua a tabela **[build-system]** no topo do seu " +"arquivo `pyproject.toml`." #: ../../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." +"The `pyproject.toml` file is a human and machine-readable file that serves " +"as the primary configuration file for your Python package." msgstr "" +"O arquivo `pyproject.toml` é um arquivo legível por humanos e por máquinas " +"que serve como arquivo de configuração principal do seu pacote Python." #: ../../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 "" +"[Fazer build do seu pacote](build-package) é a etapa que criou os arquivos " +"de distribuição necessários para você publicar no PyPI." #: ../../tutorials/pyproject-toml.md:67 msgid "About the .toml format" -msgstr "" +msgstr "Sobre o formato .toml" #: ../../tutorials/pyproject-toml.md:69 #, python-brace-format msgid "" -"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 " +"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 "" +"O arquivo **pyproject.toml** é escrito no formato {term}`TOML`. TOML é uma " +"estrutura fácil de ler baseada em pares chave/valor. Cada seção no arquivo " +"**pyproject.toml** contém um `[identificador da tabela]`. O formato TOML " +"pode ser comparado a outros formatos estruturados, como `.json`." #: ../../tutorials/pyproject-toml.md:74 msgid "" -"Below you can see the `[build-system]` table. Within that table there are" -" two required key/value pairs." +"Below you can see the `[build-system]` table. Within that table there are " +"two required key/value pairs." msgstr "" +"Abaixo você pode ver a tabela `[build-system]`. Dentro dessa tabela há dois " +"pares chave/valor obrigatórios." #: ../../tutorials/pyproject-toml.md:77 msgid "" -"`requires =` is the key and the value is `[\"hatchling\"]` within the " -"`[build-system]` array specified by square brackets `[]`." +"`requires =` is the key and the value is `[\"hatchling\"]` within " +"the`[build-system]` array specified by square brackets `[]`." msgstr "" +"`requires =` é a chave e o valor é `[\"hatchling\"]` dentro do array " +"`[build-system]` especificado por colchetes `[]`." #: ../../tutorials/pyproject-toml.md:87 msgid "What is the pyproject.toml used for?" -msgstr "" +msgstr "Para que serve o pyproject.toml?" #: ../../tutorials/pyproject-toml.md:89 msgid "The pyproject.toml file tells your build tool:" -msgstr "" +msgstr "O arquivo pyproject.toml informa à sua ferramenta de build:" #: ../../tutorials/pyproject-toml.md:91 #, python-brace-format @@ -6044,356 +6723,469 @@ msgid "" "{term}`Hatchling` in this tutorial but there are [many others to choose " "from](/package-structure-code/python-package-build-tools))." msgstr "" +"Qual {term}`backend de construção ` usar para fazer build do " +"seu pacote (neste tutorial estamos usando {term}`Hatchling`, mas há [muitas " +"outras opções](/package-structure-code/python-package-build-tools))." #: ../../tutorials/pyproject-toml.md:94 msgid "How and where to retrieve your package's version:" -msgstr "" +msgstr "Como e onde recuperar a versão do seu pacote:" #: ../../tutorials/pyproject-toml.md:95 msgid "**statically** where you declare the version `version = \"0.1.0\"` or" -msgstr "" +msgstr "**estaticamente**, onde você declara a versão `version = \"0.1.0\"` ou" #: ../../tutorials/pyproject-toml.md:96 msgid "" -"**dynamically** where the tool looks to the most recent tag in your " -"history to determine the current version." +"**dynamically** where the tool looks to the most recent tag in your history " +"to determine the current version." msgstr "" +"**dinamicamente**, quando a ferramenta consulta a tag mais recente no seu " +"histórico para determinar a versão atual." #: ../../tutorials/pyproject-toml.md:97 #, python-brace-format msgid "What {term}`Dependencies` your package needs" -msgstr "" +msgstr "Quais {term}`dependências ` o seu pacote precisa" #: ../../tutorials/pyproject-toml.md:98 msgid "What versions of Python your package supports (important for your users)." msgstr "" +"Quais versões do Python o seu pacote suporta (importante para seus " +"usuários)." #: ../../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:" msgstr "" +"O arquivo `pyproject.toml` também facilita para qualquer pessoa que navegue " +"no seu repository GitHub entender rapidamente a estrutura do seu pacote, " +"como:" #: ../../tutorials/pyproject-toml.md:103 msgid "How your package is built," -msgstr "" +msgstr "Como seu pacote é construído," #: ../../tutorials/pyproject-toml.md:104 msgid "What Python versions and operating systems it supports" -msgstr "" +msgstr "Quais versões do Python e sistemas operacionais ele suporta" #: ../../tutorials/pyproject-toml.md:105 msgid "What it does," -msgstr "" +msgstr "O que ele faz," #: ../../tutorials/pyproject-toml.md:106 msgid "Who maintains it" -msgstr "" +msgstr "Quem o mantém" #: ../../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 " -"(e.g. black, ruff)." +"Finally, the pyproject.toml file is also often used to configure tools such " +"as static type checkers (e.g. mypy) and code formatters/linters (e.g. " +"black, ruff)." msgstr "" +"Por fim, o arquivo pyproject.toml também é frequentemente usado para " +"configurar ferramentas como verificadores estáticos de tipos (por exemplo, " +"mypy) e formatadores/linters de código (por exemplo, black, ruff)." #: ../../tutorials/pyproject-toml.md:111 msgid "" "Check out the [PyPA " -"documentation](https://packaging.python.org/en/latest/tutorials" -"/packaging-projects/#choosing-a-build-backend) if you are interested in " -"setting build configurations for other tools." +"documentation](https://packaging.python.org/en/latest/tutorials/packaging-pr" +"ojects/#choosing-a-build-backend) if you are interested in setting build " +"configurations for other tools." msgstr "" +"Confira a [documentação da " +"PyPA](https://packaging.python.org/en/latest/tutorials/packaging-projects/#c" +"hoosing-a-build-backend) se você estiver interessado em definir configurações " +"de build para outras ferramentas." #: ../../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 " -"decide to use a tool other than Hatch and hatchling. We have selected " -"hatchling and hatch as our tool of choice for this tutorial as it adheres" -" to PyPA rules and guidelines." +"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 decide to use a " +"tool other than Hatch and hatchling. We have selected hatchling and hatch " +"as our tool of choice for this tutorial as it adheres to PyPA rules and " +"guidelines." msgstr "" +"Observe que algumas ferramentas de build podem divergir na forma como " +"armazenam metadata do projeto. Portanto, você pode querer consultar a " +"documentação delas se decidir usar uma ferramenta diferente de Hatch " +"e hatchling. Selecionamos hatchling e hatch como nossa ferramenta de escolha " +"neste tutorial porque ela segue as regras e diretrizes da PyPA." #: ../../tutorials/pyproject-toml.md:117 msgid "How is pyproject.toml metadata used?" -msgstr "" +msgstr "Como a metadata do pyproject.toml é usada?" #: ../../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" -" published to PyPI. This `METADATA` file is then used by PyPI to populate" -" your package's PyPI landing page and help users filter through the tens " -"of thousands of packages published there." +"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 " +"published to PyPI. This `METADATA` file is then used by PyPI to populate " +"your package's PyPI landing page and help users filter through the tens of " +"thousands of packages published there." msgstr "" +"O arquivo pyproject.toml é o arquivo que sua ferramenta de build usa para " +"preencher um `METADATA` incluído nos arquivos de distribuição do Python que " +"são publicados no PyPI. Esse arquivo `METADATA` é então usado pelo PyPI " +"para preencher a página inicial do seu pacote no PyPI e ajudar os usuários a " +"filtrar entre as dezenas de milhares de pacotes publicados lá." #: ../../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 " -"including Development status, intended audience, License, natural " -"language, operating system, programming language and topic. Below each of" -" those sections are various classifier options.\" width=\"300px\">" +"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 including " +"Development status, intended audience, License, natural language, operating " +"system, programming language and topic. Below each of those sections are " +"various classifier options.\" width=\"300px\">" msgstr "" +"Imagem mostrando a barra lateral esquerda do PyPI para o pacote xclim. A " +"seção no topo diz Classifier. Abaixo há uma lista de itens " +"incluindo Development status, intended audience, License, natural language, " +"operating system, programming language e topic. Abaixo de cada uma dessas " +"seções estão várias opções de classifiers.\" width=\"300px\">" #: ../../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 " -"that PyPI can understand and represent on your PyPI landing page. These " -"classifiers also allow users to sort through packages by version of " -"python they support, categories and more." +"When you add the classifier section to your pyproject.toml and your package " +"is built, the build tool organizes the metadata into a format that PyPI can " +"understand and represent on your PyPI landing page. These classifiers also " +"allow users to sort through packages by version of python they support, " +"categories and more." msgstr "" +"Quando você adiciona a seção de classifiers ao seu pyproject.toml e seu " +"pacote é construído, a ferramenta de build organiza a metadata em um formato " +"que o PyPI consegue entender e representar na página inicial do seu pacote " +"no PyPI. Esses classifiers também permitem que os usuários filtrem pacotes " +"por versão do Python que suportam, categorias e mais." #: ../../tutorials/pyproject-toml.md:133 msgid "A more in-depth overview of pyproject.toml files" -msgstr "" +msgstr "Uma visão geral mais aprofundada dos arquivos pyproject.toml" #: ../../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/)" +"[Our guidebook page has a more in depth overview of this " +"file](../package-structure-code/pyproject-toml-python-package-metadata/)" msgstr "" +"[Nossa página do guia tem uma visão geral mais aprofundada deste " +"arquivo](../package-structure-code/pyproject-toml-python-package-metadata/)" #: ../../tutorials/pyproject-toml.md:138 msgid "How to update your pyproject.toml file" -msgstr "" +msgstr "Como atualizar seu arquivo pyproject.toml" #: ../../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 "" +"Na lição anterior, você criou um arquivo pyproject.toml básico que continha " +"os elementos principais necessários para fazer build do seu pacote:" #: ../../tutorials/pyproject-toml.md:144 msgid "" "A `[build-system]` table where you defined your project's backend build " "tool (`hatchling`)" msgstr "" +"Uma tabela `[build-system]` onde você definiu a ferramenta de build backend " +"do projeto (`hatchling`)" #: ../../tutorials/pyproject-toml.md:145 msgid "A `[project]` table where you defined your project's version and name." -msgstr "" +msgstr "Uma tabela `[project]` onde você definiu a versão e o nome do projeto." #: ../../tutorials/pyproject-toml.md:147 msgid "The `pyproject.toml` file that you created, looked like this:" -msgstr "" +msgstr "O arquivo `pyproject.toml` que você criou ficou assim:" #: ../../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 " -"scope of your package. Once you add this metadata, you don't have to do " -"it again. These metadata fields will only be updated periodically when " -"you do something such as:" +"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 " +"scope of your package. Once you add this metadata, you don't have to do it " +"again. These metadata fields will only be updated periodically when you do " +"something such as:" msgstr "" +"Seu próximo passo é adicionar campos de metadata recomendados adicionais " +"que ajudarão os usuários a encontrar seu pacote no PyPI e também " +"descreverão melhor o escopo do seu pacote. Depois de adicionar essa " +"metadata, você não precisará fazer isso novamente. Esses campos de metadata " +"só serão atualizados periodicamente quando você fizer algo como:" #: ../../tutorials/pyproject-toml.md:162 msgid "drop a package dependency" -msgstr "" +msgstr "remover uma dependência do pacote" #: ../../tutorials/pyproject-toml.md:163 msgid "modify what Python versions your package supports." -msgstr "" +msgstr "modificar quais versões do Python o seu pacote suporta." #: ../../tutorials/pyproject-toml.md:165 msgid "More on hatchling" -msgstr "" +msgstr "Mais sobre hatchling" #: ../../tutorials/pyproject-toml.md:168 msgid "" "The documentation for the hatchling back-end is " "[here](https://hatch.pypa.io/latest/config/metadata/)" msgstr "" +"A documentação do back-end hatchling está " +"[aqui](https://hatch.pypa.io/latest/config/metadata/)" #: ../../tutorials/pyproject-toml.md:171 msgid "Step 1: Add Author, maintainer and project description" -msgstr "" +msgstr "Passo 1: Adicionar autor, mantenedor e descrição do projeto" #: ../../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 " -"in the `[project]` table." +"you should have a pyproject.toml file with a project name and a version in " +"the `[project]` table." msgstr "" +"Depois de concluir o [tutorial de código " +"instalável](create-python-package), você deve ter um arquivo pyproject.toml " +"com um nome de projeto e uma versão na tabela `[project]`." #: ../../tutorials/pyproject-toml.md:181 msgid "Add the following to your table:" -msgstr "" +msgstr "Adicione o seguinte à sua tabela:" #: ../../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!" +"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 "" +"Uma **description** do seu pacote. Deve ser uma única linha e descrever " +"brevemente o objetivo do seu pacote usando termos não técnicos, se possível!" #: ../../tutorials/pyproject-toml.md:184 msgid "package **authors**" -msgstr "" +msgstr "**authors** do pacote" #: ../../tutorials/pyproject-toml.md:185 msgid "package **maintainers**" -msgstr "" +msgstr "**maintainers** do pacote" #: ../../tutorials/pyproject-toml.md:187 msgid "The `description` is just a string like the other values you've set:" -msgstr "" +msgstr "A `description` é apenas uma string como os outros valores que você definiu:" #: ../../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 "" +"Ao adicionar authors e maintainers, você precisa usar um formato que " +"parecerá uma lista Python com um dicionário dentro dela:" #: ../../tutorials/pyproject-toml.md:212 msgid "Author names & emails" -msgstr "" +msgstr "Nomes e e-mails dos autores" #: ../../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 " -"or maintainers, like this:" +"the pyproject.toml. If you are missing the email for one or more authors or " +"maintainers, like this:" msgstr "" +"Há uma peculiaridade no PyPI para autores que têm nomes, mas não e-mails, " +"no pyproject.toml. Se estiver faltando o e-mail de um ou mais autores ou " +"mantenedores, como neste caso:" #: ../../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:" +"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 "" +"Então sugerimos que você forneça apenas nomes na sua lista de nomes para " +"garantir que tudo seja renderizado corretamente na sua página do PyPI — " +"assim:" #: ../../tutorials/pyproject-toml.md:234 msgid "don't have emails for everyone, we suggest that you only add names." -msgstr "" +msgstr "não tiver e-mails para todos, sugerimos que você adicione apenas nomes." #: ../../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 " -"your package:" +"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 your " +"package:" msgstr "" +"Seu arquivo `pyproject.toml` agora deve se parecer com o exemplo abaixo. " +"Está tudo bem se você tiver apenas 1 autor e o mesmo autor também for " +"mantenedor do seu pacote:" #: ../../tutorials/pyproject-toml.md msgid "" "Learn More: What's the difference between author and maintainer in open " "source?" -msgstr "" +msgstr "Saiba mais: Qual é a diferença entre author e maintainer em open source?" #: ../../tutorials/pyproject-toml.md:265 msgid "" "When adding maintainers and authors, you may want to think about the " "difference between the two." msgstr "" +"Ao adicionar maintainers e authors, você pode querer pensar na diferença " +"entre os dois." #: ../../tutorials/pyproject-toml.md:267 msgid "Authors generally include people who:" -msgstr "" +msgstr "Authors geralmente incluem pessoas que:" #: ../../tutorials/pyproject-toml.md:268 msgid "originally created / designed developed the package and" -msgstr "" +msgstr "criaram / projetaram originalmente o pacote e" #: ../../tutorials/pyproject-toml.md:269 msgid "people who add new functionality to the package." -msgstr "" +msgstr "pessoas que adicionam nova funcionalidade ao pacote." #: ../../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" -" maintainers. As such these lists may be similar or the same." +"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 " +"maintainers. As such these lists may be similar or the same." msgstr "" +"Já os maintainers são as pessoas que estão atualmente trabalhando " +"ativamente no projeto. Muitas vezes há sobreposição entre authors e " +"maintainers. Por isso, essas listas podem ser semelhantes ou iguais." #: ../../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 " -"maintainer to move on to other things. This person may continue to be " +"A good example of when the lists might diverge is sometimes you have " +"apackage where an initial author developed it and then stepped down asa " +"maintainer to move on to other things. This person may continue tobe " "considered an author but no longer actively maintains the package." msgstr "" +"Um bom exemplo de quando as listas podem divergir é quando um autor inicial " +"desenvolveu o pacote e depois deixou de ser mantenedor para seguir para " +"outras coisas. Essa pessoa pode continuar sendo considerada author, mas não " +"mantém mais ativamente o pacote." #: ../../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 "" +"É importante notar que há muitas formas de definir author vs maintainer e " +"não prescrevemos uma abordagem única neste tutorial." #: ../../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." +"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 "" +"No entanto, incentivamos você a considerar cuidadosamente, para publicação " +"no PyPI, quem você quer listar como authors e maintainers na página inicial " +"do seu pacote no PyPI." #: ../../tutorials/pyproject-toml.md:281 msgid "Step 2: Add README and license" -msgstr "" +msgstr "Passo 2: Adicionar README e license" #: ../../tutorials/pyproject-toml.md:283 msgid "" -"In the previous lessons, you added both a [README.md](add-readme) file " -"and a [LICENSE](add-license-coc) to your package repository. Once you " -"have those files, you can refer to the README from your pyproject.toml " -"file, and add a short code indicating your choice of LICENSE following " -"the example below." +"In the previous lessons, you added both a [README.md](add-readme) file and a " +"[LICENSE](add-license-coc) to your package repository. Once you have those " +"files, you can refer to the README from your pyproject.tomlfile, and add a " +"short code indicating your choice of LICENSE following the example below." msgstr "" +"Nas lições anteriores, você adicionou tanto um arquivo " +"[README.md](add-readme) quanto um [LICENSE](add-license-coc) ao repository " +"do seu pacote. Depois de ter esses arquivos, você pode referenciar o README " +"a partir do seu arquivo pyproject.toml e adicionar um código curto " +"indicando sua escolha de LICENSE seguindo o exemplo abaixo." #: ../../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" -"/license-expression/). Often this is a short name (with no spaces) for " -"the license, such as \"MIT\", \"BSD-3-Clause\" or \"Apache-2.0\". More " -"precisely, it must be a valid SPDX license expression, as documented in " -"the [SPDX specification](https://spdx.github.io/spdx-spec/v2.2.2/SPDX-" -"license-expressions/), either version 2.2 or a later compatible version." -msgstr "" +"expression " +"syntax](https://packaging.python.org/en/latest/specifications/license-expres" +"sion/). Often this is a short name(withnospaces) for the license, such as \"MIT\", " +"\"BSD-3-Clause\" or\"Apache-2.0\". More precisely, it must be a valid SPDX " +"license expression, as documented in the [SPDX " +"specification](https://spdx.github.io/spdx-spec/v2.2.2/SPDX-license-expressi" +"ons/), either version 2.2 or a later compatible version." +msgstr "" +"A entrada license no seu arquivo pyproject.toml deve usar a [sintaxe de " +"expressão de " +"license](https://packaging.python.org/en/latest/specifications/license-expre" +"ssion/). Muitas vezes é um nome curto (sem espaços) para a license, como \"MIT\", " +"\"BSD-3-Clause\" ou \"Apache-2.0\". Mais precisamente, deve ser uma expressão " +"de license SPDX válida, conforme documentado na [especificação " +"SPDX](https://spdx.github.io/spdx-spec/v2.2.2/SPDX-license-expressions/),seja" +" a versão 2.2 ou uma versão compatível posterior." #: ../../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 "" +"Se você tiver múltiplas licenses ou uma license personalizada, também pode " +"expressá-las usando uma expressão de license." #: ../../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 " -"[`license-files`](https://packaging.python.org/en/latest/guides/writing-" -"pyproject-toml/#license-files) entry, but this is not required." +"[`license-files`](https://packaging.python.org/en/latest/guides/writing-pypr" +"oject-toml/#license-files)entry, but this is not required." msgstr "" +"Se quiser distribuir arquivos de license ou outros arquivos com informações " +"legais junto com seu pacote, pode incluí-los usando a entrada " +"[`license-files`](https://packaging.python.org/en/latest/guides/writing-pypr" +"oject-toml/#license-files), mas isso não é obrigatório." #: ../../tutorials/pyproject-toml.md:318 msgid "Step 3: Specify Python version with `requires-python`" -msgstr "" +msgstr "Passo 3: Especificar a versão do Python com `requires-python`" #: ../../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 " -"versions that your package supports. It is set to a single value. The " -"[packaging " -"specification](https://packaging.python.org/en/latest/specifications" -"/core-metadata/#core-metadata-requires-python) defines`requires-python` " -"as a string that uses version specifiers. Most projects will specify the " -"oldest Python version supported by the package. In some advanced cases, " -"an upper bound is set to indicate which future Python versions, if any, " -"will be supported." -msgstr "" +"Add the `requires-python` field to your `pyproject.toml` `[project]` table. " +"The `requires-python` field helps pip identify which Python versions that " +"your package supports. It is set to a single value. The [packaging " +"specification](https://packaging.python.org/en/latest/specifications/core-me" +"tadata/#core-metadata-requires-python)defines `requires-python" +" `as a string that uses version specifiers. Most projects will specify the oldest " +"Python version supported by the package. In some advanced cases, an upper " +"bound is set to indicate which future Python versions, if any, will be " +"supported." +msgstr "" +"Adicione o campo `requires-python` à tabela `[project]` do seu " +"`pyproject.toml`. O campo `requires-python` ajuda o pip a identificar quais " +"versões do Python o seu pacote suporta. Ele é definido como um único valor. " +"A [especificação de " +"empacotamento](https://packaging.python.org/en/latest/specifications/core-me" +"tadata/#core-metadata-requires-python)define `requires-python` como uma string " +"que usa especificadores de versão. A maioria dos projetos especifica a " +"versão mais antiga do Python suportada pelo pacote. Em alguns casos " +"avançados, um limite superior é definido para indicar quais versões futuras " +"do Python, se houver, serão suportadas." #: ../../tutorials/pyproject-toml.md:325 msgid "But how do I figure out which Python versions I should support?" -msgstr "" +msgstr "Mas como descubro quais versões do Python devo suportar?" #: ../../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) " -"that explains the status of each Python release. Python releases go " -"through several different phases that are explained in [PEP " +"that explains the status of each Python release. Python releases go through " +"several different phases that are explained in [PEP " "602](https://peps.python.org/pep-0602/)." msgstr "" +"Boa pergunta. O guia do desenvolvedor Python fornece uma [página de " +"status](https://devguide.python.org/versions/) (e uma visualização útil) " +"que explica o status de cada release do Python. Os releases do Python " +"passam por várias fases diferentes, explicadas no [PEP " +"602](https://peps.python.org/pep-0602/)." #: ../../tutorials/pyproject-toml.md:329 msgid "" @@ -6401,105 +7193,147 @@ msgid "" "phase. If your Python release is in the **security** phase, we recommend " "migrating to a newer version of Python." msgstr "" +"Recomendamos que você use o release mais recente do Python na fase de " +"**bugfix**. Se o seu release do Python estiver na fase de **security**, " +"recomendamos migrar para uma versão mais nova do Python." #: ../../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, " -"including Python release versions, and is also worth considering for your" -" project." +"[SPEC 0](https://scientific-python.org/specs/spec-0000/) of the Scientific " +"Python project suggests a common schedule for dependencies, including Python " +"release versions, and is also worth considering for your project." msgstr "" +"O [SPEC 0](https://scientific-python.org/specs/spec-0000/) do projeto " +"Scientific Python sugere um cronograma comum para dependências, incluindo " +"versões de release do Python, e também vale a pena considerar para o seu " +"projeto." #: ../../tutorials/pyproject-toml.md:360 msgid "Step 4: Specify Dependencies" -msgstr "" +msgstr "Passo 4: Especificar Dependencies" #: ../../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 " +"Next add your dependencies table to the project table. The `dependencies =` " +"section contains a list (or array in the toml language) of the Python " "packages that your package requires to run properly in a Python " "environment. Similar to the requirements listed in the `[build-system]` " "table above:" msgstr "" +"Em seguida, adicione sua tabela de dependencies à tabela project. A seção " +"`dependencies =` contém uma lista (ou array na linguagem toml) dos pacote " +"Pythons que o seu pacote precisa para funcionar corretamente em um ambiente " +"Python. Semelhante aos requirements listados na tabela `[build-system]` " +"acima:" #: ../../tutorials/pyproject-toml.md:370 msgid "dependencies are added in an array (similar to a Python list) structure." msgstr "" +"as dependencies são adicionadas em uma estrutura de array (semelhante a uma " +"lista Python)." #: ../../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 " -"dependency name, your package can use any version of the dependent " -"package. Code changes over time, bugs are fixed, APIs change, and so it's" -" good to be clear about which version of the dependency you wrote your " -"code to be compatible with - a package you wrote this year probably isn't" -" compatible with numpy v0.0.1!" -msgstr "" +"dependency name, your package can use any version of the dependent package. " +"Code changes over time, bugs are fixed, APIs change, and so it's good to be " +"clear about which version of the dependency you wrote your code to be " +"compatible with - a package you wrote this year probably isn't compatible " +"with numpy v0.0.1!" +msgstr "" +"Uma dependency pode ser limitada a versões específicas usando um " +"**especificador de versão.** Se a dependency não tiver especificador de " +"versão após o nome da dependency, seu pacote pode usar qualquer versão do " +"pacote dependente. O código muda com o tempo, bugs são corrigidos, APIs " +"mudam, e por isso é bom ser claro sobre qual versão da dependency seu " +"código foi escrito para ser compatível — um pacote que você escreveu este " +"ano provavelmente não é compatível com numpy v0.0.1!" #: ../../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-" -"specifiers/#id5)" +"here.](https://packaging.python.org/en/latest/specifications/version-specifi" +"ers/#id5)" msgstr "" +"[Saiba mais sobre várias formas de especificar intervalos de versões de " +"pacotes " +"aqui.](https://packaging.python.org/en/latest/specifications/version-specifi" +"ers/#id5)" #: ../../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" -" the lowest version that is still compatible with your package, but in " -"practice for new packages this is often set at the version that was " -"current at the time the package was written[^lowerbound]." +"version higher than the specified version. Ideally you should set this to " +"the lowest version that is still compatible with your package, but in " +"practice for new packages this is often set at the version that was current " +"at the time the package was written[^lowerbound]." msgstr "" +"O especificador de versão mais comum é um **limite inferior,** permitindo " +"qualquer versão superior à versão especificada. Idealmente você deve " +"definir isso para a versão mais baixa que ainda é compatível com seu pacote, " +"mas na prática, para pacotes novos, isso costuma ser definido na versão que " +"estava atual no momento em que o pacote foi escrito[^lowerbound]." #: ../../tutorials/pyproject-toml.md:387 msgid "Lower bounds look like this:" -msgstr "" +msgstr "Limites inferiores ficam assim:" #: ../../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 " -"specifiers:" +"your `dependencies` section can use different types of version specifiers:" msgstr "" +"Vírgulas são usadas para separar dependencies individuais, e cada pacote na " +"sua seção `dependencies` pode usar diferentes tipos de especificadores de " +"versão:" #: ../../tutorials/pyproject-toml.md:404 msgid "Your `pyproject.toml` file will now look like this:" -msgstr "" +msgstr "Seu arquivo `pyproject.toml` agora ficará assim:" #: ../../tutorials/pyproject-toml.md:434 msgid "Pin dependencies with caution" -msgstr "" +msgstr "Fixe dependencies com cautela" #: ../../tutorials/pyproject-toml.md:435 -msgid "" -"\"Pinning\" a dependency means setting it to a specific version, like " -"this:" +msgid "\"Pinning\" a dependency means setting it to a specific version, like this:" msgstr "" +"\"Fixar\" (pinning) uma dependency significa defini-la para uma " +"versão específica, assim:" #: ../../tutorials/pyproject-toml.md:437 msgid "`numpy == 1.0`." -msgstr "" +msgstr "`numpy == 1.0`." #: ../../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 " -"version. Applications, such as production websites, will often pin their " -"dependencies since other packages will not depend on their project. This " -"is because users will be installing your package into various " -"environments. A dependency pinned to a single specific version can make " -"resolving a Python environment more challenging. As such only pin " -"dependencies to a specific version if you absolutely need to do so." -msgstr "" +"upon, you must be cautious before pinning to a precise dependency version. " +"Applications, such as production websites, will often pin their " +"dependencies since other packages will not depend on their project. This is " +"because users will be installing your package into various environments. A " +"dependency pinned to a single specific version can make resolving a Python " +"environment more challenging. As such only pin dependencies to a specific " +"version if you absolutely need to do so." +msgstr "" +"Se você está construindo um pacote de biblioteca do qual outros " +"desenvolvedores dependerão, deve ser cauteloso antes de fixar uma " +"dependency em uma versão precisa. Aplicações, como sites de produção, " +"frequentemente fixam suas dependencies, já que outros pacotes não " +"dependerão do projeto delas. Isso porque os usuários instalarão seu pacote " +"em vários ambientes. Uma dependency fixada em uma única versão específica " +"pode tornar a resolução de um ambiente Python mais desafiadora. Portanto, " +"fixe dependencies em uma versão específica somente se você absolutamente " +"precisar fazer isso." #: ../../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 "" +"Da mesma forma, você deve ser cauteloso ao especificar um limite superior " +"em um pacote. Essas duas especificações são equivalentes:" #: ../../tutorials/pyproject-toml.md:455 msgid "" @@ -6507,223 +7341,281 @@ msgid "" "upper bound by default is Poetry. [Read more about how to safely add " "dependencies with Poetry, here.](challenges-with-poetry)" msgstr "" +"Uma ferramenta de build que você deve conhecer e que fixa dependencies com " +"um limite superior por padrão é o Poetry. [Leia mais sobre como adicionar " +"dependencies com segurança usando Poetry, aqui.](challenges-with-poetry)" #: ../../tutorials/pyproject-toml.md:458 msgid "Step 5: Add PyPI classifiers" -msgstr "" +msgstr "Passo 5: Adicionar classifiers do PyPI" #: ../../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 " -"from the list of [PyPI accepted classifier values found " -"here](https://PyPI.org/classifiers/). Any deviations in spelling and " -"format will cause issues when you publish to PyPI." +"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 from " +"the list of [PyPI accepted classifier values found " +"here](https://PyPI.org/classifiers/). Any deviations in spelling and format " +"will cause issues when you publish to PyPI." msgstr "" +"Em seguida, você adicionará classifiers ao seu arquivo `pyproject.toml`. O " +"valor de cada classifier que você adicionar ao seu arquivo `pyproject.toml` " +"deve vir da lista de [valores de classifiers aceitos pelo PyPI encontrada " +"aqui](https://PyPI.org/classifiers/). Qualquer desvio na ortografia e no " +"formato causará problemas quando você publicar no PyPI." #: ../../tutorials/pyproject-toml.md:462 msgid "What happens when you use incorrect classifiers?" -msgstr "" +msgstr "O que acontece quando você usa classifiers incorretos?" #: ../../tutorials/pyproject-toml.md:465 msgid "" "If you do not [use standard classifier " "values](https://PyPI.org/classifiers/), when you try to publish your " -"package on PyPI it will be rejected. 😔 Don't worry if PyPI rejects you on" -" your first try! It has happened to all of us." +"package on PyPI it will be rejected. 😔 Don't worry if PyPI rejects you " +"on your first try! It has happened to all of us." msgstr "" +"Se você não [usar valores de classifiers " +"padrão](https://PyPI.org/classifiers/), ao tentar publicar seu pacote no " +"PyPI ele será rejeitado. 😔 Não se preocupe se o PyPI rejeitar você na " +"primeira tentativa! Isso aconteceu com todos nós." #: ../../tutorials/pyproject-toml.md:468 msgid "Review that list and add items below to your `pyproject.toml` file:" msgstr "" +"Revise essa lista e adicione os itens abaixo ao seu arquivo " +"`pyproject.toml`:" #: ../../tutorials/pyproject-toml.md:470 msgid "development status" -msgstr "" +msgstr "development status" #: ../../tutorials/pyproject-toml.md:471 msgid "intended audiences" -msgstr "" +msgstr "intended audiences" #: ../../tutorials/pyproject-toml.md:472 msgid "topic" -msgstr "" +msgstr "topic" #: ../../tutorials/pyproject-toml.md:473 msgid "programming language support" -msgstr "" +msgstr "programming language support" #: ../../tutorials/pyproject-toml.md:475 -msgid "" -"The classifier key should look something like the example below. A few " -"notes:" +msgid "The classifier key should look something like the example below. A few notes:" msgstr "" +"A chave classifier deve se parecer com o exemplo abaixo. Algumas " +"observações:" #: ../../tutorials/pyproject-toml.md:477 msgid "" -"Your classifier values might be different depending upon your intended " -"audience, development status of your package and the Python versions that" -" you support" +"Your classifier values might be different depending upon your " +"intended audience, development status of your package and the Python " +"versions that you support" msgstr "" +"Seus valores de classifiers podem ser diferentes dependendo do " +"público-alvo, do status de desenvolvimento do seu pacote e das versões do " +"Python que você suporta" #: ../../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 "" +"Você pode adicionar quantos classifiers quiser, desde que use os [valores " +"de classifiers designados pelo PyPI](https://PyPI.org/classifiers/)." #: ../../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 " -"recommend that you add them." +"Note that while classifiers are not required in your `pyproject.toml` file, " +"they will help users find your package. As such we strongly recommend that " +"you add them." msgstr "" +"Observe que, embora os classifiers não sejam obrigatórios no seu arquivo " +"`pyproject.toml`, eles ajudarão os usuários a encontrar seu pacote. Por " +"isso, recomendamos fortemente que você os adicione." #: ../../tutorials/pyproject-toml.md:519 msgid "Step 6: Add the `[project.urls]` table" -msgstr "" +msgstr "Passo 6: Adicionar a tabela `[project.urls]`" #: ../../tutorials/pyproject-toml.md:521 msgid "Finally, add the project.urls table to your pyproject.toml file." -msgstr "" +msgstr "Por fim, adicione a tabela project.urls ao seu arquivo pyproject.toml." #: ../../tutorials/pyproject-toml.md:523 msgid "" -"`project.urls` contains links that are relevant for your project. You " -"might want to include:" +"`project.urls` contains links that are relevant for your project. You might " +"want to include:" msgstr "" +"`project.urls` contém links relevantes para o seu projeto. Você pode querer " +"incluir:" #: ../../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 " -"yet. That's ok, you can skip it for the time being." +"**Homepage:** A link to your published documentation for your project. If " +"you are working through this tutorial, then you may not have this link yet. " +"That's ok, you can skip it for the time being." msgstr "" +"**Homepage:** Um link para a documentação publicada do seu projeto. Se você " +"está seguindo este tutorial, talvez ainda não tenha esse link. Tudo bem, " +"você pode pular por enquanto." #: ../../tutorials/pyproject-toml.md:526 msgid "" "**Bug reports:** a link to your issues/discussions or wherever you want " "users to report bugs." msgstr "" +"**Bug reports:** um link para suas issues/discussions ou para onde você " +"quer que os usuários reportem bugs." #: ../../tutorials/pyproject-toml.md:527 msgid "**Source:** the GitHub / GitLab link for your project." -msgstr "" +msgstr "**Fonte:** o link do GitHub / GitLab do seu projeto." #: ../../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)." +"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)." msgstr "" +"Há muitas outras URLs que você pode adicionar aqui. Confira o " +"[arquivo README aqui para uma visão " +"geral](https://github.com/patrick91/links-demo)." #: ../../tutorials/pyproject-toml.md:575 msgid "Putting it all together - your completed pyproject.toml file" -msgstr "" +msgstr "Juntando tudo — seu arquivo pyproject.toml completo" #: ../../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." +"Below is an example of a complete `pyproject.toml` file that is commented " +"with all of the sections we discussed above." msgstr "" +"Abaixo está um exemplo de um arquivo `pyproject.toml` completo, com " +"comentários em todas as seções que discutimos acima." #: ../../tutorials/pyproject-toml.md msgid "Appendix - Click for a fully commented pyproject.toml file" -msgstr "" +msgstr "Apêndice — Clique para ver um arquivo pyproject.toml totalmente comentado" #: ../../tutorials/pyproject-toml.md:626 msgid "" "Below is a fully commented pyproject.toml file if you want to use it for " "reference." msgstr "" +"Abaixo está um arquivo pyproject.toml totalmente comentado, caso queira " +"usá-lo como referência." #: ../../tutorials/pyproject-toml.md:692 msgid "Example `pyproject.toml` files" -msgstr "" +msgstr "Exemplos de arquivos `pyproject.toml`" #: ../../tutorials/pyproject-toml.md:694 msgid "" -"Below are some examples of `pyproject.toml` files from various packages " -"in the scientific and pyOpenSci ecosystem." +"Below are some examples of `pyproject.toml` files from various packages in " +"the scientific and pyOpenSci ecosystem." msgstr "" +"Abaixo estão alguns exemplos de arquivos `pyproject.toml` de vários pacotes " +"no ecossistema científico e pyOpenSci." #: ../../tutorials/pyproject-toml.md:695 msgid "" "[PyPA's fully documented example pyproject.toml " "file](https://github.com/pypa/sampleproject/blob/main/pyproject.toml)" msgstr "" +"[Arquivo pyproject.toml de exemplo totalmente documentado do " +"PyPA](https://github.com/pypa/sampleproject/blob/main/pyproject.toml)" #: ../../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)" +"package](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a53" +"dd49ad77e4cf143573/pyproject.toml)" msgstr "" +"[taxpasta tem um arquivo pyproject.toml bem organizado e é um pacote " +"aprovado pelo " +"pyOpenSci](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a" +"53dd49ad77e4cf143573/pyproject.toml)" #: ../../tutorials/pyproject-toml.md:702 msgid "At this point you've created:" -msgstr "" +msgstr "Neste ponto, você já criou:" #: ../../tutorials/pyproject-toml.md:704 msgid "A [README.md](add-readme) file for your package" -msgstr "" +msgstr "Um arquivo [README.md](add-readme) para seu pacote" #: ../../tutorials/pyproject-toml.md:705 msgid "A [CODE_OF_CONDUCT.md](add-coc) file to support your user community" msgstr "" +"Um arquivo [CODE_OF_CONDUCT.md](add-coc) para apoiar sua comunidade " +"de usuários" #: ../../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" msgstr "" +"E um arquivo [LICENSE](add-license-coc) que define limites legais sobre " +"como as pessoas podem e não podem usar seu software" #: ../../tutorials/pyproject-toml.md:708 -msgid "" -"You also learned [how to publish your package to (test)PyPI](publish-" -"pypi)." -msgstr "" +msgid "You also learned [how to publish your package to (test)PyPI](publish-pypi)." +msgstr "Você também aprendeu [como publicar seu pacote no (test)PyPI](publish-pypi)." #: ../../tutorials/pyproject-toml.md:710 msgid "Publish a new version of your package to PyPI" -msgstr "" +msgstr "Publicar uma nova versão do seu pacote no PyPI" #: ../../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" -" package now contains a lot more information." +"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 package " +"now contains a lot more information." msgstr "" +"Agora você está pronto para publicar uma nova versão do seu pacote Python " +"no (test) PyPI. Ao fazer isso, verá que a página do seu pacote agora contém " +"muito mais informações." #: ../../tutorials/pyproject-toml.md:714 msgid "Try to republish now." -msgstr "" +msgstr "Tente republicar agora." #: ../../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`." +"First, update the version of your package in your pyproject toml file. Below " +"version is updated from `0.1` to `0.1.1`." msgstr "" +"Primeiro, atualize a versão do seu pacote no arquivo pyproject.toml. " +"Abaixo, a versão é atualizada de `0.1` para `0.1.1`." #: ../../tutorials/pyproject-toml.md:729 msgid "Now use hatch to publish the new version of your package to test.PyPI.org." msgstr "" +"Agora use o Hatch para publicar a nova versão do seu pacote em " +"test.PyPI.org." #: ../../tutorials/pyproject-toml.md:736 msgid "Next (optional) step - publishing to conda-forge" -msgstr "" +msgstr "Próximo passo (opcional) — publicar no conda-forge" #: ../../tutorials/pyproject-toml.md:738 msgid "" "You now have all of the skills that you need to publish your package to " "PyPI." msgstr "" +"Agora você tem todas as habilidades necessárias para publicar seu pacote no " +"PyPI." #: ../../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." +"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 "" +"Se você também quiser publicar seu pacote no conda-forge (que é um canal " +"dentro do ecossistema conda), aprenderá como fazer isso na próxima lição." #: ../../tutorials/pyproject-toml.md:745 msgid "" @@ -6731,88 +7623,115 @@ msgid "" "https://daniel.feldroy.com/posts/2023-08-pypi-project-urls-cheatsheet " "useful (and the linked links-demo even more so)" msgstr "" +"Recursos muito bons do Jeremiah " +"https://daniel.feldroy.com/posts/2023-08-pypi-project-urls-cheatsheet úteis " +"(e o links-demo linkado ainda mais)" #: ../../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-" -"poetry.org/docs/cli/#add) will add the most recent version with a `^` " -"specifier, and [`pdm add`](https://pdm-" -"project.org/latest/reference/cli/#add) will add the most recent version " -"with `>=`." +"Some packaging tools will do this for you when you add a dependency using " +"their cli interface. For example [`poetry " +"add`](https://python-poetry.org/docs/cli/#add) will add the most recent " +"version with a `^` specifier, and [`pdm " +"add`](https://pdm-project.org/latest/reference/cli/#add) will add the most " +"recent version with `>=`." msgstr "" +"Algumas ferramentas de empacotamento fazem isso por você quando você " +"adiciona uma dependência usando a interface CLI delas. Por exemplo, " +"[`poetry add`](https://python-poetry.org/docs/cli/#add) adicionará a versão " +"mais recente com um especificador `^`, e [`pdm " +"add`](https://pdm-project.org/latest/reference/cli/#add) adicionará a " +"versão mais recente com `>=`." #: ../../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." +"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 "" +"O Python suporta metadata inline para scripts (um recurso adicionado em " +"2024). Isso torna possível executar scripts independentes com dependências " +"e versões do Python gerenciadas automaticamente." #: ../../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." +"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 "" +"Muitas ferramentas suportam esse workflow, incluindo PDM, " +"[Hatch](get-to-know-hatch) e {term}`uv`. Neste tutorial, focamos no Hatch e " +"no UV. O mesmo formato de metadata também pode ser usado com outras " +"ferramentas." #: ../../tutorials/run-python-scripts-hatch.md:22 msgid "" -"[Hatch: How to run Python scripts](https://hatch.pypa.io/latest/how-" -"to/run/python-scripts/)" +"[Hatch: How to run Python " +"scripts](https://hatch.pypa.io/latest/how-to/run/python-scripts/)" msgstr "" +"[Hatch: Como executar scripts " +"Python](https://hatch.pypa.io/latest/how-to/run/python-scripts/)" #: ../../tutorials/run-python-scripts-hatch.md:23 msgid "" "[uv: Running " -"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-" -"script)" +"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)" msgstr "" +"[uv: Executando " +"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)" #: ../../tutorials/run-python-scripts-hatch.md:26 msgid "How to create a reproducible script" -msgstr "" +msgstr "Como criar um script reproduzível" #: ../../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." +"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 "" +"Às vezes você quer compartilhar ou executar um único script sem criar um " +"{term}`pacote Python ` completo. Para isso, você pode usar " +"metadata inline de script. Esse formato permite especificar dependências e " +"versões do Python no topo do seu script em um bloco de comentários." #: ../../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:" +"When you add metadata at the top of a script, Hatch (or PDM or uv) will use " +"that metadata to:" msgstr "" +"Quando você adiciona metadata no topo de um script, o Hatch (ou PDM ouuv) " +"usará essa metadata para:" #: ../../tutorials/run-python-scripts-hatch.md:37 msgid "Create an isolated virtual Python environment for that script." -msgstr "" +msgstr "Criar um virtual environment Python isolado para esse script." #: ../../tutorials/run-python-scripts-hatch.md:38 #, python-brace-format -msgid "" -"Install the {term}`Dependencies` listed in the script into that " -"environment." +msgid "Install the {term}`Dependencies` listed in the script into that environment." msgstr "" +"Instalar as {term}`dependências ` listadas no script nesse " +"environment." #: ../../tutorials/run-python-scripts-hatch.md:39 msgid "Use the required Python version that you specify in the metadata." -msgstr "" +msgstr "Usar a versão do Python exigida que você especificar na metadata." #: ../../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." +"This approach is useful for workflows that you want to make reproducible, " +"but that do not need to become full Python packages." msgstr "" +"Essa abordagem é útil para workflows que você quer tornar reproduzíveis, " +"mas que não precisam se tornar pacote Pythons completos." #: ../../tutorials/run-python-scripts-hatch.md:44 msgid "Why use Hatch for scripts?" -msgstr "" +msgstr "Por que usar o Hatch para scripts?" #: ../../tutorials/run-python-scripts-hatch.md:46 msgid "" @@ -6821,384 +7740,491 @@ msgid "" "dependencies it needs. Hatch takes care of installing dependencies and " "using the correct Python version." msgstr "" +"Metadata inline ajuda você a tornar scripts reproduzíveis. Qualquer pessoa " +"pode executar seu script sem criar manualmente um novo environment ou " +"adivinhar quais dependências ele precisa. O Hatch cuidade instalar as " +"dependências e usar a versão correta do Python." #: ../../tutorials/run-python-scripts-hatch.md:51 msgid "How to add inline metadata to your script" -msgstr "" +msgstr "Como adicionar metadata inline ao seu script" #: ../../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." +"You will use Hatch in this example, but you can also use uv if that is your " +"preferred tool." msgstr "" +"Você usará o Hatch neste exemplo, mas também pode usar o uv se essa for sua " +"ferramenta preferida." #: ../../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." +"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 "" +"Primeiro, crie um novo arquivo chamado `script.py` com o bloco abaixo no " +"topo. O bloco de metadata começa com `# /// script` e termina com `# ///`. " +"Tudo entre eles deve ser metadata {term}`TOML` escrita como comentários." #: ../../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." +"In the example below, the script requires Python 3.11 or newer, and NumPy " +"is declared as a dependency." msgstr "" +"No exemplo abaixo, o script requer Python 3.11 ou mais recente, e o NumPy é " +"declarado como dependência." #: ../../tutorials/run-python-scripts-hatch.md:81 msgid "Run the script with Hatch" -msgstr "" +msgstr "Executar o script com o Hatch" #: ../../tutorials/run-python-scripts-hatch.md:83 msgid "" "Open your terminal and change to the directory where `script.py` lives. " "Then run:" msgstr "" +"Abra seu terminal e mude para o diretório onde `script.py` está. Em " +"seguida, execute:" #: ../../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." +"On first run, Hatch will create an environment and install dependencies. On " +"later runs, Hatch will reuse that environment so startup is faster." msgstr "" +"Na primeira execução, o Hatch criará um environment e instalará as " +"dependências. Nas execuções seguintes, o Hatch reutilizará esse environment " +"para que a inicialização seja mais rápida." #: ../../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." +"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 "" +"O nome do environment é baseado no caminho do script. Se você mover o " +"script para um novo local, o Hatch o tratará como um novo script " +"environment." #: ../../tutorials/run-python-scripts-hatch.md:98 msgid "Optional: configure script environment behavior" -msgstr "" +msgstr "Opcional: configurar o comportamento do script environment" #: ../../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:" +"You can control script-specific Hatch behavior in the same metadata block. " +"For example, to use `pip` instead of `uv` as the installer:" msgstr "" +"Você pode controlar o comportamento específico do Hatch para scripts no " +"mesmo bloco de metadata. Por exemplo, para usar `pip` em vez de `uv` como " +"instalador:" #: ../../tutorials/run-python-scripts-hatch.md:113 msgid "Run the same script with uv" -msgstr "" +msgstr "Executar o mesmo script com uv" #: ../../tutorials/run-python-scripts-hatch.md:115 msgid "If you prefer uv, you can run the same inline-metadata script with:" -msgstr "" +msgstr "Se você preferir o uv, pode executar o mesmo script com metadata inline com:" #: ../../tutorials/run-python-scripts-hatch.md:121 msgid "" "The same `# /// script` metadata block works with uv, including " "`requires-python` and `dependencies`." msgstr "" +"O mesmo bloco de metadata `# /// script` funciona com uv, incluindo " +"`requires-python` e `dependencies`." #: ../../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)." +"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 "" +"Para mais informações sobre como usar o uv para executar scripts, consulte " +"o guia: [Executando scripts com " +"uv](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)." #: ../../tutorials/run-python-scripts-hatch.md:128 msgid "When to use scripts vs. packages" -msgstr "" +msgstr "Quando usar scripts vs. pacotes" #: ../../tutorials/run-python-scripts-hatch.md:130 msgid "You may be wondering when to use scripts versus creating a package." msgstr "" +"Você pode estar se perguntando quando usar scripts em vez de criar um " +"pacote." #: ../../tutorials/run-python-scripts-hatch.md:132 msgid "This depends on your use case. Scripts are often useful when:" -msgstr "" +msgstr "Isso depende do seu caso de uso. Scripts costumam ser úteis quando:" #: ../../tutorials/run-python-scripts-hatch.md:134 msgid "You have one small task, or a specific workflow that is not generalizable." msgstr "" +"Você tem uma tarefa pequena ou um workflow específico que não é " +"generalizável." #: ../../tutorials/run-python-scripts-hatch.md:135 msgid "" -"Your workflow is still evolving, but you want to run it in a reproducible" -" environment." +"Your workflow is still evolving, but you want to run it in a reproducible " +"environment." msgstr "" +"Seu workflow ainda está evoluindo, mas você quer executá-lo em um " +"environment reproduzível." #: ../../tutorials/run-python-scripts-hatch.md:137 msgid "You want reproducible dependencies quickly." -msgstr "" +msgstr "Você quer dependências reproduzíveis rapidamente." #: ../../tutorials/run-python-scripts-hatch.md:138 msgid "You are sharing a single file with collaborators." -msgstr "" +msgstr "Você está compartilhando um único arquivo com colaboradores." #: ../../tutorials/run-python-scripts-hatch.md:140 msgid "Create a full package when:" -msgstr "" +msgstr "Crie um pacote completo quando:" #: ../../tutorials/run-python-scripts-hatch.md:142 msgid "You are building reusable modules for multiple projects." -msgstr "" +msgstr "Você está construindo modules reutilizáveis para vários projetos." #: ../../tutorials/run-python-scripts-hatch.md:143 msgid "You need tests, documentation, releases, and long-term maintenance." -msgstr "" +msgstr "Você precisa de testes, documentação, releases e manutenção de longo prazo." #: ../../tutorials/run-python-scripts-hatch.md:144 msgid "Your codebase is growing beyond one or two scripts." -msgstr "" +msgstr "Sua base de código está crescendo além de um ou dois scripts." #: ../../tutorials/run-python-scripts-hatch.md:148 msgid "[Get to know Hatch](get-to-know-hatch.md)" -msgstr "" +msgstr "[Conheça o Hatch](get-to-know-hatch.md)" #: ../../tutorials/run-python-scripts-hatch.md:149 msgid "[Create a Python package](create-python-package.md)" -msgstr "" +msgstr "[Criar um pacote Python](create-python-package.md)" #: ../../tutorials/run-python-scripts-hatch.md:150 msgid "[Command line reference guide](command-line-reference.md)" -msgstr "" +msgstr "[Guia de referência da linha de comando](command-line-reference.md)" #: ../../tutorials/setup-py-to-pyproject-toml.md:7 msgid "Using Hatch to Migrate setup.py to a pyproject.toml" -msgstr "" +msgstr "Usando o Hatch para migrar setup.py para pyproject.toml" #: ../../tutorials/setup-py-to-pyproject-toml.md:9 msgid "" -"[Hatch](get-to-know-hatch) can be useful for generating your project's " -"[pyproject.toml](pyproject-toml) file if your project already has a " +"[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 "" +"O [Hatch](get-to-know-hatch) pode ser útil para gerar o arquivo " +"[pyproject.toml](pyproject-toml) do seu projeto se ele já tiver um arquivo " +"`setup.py`." #: ../../tutorials/setup-py-to-pyproject-toml.md:13 msgid "Note" -msgstr "" +msgstr "Nota" #: ../../tutorials/setup-py-to-pyproject-toml.md:16 msgid "" -"This step is not necessary and is only helpful if your project already " -"has a `setup.py` file defined." +"This step is not necessary and is only helpful if your project already has a " +"`setup.py` file defined." msgstr "" +"Esta etapa não é necessária e só é útil se seu projeto já tiver um arquivo " +"`setup.py` definido." #: ../../tutorials/setup-py-to-pyproject-toml.md:17 msgid "" -"If your project does not already define a `setup.py` see [Make your " -"Python code installable](create-python-package)" +"If your project does not already define a `setup.py` see [Make your Python " +"code installable](create-python-package)" msgstr "" +"Se seu projeto ainda não define um `setup.py`, consulte [Torne seu código " +"Python instalável](create-python-package)" #: ../../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." +"The process of using Hatch to transition to using `pyproject.toml` " +"for projects that already have a `setup.py` defined." msgstr "" +"O processo de usar o Hatch para fazer a transição para `pyproject.toml` em " +"projetos que já têm um `setup.py` definido." #: ../../tutorials/setup-py-to-pyproject-toml.md:28 msgid "What is Hatch?" -msgstr "" +msgstr "O que é o Hatch?" #: ../../tutorials/setup-py-to-pyproject-toml.md:30 #, 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 {term}`Dependencies`, building distributions, and " +"creating, managing, and distributing Python packages. It provides " +"a convenient CLI (Command-Line Interface) for tasks such as creating " +"new projects, managing {term}`Dependencies`, building distributions, and " "publishing packages to repositories like [PyPI](publish-pypi)." msgstr "" +"O Hatch é um gerenciador de pacote Pythons projetado para " +"simplificar o processo de criar, gerenciar e distribuir pacote Pythons. Ele " +"oferece uma CLI (Command-Line Interface) conveniente para tarefas como criar " +"novos projetos, gerenciar {term}`dependências `, fazer build " +"de distribuições e publicar pacotes em repositórios como o " +"[PyPI](publish-pypi)." #: ../../tutorials/setup-py-to-pyproject-toml.md:40 msgid "See [Get to know Hatch](get-to-know-hatch) for more information." -msgstr "" +msgstr "Consulte [Conheça o Hatch](get-to-know-hatch) para mais informações." #: ../../tutorials/setup-py-to-pyproject-toml.md:43 msgid "Prerequisites" -msgstr "" +msgstr "Pré-requisitos" #: ../../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:" +"Before we begin, ensure that you have Hatch installed on your system. You " +"can install it via pip:" msgstr "" +"Antes de começar, certifique-se de que o Hatch está instalado no seu " +"sistema. Você pode instalá-lo via pip:" #: ../../tutorials/setup-py-to-pyproject-toml.md:51 msgid "Sample Directory Tree" -msgstr "" +msgstr "Árvore de diretórios de exemplo" #: ../../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 "" +"Vamos dar uma olhada em uma estrutura de árvore de diretórios de exemplo " +"antes e depois de usar `hatch init`:" #: ../../tutorials/setup-py-to-pyproject-toml.md:55 msgid "Before `hatch init`" -msgstr "" +msgstr "Antes de `hatch init`" #: ../../tutorials/setup-py-to-pyproject-toml.md:71 msgid "After `hatch init`" -msgstr "" +msgstr "Depois de `hatch init`" #: ../../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." +"As you can see, the main change after running `hatch init` is the addition " +"of the `pyproject.toml` file in the project directory." msgstr "" +"Como você pode ver, a principal mudança após executar `hatch init` é " +"a adição do arquivo `pyproject.toml` no diretório do projeto." #: ../../tutorials/setup-py-to-pyproject-toml.md:91 msgid "Step-by-Step Guide" -msgstr "" +msgstr "Guia passo a passo" #: ../../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." +"Now, let's walk through the steps to use Hatch to create a `pyproject.toml` " +"file for your project." msgstr "" +"Agora, vamos percorrer os passos para usar o Hatch e criar um arquivo " +"`pyproject.toml` para seu projeto." #: ../../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." +"prompt and navigate to the directory where your Python project is located." msgstr "" +"**Navegue até o diretório do seu projeto**: Abra seu terminal ou prompt de " +"comando e navegue até o diretório onde seu projeto Python está localizado." #: ../../tutorials/setup-py-to-pyproject-toml.md:97 msgid "" -"**Initialize Hatch**: Run the following command to initialize Hatch in " -"your project directory:" +"**Initialize Hatch**: Run the following command to initialize Hatch in your " +"project directory:" msgstr "" +"**Inicialize o Hatch**: Execute o seguinte comando para inicializar o Hatch " +"no diretório do seu projeto:" #: ../../tutorials/setup-py-to-pyproject-toml.md:103 msgid "" "**Review and Customize**: After running the previous command, Hatch will " "automatically generate a `pyproject.toml` file based on your existing " "project configuration. Take some time to review the contents of the " -"generated `pyproject.toml` file. You may want to customize certain " -"settings or dependencies based on your project's requirements (see " -"[pyproject.toml tutorial](pyproject-toml) for more information about the " -"`pyproject.toml`)." -msgstr "" +"generated `pyproject.toml` file. You may want to customize certain settings " +"or dependencies based on your project's requirements (see [pyproject.toml " +"tutorial](pyproject-toml) for more information about the `pyproject.toml`)." +msgstr "" +"**Revise e personalize**: Após executar o comando anterior, o Hatch gerará " +"automaticamente um arquivo `pyproject.toml` com base na configuração " +"existente do seu projeto. Reserve um tempo para revisar o conteúdo do " +"arquivo `pyproject.toml` gerado. Você pode querer personalizar certas " +"configurações ou dependências com base nos requisitos do seu projeto " +"(consulte o [tutorial de pyproject.toml](pyproject-toml) para mais " +"informações sobre o `pyproject.toml`)." #: ../../tutorials/setup-py-to-pyproject-toml.md:105 msgid "" -"**Verify**: Verify that the `pyproject.toml` file accurately reflects " -"your project configuration and dependencies. You can manually edit the " -"file, but be cautious and ensure that the syntax is correct." +"**Verify**: Verify that the `pyproject.toml` file accurately reflects your " +"project configuration and dependencies. You can manually edit the file, but " +"be cautious and ensure that the syntax is correct." msgstr "" +"**Verifique**: Verifique se o arquivo `pyproject.toml` reflete com precisão " +"a configuração e as dependências do seu projeto. Você pode editar o arquivo " +"manualmente, mas tenha cuidado e certifique-se de que a sintaxe está correta." #: ../../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 " -"delete it from your project directory." +"exclusively, the `setup.py` file becomes unnecessary. You can safely delete " +"it from your project directory." msgstr "" +"**Exclua o setup.py**: Como estamos migrando para usar exclusivamente " +"`pyproject.toml`, o arquivo `setup.py` se torna desnecessário. Você pode " +"excluí-lo com segurança do diretório do seu projeto." #: ../../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. " -"Run the following command to build your project:" +"your project builds successfully using only the `pyproject.toml` file. Run " +"the following command to build your project:" msgstr "" +"**Teste o build**: Antes de prosseguir, é essencial garantir que seu " +"projeto faz build com sucesso usando apenas o arquivo `pyproject.toml`. " +"Execute o seguinte comando para fazer o build do seu projeto:" #: ../../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 " -"during the build process." +"`pyproject.toml` file. Make sure to check for any errors or warnings during " +"the build process." msgstr "" +"Este comando fará o build do seu projeto com base nas especificações do " +"arquivo `pyproject.toml`. Certifique-se de verificar se há erros ou avisos " +"durante o processo de build." #: ../../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 " -"existing functionality remains intact. Run any pre-existing tests to " -"verify that everything still works as expected." +"**Test Existing Functionality**: After successfully building your project " +"with `pyproject.toml`, it's crucial to ensure that your project's existing " +"functionality remains intact. Run any pre-existing tests to verify that " +"everything still works as expected." msgstr "" +"**Teste a funcionalidade existente**: Após fazer o build do seu projeto com " +"sucesso com `pyproject.toml`, é crucial garantir que a funcionalidade " +"existente do seu projeto permaneça intacta. Execute quaisquer testes " +"pré-existentes para verificar se tudo ainda funciona como esperado." #: ../../tutorials/trusted-publishing.md:6 msgid "" "Setup Trusted Publishing for secure and automated publishing via GitHub " "Actions" msgstr "" +"Configurar Trusted Publishing para publicação segura e automatizada via " +"GitHub Actions" #: ../../tutorials/trusted-publishing.md:8 msgid "In the previous Python packaging lessons, you learned:" -msgstr "" +msgstr "Nas lições anteriores de empacotamento Python, você aprendeu:" #: ../../tutorials/trusted-publishing.md:10 msgid "[How to create a Python package](create-python-package)" -msgstr "" +msgstr "[Como criar um pacote Python](create-python-package)" #: ../../tutorials/trusted-publishing.md:11 msgid "" -"How to publish the code to [PyPI](publish-pypi) and [Conda](publish-" -"conda-forge)" +"How to publish the code to [PyPI](publish-pypi) and " +"[Conda](publish-conda-forge)" msgstr "" +"Como publicar o código no [PyPI](publish-pypi) e no " +"[Conda](publish-conda-forge)" #: ../../tutorials/trusted-publishing.md:16 msgid "In this lesson, you will learn how to:" -msgstr "" +msgstr "Nesta lição, você aprenderá como:" #: ../../tutorials/trusted-publishing.md:18 msgid "Automate building and publishing the package on GitHub Actions" -msgstr "" +msgstr "Automatizar o build e a publicação do pacote no GitHub Actions" #: ../../tutorials/trusted-publishing.md:19 #, python-brace-format msgid "Configure {term}`Trusted publishing` for the project" -msgstr "" +msgstr "Configurar {term}`Trusted publishing` para o projeto" #: ../../tutorials/trusted-publishing.md:20 msgid "" "Secure your workflow using GitHub action hashes and versions in your " "workflow file" msgstr "" +"Proteger seu workflow usando hashes e versões de GitHub actions no arquivo " +"de workflow" #: ../../tutorials/trusted-publishing.md:22 msgid "" "This tutorial assumes that your project is hosted on GitHub and that you " "want to publish a package from your project to PyPI." msgstr "" +"Este tutorial assume que seu projeto está hospedado no GitHub e que você " +"quer publicar um pacote do seu projeto no PyPI." #: ../../tutorials/trusted-publishing.md:26 msgid "Configure a release job on GitHub Actions" -msgstr "" +msgstr "Configurar um job de release no GitHub Actions" #: ../../tutorials/trusted-publishing.md:28 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](publish-pypi)." -msgstr "" +"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](publish-pypi)." +msgstr "" +"O GitHub Actions[^gha] é uma infraestrutura fornecida pelo GitHub " +"para automatizar workflows de software, diretamente do repositório GitHub do " +"projeto. Você pode configurar testes automatizados para cada pull request, " +"automatizar a publicação de documentação, automatizar a criação de páginas " +"web para o projeto e até automatizar o processo de release. Para esta " +"lição, focaremos no uso de actions para fazer release e publicar seu pacote " +"Python com segurança no [PyPI](publish-pypi)." #: ../../tutorials/trusted-publishing.md:36 msgid "Why Trusted Publishing Matters" -msgstr "" +msgstr "Por que o Trusted Publishing é importante" #: ../../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-" -"security-publish-pypi.html) that dives deeper into what can happen when " -"you don't lock down your publishing workflows." +"this blog " +"post:](https://www.pyopensci.org/blog/python-packaging-security-publish-pypi" +".html)that dives deeper into what can happen when you don't lock down your " +"publishing workflows." msgstr "" +"Se você está se perguntando por que o trusted publishing é tão importante, " +"[confira este post do " +"blog:](https://www.pyopensci.org/blog/python-packaging-security-publish-pypi" +".html)que aprofunda o que pode acontecer quando você não protege seus " +"workflows de publicação." #: ../../tutorials/trusted-publishing.md:41 msgid "Step 0: Create a release workflow" -msgstr "" +msgstr "Passo 0: Criar um workflow de release" #: ../../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`" -" directory does not exist, you can create it. It is GitHub's convention " -"that all GitHub Actions are configured via YAML files in the " -"`.github/workflows` directory." +"`.github/workflows` directory of your project. If the `.github/workflows` " +"directory does not exist, you can create it. It is GitHub's convention that " +"all GitHub Actions are configured via YAML files in the `.github/workflows` " +"directory." msgstr "" +"Para começar, crie um arquivo chamado `release.yaml` no diretório " +"`.github/workflows` do seu projeto. Se o diretório `.github/workflows` não " +"existir, você pode criá-lo. É convenção do GitHub que todas as GitHub " +"Actions sejam configuradas via arquivos YAML no diretório " +"`.github/workflows`." #: ../../tutorials/trusted-publishing.md:48 msgid "Naming your workflow file" -msgstr "" +msgstr "Nomeando seu arquivo de workflow" #: ../../tutorials/trusted-publishing.md:51 msgid "" @@ -7207,219 +8233,297 @@ msgid "" "self, and contributors who work on your project know exactly what the " "workflow does." msgstr "" +"Você pode dar ao arquivo de workflow o nome que quiser. Sugerimos usar algo " +"simples e expressivo como `release.yaml`, para que você, seu eu futuro e " +"colaboradores que trabalham no seu projeto saibam exatamente o que o " +"workflow faz." #: ../../tutorials/trusted-publishing.md:56 msgid "Step 1: Name the workflow" -msgstr "" +msgstr "Passo 1: Nomear o workflow" #: ../../tutorials/trusted-publishing.md:58 msgid "At the top of the `release.yaml` file, type the following:" -msgstr "" +msgstr "No topo do arquivo `release.yaml`, digite o seguinte:" #: ../../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." +"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 "" +"Isso fornece um nome ao workflow que você pode usar para encontrar " +"rapidamente todas as execuções desta GitHub Action na aba \"Actions\" do " +"repositório GitHub." #: ../../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 " -"GitHub repository. On the left, in the red box labeled \"2\" you can see " -"the name of the workflow, \"Release,\" as configured in this step. " -"Finally, in the center, in the red box labeled \"3\" you can see several " -"runs of the workflow, for the \"1.0\" and \"1.0.1\" releases of the " -"package." +"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 GitHub " +"repository. On the left, in the red box labeled \"2\" you can see the name of " +"the workflow, \"Release,\" as configured in this step. Finally, in the " +"center, in the red box labeled \"3\" you can see several runs of the " +"workflow, for the \"1.0\" and \"1.0.1\" releases of the package." msgstr "" +"Gráfico mostrando um exemplo de workflow configurado para o release. No " +"topo, na caixa vermelha rotulada \"1\", você vê a aba \"Actions\" do " +"repositório GitHub. À esquerda, na caixa vermelha rotulada \"2\", você pode " +"ver o nome do workflow, \"Release\", conforme configurado neste passo. Por " +"fim, no centro, na caixa vermelha rotulada \"3\", você pode ver várias " +"execuções do workflow, para os releases \"1.0\" e\"1.0.1\" do pacote." #: ../../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 " -"GitHub repository. On the left, in the red box labeled \"2\" you can see " -"the name of the workflow, as configured in this step. Finally, in the " -"center, in the red box labeled \"3\" you can see several runs of the " -"workflow, for the \"1.0\" and \"1.0.1\" releases of the package." -msgstr "" +"the top, in the red box labeled \"1\" you see the \"Actions\" tab of the GitHub " +"repository. On the left, in the red box labeled \"2\" you can see the name of " +"the workflow, as configured in this step. Finally, in the center, in the " +"red box labeled \"3\" you can see several runs of the workflow, for the \"1.0\" " +"and \"1.0.1\" releases of the package." +msgstr "" +"Esta imagem mostra um exemplo de workflow configurado para o release. No " +"topo, na caixa vermelha rotulada \"1\", você vê a aba \"Actions\" do " +"repositório GitHub. À esquerda, na caixa vermelha rotulada \"2\", você pode " +"ver o nome do workflow, conforme configurado neste passo. Por fim, no " +"centro, na caixa vermelha rotulada \"3\", você pode ver várias execuções do " +"workflow, para os releases \"1.0\" e \"1.0.1\" do pacote." #: ../../tutorials/trusted-publishing.md:73 msgid "Step 2: Add triggers to the workflow" -msgstr "" +msgstr "Passo 2: Adicionar triggers ao workflow" #: ../../tutorials/trusted-publishing.md:75 msgid "" "Every GitHub Actions workflow runs when [certain " -"conditions](https://docs.github.com/en/actions/reference/events-that-" -"trigger-workflows) are met. In this case, we assume that a release " -"workflow should only run when the repository owner creates a new " -"[release](https://docs.github.com/en/repositories/releasing-projects-on-" -"github/managing-releases-in-a-repository) for the package. Add the " -"following to the `release.yaml` file to ensure it runs when you create " -"and publish a release:" -msgstr "" +"conditions](https://docs.github.com/en/actions/reference/events-that-trigger" +"-workflows)are met. In this case, wem assume that a release workflow should only run " +"when the repository owner creates a new " +"[release](https://docs.github.com/en/repositories/releasing-projects-on-gith" +"ub/managing-releases-in-a-repository)for the package. Add the following to the" +"`release.yaml` file to ensure it runs when you create and publish a release:" +msgstr "" +"Todo workflow do GitHub Actions é executado quando [certas " +"condições](https://docs.github.com/en/actions/reference/events-that-trigger-" +"workflows)são atendidas. Neste caso, assumimos que um workflow de release só " +"deve ser executado quando o proprietário do repositório cria um novo " +"[release](https://docs.github.com/en/repositories/releasing-projects-on-gith" +"ub/managing-releases-in-a-repository)para o pacote. Adicione o seguinte ao " +"arquivo `release.yaml` para garantir que ele seja executado quando você " +"criar e publicar um release:" #: ../../tutorials/trusted-publishing.md:87 msgid "Step 3: Configure the jobs in the workflow" -msgstr "" +msgstr "Passo 3: Configurar os jobs no workflow" #: ../../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, " -"the GitHub Action runs all the jobs in a workflow (excluding any steps " -"that have conditional requirements)." +"independently; each job can also have multiple *steps.* When triggered, the " +"GitHub Action runs all the jobs in a workflow (excluding any steps that " +"have conditional requirements)." msgstr "" +"Um arquivo de *workflow* do GitHub Actions pode conter vários *jobs* que " +"são executados de forma independente; cada job também pode ter vários " +"*steps.* Quando acionado, a GitHub Action executa todos os jobs em um " +"workflow (excluindo quaisquer steps que tenham requisitos condicionais)." #: ../../tutorials/trusted-publishing.md:93 msgid "" "Jobs and steps can also have [conditional " -"logic](https://docs.github.com/en/actions/reference/workflow-syntax-for-" -"github-actions#jobsjob_idif) that allows them only to run if specific " -"criteria exist. For instance, you may want only to have a job step to " -"publish to PyPI if a release was made for the package. But you might want" -" to test building the package every time you merge a new pull request." -msgstr "" +"logic](https://docs.github.com/en/actions/reference/workflow-syntax-for-gith" +"ub-actions#jobsjob_idif)that allows them only to run if specific criteria exist. " +"For instance,you may wantonly to have a job step to publish to PyPI if a " +"release was made for the package. But you might want to test building the " +"package every time you merge a new pull request." +msgstr "" +"Jobs e steps também podem ter [lógica " +"condicional](https://docs.github.com/en/actions/reference/workflow-syntax-fo" +"r-github-actions#jobsjob_idif)que permite que sejam executados apenas se " +"critérios específicos existirem. Por exemplo, você pode querer que um step " +"do job publique no PyPI apenas se um release foi feito para o pacote. Mas " +"você pode querer testar o build do pacote toda vez que fizer merge de um " +"novo pull request." #: ../../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](get-to-know-hatch) to build your package." +"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](get-to-know-hatch) to build your package." msgstr "" +"Para um job de release, você precisa clonar ou fazer checkout do " +"repositório. Você pode usar a action `actions/checkout` para fazer checkout " +"do código. Em seguida, instala e usa o [Hatch](get-to-know-hatch) para " +"fazer o build do seu pacote." #: ../../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." +"You also need to make sure to set up Hatch on the machine GitHub is using " +"to run the workflow." msgstr "" +"Você também precisa garantir que o Hatch esteja configurado na máquina que o " +"GitHub está usando para executar o workflow." #: ../../tutorials/trusted-publishing.md:104 msgid "A minimal job definition would look like this:" -msgstr "" +msgstr "Uma definição mínima de job seria assim:" #: ../../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 " -"action. The checkout action checks out the code from your repository. In " -"this case, the code will be used to build your package." +"`action/checkout@v5` tells GitHub to use version 5 of the checkout action. " +"The checkout action checks out the code from your repository. In this case, " +"the code will be used to build your package." msgstr "" +"Observe que acima você fornece uma versão para cada step de action. " +"`action/checkout@v5` diz ao GitHub para usar a versão 5 da action checkout. " +"A action checkout faz checkout do código do seu repositório. Neste caso, o " +"código será usado para fazer o build do seu pacote." #: ../../tutorials/trusted-publishing.md:126 -msgid "" -"Next, you will learn about a better way to secure (or \"harden\") your " -"workflow" +msgid "Next, you will learn about a better way to secure (or \"harden\") your workflow" msgstr "" +"Em seguida, você aprenderá sobre uma maneira melhor de proteger (ou " +"\"endurecer\") seu workflow" #: ../../tutorials/trusted-publishing.md:128 msgid "Step 4: Secure the GitHub Actions workflow" -msgstr "" +msgstr "Passo 4: Proteger o workflow do GitHub Actions" #: ../../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." +"There are several improvements you can make to the GitHub Actions workflow " +"you just configured to improve security and readability." msgstr "" +"Há várias melhorias que você pode fazer no workflow do GitHub Actions que " +"acabou de configurar para melhorar a segurança e a legibilidade." #: ../../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 " +"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 "" +"Primeiro, podemos dar nomes aos passos relevantes do processo para aumentar " +"a legibilidade dos logs gerados durante a execução do workflow. Isso pode " +"ser feito usando linhas `name: `." #: ../../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" -" if a malicious user takes over the action, they won't be able to impact " -"your repository (an example of a supply chain attack due to GitHub " -"Actions is the recent `tj-actions/changed-files` attack[^changed-files-" -"supply-chain-attack])." -msgstr "" +"should pin that action to a commit hash. Pinning your action ensures that " +"if a malicious user takes over the action, they won't be able to impact " +"your repository (an example of a supply chain attack due to GitHub Actions " +"is the recent `tj-actions/changed-files` attack[^changed-files-supply-chain-attack])." +msgstr "" +"Mais importante, toda vez que você usar uma action existente (via `uses`), " +"deve fixar essa action a um commit hash. Fixar sua action garante que, se " +"um usuário malicioso assumir o controle da action, ele não conseguirá " +"impactar seu repositório (um exemplo de ataque à cadeia de suprimentos " +"devido a GitHub Actions é o recente ataque " +"`tj-actions/changed-files`[^changed-files-supply-chain-attack])." #: ../../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." +"actions stay up to date. The dependabot tool will open pull requests that " +"update your action versions at whatever frequency you want." msgstr "" +"Habilitar o Dependabot[^dependabot] no repositório garantirá que suas " +"actions permaneçam atualizadas. A ferramenta dependabot abrirá pull " +"requests que atualizam as versões das suas actions na frequência que você " +"desejar." #: ../../tutorials/trusted-publishing.md:149 msgid "Thus, the workflow that you should use should be similar to:" -msgstr "" +msgstr "Assim, o workflow que você deve usar deve ser semelhante a:" #: ../../tutorials/trusted-publishing.md:157 msgid "" "Now, you can commit the `.github/workflows/release.yaml` file to the " "repository and push to GitHub." msgstr "" +"Agora, você pode fazer commit do arquivo `.github/workflows/release.yaml` " +"no repositório e fazer push para o GitHub." #: ../../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. " -"Unfortunately, the wheel is only available on the runner and will be " -"deleted at the end of the workflow run." +"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. Unfortunately, " +"the wheel is only available on the runner and will be deleted at the end of " +"the workflow run." msgstr "" +"Neste ponto, se você criar um novo release para seu projeto no GitHub, o " +"workflow configurado deve ser executado e fazer o build de uma wheel para " +"você. Infelizmente, a wheel só está disponível no runner e será excluída ao " +"final da execução do workflow." #: ../../tutorials/trusted-publishing.md:163 msgid "Step 5: Upload the built artifact to GitHub Artifacts" -msgstr "" +msgstr "Passo 5: Fazer upload do artefato build para GitHub Artifacts" #: ../../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:" +"the wheel. You will upload it to the artifacts temporary " +"area[^github-artifacts]. Add the following to the `release.yaml` file:" msgstr "" +"Você precisa adicionar mais um step à definição do job para poder acessar a " +"wheel. Você fará upload dela para a área temporária de " +"artifacts[^github-artifacts]. Adicione o seguinte ao arquivo `release.yaml`:" #: ../../tutorials/trusted-publishing.md:175 msgid "Upload artifacts parameters" -msgstr "" +msgstr "Parâmetros de upload de artifacts" #: ../../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 " +"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 "" +"Acima, você configurou o artifact para ser excluído após 1 dia. O " +"armazenamento de artifacts no GitHub Actions é temporário; os usuários não " +"devem baixar seu pacote dos artifacts do GitHub." #: ../../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 " -"previous step) failed to build our package, so there is nothing to " -"release." +"You have also configured the release job to error if the `dist/` directory " +"does not exist. This means that `hatch build` (from the previous step) " +"failed to build our package, so there is nothing to release." msgstr "" +"Você também configurou o job de release para gerar erro se o " +"diretório`dist/` não existir. Isso significa que `hatch build` (do step " +"anterior) falhou ao fazer o build do nosso pacote, então não há nada para " +"fazer release." #: ../../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 "" +"Neste ponto, se você fizer push do `release.yaml` para o GitHub e criar um " +"novo release, o job do GitHub Actions irá:" #: ../../tutorials/trusted-publishing.md:189 msgid "run," -msgstr "" +msgstr "executar," #: ../../tutorials/trusted-publishing.md:190 msgid "clone your repository," -msgstr "" +msgstr "clonar seu repositório," #: ../../tutorials/trusted-publishing.md:191 msgid "install and set up Hatch," -msgstr "" +msgstr "instalar e configurar o Hatch," #: ../../tutorials/trusted-publishing.md:192 msgid "build your package and" -msgstr "" +msgstr "fazer o build do seu pacote e" #: ../../tutorials/trusted-publishing.md:193 msgid "upload your package as an archive to the artifacts storage." msgstr "" +"fazer upload do seu pacote como um arquivo para o armazenamento de " +"artifacts." #: ../../tutorials/trusted-publishing.md:196 msgid "" @@ -7427,102 +8531,127 @@ msgid "" "running. Each step in the log is matched to one step in the workflow " "definition." msgstr "" +"Gráfico mostrando um exemplo de workflow de release que acabou de terminar " +"de executar. Cada step no log corresponde a um step na definição do " +"workflow." #: ../../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 " +"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 "" +"Esta figura mostra um exemplo de workflow de release que acabou de terminar " +"de executar. Cada step no log corresponde a um step na definição do " +"workflow." #: ../../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:" +"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 "" +"Na parte inferior da página de execução do workflow no GitHub, você deve " +"ver uma seção para os artifacts produzidos durante a execução e enviados " +"para esta área de armazenamento:" #: ../../tutorials/trusted-publishing.md:205 -msgid "" -"Graphic showing an example of an artifact produced by the release " -"workflow." -msgstr "" +msgid "Graphic showing an example of an artifact produced by the release workflow." +msgstr "Gráfico mostrando um exemplo de artifact produzido pelo workflow de release." #: ../../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." +"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 "" +"Esta figura mostra o artifact produzido pelo workflow de release acima. " +"Agora está marcado como expirado, pois o workflow foi executado há mais de " +"um dia." #: ../../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" -" to test the built wheel. Next, you will configure uploading to PyPI " -"using trusted publishing." +"the wheel contained within. However, this should only be done if you want " +"to test the built wheel. Next, you will configure uploading to PyPI using " +"trusted publishing." msgstr "" +"Você pode baixar o artifact (antes que expire), descompactá-lo e instalar a " +"wheel contida nele. No entanto, isso só deve ser feito se você quiser " +"testar a wheel build. Em seguida, você configurará o upload para o PyPI " +"usando trusted publishing." #: ../../tutorials/trusted-publishing.md:215 msgid "Configure automatic publishing to PyPI" -msgstr "" +msgstr "Configurar publicação automática no PyPI" #: ../../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 " -"the package from the same job, but it is better to create a separate one " -"to maintain a separation of tasks. This is why, in the previous section, " -"we uploaded the artifact to the temporary storage." +"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 the package " +"from the same job, but it is better to create a separate one to maintain a " +"separation of tasks. This is why, in the previous section, we uploaded the " +"artifact to the temporary storage." msgstr "" +"O job que você configurou acima usando GitHub Actions faz o build do seu " +"pacote usando seu código. Você ainda precisa fazer upload dele para o PyPI. " +"Você poderia fazer upload do pacote no mesmo job, mas é melhor criar um " +"separado para manter a separação de tarefas. É por isso que, na seção " +"anterior, fizemos upload do artifact para o armazenamento temporário." #: ../../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." +"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 "" +"No novo job, você fará download do pacote de lá e fará upload dele para o " +"PyPI. Como o job `build` não faz mais nada, não há possibilidade de o " +"pacote ser comprometido antes do release." #: ../../tutorials/trusted-publishing.md:227 msgid "Step 1: Add the upload job" -msgstr "" +msgstr "Passo 1: Adicionar o job de upload" #: ../../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 "" +"No arquivo `release.yaml`, adicione o seguinte novo job, após o job " +"definido na seção anterior:" #: ../../tutorials/trusted-publishing.md:238 msgid "Make sure to change the URL" -msgstr "" +msgstr "Certifique-se de alterar a URL" #: ../../tutorials/trusted-publishing.md:240 msgid "Remember to change the `url:` value to the URL for your package on PyPI!" -msgstr "" +msgstr "Lembre-se de alterar o valor `url:` para a URL do seu pacote no PyPI!" #: ../../tutorials/trusted-publishing.md:243 msgid "This job has two steps:" -msgstr "" +msgstr "Este job tem dois steps:" #: ../../tutorials/trusted-publishing.md:245 msgid "" -"It uses `download-artifact` to download the artifacts built in the " -"previous job" -msgstr "" +"It uses `download-artifact` to download the artifacts built in the previous " +"job" +msgstr "Ele usa `download-artifact` para baixar os artifacts build no job anterior" #: ../../tutorials/trusted-publishing.md:247 msgid "It uses `gh-action-pypi-publish` to publish the package to PyPI." -msgstr "" +msgstr "Ele usa `gh-action-pypi-publish` para publicar o pacote no PyPI." #: ../../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!" +"You are almost there!! Now, you just need to enable trusted publishing for " +"your project on PyPI. And then, your work is done!" msgstr "" +"Você está quase lá!! Agora, você só precisa habilitar o trusted publishing " +"para seu projeto no PyPI. E então, seu trabalho está feito!" #: ../../tutorials/trusted-publishing.md:252 msgid "Step 2: Enable trusted publishing on PyPI" -msgstr "" +msgstr "Passo 2: Habilitar trusted publishing no PyPI" #: ../../tutorials/trusted-publishing.md:256 msgid "" @@ -7531,46 +8660,71 @@ msgid "" "Step 3 securely uploads to PyPI. Shows chain of trust with lock icon " "connecting GitHub Action to Python Package Index." msgstr "" +"Diagrama mostrando o workflow de trusted publisher do PyPI: o Passo 1 faz " +"build dos arquivos de distribuição via GitHub, o Passo 2 usa um environment " +"confiável (PyPI), o Passo 3 faz upload seguro para o PyPI. Mostra a cadeia " +"de confiança com ícone de cadeado conectando a GitHub Action ao Python " +"pacote Index." #: ../../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 " -"arguments to the `gh-action-pypi-publish` step. While documentation " -"recommends using the GitHub's `secrets` environment for the " -"password/token, in several cases, users were pasting the password " -"directly into the workflow file. Furthermore, accidental leakage of the " -"password or token could allow attackers to publish new packages using " -"your account, until you discover the compromise and revoke the leaked " -"credentials." -msgstr "" +"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 arguments to the `gh-action-pypi-publish` step. While " +"documentation recommends using the GitHub's `secrets` environment for the " +"password/token, in several cases, users were pasting the password directly " +"into the workflow file. Furthermore, accidental leakage of the password or " +"token could allow attackers to publish new packages using your account, " +"until you discover the compromise and revoke the leaked credentials." +msgstr "" +"Antes da criação do trusted publishing, para fazer upload para o PyPI a " +"partir de GitHub Actions você precisaria adicionar o nome de usuário e a " +"senha como argumentos ao step `gh-action-pypi-publish`. Embora a " +"documentação recomende usar o environment `secrets` do GitHub para a " +"senha/token, em vários casos os usuários colavam a senha diretamente no " +"arquivo de workflow. Além disso, o vazamento acidental da senha ou token " +"poderia permitir que atacantes publicassem novos pacotes usando sua conta, " +"até que você descobrisse o comprometimento e revogasse as credenciais " +"vazadas." #: ../../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/). " -"Trusted publishing allows you to register a publishing workflow on PyPI " -"and then map that workflow to an automation workflow (e.g., GitHub " -"Actions) that is allowed to publish the package." +"Trusted publishing allows you to register a publishing workflow on PyPI and " +"then map that workflow to an automation workflow (e.g., GitHub Actions) " +"that is allowed to publish the package." msgstr "" +"Para prevenir esses incidentes e melhorar a segurança da cadeia de " +"suprimentos, desenvolvedores criaram o [Trusted " +"Publishing](https://docs.pypi.org/trusted-publishers/). O Trusted " +"Publishing permite registrar um workflow de publicação no PyPI e mapear " +"esse workflow a um workflow de automação (por exemplo, GitHub Actions) que " +"tem permissão para publicar o pacote." #: ../../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" +"You do not need to enter a token or password value in a trusted publisher " +"workflow. It's a secure connection between your" msgstr "" +"Você não precisa inserir um valor de token ou senha em um workflow de " +"trusted publisher. É uma conexão segura entre seu" #: ../../tutorials/trusted-publishing.md:277 msgid "Trusted Publishing outside of GitHub Actions" -msgstr "" +msgstr "Trusted Publishing fora do GitHub Actions" #: ../../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 " -"multiple workflows or multiple publishers for the same package. These are" -" advanced uses, out of scope for this lesson." +"Actions. It is also possible to configure a trusted publisher for multiple " +"workflows or multiple publishers for the same package. These are advanced " +"uses, out of scope for this lesson." msgstr "" +"O Trusted Publishing suporta outras plataformas de automação, além do " +"GitHub Actions. Também é possível configurar um trusted publisher " +"para vários workflows ou vários publishers para o mesmo pacote. Esses são " +"usos avançados, fora do escopo desta lição." #: ../../tutorials/trusted-publishing.md:286 msgid "" @@ -7579,6 +8733,9 @@ msgid "" "PyPI publishing](create-python-package), you should have this project " "already created." msgstr "" +"Para esta lição, focaremos em configurar um trusted publisher para um " +"projeto que já existe no PyPI. Se você completou a [lição sobre publicação " +"no PyPI](create-python-package), você já deve ter este projeto criado." #: ../../tutorials/trusted-publishing.md:288 msgid "" @@ -7586,137 +8743,180 @@ msgid "" "releases will only run the GitHub Actions workflow we are configuring in " "`release.yaml`." msgstr "" +"Esta etapa de configuração precisa ser executada apenas uma vez para " +"o projeto. Releases futuros apenas executarão o workflow do GitHub Actions " +"que estamos configurando em `release.yaml`." #: ../../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." +"On the [\"Your projects\" page on PyPI](https://pypi.org/manage/projects/), " +"click \"Manage\" on any project you want to configure." msgstr "" +"Na [página \"Your projects\" no PyPI](https://pypi.org/manage/projects/), " +"clique em \"Manage\" em qualquer projeto que você queira configurar." #: ../../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 "" +"Gráfico mostrando uma captura de tela da página \"Your projects\" no PyPI. O " +"botão \"Manage\" de um dos projetos está destacado." #: ../../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." +"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 "" +"Esta imagem mostra vários projetos. O botão \"Manage\" está destacado para um " +"dos projetos, aquele que queremos configurar o trusted publishing." #: ../../tutorials/trusted-publishing.md:300 msgid "Then click \"Publishing\" in the project's sidebar." -msgstr "" +msgstr "Em seguida, clique em \"Publishing\" na barra lateral do projeto." #: ../../tutorials/trusted-publishing.md:303 msgid "" -"Graphic showing the management page for one project. The \"Publishing\" " -"link in the sidebar is highlighted." +"Graphic showing the management page for one project. The \"Publishing\" link " +"in the sidebar is highlighted." msgstr "" +"Gráfico mostrando a página de gerenciamento de um projeto. O link " +"\"Publishing\" na barra lateral está destacado." #: ../../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." +"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 "" +"Após clicar no botão \"Manage\", chegamos à página do projeto. Na barra " +"lateral, temos a opção \"publishing\", conforme destacado aqui." #: ../../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:" +"Trusted publishers can be configured via the forms here. Filling the GitHub " +"form with the following information:" msgstr "" +"Isso levará você à página de configuração do publisher para o " +"projeto. Trusted publishers podem ser configurados via os formulários aqui. " +"Preencha o formulário do GitHub com as seguintes informações:" #: ../../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 " +"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 "" +"Owner: o nome da organização GitHub da organização que possui o projeto. Se " +"este for seu projeto pessoal, use seu nome de usuário GitHub aqui." #: ../../tutorials/trusted-publishing.md:315 msgid "Repository name: the name of the repository that contains the project." -msgstr "" +msgstr "Repository name: o nome do repositório que contém o projeto." #: ../../tutorials/trusted-publishing.md:316 msgid "" -"Workflow name: Should be `release.yaml` if you followed this guide, it is" -" the workflow we just configured." +"Workflow name: Should be `release.yaml` if you followed this guide, it is " +"the workflow we just configured." msgstr "" +"Workflow name: Deve ser `release.yaml` se você seguiu este guia; é o " +"workflow que acabamos de configurar." #: ../../tutorials/trusted-publishing.md:318 msgid "" "Environment name: Should be `pypi`, as that is what we configured in " "`release.yaml`." msgstr "" +"Environment name: Deve ser `pypi`, pois é o que configuramos em " +"`release.yaml`." #: ../../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." +"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 "" +"Depois de preencher este formulário e clicar em \"Add\", o publisher " +"é configurado e pode ser usado para publicar novos releases do seu pacote." #: ../../tutorials/trusted-publishing.md:324 msgid "Fully hardened GitHub Actions release workflow" -msgstr "" +msgstr "Workflow de release do GitHub Actions totalmente endurecido" #: ../../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 " +"For better security, it is also recommended to control the permissions of " +"the GitHub token used within each job of the workflow. The permissions " "should be scoped at job level and be as minimal as possible. A workflow " "that configures trusted publishing and also does this is the following:" msgstr "" +"Para maior segurança, também é recomendado controlar as permissões do token " +"GitHub usado em cada job do workflow. As permissões devem ser definidas no " +"nível do job e ser o mais mínimas possível. Um workflow que configura " +"trusted publishing e também faz isso é o seguinte:" #: ../../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." +"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 "" +"Você pode copiar o conteúdo acima para seu arquivo `release.yaml`. Você só " +"precisa atualizar o campo `url:` e configurar o trusted publishing no PyPI." #: ../../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." +"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 "" +"O workflow acima deve estar atualizado com as versões atuais das GitHub " +"actions. No entanto, é bom habilitar o Dependabot para atualizar as versões " +"das actions no futuro." #: ../../tutorials/trusted-publishing.md:343 msgid "You have enabled trusted publishing for your project" -msgstr "" +msgstr "Você habilitou o trusted publishing para seu projeto" #: ../../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 " -"have configured builds the package from the exact version of code that we" -" are tagging. This provides a guarantee for your users that the package " -"that you have released does precisely what the code states it does. There" -" is little to no potential for supply chain related vulnerabilities " -"arising from your package! If you have a package that is ready for real-" -"world use on the real PyPI, then you can follow the same steps to publish" -" it securely." -msgstr "" +"releases when a new version is being tagged on GitHub. The workflow we have " +"configured builds the package from the exact version of code that we are " +"tagging. This provides a guarantee for your users that the package that you " +"have released does precisely what the code states it does. There is little " +"to no potential for supply chain related vulnerabilities arising from your " +"package! If you have a package that is ready for real-world use on the real " +"PyPI, then you can follow the same steps to publish it securely." +msgstr "" +"Parabéns!! Você agora configurou seu projeto para fazer releases seguros " +"quando uma nova versão for marcada no GitHub. O workflow que configuramos " +"faz o build do pacote a partir da versão exata do código que estamos " +"marcando. Isso oferece uma garantia para seus usuários de que o pacote que " +"você fez release faz exatamente o que o código declara que faz. Há pouca ou " +"nenhuma possibilidade de vulnerabilidades relacionadas à cadeia de " +"suprimentos surgirem do seu pacote! Se você tem um pacote pronto para uso " +"no mundo real no PyPI real, pode seguiros mesmos passos para publicá-lo com " +"segurança." #: ../../tutorials/trusted-publishing.md:349 msgid "" -msgstr "" +msgstr "" #: ../../tutorials/trusted-publishing.md:350 msgid "" -"" +"" msgstr "" +"" #: ../../tutorials/trusted-publishing.md:351 msgid "" -"" +"" msgstr "" +"" #: ../../tutorials/trusted-publishing.md:352 msgid "" -msgstr "" +msgstr "" From 140e3f216a1134da9da25f67b5d0e32ef5bdfcf9 Mon Sep 17 00:00:00 2001 From: Roberto Date: Tue, 23 Jun 2026 22:10:30 -0700 Subject: [PATCH 5/5] docs: Final review of Portuguese translation for tutorials.po. --- locales/pt/LC_MESSAGES/tutorials.po | 2995 ++++++++++++++------------- 1 file changed, 1529 insertions(+), 1466 deletions(-) diff --git a/locales/pt/LC_MESSAGES/tutorials.po b/locales/pt/LC_MESSAGES/tutorials.po index de7123ba..8f4fa25c 100644 --- a/locales/pt/LC_MESSAGES/tutorials.po +++ b/locales/pt/LC_MESSAGES/tutorials.po @@ -30,16 +30,17 @@ msgstr "Na [lição anterior](add-readme) você:" #: ../../tutorials/add-license-coc.md:10 msgid "" -" Created a " -"basic `README.md` file for your scientific Python package" +" " +"Created a basic `README.md` file for your scientific Python package" msgstr "" " Criou um " "arquivo `README.md` básico para o seu pacote Python científico" #: ../../tutorials/add-license-coc.md:12 msgid "" -" Learned " -"about the core components that are useful to have in a `README` file." +" " +"Learned about the core components that are useful to have in a `README` " +"file." msgstr "" " Aprendeu " "sobre os componentes principais que são úteis ter em um arquivo `README`." @@ -48,7 +49,8 @@ msgstr "" msgid "Learning objectives" msgstr "Objetivos de aprendizagem" -#: ../../tutorials/add-license-coc.md:17 ../../tutorials/add-readme.md:17 ../../tutorials/pyproject-toml.md:30 +#: ../../tutorials/add-license-coc.md:17 ../../tutorials/add-readme.md:17 +#: ../../tutorials/pyproject-toml.md:30 msgid "In this lesson you will learn:" msgstr "Nesta lição você aprenderá:" @@ -66,8 +68,8 @@ msgstr "Como adicionar um arquivo `CODE_OF_CONDUCT` ao repositório do seu pacot #: ../../tutorials/add-license-coc.md:21 msgid "" -"How you can use the Contributors Covenant website to add generic language " -"as a starting place for your `CODE_OF_CONDUCT`." +"How you can use the Contributors Covenant website to add generic language" +" as a starting place for your `CODE_OF_CONDUCT`." msgstr "" "Como você pode usar o site Contributors Covenant para adicionar uma " "linguagem genérica como ponto de partida para o seu `CODE_OF_CONDUCT`." @@ -102,11 +104,11 @@ msgstr "" #: ../../tutorials/add-license-coc.md:31 msgid "" -"By adding this metadata to your [pyproject.toml](pyproject-toml) file,the " -"choice of license will be included in your package's metadatawhich 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." +"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 "" "Ao adicionar esses metadata ao arquivo [pyproject.toml](pyproject-toml), a " "escolha de licença será incluída nos metadata do seu pacote, que são usados " @@ -121,8 +123,8 @@ msgstr "Qual licença você deve usar?" #: ../../tutorials/add-license-coc.md:38 msgid "" "We suggest that you use a permissive license that accommodates the other " -"most commonly used licenses in the scientific Python ecosystem (MIT[^mit] " -"and BSD-3-Clause[^bsd3]). If you are unsure, use MIT given it's the " +"most commonly used licenses in the scientific Python ecosystem (MIT[^mit]" +" and BSD-3-Clause[^bsd3]). If you are unsure, use MIT given it's the " "generally recommended license on " "[choosealicense.com](https://choosealicense.com/)." msgstr "" @@ -151,8 +153,8 @@ msgstr "Onde o arquivo `LICENSE` deve ficar" 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 " -"automagically discover it and provide users with a direct link to " -"your`LICENSE` file within your GitHub repository." +"automagically discover it and provide users with a direct link to your " +"`LICENSE` file within your GitHub repository." msgstr "" "Seu arquivo `LICENSE` deve ficar na raiz do repositório do seu " "pacote. Quando você adiciona o `LICENSE` na raiz, o GitHub o " @@ -160,18 +162,20 @@ msgstr "" "arquivo `LICENSE` dentro do repositório no GitHub." #: ../../tutorials/add-license-coc.md:53 -msgid "Image showing the GitHub repository for SunPy an accepted pyOpenSci package." +msgid "" +"Image showing the GitHub repository for SunPy an accepted pyOpenSci " +"package." msgstr "" "Imagem mostrando o repositório no GitHub do SunPy, um pacote " "pyOpenSciaceito." #: ../../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, the " -"`CODE_OF_CONDUCT` file and one that specifies the licensethat SunPy uses. " -"These files are discovered by GitHub because they areplaced in the root of " -"the project directory using standard naming conventions." +"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, " +"the `CODE_OF_CONDUCT` file and one that specifies the license that SunPy " +"uses. These files are discovered by GitHub because they are placed in the" +" root of the project directory using standard naming conventions." msgstr "" "Observe que na parte superior da seção README da página inicial do GitHub, " "há três abas com links diretos para o arquivo `README`, que está visível, o " @@ -189,9 +193,9 @@ msgstr "Há várias maneiras de adicionar um arquivo `LICENSE`:" #: ../../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 the " -"file for you." +"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 " +"the file for you." msgstr "" "Quando você cria um novo repositório no GitHub, ele perguntará se deseja " "adicionar um arquivo `LICENSE` naquele momento. Se você selecionar sim, ele " @@ -199,10 +203,10 @@ msgstr "" #: ../../tutorials/add-license-coc.md:67 msgid "" -"You can add a `LICENSE` through the GitHub gui following the [ instructions " -"here](https://docs.github.com/en/communities/setting-up-your-project-for-hea" -"lthy-contributions/adding-a-license-to-a-repository)." +"You can add a `LICENSE` through the GitHub gui following the [ instructions " +"here](https://docs.github.com/en/communities/setting-up-your-project-for-" +"healthy-contributions/adding-a-license-to-a-repository)." msgstr "" "Você pode adicionar um `LICENSE` pela GUI do GitHub seguindo as [ instruções " @@ -227,9 +231,9 @@ msgstr "[publicar seu pacote no PyPI](publish-pypi.md)" #: ../../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 this " -"tutorial which walks you through adding a `CODE_OF_CONDUCT`." +"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 " +"this tutorial which walks you through adding a `CODE_OF_CONDUCT`." msgstr "" "então você já tem um arquivo `LICENSE` contendo o texto da licença MIT no " "seu pacote Python. Assim, você pode pular para a próxima seção deste " @@ -249,7 +253,8 @@ msgstr "Como adicionar um `LICENSE` ao seu pacote — a maneira manual" #: ../../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 by" +"platform such as GitHub or GitLab, then you can create a `LICENSE` file " +"by" msgstr "" "Se você ainda não tem um arquivo `LICENSE` e ainda não usa uma plataforma " "como GitHub ou GitLab, pode criar um arquivo `LICENSE`" @@ -292,11 +297,11 @@ msgstr "Uma visão geral das licenças no ecossistema Python científico" #: ../../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 Python ecosystem. Wereview why " -"license files are important, which ones are most commonlyused for " -"scientific software and how to select the correct license." +"In the pyOpenSci [packaging guidebook](../documentation/repository-files" +"/license-files), we provide an overview of licenses in the scientific " +"Python ecosystem. We review why license files are important, which ones " +"are most commonly used for scientific software and how to select the " +"correct license." msgstr "" "No [guia de empacotamento](../documentation/repository-files/license-files) " "do pyOpenSci, fornecemos uma visão geral das licenças no ecossistema Python " @@ -306,11 +311,10 @@ msgstr "" #: ../../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 " -"side of " -"things.](https://opensource.guide/legal/#just-give-me-the-tldr-on-what-i-nee" -"d-to-protect-my-project)" +"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" +" side of things.](https://opensource.guide/legal/#just-give-me-the-tldr-" +"on-what-i-need-to-protect-my-project)" msgstr "" "Se quiser uma visão geral ampla de por que as licenças são importantes para " "proteger software de código aberto, [confira esta postagem de blog que " @@ -336,13 +340,13 @@ msgstr "" #: ../../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. Below " -"that you can add a description of the repository. Below that you can set it " -"to be public or private. At the bottom of the interface there is an Add a " -"README checkbox where it will add a blank readme file for you. At the very " -"bottom there is a line to add a.gitignore file and another to choose a " -"license." +"Screenshot of the create new repository interface that GitHub provides. " +"The elements of this are the owner and repository name for the new repo. " +"Below that you can add a description of the repository. Below that you " +"can set it to be public or private. At the bottom of the interface there " +"is an Add a README checkbox where it will add a blank readme file for " +"you. At the very bottom there is a line to add a .gitignore file and " +"another to choose a license." msgstr "" "Captura de tela da interface de criação de novo repositório do GitHub. Os " "elementos são o proprietário e o nome do repositório para o novo repo. " @@ -354,8 +358,8 @@ msgstr "" #: ../../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." +"Image showing the GitHub interface that allows you to add a `LICENSE` and" +" `README` file when you create a new repository." msgstr "" "Imagem mostrando a interface do GitHub que permite adicionar um arquivo " "`LICENSE` e um `README` ao criar um novo repositório." @@ -366,8 +370,9 @@ msgstr "Adicionar `LICENSE`: repositório GitHub existente" #: ../../tutorials/add-license-coc.md:127 msgid "" -"If you already have a GitHub repository for your package, then you canadd a " -"`LICENSE` using the GitHub interface by adding a new file to therepository." +"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 " +"repository." msgstr "" "Se você já tem um repositório no GitHub para o seu pacote, pode adicionar " "um `LICENSE` pela interface do GitHub, criando um novo arquivo no " @@ -375,10 +380,10 @@ msgstr "" #: ../../tutorials/add-license-coc.md:129 msgid "" -"Follow the instructions to select and add a license to your repositoryon " -"the [GitHub LICENSE " -"page](https://docs.github.com/en/communities/setting-up-your-project-for-hea" -"lthy-contributions/adding-a-license-to-a-repository)." +"Follow the instructions to select and add a license to your repository on" +" the [GitHub LICENSE page](https://docs.github.com/en/communities" +"/setting-up-your-project-for-healthy-contributions/adding-a-license-" +"to-a-repository) ." msgstr "" "Siga as instruções para selecionar e adicionar uma licença ao seu " "repositório na [página LICENSE do " @@ -388,8 +393,8 @@ msgstr "" #: ../../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 pull` " -"to update your local branch." +"repository with the repository on GitHub.com. This means running `git " +"pull` to update your local branch." msgstr "" "Depois de adicionar o arquivo `LICENSE`, sincronize o repositório git local " "com o repositório em GitHub.com. Isso significa executar `git pull` para " @@ -397,12 +402,12 @@ msgstr "" #: ../../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 3-clause " -"New or revised license. Then there is some text describing both what the " -"license is and the associated permissions forthat specific license. At the " -"bottom of the image, the actual text forthe license is shown in the LICENSE " -"file." +"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 " +"3-clause New or revised license. Then there is some text describing both " +"what the license is and the associated permissions for that specific " +"license. At the bottom of the image, the actual text for the license is " +"shown in the LICENSE file." msgstr "" "Imagem mostrando como o arquivo LICENSE aparece na interface do GitHub. No " "topo, você vê a licença em si — nesta imagem, BSD 3-clause New or revised " @@ -464,8 +469,8 @@ msgstr "Identifica comportamentos negativos que você não quer nas interações #: ../../tutorials/add-license-coc.md:158 msgid "" -"You can use your code of conduct as a tool that can be referenced " -"whenmoderating challenging conversations." +"You can use your code of conduct as a tool that can be referenced when " +"moderating challenging conversations." msgstr "" "Você pode usar seu código de conduta como ferramenta de referência ao " "moderar conversas difíceis." @@ -476,10 +481,10 @@ msgstr "O que incluir no seu arquivo `CODE_OF_CONDUCT`" #: ../../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 " -"language](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)" -"asastartingplace." +"If you are unsure of what language to add to your `CODE_OF_CONDUCT` file," +" we suggest that you adopt the [contributor covenant " +"language](https://www.contributor-" +"covenant.org/version/2/1/code_of_conduct/) as a starting place." msgstr "" "Se não souber que linguagem adicionar ao arquivo `CODE_OF_CONDUCT`, " "sugerimos adotar a [linguagem do Contributors " @@ -489,8 +494,7 @@ msgstr "" #: ../../tutorials/add-license-coc.md:165 msgid "" "![Contributor " -"Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" -")" +"Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)" msgstr "" "![Contributor " "Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg" @@ -522,13 +526,13 @@ msgstr "" #: ../../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 " -"conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/co" -"de_of_conduct.md)toyour`CODE_OF_CONDUCT.md`file.Besuretofillin any " -"placeholder information. Read the text closely to ensure you both " -"understand it and also agree with its contents!" +"Visit the [contributor covenant website](https://www.contributor-" +"covenant.org/) and add [the markdown version of their code of " +"conduct](https://www.contributor-" +"covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) to your " +"`CODE_OF_CONDUCT.md` file. Be sure to fill in any placeholder " +"information. Read the text closely to ensure you both understand it and " +"also agree with its contents!" msgstr "" "Visite o [site do Contributors " "Covenant](https://www.contributor-covenant.org/) e adicione [a versão em " @@ -549,8 +553,8 @@ msgstr "Recursos adicionais sobre código de conduta" #: ../../tutorials/add-license-coc.md:184 msgid "" "[ Guide: `CODE_OF_CONDUCT.md` " -"files](https://docs.github.com/en/communities/setting-up-your-project-for-he" -"althy-contributions/adding-a-code-of-conduct-to-your-project)" +"files](https://docs.github.com/en/communities/setting-up-your-project-" +"for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" msgstr "" "[ Guia: arquivos " "`CODE_OF_CONDUCT.md`](https://docs.github.com/en/communities/setting-up-your" @@ -559,14 +563,16 @@ msgstr "" #: ../../tutorials/add-license-coc.md:185 msgid "" "[pyOpenSci package guide `CODE_OF_CONDUCT.md` " -"overview](https://www.pyopensci.org/python-package-guide/documentation/repos" -"itory-files/code-of-conduct-file.html)" +"overview](https://www.pyopensci.org/python-package-guide/documentation" +"/repository-files/code-of-conduct-file.html)" msgstr "" "[Visão geral do `CODE_OF_CONDUCT.md` no guia de pacotes do " "pyOpenSci](https://www.pyopensci.org/python-package-guide/documentation/repo" "sitory-files/code-of-conduct-file.html)" -#: ../../tutorials/add-license-coc.md:188 ../../tutorials/add-readme.md:240 ../../tutorials/publish-conda-forge.md:475 ../../tutorials/pyproject-toml.md:699 +#: ../../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 " Encerramento" @@ -588,15 +594,16 @@ msgstr "arquivo `CODE_OF_CONDUCT`." #: ../../tutorials/add-license-coc.md:196 msgid "" -"These are fundamental files needed for every scientific Python " -"packagerepository. These files help users understand how to use your " -"package and interact with package maintainers." +"These are fundamental files needed for every scientific Python package " +"repository. These files help users understand how to use your package and" +" interact with package maintainers." msgstr "" "Esses são arquivos fundamentais para todo repositório de pacote " "Python científico. Eles ajudam os usuários a entender como usar seu pacote e " "interagir com os mantenedores(as) do pacote." -#: ../../tutorials/add-license-coc.md:200 ../../tutorials/create-python-package.md:455 +#: ../../tutorials/add-license-coc.md:200 +#: ../../tutorials/create-python-package.md:455 msgid "In the upcoming lessons, you will:" msgstr "Nas próximas lições, você irá:" @@ -616,7 +623,10 @@ msgstr "" "Publicar uma nova versão do seu pacote Python no test PyPI para visualizar " "a página de metadata atualizada." -#: ../../tutorials/add-license-coc.md:208 ../../tutorials/create-python-package.md:550 ../../tutorials/publish-conda-forge.md:487 ../../tutorials/publish-pypi.md:419 +#: ../../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 "Notas de rodapé" @@ -671,8 +681,8 @@ msgstr "O que é um arquivo README?" #: ../../tutorials/add-readme.md:25 #, python-brace-format msgid "" -"The `README.md` file is the project's {term}`README` and is located atthe " -"root of your project directory. It 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 "" "O arquivo `README.md` é o {term}`README` do projeto e fica na raiz do " "diretório do projeto. Ele ajuda o usuário a entender:" @@ -683,8 +693,9 @@ msgstr "O nome do seu pacote" #: ../../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 audience." +"What the package does. Your README file should clearly state the " +"problem(s) that your software is designed to solve and its target " +"audience." msgstr "" "O que o pacote faz. Seu README deve deixar claro o(s) problema(s) que seu " "software resolve e o público-alvo." @@ -708,8 +719,8 @@ msgstr "Como citar seu pacote" #: ../../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 isalso used " -"to populate your PyPI landing page." +"someone sees before they install your package. The README file is also " +"used to populate your PyPI landing page." msgstr "" "Seu arquivo **README.md** é importante, pois costuma ser a primeira coisa " "que alguém vê antes de instalar seu pacote. O README também é usado para " @@ -717,9 +728,9 @@ msgstr "" #: ../../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 include in " -"your README file." +"Note that there is no specific content structure for README files. " +"However, this tutorial outlines the sections that we suggest that you " +"include in your README file." msgstr "" "Note que não há uma estrutura de conteúdo específica para arquivos README. " "No entanto, este tutorial descreve as seções que sugerimos incluir no seu " @@ -739,8 +750,8 @@ msgstr "Passo 0: Crie um arquivo README" #: ../../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." +"To get started, if you don't already have a README.md file in your " +"project directory, create one." msgstr "" "Para começar, se ainda não tiver um arquivo README.md no diretório do " "projeto, crie um." @@ -771,8 +782,8 @@ msgstr "No topo do arquivo `README.md`, adicione o nome do seu pacote." #: ../../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." +"If you are using markdown it should be a header 1 (H1) tag which is " +"denoted with a single `#` sign." msgstr "" "Se estiver usando markdown, deve ser um título H1 (header 1), indicado com " "um único `#`." @@ -787,8 +798,8 @@ msgstr "Passo 2: adicione badges ao topo do seu arquivo README" #: ../../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:" +"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:" msgstr "" "É comum os mantenedores adicionarem badges ao topo dos arquivos README. Os " "badges permitem que você e os pessoas usuárias do pacote acompanhem coisas " @@ -804,8 +815,8 @@ msgstr "Versões do seu pacote no PyPI e no conda." #: ../../tutorials/add-readme.md:75 msgid "" -"Whether your package has been reviewed and vetted by an organization such " -"as pyOpenSci and/or JOSS." +"Whether your package has been reviewed and vetted by an organization such" +" as pyOpenSci and/or JOSS." msgstr "" "Se o seu pacote foi revisado e validado por uma organização como pyOpenSci " "e/ou JOSS." @@ -813,9 +824,9 @@ msgstr "" #: ../../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/py-pi-version). This badge will " -"dynamically update as you release new versions of your package to PyPI." +"[shields.io to create a package version badge](https://shields.io/badges" +"/py-pi-version). This badge will dynamically update as you release new " +"versions of your package to PyPI." msgstr "" "Se você já publicou seu pacote em pypi.org, pode usar [shields.io para criar " "um badge de versão do pacote](https://shields.io/badges/py-pi-version). " @@ -824,8 +835,8 @@ msgstr "" #: ../../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." +"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 "" "Caso contrário, pode deixar o topo vazio por enquanto e adicionar badges ao " "README mais tarde, quando fizer sentido." @@ -836,8 +847,8 @@ msgstr "Passo 3: Adicione uma descrição do que seu pacote faz" #: ../../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." +"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 "" "Abaixo dos badges (se houver), adicione um trecho de texto com uma visão " "geral fácil de entender do que seu pacote faz." @@ -852,16 +863,16 @@ msgstr "Tente evitar jargão." #: ../../tutorials/add-readme.md:89 msgid "" -"Define technical terms that you use to make the description accessibleto " -"more people." +"Define technical terms that you use to make the description accessible to" +" more people." msgstr "" "Defina termos técnicos que usar para tornar a descrição acessível a mais " "pessoas." #: ../../tutorials/add-readme.md:91 msgid "" -"Remember that the more people understand what your package does, the more " -"people will use it." +"Remember that the more people understand what your package does, the more" +" people will use it." msgstr "" "Lembre-se: quanto mais pessoas entenderem o que seu pacote faz, mais " "pessoas o usarão." @@ -879,8 +890,8 @@ msgstr "" #: ../../tutorials/add-readme.md:97 #, python-brace-format msgid "" -"For example, can they use {term}`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 "" "Por exemplo, dá para instalar o pacote com {term}`pip`? `python -m " "pip install packagename`" @@ -907,9 +918,9 @@ msgstr "Passo 5: Configuração adicional" #: ../../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 section " -"on additional setup to your README file." +"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" +" section on additional setup to your README file." msgstr "" "Em alguns casos, os usuários do pacote podem precisar " "instalar manualmente outras ferramentas para usá-lo. Nesse caso, adicione " @@ -917,8 +928,8 @@ msgstr "" #: ../../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:" +"Here, briefly document (or link to documentation for) any additional " +"setup that is required to use your package. This might include:" msgstr "" "Aqui, documente brevemente (ou inclua um link para documentação " "sobre) qualquer configuração adicional necessária para usar seu " @@ -947,8 +958,8 @@ msgstr "Passo 6: Adicione uma seção de primeiros passos" #: ../../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 in " -"your package." +"example that demonstrates importing and using some of the functionality " +"in your package." msgstr "" "Em seguida, adicione uma seção de primeiros passos. Nela, inclua um pequeno " "exemplo de código que demonstre o import e o uso de alguma funcionalidade " @@ -960,24 +971,24 @@ msgstr "Forneça um trecho de código totalmente funcional, se possível" #: ../../tutorials/add-readme.md:136 msgid "" -"It is important to try to make the code examples that you provide yourusers " -"as useful as possible." +"It is important to try to make the code examples that you provide your " +"users as useful as possible." msgstr "" "É importante tentar tornar os exemplos de código que você fornece aos " "usuários o mais úteis possível." #: ../../tutorials/add-readme.md:138 msgid "" -"Be sure to provide a copy/paste code example that will work as-is " -"whenpasted into a Jupyter Notebook or .py file if that is possible." +"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 "" "Forneça um exemplo de código para copiar/colar que funcione como está " "quando colado em um Jupyter Notebook ou arquivo .py, se isso for possível." #: ../../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." +"If there are tokens and other steps needed to run your package, be sure " +"to be clear about what those steps are." msgstr "" "Se forem necessários tokens e outras etapas para executar seu pacote, deixe " "claras quais são." @@ -999,8 +1010,8 @@ msgstr "" #: ../../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." +"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 "" "Este também seria um ótimo lugar para adicionar links para tutoriais que " "ajudem os usuários a entender como usar seu pacote em workflows comuns." @@ -1011,9 +1022,9 @@ msgstr "Passo 7: Seção de comunidade" #: ../../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 engagement will " -"likely happen on a platform like GitHub or GitLab." +"The community section of your README file is a place to include " +"information for users who may want to engage with your project. This " +"engagement will likely happen on a platform like GitHub or GitLab." msgstr "" "A seção de comunidade do README é o lugar para incluir informações para " "usuários que queiram se envolver com o projeto. Esse engajamento " @@ -1021,9 +1032,9 @@ msgstr "" #: ../../tutorials/add-readme.md:163 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 filein the [next " -"lesson](add-license-coc)." +"In the community section, you will add links to your contributing guide " +"and `CODE_OF_CONDUCT.md`. You will create a code of conduct file in the " +"[next lesson](add-license-coc)." msgstr "" "Na seção de comunidade, você adicionará links para o guia de contribuição e " "para o `CODE_OF_CONDUCT.md`. Você criará um arquivo de código de conduta na " @@ -1031,9 +1042,9 @@ msgstr "" #: ../../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:" +"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 "" "Conforme seu pacote cresce, você também pode ter um link para um guia de " "desenvolvimento que contribuidores e a equipe de mantenedores seguirão. O " @@ -1061,17 +1072,17 @@ msgstr "Passo 8: Informações de citação" #: ../../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." +"Finally it is important to let users know how to cite your package. You " +"can communicate citation information in a few different ways." msgstr "" "Por fim, é importante informar aos usuários como citar seu pacote. Você " "pode comunicar informações de citação de algumas formas diferentes." #: ../../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 GitHub. " -"[Check out this short tutorial that covers setting that " +"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 " +"GitHub. [Check out this short tutorial that covers setting that " "up.](https://coderefinery.github.io/github-without-command-line/doi/)" msgstr "" "Você pode usar uma ferramenta como o zenodo para criar um DOI e informações " @@ -1082,13 +1093,12 @@ msgstr "" #: ../../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-review/index.html). After " -"being accepted by pyOpenSci, if your package is in scope, you can be " -"accepted by the Journal of Open Source Software and get a cross-ref DOI " -"through [our partnership with the Journal of Open " -"SourceSoftware.](https://www.pyopensci.org/about-peer-review/index.html)" +"Alternatively if you send your package through a peer review process such" +" as the [one lead by pyOpenSci](https://www.pyopensci.org/about-peer-" +"review/index.html). After being accepted by pyOpenSci, if your package is" +" in scope, you can be accepted by the Journal of Open Source Software and" +" get a cross-ref DOI through [our partnership with the Journal of Open " +"Source Software.](https://www.pyopensci.org/about-peer-review/index.html)" msgstr "" "Alternativamente, se você submeter seu pacote a um processo de revisão por " "pares, como [o liderado pelo " @@ -1108,11 +1118,12 @@ msgstr "Seu arquivo `README.md` finalizado deve ficar parecido com isto:" #: ../../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 perfect " -"template, above is a set of recommendations as youare just getting started. " -"You may find the need for other elements to be added to this file as you " -"further develop your package and as a community begins to use your package." +"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 " +"perfect template, above is a set of recommendations as you are just " +"getting started. You may find the need for other elements to be added to " +"this file as you further develop your package and as a community begins " +"to use your package." msgstr "" "É importante considerar as informações que um novo usuário ou contribuidor " "pode precisar ao criar seu arquivo `README.md`. Embora não exista um " @@ -1123,8 +1134,8 @@ msgstr "" #: ../../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 they " -"legally can (and can't) use your package. It also:" +"your Python package. A license file is critical as it tells users how " +"they legally can (and can't) use your package. It also:" msgstr "" "Na [próxima lição](add-license-coc.md), você adicionará um arquivo LICENSE " "ao seu pacote Python. Um arquivo de licença é fundamental, pois informa aos " @@ -1144,11 +1155,11 @@ msgstr "Guia de referência da linha de comando" #: ../../tutorials/command-line-reference.md:9 msgid "" -"**What these tables are:** These tables summarize the command line inputs " -"(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." +"**What these tables are:** These tables summarize the command line inputs" +" (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 "" "**O que são estas tabelas:** Estas tabelas resumem as entradas de linha de " "comando (por exemplo, `pipx install hatch`, `hatch build` ou `python -m " @@ -1159,8 +1170,8 @@ msgstr "" #: ../../tutorials/command-line-reference.md:14 #, python-brace-format msgid "" -"**What these tables are not:** These tables do not cover the manual " -"ornon-automated steps (e.g., create a PyPI account, create a {term}`API " +"**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 "" "**O que estas tabelas não são:** Estas tabelas não cobrem as etapas manuais " @@ -1171,10 +1182,10 @@ msgstr "" #: ../../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-specific commands are indicated with parentheses after the description " -"of the command, e.g., [COMMAND_DESCRIPTION] (Windows). Corresponding " -"commands for macOS and Linux will be added inthe future." +"tested on the Windows OS only. Many commands are Windows-specific. OS-" +"specific commands are indicated with parentheses after the description of" +" the command, e.g., [COMMAND_DESCRIPTION] (Windows). Corresponding " +"commands for macOS and Linux will be added in the future." msgstr "" "**Nota sobre sistema operacional:** A versão atual deste guia foi testada " "apenas no Windows. Muitos comandos são específicos do Windows. Comandos " @@ -1202,17 +1213,16 @@ msgstr "Versões e ambientes" msgid "Create a pure Python package" msgstr "Crie um pacote Python puro" -#: ../../tutorials/create-python-package.md:9 ../../tutorials/develop-python-package-hatch.md:9 +#: ../../tutorials/create-python-package.md:9 +#: ../../tutorials/develop-python-package-hatch.md:9 msgid "About this lesson" msgstr "Sobre esta lição" - - -##: ../../tutorials/create-python-package.md:13 +#: ../../tutorials/create-python-package.md:13 #, python-brace-format msgid "" -"This lesson uses the pyOpenSci Python package copier template to create a " -"{term}`Python package` quickly. Your package will be installable both " +"This lesson uses the pyOpenSci Python package copier template to create a" +" {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 "" @@ -1221,22 +1231,23 @@ msgstr "" "instalável localmente e remotamente a partir de um site como GitHub (ou " "GitLab) em um ambiente Python." -#: ../../tutorials/create-python-package.md:18 ../../tutorials/setup-py-to-pyproject-toml.md:23 +#: ../../tutorials/create-python-package.md:18 +#: ../../tutorials/setup-py-to-pyproject-toml.md:23 msgid "In this lesson, you will learn:" msgstr "Nesta lição, você aprenderá:" #: ../../tutorials/create-python-package.md:20 msgid "" -"How to make your code installable into any Python environment, both locally " -"and from GitHub" +"How to make your code installable into any Python environment, both " +"locally and from GitHub" msgstr "" "Como tornar seu código instalável em qualquer ambiente Python, localmente e " "a partir do GitHub" #: ../../tutorials/create-python-package.md:21 msgid "" -"How to update a [pyproject.toml file](pyproject-toml), 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 "" "Como atualizar um [arquivo pyproject.toml](pyproject-toml), que contém os " "metadata necessários para fazer build, instalar e publicar seu pacote." @@ -1244,8 +1255,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:23 #, python-brace-format msgid "" -"How to declare a {term}`Build backend` 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 "" "Como declarar um {term}`backend de construção ` que será " "usado para fazer [build](build-package) e instalar seu pacote" @@ -1260,10 +1271,10 @@ msgstr "**O que você precisa para concluir esta lição**" #: ../../tutorials/create-python-package.md:30 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](get-to-know-hatch) to complete the lesson successfully." +"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" +"](get-to-know-hatch) to complete the lesson successfully." msgstr "" "Para concluir esta lição, você precisará de um ambiente Python local e de um " "shell no seu computador. Será necessário ter o " @@ -1273,9 +1284,10 @@ msgstr "" #: ../../tutorials/create-python-package.md:35 msgid "" "If you are using Windows or are not familiar with Shell, you may want to " -"check out the Carpentries shell lesson[^shell-lesson]. Windows users will " -"likely need to configure a tool such as " -"[gitbash](https://gitforwindows.org/) for any Shell and git-related steps." +"check out the Carpentries shell lesson[^shell-lesson]. Windows users will" +" likely need to configure a tool such as " +"[gitbash](https://gitforwindows.org/) for any Shell and git-related " +"steps." msgstr "" "Se você usa Windows ou não está familiarizado com Shell, pode querer " "conferir a lição de shell da Carpentries[^shell-lesson]. Usuários de " @@ -1285,11 +1297,11 @@ msgstr "" #: ../../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 " -"package. The environment box on the right reads - your Python environment. " -"It them lists your-package along with a few other core packages such as " -"Matplotlib, NumPy, Pandas, Xarray and GeoPandas." +"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 " +"package. The environment box on the right reads - your Python " +"environment. It them lists your-package along with a few other core " +"packages such as Matplotlib, NumPy, Pandas, Xarray and GeoPandas." msgstr "" "Este diagrama tem duas caixas menores com setas apontando para a direita em " "direção a um ambiente Python. As caixas pequenas mostram seu-pacote e pip " @@ -1300,12 +1312,12 @@ msgstr "" #: ../../tutorials/create-python-package.md:43 msgid "" "In a [previous lesson, you learned what a Python package is](intro). " -"Creating a Python package allows you to install your code into any Python " -"environment on your computer. You can then import it into workflows in the " -"same way that you might import a package such as Pandas or GeoPandas. If " -"you push your code to GitHub or GitLab, you can also install it directly " -"from there. [Scroll to the bottom of the page to learn more about the basic " -"elements of a Python package.](package-overview)." +"Creating a Python package allows you to install your code into any Python" +" environment on your computer. You can then import it into workflows in " +"the same way that you might import a package such as Pandas or GeoPandas." +" If you push your code to GitHub or GitLab, you can also install it " +"directly from there. [Scroll to the bottom of the page to learn more " +"about the basic elements of a Python package.](package-overview)." msgstr "" "Em uma [lição anterior, você aprendeu o que é um pacote Python](intro). " "Criar um pacote Python permite instalar seu código em qualquer ambiente " @@ -1322,10 +1334,11 @@ msgstr "Crie seu pacote Python" #: ../../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 template " -"uses Hatch as the default packaging tool. At the bottom of this lesson, " -"you'll learn more about the basics of the Python package directory " -"structure, and associated key files (`__init__.py` and `pyproject.toml`)." +"template](https://github.com/pyOpenSci/pyos-package-template). Our " +"template uses Hatch as the default packaging tool. At the bottom of this " +"lesson, you'll learn more about the basics of the Python package " +"directory structure, and associated key files (`__init__.py` and " +"`pyproject.toml`)." msgstr "" "Abaixo, você criará um pacote Python puro usando o [template copier " "dopyOpenSci](https://github.com/pyOpenSci/pyos-package-template). Nosso " @@ -1344,9 +1357,9 @@ msgstr "Abra seu shell ou terminal preferido." #: ../../tutorials/create-python-package.md:56 msgid "" -"Use the shell `cd` command to navigate in your shell to the location where " -"you'd like your package to live. Our template will create the package " -"directory structure for you" +"Use the shell `cd` command to navigate in your shell to the location " +"where you'd like your package to live. Our template will create the " +"package directory structure for you" msgstr "" "Use o comando `cd` do shell para navegar até o local onde você quer que seu " "pacote fique. Nosso template criará a estrutura de diretórios do pacote para " @@ -1370,8 +1383,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:60 msgid "" -"Only use letters and the characters _ or - in the name. This means that the " -"name `pyos*package` is not an acceptable name. However, the names " +"Only use letters and the characters _ or - in the name. This means that " +"the name `pyos*package` is not an acceptable name. However, the names " "`pyos_package` or `pyos-package` are both OK." msgstr "" "Use apenas letras e os caracteres _ ou - no nome. Isso significa que o nome " @@ -1381,8 +1394,8 @@ msgstr "" #: ../../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." +"prompts that will ask you questions and help you to customize your Python" +" package." msgstr "" "No seu terminal, **execute o comando abaixo**. Isso iniciará uma série de " "prompts que farão perguntas e ajudarão você a personalizar seu pacote Python." @@ -1399,9 +1412,9 @@ msgstr "" 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 " -"Yes, but with a minimal setup to create the most basic version " -"of your package that contains documentation, tests and a example module for " -"you to use." +"Yes, but with a minimal setup to create the most basic version" +" of your package that contains documentation, tests and a example module " +"for you to use." msgstr "" "Observe que, quando chegar ao prompt \"Do you want to answer one more " "question, and skip the rest, using the default values?\", você pode escolher " @@ -1436,12 +1449,12 @@ msgstr "Um pacote completo com testes, docs e infraestrutura do GitHub" #: ../../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 Hatch. If you " -"customize the entire package, then you canselect what platform you wish to " -"host it on (GitHub vs GitLab), whether you want typing, what documentation " -"engine you want to use, and more." +"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 "" "Se você usar a opção padrão \"bells and whistles\" ao responder aos prompts " "do template, nosso template criará uma configuração completa do pacote com " @@ -1460,9 +1473,9 @@ msgstr "As ferramentas padrão que seu pacote usa são:" #: ../../tutorials/create-python-package.md:148 msgid "" -"[Sphinx](https://www.pyopensci.org/python-package-guide/documentation/hostin" -"g-tools/sphinx-python-package-documentation-tools.html)withthePyDataSphinxTh" -"emefordocumentation" +"[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 "" "[Sphinx](https://www.pyopensci.org/python-package-guide/documentation/hostin" "g-tools/sphinx-python-package-documentation-tools.html) com o PyData Sphinx " @@ -1479,8 +1492,8 @@ msgstr "Hatch para configuração de ambiente" #: ../../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:" +"package setup, choose `No, I want to fully customize the template.`. " +"This will allow you to select:" msgstr "" "**Personalização completa** Se você quiser personalizar qualquer elemento " "da configuração do seu pacote, escolha `No, I want to fully customize the " @@ -1509,10 +1522,10 @@ msgstr "Passo 2: Explore o módulo existente no seu pacote" #: ../../tutorials/create-python-package.md:163 #, python-brace-format msgid "" -"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 testout 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 "" "Um {term}`módulo ` refere-se a um arquivo `.py` contendo o código " "que você quer que seu pacote acesse e execute. No subdiretório " @@ -1533,15 +1546,16 @@ msgstr "Ele usa [typing](type-hints)" #: ../../tutorials/create-python-package.md:171 msgid "" -"At the top of the module, there is a docstring explaining what the module " -"does." -msgstr "No topo do module, há uma docstring explicando o que o module faz." +"At the top of the module, there is a docstring explaining what the module" +" does." +msgstr "" #: ../../tutorials/create-python-package.md:173 msgid "" -"Python supports different docstring formats. The most popular formats for " -"documenting Python objects are NumPy Style Docstring[^numpydoc], Google " -"Style Docstring[^googledoc], and the Epytext Style Docstrings[^epytextdoc]." +"Python supports different docstring formats. The most popular formats for" +" documenting Python objects are NumPy Style Docstring[^numpydoc], Google " +"Style Docstring[^googledoc], and the Epytext Style " +"Docstrings[^epytextdoc]." msgstr "" "Python suporta diferentes formatos de docstring. Os formatos mais populares " "para documentar objetos Python são NumPy Style Docstring[^numpydoc], Google " @@ -1553,8 +1567,8 @@ msgstr "**A pyOpenSci recomenda usar a convenção NumPy Docstring.**" #: ../../tutorials/create-python-package.md:177 msgid "" -"[Learn more about docstrings here](api-docstrings) for an overview of both " -"topics." +"[Learn more about docstrings here](api-docstrings) for an overview of " +"both topics." msgstr "" "[Saiba mais sobre docstrings aqui](api-docstrings) para uma visão geral de " "ambos os tópicos." @@ -1569,9 +1583,9 @@ msgstr "A palavra módulo refere-se a um arquivo `.py` contendo código Python." #: ../../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 can " -"have multiple modules[^python-modules]." +"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" +" can have multiple modules[^python-modules]." msgstr "" "O `__init__.py` permite que o Python reconheça que um diretório contém pelo " "menos um módulo que pode ser importado e usado no seu código. Um pacote " @@ -1583,8 +1597,8 @@ msgstr "Passo 3: Opcional -- Adicione código ao seu módulo" #: ../../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 " +"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 "" "Se quiser, adicione uma segunda função ao módulo `example.py`. Pode ser " @@ -1598,9 +1612,9 @@ msgstr "Passo 4: Confira o metadata no seu arquivo `pyproject.toml`" #: ../../tutorials/create-python-package.md:224 msgid "" "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." +"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 "" "Um arquivo [pyproject.toml](pyproject-toml) armazena metadata que fornece " "instruções a várias ferramentas que interagem com ele, incluindo " @@ -1609,9 +1623,9 @@ msgstr "" #: ../../tutorials/create-python-package.md:229 msgid "" -"You will learn more about the `pyproject.toml` format in the [next lesson " -"when you add additional metadata/information to this " -"file.](pyproject-toml.md)" +"You will learn more about the `pyproject.toml` format in the [next lesson" +" when you add additional metadata/information to this file.](pyproject-" +"toml.md)" msgstr "" "Você aprenderá mais sobre o formato `pyproject.toml` na [próxima lição, " "quando adicionar metadata/informações adicionais a este " @@ -1643,9 +1657,9 @@ msgstr "`[this-is-a-table]`." #: ../../tutorials/create-python-package.md:241 msgid "" -"Tables can contain variables within them defined by a variable name and an " -"`=` sign. For instance, a `build-system` table most often holdstwo (2) " -"variables:" +"Tables can contain variables within them defined by a variable name and " +"an `=` sign. For instance, a `build-system` table most often holds two " +"(2) variables:" msgstr "" "Tabelas podem conter variáveis definidas por um nome de variável e um sinal " "de `=`. Por exemplo, uma tabela `build-system` geralmente contém duas (2) " @@ -1653,8 +1667,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:244 msgid "" -"`requires = `, which tells a build tool what tools it needs to installprior " -"to building your package. In this case " +"`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/)." msgstr "" "`requires = `, que informa a uma ferramenta de build quais ferramentas ela " @@ -1663,8 +1677,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:246 msgid "" -"`build-backend = `, which is used to define the specific build-backendname, " -"(in this example we are using `hatchling.build`)." +"`build-backend = `, which is used to define the specific build-backend " +"name, (in this example we are using `hatchling.build`)." msgstr "" "`build-backend = `, que é usado para definir o nome específico do " "build-backend (neste exemplo estamos usando `hatchling.build`)." @@ -1683,25 +1697,25 @@ msgstr "[Saiba mais sobre o formato pyproject.toml aqui.](pyprojecttoml-metadata #: ../../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." +"Open up the `pyproject.toml` file that Hatch created in your favorite " +"text editor. It should look something like the example below." msgstr "" "Abra o arquivo `pyproject.toml` que o Hatch criou no seu editor de texto " "favorito. Ele deve parecer algo como o exemplo abaixo." #: ../../tutorials/create-python-package.md:262 msgid "" -"Make sure the package version, package name, and author name look correct. " -"The email is optional." +"Make sure the package version, package name, and author name look " +"correct. The email is optional." msgstr "" "Verifique se a versão do pacote, o nome do pacote e o nome do autor estão " "corretos. O e-mail é opcional." #: ../../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." +"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 "" "Na parte inferior do arquivo `pyproject.toml` gerado pelo template, você " "verá uma seção que define ambientes Hatch. Abordaremos ambientes Hatch " @@ -1713,9 +1727,10 @@ msgstr "O mínimo necessário em um arquivo pyproject.toml" #: ../../tutorials/create-python-package.md:305 msgid "" -"The core information that you need in a `pyproject.toml` file to publish on " -"PyPI is your **package's name** and the **version**. However, we suggest " -"that you flesh out your metadata early on in the `pyproject.toml` file." +"The core information that you need in a `pyproject.toml` file to publish " +"on PyPI is your **package's name** and the **version**. However, we " +"suggest that you flesh out your metadata early on in the `pyproject.toml`" +" file." msgstr "" "As informações essenciais que você precisa em um arquivo `pyproject.toml` " "para publicar no PyPI são o **nome do pacote** e a **versão**. Porém, " @@ -1724,8 +1739,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:307 msgid "" -"Once you have your project metadata in the `pyproject.toml` file, you will " -"rarely update it." +"Once you have your project metadata in the `pyproject.toml` file, you " +"will rarely update it." msgstr "" "Depois que você tiver o metadata do projeto no arquivo `pyproject.toml`, " "raramente precisará atualizá-lo." @@ -1758,8 +1773,8 @@ msgstr "Agora você está pronto para instalar (e fazer o build) do seu pacote P #: ../../tutorials/create-python-package.md:321 msgid "" -"While you can do this using Hatch, we will use pip for this lesson, soyou " -"can see how to install your tool into your preferred environment." +"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 "" "Embora você possa fazer isso usando Hatch, usaremos pip nesta lição, para " "que você veja como instalar sua ferramenta no ambiente de sua " @@ -1767,8 +1782,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:323 msgid "" -"First, open your preferred shell (Windows users may use something " -"likeGitBash) and `cd` into your project directory if you are not already " +"First, open your preferred shell (Windows users may use something like " +"GitBash) and `cd` into your project directory if you are not already " "there." msgstr "" "Primeiro, abra seu shell preferido (usuários do Windows podem usar algo " @@ -1783,8 +1798,12 @@ msgstr "Ative o ambiente Python que deseja usar." msgid "Run `python -m pip install -e .`" msgstr "Execute `python -m pip install -e .`" -#: ../../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 +#: ../../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" @@ -1794,8 +1813,8 @@ msgstr "Adicionar isso de volta quando a lição for publicada" #: ../../tutorials/create-python-package.md:329 msgid "" -"Activate the Python environment that you wish to use. If you need helpwith " -"working with virtual environments check out this lesson (add link)." +"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 "" "Ative o ambiente Python que deseja usar. Se precisar de ajuda para " "trabalhar com ambiente virtual, confira esta lição (adicionar link)." @@ -1806,12 +1825,12 @@ msgstr "O que `python -m pip install -e .` faz?" #: ../../tutorials/create-python-package.md:358 msgid "" -"`python -m pip install -e .` installs your package into the current active " -"Python environment in **editable mode** (`-e`). Installing yourpackage in " -"editable mode, allows you to work on your code and thentest the updates " -"interactively in your favorite Python interface. One important caveat of " -"editable mode is that every time you update your code, you need to restart " -"Python." +"`python -m pip install -e .` installs your package into the current " +"active Python environment in **editable mode** (`-e`). Installing your " +"package in editable mode, allows you to work on your code and then test " +"the updates interactively in your favorite Python interface. One " +"important caveat of editable mode is that every time you update your " +"code, you need to restart Python." msgstr "" "`python -m pip install -e .` instala seu pacote no ambiente Python ativo " "atual em **modo editável** (`-e`). Instalar seu pacote em modo editável " @@ -1822,8 +1841,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:363 msgid "" -"If you wish to install the package regularly (not in editable mode) you can " -"use:" +"If you wish to install the package regularly (not in editable mode) you " +"can use:" msgstr "" "Se quiser instalar o pacote normalmente (não em modo editável), você pode " "usar:" @@ -1839,8 +1858,8 @@ msgstr "**Usando `python -m` ao chamar `pip`**" #: ../../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 are " -"calling the version of pip installed in your current environment." +"current active environment. `python -m` is important to ensure that you " +"are calling the version of pip installed in your current environment." msgstr "" "Acima, você usa`python -m` para chamar a versão do pip instalada no seu " "ambiente ativo atual. `python -m` é importante para garantir que você " @@ -1848,11 +1867,11 @@ msgstr "" #: ../../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 folder " -"by using the `.`. You could also specify a path tothe project directory on " -"your computer instead of the `.` which tells pip to use the current working " -"directory." +"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 " +"folder by using the `.`. You could also specify a path to the project " +"directory on your computer instead of the `.` which tells pip to use the " +"current working directory." msgstr "" "IMPORTANTE: pip também pode ser usado para instalar pacotes do PyPI. Porém, " "neste caso, você está dizendo ao pip para instalar seu pacote apartir de " @@ -1867,8 +1886,8 @@ msgstr "Procure pyospackage no seu ambiente" #: ../../tutorials/create-python-package.md:379 msgid "" "Once you have installed your package, you can view it in your current " -"environment. If you are using `venv` or `conda`, `pip` list will return a " -"list of packages in the current active environment." +"environment. If you are using `venv` or `conda`, `pip` list will return a" +" list of packages in the current active environment." msgstr "" "Depois de instalar seu pacote, você pode visualizá-lo no seu ambiente " "atual. Se estiver usando `venv` ou `conda`, `pip list` retornará uma lista " @@ -1876,8 +1895,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:383 msgid "" -"Note that because `pyospackage` is installed in editable mode (`-e`), pip " -"will show you the directory path to your project's code" +"Note that because `pyospackage` is installed in editable mode (`-e`), pip" +" will show you the directory path to your project's code" msgstr "" "Observe que, como `pyospackage` está instalado em modo editável (`-e`), o " "pip mostrará o caminho do diretório para o código do seu projeto" @@ -1888,8 +1907,8 @@ msgstr "Passo 6: Teste seu novo pacote" #: ../../tutorials/create-python-package.md:413 msgid "" -"After installing your package, type “python” at the command promptin " -"your chosen terminal to start a Python session in your activePython " +"After installing your package, type “python” at the command prompt in " +"your chosen terminal to start a Python session in your active Python " "environment." msgstr "" "Depois de instalar seu pacote, digite \"python\" no prompt de comando no " @@ -1921,15 +1940,17 @@ msgid "Create a new GitHub repository" msgstr "Criar um novo repositório do GitHub" #: ../../tutorials/create-python-package.md:440 -msgid "Push the contents of the project directory that you created above, to GitHub" +msgid "" +"Push the contents of the project directory that you created above, to " +"GitHub" msgstr "" "Fazer push do conteúdo do diretório do projeto que você criou acima para o " "GitHub" #: ../../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 " +"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 " "branch_or_tag with your specific values." msgstr "" "Por fim, instale o pacote do GitHub usando o comando acima. Ao usar " @@ -1938,8 +1959,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:443 msgid "" -"For instance below you install the pyospackage from the main branch ofthe " -"pyOpenSci repository." +"For instance below you install the pyospackage from the main branch of " +"the pyOpenSci repository." msgstr "" "Por exemplo, abaixo você instala o pyospackage da branch main do repositório " "da pyOpenSci." @@ -1954,8 +1975,8 @@ msgstr "Parabéns! Você criou seu primeiro pacote Python" #: ../../tutorials/create-python-package.md:452 msgid "" -"You have now created a Python package that you can install into any Python " -"environment." +"You have now created a Python package that you can install into any " +"Python environment." msgstr "" "Agora você criou um pacote Python que pode instalar em qualquer " "ambiente Python." @@ -1986,8 +2007,8 @@ msgstr "" #: ../../tutorials/create-python-package.md:460 msgid "" -"Finally you will learn how to [publish to " -"**conda-forge**](publish-conda-forge) from **PyPI**." +"Finally you will learn how to [publish to **conda-forge**](publish-conda-" +"forge) from **PyPI**." msgstr "" "Por fim, você aprenderá a [publicar no " "**conda-forge**](publish-conda-forge) a partir do **PyPI**." @@ -2026,9 +2047,9 @@ msgstr "A estrutura de diretório que você criará nesta lição ficará assim: #: ../../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 " -"code, create package structure, add metadata to pyproject.toml and pip " +"Diagram showing the basic steps to creating an installable package. There" +" are 4 boxes with arrows pointing towards the right. The boxes read, your" +" code, create package structure, add metadata to pyproject.toml and pip " "install package." msgstr "" "Diagrama mostrando os passos básicos para criar um pacote instalável. Há 4 " @@ -2057,10 +2078,10 @@ msgstr "Observe algumas coisas sobre o layout acima:" #: ../../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 that " -"you are running tests on the installed version of " -"yourcode](https://www.pyopensci.org/python-package-guide/package-structure-c" -"ode/python-package-structure.html#the-src-layout-and-testing)." +"that you use `src` (short for **source code**) directory as it [ensures " +"that you are running tests on the installed version of your " +"code](https://www.pyopensci.org/python-package-guide/package-structure-" +"code/python-package-structure.html#the-src-layout-and-testing)." msgstr "" "O código do seu pacote fica dentro de um diretório " "`src/packagename`. Sugerimos que você use o diretório `src` (abreviação de " @@ -2072,8 +2093,9 @@ msgstr "" #: ../../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 " -"will be the name for importing your package in Python code once installed." +"`pyospackage`. Use the name of your package for that directory name. This" +" will be the name for importing your package in Python code once " +"installed." msgstr "" "Dentro do diretório `src`, você tem um diretório de pacote chamado " "`pyospackage`. Use o nome do seu pacote para esse diretório. Este será o " @@ -2081,8 +2103,8 @@ msgstr "" #: ../../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." +"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." msgstr "" "No diretório do seu pacote, você tem um arquivo `__init__.py` e todos os " "seus Python modules. Você aprenderá mais sobre o arquivo `__init__.py` " @@ -2094,10 +2116,10 @@ msgstr "O arquivo `pyproject.toml` fica no diretório raiz do seu pacote." #: ../../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 see " -"that the GitHub / GitLab repository and the root directory name are the " -"same as the package name." +"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 " +"see that the GitHub / GitLab repository and the root directory name are " +"the same as the package name." msgstr "" "O nome do diretório raiz do pacote é **pyospackage**, que é o nome " "do pacote. Isso não é obrigatório, mas você verá com frequência que o " @@ -2110,9 +2132,9 @@ msgstr "O que é um arquivo `__init__.py`?" #: ../../tutorials/create-python-package.md:505 msgid "" -"The `__init__.py` file tells Python that a directory should be treatedas a " -"Python package. As such, a directory with an `__init__.py`file can be " -"imported directly into Python. The `__init__.py` file doesnot need to " +"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" +" imported directly into Python. The `__init__.py` file does not need to " "contain any code in order for Python to recognize it; it can be empty." msgstr "" "O arquivo `__init__.py` informa ao Python que um diretório deve ser tratado " @@ -2129,7 +2151,8 @@ msgstr "" "Por exemplo, seguindo o exemplo de estrutura de arquivos acima, que tem um " "arquivo `__init__.py` dentro dele, você pode executar:" -#: ../../tutorials/create-python-package.md:515 ../../tutorials/pyproject-toml.md:56 +#: ../../tutorials/create-python-package.md:515 +#: ../../tutorials/pyproject-toml.md:56 msgid "What is a pyproject.toml file?" msgstr "O que é um arquivo pyproject.toml?" @@ -2139,8 +2162,8 @@ msgstr "O arquivo **pyproject.toml** é:" #: ../../tutorials/create-python-package.md:519 msgid "" -"Where you define your project's metadata (including its name, " -"authors,license, etc)" +"Where you define your project's metadata (including its name, authors, " +"license, etc)" msgstr "" "Onde você define o metadata do seu projeto (incluindo nome, autores, " "license, etc.)" @@ -2151,10 +2174,9 @@ msgstr "Onde você define dependências (os pacotes dos quais ele depende)" #: ../../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-distribution-files-sdist-w" -"heel)." +"Used to specify and configure what build backend you want to use to " +"[build your package](../package-structure-code/python-package-" +"distribution-files-sdist-wheel)." msgstr "" "Usado para especificar e configurar qual build backend você quer usar para " "[fazer o build do seu " @@ -2164,9 +2186,10 @@ msgstr "" #: ../../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 using " -"tools such as pip. Note that the `pyproject.toml` file needs to have a few " -"basic items defined for the package to be installable including:" +"package can be built and distributed as an installable Python package " +"using tools such as pip. Note that the `pyproject.toml` file needs to " +"have a few basic items defined for the package to be installable " +"including:" msgstr "" "Depois que os arquivos `__init__.py` e `pyproject.toml` forem adicionados, " "seu pacote pode ser construído e distribuído como um pacote Python " @@ -2189,8 +2212,8 @@ msgstr "Por que o arquivo pyproject.toml é importante" #: ../../tutorials/create-python-package.md:535 msgid "" "The `pyproject.toml` file replaces some of the functionality of both the " -"`setup.py` file and `setup.cfg` files. If you try to pip install apackage " -"with no `pyproject.toml`, you will get the following error:" +"`setup.py` file and `setup.cfg` files. If you try to pip install a " +"package with no `pyproject.toml`, you will get the following error:" msgstr "" "O arquivo `pyproject.toml` substitui parte da funcionalidade dos arquivos " "`setup.py` e `setup.cfg`. Se você tentar pip install um pacote sem " @@ -2206,27 +2229,27 @@ msgstr "" #: ../../tutorials/create-python-package.md:546 msgid "" -"See [Using Hatch to Migrate setup.py to a " -"pyproject.toml](setup-py-to-pyproject-toml.md)" +"See [Using Hatch to Migrate setup.py to a pyproject.toml](setup-py-to-" +"pyproject-toml.md)" msgstr "" "Veja [Using Hatch to Migrate setup.py to a " "pyproject.toml](setup-py-to-pyproject-toml.md)" #: ../../tutorials/create-python-package.md:561 msgid "" -"Is it clear where to add commands? Bash vs. Python console Bash vs. Zsh is " -"different" +"Is it clear where to add commands? Bash vs. Python console Bash vs. Zsh " +"is different" msgstr "" "Está claro onde adicionar comandos? Bash vs. console Python Bash vs. Zsh é " "diferente" #: ../../tutorials/create-python-package.md:563 msgid "" -"ADD: note about what makes something \"package worthy\", with a " -"commonmisconception being that a package should be production-ready code " -"that's valuable to a broad audience. This may not be a pervasive " -"misconception in Python, but a quick break-out with an explanation of what " -"a package can consist of would be helpful." +"ADD: note about what makes something \"package worthy\", with a common " +"misconception being that a package should be production-ready code that's" +" valuable to a broad audience. This may not be a pervasive misconception " +"in Python, but a quick break-out with an explanation of what a package " +"can consist of would be helpful." msgstr "" "ADICIONAR: nota sobre o que torna algo \"package worthy\", com um equívoco " "comum de que um pacote deve ser código pronto para produção valioso para um " @@ -2278,10 +2301,10 @@ msgstr "Use ambientes Hatch com seu pacote puro Python" #: ../../tutorials/develop-python-package-hatch.md:13 msgid "" -"[In a previous lesson](create-pure-python-package), you learned how " -"tocreate a Python package using the pyOpenSci copier template. In " -"thislesson, you'll learn how to manage and use the Hatch environments set " -"up by de **What you need to complete this lesson**" +"[In a previous lesson](create-pure-python-package), you learned how to " +"create a Python package using the pyOpenSci copier template. In this " +"lesson, you'll learn how to manage and use the Hatch environments set up " +"by de **What you need to complete this lesson**" msgstr "" "[Em uma lição anterior](create-pure-python-package), você aprendeu a criar " "um pacote Python usando o copier template da pyOpenSci. Nesta lição, você " @@ -2290,10 +2313,10 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:16 msgid "" -"To complete this lesson, you will need a local Python environment and shell " -"on your computer. You will need to have created a package usingour " -"pyOpenSci copier template. You should also have [Hatch " -"installed](get-to-know-hatch)." +"To complete this lesson, you will need a local Python environment and " +"shell on your computer. You will need to have created a package using " +"our pyOpenSci copier template. You should also have [Hatch installed" +"](get-to-know-hatch)." msgstr "" "Para completar esta lição, você precisará de um Python environment local e " "shell no seu computador. Você precisará ter criado um pacote usando nosso " @@ -2303,10 +2326,10 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:20 msgid "" "If you are using Windows or are not familiar with Shell, you may want to " -"check out the [Carpentries shell " -"lesson](https://swcarpentry.github.io/shell-novice/). Windows users will " -"likely need to configure a tool such as " -"[GitBash](https://gitforwindows.org/) for any Shell and git-related steps." +"check out the [Carpentries shell lesson](https://swcarpentry.github.io" +"/shell-novice/). Windows users will likely need to configure a tool such " +"as [GitBash](https://gitforwindows.org/) for any Shell and git-related " +"steps." msgstr "" "Se estiver usando Windows ou não estiver familiarizado com Shell, " "pode querer conferir a [Carpentries shell " @@ -2317,8 +2340,8 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:23 msgid "" -"Welcome to your shiny new package! This page will help you get startedwith " -"using [Hatch](get-to-know-hatch) to run tests, build and check your " +"Welcome to your shiny new package! This page will help you get started " +"with using [Hatch](get-to-know-hatch) to run tests, build and check your " "package, and build your documentation." msgstr "" "Boas-vindas ao seu novo pacote! Esta página ajudará você a começar a usar " @@ -2328,9 +2351,9 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:27 #, python-brace-format msgid "" -"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:" +"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 "" "Para começar, dê uma olhada no arquivo [pyproject.toml](pyproject-toml) no " "diretório do seu pacote. Este arquivo contém a configuração do seu pacote e " @@ -2345,14 +2368,16 @@ msgid "You can nest tables with double brackets like this`[[]]`" msgstr "Você pode aninhar tabelas com colchetes duplos assim`[[]]`" #: ../../tutorials/develop-python-package-hatch.md:33 -msgid "Tables contain information about a certain thing that you want to configure." +msgid "" +"Tables contain information about a certain thing that you want to " +"configure." msgstr "Tabelas contêm informações sobre algo que você quer configurar." #: ../../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 willsignificantly speed " -"up environment creation." +"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 "" "Você pode configurar o Hatch para usar UV por padrão para gerenciamento de " "ambiente. UV é um gerenciador de pacotes construído em Rust. É rápido e " @@ -2360,25 +2385,25 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:38 msgid "" -"To use UV with Hatch, configure Hatch in the \"tools\" section of " -"your`pyproject.toml` file." +"To use UV with Hatch, configure Hatch in the \"tools\" section of your " +"`pyproject.toml` file." msgstr "" "Para usar UV com Hatch, configure o Hatch na seção \"tools\" do seu arquivo " "`pyproject.toml`." #: ../../tutorials/develop-python-package-hatch.md:46 msgid "" -"Using Hatch for developing, building, and maintaining your pure " -"Pythonpackage" +"Using Hatch for developing, building, and maintaining your pure Python " +"package" msgstr "Usando Hatch para desenvolver, fazer o build, e manter seu pacote Python puro" #: ../../tutorials/develop-python-package-hatch.md:48 #, python-brace-format msgid "" "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:" +"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 "" "No template de pacote Python da pyOpenSci, configuramos definições " "de{term}`Hatch environment`. Você notará na parte inferior do arquivo uma " @@ -2387,8 +2412,8 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:59 msgid "" -"Hatch allows you to configure and run environments and scripts similarto a " -"workflow tool like tox or nox." +"Hatch allows you to configure and run environments and scripts similar to" +" a workflow tool like tox or nox." msgstr "" "Hatch permite que você configure e execute ambientes e scripts de forma " "semelhante a uma ferramenta de workflow como tox ou nox." @@ -2412,16 +2437,16 @@ msgstr "" #: ../../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:" +"Below is the Hatch environment used to build and test your package. " +"Anytime you see: `tool.hatch.envs.test`, it tells Hatch:" msgstr "" "Abaixo está o ambiente Hatch usado para fazer o build e testar seu " "pacote. Sempre que você vir: `tool.hatch.envs.test`, isso informa ao Hatch:" #: ../../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.\"" +"\"Hey, Hatch, this is the definition for an environment.`test` is the " +"name of the environment that I want you to create.\"" msgstr "" "\"Ei, Hatch, esta é a definição de um ambiente. `test` é o nome do " "ambiente que quero que você crie.\"" @@ -2432,8 +2457,8 @@ msgstr "Então `tool.hatch.envs.build` criará um ambiente chamado `build`." #: ../../tutorials/develop-python-package-hatch.md:75 msgid "" -"Below the environment \"declaration,\" you can see the definition of what " -"should be in that environment." +"Below the environment \"declaration,\" you can see the definition of what" +" should be in that environment." msgstr "" "Abaixo da \"declaração\" do ambiente, você pode ver a definição do que " "deve estar nesse ambiente." @@ -2445,9 +2470,9 @@ msgstr "Um ambiente Hatch para fazer o build do seu pacote" #: ../../tutorials/develop-python-package-hatch.md:79 #, python-brace-format msgid "" -"Below is a Hatch environment definition that you will find in your " -"newproject's [pyproject.toml](pyproject-toml) file. It is set up to " -"buildyour package's {term}`Distribution files` ({term}`Source distribution " +"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 "" "Abaixo está uma definição de ambiente Hatch que você encontrará no " @@ -2459,10 +2484,10 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:84 #, python-brace-format msgid "" -"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)." +"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 "" "Observe que a definição do ambiente declara duas {term}`dependências " "`: `pip` e `twine`, que o ambiente precisa para executar " @@ -2475,8 +2500,8 @@ msgstr "Hatch instalará seu pacote em modo editável por padrão" #: ../../tutorials/develop-python-package-hatch.md:100 msgid "" -"Notice the `detached = True` flag at the bottom of the environment. " -"Bydefault, hatch will install your package in editable mode into any " +"Notice the `detached = True` flag at the bottom of the environment. By " +"default, hatch will install your package in editable mode into any " "environment it creates. `detached=True` tells it not to install your " "package into the environment." msgstr "" @@ -2501,8 +2526,8 @@ msgstr "" #: ../../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." +"create as a virtual environment (venv). Because `detached = True` in that" +" environment, Hatch won't install your package into it." msgstr "" "Acima, você definiu um novo ambiente chamado 'build' que o Hatch criará " "como um ambiente virtual (venv). Como `detached = True` nesse " @@ -2510,8 +2535,8 @@ msgstr "" #: ../../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." +"You can then use that environment to run \"scripts\". The definition " +"below tells Hatch to run the following scripts in the build environment." msgstr "" "Você pode então usar esse ambiente para executar \"scripts\". A definição " "abaixo informa ao Hatch para executar os seguintes scripts no ambiente " @@ -2535,14 +2560,16 @@ msgstr "`envs.build`: Use o ambiente build definido." #: ../../tutorials/develop-python-package-hatch.md:119 msgid "" -"`scripts`: Define what scripts to run. In this case, Hatch will run shell " -"scripts." +"`scripts`: Define what scripts to run. In this case, Hatch will run shell" +" scripts." msgstr "" "`scripts`: Defina quais scripts executar. Neste caso, o Hatch executará " "shell scripts." #: ../../tutorials/develop-python-package-hatch.md:122 -msgid "Below is the `build.scripts` table that defines 3 shell commands to berun:" +msgid "" +"Below is the `build.scripts` table that defines 3 shell commands to be " +"run:" msgstr "" "Abaixo está a tabela `build.scripts` que define 3 comandos shell a serem " "executados:" @@ -2559,17 +2586,17 @@ msgstr "" #: ../../tutorials/develop-python-package-hatch.md:126 msgid "" -"`twine check dist/*` # use twine to check that your package's sdist (source " -"distribution) is ok." +"`twine check dist/*` # use twine to check that your package's sdist " +"(source distribution) is ok." msgstr "" "`twine check dist/*` # usa twine para verificar se o sdist (source " "distribution) do seu pacote está ok." #: ../../tutorials/develop-python-package-hatch.md:140 msgid "" -"Hatch, by default, will install your package in editable mode into " -"anyvirtual environment (venv) that it creates. If `detached=True` is " -"set,then it will skip that step." +"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 "" "Hatch, por padrão, instalará seu pacote em modo editável em qualquer " "ambiente virtual (venv) que criar. Se `detached=True` estiver definido, " @@ -2589,8 +2616,8 @@ msgstr "`hatch run build:check`" #: ../../tutorials/develop-python-package-hatch.md:149 msgid "" -"This step updates the build environment and then builds and checks " -"theoutput distributions of your package." +"This step updates the build environment and then builds and checks the " +"output distributions of your package." msgstr "" "Esta etapa atualiza o ambiente build e então faz o build e verifica as " "distribuições de saída do seu pacote." @@ -2603,7 +2630,8 @@ msgstr "Você pode entrar no ambiente build no seu shell para conferir:" msgid "If you run `pip list` in the environment, twine will be there:" msgstr "Se executar `pip list` no ambiente, o twine estará lá:" -#: ../../tutorials/develop-python-package-hatch.md:163 ../../tutorials/develop-python-package-hatch.md:221 +#: ../../tutorials/develop-python-package-hatch.md:163 +#: ../../tutorials/develop-python-package-hatch.md:221 msgid "To leave the environment use:" msgstr "Para sair do ambiente, use:" @@ -2627,9 +2655,9 @@ msgstr "Abaixo, você vê a tabela do ambiente Hatch test." #: ../../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)." +"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 "" "Semelhante ao ambiente build acima, o ambiente abaixo define as " "dependencies que o Hatch precisa instalar no ambiente de teste " @@ -2641,9 +2669,9 @@ msgstr "Seu ambiente de teste tem uma matriz associada a ele" #: ../../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." +"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 "" "Se o ambiente tiver uma matriz associada, isso informa ao Hatch para " "executar os testes em diferentes versões do Python. Abaixo, você está " @@ -2652,8 +2680,9 @@ msgstr "" #: ../../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 install " -"Hatch and also when you declare a matrix environment like the one below" +"UV](https://docs.astral.sh/uv/guides/install-python/) both when you " +"install Hatch and also when you declare a matrix environment like the one" +" below" msgstr "" "Hatch, por padrão, instalará Python [usando " "UV](https://docs.astral.sh/uv/guides/install-python/) tanto quando você " @@ -2663,8 +2692,8 @@ msgstr "" 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 " -"choose from, you need to select the environment with the Python version you " -"want to use." +"choose from, you need to select the environment with the Python version " +"you want to use." msgstr "" "No seu projeto, se executar `hatch shell test`, verá a saída abaixo. Isso " "significa que, como há uma matriz de versões do Python para escolher, você " @@ -2684,9 +2713,9 @@ msgstr "Hatch scripts para testes" #: ../../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." +"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 "" "Na mesma seção de testes, você verá uma seção " "`tool.hatch.envs.test.scripts`. Semelhante ao que você viu acima com as " @@ -2714,24 +2743,26 @@ msgid "Reminder" msgstr "Lembrete" #: ../../tutorials/develop-python-package-hatch.md:246 -msgid "`hatch run`: this calls hatch and tells it that it will be running a command" +msgid "" +"`hatch run`: this calls hatch and tells it that it will be running a " +"command" msgstr "`hatch run`: isso chama o Hatch e informa que ele executará um comando" #: ../../tutorials/develop-python-package-hatch.md:247 msgid "" -"`test:run` defines the environment you want it to run (`test`) in thiscase, " -"and the script is defined as `run`" +"`test:run` defines the environment you want it to run (`test`) in this " +"case, and the script is defined as `run`" msgstr "" "`test:run` define o ambiente em que você quer que execute (`test`) neste " "caso, e o script é definido como `run`" #: ../../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 Python " -"environment. In this case, since there are four Python versions in the " -"environment, your tests will be run four times, once in each Python version " -"listed in the matrix table." +"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 " +"Python environment. In this case, since there are four Python versions in" +" the environment, your tests will be run four times, once in each Python " +"version listed in the matrix table." msgstr "" "Se você tiver uma matriz configurada para testes, ela instalará a versão " "necessária do Python usando UV e executará seus testes em cada versão do " @@ -2745,8 +2776,8 @@ msgstr "Construa sua documentação com um ambiente Hatch" #: ../../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:" +"Finally, you can build and serve your documentation using hatch. To build" +" a static HTML version of the docs run:" msgstr "" "Por fim, você pode fazer o build e servir sua documentação usando o Hatch. " "Para gerar uma versão HTML estática da documentação, execute:" @@ -2792,9 +2823,9 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:13 msgid "" -"It is an end-to-end tool that supports most of the steps required to create " -"a quality Python package. Beginners will have fewer tools to learn if they " -"use Hatch." +"It is an end-to-end tool that supports most of the steps required to " +"create a quality Python package. Beginners will have fewer tools to learn" +" if they use Hatch." msgstr "" "É uma ferramenta ponta a ponta que suporta a maioria das etapas necessárias " "para criar um pacote Python de qualidade. Iniciantes terão menos ferramentas " @@ -2819,8 +2850,8 @@ msgstr "" #: ../../tutorials/get-to-know-hatch.md:21 msgid "" -"In this tutorial, you will install and get to know Hatch a bit more before " -"starting to use it." +"In this tutorial, you will install and get to know Hatch a bit more " +"before starting to use it." msgstr "" "Neste tutorial, você instalará e conhecerá um pouco mais o Hatch antes de " "começar a usá-lo." @@ -2839,8 +2870,8 @@ msgstr "Você precisa ter o Hatch instalado." #: ../../tutorials/get-to-know-hatch.md:30 msgid "" -"If you don't already have Python installed on your computer, Hatch will do " -"it for you when you install Hatch." +"If you don't already have Python installed on your computer, Hatch will " +"do it for you when you install Hatch." msgstr "" "Se você ainda não tiver o Python instalado no seu computador, o Hatch fará " "isso por você quando você instalar o Hatch." @@ -2869,8 +2900,8 @@ msgstr "Siga as instruções [aqui](https://hatch.pypa.io/latest/install/#instal #: ../../tutorials/get-to-know-hatch.md:45 msgid "" -"Download the latest GUI installer for MAC " -"[hatch-universal.pkg](https://github.com/pypa/hatch/releases/latest/download" +"Download the latest GUI installer for MAC [hatch-" +"universal.pkg](https://github.com/pypa/hatch/releases/latest/download" "/hatch-universal.pkg)." msgstr "" "Baixe o instalador GUI mais recente para MAC " @@ -2892,8 +2923,7 @@ msgstr "Windows" #: ../../tutorials/get-to-know-hatch.md:53 msgid "" "In your browser, download the correct `.msi` file for your system: " -"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch" -"-x64.msi)" +"[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch-x64.msi)" msgstr "" "No seu navegador, baixe o arquivo `.msi` correto para o seu sistema: " "[hatch-x64.msi](https://github.com/pypa/hatch/releases/latest/download/hatch" @@ -2909,8 +2939,8 @@ msgstr "Linux" #: ../../tutorials/get-to-know-hatch.md:61 msgid "" -"We suggest that you install Hatch using pipx on Linux. however, if " -"youprefer another method, check out the [Hatch installation " +"We suggest that you install Hatch using pipx on Linux. however, if you " +"prefer another method, check out the [Hatch installation " "documentation](https://hatch.pypa.io/latest/install/) for other methods." msgstr "" "Sugerimos que você instale o Hatch usando pipx no Linux. No entanto, se " @@ -2921,8 +2951,8 @@ msgstr "" #, python-brace-format msgid "" "Hatch can also be installed directly using {term}`pip` or " -"[conda](https://hatch.pypa.io/latest/install/#conda). We encourage youto " -"follow the instructions above because we have found that the Hatch " +"[conda](https://hatch.pypa.io/latest/install/#conda). We encourage you to" +" follow the instructions above because we have found that the Hatch " "installers for Windows and Mac are the easiest and most efficient." msgstr "" "O Hatch também pode ser instalado diretamente usando {term}`pip` ou " @@ -2941,8 +2971,9 @@ msgstr "" #: ../../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 that " -"Hatch is available across all of your Python environments on yourcomputer." +"ensure that you have Hatch installed globally. A global install means " +"that Hatch is available across all of your Python environments on your " +"computer." msgstr "" "Ambas as abordagens (usar um instalador gráfico no Windows/Mac e " "pipx) garantem que você tenha o Hatch instalado globalmente. Uma instalação " @@ -2955,8 +2986,8 @@ msgstr "Verifique se o Hatch foi instalado corretamente" #: ../../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 usingthe " +"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 "" "Depois de concluir as instruções de instalação acima, abra o terminal e " @@ -2977,8 +3008,8 @@ msgstr "Configurar o Hatch" #: ../../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 youcreate. " -"While this step is not required, we suggest that you do it." +"includes setting the default name and setup for every package you create." +" While this step is not required, we suggest that you do it." msgstr "" "Depois de instalar o Hatch, você pode personalizar sua configuração. Isso " "inclui definir o nome padrão e a configuração de cada pacote que você criar. " @@ -2995,8 +3026,8 @@ msgstr "" #: ../../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 using " -"it for the first time." +"might be easier to look at and update it in a text editor if you are " +"using it for the first time." msgstr "" "Embora você possa atualizar o arquivo `config.toml` pela linha de comando, " "pode ser mais fácil visualizá-lo e editá-lo em um editor de texto se for a " @@ -3008,8 +3039,8 @@ msgstr "Etapa 1: Abrir e editar seu arquivo `config.toml`" #: ../../tutorials/get-to-know-hatch.md:115 msgid "" -"To open the config file in your file browser, run the following command in " -"your shell:" +"To open the config file in your file browser, run the following command " +"in your shell:" msgstr "" "Para abrir o arquivo de configuração no explorador de arquivos, execute o " "seguinte comando no shell:" @@ -3020,16 +3051,16 @@ msgstr "`hatch config explore`" #: ../../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." +"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 "" "Isso abrirá uma janela de diretório que permite clicar duas vezes no " "arquivo e abri-lo no seu editor de texto favorito." #: ../../tutorials/get-to-know-hatch.md:123 msgid "" -"You can also retrieve the location of the Hatch config file by runningthe " -"following command in your shell:" +"You can also retrieve the location of the Hatch config file by running " +"the following command in your shell:" msgstr "" "Você também pode obter a localização do arquivo de configuração do Hatch " "executando o seguinte comando no shell:" @@ -3042,7 +3073,8 @@ msgstr "Etapa 2 - atualize seu e-mail e nome" 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](pyproject-toml) metadata files that you create using Hatch." +"[pyproject.toml](pyproject-toml) metadata files that you create using " +"Hatch." msgstr "" "Com o arquivo aberto, atualize a tabela [template] do arquivo `config.toml` " "com seu nome e e-mail. Essas informações serão usadas em quaisquer arquivos " @@ -3058,10 +3090,10 @@ msgstr "Em seguida, defina `tests` como `false` na tabela `[template.plugins.def #: ../../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 " -"to use this feature in this beginner friendly tutorial series butwe will " -"introduce it in later tutorials." +"While tests are important, setting the tests configuration in Hatch to " +"`true` will create a more complex `pyproject.toml` file. You won't need " +"to use this feature in this beginner friendly tutorial series but we will" +" introduce it in later tutorials." msgstr "" "Embora testes sejam importantes, definir a configuração de `tests` no Hatch " "como `true` criará um arquivo `pyproject.toml` mais complexo. Você não " @@ -3074,11 +3106,11 @@ msgstr "Seu arquivo `config.toml` deve ficar parecido com o exemplo abaixo." #: ../../tutorials/get-to-know-hatch.md:191 msgid "" -"Also notice that the default license option is MIT. While we will discuss " -"license in more detail in a later lesson, the MIT license is the " +"Also notice that the default license option is MIT. While we will discuss" +" license in more detail in a later lesson, the MIT license is the " "recommended permissive license from " -"[choosealicense.com](https://choosealicense.com/) and as such we will use " -"it for this tutorial series." +"[choosealicense.com](https://choosealicense.com/) and as such we will use" +" it for this tutorial series." msgstr "" "Observe também que a opção de `license` padrão é MIT. Embora abordemos " "`license` com mais detalhes em uma lição posterior, a `license` MIT é a " @@ -3092,8 +3124,8 @@ msgstr "Você pode, claro, escolher outra `license`." #: ../../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" +"I think we'd need the SPDX license options here if they want to chose " +"bsd-3 for instance" msgstr "" "Acho que precisaríamos das opções de `license` SPDX aqui se quisessem " "escolher bsd-3, por exemplo" @@ -3104,8 +3136,8 @@ msgstr "Etapa 4: Feche o arquivo de configuração e execute `hatch config show` #: ../../tutorials/get-to-know-hatch.md:205 msgid "" -"Once you have completed the steps above run the following command in your " -"shell." +"Once you have completed the steps above run the following command in your" +" shell." msgstr "Depois de concluir as etapas acima, execute o seguinte comando no shell." #: ../../tutorials/get-to-know-hatch.md:207 @@ -3114,9 +3146,9 @@ msgstr "`hatch config show`" #: ../../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 is set. " -"Also make sure that `tests=false`." +"`hatch config show` will print out the contents of your `config.toml` " +"file in your shell. Look at the values and ensure that your name, email " +"is set. Also make sure that `tests=false`." msgstr "" "`hatch config show` exibirá o conteúdo do seu arquivo `config.toml` " "no shell. Verifique os valores e confirme que seu nome e e-mail estão " @@ -3140,8 +3172,9 @@ msgstr "Comparação com outras ferramentas" #: ../../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-features)" +"[We compared Hatch to several of the other popular packaging tools in the" +" ecosystem including flit, pdm and poetry. Learn more here](package-" +"features)" msgstr "" "[Comparamos o Hatch a várias outras ferramentas populares de empacotamento " "do ecossistema, incluindo flit, pdm e poetry. Saiba " @@ -3157,7 +3190,7 @@ msgstr "Alguns recursos que o Hatch oferece" #: ../../tutorials/get-to-know-hatch.md:227 msgid "" -"It will convert metadata stored in a `setup.py` or `setup.cfg` file toa " +"It will convert metadata stored in a `setup.py` or `setup.cfg` file to a " "pyproject.toml file for you (see [Migrating setup.py to pyproject.toml " "using Hatch](setup-py-to-pyproject-toml.md ))" msgstr "" @@ -3268,8 +3301,8 @@ msgstr "_Um tutorial para iniciantes, do começo ao fim_" #: ../../tutorials/intro.md:11 #, python-brace-format msgid "" -"Welcome to the pyOpenSci Python packaging tutorial se ries. The lessons on " -"the upcoming pages walk you through the core steps needed to create a " +"Welcome to the pyOpenSci Python packaging tutorial series. The lessons on" +" the upcoming pages walk you through the core steps needed to create a " "{term}`Python package`." msgstr "" "Boas-vindas à série de tutoriais de empacotamento Python da pyOpenSci. As " @@ -3278,10 +3311,10 @@ msgstr "" #: ../../tutorials/intro.md:17 msgid "" -"Diagram showing the lessons in our packaging tutorial. There are 6 total - " -"what is a Python package, make code pip installable, publish your package " -"to PyPI, add a README and LICENSE file, add metadata for PyPI and finally " -"publish to conda forge." +"Diagram showing the lessons in our packaging tutorial. There are 6 total " +"- what is a Python package, make code pip installable, publish your " +"package to PyPI, add a README and LICENSE file, add metadata for PyPI and" +" finally publish to conda forge." msgstr "" "Diagrama mostrando as lições do nosso tutorial de empacotamento. São 6 ao " "todo: o que é um pacote Python, tornar o código instalável com pip, publicar " @@ -3302,10 +3335,10 @@ msgstr "Para quem são estes tutoriais?" #: ../../tutorials/intro.md:24 msgid "" -"The content in this tutorial series is beginner friendly and assumes that " -"you have not created a Python package before. However, the content will " -"still be valuable if you are interested in better understanding the steps " -"involved in creating a Python package." +"The content in this tutorial series is beginner friendly and assumes that" +" you have not created a Python package before. However, the content will " +"still be valuable if you are interested in better understanding the steps" +" involved in creating a Python package." msgstr "" "O conteúdo desta série de tutoriais é adequado para iniciantes e parte do " "pressuposto de que você ainda não criou um pacote Python. No entanto, o " @@ -3314,22 +3347,24 @@ msgstr "" #: ../../tutorials/intro.md:29 msgid "" -"In this series you will learn about the core elements that you need " -"topublish your package to [PyPI](publish-pypi)." +"In this series you will learn about the core elements that you need to " +"publish your package to [PyPI](publish-pypi)." msgstr "" "Nesta série, você aprenderá sobre os elementos essenciais de que precisa " "para publicar seu pacote no [PyPI](publish-pypi)." #: ../../tutorials/intro.md:32 msgid "" -"In the second series, you will learn about infrastructure and documentation " -"needed to support package maintenance." +"In the second series, you will learn about infrastructure and " +"documentation needed to support package maintenance." msgstr "" "Na segunda série, você aprenderá sobre a infraestrutura e a documentação " "necessárias para dar suporte à manutenção do pacote." -#: ../../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 +#: ../../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 "Objetivos de Aprendizagem" @@ -3351,16 +3386,16 @@ msgstr "Ser capaz de listar os 5 componentes centrais de um pacote Python" #: ../../tutorials/intro.md:84 msgid "" -"Be able to explain the difference between generalizable code and code that " -"supports a specific scientific application" +"Be able to explain the difference between generalizable code and code " +"that supports a specific scientific application" msgstr "" "Ser capaz de explicar a diferença entre código generalizável e código que " "dá suporte a uma aplicação científica específica" #: ../../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." +"At a high level, you can think about a Python package as a toolbox that " +"you can use to perform various tasks." msgstr "" "Em um nível geral, você pode pensar em um pacote Python como uma caixa de " "ferramentas que pode ser usada para realizar diversas tarefas." @@ -3368,12 +3403,12 @@ msgstr "" #: ../../tutorials/intro.md:94 #, python-brace-format msgid "" -"A Python package is basically a directory with a specific file structure. " -"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." +"A Python package is basically a directory with a specific file structure." +" 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 "" "Um pacote Python é basicamente um diretório com uma estrutura de arquivos " "específica. Dentro da estrutura de diretórios do pacote, há objetos " @@ -3384,16 +3419,16 @@ msgstr "" #: ../../tutorials/intro.md:103 msgid "" -"Diagram showing a sketch of a toolbox filled with different tools including " -"a hammer and a saw." +"Diagram showing a sketch of a toolbox filled with different tools " +"including a hammer and a saw." msgstr "" "Diagrama mostrando um esboço de uma caixa de ferramentas cheia de " "diferentes ferramentas, incluindo um martelo e um serrote." #: ../../tutorials/intro.md:105 msgid "" -"You can think about a package as a toolbox filled with coding tools. Atool " -"may be a function or a class. Each tool does a specific thing well." +"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." msgstr "" "Você pode pensar em um pacote como uma caixa de ferramentas cheia de " "ferramentas de código. Cada ferramenta pode ser uma função ou uma classe. " @@ -3407,8 +3442,8 @@ msgstr "Pacotes Python são instaláveis" 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 " -"functionality like you would import core scientific Pythonpackages such as " -"NumPy or Matplotlib." +"functionality like you would import core scientific Python packages such " +"as NumPy or Matplotlib." msgstr "" "Um pacote é instalável, o que significa que você pode adicionar a " "funcionalidade do código do pacote a qualquer ambiente Python e importar " @@ -3417,10 +3452,10 @@ msgstr "" #: ../../tutorials/intro.md:121 msgid "" -"Installing a package into an environment makes it easier to manage andreuse " -"your code across different projects. Structuring your code asa package is " -"the first step you need to take so you can share the tools in the toolbox " -"you've created and let others build with it." +"Installing a package into an environment makes it easier to manage and " +"reuse your code across different projects. Structuring your code as a " +"package is the first step you need to take so you can share the tools in " +"the toolbox you've created and let others build with it." msgstr "" "Instalar um pacote em um ambiente facilita gerenciar e reutilizar seu código " "em projetos diferentes. Estruturar seu código como um pacote é o primeiro " @@ -3439,8 +3474,8 @@ msgstr "Você pode criar um pacote Python porque deseja:" msgid "" "**Use your code across different projects:** At its most basic level, " "creating a package allows you to install your code into a Python " -"environment. This allows you to then import functions and classes intoany " -"workflows both locally and in the cloud." +"environment. This allows you to then import functions and classes into " +"any workflows both locally and in the cloud." msgstr "" "**Usar seu código em projetos diferentes:** No nível mais básico, criar um " "pacote permite instalar seu código em um ambiente Python. Isso permite " @@ -3450,9 +3485,9 @@ msgstr "" #: ../../tutorials/intro.md:131 #, python-brace-format msgid "" -"**Share your code:** If you publish a package on a public repository such " -"as PyPI or conda-forge, your package can be installed on any machine using " -"{term}`pip` or conda with a single command." +"**Share your code:** If you publish a package on a public repository such" +" as PyPI or conda-forge, your package can be installed on any machine " +"using {term}`pip` or conda with a single command." msgstr "" "**Compartilhar seu código:** Se você publicar um pacote em um repositório " "público como PyPI ou conda-forge, seu pacote pode ser instalado em qualquer " @@ -3460,13 +3495,13 @@ msgstr "" #: ../../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 on GitHub). " -"A version control system such as git (the systemused by GitHub), further " -"makes it easier to track changes to thecodebase over time. Tools such as " -"issues and pull requests make it easier for outside users to contribute bug " -"fixes and to establish review processes for accepting changes to the code " -"base." +"**Build community around your code:** Packages make it easier for " +"multiple people to work on the same project (particularly when published " +"on GitHub). A version control system such as git (the system used by " +"GitHub), further makes it easier to track changes to the codebase over " +"time. Tools such as issues and pull requests make it easier for outside " +"users to contribute bug fixes and to establish review processes for " +"accepting changes to the code base." msgstr "" "**Construir comunidade em torno do seu código:** pacotes facilitam " "que várias pessoas trabalhem no mesmo projeto (especialmente quando " @@ -3479,9 +3514,9 @@ msgstr "" #: ../../tutorials/intro.md:135 msgid "" "**Organize your code:** Packages can be used to organize large code " -"projects, dividing them into smaller, more manageable components. " -"Thisstructure can help with both maintaining the codebase and with making " -"it easier to understand." +"projects, dividing them into smaller, more manageable components. This " +"structure can help with both maintaining the codebase and with making it " +"easier to understand." msgstr "" "**Organizar seu código:** pacotes podem ser usados para organizar grandes " "projetos de código, dividindo-os em componentes menores e mais gerenciáveis. " @@ -3516,9 +3551,9 @@ msgstr "Se você tem tempo para adicionar coisas como documentação e testes" #: ../../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 update it, " -"fix bugs and answer questions." +"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 " +"update it, fix bugs and answer questions." msgstr "" "Por quanto tempo você poderá mantê-lo: lembre-se de que, quando as pessoas " "começarem a usar seu pacote, elas dependerão da sua equipe de mantenedores " @@ -3543,9 +3578,9 @@ msgstr "Diagrama mostrando .. mais aqui se isto permanecer." #: ../../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 making " -"sure everything works and is up to date while fixing bugs and addressing " -"user concerns." +"OSI-approved license and infrastructure. Maintainers are at the core " +"making sure everything works and is up to date while fixing bugs and " +"addressing user concerns." msgstr "" "Os elementos de um pacote Python incluem código, documentação, testes,uma " "`license` aprovada pela OSI e infraestrutura. Os mantenedores estão no centro, " @@ -3566,8 +3601,8 @@ msgstr "" #: ../../tutorials/intro.md:164 msgid "" -"**Documentation:** Installation instructions, tutorials, and examples that " -"both help users get started using your package and contributors and " +"**Documentation:** Installation instructions, tutorials, and examples " +"that both help users get started using your package and contributors and " "maintainers fix bugs and maintain the package." msgstr "" "**Documentation:** Instruções de instalação, tutoriais e exemplos que " @@ -3576,8 +3611,8 @@ msgstr "" #: ../../tutorials/intro.md:165 msgid "" -"Contributor Documentation in the form of a **CONTRIBUTING.md** file " -"isuseful to help people to contribute to your package." +"Contributor Documentation in the form of a **CONTRIBUTING.md** file is " +"useful to help people to contribute to your package." msgstr "" "Documentação para contributors na forma de um arquivo **CONTRIBUTING.md** é " "útil para ajudar pessoas a contribuir com seu pacote." @@ -3592,8 +3627,9 @@ msgstr "" #: ../../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 codein the future" +"**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 "" "**Tests:** que garantem que seu código funciona como deveria e facilitam " "que você e outras pessoas contribuam, modifiquem e atualizemo código no " @@ -3613,10 +3649,11 @@ msgstr "" #: ../../tutorials/intro.md:169 msgid "" -"**Infrastructure** that automates updates, publication workflows and runs " -"test suites. Infrastructure includes a suite of things such as platforms " -"like GitHub and GitLab, tools to run tests and tools locallysuch as nox and " -"tox and continuous integration that automates package maintenance steps." +"**Infrastructure** that automates updates, publication workflows and runs" +" test suites. Infrastructure includes a suite of things such as platforms" +" like GitHub and GitLab, tools to run tests and tools locally such as nox" +" and tox and continuous integration that automates package maintenance " +"steps." msgstr "" "**Infrastructure** que automatiza atualizações, workflows de publicação e " "executa suites de testes. A infraestrutura inclui um conjunto de coisas, " @@ -3631,10 +3668,10 @@ msgstr "O que a pyOpenSci busca em um pacote" #: ../../tutorials/intro.md:174 msgid "" "pyOpenSci performs an [initial set of editor " -"checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chie" -"f-guide.html#editor-checklist-template)foranypackagesubmittedtousforpeerrevi" -"ew. You may find these checksuseful as you create yourpackageas a baseline " -"for things thatyou package should have." +"checks](https://www.pyopensci.org/software-peer-review/how-to/editor-in-" +"chief-guide.html#editor-checklist-template) for any package submitted to " +"us for peer review. You may find these checks useful as you create your " +"package as a baseline for things that you package should have." msgstr "" "A pyOpenSci realiza um [conjunto inicial de verificações do " "editor](https://www.pyopensci.org/software-peer-review/how-to/editor-in-chie" @@ -3649,9 +3686,9 @@ msgstr "Pacotes são mais do que apenas código - Infraestrutura" #: ../../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 only " -"writing high quality code, but also the various elements of a package that " -"make it a useful community resource." +"people to use your package, besides yourself, you should consider not " +"only writing high quality code, but also the various elements of a " +"package that make it a useful community resource." msgstr "" "Um pacote em qualquer linguagem é mais do que apenas código. Se você espera " "que outras pessoas usem seu pacote, além de você mesmo, considere não " @@ -3667,9 +3704,9 @@ 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/) " "for version control. Having your software under version control is " -"important because it allows you to both trackchanges over time while also " -"going back in history and undoing changesin the case that a change to the " -"code base unexpectedly breaks something." +"important because it allows you to both track changes over time while " +"also going back in history and undoing changes in the case that a change " +"to the code base unexpectedly breaks something." msgstr "" "A maioria dos pacotes Python fica em uma plataforma online de controle de " "versão como GitHub ou GitLab. GitHub e GitLab executam " @@ -3681,9 +3718,9 @@ msgstr "" #: ../../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 make " -"contributions using a pull request (GitHub) / merge request (GitLab) / code " -"review workflow." +"public facing. This means that others can both see your code and also " +"make contributions using a pull request (GitHub) / merge request (GitLab)" +" / code review workflow." msgstr "" "Ao publicar seu pacote no GitHub ou GitLab, você o torna público. " "Isso significa que outras pessoas podem ver seu código e também contribuir " @@ -3696,10 +3733,10 @@ msgstr "GitHub e GitLab vs. Git" #: ../../tutorials/intro.md:199 msgid "" -"GitHub and GitLab are online (cloud) platforms that run `git` " -"(versioncontrol software) on the backend. Running git locally on your " -"computerallows you to upload (`git push`) and download (`git pull`) files " -"to GitHub and GitLab." +"GitHub and GitLab are online (cloud) platforms that run `git` (version " +"control software) on the backend. Running git locally on your computer " +"allows you to upload (`git push`) and download (`git pull`) files to " +"GitHub and GitLab." msgstr "" "GitHub e GitLab são plataformas online (na nuvem) que executam `git` " "(software de controle de versão) no backend. Executar git localmente no seu " @@ -3730,8 +3767,8 @@ msgstr "que usuários reportem bugs, façam perguntas e solicitem novos recursos #: ../../tutorials/intro.md:210 msgid "" -"you to publicly keep track of enhancements and features you want to work on " -"for your package." +"you to publicly keep track of enhancements and features you want to work " +"on for your package." msgstr "" "que você acompanhe publicamente melhorias e recursos que deseja desenvolver " "para seu pacote." @@ -3743,8 +3780,8 @@ msgstr "Integração contínua e implantação contínua" #: ../../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 " -"automatically runs a specific job when a certain event occurs, whereas " +"deployment (CI/CD). Continuous integration (CI) refers to a platform that" +" automatically runs a specific job when a certain event occurs, whereas " "continuous deployment (CD) is an extension of CI that refers to not only " "running or building but also to publishing the final outputs somewhere." msgstr "" @@ -3761,8 +3798,8 @@ msgstr "**Um exemplo de integração contínua:**" #: ../../tutorials/intro.md:218 msgid "" -"When someone submits a change to your code, your tests will run " -"acrossdifferent operating systems and the code will be checked for format " +"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 "" "Quando alguém envia uma mudança no seu código, seus testes serão executados " @@ -3775,8 +3812,9 @@ msgstr "**Um exemplo de implantação contínua:**" #: ../../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." +"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 "" "Quando você estiver pronto para fazer release do seu pacote no PyPI, uma " "operação de implantação contínua pode ser acionada no release para publicar " @@ -3785,9 +3823,9 @@ msgstr "" #: ../../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 you " -"maintain code style and format consistency for every new change to your " -"code." +"changes to the code don't break things unexpectedly. They can also help " +"you maintain code style and format consistency for every new change to " +"your code." msgstr "" "CI/CD integrado ajudará você a manter seu software, garantindo que mudanças " "no código não quebrem coisas inesperadamente. Também pode ajudar a manter " @@ -3816,12 +3854,12 @@ msgstr "Há alguns casos de uso a considerar:" #: ../../tutorials/intro.md:242 msgid "" -"**Creating a basic package for yourself:** Sometimes you want create " -"apackage for your own personal use. This might mean making your code " -"locally pip installable and you may also want to publish it to GitHub.In " -"that case you don't expect others to use your code, and as such youmay only " -"have documentation for you and your future self if you need to update the " -"package." +"**Creating a basic package for yourself:** Sometimes you want create a " +"package for your own personal use. This might mean making your code " +"locally pip installable and you may also want to publish it to GitHub. In" +" that case you don't expect others to use your code, and as such you may " +"only have documentation for you and your future self if you need to " +"update the package." msgstr "" "**Criar um pacote básico para você mesmo:** Às vezes você quer criar um " "pacote para uso pessoal. Isso pode significar tornar seu código instalável " @@ -3833,8 +3871,8 @@ msgstr "" #: ../../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 beuseful to " -"have those functions available to all of your projects." +"write that are useful across several of your projects. It could be useful" +" to have those functions available to all of your projects." msgstr "" "Um exemplo desse tipo de pacote pode ser um conjunto de funções que você " "escreveu e que são úteis em vários dos seus projetos. Pode ser útil ter " @@ -3849,14 +3887,14 @@ msgstr "" #: ../../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 " -"to other people as well. In that case, you might consider both creating the " -"package, publishing it on GitHub, and because other users may be using it, " -"you may make use of GitHub's infrastructure including CI/CD pipelines and " -"issue trackers. Because you want other people to use your package, you will " -"want to also include LICENSE information, documentation for users and " -"contributors and tests. This type of package is most often published to " -"PyPI." +"some code that you soon realize might also be useful to not just you, but" +" to other people as well. In that case, you might consider both creating " +"the package, publishing it on GitHub, and because other users may be " +"using it, you may make use of GitHub's infrastructure including CI/CD " +"pipelines and issue trackers. Because you want other people to use your " +"package, you will want to also include LICENSE information, documentation" +" for users and contributors and tests. This type of package is most often" +" published to PyPI." msgstr "" "**Criar um pacote para a comunidade:** Em outros casos, você pode criar " "código que logo percebe ser útil não só para você, mas também para outras " @@ -3869,9 +3907,9 @@ msgstr "" #: ../../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 just the maintainers." +"For example, all of the [pyOpenSci packages](https://www.pyopensci.org" +"/python-packages.html) are public facing with an intended audience beyond" +" just the maintainers." msgstr "" "Por exemplo, todos os [pacotes da " "pyOpenSci](https://www.pyopensci.org/python-packages.html) são voltados " @@ -3885,8 +3923,8 @@ msgstr "" #: ../../tutorials/intro.md:257 msgid "" -"Ideally the code in your Python package is focused on a specific themeor " -"use case. This theme is important as it's a way to scope the content of " +"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 " "your package." msgstr "" "Idealmente, o código do seu pacote Python está focado em um tema ou caso de " @@ -3895,10 +3933,11 @@ msgstr "" #: ../../tutorials/intro.md:259 msgid "" -"It can be tricky to decide when your code becomes something that mightbe " -"more broadly useful to others. But one question you can ask yourself is - " -"is your code written specifically for a single research project? Or could " -"it have a broader application across multiple projects in your domain?" +"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 " +"- is your code written specifically for a single research project? Or " +"could it have a broader application across multiple projects in your " +"domain?" msgstr "" "Pode ser difícil decidir quando seu código se torna algo que pode ser mais " "amplamente útil para outras pessoas. Mas uma pergunta que você pode fazer " @@ -3912,12 +3951,11 @@ msgstr "Como isso se relaciona com código de um projeto de pesquisa?" #: ../../tutorials/intro.md:264 msgid "" -"A [Research " -"Compendium](https://book.the-turing-way.org/reproducible-research/compendia." -"html)isanorganizedsetofcode,dataanddocumentation that supports a " -"specificresearch project.It aims to enhance the reproducibility and " -"transparency of research byproviding acomprehensive record of the methods, " -"data, andanalyses used in a study." +"A [Research Compendium](https://book.the-turing-way.org/reproducible-" +"research/compendia.html) is an organized set of code, data and " +"documentation that supports a specific research project. It aims to " +"enhance the reproducibility and transparency of research by providing a " +"comprehensive record of the methods, data, and analyses used in a study." msgstr "" "Um [Research " "Compendium](https://book.the-turing-way.org/reproducible-research/compendia." @@ -3928,10 +3966,10 @@ msgstr "" #: ../../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 " -"workflows. As such a Python package is more generalizable than a Research " -"Compendium which supports a specific project." +"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 " +"workflows. As such a Python package is more generalizable than a Research" +" Compendium which supports a specific project." msgstr "" "Um pacote Python é uma coleção de modules que podem ser usados para " "executar um conjunto específico de tarefas. Essas tarefas devem ser " @@ -3942,8 +3980,7 @@ msgstr "" #: ../../tutorials/intro.md:274 msgid "" "[Read about `Good enough practices in scientific " -"computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journa" -"l.pcbi.1005510)" +"computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005510)" msgstr "" "[Leia sobre `Good enough practices in scientific " "computing`](https://journals.plos.org/ploscompbiol/article?id=10.1371/journa" @@ -3951,9 +3988,9 @@ msgstr "" #: ../../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-future-sel" -"f/)" +"[Learn more about research compendia (also called repo-packs) in this " +"blog post.](https://lorenabarba.com/blog/how-repro-packs-can-save-your-" +"future-self/)" msgstr "" "[Saiba mais sobre research compendia (também chamados de repo-packs) neste " "post de " @@ -3968,9 +4005,9 @@ msgstr "" #: ../../tutorials/intro.md:280 msgid "" -"[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): is a " -"packagedesigned to work with annotating animal vocalizations and " -"bioacousticsdata. This package helps scientists process different types of " +"[Crowsetta](https://crowsetta.readthedocs.io/en/latest/): is a package " +"designed to work with annotating animal vocalizations and bioacoustics " +"data. This package helps scientists process different types of " "bioacoustic data rather than focusing on a specific individual research " "application associated with a user-specific research workflow." msgstr "" @@ -3982,9 +4019,9 @@ msgstr "" #: ../../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 research " -"application." +"[Pandera](https://www.union.ai/pandera) is another more broadly used " +"Python package. Pandera supports data testing and thus also has a broader" +" research application." msgstr "" "[Pandera](https://www.union.ai/pandera) é outro pacote Python de uso mais " "amplo. Pandera suporta testes de dados e, portanto, também tem aplicação de " @@ -3994,13 +4031,10 @@ msgstr "" msgid "Matplotlib as an example" msgstr "Matplotlib como exemplo" - - - #: ../../tutorials/intro.md:285 msgid "" -"At the larger end of the user spectrum, Matplotlib is a great " -"example.Matplotlib does one thing really well:" +"At the larger end of the user spectrum, Matplotlib is a great example. " +"Matplotlib does one thing really well:" msgstr "" "No extremo maior do espectro de usuários, Matplotlib é um ótimo exemplo. " "Matplotlib faz uma coisa muito bem:" @@ -4011,10 +4045,10 @@ msgstr "_Ele cria gráficos visuais de dados._" #: ../../tutorials/intro.md:290 msgid "" -"Thousands of people use Matplotlib for different plotting applicationsusing " -"different types of data. While few scientific packages will havethe same " -"broad application and large user base that Matplotlib has, the idea of " -"scoping out what your package does is still important." +"Thousands of people use Matplotlib for different plotting applications " +"using different types of data. While few scientific packages will have " +"the same broad application and large user base that Matplotlib has, the " +"idea of scoping out what your package does is still important." msgstr "" "Milhares de pessoas usam Matplotlib para diferentes aplicações de plotagem " "com diferentes tipos de dados. Embora poucos pacotes científicos tenham a " @@ -4043,10 +4077,11 @@ msgstr "" #: ../../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 ensure " -"this consistency throughout your entire package. [Learn more about code " -"formatters here.](../package-structure-code/code-style-linting-format)" +"**Readable code:** readable code is code written with a consistent style." +" You can use linters and code formatters such as black and flake8 to " +"ensure this consistency throughout your entire package. [Learn more about" +" code formatters here.](../package-structure-code/code-style-linting-" +"format)" msgstr "" "**Readable code:** Readable code é código escrito com um estilo " "consistente. Você pode usar linters e formatadores de código como black e " @@ -4056,12 +4091,11 @@ msgstr "" #: ../../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 do and " -"also what the input and output elements of each function are. [You can " -"learn more about docstrings in our guide, " -"here.](../documentation/write-user-documentation/document-your-code-api-docs" -"trings)" +"**Documented code:** documented code is written using docstrings that " +"help a user understand both what the functions and methods in your code " +"do and also what the input and output elements of each function are. [You" +" can learn more about docstrings in our guide, here.](../documentation" +"/write-user-documentation/document-your-code-api-docstrings)" msgstr "" "**Documented code:** Documented code é escrito usando docstrings que ajudam " "o usuário a entender tanto o que as funções e methods do seu código fazem " @@ -4080,9 +4114,9 @@ msgstr "Pacotes Python e ambientes" #: ../../tutorials/intro.md:316 msgid "" -"You can install a Python package into a Python environment in the sameway " -"you might install NumPy or Pandas. Installing your package into " -"anenvironment allows you to access it from any code run with thatspecific " +"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 " +"environment allows you to access it from any code run with that specific " "Python environment activated." msgstr "" "Você pode instalar um pacote Python em um ambiente Python da mesma forma " @@ -4094,10 +4128,10 @@ msgstr "" 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 " -"install package. The second arrow leads to a box that represents aPython " -"environment that already has some packages installed such as Pandas and " -"NumPy. Your package will also get installed into that same environment when " -"you pip install it." +"install package. The second arrow leads to a box that represents a Python" +" environment that already has some packages installed such as Pandas and " +"NumPy. Your package will also get installed into that same environment " +"when you pip install it." msgstr "" "Diagrama mostrando as etapas associadas à criação de um pacote e depois à " "sua instalação. A primeira seta diz seu pacote e a segunda diz pip install " @@ -4107,11 +4141,11 @@ msgstr "" #: ../../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 " -"codeinstallable locally on your computer and use it for projects that you " -"are working on without having to ever publish to PyPI. Publishing to PyPI " -"is useful when you want to make your code public-facing and shareit with " +"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 " +"installable locally on your computer and use it for projects that you are" +" working on without having to ever publish to PyPI. Publishing to PyPI is" +" useful when you want to make your code public-facing and share it with " "others." msgstr "" "Você não precisa publicar no PyPI para tornar seu código instalável. Com a " @@ -4128,8 +4162,8 @@ msgstr "Publicar um pacote no PyPI / Conda-Forge" #: ../../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 publishit in a " -"repository such as **PyPI** or **conda-forge**." +"download the code to your computer locally then you need to publish it in" +" a repository such as **PyPI** or **conda-forge**." msgstr "" "Se você quer tornar seu pacote diretamente instalável sem precisar baixar o " "código para o seu computador localmente, precisa publicá-lo em um " @@ -4137,15 +4171,15 @@ msgstr "" #: ../../tutorials/intro.md:337 msgid "" -"Learn [how to publish your package to PyPI in this " -"tutorial.](publish-pypi.md)" +"Learn [how to publish your package to PyPI in this tutorial.](publish-" +"pypi.md)" msgstr "Aprenda [como publicar seu pacote no PyPI neste tutorial.](publish-pypi.md)" #: ../../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 " -"this recipe to conda-forge." +"[Grayskull](https://github.com/conda/grayskull) tool. You can then submit" +" this recipe to conda-forge." msgstr "" "Depois você pode criar uma recipe do conda-forge usando a ferramenta " "[Grayskull](https://github.com/conda/grayskull). Em seguida, envie essa " @@ -4153,22 +4187,22 @@ msgstr "" #: ../../tutorials/intro.md:341 msgid "" -"[You will learn more about the conda-forge publication process " -"here.](publish-conda-forge.md)" +"[You will learn more about the conda-forge publication process here" +".](publish-conda-forge.md)" msgstr "" "[Você aprenderá mais sobre o processo de publicação no conda-forge " "aqui.](publish-conda-forge.md)" #: ../../tutorials/intro.md:344 msgid "" -"Graphic showing the high level packaging workflow. On the left you seea " -"graphic with code, metadata and tests in it. Those items all go intoyour " -"package. Documentation and data are below that box because they aren't " +"Graphic showing the high level packaging workflow. On the left you see a " +"graphic with code, metadata and tests in it. Those items all go into your" +" package. Documentation and data are below that box because they aren't " "normally published in your packaging wheel distribution. An arrow to the " "right takes you to a build distribution files box. That box leads you to " "either publishing to TestPyPI or the real PyPI. From PyPI you can then " -"connect to conda-forge for an automated build that sends distributions from " -"PyPI to conda-forge." +"connect to conda-forge for an automated build that sends distributions " +"from PyPI to conda-forge." msgstr "" "Gráfico mostrando o workflow de alto nível de empacotamento. À esquerda " "você vê um gráfico com código, metadata e testes. Esses itens entram no seu " @@ -4181,14 +4215,14 @@ msgstr "" #: ../../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-distribution) and [wheel](#python-wheel) files.Once " -"you are ready to make your code publicly installable, you can publish it on " -"PyPI. Once your code is on PyPI it is straight forward to then publish to " -"conda-forge. You create a recipe using the Grayskull package and then you " -"open a pr in the conda-forge recipe repository. You will learn more about " -"this process in the [conda-forgelesson](/tutorials/publish-conda-forge)." +"In the image above, you can see the steps associated with publishing your" +" package on PyPI and conda-forge. PyPI supports [sdist](#python-source-" +"distribution) and [wheel](#python-wheel) files. Once you are ready to " +"make your code publicly installable, you can publish it on PyPI. Once " +"your code is on PyPI it is straight forward to then publish to conda-" +"forge. You create a recipe using the Grayskull package and then you open " +"a pr in the conda-forge recipe repository. You will learn more about this" +" process in the [conda-forge lesson](/tutorials/publish-conda-forge)." msgstr "" "Na imagem acima, você pode ver as etapas associadas à publicação do seu " "pacote no PyPI e conda-forge. O PyPI suporta arquivos " @@ -4208,9 +4242,10 @@ msgstr "Ótimo, seu pacote tem usuários! E agora?" msgid "" "As the community using your package grows, you may also find yourself " "managing users, contributors, and others who want to interact with your " -"package. It’s important to consider all this before you dive into " -"development. Once you have a user base in the community, people will depend " -"upon your code to work and will need direction regarding how to use it." +"package. It’s important to consider all this before you dive into " +"development. Once you have a user base in the community, people will " +"depend upon your code to work and will need direction regarding how to " +"use it." msgstr "" "À medida que a comunidade que usa seu pacote cresce, você também pode se ver " "gerenciando usuários, contributors e outras pessoas que querem interagir " @@ -4241,9 +4276,9 @@ msgstr "" #: ../../tutorials/intro.md:358 msgid "" -"[a contributing guide that helps users understand expectations associated " -"with making contributions to your " -"project](/documentation/repository-files/contributing-file.md)" +"[a contributing guide that helps users understand expectations associated" +" with making contributions to your project](/documentation/repository-" +"files/contributing-file.md)" msgstr "" "[um guia de contribuição que ajuda usuários a entender expectativas " "associadas a contribuições ao seu " @@ -4255,10 +4290,10 @@ msgstr "Suporte para contributors e mantenedores" #: ../../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 " +"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 " "development** guide to help new potential contributors get started with " -"contributing to your package, as well as a **code of conduct** toensure " +"contributing to your package, as well as a **code of conduct** to ensure " "community interactions remain healthy both for you and your contributors " "and maintainer team." msgstr "" @@ -4273,8 +4308,8 @@ msgstr "" 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 " -"want extra help, development, and contributing documentation will help you " -"onboard new maintainers." +"want extra help, development, and contributing documentation will help " +"you onboard new maintainers." msgstr "" "Os elementos acima também são importantes para a manutenção futura do seu " "pacote. Caso você não consiga mais mantê-lo ou simplesmente queira ajuda " @@ -4288,10 +4323,10 @@ msgstr "Próximos passos" #: ../../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 for " -"others to contribute to and easier for other scientists to use. However, " -"first we want to get you to your initial goal of publishing a Python " -"package." +"published Python package that makes it both easier to maintain, easier " +"for others to contribute to and easier for other scientists to use. " +"However, first we want to get you to your initial goal of publishing a " +"Python package." msgstr "" "Em lições futuras você aprenderá mais sobre a infraestrutura em torno de um " "pacote Python publicado que facilita a manutenção, a contribuição de outras " @@ -4300,8 +4335,8 @@ msgstr "" #: ../../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 " +"In this next lesson you will learn how to create a basic installable " +"Python package. Make your code pip installable " msgstr "" "Nessa próxima lição você aprenderá como criar um pacote Python básico " "instalável. Torne seu código pip instalável " @@ -4316,9 +4351,8 @@ msgstr "Nas lições anteriores, você aprendeu:" #: ../../tutorials/publish-conda-forge.md:10 msgid "" -"How to [create the most basic version of a Python " -"package](create-python-package.md). This entailed making your code " -"installable." +"How to [create the most basic version of a Python package](create-python-" +"package.md). This entailed making your code installable." msgstr "" "Como [criar a versão mais básica de um pacote " "Python](create-python-package.md). Isso envolveu tornar seu código " @@ -4335,8 +4369,8 @@ msgstr "Como adicionar arquivos `README` e `LICENSE` ao seu pacote" #: ../../tutorials/publish-conda-forge.md:13 msgid "" "How to setup your [pyproject.toml](pyproject-toml) file with all of the " -"metadata that PyPI requires and also metadata that will be helpfulfor users " -"to find your package." +"metadata that PyPI requires and also metadata that will be helpful for " +"users to find your package." msgstr "" "Como configurar seu arquivo [pyproject.toml](pyproject-toml) com toda a " "metadata exigida pelo PyPI e também metadata que ajudará usuários a " @@ -4352,9 +4386,9 @@ msgstr "" #: ../../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 pypi.org that you plan to maintain." +"**IMPORTANT:** Please do not practice publishing your package to conda-" +"forge. You should only publish to conda-forge when you have a package on " +"pypi.org that you plan to maintain." msgstr "" "**IMPORTANTE:** Por favor, não pratique publicar seu pacote no conda-forge. " "Você só deve publicar no conda-forge quando tiver um pacote no pypi.org que " @@ -4370,16 +4404,16 @@ msgstr "Criar uma recipe YAML do conda-forge para seu pacote usando Grayskull" #: ../../tutorials/publish-conda-forge.md:29 msgid "" -"Submit the recipe (yaml file) to the conda-forge staged recipes repository " -"as a pull request" +"Submit the recipe (yaml file) to the conda-forge staged recipes " +"repository as a pull request" msgstr "" "Enviar a recipe (arquivo YAML) para o repositório staged recipes do " "conda-forge como pull request" #: ../../tutorials/publish-conda-forge.md:30 msgid "" -"Maintain your conda-forge package by creating new releases for your package " -"on PyPI" +"Maintain your conda-forge package by creating new releases for your " +"package on PyPI" msgstr "" "Manter seu pacote no conda-forge criando novos releases para seu pacote no " "PyPI" @@ -4387,10 +4421,10 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:33 #, 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 {term}`Source distribution (sdist)` file." +"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 {term}`Source distribution (sdist)` file." msgstr "" "Depois que seu pacote estiver no PyPI, você pode publicá-lo facilmente no " "conda-forge usando a ferramenta " @@ -4401,11 +4435,12 @@ msgstr "" #: ../../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 andturn it into " -"distribution files (sdist and wheel) that PyPI accepts. Then there is an " -"arrow towards the PyPI repository where ou publish both distributions. From " -"PyPI if you create a conda-forge recipe you can then publish to conda-forge." +"Image showing the progression of creating a Python package, building it " +"and then publishing to PyPI and conda-forge. You take your code and turn " +"it into distribution files (sdist and wheel) that PyPI accepts. Then " +"there is an arrow towards the PyPI repository where ou publish both " +"distributions. From PyPI if you create a conda-forge recipe you can then " +"publish to conda-forge." msgstr "" "Imagem mostrando a progressão de criar um pacote Python, fazer build " "e publicar no PyPI e conda-forge. Você pega seu código e o transforma " @@ -4418,10 +4453,10 @@ msgstr "" #, python-brace-format msgid "" "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." +"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 "" "Depois que você publicou ambas as distribuições do pacote (a " "{term}`distribuição fonte (sdist) ` e a " @@ -4436,8 +4471,8 @@ msgstr "O que é conda-forge?" #: ../../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." +"conda is an open source package and environment management tool that can " +"be used to install tools from the different channels on Anaconda.org." msgstr "" "conda é uma ferramenta open source de gerenciamento de pacotes e ambientes " "que pode ser usada para instalar ferramentas de diferentes channels no " @@ -4447,13 +4482,14 @@ msgstr "" 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 " -"`conda install packagename`. In the case of conda channels, some of these " -"channels such as the `defaults` channel, is managed by Anaconda (the " -"company). Only Anaconda can decide what packages are available inthe " +"`conda install packagename`. In the case of conda channels, some of these" +" channels such as the `defaults` channel, is managed by Anaconda (the " +"company). Only Anaconda can decide what packages are available in the " "`defaults` channel. However, the conda-forge (and bioconda) channel are " -"community-managed channels. Anyone can submit a package tothese channels " -"however they must pass a technical review in the [staged-recipes GitHub " -"repository](https://github.com/conda-forge/staged-recipes) to be published." +"community-managed channels. Anyone can submit a package to these channels" +" however they must pass a technical review in the [staged-recipes GitHub " +"repository](https://github.com/conda-forge/staged-recipes) to be " +"published." msgstr "" "Você pode pensar em um channel como um local específico onde um grupo de " "pacotes é armazenado e pode ser instalado usando um comando como `conda " @@ -4472,14 +4508,14 @@ msgstr "[Saiba mais sobre conda channels aqui.](#about-conda)" #: ../../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 hosted on a " -"conda channel can be installed using conda install. Below that there are " -"two rows. The top row says conda channels. Next to it are three boxes one " -"with conda-forge, community maintained; bioconda and then default - managed " -"by the Anaconda team. Below that there is arow that says PyPI servers. PyPI " -"- anyone can publish to PyPI and testPyPI (a testbed server for you to " -"practice)." +"Graphic with the title Python package repositories. Below it says " +"anything hosted on PyPI can be installed using pip install. Packaging " +"hosted on a conda channel can be installed using conda install. Below " +"that there are two rows. The top row says conda channels. Next to it are " +"three boxes one with conda-forge, community maintained; bioconda and then" +" default - managed by the Anaconda team. Below that there is a row that " +"says PyPI servers. PyPI - anyone can publish to PyPI and test PyPI (a " +"testbed server for you to practice)." msgstr "" "Gráfico com o título Repositórios de pacote Pythons. Abaixo diz que " "qualquer coisa hospedada no PyPI pode ser instalada usando pip install. " @@ -4492,11 +4528,11 @@ msgstr "" #: ../../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 cansubmit a " -"recipe there. PyPI is also a community maintained repository.Anyone can " -"submit a package to PyPI and test PyPI. Unlike conda-forge there are no " -"manual checks of packages submitted to PyPI." +"Conda channels represent various repositories that you can install " +"packages from. Because conda-forge is community maintained, anyone can " +"submit a recipe there. PyPI is also a community maintained repository. " +"Anyone can submit a package to PyPI and test PyPI. Unlike conda-forge " +"there are no manual checks of packages submitted to PyPI." msgstr "" "Conda channels representam vários repositórios de onde você pode instalar " "pacotes. Como o conda-forge é mantido pela comunidade, qualquer pessoa pode " @@ -4512,11 +4548,11 @@ msgstr "Por que publicar no conda-forge" #: ../../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, having " -"packages available to these users on the conda-forge channel is useful. In " -"some cases packages on conda-forge can minimize dependency conflicts that " -"can occur when mixing installations using pip and conda. This is " -"particularly important for the spatial ecosystem." +"use conda as their primary package manager / environment tool. Thus, " +"having packages available to these users on the conda-forge channel is " +"useful. In some cases packages on conda-forge can minimize dependency " +"conflicts that can occur when mixing installations using pip and conda. " +"This is particularly important for the spatial ecosystem." msgstr "" "Existem muitos usuários, especialmente no ecossistema científico Python, " "que usam conda como seu gerenciador de pacotes / ferramenta deambientes " @@ -4531,9 +4567,9 @@ msgstr "Como funciona a publicação no conda-forge" #: ../../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 additional build step " -"needed to publish to conda-forge." +"Once you have built and published your package to PyPI, you have " +"everything that you need to publish to conda-forge. There is no " +"additional build step needed to publish to conda-forge." msgstr "" "Depois de fazer o build e publicar seu pacote no PyPI, você tem tudo o que " "precisa para publicar no conda-forge. Não há etapa adicional de build " @@ -4541,9 +4577,9 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:75 msgid "" -"Conda-forge will build your package from the source distribution whichyou " -"[published to PyPI in the previous lesson](publish-pypi) using therecipe " -"that you will create below." +"Conda-forge will build your package from the source distribution which " +"you [published to PyPI in the previous lesson](publish-pypi) using the " +"recipe that you will create below." msgstr "" "O conda-forge fará o build do seu pacote a partir da source distribution " "que você [publicou no PyPI na lição anterior](publish-pypi), usando a " @@ -4563,11 +4599,11 @@ msgstr "" #: ../../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 yaml " -"file recipe that can be submitted to the conda-forge staged recipes " -"repository for review. Once that recipe is accepted, your package will get " -"it's on repository (known as a feedstock) on conda-forge." +"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 " +"yaml file recipe that can be submitted to the conda-forge staged recipes " +"repository for review. Once that recipe is accepted, your package will " +"get it's on repository (known as a feedstock) on conda-forge." msgstr "" "As etapas para publicar no conda-forge começam com a publicação do " "seu pacote Python no PyPI. Depois de publicar no PyPI, você pode criar " @@ -4588,9 +4624,9 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:88 msgid "" -"Create a conda-forge recipe, which is a yaml file with instructions onhow " -"to build your package on conda-forge, using the grayskull[^grayskull] " -"package." +"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]" +" package." msgstr "" "Crie uma recipe conda-forge, que é um arquivo yaml com instruções sobre " "como fazer o build do seu pacote no conda-forge, usando o " @@ -4598,9 +4634,10 @@ msgstr "" #: ../../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 submission from " -"pyOpenSci.](https://github.com/conda-forge/staged-recipes/pull/25173)" +"Submit the recipe (yaml file) to the conda-forge staged recipes " +"repository as a pull request for review. [Click here for an example " +"submission from pyOpenSci.](https://github.com/conda-forge/staged-" +"recipes/pull/25173)" msgstr "" "Submeta a recipe (arquivo yaml) ao repositório staged recipes do " "conda-forge como um pull request para revisão. [Clique aqui para ver um " @@ -4609,9 +4646,9 @@ msgstr "" #: ../../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 and " -"merged." +"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 " +"and merged." msgstr "" "Depois que alguém da equipe conda-forge revisar seu pull request, você pode " "precisar fazer algumas alterações. Eventualmente o pull request será " @@ -4619,8 +4656,8 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:93 msgid "" -"Once your recipe is accepted and merged on conda-forge, users can install " -"your package using:" +"Once your recipe is accepted and merged on conda-forge, users can install" +" your package using:" msgstr "" "Depois que sua recipe for aceita e merged no conda-forge, os usuários " "poderão instalar seu pacote usando:" @@ -4643,10 +4680,10 @@ msgstr "Mantendo um pacote conda-forge" #: ../../tutorials/publish-conda-forge.md:101 msgid "" -"Once your package is on conda-forge, the repository will track " -"releaseactivity on the package's PyPI repository. Any time you make a new " -"PyPI release with a new source distribution, conda-forge will build and " -"update your conda-forge repository (also known as a feedstock)." +"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 " +"release with a new source distribution, conda-forge will build and update" +" your conda-forge repository (also known as a feedstock)." msgstr "" "Depois que seu pacote estiver no conda-forge, o repositório acompanhará a " "atividade de release no repositório PyPI do pacote. Sempre que você fizer " @@ -4656,8 +4693,8 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:103 msgid "" -"When the update is processed, the friendly conda-forge bot will createa new " -"pull request with an updated distribution recipe in your feedstock." +"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 "" "Quando a atualização for processada, o amigável bot conda-forge criará um " "novo pull request com uma recipe de distribuição atualizada no seu " @@ -4673,8 +4710,8 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:107 msgid "" -" How to Publish your package on " -"conda-forge" +" How to Publish your package" +" on conda-forge" msgstr "" " Como publicar seu pacote no " "conda-forge" @@ -4682,8 +4719,8 @@ msgstr "" #: ../../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 also " -"remember that the team managing conda-forge are all volunteers." +"your package needs to be on PyPI before the steps below will work. And " +"also remember that the team managing conda-forge are all volunteers." msgstr "" "É hora de adicionar seu pacote ao channel conda-forge. Lembre-se de que seu " "pacote precisa estar no PyPI antes que as etapas abaixo funcionem. E " @@ -4700,16 +4737,16 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:115 msgid "" -"Only submit your package to conda-forge if you intend to maintain it over " -"time." +"Only submit your package to conda-forge if you intend to maintain it over" +" time." msgstr "" "Submeta seu pacote ao conda-forge somente se você pretende mantê-lo ao longo " "do tempo." #: ../../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 " +"Note - this is a tutorial aimed to help you get your package onto conda-" +"forge. The official conda documentation for this processed [is " "here](https://conda-forge.org/docs/maintainer/adding_pkgs.html)." msgstr "" "Nota: este é um tutorial destinado a ajudá-lo a colocar seu pacote " @@ -4723,8 +4760,8 @@ msgstr "Etapa 1: Instalar grayskull" #: ../../tutorials/publish-conda-forge.md:122 msgid "" "First, [install " -"grayskull](https://conda.github.io/grayskull/user_guide.html). You " -"caninstall it using either pip:" +"grayskull](https://conda.github.io/grayskull/user_guide.html). You can " +"install it using either pip:" msgstr "" "Primeiro, [instale o " "grayskull](https://conda.github.io/grayskull/user_guide.html). Você pode " @@ -4736,8 +4773,8 @@ msgstr "ou conda" #: ../../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." +"To run this command, use the same shell / terminal that you have been " +"using to run hatch commands in the previous tutorials." msgstr "" "Para executar este comando, use o mesmo shell / terminal que você usou para " "executar comandos hatch nos tutoriais anteriores." @@ -4810,8 +4847,8 @@ msgstr "Em seguida, navegue até o diretório recipes" #: ../../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." +"If you run `ls` here, you will notice there is an example directory with " +"an example recipe for you to look at." msgstr "" "Se você executar `ls` aqui, notará que há um diretório de exemplo com uma " "recipe de exemplo para você consultar." @@ -4824,16 +4861,16 @@ msgstr "" #: ../../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." +"Grayskull will pull metadata about your package from PyPI. It does not " +"use your local installation of the package." msgstr "" "O Grayskull buscará metadata sobre seu pacote no PyPI. Ele não usa " "sua instalação local do pacote." #: ../../tutorials/publish-conda-forge.md:230 msgid "" -"An internet connection is needed to run the `grayskull pypi " -"your-package-name` step." +"An internet connection is needed to run the `grayskull pypi your-package-" +"name` step." msgstr "" "Uma conexão com a internet é necessária para executar a etapa `grayskull " "pypi your-package-name`." @@ -4860,8 +4897,8 @@ msgstr "`recipes/packagename/meta.yaml`" #: ../../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." +"At the very bottom of the grayskull output, it will also tell you where " +"it saved the recipe file." msgstr "" "Na parte inferior da saída do grayskull, ele também informará onde salvou o " "arquivo de recipe." @@ -4880,11 +4917,11 @@ msgstr "Etapa 3b: Correção de bug — adicionar uma home url à seção about" #: ../../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 receive " -"an error " -"message](https://github.com/conda-forge/staged-recipes/pull/25173#issuecomme" -"nt-1917916528)fromthefriendlyconda-forgelinterbot." +"There is currently a small bug in Grayskull where it doesn't populate the" +" home: element of the recipe. If you don't include this, [you will " +"receive an error message](https://github.com/conda-forge/staged-" +"recipes/pull/25173#issuecomment-1917916528) from the friendly conda-forge" +" linter bot." msgstr "" "Atualmente há um pequeno bug no Grayskull em que ele não preenche o " "elemento home: da recipe. Se você não incluir isso, [receberá uma mensagem " @@ -4922,8 +4959,8 @@ msgstr "Etapa 4: testes para conda-forge" #: ../../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 with " -"your package and run `pip check`." +"minimum you should import your package or the main modules associated " +"with your package and run `pip check`." msgstr "" "Em seguida, dê uma olhada na seção tests do seu arquivo **meta.yaml**. No " "mínimo, você deve importar seu pacote ou os principais modules associados " @@ -4931,16 +4968,16 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:333 msgid "" -"`pip check` will ensure that your package installs properly with all of the " -"proper dependencies." +"`pip check` will ensure that your package installs properly with all of " +"the proper dependencies." msgstr "" "`pip check` garantirá que seu pacote seja instalado corretamente com todas " "as dependências adequadas." #: ../../tutorials/publish-conda-forge.md:345 msgid "" -"If you have more advanced tests that you wish to run, you can add themhere. " -"However, you can also simply leave the tests section as it is." +"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 "" "Se você tiver testes mais avançados que deseja executar, pode adicioná-los " "aqui. No entanto, você também pode simplesmente deixar a seção tests como " @@ -4952,8 +4989,8 @@ msgstr "Etapa 4: Submeter um pull request ao repositório staged-recipes" #: ../../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`." +"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 "" "Depois de concluir tudo acima, você está pronto para abrir um pull request " "no repositório `conda-forge/staged-recipes`." @@ -4984,8 +5021,8 @@ msgstr "Checklist de pull request do Staged-recipes conda-forge" #: ../../tutorials/publish-conda-forge.md:360 msgid "" -"When you submit your package to conda-forge, the pull request " -"templateincludes a list of checks that you want to ensure you have covered." +"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 "" "Quando você submete seu pacote ao conda-forge, o template de pull request " "inclui uma lista de verificações que você deve garantir ter coberto." @@ -5000,8 +5037,8 @@ msgstr "Dicas do checklist do template de pull request" #: ../../tutorials/publish-conda-forge.md:367 msgid "" -"-[x] Title of this PR is meaningful: e.g. \"Adding my_nifty_package\",not " -"\"updated meta.yaml\"." +"-[x] Title of this PR is meaningful: e.g. \"Adding my_nifty_package\", " +"not \"updated meta.yaml\"." msgstr "" "-[x] O título deste PR é significativo: por exemplo, \"Adding " "my_nifty_package\", não \"updated meta.yaml\"." @@ -5016,9 +5053,10 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:372 msgid "" -"-[x] License file is packaged (see " -"[here](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169" -"089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73)foranexample)." +"-[x] License file is packaged (see [here](https://github.com/conda-forge" +"/staged-" +"recipes/blob/5eddbd7fc9d1502169089da06c3688d9759be978/recipes/example/meta.yaml#L64-L73)" +" for an example)." msgstr "" "-[x] O arquivo LICENSE está incluído no pacote (veja " "[aqui](https://github.com/conda-forge/staged-recipes/blob/5eddbd7fc9d1502169" @@ -5026,12 +5064,12 @@ msgstr "" #: ../../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 tutorials then you " -"already have a LICENSE file and are likely using the MIT license. When you " -"run `hatch build`, it will bundle that file into the output [source " -"distribution file (which is the tar.gz file)](python-source-distribution) " -"that conda-forge will use to build your package." +"**Translation:** You should have a LICENSE file included in your " +"package's source distribution. If you have followed the pyOpenSci " +"tutorials then you already have a LICENSE file and are likely using the " +"MIT license. When you run `hatch build`, it will bundle that file into " +"the output [source distribution file (which is the tar.gz file)](python-" +"source-distribution) that conda-forge will use to build your package." msgstr "" "**Tradução:** Você deve ter um arquivo LICENSE incluído na source " "distribution do seu pacote. Se você seguiu os tutoriais do pyOpenSci, já tem " @@ -5046,10 +5084,10 @@ msgstr "[x] A source é de uma fonte oficial." #: ../../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) thenyou are in good " -"shape. conda-forge prefers that your distribution is published to a known " -"repository." +"**Translation:** If your package is on PyPI as you learned in the " +"[previous lesson on publishing your Python package](publish-pypi) then " +"you are in good shape. conda-forge prefers that your distribution is " +"published to a known repository." msgstr "" "**Tradução:** Se seu pacote está no PyPI, como você aprendeu na " "[lição anterior sobre publicar seu pacote Python](publish-pypi), você está " @@ -5058,9 +5096,9 @@ msgstr "" #: ../../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 licenses of all " -"packages need to be packaged)." +"-[x] Package does not vendor other packages. (If a package uses the " +"source of another package, they should be separate packages or the " +"licenses of all packages need to be packaged)." msgstr "" "-[x] O pacote não inclui (vendor) outros pacotes. (Se um pacote usa o source " "de outro pacote, eles devem ser pacotes separados ou as licenças de todos " @@ -5069,10 +5107,10 @@ msgstr "" #: ../../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 taken " -"from other packages then you may need to declare that and include licenses " -"for that code if it is different. If you followed these tutorials then you " -"do not have any vendored code." +"shares the same LICENSE then you are in good shape. If you have code " +"taken from other packages then you may need to declare that and include " +"licenses for that code if it is different. If you followed these " +"tutorials then you do not have any vendored code." msgstr "" "**Tradução:** Se a base de código do seu pacote é sua e tudo compartilha a " "mesma LICENSE, você está em boa forma. Se você tem código retirado de " @@ -5082,8 +5120,8 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:384 msgid "" -"-[x] If static libraries are linked in, the license of the static library " -"is packaged." +"-[x] If static libraries are linked in, the license of the static library" +" is packaged." msgstr "" "-[x] Se bibliotecas estáticas forem linkadas, a licença da biblioteca " "estática está incluída no pacote." @@ -5091,8 +5129,8 @@ msgstr "" #: ../../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-forge/cfep/blob/main/cfep-18.md)." +"needed, [follow CFEP-18](https://github.com/conda-" +"forge/cfep/blob/main/cfep-18.md)." msgstr "" "-[x] O pacote não distribui bibliotecas estáticas. Se bibliotecas estáticas " "forem necessárias, [siga o " @@ -5100,10 +5138,10 @@ msgstr "" #: ../../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 check " -"that your package does not ship static libraries as this does not apply to " -"you." +"**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" +" check that your package does not ship static libraries as this does not " +"apply to you." msgstr "" "**Tradução:** Uma biblioteca estática refere-se a uma cópia de um pacote " "incorporada ao seu pacote. Se seu pacote é um pacote puro Python, você pode " @@ -5112,8 +5150,8 @@ msgstr "" #: ../../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) " +"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 "" "Os tutoriais do pyOpenSci são todos pure Python e, como tal, não usam " @@ -5122,9 +5160,9 @@ msgstr "" #: ../../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." +"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 "" "Se seu pacote tem um build mais complexo que inclui links para extensões " "escritas em outras linguagens, como C++, certifique-se de incluir as " @@ -5133,8 +5171,9 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:397 msgid "" "If you want to learn more about static libraries, then [this " -"overview](https://pypackaging-native.github.io/background/compilation_concep" -"ts/#shared-vs-static-libraries)mighthelp." +"overview](https://pypackaging-" +"native.github.io/background/compilation_concepts/#shared-vs-static-" +"libraries) might help." msgstr "" "Se você quiser saber mais sobre bibliotecas estáticas, [esta visão " "geral](https://pypackaging-native.github.io/background/compilation_concepts/" @@ -5146,9 +5185,9 @@ msgstr "-[ ] O build number é 0." #: ../../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 what you " -"should see in that section of your recipe." +"**Translation:** The build number in your recipe is right below the " +"source location of your package's source distribution. `number: 0` is " +"what you should see in that section of your recipe." msgstr "" "**Tradução:** O numero da sua build recipe fica logo abaixo da localização " "da source distribution do seu pacote. `number: 0` é o que você deve ver " @@ -5156,10 +5195,9 @@ msgstr "" #: ../../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-forge.org/docs/maintainer/adding_pkgs.html) for more " -"details)." +"[x] A tarball (`url`) rather than a repo (e.g. `git_url`) is used in your" +" recipe (see [here](https://conda-" +"forge.org/docs/maintainer/adding_pkgs.html) for more details)." msgstr "" "[x] Um tarball (`url`) em vez de um repo (por exemplo, `git_url`) é usado " "na sua recipe (veja " @@ -5170,9 +5208,9 @@ msgstr "" msgid "" "**Translation:** Here conda wants you to provide a link to the source " "distribution on PyPI rather than a link to your GitHub repository " -"distribution. Notice above in the Source section of your recipe there is a " -"`url:` section that provides a PyPI url that ends in tar.gz. Thatis a link " -"to your source distribution that conda-forge will use." +"distribution. Notice above in the Source section of your recipe there is " +"a `url:` section that provides a PyPI url that ends in tar.gz. That is a " +"link to your source distribution that conda-forge will use." msgstr "" "**Tradução:** Aqui o conda quer que você forneça um link para a " "source distribution no PyPI em vez de um link para a distribuição do seu " @@ -5202,8 +5240,8 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:427 msgid "" "[x] When in trouble, please check our [knowledge base " -"documentation](https://conda-forge.org/docs/maintainer/knowledge_base.html)b" -"eforepingingateam." +"documentation](https://conda-" +"forge.org/docs/maintainer/knowledge_base.html) before pinging a team." msgstr "" "[x] Em caso de problemas, consulte nossa [documentação da base de " "conhecimento](https://conda-forge.org/docs/maintainer/knowledge_base.html)an" @@ -5212,8 +5250,8 @@ msgstr "" #: ../../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 " -"firstbefore tagging one of them for help." +"supporting our community. Please try to troubleshoot on your own first " +"before tagging one of them for help." msgstr "" "**Tradução** A equipe conda são voluntários que dedicam seu tempo " "para apoiar nossa comunidade. Tente resolver por conta própria antes " @@ -5221,17 +5259,17 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:431 msgid "" -"This is also why we don't suggest you publish to conda-forge as a practice " -"run." +"This is also why we don't suggest you publish to conda-forge as a " +"practice run." msgstr "" "É por isso também que não sugerimos publicar no conda-forge como um " "exercício de prática." #: ../../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 work with " -"you to get your recipe in good shape and merged." +"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 " +"work with you to get your recipe in good shape and merged." msgstr "" "Depois de criar seu pull request, um conjunto de ações de CI será executado " "que faz o build e testa o build do seu pacote. Um maintainer do conda-forge " @@ -5239,16 +5277,16 @@ msgstr "" #: ../../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've created a pull request." +"Image showing the 5 CI tasks that will run against your package in the " +"GitHub interface after you'ce created a pull request." msgstr "" "Imagem mostrando as 5 tarefas de CI que serão executadas contra seu pacote " "na interface do GitHub depois que você criar um pull request." #: ../../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." +"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." msgstr "" "Aguarde até que todas as etapas de CI do seu pull request tenham sido " "executadas. Nesse ponto, seu pull request está pronto para revisão por um " @@ -5275,10 +5313,10 @@ msgstr "staged recipes do conda-forge e falhas de CI" #: ../../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 requirements " -"(known as noarch: Python or no architecture requirements)then the " -"conda-forge team only requires tests for Linux CI to pass." +"If your package is a pure Python package that can be installed on any " +"type of computer (Windows, mac, linux) and has no architecture " +"requirements (known as noarch: Python or no architecture requirements) " +"then the conda-forge team only requires tests for Linux CI to pass." msgstr "" "Se seu pacote é um pure pacote Python que pode ser instalado em qualquer " "tipo de computador (Windows, mac, linux) e não tem requisitosde arquitetura " @@ -5288,8 +5326,8 @@ msgstr "" #: ../../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 get " -"your package published." +"case, don't worry about failing tests, the maintainer team can help you " +"get your package published." msgstr "" "Então, se os testes para Windows e MAC OS falharem, isso é esperado. Nesse " "caso, não se preocupe com testes falhando; a equipe de maintainers pode " @@ -5297,9 +5335,9 @@ msgstr "" #: ../../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 maintainer can " -"likely help you figure things out." +"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 " +"maintainer can likely help you figure things out." msgstr "" "Depois de submeter sua recipe, você pode aguardar o build de CI passar. Se " "não estiver passando e você não souber por quê, um maintainer do " @@ -5307,8 +5345,8 @@ msgstr "" #: ../../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 " +"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 " "package](https://github.com/conda-forge/gemgis-feedstock)." msgstr "" "Depois que sua recipe for construida e merged, a equipe conda criará um novo " @@ -5317,17 +5355,17 @@ msgstr "" #: ../../tutorials/publish-conda-forge.md:460 msgid "" -" Congratulations - you have " -"added your package to conda-forge." +" Congratulations - you " +"have added your package to conda-forge." msgstr "" " Parabéns — você adicionou " "seu pacote ao conda-forge." #: ../../tutorials/publish-conda-forge.md:462 msgid "" -"The last part of this process is maintaining the repository. We cover that " -"next." +"The last part of this process is maintaining the repository. We cover " +"that next." msgstr "" "A última parte deste processo é manter o repositório. Cobrimos isso a " "seguir." @@ -5336,16 +5374,11 @@ msgstr "" msgid "Maintaining your conda-forge feedstock" msgstr "Mantendo seu feedstock conda-forge" - - - - - #: ../../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 package. This process may take a day or two to complete so be patient." +"Every time you create a new release on PyPI, the conda-forge bots will " +"recognize the release and will rebuild the newly released version of your" +" package. This process may take a day or two to complete so be patient." msgstr "" "Toda vez que você criar um novo release no PyPI, os bots do conda-forge " "reconhecerão o release e farão rebuild da versão recém-lançada do seu " @@ -5354,8 +5387,8 @@ msgstr "" #: ../../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 " +"Once the conda-forge build is complete, all of the maintainers of your " +"conda-forge feedstock will get a ping on GitHub that a new pull request " "has been opened." msgstr "" "Quando o build do conda-forge estiver concluído, todos os maintainers do " @@ -5410,9 +5443,9 @@ msgstr "Sabe como publicar seu pacote no conda-forge" #: ../../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 of " -"maintaining your package." +"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 " +"of maintaining your package." msgstr "" "Os itens acima são as etapas básicas que você precisa seguir para criar e " "publicar um pacote Python. Em uma futura série de tutoriais, cobriremos o " @@ -5451,8 +5484,8 @@ msgstr "Como tornar seu código instalável." #: ../../tutorials/publish-pypi.md:26 #, python-brace-format msgid "" -"Build your package's {term}`Source distribution (sdist)` and {term}`Wheel " -"(.whl)` {term}`Distribution files`" +"Build your package's {term}`Source distribution (sdist)` and {term}`Wheel" +" (.whl)` {term}`Distribution files`" msgstr "" "Fazer o build da {term}`distribuição fonte (sdist) ` e da {term}`Wheel(.whl)` {term}`arquivos de distribuição " @@ -5468,16 +5501,17 @@ msgstr "Publicar seu pacote no TestPyPI e no PyPI" #: ../../tutorials/publish-pypi.md:31 msgid "" -"You will do all of your development work in this lesson using " -"[Hatch](get-to-know-hatch)." +"You will do all of your development work in this lesson using [Hatch" +"](get-to-know-hatch)." msgstr "" "Você fará todo o trabalho de desenvolvimento nesta lição usando " "[Hatch](get-to-know-hatch)." #: ../../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 [Grayskull](https://conda.github.io/grayskull/)." +"Once your package is on PyPI you can publish it to conda-forge (which is " +"a channel on conda) using " +"[Grayskull](https://conda.github.io/grayskull/)." msgstr "" "Depois que seu pacote estiver no PyPI, você pode publicá-lo no conda-forge " "(que é um channel no conda) usando " @@ -5485,8 +5519,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:37 msgid "" -"You will learn how to publish to conda-forge in the [next " -"lesson](publish-conda-forge)." +"You will learn how to publish to conda-forge in the [next lesson" +"](publish-conda-forge)." msgstr "" "Você aprenderá como publicar no conda-forge na [próxima " "lição](publish-conda-forge)." @@ -5494,13 +5528,13 @@ msgstr "" #: ../../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 " -"package. An arrow to the right takes you to a build distribution files box. " -"Another arrow to the right takes you to a publish to PyPI box which has an " -"arrow containing sdist and wheel thatnotes those files go to PyPI for " -"hosting. From PyPI is an arrow containing sdist since you can then connect " -"to conda-forge for an automated build that sends distributions from PyPI to " -"conda-forge." +"graphic with code, metadata and tests in it. Those items all go into your" +" package. An arrow to the right takes you to a build distribution files " +"box. Another arrow to the right takes you to a publish to PyPI box which " +"has an arrow containing sdist and wheel that notes those files go to PyPI" +" for hosting. From PyPI is an arrow containing sdist since you can then " +"connect to conda-forge for an automated build that sends distributions " +"from PyPI to conda-forge." msgstr "" "Gráfico mostrando o workflow de alto nível de empacotamento. À esquerda " "você vê um gráfico com code, metadata e tests. Esses itens entram no seu " @@ -5551,12 +5585,12 @@ msgstr "" #: ../../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 which users " -"will get your package. IMPORTANT: Only publish your package to PyPI when " -"you are ready for it to be used by others and/or confident that it will " -"become a package that you will maintain. PyPI is not a place to practice " -"learning how to publish a Python package." +"**[PyPI](https://pypi.org):** This is the live, production PyPI " +"repository where you can officially publish your Python package, and from" +" which users will get your package. IMPORTANT: Only publish your package " +"to PyPI when you are ready for it to be used by others and/or confident " +"that it will become a package that you will maintain. PyPI is not a place" +" to practice learning how to publish a Python package." msgstr "" "**[PyPI](https://pypi.org):** Este é o repositório PyPI de produção, ao " "vivo, onde você pode publicar oficialmente seu pacote Python e de onde os " @@ -5579,9 +5613,9 @@ msgstr "4 etapas para publicar um pacote Python no TestPyPI (ou PyPI)" #: ../../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 need to " -"do to publish your Python package: to TestPyPI. You need to:" +"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" +" need to do to publish your Python package: to TestPyPI. You need to:" msgstr "" "Nesta lição você aprenderá como publicar seu pacote no TestPyPI " "usando[Hatch](https://hatch.pypa.io/latest/). Há 4 coisas que você precisa " @@ -5594,12 +5628,11 @@ msgstr "**Criar um ambiente de desenvolvimento do pacote**" #: ../../tutorials/publish-pypi.md:65 #, python-brace-format msgid "" -"[**Build your package using `hatch " -"build`**](../package-structure-code/python-package-distribution-files-sdist-" -"wheel).Building a packag 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 use {term}`pip` to install your " -"package." +"[**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 use {term}`pip` to install your package." msgstr "" "[**Fazer o build do seu pacote usando `hatch " "build`**](../package-structure-code/python-package-distribution-files-sdist-" @@ -5611,8 +5644,8 @@ msgstr "" #: ../../tutorials/publish-pypi.md:66 #, python-brace-format msgid "" -"**Create an account on TestPyPI (or PyPI)**: You will need to create " -"a TestPyPI account and associated {term}`API token` which provides " +"**Create an account on TestPyPI (or PyPI)**: You will need to create a " +"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 "" @@ -5627,9 +5660,9 @@ msgstr "**Publicar no TestPyPI usando `hatch publish`**" #: ../../tutorials/publish-pypi.md:69 msgid "" -"In a [future lesson](trusted-publishing), you will learn how to create an " -"automated GitHub Actions workflow that publishes an updated version of your " -"package to PyPI every time you create a GitHub release." +"In a [future lesson](trusted-publishing), you will learn how to create an" +" automated GitHub Actions workflow that publishes an updated version of " +"your package to PyPI every time you create a GitHub release." msgstr "" "Em uma [lição futura](trusted-publishing), você aprenderá como criar um " "workflow automatizado de GitHub Actions que publica uma versão atualizada " @@ -5641,8 +5674,8 @@ msgstr "Saiba mais sobre build de pacote Pythons no nosso guia" #: ../../tutorials/publish-pypi.md:75 msgid "" -"[Learn more about what building a Python package " -"is](../package-structure-code/python-package-distribution-files-sdist-wheel)" +"[Learn more about what building a Python package is](../package-" +"structure-code/python-package-distribution-files-sdist-wheel)" msgstr "" "[Saiba mais sobre o que é fazer build de um pacote " "Python](../package-structure-code/python-package-distribution-files-sdist-wh" @@ -5650,16 +5683,17 @@ msgstr "" #: ../../tutorials/publish-pypi.md:76 msgid "" -"[Learn more about the package distribution file that PyPI needs called the " -"wheel](#python-wheel)" +"[Learn more about the package distribution file that PyPI needs called " +"the wheel](#python-wheel)" msgstr "" "[Saiba mais sobre o arquivo de distribuição do pacote que o PyPI precisa, " "chamado wheel](#python-wheel)" #: ../../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-distribution)" +"[Learn more about the package distribution file that conda-forge will " +"need on PyPI called the sdist (source distribution)](#python-source-" +"distribution)" msgstr "" "[Saiba mais sobre o arquivo de distribuição do pacote que o conda-forge " "precisará no PyPI, chamado sdist (source " @@ -5691,9 +5725,9 @@ msgstr "" #: ../../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 environment " -"in development or editable mode." +"Then activate the environment. Note that when you call a shell from a " +"Hatch environment, it will automatically install your package into the " +"environment in development or editable mode." msgstr "" "Depois ative o ambiente. Observe que quando você chama um shell de um " "ambiente Hatch, ele instalará automaticamente seu pacote no ambiente em " @@ -5713,9 +5747,9 @@ msgstr "Hatch e ambientes" #: ../../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 tool that " -"comes with Python installations." +"Behind the scenes when hatch creates a new virtual environment, by " +"default it uses venv[^venv] which is the default environment management " +"tool that comes with Python installations." msgstr "" "Nos bastidores, quando o hatch cria um novo virtual environment, por padrão " "ele usa venv[^venv], que é a ferramenta padrão de gerenciamentode ambientes " @@ -5731,9 +5765,9 @@ msgstr "Criar um novo virtualenv (venv) localizado no seu computador." #: ../../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 " -"your project's dependencies as declared in your pyproject.toml file." +"Install your package into the environment in editable mode (similar to " +"`python -m pip install -e`). This means it installs both your project and" +" your project's dependencies as declared in your pyproject.toml file." msgstr "" "Instalar seu pacote no ambiente em modo editable (semelhante a `python-m " "pip install -e`). Isso significa que instala tanto o seu projeto quanto as " @@ -5746,8 +5780,8 @@ msgstr "Etapa 2: Fazer o build das distribuições sdist e wheel do seu pacote" #: ../../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 turning " -"your Python package file structure into two distribution files:" +"your package using Hatch. Remember that building is the process of " +"turning your Python package file structure into two distribution files:" msgstr "" "Depois de configurar seu ambiente de desenvolvimento, você está pronto para " "fazer o build do seu pacote usando Hatch. Lembre-se de que build é o " @@ -5756,9 +5790,9 @@ msgstr "" #: ../../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 such as `pip`. This file has the extension `.whl`." +"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" +" such as `pip`. This file has the extension `.whl`." msgstr "" "A [distribuição wheel](#python-wheel) é uma versão pré-buildada do " "seu package. É útil para usuários, pois pode ser instalada diretamente " @@ -5766,8 +5800,8 @@ msgstr "" #: ../../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 " +"The [source distribution](#python-source-distribution) contains the files" +" that make up your package in an unbuilt format. This file will have the " "extension `.tar.gz`." msgstr "" "A [source distribution](#python-source-distribution) contém os arquivos que " @@ -5776,10 +5810,11 @@ msgstr "" #: ../../tutorials/publish-pypi.md:161 msgid "" -"You will use Hatch as a **Front end** tool that builds your package's sdist " -"and wheel using the [hatchling](https://hatch.pypa.io/latest/) build " -"back-end. The hatchling build back-end is used because you declared it in " -"your pyproject.toml file in the [previous lesson](create-python-package)." +"You will use Hatch as a **Front end** tool that builds your package's " +"sdist and wheel using the [hatchling](https://hatch.pypa.io/latest/) " +"build back-end. The hatchling build back-end is used because you declared" +" it in your pyproject.toml file in the [previous lesson](create-python-" +"package)." msgstr "" "Você usará o Hatch como ferramenta de **Front end** que faz o build do sdist " "e wheel do seu pacote usando o build back-end " @@ -5798,8 +5833,8 @@ msgstr "Saiba mais sobre build de pacote Python" #: ../../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-whe" -"el)." +"guide](../package-structure-code/python-package-distribution-files-sdist-" +"wheel)." msgstr "" "Você pode saber mais sobre build na [página de build do nosso guia de " "empacotamento](../package-structure-code/python-package-distribution-files-s" @@ -5807,9 +5842,8 @@ msgstr "" #: ../../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." +"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." msgstr "" "O sdist é importante se você deseja [publicar seu pacote no " "conda-forge](publish-conda-forge). Você aprenderá sobre isso em uma lição " @@ -5831,9 +5865,9 @@ msgstr "" #: ../../tutorials/publish-pypi.md:193 msgid "" -" Congratulations - you've " -"created your Python package distribution files " +" Congratulations - " +"you've created your Python package distribution files " msgstr "" " Parabéns — você criou os " "arquivos de distribuição do seu pacote Python " +"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 " +"including Development status, intended audience, License, natural " +"language, operating system, programming language and topic. Below each of" +" those sections are various classifier options.\" width=\"300px\">" msgstr "" "Imagem mostrando a barra lateral esquerda do PyPI para o pacote xclim. A " "seção no topo diz Classifier. Abaixo há uma lista de itens " @@ -6849,11 +6886,11 @@ msgstr "" #: ../../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 that PyPI can " -"understand and represent on your PyPI landing page. These classifiers also " -"allow users to sort through packages by version of python they support, " -"categories and more." +"When you add the classifier section to your pyproject.toml and your " +"package is built, the build tool organizes the metadata into a format " +"that PyPI can understand and represent on your PyPI landing page. These " +"classifiers also allow users to sort through packages by version of " +"python they support, categories and more." msgstr "" "Quando você adiciona a seção de classifiers ao seu pyproject.toml e seu " "pacote é construído, a ferramenta de build organiza a metadata em um formato " @@ -6867,8 +6904,8 @@ msgstr "Uma visão geral mais aprofundada dos arquivos pyproject.toml" #: ../../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/)" +"[Our guidebook page has a more in depth overview of this file" +"](../package-structure-code/pyproject-toml-python-package-metadata/)" msgstr "" "[Nossa página do guia tem uma visão geral mais aprofundada deste " "arquivo](../package-structure-code/pyproject-toml-python-package-metadata/)" @@ -6903,11 +6940,11 @@ msgstr "O arquivo `pyproject.toml` que você criou ficou assim:" #: ../../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 " -"scope of your package. Once you add this metadata, you don't have to do it " -"again. These metadata fields will only be updated periodically when you do " -"something such as:" +"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 " +"scope of your package. Once you add this metadata, you don't have to do " +"it again. These metadata fields will only be updated periodically when " +"you do something such as:" msgstr "" "Seu próximo passo é adicionar campos de metadata recomendados adicionais " "que ajudarão os usuários a encontrar seu pacote no PyPI e também " @@ -6942,8 +6979,8 @@ msgstr "Passo 1: Adicionar autor, mantenedor e descrição do projeto" #: ../../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 in " -"the `[project]` table." +"you should have a pyproject.toml file with a project name and a version " +"in the `[project]` table." msgstr "" "Depois de concluir o [tutorial de código " "instalável](create-python-package), você deve ter um arquivo pyproject.toml " @@ -6955,9 +6992,9 @@ msgstr "Adicione o seguinte à sua tabela:" #: ../../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!" +"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 "" "Uma **description** do seu pacote. Deve ser uma única linha e descrever " "brevemente o objetivo do seu pacote usando termos não técnicos, se possível!" @@ -6989,8 +7026,8 @@ msgstr "Nomes e e-mails dos autores" #: ../../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 or " -"maintainers, like this:" +"the pyproject.toml. If you are missing the email for one or more authors " +"or maintainers, like this:" msgstr "" "Há uma peculiaridade no PyPI para autores que têm nomes, mas não e-mails, " "no pyproject.toml. Se estiver faltando o e-mail de um ou mais autores ou " @@ -6998,8 +7035,8 @@ msgstr "" #: ../../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:" +"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 "" "Então sugerimos que você forneça apenas nomes na sua lista de nomes para " "garantir que tudo seja renderizado corretamente na sua página do PyPI — " @@ -7011,9 +7048,9 @@ msgstr "não tiver e-mails para todos, sugerimos que você adicione apenas nomes #: ../../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 your " -"package:" +"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 " +"your package:" msgstr "" "Seu arquivo `pyproject.toml` agora deve se parecer com o exemplo abaixo. " "Está tudo bem se você tiver apenas 1 autor e o mesmo autor também for " @@ -7047,9 +7084,9 @@ msgstr "pessoas que adicionam nova funcionalidade ao pacote." #: ../../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 " -"maintainers. As such these lists may be similar or the same." +"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" +" maintainers. As such these lists may be similar or the same." msgstr "" "Já os maintainers são as pessoas que estão atualmente trabalhando " "ativamente no projeto. Muitas vezes há sobreposição entre authors e " @@ -7057,9 +7094,9 @@ msgstr "" #: ../../tutorials/pyproject-toml.md:273 msgid "" -"A good example of when the lists might diverge is sometimes you have " -"apackage where an initial author developed it and then stepped down asa " -"maintainer to move on to other things. This person may continue tobe " +"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 " +"maintainer to move on to other things. This person may continue to be " "considered an author but no longer actively maintains the package." msgstr "" "Um bom exemplo de quando as listas podem divergir é quando um autor inicial " @@ -7077,9 +7114,9 @@ msgstr "" #: ../../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." +"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 "" "No entanto, incentivamos você a considerar cuidadosamente, para publicação " "no PyPI, quem você quer listar como authors e maintainers na página inicial " @@ -7091,10 +7128,11 @@ msgstr "Passo 2: Adicionar README e license" #: ../../tutorials/pyproject-toml.md:283 msgid "" -"In the previous lessons, you added both a [README.md](add-readme) file and a " -"[LICENSE](add-license-coc) to your package repository. Once you have those " -"files, you can refer to the README from your pyproject.tomlfile, and add a " -"short code indicating your choice of LICENSE following the example below." +"In the previous lessons, you added both a [README.md](add-readme) file " +"and a [LICENSE](add-license-coc) to your package repository. Once you " +"have those files, you can refer to the README from your pyproject.toml " +"file, and add a short code indicating your choice of LICENSE following " +"the example below." msgstr "" "Nas lições anteriores, você adicionou tanto um arquivo " "[README.md](add-readme) quanto um [LICENSE](add-license-coc) ao repository " @@ -7105,13 +7143,12 @@ msgstr "" #: ../../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/license-expres" -"sion/). Often this is a short name(withnospaces) for the license, such as \"MIT\", " -"\"BSD-3-Clause\" or\"Apache-2.0\". More precisely, it must be a valid SPDX " -"license expression, as documented in the [SPDX " -"specification](https://spdx.github.io/spdx-spec/v2.2.2/SPDX-license-expressi" -"ons/), either version 2.2 or a later compatible version." +"expression syntax](https://packaging.python.org/en/latest/specifications" +"/license-expression/). Often this is a short name (with no spaces) for " +"the license, such as \"MIT\", \"BSD-3-Clause\" or \"Apache-2.0\". More " +"precisely, it must be a valid SPDX license expression, as documented in " +"the [SPDX specification](https://spdx.github.io/spdx-spec/v2.2.2/SPDX-" +"license-expressions/), either version 2.2 or a later compatible version." msgstr "" "A entrada license no seu arquivo pyproject.toml deve usar a [sintaxe de " "expressão de " @@ -7134,8 +7171,8 @@ msgstr "" msgid "" "If you want to distribute license files, or other files containing legal " "information, with your package, you can include these using the " -"[`license-files`](https://packaging.python.org/en/latest/guides/writing-pypr" -"oject-toml/#license-files)entry, but this is not required." +"[`license-files`](https://packaging.python.org/en/latest/guides/writing-" +"pyproject-toml/#license-files) entry, but this is not required." msgstr "" "Se quiser distribuir arquivos de license ou outros arquivos com informações " "legais junto com seu pacote, pode incluí-los usando a entrada " @@ -7148,15 +7185,16 @@ msgstr "Passo 3: Especificar a versão do Python com `requires-python`" #: ../../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 versions that " -"your package supports. It is set to a single value. The [packaging " -"specification](https://packaging.python.org/en/latest/specifications/core-me" -"tadata/#core-metadata-requires-python)defines `requires-python" -" `as a string that uses version specifiers. Most projects will specify the oldest " -"Python version supported by the package. In some advanced cases, an upper " -"bound is set to indicate which future Python versions, if any, will be " -"supported." +"Add the `requires-python` field to your `pyproject.toml` `[project]` " +"table. The `requires-python` field helps pip identify which Python " +"versions that your package supports. It is set to a single value. The " +"[packaging " +"specification](https://packaging.python.org/en/latest/specifications" +"/core-metadata/#core-metadata-requires-python) defines`requires-python` " +"as a string that uses version specifiers. Most projects will specify the " +"oldest Python version supported by the package. In some advanced cases, " +"an upper bound is set to indicate which future Python versions, if any, " +"will be supported." msgstr "" "Adicione o campo `requires-python` à tabela `[project]` do seu " "`pyproject.toml`. O campo `requires-python` ajuda o pip a identificar quais " @@ -7177,8 +7215,8 @@ msgstr "Mas como descubro quais versões do Python devo suportar?" msgid "" "Good question. The Python developer guide provides a [status " "page](https://devguide.python.org/versions/) (and a handy visualization) " -"that explains the status of each Python release. Python releases go through " -"several different phases that are explained in [PEP " +"that explains the status of each Python release. Python releases go " +"through several different phases that are explained in [PEP " "602](https://peps.python.org/pep-0602/)." msgstr "" "Boa pergunta. O guia do desenvolvedor Python fornece uma [página de " @@ -7199,9 +7237,10 @@ msgstr "" #: ../../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, including Python " -"release versions, and is also worth considering for your project." +"[SPEC 0](https://scientific-python.org/specs/spec-0000/) of the " +"Scientific Python project suggests a common schedule for dependencies, " +"including Python release versions, and is also worth considering for your" +" project." msgstr "" "O [SPEC 0](https://scientific-python.org/specs/spec-0000/) do projeto " "Scientific Python sugere um cronograma comum para dependências, incluindo " @@ -7214,8 +7253,8 @@ msgstr "Passo 4: Especificar Dependencies" #: ../../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 " +"Next add your dependencies table to the project table. The `dependencies " +"=` section contains a list (or array in the toml language) of the Python " "packages that your package requires to run properly in a Python " "environment. Similar to the requirements listed in the `[build-system]` " "table above:" @@ -7236,11 +7275,11 @@ msgstr "" msgid "" "A dependency can be limited to specific versions using a **version " "specifier.** If the dependency has no version specifier after the " -"dependency name, your package can use any version of the dependent package. " -"Code changes over time, bugs are fixed, APIs change, and so it's good to be " -"clear about which version of the dependency you wrote your code to be " -"compatible with - a package you wrote this year probably isn't compatible " -"with numpy v0.0.1!" +"dependency name, your package can use any version of the dependent " +"package. Code changes over time, bugs are fixed, APIs change, and so it's" +" good to be clear about which version of the dependency you wrote your " +"code to be compatible with - a package you wrote this year probably isn't" +" compatible with numpy v0.0.1!" msgstr "" "Uma dependency pode ser limitada a versões específicas usando um " "**especificador de versão.** Se a dependency não tiver especificador de " @@ -7253,8 +7292,8 @@ msgstr "" #: ../../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-specifi" -"ers/#id5)" +"here.](https://packaging.python.org/en/latest/specifications/version-" +"specifiers/#id5)" msgstr "" "[Saiba mais sobre várias formas de especificar intervalos de versões de " "pacotes " @@ -7264,10 +7303,10 @@ msgstr "" #: ../../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 " -"the lowest version that is still compatible with your package, but in " -"practice for new packages this is often set at the version that was current " -"at the time the package was written[^lowerbound]." +"version higher than the specified version. Ideally you should set this to" +" the lowest version that is still compatible with your package, but in " +"practice for new packages this is often set at the version that was " +"current at the time the package was written[^lowerbound]." msgstr "" "O especificador de versão mais comum é um **limite inferior,** permitindo " "qualquer versão superior à versão especificada. Idealmente você deve " @@ -7282,7 +7321,8 @@ msgstr "Limites inferiores ficam assim:" #: ../../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 specifiers:" +"your `dependencies` section can use different types of version " +"specifiers:" msgstr "" "Vírgulas são usadas para separar dependencies individuais, e cada pacote na " "sua seção `dependencies` pode usar diferentes tipos de especificadores de " @@ -7297,7 +7337,9 @@ msgid "Pin dependencies with caution" msgstr "Fixe dependencies com cautela" #: ../../tutorials/pyproject-toml.md:435 -msgid "\"Pinning\" a dependency means setting it to a specific version, like this:" +msgid "" +"\"Pinning\" a dependency means setting it to a specific version, like " +"this:" msgstr "" "\"Fixar\" (pinning) uma dependency significa defini-la para uma " "versão específica, assim:" @@ -7309,13 +7351,13 @@ msgstr "`numpy == 1.0`." #: ../../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 version. " -"Applications, such as production websites, will often pin their " -"dependencies since other packages will not depend on their project. This is " -"because users will be installing your package into various environments. A " -"dependency pinned to a single specific version can make resolving a Python " -"environment more challenging. As such only pin dependencies to a specific " -"version if you absolutely need to do so." +"upon, you must be cautious before pinning to a precise dependency " +"version. Applications, such as production websites, will often pin their " +"dependencies since other packages will not depend on their project. This " +"is because users will be installing your package into various " +"environments. A dependency pinned to a single specific version can make " +"resolving a Python environment more challenging. As such only pin " +"dependencies to a specific version if you absolutely need to do so." msgstr "" "Se você está construindo um pacote de biblioteca do qual outros " "desenvolvedores dependerão, deve ser cauteloso antes de fixar uma " @@ -7351,11 +7393,11 @@ msgstr "Passo 5: Adicionar classifiers do PyPI" #: ../../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 from " -"the list of [PyPI accepted classifier values found " -"here](https://PyPI.org/classifiers/). Any deviations in spelling and format " -"will cause issues when you publish to PyPI." +"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 " +"from the list of [PyPI accepted classifier values found " +"here](https://PyPI.org/classifiers/). Any deviations in spelling and " +"format will cause issues when you publish to PyPI." msgstr "" "Em seguida, você adicionará classifiers ao seu arquivo `pyproject.toml`. O " "valor de cada classifier que você adicionar ao seu arquivo `pyproject.toml` " @@ -7371,8 +7413,8 @@ msgstr "O que acontece quando você usa classifiers incorretos?" msgid "" "If you do not [use standard classifier " "values](https://PyPI.org/classifiers/), when you try to publish your " -"package on PyPI it will be rejected. 😔 Don't worry if PyPI rejects you " -"on your first try! It has happened to all of us." +"package on PyPI it will be rejected. 😔 Don't worry if PyPI rejects you on" +" your first try! It has happened to all of us." msgstr "" "Se você não [usar valores de classifiers " "padrão](https://PyPI.org/classifiers/), ao tentar publicar seu pacote no " @@ -7402,16 +7444,18 @@ msgid "programming language support" msgstr "programming language support" #: ../../tutorials/pyproject-toml.md:475 -msgid "The classifier key should look something like the example below. A few notes:" +msgid "" +"The classifier key should look something like the example below. A few " +"notes:" msgstr "" "A chave classifier deve se parecer com o exemplo abaixo. Algumas " "observações:" #: ../../tutorials/pyproject-toml.md:477 msgid "" -"Your classifier values might be different depending upon your " -"intended audience, development status of your package and the Python " -"versions that you support" +"Your classifier values might be different depending upon your intended " +"audience, development status of your package and the Python versions that" +" you support" msgstr "" "Seus valores de classifiers podem ser diferentes dependendo do " "público-alvo, do status de desenvolvimento do seu pacote e das versões do " @@ -7427,9 +7471,9 @@ msgstr "" #: ../../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 recommend that " -"you add them." +"Note that while classifiers are not required in your `pyproject.toml` " +"file, they will help users find your package. As such we strongly " +"recommend that you add them." msgstr "" "Observe que, embora os classifiers não sejam obrigatórios no seu arquivo " "`pyproject.toml`, eles ajudarão os usuários a encontrar seu pacote. Por " @@ -7445,17 +7489,17 @@ msgstr "Por fim, adicione a tabela project.urls ao seu arquivo pyproject.toml." #: ../../tutorials/pyproject-toml.md:523 msgid "" -"`project.urls` contains links that are relevant for your project. You might " -"want to include:" +"`project.urls` contains links that are relevant for your project. You " +"might want to include:" msgstr "" "`project.urls` contém links relevantes para o seu projeto. Você pode querer " "incluir:" #: ../../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 yet. " -"That's ok, you can skip it for the time being." +"**Homepage:** A link to your published documentation for your project. If" +" you are working through this tutorial, then you may not have this link " +"yet. That's ok, you can skip it for the time being." msgstr "" "**Homepage:** Um link para a documentação publicada do seu projeto. Se você " "está seguindo este tutorial, talvez ainda não tenha esse link. Tudo bem, " @@ -7475,8 +7519,8 @@ msgstr "**Fonte:** o link do GitHub / GitLab do seu projeto." #: ../../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)." +"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)." msgstr "" "Há muitas outras URLs que você pode adicionar aqui. Confira o " "[arquivo README aqui para uma visão " @@ -7488,8 +7532,8 @@ msgstr "Juntando tudo — seu arquivo pyproject.toml completo" #: ../../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." +"Below is an example of a complete `pyproject.toml` file that is commented" +" with all of the sections we discussed above." msgstr "" "Abaixo está um exemplo de um arquivo `pyproject.toml` completo, com " "comentários em todas as seções que discutimos acima." @@ -7512,8 +7556,8 @@ msgstr "Exemplos de arquivos `pyproject.toml`" #: ../../tutorials/pyproject-toml.md:694 msgid "" -"Below are some examples of `pyproject.toml` files from various packages in " -"the scientific and pyOpenSci ecosystem." +"Below are some examples of `pyproject.toml` files from various packages " +"in the scientific and pyOpenSci ecosystem." msgstr "" "Abaixo estão alguns exemplos de arquivos `pyproject.toml` de vários pacotes " "no ecossistema científico e pyOpenSci." @@ -7530,8 +7574,7 @@ msgstr "" msgid "" "[taxpasta has a nicely organized pyproject.toml file and is a pyOpenSci " "approved " -"package](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a53" -"dd49ad77e4cf143573/pyproject.toml)" +"package](https://github.com/taxprofiler/taxpasta/blob/f9f6eea2ae7dd08bb60a53dd49ad77e4cf143573/pyproject.toml)" msgstr "" "[taxpasta tem um arquivo pyproject.toml bem organizado e é um pacote " "aprovado pelo " @@ -7561,7 +7604,9 @@ msgstr "" "como as pessoas podem e não podem usar seu software" #: ../../tutorials/pyproject-toml.md:708 -msgid "You also learned [how to publish your package to (test)PyPI](publish-pypi)." +msgid "" +"You also learned [how to publish your package to (test)PyPI](publish-" +"pypi)." msgstr "Você também aprendeu [como publicar seu pacote no (test)PyPI](publish-pypi)." #: ../../tutorials/pyproject-toml.md:710 @@ -7570,9 +7615,9 @@ msgstr "Publicar uma nova versão do seu pacote no PyPI" #: ../../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 package " -"now contains a lot more information." +"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" +" package now contains a lot more information." msgstr "" "Agora você está pronto para publicar uma nova versão do seu pacote Python " "no (test) PyPI. Ao fazer isso, verá que a página do seu pacote agora contém " @@ -7584,8 +7629,8 @@ msgstr "Tente republicar agora." #: ../../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`." +"First, update the version of your package in your pyproject toml file. " +"Below version is updated from `0.1` to `0.1.1`." msgstr "" "Primeiro, atualize a versão do seu pacote no arquivo pyproject.toml. " "Abaixo, a versão é atualizada de `0.1` para `0.1.1`." @@ -7610,9 +7655,9 @@ msgstr "" #: ../../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." +"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 "" "Se você também quiser publicar seu pacote no conda-forge (que é um canal " "dentro do ecossistema conda), aprenderá como fazer isso na próxima lição." @@ -7629,12 +7674,12 @@ msgstr "" #: ../../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-poetry.org/docs/cli/#add) will add the most recent " -"version with a `^` specifier, and [`pdm " -"add`](https://pdm-project.org/latest/reference/cli/#add) will add the most " -"recent version with `>=`." +"Some packaging tools will do this for you when you add a dependency using" +" their cli interface. For example [`poetry add`](https://python-" +"poetry.org/docs/cli/#add) will add the most recent version with a `^` " +"specifier, and [`pdm add`](https://pdm-" +"project.org/latest/reference/cli/#add) will add the most recent version " +"with `>=`." msgstr "" "Algumas ferramentas de empacotamento fazem isso por você quando você " "adiciona uma dependência usando a interface CLI delas. Por exemplo, " @@ -7645,9 +7690,9 @@ msgstr "" #: ../../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." +"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 "" "O Python suporta metadata inline para scripts (um recurso adicionado em " "2024). Isso torna possível executar scripts independentes com dependências " @@ -7656,9 +7701,9 @@ 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." +"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 "" "Muitas ferramentas suportam esse workflow, incluindo PDM, " "[Hatch](get-to-know-hatch) e {term}`uv`. Neste tutorial, focamos no Hatch e " @@ -7667,8 +7712,8 @@ 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/)" +"[Hatch: How to run Python scripts](https://hatch.pypa.io/latest/how-" +"to/run/python-scripts/)" msgstr "" "[Hatch: Como executar scripts " "Python](https://hatch.pypa.io/latest/how-to/run/python-scripts/)" @@ -7676,7 +7721,8 @@ msgstr "" #: ../../tutorials/run-python-scripts-hatch.md:23 msgid "" "[uv: Running " -"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)" +"scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-" +"script)" msgstr "" "[uv: Executando " "scripts](https://docs.astral.sh/uv/guides/scripts/#creating-a-python-script)" @@ -7688,10 +7734,10 @@ msgstr "Como criar um script reproduzível" #: ../../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." +"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 "" "Às vezes você quer compartilhar ou executar um único script sem criar um " "{term}`pacote Python ` completo. Para isso, você pode usar " @@ -7700,8 +7746,8 @@ 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:" +"When you add metadata at the top of a script, Hatch (or PDM or uv) will " +"use that metadata to:" msgstr "" "Quando você adiciona metadata no topo de um script, o Hatch (ou PDM ouuv) " "usará essa metadata para:" @@ -7712,7 +7758,9 @@ msgstr "Criar um virtual environment Python isolado para esse script." #: ../../tutorials/run-python-scripts-hatch.md:38 #, python-brace-format -msgid "Install the {term}`Dependencies` listed in the script into that environment." +msgid "" +"Install the {term}`Dependencies` listed in the script into that " +"environment." msgstr "" "Instalar as {term}`dependências ` listadas no script nesse " "environment." @@ -7723,8 +7771,8 @@ msgstr "Usar a versão do Python exigida que você especificar na metadata." #: ../../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." +"This approach is useful for workflows that you want to make reproducible," +" but that do not need to become full Python packages." msgstr "" "Essa abordagem é útil para workflows que você quer tornar reproduzíveis, " "mas que não precisam se tornar pacote Pythons completos." @@ -7751,8 +7799,8 @@ msgstr "Como adicionar metadata inline ao seu script" #: ../../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." +"You will use Hatch in this example, but you can also use uv if that is " +"your preferred tool." msgstr "" "Você usará o Hatch neste exemplo, mas também pode usar o uv se essa for sua " "ferramenta preferida." @@ -7760,9 +7808,9 @@ 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." +"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 "" "Primeiro, crie um novo arquivo chamado `script.py` com o bloco abaixo no " "topo. O bloco de metadata começa com `# /// script` e termina com `# ///`. " @@ -7770,8 +7818,8 @@ 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." +"In the example below, the script requires Python 3.11 or newer, and NumPy" +" is declared as a dependency." msgstr "" "No exemplo abaixo, o script requer Python 3.11 ou mais recente, e o NumPy é " "declarado como dependência." @@ -7790,8 +7838,8 @@ 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." +"On first run, Hatch will create an environment and install dependencies. " +"On later runs, Hatch will reuse that environment so startup is faster." msgstr "" "Na primeira execução, o Hatch criará um environment e instalará as " "dependências. Nas execuções seguintes, o Hatch reutilizará esse environment " @@ -7799,8 +7847,8 @@ 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." +"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 "" "O nome do environment é baseado no caminho do script. Se você mover o " "script para um novo local, o Hatch o tratará como um novo script " @@ -7812,8 +7860,8 @@ msgstr "Opcional: configurar o comportamento do script environment" #: ../../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:" +"You can control script-specific Hatch behavior in the same metadata " +"block. For example, to use `pip` instead of `uv` as the installer:" msgstr "" "Você pode controlar o comportamento específico do Hatch para scripts no " "mesmo bloco de metadata. Por exemplo, para usar `pip` em vez de `uv` como " @@ -7837,8 +7885,8 @@ 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)." +"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 "" "Para mais informações sobre como usar o uv para executar scripts, consulte " "o guia: [Executando scripts com " @@ -7866,8 +7914,8 @@ msgstr "" #: ../../tutorials/run-python-scripts-hatch.md:135 msgid "" -"Your workflow is still evolving, but you want to run it in a reproducible " -"environment." +"Your workflow is still evolving, but you want to run it in a reproducible" +" environment." msgstr "" "Seu workflow ainda está evoluindo, mas você quer executá-lo em um " "environment reproduzível." @@ -7914,8 +7962,8 @@ msgstr "Usando o Hatch para migrar setup.py para pyproject.toml" #: ../../tutorials/setup-py-to-pyproject-toml.md:9 msgid "" -"[Hatch](get-to-know-hatch) can be useful for generating your " -"project's[pyproject.toml](pyproject-toml) file if your project already has a " +"[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 "" "O [Hatch](get-to-know-hatch) pode ser útil para gerar o arquivo " @@ -7928,24 +7976,24 @@ msgstr "Nota" #: ../../tutorials/setup-py-to-pyproject-toml.md:16 msgid "" -"This step is not necessary and is only helpful if your project already has a " -"`setup.py` file defined." +"This step is not necessary and is only helpful if your project already " +"has a `setup.py` file defined." msgstr "" "Esta etapa não é necessária e só é útil se seu projeto já tiver um arquivo " "`setup.py` definido." #: ../../tutorials/setup-py-to-pyproject-toml.md:17 msgid "" -"If your project does not already define a `setup.py` see [Make your Python " -"code installable](create-python-package)" +"If your project does not already define a `setup.py` see [Make your " +"Python code installable](create-python-package)" msgstr "" "Se seu projeto ainda não define um `setup.py`, consulte [Torne seu código " "Python instalável](create-python-package)" #: ../../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." +"The process of using Hatch to transition to using `pyproject.toml` for " +"projects that already have a `setup.py` defined." msgstr "" "O processo de usar o Hatch para fazer a transição para `pyproject.toml` em " "projetos que já têm um `setup.py` definido." @@ -7958,9 +8006,9 @@ msgstr "O que é o Hatch?" #, 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 {term}`Dependencies`, building distributions, and " +"creating, managing, and distributing Python packages. It provides a " +"convenient CLI (Command-Line Interface) for tasks such as creating new " +"projects, managing {term}`Dependencies`, building distributions, and " "publishing packages to repositories like [PyPI](publish-pypi)." msgstr "" "O Hatch é um gerenciador de pacote Pythons projetado para " @@ -7980,8 +8028,8 @@ msgstr "Pré-requisitos" #: ../../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:" +"Before we begin, ensure that you have Hatch installed on your system. You" +" can install it via pip:" msgstr "" "Antes de começar, certifique-se de que o Hatch está instalado no seu " "sistema. Você pode instalá-lo via pip:" @@ -8008,8 +8056,8 @@ msgstr "Depois de `hatch init`" #: ../../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." +"As you can see, the main change after running `hatch init` is the " +"addition of the `pyproject.toml` file in the project directory." msgstr "" "Como você pode ver, a principal mudança após executar `hatch init` é " "a adição do arquivo `pyproject.toml` no diretório do projeto." @@ -8020,8 +8068,8 @@ msgstr "Guia passo a passo" #: ../../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." +"Now, let's walk through the steps to use Hatch to create a " +"`pyproject.toml` file for your project." msgstr "" "Agora, vamos percorrer os passos para usar o Hatch e criar um arquivo " "`pyproject.toml` para seu projeto." @@ -8029,15 +8077,16 @@ msgstr "" #: ../../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." +"prompt and navigate to the directory where your Python project is " +"located." msgstr "" "**Navegue até o diretório do seu projeto**: Abra seu terminal ou prompt de " "comando e navegue até o diretório onde seu projeto Python está localizado." #: ../../tutorials/setup-py-to-pyproject-toml.md:97 msgid "" -"**Initialize Hatch**: Run the following command to initialize Hatch in your " -"project directory:" +"**Initialize Hatch**: Run the following command to initialize Hatch in " +"your project directory:" msgstr "" "**Inicialize o Hatch**: Execute o seguinte comando para inicializar o Hatch " "no diretório do seu projeto:" @@ -8047,9 +8096,10 @@ msgid "" "**Review and Customize**: After running the previous command, Hatch will " "automatically generate a `pyproject.toml` file based on your existing " "project configuration. Take some time to review the contents of the " -"generated `pyproject.toml` file. You may want to customize certain settings " -"or dependencies based on your project's requirements (see [pyproject.toml " -"tutorial](pyproject-toml) for more information about the `pyproject.toml`)." +"generated `pyproject.toml` file. You may want to customize certain " +"settings or dependencies based on your project's requirements (see " +"[pyproject.toml tutorial](pyproject-toml) for more information about the " +"`pyproject.toml`)." msgstr "" "**Revise e personalize**: Após executar o comando anterior, o Hatch gerará " "automaticamente um arquivo `pyproject.toml` com base na configuração " @@ -8061,9 +8111,9 @@ msgstr "" #: ../../tutorials/setup-py-to-pyproject-toml.md:105 msgid "" -"**Verify**: Verify that the `pyproject.toml` file accurately reflects your " -"project configuration and dependencies. You can manually edit the file, but " -"be cautious and ensure that the syntax is correct." +"**Verify**: Verify that the `pyproject.toml` file accurately reflects " +"your project configuration and dependencies. You can manually edit the " +"file, but be cautious and ensure that the syntax is correct." msgstr "" "**Verifique**: Verifique se o arquivo `pyproject.toml` reflete com precisão " "a configuração e as dependências do seu projeto. Você pode editar o arquivo " @@ -8072,8 +8122,8 @@ msgstr "" #: ../../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 delete " -"it from your project directory." +"exclusively, the `setup.py` file becomes unnecessary. You can safely " +"delete it from your project directory." msgstr "" "**Exclua o setup.py**: Como estamos migrando para usar exclusivamente " "`pyproject.toml`, o arquivo `setup.py` se torna desnecessário. Você pode " @@ -8082,8 +8132,8 @@ msgstr "" #: ../../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. Run " -"the following command to build your project:" +"your project builds successfully using only the `pyproject.toml` file. " +"Run the following command to build your project:" msgstr "" "**Teste o build**: Antes de prosseguir, é essencial garantir que seu " "projeto faz build com sucesso usando apenas o arquivo `pyproject.toml`. " @@ -8092,8 +8142,8 @@ msgstr "" #: ../../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 during " -"the build process." +"`pyproject.toml` file. Make sure to check for any errors or warnings " +"during the build process." msgstr "" "Este comando fará o build do seu projeto com base nas especificações do " "arquivo `pyproject.toml`. Certifique-se de verificar se há erros ou avisos " @@ -8101,10 +8151,10 @@ msgstr "" #: ../../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 existing " -"functionality remains intact. Run any pre-existing tests to verify that " -"everything still works as expected." +"**Test Existing Functionality**: After successfully building your project" +" with `pyproject.toml`, it's crucial to ensure that your project's " +"existing functionality remains intact. Run any pre-existing tests to " +"verify that everything still works as expected." msgstr "" "**Teste a funcionalidade existente**: Após fazer o build do seu projeto com " "sucesso com `pyproject.toml`, é crucial garantir que a funcionalidade " @@ -8129,8 +8179,8 @@ msgstr "[Como criar um pacote Python](create-python-package)" #: ../../tutorials/trusted-publishing.md:11 msgid "" -"How to publish the code to [PyPI](publish-pypi) and " -"[Conda](publish-conda-forge)" +"How to publish the code to [PyPI](publish-pypi) and [Conda](publish-" +"conda-forge)" msgstr "" "Como publicar o código no [PyPI](publish-pypi) e no " "[Conda](publish-conda-forge)" @@ -8171,12 +8221,12 @@ msgstr "Configurar um job de release no GitHub Actions" #: ../../tutorials/trusted-publishing.md:28 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](publish-pypi)." +"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](publish-pypi)." msgstr "" "O GitHub Actions[^gha] é uma infraestrutura fornecida pelo GitHub " "para automatizar workflows de software, diretamente do repositório GitHub do " @@ -8193,10 +8243,9 @@ msgstr "Por que o Trusted Publishing é importante" #: ../../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-security-publish-pypi" -".html)that dives deeper into what can happen when you don't lock down your " -"publishing workflows." +"this blog post:](https://www.pyopensci.org/blog/python-packaging-" +"security-publish-pypi.html) that dives deeper into what can happen when " +"you don't lock down your publishing workflows." msgstr "" "Se você está se perguntando por que o trusted publishing é tão importante, " "[confira este post do " @@ -8211,10 +8260,10 @@ msgstr "Passo 0: Criar um workflow de release" #: ../../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` " -"directory does not exist, you can create it. It is GitHub's convention that " -"all GitHub Actions are configured via YAML files in the `.github/workflows` " -"directory." +"`.github/workflows` directory of your project. If the `.github/workflows`" +" directory does not exist, you can create it. It is GitHub's convention " +"that all GitHub Actions are configured via YAML files in the " +"`.github/workflows` directory." msgstr "" "Para começar, crie um arquivo chamado `release.yaml` no diretório " "`.github/workflows` do seu projeto. Se o diretório `.github/workflows` não " @@ -8248,8 +8297,9 @@ msgstr "No topo do arquivo `release.yaml`, digite o seguinte:" #: ../../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." +"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 "" "Isso fornece um nome ao workflow que você pode usar para encontrar " "rapidamente todas as execuções desta GitHub Action na aba \"Actions\" do " @@ -8257,12 +8307,13 @@ msgstr "" #: ../../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 GitHub " -"repository. On the left, in the red box labeled \"2\" you can see the name of " -"the workflow, \"Release,\" as configured in this step. Finally, in the " -"center, in the red box labeled \"3\" you can see several runs of the " -"workflow, for the \"1.0\" and \"1.0.1\" releases of the package." +"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 " +"GitHub repository. On the left, in the red box labeled \"2\" you can see " +"the name of the workflow, \"Release,\" as configured in this step. " +"Finally, in the center, in the red box labeled \"3\" you can see several " +"runs of the workflow, for the \"1.0\" and \"1.0.1\" releases of the " +"package." msgstr "" "Gráfico mostrando um exemplo de workflow configurado para o release. No " "topo, na caixa vermelha rotulada \"1\", você vê a aba \"Actions\" do " @@ -8274,11 +8325,11 @@ msgstr "" #: ../../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 GitHub " -"repository. On the left, in the red box labeled \"2\" you can see the name of " -"the workflow, as configured in this step. Finally, in the center, in the " -"red box labeled \"3\" you can see several runs of the workflow, for the \"1.0\" " -"and \"1.0.1\" releases of the package." +"the top, in the red box labeled \"1\" you see the \"Actions\" tab of the " +"GitHub repository. On the left, in the red box labeled \"2\" you can see " +"the name of the workflow, as configured in this step. Finally, in the " +"center, in the red box labeled \"3\" you can see several runs of the " +"workflow, for the \"1.0\" and \"1.0.1\" releases of the package." msgstr "" "Esta imagem mostra um exemplo de workflow configurado para o release. No " "topo, na caixa vermelha rotulada \"1\", você vê a aba \"Actions\" do " @@ -8294,12 +8345,13 @@ msgstr "Passo 2: Adicionar triggers ao workflow" #: ../../tutorials/trusted-publishing.md:75 msgid "" "Every GitHub Actions workflow runs when [certain " -"conditions](https://docs.github.com/en/actions/reference/events-that-trigger" -"-workflows)are met. In this case, wem assume that a release workflow should only run " -"when the repository owner creates a new " -"[release](https://docs.github.com/en/repositories/releasing-projects-on-gith" -"ub/managing-releases-in-a-repository)for the package. Add the following to the" -"`release.yaml` file to ensure it runs when you create and publish a release:" +"conditions](https://docs.github.com/en/actions/reference/events-that-" +"trigger-workflows) are met. In this case, we assume that a release " +"workflow should only run when the repository owner creates a new " +"[release](https://docs.github.com/en/repositories/releasing-projects-on-" +"github/managing-releases-in-a-repository) for the package. Add the " +"following to the `release.yaml` file to ensure it runs when you create " +"and publish a release:" msgstr "" "Todo workflow do GitHub Actions é executado quando [certas " "condições](https://docs.github.com/en/actions/reference/events-that-trigger-" @@ -8317,9 +8369,9 @@ msgstr "Passo 3: Configurar os jobs no workflow" #: ../../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, the " -"GitHub Action runs all the jobs in a workflow (excluding any steps that " -"have conditional requirements)." +"independently; each job can also have multiple *steps.* When triggered, " +"the GitHub Action runs all the jobs in a workflow (excluding any steps " +"that have conditional requirements)." msgstr "" "Um arquivo de *workflow* do GitHub Actions pode conter vários *jobs* que " "são executados de forma independente; cada job também pode ter vários " @@ -8329,11 +8381,11 @@ msgstr "" #: ../../tutorials/trusted-publishing.md:93 msgid "" "Jobs and steps can also have [conditional " -"logic](https://docs.github.com/en/actions/reference/workflow-syntax-for-gith" -"ub-actions#jobsjob_idif)that allows them only to run if specific criteria exist. " -"For instance,you may wantonly to have a job step to publish to PyPI if a " -"release was made for the package. But you might want to test building the " -"package every time you merge a new pull request." +"logic](https://docs.github.com/en/actions/reference/workflow-syntax-for-" +"github-actions#jobsjob_idif) that allows them only to run if specific " +"criteria exist. For instance, you may want only to have a job step to " +"publish to PyPI if a release was made for the package. But you might want" +" to test building the package every time you merge a new pull request." msgstr "" "Jobs e steps também podem ter [lógica " "condicional](https://docs.github.com/en/actions/reference/workflow-syntax-fo" @@ -8345,9 +8397,9 @@ msgstr "" #: ../../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](get-to-know-hatch) to build your package." +"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](get-to-know-hatch) to build your package." msgstr "" "Para um job de release, você precisa clonar ou fazer checkout do " "repositório. Você pode usar a action `actions/checkout` para fazer checkout " @@ -8356,8 +8408,8 @@ msgstr "" #: ../../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." +"You also need to make sure to set up Hatch on the machine GitHub is using" +" to run the workflow." msgstr "" "Você também precisa garantir que o Hatch esteja configurado na máquina que o " "GitHub está usando para executar o workflow." @@ -8369,9 +8421,9 @@ msgstr "Uma definição mínima de job seria assim:" #: ../../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 action. " -"The checkout action checks out the code from your repository. In this case, " -"the code will be used to build your package." +"`action/checkout@v5` tells GitHub to use version 5 of the checkout " +"action. The checkout action checks out the code from your repository. In " +"this case, the code will be used to build your package." msgstr "" "Observe que acima você fornece uma versão para cada step de action. " "`action/checkout@v5` diz ao GitHub para usar a versão 5 da action checkout. " @@ -8379,7 +8431,9 @@ msgstr "" "código será usado para fazer o build do seu pacote." #: ../../tutorials/trusted-publishing.md:126 -msgid "Next, you will learn about a better way to secure (or \"harden\") your workflow" +msgid "" +"Next, you will learn about a better way to secure (or \"harden\") your " +"workflow" msgstr "" "Em seguida, você aprenderá sobre uma maneira melhor de proteger (ou " "\"endurecer\") seu workflow" @@ -8390,16 +8444,16 @@ msgstr "Passo 4: Proteger o workflow do GitHub Actions" #: ../../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." +"There are several improvements you can make to the GitHub Actions " +"workflow you just configured to improve security and readability." msgstr "" "Há várias melhorias que você pode fazer no workflow do GitHub Actions que " "acabou de configurar para melhorar a segurança e a legibilidade." #: ../../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 " +"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 "" "Primeiro, podemos dar nomes aos passos relevantes do processo para aumentar " @@ -8409,10 +8463,11 @@ msgstr "" #: ../../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 " -"if a malicious user takes over the action, they won't be able to impact " -"your repository (an example of a supply chain attack due to GitHub Actions " -"is the recent `tj-actions/changed-files` attack[^changed-files-supply-chain-attack])." +"should pin that action to a commit hash. Pinning your action ensures that" +" if a malicious user takes over the action, they won't be able to impact " +"your repository (an example of a supply chain attack due to GitHub " +"Actions is the recent `tj-actions/changed-files` attack[^changed-files-" +"supply-chain-attack])." msgstr "" "Mais importante, toda vez que você usar uma action existente (via `uses`), " "deve fixar essa action a um commit hash. Fixar sua action garante que, se " @@ -8424,8 +8479,8 @@ msgstr "" #: ../../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." +"actions stay up to date. The dependabot tool will open pull requests that" +" update your action versions at whatever frequency you want." msgstr "" "Habilitar o Dependabot[^dependabot] no repositório garantirá que suas " "actions permaneçam atualizadas. A ferramenta dependabot abrirá pull " @@ -8446,10 +8501,10 @@ msgstr "" #: ../../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. Unfortunately, " -"the wheel is only available on the runner and will be deleted at the end of " -"the workflow run." +"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. " +"Unfortunately, the wheel is only available on the runner and will be " +"deleted at the end of the workflow run." msgstr "" "Neste ponto, se você criar um novo release para seu projeto no GitHub, o " "workflow configurado deve ser executado e fazer o build de uma wheel para " @@ -8463,8 +8518,8 @@ msgstr "Passo 5: Fazer upload do artefato build para GitHub Artifacts" #: ../../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:" +"the wheel. You will upload it to the artifacts temporary area[^github-" +"artifacts]. Add the following to the `release.yaml` file:" msgstr "" "Você precisa adicionar mais um step à definição do job para poder acessar a " "wheel. Você fará upload dela para a área temporária de " @@ -8476,8 +8531,8 @@ msgstr "Parâmetros de upload de artifacts" #: ../../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 " +"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 "" "Acima, você configurou o artifact para ser excluído após 1 dia. O " @@ -8486,9 +8541,10 @@ msgstr "" #: ../../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 previous step) " -"failed to build our package, so there is nothing to release." +"You have also configured the release job to error if the `dist/` " +"directory does not exist. This means that `hatch build` (from the " +"previous step) failed to build our package, so there is nothing to " +"release." msgstr "" "Você também configurou o job de release para gerar erro se o " "diretório`dist/` não existir. Isso significa que `hatch build` (do step " @@ -8537,8 +8593,8 @@ msgstr "" #: ../../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 " +"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 "" "Esta figura mostra um exemplo de workflow de release que acabou de terminar " @@ -8547,21 +8603,24 @@ msgstr "" #: ../../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:" +"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 "" "Na parte inferior da página de execução do workflow no GitHub, você deve " "ver uma seção para os artifacts produzidos durante a execução e enviados " "para esta área de armazenamento:" #: ../../tutorials/trusted-publishing.md:205 -msgid "Graphic showing an example of an artifact produced by the release workflow." +msgid "" +"Graphic showing an example of an artifact produced by the release " +"workflow." msgstr "Gráfico mostrando um exemplo de artifact produzido pelo workflow de release." #: ../../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." +"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 "" "Esta figura mostra o artifact produzido pelo workflow de release acima. " "Agora está marcado como expirado, pois o workflow foi executado há mais de " @@ -8570,9 +8629,9 @@ msgstr "" #: ../../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 " -"to test the built wheel. Next, you will configure uploading to PyPI using " -"trusted publishing." +"the wheel contained within. However, this should only be done if you want" +" to test the built wheel. Next, you will configure uploading to PyPI " +"using trusted publishing." msgstr "" "Você pode baixar o artifact (antes que expire), descompactá-lo e instalar a " "wheel contida nele. No entanto, isso só deve ser feito se você quiser " @@ -8585,11 +8644,11 @@ msgstr "Configurar publicação automática no PyPI" #: ../../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 the package " -"from the same job, but it is better to create a separate one to maintain a " -"separation of tasks. This is why, in the previous section, we uploaded the " -"artifact to the temporary storage." +"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 " +"the package from the same job, but it is better to create a separate one " +"to maintain a separation of tasks. This is why, in the previous section, " +"we uploaded the artifact to the temporary storage." msgstr "" "O job que você configurou acima usando GitHub Actions faz o build do seu " "pacote usando seu código. Você ainda precisa fazer upload dele para o PyPI. " @@ -8599,9 +8658,9 @@ msgstr "" #: ../../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." +"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 "" "No novo job, você fará download do pacote de lá e fará upload dele para o " "PyPI. Como o job `build` não faz mais nada, não há possibilidade de o " @@ -8633,8 +8692,8 @@ msgstr "Este job tem dois steps:" #: ../../tutorials/trusted-publishing.md:245 msgid "" -"It uses `download-artifact` to download the artifacts built in the previous " -"job" +"It uses `download-artifact` to download the artifacts built in the " +"previous job" msgstr "Ele usa `download-artifact` para baixar os artifacts build no job anterior" #: ../../tutorials/trusted-publishing.md:247 @@ -8643,8 +8702,8 @@ msgstr "Ele usa `gh-action-pypi-publish` para publicar o pacote no PyPI." #: ../../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!" +"You are almost there!! Now, you just need to enable trusted publishing " +"for your project on PyPI. And then, your work is done!" msgstr "" "Você está quase lá!! Agora, você só precisa habilitar o trusted publishing " "para seu projeto no PyPI. E então, seu trabalho está feito!" @@ -8668,14 +8727,15 @@ msgstr "" #: ../../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 arguments to the `gh-action-pypi-publish` step. While " -"documentation recommends using the GitHub's `secrets` environment for the " -"password/token, in several cases, users were pasting the password directly " -"into the workflow file. Furthermore, accidental leakage of the password or " -"token could allow attackers to publish new packages using your account, " -"until you discover the compromise and revoke the leaked credentials." +"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 " +"arguments to the `gh-action-pypi-publish` step. While documentation " +"recommends using the GitHub's `secrets` environment for the " +"password/token, in several cases, users were pasting the password " +"directly into the workflow file. Furthermore, accidental leakage of the " +"password or token could allow attackers to publish new packages using " +"your account, until you discover the compromise and revoke the leaked " +"credentials." msgstr "" "Antes da criação do trusted publishing, para fazer upload para o PyPI a " "partir de GitHub Actions você precisaria adicionar o nome de usuário e a " @@ -8691,9 +8751,9 @@ msgstr "" msgid "" "To prevent these incidents and improve supply chain security, developers " "created [Trusted Publishing](https://docs.pypi.org/trusted-publishers/). " -"Trusted publishing allows you to register a publishing workflow on PyPI and " -"then map that workflow to an automation workflow (e.g., GitHub Actions) " -"that is allowed to publish the package." +"Trusted publishing allows you to register a publishing workflow on PyPI " +"and then map that workflow to an automation workflow (e.g., GitHub " +"Actions) that is allowed to publish the package." msgstr "" "Para prevenir esses incidentes e melhorar a segurança da cadeia de " "suprimentos, desenvolvedores criaram o [Trusted " @@ -8704,8 +8764,8 @@ msgstr "" #: ../../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" +"You do not need to enter a token or password value in a trusted publisher" +" workflow. It's a secure connection between your" msgstr "" "Você não precisa inserir um valor de token ou senha em um workflow de " "trusted publisher. É uma conexão segura entre seu" @@ -8717,9 +8777,9 @@ msgstr "Trusted Publishing fora do GitHub Actions" #: ../../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 multiple " -"workflows or multiple publishers for the same package. These are advanced " -"uses, out of scope for this lesson." +"Actions. It is also possible to configure a trusted publisher for " +"multiple workflows or multiple publishers for the same package. These are" +" advanced uses, out of scope for this lesson." msgstr "" "O Trusted Publishing suporta outras plataformas de automação, além do " "GitHub Actions. Também é possível configurar um trusted publisher " @@ -8749,8 +8809,9 @@ msgstr "" #: ../../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." +"On the [\"Your projects\" page on " +"PyPI](https://pypi.org/manage/projects/), click \"Manage\" on any project" +" you want to configure." msgstr "" "Na [página \"Your projects\" no PyPI](https://pypi.org/manage/projects/), " "clique em \"Manage\" em qualquer projeto que você queira configurar." @@ -8765,8 +8826,9 @@ msgstr "" #: ../../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." +"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 "" "Esta imagem mostra vários projetos. O botão \"Manage\" está destacado para um " "dos projetos, aquele que queremos configurar o trusted publishing." @@ -8777,16 +8839,16 @@ msgstr "Em seguida, clique em \"Publishing\" na barra lateral do projeto." #: ../../tutorials/trusted-publishing.md:303 msgid "" -"Graphic showing the management page for one project. The \"Publishing\" link " -"in the sidebar is highlighted." +"Graphic showing the management page for one project. The \"Publishing\" " +"link in the sidebar is highlighted." msgstr "" "Gráfico mostrando a página de gerenciamento de um projeto. O link " "\"Publishing\" na barra lateral está destacado." #: ../../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." +"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 "" "Após clicar no botão \"Manage\", chegamos à página do projeto. Na barra " "lateral, temos a opção \"publishing\", conforme destacado aqui." @@ -8794,8 +8856,8 @@ msgstr "" #: ../../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. Filling the GitHub " -"form with the following information:" +"Trusted publishers can be configured via the forms here. Fill in the " +"GitHub form with the following information:" msgstr "" "Isso levará você à página de configuração do publisher para o " "projeto. Trusted publishers podem ser configurados via os formulários aqui. " @@ -8803,8 +8865,8 @@ msgstr "" #: ../../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 " +"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 "" "Owner: o nome da organização GitHub da organização que possui o projeto. Se " @@ -8816,8 +8878,8 @@ msgstr "Repository name: o nome do repositório que contém o projeto." #: ../../tutorials/trusted-publishing.md:316 msgid "" -"Workflow name: Should be `release.yaml` if you followed this guide, it is " -"the workflow we just configured." +"Workflow name: Should be `release.yaml` if you followed this guide, it is" +" the workflow we just configured." msgstr "" "Workflow name: Deve ser `release.yaml` se você seguiu este guia; é o " "workflow que acabamos de configurar." @@ -8832,8 +8894,8 @@ msgstr "" #: ../../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." +"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 "" "Depois de preencher este formulário e clicar em \"Add\", o publisher " "é configurado e pode ser usado para publicar novos releases do seu pacote." @@ -8844,8 +8906,8 @@ msgstr "Workflow de release do GitHub Actions totalmente endurecido" #: ../../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 " +"For better security, it is also recommended to control the permissions of" +" the GitHub token used within each job of the workflow. The permissions " "should be scoped at job level and be as minimal as possible. A workflow " "that configures trusted publishing and also does this is the following:" msgstr "" @@ -8856,17 +8918,17 @@ msgstr "" #: ../../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." +"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 "" "Você pode copiar o conteúdo acima para seu arquivo `release.yaml`. Você só " "precisa atualizar o campo `url:` e configurar o trusted publishing no PyPI." #: ../../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." +"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 "" "O workflow acima deve estar atualizado com as versões atuais das GitHub " "actions. No entanto, é bom habilitar o Dependabot para atualizar as versões " @@ -8879,13 +8941,14 @@ msgstr "Você habilitou o trusted publishing para seu projeto" #: ../../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 have " -"configured builds the package from the exact version of code that we are " -"tagging. This provides a guarantee for your users that the package that you " -"have released does precisely what the code states it does. There is little " -"to no potential for supply chain related vulnerabilities arising from your " -"package! If you have a package that is ready for real-world use on the real " -"PyPI, then you can follow the same steps to publish it securely." +"releases when a new version is being tagged on GitHub. The workflow we " +"have configured builds the package from the exact version of code that we" +" are tagging. This provides a guarantee for your users that the package " +"that you have released does precisely what the code states it does. There" +" is little to no potential for supply chain related vulnerabilities " +"arising from your package! If you have a package that is ready for real-" +"world use on the real PyPI, then you can follow the same steps to publish" +" it securely." msgstr "" "Parabéns!! Você agora configurou seu projeto para fazer releases seguros " "quando uma nova versão for marcada no GitHub. O workflow que configuramos " @@ -8903,16 +8966,16 @@ msgstr "" #: ../../tutorials/trusted-publishing.md:350 msgid "" -"" +"" msgstr "" "" #: ../../tutorials/trusted-publishing.md:351 msgid "" -"" +"" msgstr "" ""