CPYTHON_CLONE := ../cpython/

SPHINX_CONF := $(CPYTHON_CLONE)/Doc/conf.py

LANGUAGE := es

VENV := ~/.venvs/python-docs-i18n/

PYTHON := $(shell which python3)

MODE := html

BRANCH = 3.7

COMMIT =

JOBS = auto

.PHONY: all

all: $(SPHINX_CONF) $(VENV)/bin/activate

ifneq "$(shell cd $(CPYTHON_CLONE) 2>/dev/null && git describe --contains --all HEAD)" "$(BRANCH)"

$(warning "Your ../cpython checkout may be on the wrong branch, got $(shell cd $(CPYTHON_CLONE) 2>/dev/null && git describe --contains --all HEAD) expected $(BRANCH)")

mkdir -p $(CPYTHON_CLONE)/locales/$(LANGUAGE)/

ln -nfs $(shell $(PYTHON) -c 'import os; print(os.path.realpath("."))') $(CPYTHON_CLONE)/locales/$(LANGUAGE)/LC_MESSAGES

$(MAKE) -C $(CPYTHON_CLONE)/Doc/ VENVDIR=$(VENV) PYTHON=$(PYTHON) SPHINXOPTS='-qW -j$(JOBS) -D locale_dirs=../locales -D language=$(LANGUAGE) -D gettext_compact=0 -D latex_engine=xelatex -D latex_elements.inputenc= -D latex_elements.fontenc=' $(MODE)

$(SPHINX_CONF):

git clone --depth 1 --branch $(BRANCH) https://github.com/python/cpython.git $(CPYTHON_CLONE)

[ -n "$(COMMIT)" ] && (i=1; while ! $$(git -C $(CPYTHON_CLONE) checkout $(COMMIT)); do i=$$((i * 2)); git -C $(CPYTHON_CLONE) fetch --depth $$i; done) || true

.PHONY: upgrade_venv

upgrade_venv:

$(MAKE) -C $(CPYTHON_CLONE)/Doc/ VENVDIR=$(VENV) PYTHON=$(PYTHON) venv

$(VENV)/bin/activate:

$(MAKE) -C $(CPYTHON_CLONE)/Doc/ VENVDIR=$(VENV) PYTHON=$(PYTHON) venv

.PHONY: progress

progress:

@python3 -c 'import sys; print("{:.1%}".format(int(sys.argv[1]) / int(sys.argv[2])))' \

$(shell msgcat *.po */*.po | msgattrib --translated | grep -c '^msgid') \

$(shell msgcat *.po */*.po | grep -c '^msgid')

.PHONY: merge

merge: upgrade_venv

ifneq "$(shell cd $(CPYTHON_CLONE) 2>/dev/null && git describe --contains --all HEAD)" "$(BRANCH)"

$(error "You're merging from a different branch:" "$(shell cd $(CPYTHON_CLONE) 2>/dev/null && git describe --contains --all HEAD)" vs "$(BRANCH)")

(cd $(CPYTHON_CLONE)/Doc; rm -f build/NEWS)

(cd $(CPYTHON_CLONE); $(VENV)/bin/sphinx-build -Q -b gettext -D gettext_compact=0 Doc pot/)

find $(CPYTHON_CLONE)/pot/ -name '*.pot' |\

while read -r POT;\

do\

PO="./$$(echo "$$POT" | sed "s#$(CPYTHON_CLONE)/pot/##; s#\.pot\$$#.po#")";\

.PHONY: fuzzy

fuzzy:

