| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Updating _FATAL_ERROR_IGNORE worries me: I don't think I understand all consequences of this PR. Could you please elaborate more?
Sorry, something went wrong.
|
_FATAL_ERROR_IGNORE is a tuple of exceptions which doesn't generate noisy loop.call_exception_handler() if connection cannot be established (see https://github.com/python/asyncio/blob/master/asyncio/selector_events.py#L633) for usage example. |
Sorry, something went wrong.
|
Makes sense. Would you be able to write a unittest for this? |
Sorry, something went wrong.
|
@asvetlov If you want this in 3.6.1 you need to add a unittest and resubmit this PR to python/cpython today. |
Sorry, something went wrong.
|
@1st1 ok, so 3.6.1 is going out after today? btw would it also include the latest version of zlib as well because it has updated a to version above 1.2.8 this year to fix bugs and stuff. |
Sorry, something went wrong.
Yes. Re zlib - not sure, please check on GH or bugs.python.org or python-dev mailing list. |
Sorry, something went wrong.
|
hmm, from the looks on http://svn.python.org/projects/external/ I only see it having zlib v1.2.3 But I could have sworn python 3.6.0 was using 1.2.8. Will look at bugs.python.org or the python-dev irc channel. |
Sorry, something went wrong.
|
@1st1 It looks like this repo was not marked as Read Only in it's settings to disable (I think it disables) the new issue / Pull Request buttons. Might want to do it explicitly in case someone does not read the readme in the redirect branch. |
Sorry, something went wrong.
|
@asvetlov are you going to resubmit this PR to python/cpython ? I hope it's not abandoned. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Don't pass ssl certivicate error to loop.call_exception_handler()
Handle ssl.CertificateError only because ssl.SSLError may be raised not only on connection establishment.
@1st1 please take a look