Hi Erik, thanks a lot for the support. As mentioned in the thread in
Doc-Sig list, IMO it can be great showcase to use identifiers in native
languages, which PEP 3131 was designed for initially, while even now
many beginners don't even know it's possible.
Besides, thanks to the references from
FYI I already post this in Doc-SIG mailing list, as it seems to be more
relevant there.
@Shell, thanks for the reference. Please correct me if I'm wrong, but I
don't think the code standard for Python standard library applies to
sample programs in the tutorials.
Best,
Xuan.
On 4/15/18 7:49
On Mon, Apr 16, 2018 at 4:49 AM, Shell Xu wrote:
> Well, I'm not sure weather or not this is what you're looking for, but pep-8
> (https://www.python.org/dev/peps/pep-0008/) suggest like this:
>
> For Python 3.0 and beyond, the following policy is prescribed for the
> standard library (see PEP 313
Well, I'm not sure weather or not this is what you're looking for, but
pep-8 (https://www.python.org/dev/peps/pep-0008/) suggest like this:
For Python 3.0 and beyond, the following policy is prescribed for the
standard library (see PEP 3131): All identifiers in the Python standard
library MUST use
Excuse me if this was discussed before, but in French and Japanese
translations, all the sample programs seem to have identifiers in
English still. According to "PEP 545 -- Python Documentation
Translations", as I understand .po files are used for translations. May
I ask if there's technical re
