Skip to content

/ python-docs-es

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Actualizar rama 3.7 con últimos cambios de 3.7.7 #334

Open
raulcd opened this issue May 23, 2020 · 4 comments
Open

Actualizar rama 3.7 con últimos cambios de 3.7.7 #334

raulcd opened this issue May 23, 2020 · 4 comments

Comments

@raulcd
Copy link
Collaborator

@raulcd raulcd commented May 23, 2020 •
edited

There are some paragraphs:

Besides the while statement just introduced, Python uses the usual flow control statements known from other languages, with some twists.

That appear incorrectly because we haven't updated the last 3.7 version and applied the backports that were done:
python/cpython@8b907a8
This was backported from 3.8 and is translated there.
It can be seen on the published documentation here:
https://docs.python.org/es/3.7/tutorial/controlflow.html#more-control-flow-tools)
@humitos
Copy link
Collaborator

@humitos humitos commented May 23, 2020

Shouldn't we tell them to disable 3.7 online version and just stick with 3.8?
@raulcd
Copy link
Collaborator Author

@raulcd raulcd commented May 23, 2020

I don't think so, lots of changes appear directly if we just merge. For example the tutorial is almost all translated on python3.6 just because the different paragraphs haven't changed and it just picks them up:
https://docs.python.org/es/3.6/tutorial/
I think we can just use that there's not that many releases and these process should be done only once a new release is created.
@clacri
Copy link
Collaborator

@clacri clacri commented Sep 27, 2020

@raulcd esta issue tiene que seguir abierta o está ya outdated?
@humitos
Copy link
Collaborator

@humitos humitos commented Oct 6, 2020

@clacri entiendo que no, lo que reporta @raulcd sigue pasando. Hay que actualizar las ramas anteriores con lo nuevo que tenemos. Ellos construyen todas las versiones aunque no las tengamos 100% traducidas. Sin embargo, hay mucho texto que se comparte entre todas las versiones y haciendo un "merge loco" de las versiones nuevas hacia atrás podemos tener las más viejas con más párrafos traducidos.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@humitos @raulcd @clacri
You can’t perform that action at this time.