[CuriouslyC]

Using a consistent string delimiter has value: if you search for ['foo'] you will find all instances of the string foo. With inconsistent delimiters, you better have a single canonical 'foo' in your project or you're going to run into problems.

[preg_match]

The inverse is also true (speaking from PHP, I'm not 100% familiar with Python semantics). If we use '' where appropriate, then we know absolutely no escaping and no interpolation is done. That has value. If we use "" for everything, then we have to examine the string for interpolation or for escaping.

[maratc]

See if you know where this leads before clicking on it: https://xkcd.com/208/

[CuriouslyC]

So your argument is that your freedom to use whatever string delimiter you want (remember that ''', """, ` and even weird unicode glyphs are valid in many languages) is worth forcing other engineers on the team to know all valid string delimiters and remember to use the right regex to account for all possible weirdo choices?

[maratc]

My argument is that searching for \bfoo\b will produce all the results you want.

Python was designed from the start so that 'foo' and "foo" are equal. It also worked like that for 30 years or so. This has not been an issue in these 30 years. But then someone came with an opinion that one of them is better than the other.

[CuriouslyC]

\bfoo\b will produce noisy results. People have been pushing linting rules that force a single consistent choice of string delimiters since at least 2010 when Python went from a cute academic language to a real industry workhorse.

[maratc]

> \bfoo\b will produce noisy results.

Add a look-behind for '[' and a look-ahead for ']' and you'll be fine.

[jason1cho]

When a string contains strange characters, how do you enforce the single consistent delimiter?

You probably haven't written diverse enough code.