Thomas Wouters wrote: > 1) It (passively) promotes supporting only simple slicing, > as observed by the builtin types only supporting extended > slicing many years after extended slicing was introduced
Should that read "...only supporting simple slicing..."? > The proposed solution, as implemented in the p3yk-noslice > SVN branch, gets rid of the simple slicing methods and > PyType entries. The simple C API (using ``Py_ssize_t`` > for start and stop) remains, but creates a slice object > as necessary instead. Various types had to be updated to > support slice objects, or improve the simple slicing case > of extended slicing. Am I reading this correctly, that: since the "simple C API remains", one can still write S[3:8] with only one colon and have it work as before? Or would it have to be rewritten to include two colons? Robert Brewer [EMAIL PROTECTED]
_______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
