Jorgen Schäfer

Hello, and thanks for the report. What's the value of `python-shell-interpreter` with and without Elpy enabled? Are you using a virtualenv in either case?

Could you copy the definition of the function `python-shell-completion-native-setup` into your `*scratch*` buffer and edit it so that the part before `pytho.el: native completion setup failed` reads like this: ```...

There's nothing Elpy does here that should interfere with that code. I have no idea what's going on there. :-(

> Interestingly, even setting elpy-modules to nil doesn't suppress the problem. What does elpy do that's not in a module? Not much. This is a problem with python-mode in Emacs,...

But the output you showed above was from ipython?

Could you copy the definition of the function `python-shell-completion-native-setup` into your `*scratch*` buffer and edit it so that the part before `pytho.el: native completion setup failed` reads like this: ```...

Yes I did, but that was with ipython which might have had different code paths :-) When trying to debug some weird behavior, it's confusing when the environment changes randomly....

Thank you for finding that upstream bug! That solves one of my headaches here :-D

Is it possible to reliably detect the problem? I would not mind having the fix in elpy.el's "backwards compatibility" section …

Very nice, thanks a lot for your work! I did add a few comments to the patch. :-)