Anj-A <2017...@gmail.com> added the comment:
Hey, if there is no bug here, could we get this issue closed?
Alternatively, I'd be interested in doing the required change in
documentation/error type if that's seen to be the right solution.
Personally, I think returning False in
Change by Anj-A <2017...@gmail.com>:
--
keywords: +patch
pull_requests: +16563
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17047
___
Python tracker
<https://bugs.python.or
Anj-A <2017...@gmail.com> added the comment:
Hey, I've done the change and opened a pull request for it (I'm working with
Ben and I've let him know)
--
nosy: +Anj-A
___
Python tracker
<https://bu
Change by Anj-A <2017...@gmail.com>:
--
keywords: +patch
pull_requests: +16560
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17047
___
Python tracker
<https://bugs.python.or
Anj-A <2017...@gmail.com> added the comment:
Hey, I'm not exactly clear what the required fix is here and would appreciate
some guidance, is it in the documentation or in the way the error is handled?
--
___
Python tracker
<https://b
Anj-A <2017...@gmail.com> added the comment:
Hi all, I'm a newcomer interested in doing a small fix. Wondering if anyone's
working on this at the moment?
----------
nosy: +Anj-A
___
Python tracker
<https://bugs.py