[Python-3000] Droping find/rfind? (original) (raw)

Terry Reedy tjreedy at udel.edu
Thu Aug 24 02:27:26 CEST 2006

"Brian Holmes" <holmesbj.dev at gmail.com> wrote in message news:e3c648160608222346g4587d55eiff521787ca4d915f at mail.gmail.com...

Even after reading Terry Reedy's arguments, I don't see why we need to >remove this option.

Since this is my first post in this current thread, you either meant someone else or are remembering my posts about in- and out-of-band error signaling from the last time we discussed this.

Let both exist. I'd prefer grandfathering something like this and leaving it >in, even if it wouldn't be there had known everything from the start.

One point of the 3.0 cleanup is to remove or change things that we definitely would not do today. When I learned Python, both the find/match duplication and the in-band same-type Unix/Cism -1 return stuck out to me like sore thumbs. So I would either

  1. just remove find() and leave match(); or
  2. change find()'s error return to None, and remove index();

or possibly consider Josiah's idea of 3. remove both in favor of an index generator.

I am strongly -1 on leaving both as are.

Terry Jan Reedy

More information about the Python-3000 mailing list