New submission from Nick Coghlan: Trying to streamline the URL retrieval example in the concurrent.futures docs were severely hampered by the fact the URLError thrown by urlopen doesn't tell you *what URL* it was trying to retrieve when it failed.
This is OK in synchronous code (where you probably still have the URL around), but quite a pain in asynchronous code (such as that using concurrent.futures) where the original context may have been lost by the time the future is signalled. ---------- messages: 173035 nosy: ncoghlan priority: normal severity: normal status: open title: Report failing url in URLError? _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16247> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
