Basically, Python has the "buffer" object which is a 0-copy view of some memory area (lets an object expose itself as a bytes array of sorts). It's always been plagued with a number of issues.
In Python 3, `buffer` was removed and replaced with `memoryview`, which was backported to Python 2.7. But in said Python 2.7, `buffer` and `memoryview` both exist and fill very similar need so e.g. older libraries will likely return a buffer which newer code will want to use as a memoryview. No such luck, they're not compatible.
2.7.4 fixes that so you can get a memoryview from a buffer.
And you can create a memoryview which is the "new" and more flexible buffer interface: http://docs.python.org/2/library/stdtypes.html#typememoryvie...
You can get a buffer of a string:
>>> buffer("foo")
<read-only buffer for 0x1005a5ee0, size -1, offset 0 at 0x10054f270>
and a view of a string: >>> memoryview("foo")
<memory at 0x100574d60>
but when you get this unhelpful and really stupid result: >>> memoryview(buffer("foo"))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: cannot make memory view because object does not have the buffer interface
2.7.4 fixed this so it actually works and you can get a memoryview out of an old buffer.