-
Notifications
You must be signed in to change notification settings - Fork 88
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
TypeError: __init__() got an unexpected keyword argument 'environment' in service_factory #296
Comments
Downgrading to |
Hi, can you provide more details about the virtual environment? Also, provide your emacs settings. |
Sure, for this one I don't use virtual environment, so it's my global python (which is 3.6.5, with jedi 0.12) (use-package anaconda-mode
:hook ((python-mode . anaconda-mode)
(python-mode . anaconda-eldoc-mode))
:config
(use-package company-anaconda
:requires company
:config (add-to-list 'company-backends 'company-anaconda))) I'm using use-package, but it's basically the same as in readme |
Hm... I have exactly the same settings, can't reproduce at all. Are you familiar with python hunter tracing tool? |
Just looked it up, looks interesting. I'll try to debug it further and provide more details. |
Cool, thanks! Let me know if you need further assistance. |
Well, that's weird, I wanted to do a clean experiment and pruned |
I have the same error here, did a clean up and it keeps the same, couldn't fix it |
I met the same problem, then I use |
Why do you need |
I have the latest version of anaconda-mode installed fmo melpa in my Emacs set up. For some random reason I checked out v0.1.11 in another folder to try it. Back then there was a file called setup.py , I ran the command "python3 setup.py install", for some reason everything started working again. Now my question is, I have latest version of anaconda-mode installed in my Emacs, but I ran the python installation script of v0.1.11, hehe did I mess up everything? Was it expected to start working again by running the "setup.py install"? |
@diegotsu Here comes the deps installation code: https://github.com/proofit404/anaconda-mode/blob/master/anaconda-mode.el#L98-L119 |
Anaconda mode does not require setup.py anymore. It should handle all necessary information under the hood. Everything you need to do is install anaconda-mode from Melpa. |
@proofit404 Hmmm... it's a magic command (for me) I heard from community, I'm not sure if |
json-rpc dependency was removed in 2015. Feel free to uninstall it. |
Got the same error this morning, then checked https://github.com/proofit404/anaconda-mode/blob/master/anaconda-mode.el#L98-L119 -> the issue was jedi 0.11 was installed instead of the minimal 0.12 anaconda-mode requires. Fixed with pip install --upgrade jedi The dependency check doesn't account for the lib's version so it'll fail silently if jedi is not up to date: try:
import jedi
except ImportError:
missing_dependencies.append('jedi>=0.12') |
Unfortunately, we can't use it. If you can trick |
Thanks @NathanLovato Upgrading jedi from 0.10.2 to 0.12.1 resolved this issue for me. |
I still have the exact same issue even with jedi 0.12.1. |
Please try to cleanup cache directories. |
Thanks for quick reply. I just cleaned up the .emacs.d/.cache directory but the issue still exists. Traceback (most recent call last): |
The issue only happens with spacemacs. I don't have the issue with emacs prelude. It may have something to do with the configuration of spacemacs. I'll switch to emacs prelude then. |
Thank you @valignatev . Hmm. You're right. Not sure what happened to my virtualenv. I'll stick with prelude for now. |
I have the same issue in SpaceVim |
Hi @jingpengw What what anaconda mode version do you use? What python libraries it installed? Regards, Artem. |
Anaconda-mode does not use uvicorn or click packages. You problem related to something else. |
@proofit404 could you tell me more about this ? My problem is related to what then ? |
You use issue tracker of the wrong project. |
Just updated to 0.1.12 and got this error:
The text was updated successfully, but these errors were encountered: