Python 2.7 import socket urllib fails to load, module not found

[wdtate at comcast.net]

On Friday, August 17, 2012 5:15:35 PM UTC-4, (unknown) wrote:
> > 
> 
> > So, try the following in both environments:
> 
> >      import sys
> 
> >      for ii in sys.path: print ii
> 
> >
> 
> > You'll likely find diffferences between the two.
> 
> 
> 
> > In the pythonwin environment, try:
> 
> > 
> 
> > 
> 
> > 
> 
> >      import socket
> 
> > 
> 
> >      print socket.__file__
> 
> > 
> 
> > 
> 
> > Chances are the __file__'s directory isn't in the command line's sys.path.
> 
> > 
> 
> > 
> 
> > 
> 
> > Emile
> 
> 
> 
> Done - tail end of the python path had a missing bit...grrrrr... thanks so much

Well it's bizarre - now it doesn't.  did an import sys from within interpreter, then did import socket.  Worked the first time.  Restarted and it happened again.  The sys.path outputs are identical.  The print socket.__file__ reveals a file that is in the sys.path...grrrr.


On Friday, August 17, 2012 5:15:35 PM UTC-4, (unknown) wrote:
> > 
> 
> > So, try the following in both environments:
> 
> >      import sys
> 
> >      for ii in sys.path: print ii
> 
> >
> 
> > You'll likely find diffferences between the two.
> 
> 
> 
> > In the pythonwin environment, try:
> 
> > 
> 
> > 
> 
> > 
> 
> >      import socket
> 
> > 
> 
> >      print socket.__file__
> 
> > 
> 
> > 
> 
> > Chances are the __file__'s directory isn't in the command line's sys.path.
> 
> > 
> 
> > 
> 
> > 
> 
> > Emile
> 
> 
> 
> Done - tail end of the python path had a missing bit...grrrrr... thanks so much



On Friday, August 17, 2012 5:15:35 PM UTC-4, (unknown) wrote:
> > 
> 
> > So, try the following in both environments:
> 
> >      import sys
> 
> >      for ii in sys.path: print ii
> 
> >
> 
> > You'll likely find diffferences between the two.
> 
> 
> 
> > In the pythonwin environment, try:
> 
> > 
> 
> > 
> 
> > 
> 
> >      import socket
> 
> > 
> 
> >      print socket.__file__
> 
> > 
> 
> > 
> 
> > Chances are the __file__'s directory isn't in the command line's sys.path.
> 
> > 
> 
> > 
> 
> > 
> 
> > Emile
> 
> 
> 
> Done - tail end of the python path had a missing bit. Corrected that.  the sys.path outputs match but I still have the same problem.  

print socket.__file__ produces a path that is in the pythonpath.