Fix syntax warning over comparison of literals using is. #178
Conversation
|
The same problem. Please merge this PR :) |
| @@ -107,7 +107,7 @@ class _ConnectionDeadError(Exception): | |||
|
|
|||
|
|
|||
| class Client(threading.local): | |||
| """Object representing a pool of memcache servers. | |||
| r"""Object representing a pool of memcache servers. | |||
There was a problem hiding this comment.
r"""Object representing a pool of memcache servers.
it's correct to start with the letter "r" ?
There was a problem hiding this comment.
I believe this is valid.
Both string and bytes literals may optionally be prefixed with a letter 'r' or 'R'; such strings are called raw strings and treat backslashes as literal characters. As a result, in string literals, '\U' and '\u' escapes in raw strings are not treated specially. Given that Python 2.x’s raw unicode literals behave differently than Python 3.x’s the 'ur' syntax is not supported.
source: https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals
There was a problem hiding this comment.
I'm going to remove that \ in the docstring which should resolve this without the 'r'. I don't believe the \ is needed, it probably was an artifact of a continuation line. Your is -> == is included in a patch I just accepted, so I'm going to commit this change and close this PR as fixed, thank you for the PR!
|
is -> == done by another PR, removing spurious \ in docstring rather than converting to r string. |
Fixes #176