Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #86189 > unrolled thread

Re: Unrecognized backslash escapes in string literals

Started byBen Finney <ben+python@benfinney.id.au>
First post2015-02-23 14:35 +1100
Last post2015-02-23 14:35 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#86189 — Re: Unrecognized backslash escapes in string literals

FromBen Finney <ben+python@benfinney.id.au>
Date2015-02-23 14:35 +1100
SubjectRe: Unrecognized backslash escapes in string literals
Message-ID<mailman.19051.1424662522.18130.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web