Christian Heimes schrieb: >> You mean 'formerly', not 'formally' :-) I prefer to just call these by >> their C names (PyString) to be precise, as the C names aren't changing >> (at least not yet ;-). > > Oh, formerly ... right. The current state of the names is very > confusing. It's going to cost me some cups of coffee. > > str - PyUnicode > bytes - PyString > buffer - PyBytes
I agree that this is quite confusing. The PyBytes functions can be changed without a thought since they aren't 2.x heritage. Since PyBuffer_* is already taken, what about a PyByteBuffer_ prefix? PyString_ could then be renamed to PyByteString_. PyUnicode might be allowed to stay... Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. _______________________________________________ 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
