[Python-3000] The grand renaming

[Guido van Rossum]

I don't like renaming PyString to PyBytes right now -- in 2.6 this
sounds wrong since it is publicly known as the str[ing] type. Renaming
only in 3.0 would make merges from the trunk harder. (Unless you have
evidence to the contrary?)

I'm okay with renaming PyBytes -> PyByteArray, PyBuffer ->
PyMemoryView, and the corresponding file renames (make sure to update
all the project files, even for obsolete or minority compilers or
platforms).

There's also a bunch of potential renames in the area of method and
function objects, but I don't have the time to dig up the details.

--Guido

On Dec 30, 2007 8:16 AM, Christian Heimes <lists at cheimes.de> wrote:
> Python 3.0a2 is out and some people are working on backports of Python
> 3.0 features to 2.6. Shouldn't we start to rename the new API functions
> and files to their final names before we back merge code to 2.6?
>
> I'm proposing to change the names and files as following. I'm willing to
> make the necessary changes myself.
>
> API methods:
> PyUnicode - keep the name
> PyBytes - PyByteArray
> PyString - PyBytes
> PyBuffer - PyMemoryView
>
> Files:
> bytesobject.[ch] - bytearrayobject.[ch]
> memoryobject.[ch] - memoryviewobject.[ch]
> stringobject.[ch] - bytesobject.[ch]
>
> Christian
> _______________________________________________
> Python-3000 mailing list
> Python-3000 at python.org
> http://mail.python.org/mailman/listinfo/python-3000
> Unsubscribe: http://mail.python.org/mailman/options/python-3000/guido%40python.org
>



-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)