Re: ModuleNotFoundError: No module named 'Paramiko'

[Wenyong Wei via Python-list]

hi Sravan,

Thanks for your response, checked and found there is only one python in my PC.




From: Sravan Kumar Chitikesi 
Sent: Tuesday, 9 April 2024 3:42 AM
To: Wenyong Wei 
Cc: python-list@python.org 
Subject: Re: ModuleNotFoundError: No module named 'Paramiko'

pip may be pointed to another python version. try to remove other python 
versions and re install pip

Regards,
Sravan Chitikesi
AWS Solutions Architect - Associate


On Mon, Apr 8, 2024 at 10:58 PM Wenyong Wei via Python-list 
mailto:python-list@python.org>> wrote:

Dear Sir/Madam,

Recently I encounter a problem that I can't import paramiko in my computer. My 
PC running on window 10 64 bits. I have investigate this issue via internet, 
there are a lot of solutions for this issue, after trying most of the steps, I 
still can't run this module, the major steps I have try are:


  1.
Install python ver 3.7.1 or 3.11.8 by itself or customer installation (changing 
the installation folder) and check add python to the path.
  2.
pip install paramiko, if ver 3.7.1 installed, need to upgrade the pip version.
  3.
Checking the environment path, there are two path related to the python, one 
for python.exe, the other for \Lib\site-packages\paramiko

can you please provide advice on this issue?



BR

Ken
--
https://mail.python.org/mailman/listinfo/python-list
-- 
https://mail.python.org/mailman/listinfo/python-list

[RELEASE] Python 3.12.3 and 3.13.0a6 released

[Thomas Wouters via Python-list]

*It’s time to eclipse the Python 3.11.9 release with two releases*, one of
which is the *very last alpha release of Python 3.13*:
Python
3.12.3

300+ of the finest commits went into this latest maintenance release of the
latest Python version, the most stablest, securest, bugfreeest we could
make it.
https://www.python.org/downloads/release/python-3123/
Python
3.13.0a6

What’s that? The last alpha release? Just one more month until feature
freeze! Get your features done, get your bugs fixed, let’s get 3.13.0 ready
for people to actually use! Until then, let’s test with alpha 6. The
highlights of 3.13 you ask? Well:

   - In the interactive interpreter, exception tracebacks are now colorized
   by default
   .
   - A preliminary, *experimental* JIT was added
   ,
   providing the ground work for significant performance improvements.
   - The (cyclic) garbage collector is now incremental
   
,
   which should mean shorter pauses for collection in programs with a lot of
   objects.
   - Docstrings now have their leading indentation stripped
   ,
   reducing memory use and the size of .pyc files. (Most tools handling
   docstrings already strip leading indentation.)
   - The dbm module  has a
   new dbm.sqlite3 backend
    that is used by
   default when creating new files.
   - PEP 594 (Removing dead batteries from the standard library)
    scheduled removals of many
   deprecated modules: aifc, audioop, chunk, cgi, cgitb, crypt, imghdr,
   mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau,
   telnetlib, uu, xdrlib, lib2to3.
   - Many other removals
    of deprecated
   classes, functions and methods in various standard library modules.
   - New deprecations
   , most of
   which are scheduled for removal from Python 3.15 or 3.16.
   - C API removals 
   and deprecations .
   (Some removals present in alpha 1 were reverted in alpha 2, as the removals
   were deemed too disruptive at this time.)

(Hey, *fellow core developer,* if a feature you find important is missing
from this list, let Thomas know . It’s getting to be
really important now!)
https://www.python.org/downloads/release/python-3130a6/
We
hope you enjoy the new releases!

Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself, or through contributions to the Python Software
Foundation  or CPython itself
.

Thomas “can you tell I haven’t had coffee today” Wouters
on behalf of your release team,

Ned Deily
Steve Dower
Pablo Galindo Salgado
Łukasz Langa
-- 
Thomas Wouters 
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: ModuleNotFoundError: No module named 'Paramiko'

[Mats Wichmann via Python-list]

On 4/7/24 19:31, Wenyong Wei via Python-list wrote:


Dear Sir/Madam,

Recently I encounter a problem that I can't import paramiko in my computer. My 
PC running on window 10 64 bits. I have investigate this issue via internet, 
there are a lot of solutions for this issue, after trying most of the steps, I 
still can't run this module, the major steps I have try are:


   1.
Install python ver 3.7.1 or 3.11.8 by itself or customer installation (changing 
the installation folder) and check add python to the path.
   2.
pip install paramiko, if ver 3.7.1 installed, need to upgrade the pip version.
   3.
Checking the environment path, there are two path related to the python, one 
for python.exe, the other for \Lib\site-packages\paramiko

can you please provide advice on this issue?


Going to be more explicit than the other answers:

===
If an attempted import gives you ModuleNotFound, that *always* means the 
package is not installed... not at all, or just not in the paths that 
copy of Python is looking in.

===

The problem arises in part because most package installation 
instructions take the simplest approach and just tell you to (for example)


pip install paramiko

So it's installed. But where did it go? You can check where it went:

pip show paramiko

That path ("location") needs to be one where your Python interpreter is 
looking.


If all goes well, "pip" and "python" are perfectly matched, but in the 
current world, there are often several Python interpreters installed 
(projects may require a specific version, an IDE may grab its own 
version, something may create and setup a virtualenv, alternate worlds 
like Conda may set up a Python, the list goes on), and for any given 
installation on Windows, python.exe and the pip excutable pip.exe go in 
different directories anyway, and the Windows PATH doesn't always 
include both, and you easily get mismatches.


As others have said, the way to avoid mismatches is to use pip As A 
Module, specifically a module of the Python you want to use.  So if 
you're using the Python Launcher, that looks like:


py -m pip install paramiko

Hope this helps.

--
https://mail.python.org/mailman/listinfo/python-list