Message173035
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. |
|
Date |
User |
Action |
Args |
2012-10-16 12:31:20 | ncoghlan | set | recipients:
+ ncoghlan |
2012-10-16 12:31:20 | ncoghlan | set | messageid: <1350390680.77.0.132205585956.issue16247@psf.upfronthosting.co.za> |
2012-10-16 12:31:20 | ncoghlan | link | issue16247 messages |
2012-10-16 12:31:20 | ncoghlan | create | |
|