Re: Unrecognized backslash escapes in string literals

From	Ben Finney <ben+python@benfinney.id.au>
Subject	Re: Unrecognized backslash escapes in string literals
Date	2015-02-23 14:35 +1100
References	<CAPTjJmqx3s1a0LL4RLgVB1PsOfyF9ryy6nwHwOwrQs1Zx2Hd-Q@mail.gmail.com> <85vbit73jd.fsf@benfinney.id.au> <CAPTjJmqY0ZMr-xMgJ1hsBc1mPMeML0q-QuRsU0Mnm8sngU64yg@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.19051.1424662522.18130.python-list@python.org> (permalink)

Show all headers | View raw

Chris Angelico <rosuav@gmail.com> writes:

> That said, though, there's probably a lot of code out there that
> depends on backslashes being non-special, so it's quite probably
> something that can't be changed. But it'd be nice to be able to turn
> on a warning for it.

If you're motivated to see such warnings, an appropriate place to
implement them would be in PyLint or another established static code
analysis tool.

-- 
 \            “The whole area of [treating source code as intellectual |
  `\    property] is almost assuring a customer that you are not going |
_o__)               to do any innovation in the future.” —Gary Barnett |
Ben Finney

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Unrecognized backslash escapes in string literals Ben Finney <ben+python@benfinney.id.au> - 2015-02-23 14:35 +1100

csiph-web