Path: csiph.com!usenet.pasdenom.info!gegeweb.org!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Fri, 17 Aug 2012 14:22:38 -0700 (PDT)
In-Reply-To: <mailman.3433.1345238143.4697.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=50.136.9.168; posting-account=hINqSwoAAACa9BnfUo4SmDvMl4mWdwot
References: <22db6f61-180c-47ce-a0c3-3315b40b8315@googlegroups.com> <mailman.3429.1345232370.4697.python-list@python.org> <1726c197-b2bb-47d8-982f-9f26af1e310d@googlegroups.com> <mailman.3432.1345237052.4697.python-list@python.org> <mailman.3433.1345238143.4697.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Python 2.7 import socket urllib fails to load, module not found
From: wdtate@comcast.net
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.3434.1345238561.4697.python-list@python.org>
Lines: 157
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:27271

On Friday, August 17, 2012 5:15:35 PM UTC-4, (unknown) wrote:
> >=20
>=20
> > So, try the following in both environments:
>=20
> >      import sys
>=20
> >      for ii in sys.path: print ii
>=20
> >
>=20
> > You'll likely find diffferences between the two.
>=20
>=20
>=20
> > In the pythonwin environment, try:
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> >      import socket
>=20
> >=20
>=20
> >      print socket.__file__
>=20
> >=20
>=20
> >=20
>=20
> > Chances are the __file__'s directory isn't in the command line's sys.pa=
th.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > Emile
>=20
>=20
>=20
> Done - tail end of the python path had a missing bit...grrrrr... thanks s=
o much

Well it's bizarre - now it doesn't.  did an import sys from within interpre=
ter, then did import socket.  Worked the first time.  Restarted and it happ=
ened 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:
> >=20
>=20
> > So, try the following in both environments:
>=20
> >      import sys
>=20
> >      for ii in sys.path: print ii
>=20
> >
>=20
> > You'll likely find diffferences between the two.
>=20
>=20
>=20
> > In the pythonwin environment, try:
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> >      import socket
>=20
> >=20
>=20
> >      print socket.__file__
>=20
> >=20
>=20
> >=20
>=20
> > Chances are the __file__'s directory isn't in the command line's sys.pa=
th.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > Emile
>=20
>=20
>=20
> Done - tail end of the python path had a missing bit...grrrrr... thanks s=
o much



On Friday, August 17, 2012 5:15:35 PM UTC-4, (unknown) wrote:
> >=20
>=20
> > So, try the following in both environments:
>=20
> >      import sys
>=20
> >      for ii in sys.path: print ii
>=20
> >
>=20
> > You'll likely find diffferences between the two.
>=20
>=20
>=20
> > In the pythonwin environment, try:
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> >      import socket
>=20
> >=20
>=20
> >      print socket.__file__
>=20
> >=20
>=20
> >=20
>=20
> > Chances are the __file__'s directory isn't in the command line's sys.pa=
th.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > Emile
>=20
>=20
>=20
> Done - tail end of the python path had a missing bit. Corrected that.  th=
e sys.path outputs match but I still have the same problem. =20

print socket.__file__ produces a path that is in the pythonpath.