-
- Notifications
You must be signed in to change notification settings - Fork 264
library/asyncio-task #548
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
library/asyncio-task #548
Conversation
MAJ awecx/python-docs-fr
Correction erreur de build.
Correction erreur de build.
Co-Authored-By: awecx <43954001+awecx@users.noreply.github.com>
Co-Authored-By: awecx <43954001+awecx@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merci pour cette contribution importante.
Je pense qu'il faut mettre futur entre astérisques pour indiquer le concept.
De Christophe. Co-Authored-By: awecx <43954001+awecx@users.noreply.github.com>
Co-Authored-By: awecx <43954001+awecx@users.noreply.github.com>
Co-Authored-By: awecx <43954001+awecx@users.noreply.github.com>
@christopheNan je pense que c'est bon, tu valides ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trois fois rien
Premier jet de library/asyncio-task.
La documentation originale n'est pas très homogène sur la désignation des objets Task et Future. Elle parle parfois de "task", de "Task", d' "objet Task" ou de Task. Idem pour Future.
J'ai traduit "Task" par "tâche" et "Future" par "futur" quand il me semble qu'on désigne le concept plutôt que la classe.
Bonne relecture.