Issue 16247: Report failing url in URLError? (original) (raw)

Created on 2012-10-16 12:31 by ncoghlan, last changed 2022-04-11 14:57 by admin.

Messages (5)
msg173035 - (view)	Author: Alyssa Coghlan (ncoghlan) *	Date: 2012-10-16 12:31
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.
msg173036 - (view)	Author: Ezio Melotti (ezio.melotti) *	Date: 2012-10-16 12:33
See also #10836 and .
msg173494 - (view)	Author: Senthil Kumaran (orsenthil) *	Date: 2012-10-22 00:57
The URLError changes gone in as part of fix for should give e.filename and e.reason.
msg407759 - (view)	Author: Irit Katriel (iritkatriel) *	Date: 2021-12-05 23:38
Senthil, can this issue be closed now or is there something left to do?
msg408419 - (view)	Author: Senthil Kumaran (orsenthil) *	Date: 2021-12-13 02:07
It is going to take a few weeks for me to get to my alerts, I will address this as soon as I get to it . Thanks for the triage, Irit. On Mon, Dec 13, 2021, 12:31 AM Irit Katriel <report@bugs.python.org> wrote: > > Change by Irit Katriel <iritkatriel@gmail.com>: > > > ---------- > status: open -> pending > > _______________________________________ > Python tracker <report@bugs.python.org> > <https://bugs.python.org/issue16247> > _______________________________________ >