Other syntax ideas and feature ideas for Python3.0 .
Contents
- declaring parameter and variable types
- script to translate python source from one version to one other
- Different regular expressions modules for bytes and unicode text
- New binary operator symbols d e `
- Optional Static Typing / Adaptation
- Lambda / Anonymous Methods / Closures
- Print as builtin instead of a statement
- ".." Sequences, Custom Infix Operators
- Improved default value logic for Dictionaries
- Better boolean logic
- Disallow calling class methods from instances
- Simplify the syntax for raising exceptions
- Fix implementation of in-place operators
- Remove the distinction between data and non-data decriptors
- Reconsider the inclusion of __slots__ or re-evaluate its implementation
- Extra operators for strings and lists
- Move rarely-used builtins to the library
- Don't remove callable()
- Make API of set, list, dict more consistent
- Make copy and deepcopy built-ins, replace copy methods by __copy__
- Don't remove cmp() and __cmp__
- Builtin Literal for sets
- Make extended function call syntax more iterator friendly
- Require __iter__() for DictMixin instead of keys()
- Raise the level of os module functions
- Parameterize functions that hardcode stdout or stderr
- Module interface
- Stronger Distinction between Tuples & Lists
- Unifying generators
- Replace Integer Masks with Sets
- Replace abs() with | |
- Require Parens for Tuple Definition
- Remove [<listcomp>] syntax in favor of list(<genexp>) syntax
- Move builtins to be methods on the types they apply to:
- Default to assign class object rather than class reference
- Unicode identifier
- Remove support for complex numbers
- Reserve some keywords for futur extensions
- Simplify the filename search when importing
- Increment operator
declaring parameter and variable types
It may be easier, reduce bugs, offers intelli-sense like in Microsoft Visual Studio. All of that could reduce development-time.
script to translate python source from one version to one other
does any script (will) exists, to translate code, form python 2.3 to python 2.4 or from python 2.3 to 2.4?
Different regular expressions modules for bytes and unicode text
I do not allways understand whether re module is designed for text or binary? The struct module for interfacing with binary files, or network datagrams might be improved by adding some of the regular expressions facilities, such as split.
Two modules like re might be a good thing, one binary oriented, and the other unicode oriented: * one for binary data, with some of the re and struct facilities adapted to bytes. ... with eventually stuff like reading a two bytes encoded size, then a buffer from the previous size ... * one for unicode/text regular expression should be in some way text/unicode oriented.... like ICU portable one.
For example, the ICU one provide the following patterns:
- \N{UNICODE CHARACTER NAME} Correspond au caractère nommé
- \p{UNICODE PROPERTY NAME} Correspond au carctère doté de la propriété Unicode spécifiée.
- \P{UNICODE PROPERTY NAME} Correspond au carctère non doté de la propriété Unicode spécifiée.
- \s Correspond à un caractère séparateur. un séparateur est définit comme [\t\n\f\r\p{Z}].
- \uhhhh Correspond à un caractère dont la valeur hexa est hhhh.
- \Uhhhhhhhh Correspond à un caractère dont la valeur hexa est hhhhhhhh. Exactement huit chiffres héxa doivent être fournis, même si le code point unicode le plus grand est \U0010ffff.
- the portable library "International Components for Unicode" might be used. It might be largely available as it is existing in debian distribution.
related pep:
New binary operator symbols d e `
these operators d e ` should be added to the language having the following meaning:
<= >= !=
this should improve readibility (and make language more accessible to beginners).
This should be an evolution similar to the digraphe and trigraph (digramme et trigramme) from C and C++ languages. In C, "<%" or "??<" mean "{" such as.
gcc -trigraphs a.c
??=include <stdio.h>
int main(int argc, char *argv ??( ??) )
??<
printf ("hello world\n");
??>See also: * The <> operator: use != instead http://www.python.org/peps/pep-3000.html#id54
From an aesthetic point of view, I would very much