Trace back error just trying to run a simple import of requests

Chris Angelico rosuav at gmail.com
Fri Feb 2 10:34:08 EST 2018


On Sat, Feb 3, 2018 at 2:25 AM, Grant Edwards <grant.b.edwards at gmail.com> wrote:
> On 2018-02-01, MRAB <python at mrabarnett.plus.com> wrote:
>> On 2018-02-01 22:32, Grant Edwards wrote:
>>> On 2018-02-01, William Sewell <william.sewell at wgu.edu> wrote:
>>>
>>>> My python script which I run daily just blew up.  So, I went into
>>>> python to diagnose and just typed in the first line - import
>>>> requests.  I received screenfulls of errors.  Why?  What could have
>>>> happened when nothing changed on my end?  The traceback is copied
>>>> below.
>>>>
>>>> [cid:image001.png at 01D39B71.014E8850]
>>>
>>> I don't recoginze "cid:image001.png at 01D39B71.014E8850" as an error
>>> message.
>>>
>> Isn't it ironic that we've just had a thread about this very issue,
>> namely sending screenshots?
>
> I dunno, is it time for a long thread on what "ironic" means?   ;)
>

An ironic thread is slightly lighter than a cobaltic thread, slightly
heavier than a maganetic thread. It's also heavier than Chromium,
which is quite an accomplishment, considering the atomic RAM weight of
Chromium.

ChrisA



More information about the Python-list mailing list