A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2005-August/055822.html below:

[Python-Dev] partition() (was: Remove str.find in 3.0?)

[Python-Dev] partition() (was: Remove str.find in 3.0?)Phillip J. Eby pje at telecommunity.com
Tue Aug 30 17:27:54 CEST 2005
At 04:28 PM 8/30/2005 +0200, Eric Nieuwland wrote:
>I have some use cases with:
>         cut_at = some_str.find(sep)
>         head, tail = some_str[:cut_at], some_str[cut_at:]
>and:
>         cut_at = some_str.find(sep)
>         head, tail = some_str[:cut_at], some_str[cut_at+offset:] # offset !=
>len(sep)
>
>So if partition() [or whatever it'll be called] could have an optional
>second argument that defines the width of the 'cut' made, I would be
>helped enormously. The default for this second argument would be
>len(sep), to preserve the current proposal.

Unrelated comment: maybe 'cut()' and rcut() would be nice short names.

I'm not seeing the offset parameter, though, because this:

     head,__,tail = some_str.cut(sep)
     tail = tail[offset:]

is still better than the original example.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4