[Python-checkins] python/nondist/peps pep-0292.txt,1.4,1.5
bwarsaw@users.sourceforge.net
bwarsaw@users.sourceforge.net
Fri, 12 Jul 2002 16:21:10 -0700
Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv18468
Modified Files:
pep-0292.txt
Log Message:
Added a section containing Guido's list of real issues.
Index: pep-0292.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0292.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** pep-0292.txt 23 Jun 2002 02:20:50 -0000 1.4
--- pep-0292.txt 12 Jul 2002 23:21:08 -0000 1.5
***************
*** 302,305 ****
--- 302,330 ----
+ BDFL Weathervane
+
+ Guido lays out[3] what he feels are the real issues that need to
+ be fleshed out in this PEP:
+
+ - Compile-time vs. run-time parsing. I've become convinced that
+ the compiler should do the parsing: this is the only way to make
+ access to variables in nested scopes work, avoids security
+ issues, and makes it easier to diagnose errors (e.g. in
+ PyChecker).
+
+ - How to support translation. Here the template must be replaced
+ at run-time, but it is still desirable that the collection of
+ available names is known at compile time (to avoid the security
+ issues).
+
+ - Optional formatting specifiers. I agree with Lalo that these
+ should not be part of the interpolation syntax but need to be
+ dealt with at a different level. I think these are only
+ relevant for numeric data. Funny, there's still a
+ (now-deprecated) module fpformat.py that supports arbitrary
+ floating point formatting, and string.zfill() supports a bit of
+ integer formatting.
+
+
References
***************
*** 309,312 ****
--- 334,340 ----
[2] Identifiers and Keywords
http://www.python.org/doc/current/ref/identifiers.html
+
+ [3] Guido's python-dev posting from 21-Jul-2002
+ http://mail.python.org/pipermail/python-dev/2002-July/026397.html