RetroSearch Browse

Mon Apr 23 09:59:45 EDT 2001 · http://mail.python.org/pipermail/python-list/2001-April/098240.html

Hello, all -

I'm a Python newbie, I'll admit, but I have a request for a change (or a
request for an explanation of why not to change :).

In the xreadlines unit, I think that once it raises an IndexError for a given
index i, it should raise an IndexError for that same i instead of a
RuntimeError.  The xreadlines object does not have to be considered indexed
"out-of-order" in this case, since the last index did not succeed.

The reason that I want this behaviour is that I'm developing a series of
algorithms that assume that once an IndexError is raised for an index, then
it always will be.

    newbie-already-trying-to-change-the-library-ly y'rs,
    -Steve

 -----  Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web  -----
  http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
   NewsOne.Net prohibits users from posting spam.  If this or other posts
made through NewsOne.Net violate posting guidelines, email abuse at newsone.net

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-list/2001-April/098240.html below:

xreadlines border case