On Friday, May 5, 2023 at 11:10:59 PM UTC+1 tbp1...@gmail.com wrote:
On Friday, May 5, 2023 at 6:01:33 PM UTC-4 Edward K. Ream wrote:
On Fri, May 5, 2023 at 3:24 PM jkn wrote:
https://peps.python.org/pep-0008/
"This document gives coding conventions for the Python code *comprising the
On Friday, May 5, 2023 at 6:01:33 PM UTC-4 Edward K. Ream wrote:
On Fri, May 5, 2023 at 3:24 PM jkn wrote:
https://peps.python.org/pep-0008/
"This document gives coding conventions for the Python code *comprising the
standard library* in the main Python distribution"
Pep 8 contains many
On Fri, May 5, 2023 at 3:24 PM jkn wrote:
https://peps.python.org/pep-0008/
>
> "This document gives coding conventions for the Python code *comprising
> the standard library* in the main Python distribution"
>
Pep 8 contains many caveats and subtle points. I don't want to debate those
:-)
The
I've mentioned this before, but note the wording at beginning of PEP-8:
https://peps.python.org/pep-0008/
"This document gives coding conventions for the Python code *comprising the
standard library* in the main Python distribution"
*emphasis* mine.
On Friday, May 5, 2023 at 2:36:23 PM
On Fri, May 5, 2023 at 8:22 AM Thomas Passin wrote:
> +1!
>
:-) I've considered this several times. Apparently I need constant
reminding that this is not a clever idea!
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe
+1!
On Friday, May 5, 2023 at 9:20:09 AM UTC-4 Edward K. Ream wrote:
> I recently asked myself whether Leo's code should use Pep 8 naming
> conventions. The short answer is an emphatic NO! Such changes would have
> massive impacts on LeoJS and existing Leo scripts.
>
> I entertained this
I recently asked myself whether Leo's code should use Pep 8 naming
conventions. The short answer is an emphatic NO! Such changes would have
massive impacts on LeoJS and existing Leo scripts.
I entertained this question for two reasons:
- Leo could define an *@alias* decorator to retain
