Get ide-python package working with Atom flatpak

[johanmcos]

Expected Behavior: ide-python works once pyls is installed
Actual Behavior: ide-python fails with a long error log

Steps to reproduce:

1. Install Atom flatpak:
   flatpak install flathub io.atom.Atom
2. Install ide-python and atom-ide-ui plugins:
   flatpak run --command=apm io.atom.Atom install ide-python atom-ide-ui
3. install python-language-server usuing pip:
   flatpak run --command=pip3 io.atom.Atom install --user python-language-server[all]
4. Verify that pyls is installed correctly:
   flatpak run --command=python3 io.atom.Atom -m pyls --help
5. Launch Atom:
   flatpak run io.atom.Atom
6. Open a python file
7. Observe no output in diagnostics
8. Open developer tools
9. See errors in terminal

Description:
Somewhat related to #2 I'm trying to see if I can get my development environment working with this Flatpak instead of the RPM from Atom's website.

All the installation steps seem to go fine, however, when I start Atom and open a Python file, the linter doesn't start up, and upon checking the development console, I have a huge log of python errors

I can't say for 100% certain that this is related to Flatpak, but I've never experienced a similar issue with installing natively, so I suspect that it is.

So far, I've tried running the flatpak app with --devel option as well, but that doesn't seem to make a difference.

Any help would be much appreciated, I'm hoping to be able to figure this out and then publish a tutorial for other interested users to follow.

Thanks!

[TingPing]

Sadly those logs don't show the full pyls error, thats kind of important to know why its failing.

[johanmcos]

Sadly those logs don't show the full pyls error, thats kind of important to know why its failing.

How would I get the full pyls errors? I'm unfortunately not super knowledgeable about these things.

Thank you

[TingPing]

I'm not familiar with debugging Atom extensions either, sorry.

[takluyver]

The full traceback is actually in there, but every line of the Python traceback is surrounded by about 10 other lines of logging.

When you decode that, it looks like a bug in python-language-server that was fixed some time after this was opened: palantir/python-language-server#769