for file in *.po */*.po; do echo $$(msgattrib --only-fuzzy --no-obsolete "$$file" | grep -c '#, fuzzy') $$file; done | grep -v ^0 | sort -gr

Translation of the Python Documentation — es

.. image:: https://travis-ci.org/python/python-docs-es.svg?branch=3.7

:target: https://travis-ci.org/python/python-docs-es

Documentation Contribution Agreement

NOTE REGARDING THE LICENSE FOR TRANSLATIONS: Python's documentation is

maintained using a global network of volunteers. By posting this

project on Transifex, Github, and other public places, and inviting

you to participate, we are proposing an agreement that you will

provide your improvements to Python's documentation or the translation

of Python's documentation for the PSF's use under the CC0 license

(available at

https://creativecommons.org/publicdomain/zero/1.0/legalcode). In

return, you may publicly claim credit for the portion of the

translation you contributed and if your translation is accepted by the

PSF, you may (but are not required to) submit a patch including an

appropriate annotation in the Misc/ACKS or TRANSLATORS file. Although

nothing in this Documentation Contribution Agreement obligates the PSF

to incorporate your textual contribution, your participation in the

Python community is welcomed and appreciated.

You signify acceptance of this agreement by submitting your work to

the PSF for inclusion in the documentation.

Contributing to the Translation

How to Contribute

You can contribute using:

- Github

- `transifex <https://www.transifex.com/python-doc/public/>`_

- Or just by opening `an issue on github <https://github.com/python/python-docs-esfr/issues>`_

Contributing using Github

Prerequisites:

- A `github account <https://github.com/join>`_.

- ``git`` `installed <https://help.github.com/articles/set-up-git/>`_ (for windows, see

https://gitforwindows.org/).

- A ``.po`` file editor (Use `poedit <https://poedit.net/>`_

if you don't already have one).

Let's start:

You'll need to fork the `python-docs-es

<https://github.com/python/python-docs-es>`_ clicking its ``Fork``

button. This creates a copy of the whole project on your github

account: a place where you have the rights to do modifications.

Step by step:

.. code-block:: bash

All the translations must be made on the latest release.

We never translate on an oldest version, by example, the latest python release

is python 3.7, we don't want to translate directly on the python 3.5 release.

If needed translations would be backported on the oldest versions by the

`documentation team <https://www.python.org/dev/peps/pep-8015/#documentation-team>`.

Now you're ready to start a work session, each time you'll start a new task, start here:

.. code-block:: bash

You may have noted that this looks like a triangle, with a missing segment:

- You're fetching from upstream (public common repo on github)

- You're pushing to origin (your clone on github)

So yes it's the work of someone to add the last segment, from your

origin to the public upstream, to "close the loop", that's the role of

the people who merges pull requests after proofreading them.

You may also have noted you never ever commit on a version branch

(``3.6``, ``3.7``, ...), only pull from them, consider them read-only

you'll avoid problems.

What to translate

You can start with easy tasks like reviewing fuzzy entries to help

keeping the documentation up to date (find them using ``make fuzzy``).

You can also proofread already translated entries, and finally

translate untranslated ones (find them using ``make todo``)..

- Do not translate content of ``:ref:...`` and ``:term:...``

- Put english words, if you have to use them, in *italics* (surrounded

by stars).

- If you translate a link title, please translate the link too

(typically if it's Wikipedia and the article has a translation). If

no translation of the target exists, do not translate the

title.

Where to get help

Translation Resources

Glossary

For consistency in our translations, here are some propositions and

reminders for frequent terms you'll have to translate, don't hesitate

to open an issue if you disagree.

To easily find how a term is already translated in our documentation,

you may use

`find_in_po.py <https://gist.github.com/JulienPalard/c430ac23446da2081060ab17bf006ac1>`_.

Term Proposed Translation

-like

abstract data type

argument

backslash

bound

bug

built-in

call stack

debugging

deep copy

double quote

e.g.

garbage collector

identifier

immutable

installer

interpreter

library

list comprehension

little-endian, big-endian

mutable

namespace

parameter

prompt

raise

regular expression

return

simple quote

socket

statement

subprocess

thread

underscore

expression

Simplify git diffs

Git diffs are often crowded with useless line number changes, like:

.. code-block:: diff

To tell git they are not usefull information, you can do the following

after ensuring ``~/.local/bin/`` is in your ``PATH``.

.. code-block:: bash