Python | Ways to split a string in different ways

| | | | |

Examples :

Input: Paras_Jain_Moengage_best
Output: [’Paras’, ’Paras_Jain’, ’Paras_Jain_Moengage’, ’Paras_Jain_Moengage_best’]

Input: chunky_2808_GFG_Codechef
Output: [’chunky’, ’chunky_2808 , ’chunky_2808_GFG’, ’chunky_2808_GFG_Codechef’]

Here are some ways to do it.

Method # 1: Using iteration

# Python code for splitting a string in a substring fashion

# Initialize input

Input = "Geeks_for_geeks_is_best"

# Divide —å initialization

split_string = Input . split ( ’_’ )

# Initialize the output list

Output = []

# Iteration

for a in range ( len (split_string)):

temp = split_string [: a + 1 ]

temp = " _ " . join (temp)

Output.append (temp)

# printout

print (Output)


[ ’Geeks’, ’Geeks_for’, ’Geeks_for_geeks’, ’Geeks_for_geeks_is’, ’Geeks_for_geeks_is_best’]

Method 2: Using Itertools

# Python code to split the string in a substring fashion

# Import

from itertools import accumulate

# Initialize input

Input = "Geeks_for_geeks_is_best"

# Usage to accumulate

Output = [ * accumulate ( Input . split ( ’_’ ), lambda temp1, temp2:

’_’ . join ([temp1, temp2])),] < / p>

# Printout

print (Output)


[’Geeks’, ’Geeks_for’, ’Geeks_for_geeks’, ’Geeks_for_geeks_is’, ’Geeks_for_geeks_is_best’]

Python | Ways to split a string in different ways accumulate: Questions

Python | Ways to split a string in different ways join: Questions

Why is it string.join(list) instead of list.join(string)?

5 answers

Evan Fosmark By Evan Fosmark

This has always confused me. It seems like this would be nicer:

my_list = ["Hello", "world"]
# Produce: "Hello-world"

Than this:

my_list = ["Hello", "world"]
# Produce: "Hello-world"

Is there a specific reason it is like this?


Answer #1

It"s because any iterable can be joined (e.g, list, tuple, dict, set), but its contents and the "joiner" must be strings.

For example:

"_".join(["welcome", "to", "stack", "overflow"])
"_".join(("welcome", "to", "stack", "overflow"))

Using something other than strings will raise the following error:

TypeError: sequence item 0: expected str instance, int found


Answer #2

This was discussed in the String methods... finally thread in the Python-Dev achive, and was accepted by Guido. This thread began in Jun 1999, and str.join was included in Python 1.6 which was released in Sep 2000 (and supported Unicode). Python 2.0 (supported str methods including join) was released in Oct 2000.

  • There were four options proposed in this thread:
    • str.join(seq)
    • seq.join(str)
    • seq.reduce(str)
    • join as a built-in function
  • Guido wanted to support not only lists and tuples, but all sequences/iterables.
  • seq.reduce(str) is difficult for newcomers.
  • seq.join(str) introduces unexpected dependency from sequences to str/unicode.
  • join() as a built-in function would support only specific data types. So using a built-in namespace is not good. If join() supports many datatypes, creating an optimized implementation would be difficult, if implemented using the __add__ method then it would ve O(n¬≤).
  • The separator string (sep) should not be omitted. Explicit is better than implicit.

Here are some additional thoughts (my own, and my friend"s):

  • Unicode support was coming, but it was not final. At that time UTF-8 was the most likely about to replace UCS2/4. To calculate total buffer length of UTF-8 strings it needs to know character coding rule.
  • At that time, Python had already decided on a common sequence interface rule where a user could create a sequence-like (iterable) class. But Python didn"t support extending built-in types until 2.2. At that time it was difficult to provide basic iterable class (which is mentioned in another comment).

Guido"s decision is recorded in a historical mail, deciding on str.join(seq):

Funny, but it does seem right! Barry, go for it...
Guido van Rossum


Answer #3

Because the join() method is in the string class, instead of the list class?

I agree it looks funny.


Historical note. When I first learned Python, I expected join to be a method of a list, which would take the delimiter as an argument. Lots of people feel the same way, and there’s a story behind the join method. Prior to Python 1.6, strings didn’t have all these useful methods. There was a separate string module which contained all the string functions; each function took a string as its first argument. The functions were deemed important enough to put onto the strings themselves, which made sense for functions like lower, upper, and split. But many hard-core Python programmers objected to the new join method, arguing that it should be a method of the list instead, or that it shouldn’t move at all but simply stay a part of the old string module (which still has lots of useful stuff in it). I use the new join method exclusively, but you will see code written either way, and if it really bothers you, you can use the old string.join function instead.

--- Mark Pilgrim, Dive into Python


Best laptop for Fortnite


Best laptop for Excel


Best laptop for Solidworks


Best laptop for Roblox


Best computer for crypto mining


Best laptop for Sims 4


Best laptop for Zoom


Best laptop for Minecraft


Latest questions


psycopg2: insert multiple rows with one query

12 answers


How to convert Nonetype to int or string?

12 answers


How to specify multiple return types using type-hints

12 answers


Javascript Error: IPython is not defined in JupyterLab

12 answers



Python OpenCV | cv2.putText () method

numpy.arctan2 () in Python

Python | os.path.realpath () method

Python OpenCV | () method

Python OpenCV cv2.cvtColor () method

Python - Move item to the end of the list

time.perf_counter () function in Python

Check if one list is a subset of another in Python

Python os.path.join () method