I found the problem. After the python setup install I found the paramiko
folder located at:
Python25\Lib\site-packages\paramiko-1.7.2\build\lib\parmiko\
When I simply copied that final paramiko\ folder to sys.prefix (i.e.
C:\\Python25)
Python25\paramiko
then everything worked great! Was that in fact a PYTHONPATH problem? How
do I echo $PYTHONPATH to see what it is? What *should* it be set to? I think
for sure I set it to C:\\Python25 when I originally installed Python. How
should the setup normally know where to install site-packages? Should the
final paramiko\ folder actually be in C:\\Python25, or would it be more
usual to have it located in site-packages?
One thing the on-line Python documentation is not very clear on is how
installation actually works, where the packages are actually installed,
where the source.py and compiled.pyc files actually belong. That would make
it a lot easier to debug installation problems if we knew where to go
looking for them after installation.
On Thu, Sep 9, 2010 at 7:03 PM, Tobias Mueller mue...@cryptobitch.dewrote:
Heya,
On 09.09.2010 22:55, Steven Lehar wrote:
import paramiko
it imports without error. But if I exit python and start a whole new
python session, then it does NOT work!
import paramiko
...ImportError: No module named paramiko
Can somebody tell me what I am doing wrong?
Sounds like a wrong PYTHONPATH.
Cheers,
Tobi
___
paramiko mailing list
paramiko@lag.net
http://www.lag.net/cgi-bin/mailman/listinfo/paramiko