Update about_py.md

[Honaminto]

Review of the French translation of About These Lectures

1. Relative Popularity section – the English insertion "one of the most -- if not the most --" doesn't translate naturally into French with this construction, since "l'un des langages les plus populaires" and "le langage le plus populaire" need different grammatical structures.

   • Before: Python est l'un des -- si ce n'est le -- langages de programmation les plus populaires.
   • After: Python est l'un des langages de programmation les plus populaires, si ce n'est le plus populaire.

2. NumPy Alternatives section – the placement of intégrés was ambiguous and could be read as modifying only opérations sur les tableaux rather than both array types and array operations.

   • Before: Des bibliothèques telles que JAX, PyTorch et CuPy disposent également de types de tableaux et d'opérations sur les tableaux intégrés qui peuvent être très rapides et efficaces.
   • After: Des bibliothèques telles que JAX, PyTorch et CuPy intègrent également des types de tableaux et des opérations sur les tableaux qui peuvent être très rapides et efficaces.

3. Graphics section – terminology consistency with the figure caption immediately below it (Exemple de tracé de contour).

   • Before: des tracés, des histogrammes, des images de contours, des graphiques 3D, des diagrammes à barres, etc.
   • After: des tracés, des histogrammes, des tracés de contours, des graphiques 3D, des diagrammes à barres, etc.

4. Graphics section – capitalization of Matplotlib for consistency with the rest of the document.

   • Before: une interface de haut niveau pour matplotlib
   • After: une interface de haut niveau pour Matplotlib

[github-actions]

📖 Netlify Preview Ready!

Preview URL: https://pr-84--verdant-toffee-3261a8.netlify.app

Commit: c34167f

📚 Changed Lectures

• about_py

---

Build Info

• Workflow: Build Project [using jupyter-book]

[Honaminto]

Hey Matt, I have a quick question on convention. I've noticed the chapters aren't fully consistent about whether comments and docstrings inside code cells get translated into French. about_py.md already has French comments like # Charger la bibliothèque, but some other chapters leave comments and docstrings in English. Should we translate explanatory comments and docstrings consistently going forward, while leaving code identifiers, API names, and executable output strings as-is? Want to make sure I'm applying the same rule across chapters rather than deciding it one by one.

[mmcky]

Thanks, Emile, good question. The inconsistency is ours: the first translation translated the # comments in most lectures but not all, and left nearly all docstrings in English. Your rule is a good one: translate explanatory comments and docstrings, and leave code identifiers, API names and executable output strings as they are. I've opened #88 to settle it for the whole edition, since it also decides how the translation tool drafts each new lecture, and added you to it. Please add anything there, for example a case where you think a comment should stay in English. For about_py, keep the comments as you have them; if #88 changes anything, I'll make the change on this pull request and list it for you to check.

I've also pushed one commit here that puts back the non-breaking spaces before : ; ! ?. GitHub's web editor replaces them with ordinary spaces, and they can't be seen there, so there's nothing for you to do about them. When you're done with this lecture, just say so here.