On Thu, Aug 27, 2009 at 14:15, Jake McGuire<mcguire@google.com> wrote:

The python documentation says that the read() and write() methods on array objects have been deprecated since 1.5.1.  I assume this is because their semantics are almost the exact opposite of read() and write() on a file-like object; array.read() reads data from a file into the array and array.write() writes data from the array to a file. This causes fatal confusion in code that checks for the existence of read() and write() to determine whether an object is file-like.  Code such as httplib. What is the timeline for removing these methods from array?  It has been 11 years now.

They are gone from Python 3.x, so they have been removed where it counts. Bothering with 2.x is not worth it at this point.

On Thu, Aug 27, 2009 at 14:15, Jake McGuire<mcguire@google.com> wrote:

The python documentation says that the read() and write() methods on array objects have been deprecated since 1.5.1.  I assume this is because their semantics are almost the exact opposite of read() and write() on a file-like object; array.read() reads data from a file into the array and array.write() writes data from the array to a file. This causes fatal confusion in code that checks for the existence of read() and write() to determine whether an object is file-like.  Code such as httplib. What is the timeline for removing these methods from array?  It has been 11 years now.

They are gone from Python 3.x, so they have been removed where it counts. Bothering with 2.x is not worth it at this point.