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

[William Sewell]

It is allright.  I just cannot account for the sudden change.  In my usual path everything worked fine.  Now, I have to navigate to where the Python executable, even though I have added the path to the Windows path.

Please close my case.


Dr. William Sewell
Direct Line: 385.428.5377  Toll Free: 877.435.7948 ext 5377
Course Instructor, IT

WGU will be closed President's Day, February 19th.
Mountain Time Office hours: Sun 3:00 PM - 8:00 PM, Mon 6:30 AM - 3:30 PM, Tue 9:30 AM - 6:30 PM, Wed 9:00 AM - 5:00 PM, Thu 6:30 AM - 3:30 PM
Your success is very important to me.  
IT MSDA and Database Team 
cmdatabase at wgu.edu
Toll Free: 1-877-435-7948
Student Services: 1-866-903-0110
WellConnect Counseling Services: 1-877-685-3269
Western Governors University
mailto:william.sewell at wgu.edu



More about WGU in Fast Company, CNN, NPR, NBC Nightly News, Money, The Atlantic, TIME, etc.
wgu.edu


-----Original Message-----
From: Cameron Simpson [mailto:cs at cskk.id.au] 
Sent: Thursday, February 01, 2018 8:08 PM
To: William Sewell <william.sewell at wgu.edu>
Cc: python-list at python.org
Subject: Re: Trace back error just trying to run a simple import of requests

On 01Feb2018 20:26, 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]

Please followup to the list with a cut/paste of the error text. This list is text only and strips attachments as an aid to readability.

We want to help you, but we deal in plain text - it is far more useful to all.

Cheers,
Cameron Simpson <cs at cskk.id.au> (formerly cs at zip.com.au)