From: c.buhtz@posteo.jp
To: help-gnu-emacs@gnu.org
Subject: elpy on Windows: No module named 'encodings'
Date: Thu, 05 Nov 2020 11:55:48 +0100 [thread overview]
Message-ID: <dfc419866319afd53e6920ab66c872b6@posteo.de> (raw)
Hello, I try to get elpy run on Windows.
On Debian 10 I run such an elpy environment. So I know what to expect.
When editing a py-file I got the elpy-output-error
"Fatal Python error: initfsencoding: unable to load the file system
codec
ModuleNotFoundError: No module named 'encodings'"
Ok, I checked (elpy-config)
Emacs.............: 27.1
Elpy..............: Not found (Python), 1.34.0 (Emacs Lisp)
Virtualenv........: None
Interactive Python: python .
(c:/Users/Buhtzy/AppData/Local/Microsoft/WindowsApps/python.exe)
RPC virtualenv....: rpc-venv
(c:/Users/Buhtzy/AppData/Roaming/.emacs.d/elpy/rpc-venv)
Python...........: c:/WINDOWS/py.exe nil (c:/WINDOWS/py.exe)
Jedi.............: Not found
Rope.............: Not found
Autopep8.........: Not found
Yapf.............: Not found
Black............: Not found
Syntax checker....: flake8.exe (c:/Program Files
(x86)/Python37-32/Scripts/flake8.exe)
Ok, this does not looks good.
When I do "py" on a "Windows Terminal" or on a classic "Command Prompt"
a Python 3.9.0 prompt comes up. So it is there.
Python2 is not installed - but should not be relevant.
Based on the Windows-Feature list, only Python3.9 is installed - no
other Python version.
Python3.9 is installed in
"C:\Users\Buhtzy\AppData\Local\Programs\Python\Python39"
But this two folders still exists:
"c:/Program Files (x86)/Python37-32"
"c:/Program Files (x86)/Python36-32"
But they have no python binaries but a Lib and Scripts sub-folder.
It confuses me. Maye it confuses elpy, too? ;)
What can I do next?
next reply other threads:[~2020-11-05 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:55 c.buhtz [this message]
2020-11-05 13:40 ` elpy on Windows: No module named 'encodings' Jean Louis
2020-11-05 15:54 ` c.buhtz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfc419866319afd53e6920ab66c872b6@posteo.de \
--to=c.buhtz@posteo.jp \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).