OdooLS overriding Pycharm builtin info (with worse content)

[xmo-odoo]

With a PYTHONPATH-based setup and a properly configured project, pycharm can figure out most of the imports just fine, with all the usual features e.g. jump to symbol, find usages, show documentation, ...:

If odools is enabled, it tends to be quite confused about a lot of the setup, and to flag every symbol as "not found" with a documentation fallback of "(import) ...: Any"

But it is superior at the odoo stuff (usually), so things get kind of awkward on whether ls should or should not be enabled, depending on the frustration with the task at hand in either.

(also the built-in jump to symbol works with odools enabled so you get a warning that a symbol is not found but can still jump to it, which is a bit freaky, find usage still doesn't work tho)

[fda-odoo]

If all these imports are not found, it means that your odools is not properly configured or that you didn't use the right profile.
The integration of LSP in PyCharm is indeed still a little bit unfriendly, but we can't really do anything about that unfortunately.
The "find usage" feature, or "GoToReference" in LSP is under development right now, so it should arrives in next version :)

[xmo-odoo]

If all these imports are not found, it means that your odools is not properly configured or that you didn't use the right profile.

I can believe that, but I've no idea what it doesn't like specifically, and it doesn't seem to take pycharm's own configuration in account.

[fda-odoo]

Did you create odools.toml files, or do you use only default behavior of odooLS?
By default OdooLS will try to find odoo as the root folder of your workspace, and add other root folders (in multi-root setup) as other addons path. If it is not the structure you have in your editor, you should create your config file to explain how it is organized. You can find the syntax of config files here: https://github.com/odoo/odoo-ls/wiki/3.-Configuration-files
Then, you can select the profile you created in your config file directly in the UI of PyCharm (in the bottom right)

[xmo-odoo]

Did you create odools.toml files, or do you use only default behavior of odooLS?

Tried both.

By default OdooLS will try to find odoo as the root folder of your workspace, and add other root folders (in multi-root setup) as other addons path. If it is not the structure you have in your editor, you should create your config file to explain how it is organized. You can find the syntax of config files here: https://github.com/odoo/odoo-ls/wiki/3.-Configuration-files

Yes I followed that (as the default as I don't have a use for profiles), and according to the logs odools has the right addons path, but it doesn't look like it understands the pythonpath at all, or the (uv-created) virtualenv (in fact it resolves the python it's given to the global one uv downloaded, so I don't see how it could even find the virtualenv).

[fda-odoo]

The pythonpath should not be really important. It's used only to detect the python version and libraries that would not be present in the provided typeshed.
Indeed we are not using pycharm setup to detect the virtualenv, we have to improve that, but it should not generate these issues

[xmo-odoo]

The pythonpath should not be really important. It's used only to detect the python version and libraries that would not be present in the provided typeshed. Indeed we are not using pycharm setup to detect the virtualenv, we have to improve that, but it should not generate these issues

Well there are two relevant bits:

1. the python being provided (or configured in the pycharm project) can carry a site-package if it's a virtualenv
2. PYTHONPATH (/ pycharm source folders) can be used to provide odoo modules as an alternative to addons-path, and that's how I setup pycharm (and uv)

So odoo-pycharm being able to forward -- and odools to use -- those would probably provide a better working experience out of the box.