I would like to take whatsnew/3.13.po for this issue (currently untranslated). I will strictly follow the repo's rules and the existing glossary/style guidance, submit a whole-file PR that builds (and lints) cleanly. If there is a higher-priority file, I am happy to switch immediately.
Thanks to @flowdas for curating the glossary, process notes, and steady maintenance ㅡ I will align with those to keep review overhead low.
The translation branch will be changed to 3.14 on October 12th. After that date, we will not accept PRs to the 3.13 branch. Please note that this issue is quite large, so you may need to switch branches during your work.
Thank you for the heads-up @flowdas, and also for the continued stewardship of this repo. Duly noted and truly appreciate the heads up. If the timing slips, I can switch to the 3.14 branch and continue there. I have started with the summary and highlights part; I can open a series of small, self-contained PRs by section if it would make the review process easier (please let me know if there is any kinds of specific preferences). Moreover, if there is a file of higher priority or any other notes (or guidelines) that I should be aware of, please let me know. As I am rather new to open-source env, any kind of feedback (or hopefully a kind of guidance) is much appreciated (and welcomed)! 😊
PS. BTW, as it is rather important documents (that are tightly connected to the PEPs) for the CPython eco-system, I believe such translation (even at the time when 3.14 or higher is up) might be worthwhile to be read in some native languages. 😇🙏
Activity
emmanuel-stone commented on Sep 7, 2025
I would like to take whatsnew/3.13.po for this issue (currently untranslated). I will strictly follow the repo's rules and the existing glossary/style guidance, submit a whole-file PR that builds (and lints) cleanly. If there is a higher-priority file, I am happy to switch immediately.
Thanks to @flowdas for curating the glossary, process notes, and steady maintenance ㅡ I will align with those to keep review overhead low.
flowdas commented on Sep 8, 2025
Thank you @emmanuel-stone .
The translation branch will be changed to 3.14 on October 12th. After that date, we will not accept PRs to the 3.13 branch. Please note that this issue is quite large, so you may need to switch branches during your work.
emmanuel-stone commented on Sep 9, 2025
Thank you for the heads-up @flowdas, and also for the continued stewardship of this repo. Duly noted and truly appreciate the heads up. If the timing slips, I can switch to the 3.14 branch and continue there. I have started with the summary and highlights part; I can open a series of small, self-contained PRs by section if it would make the review process easier (please let me know if there is any kinds of specific preferences). Moreover, if there is a file of higher priority or any other notes (or guidelines) that I should be aware of, please let me know. As I am rather new to open-source env, any kind of feedback (or hopefully a kind of guidance) is much appreciated (and welcomed)! 😊
PS. BTW, as it is rather important documents (that are tightly connected to the PEPs) for the CPython eco-system, I believe such translation (even at the time when 3.14 or higher is up) might be worthwhile to be read in some native languages. 😇🙏
#646 - 부분 번역
#646 - translate whatsnew/3.13.po (wrapping up)
#646 - translate whatsnew/3.13.po (glossary terms consistency)