Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warnings when opening python code, emacs 29.3. #2048

Open
simoncasassus opened this issue Jul 24, 2024 · 0 comments
Open

warnings when opening python code, emacs 29.3. #2048

simoncasassus opened this issue Jul 24, 2024 · 0 comments

Comments

@simoncasassus
Copy link

Summary

Elpy is behaving strangely on a new installation with emacs 29.3 on Ubuntu 24.0: a buffer opens with rather bad looking warnings. Also M-x elpy-format-code returns an error.

Steps to reproduce

Open Python code and get these messages:
⛔ Warning (comp): .yas-setup.el:45:48: Warning: reference to free variable ‘start-point’
⛔ Warning (comp): .yas-setup.el:65:70: Warning: reference to free variable ‘elpy-rpc-python-command’
⛔ Warning (comp): .yas-setup.el:22:13: Warning: the function ‘python-nav-beginning-of-defun’ is not known to be defined.
⛔ Warning (comp): .yas-setup.el:19:25: Warning: the function ‘python-info-current-defun’ is not known to be defined.

Try to format code with M-x elpy-format-code and get this error:
elpy-rpc--default-error-callback: Elpy error: Error during formatting: FormatCode() got an unexpected keyword argument 'verify'

My configuration

OS

Ubuntu 24.04

Result of (elpy-config)

Elpy Configuration

Emacs.............: 29.3
Elpy..............: 1.35.0
Virtualenv........: None
Interactive Python: jupyter ... (/home/simon/anaconda3/bin/jupyter)
RPC virtualenv....: anaconda3 (/home/simon/anaconda3)
Python...........: python 3.12.4 (/home/simon/anaconda3/bin/python)
Jedi.............: 0.19.1
Autopep8.........: 2.3.1
Yapf.............: 0.40.2
Black............: 24.4.2
Syntax checker....: flake8 (/home/simon/anaconda3/bin/flake8)

Warnings

You have not activated a virtual env. It is not mandatory but often a
good idea to work inside a virtual env. You can use M-x pyvenv-activate or M-x pyvenv-workon to activate one.

Elpy configuration in my init.el

(setq elpy-rpc-virtualenv-path 'current)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant