How to set a .venv, and get intellisense from it?

[BerndHme]

On the bottom of this page.
https://github.com/odoo/odoo-ls/wiki/How-to-use

There is noted that
"You can choose a python that is in a virtual environment, it will be used in it."

How can you choose your .venv folder?

Because when you select it at "additional addons"
it gives a red light.

My folder structure is

root
--- .venv
--- odoo (community)
--- enterprise

How can I get intellisense from the packages stored in the .venv?
i.e.:
~.venv\Lib\site-packages\dateutil

because now it doesn't.

[fda-odoo]

Hello @BerndHme ,

There is 2 ways to use a virtual environment with odoo-ls.
If you use the Python Extension from Microsoft, we are using the current selected Python in this extension. It means you just have to change your current selected Python in the bottom right of your window:

If you are not using the extension, the config view should show an extra field: Python Path, where you can put the path to the python that is in your venv directory.
If that's not the case you can manually set up it in the settings.json at User level. In the right "Odoo.configurations", set the value "pythonPath" to the path of python in your venv.

Let me know if you succeeded to set it up, else it would be a pleasure to answer your questions :)

[BerndHme]

Hi,

Thank you for your response.
I've set it up with the .venv like you said.
Using the microsoft Python extension.

user settings:

{
    "python.languageServer": "None",
}

If I add this in a .py file

from dateutil.relativedelta import relativedelta

I still don't get intellisense while typing it.
Though hovering over the last "relativedelta" when it's actually written,
it now does show a relevant info pane.

---

my current default setup is
extensions:

ms Python
ms Pylance
ms Black Formatter
ms Python Debugger

with this in my user settings

{
    "python.analysis.extraPaths": [
        "./.venv/Lib/site-packages",
        "./odoo",
        "./odoo/addons",
        "./enterprise",
    ],
}

This works, except for the dynamically created objects by the odoo ORM I guess.
Also, now when I type id in a class like this

class MyClass(models.Model):

I also get intellisense for the default class attributes.

I also have nice coloring using the ms extensions.

Would be nice to have this all with the odoo extension.

---

Using the odoo extension I disable the Pylance extension.
Is this correct?

What extensions should I use to get proper code:

completions
formatting
linting
debugging

?

[fda-odoo]

Indeed, OdooLS is not able to provide autocompletion on symbols that has not been loaded already. Import statement are not fully auto-completable too. That's a current limitation we still have to work on. It should be able to show you documentation on 'hover' and follow 'go to definition' on symbols to your virtualenv however. Outside of the import statement you should be able to see autocompletion too, by typing "relativedelta." for example.

---

I'm not sure to understand your second question though. If you mean that it would be nice to have coloration in OdooLS, that's not planned soon, as the extension is made to work alongside the Microsoft Python Extension if you want and it is providing these feature.

---

Indeed, Pylance will conflict with OdooLS and will show you a lot of duplicates results. You will have definitions, autocompletion, etc... in double. You should then set up your language server of Python to 'None' instead of 'pylance', like you did in the first part of your message:

"python.languageServer": "None",

Actually the development of OdooLS is focusing on:

• Autocompletion
• linting specific to Odoo
• Hovering
• Go to definition
• Symbol resolution

Debugging is planned, but not included yet.
Formatting is actually not planned, but could be later on.

Let me know if you still have some questions !

[BerndHme]

I gues the only real question I have is:

How do you set up a stable odoo python development?

In which you have at least normal code completions.

Now suddenly I have a warning that the imports are not found.

[BerndHme]

What I do now is I just use these extensions

ms Python
ms Pylance
ms Black Formatter
ms Python Debugger

I disable the pylance typechecking.

I add annotations to properties (attributes) from where I want intellisense.

I add the types using a

if typing.TYPE_CHECKING:
    from x import y

[fda-odoo]

That's a good question, and I think that the answer will depend on your needs.
Beside a classical python environment, if you want odoo completion, validation, etc... OdooLS is the official tool to do it from Odoo. however it is still under development and you can face crashs/errors/inconstistences in it.
I think Odoo IDE is a good and complete extension from the community it you want to try it. It is not opensource however.
Personnally I would use OdooLS + Python extension (with language server set to None). But if you want a stable environment, I would go with Odoo IDE or without any Odoo extension

The warning you got can happen if the file you opened iis not in your configuration or is not imported by another file of the project (and so not detected as part of it). If that's the case, it could be a bug. Do not hesitate to give us feedback on the project to help us improve it :)

[BerndHme]

Hi,
Thank you for your reply.
Now suddenly the error is gone... same file.
I don't know what happened but ok.

I think if the automcompletion for the imports would work, it would give a nice extra touch for the dev. experience.

Also, the configuration id count keeps counting up, you can't reset it.
Even if you remove the configuration id from the global vscode settings.

I think the configuration count is stored somewhere in
"~\AppData\Roaming\Code\User\globalStorage\state.vscdb"
(I'm on windows)

[fda-odoo]

That's in our plans to add the autocompletion for imports, but this is not supported right now because the code to scan for available imports is not ready yet, so you would only see already imported items.
About the configuration id, we know that the current configuration system is not perfect, and we will refactor it completely in the next version, for something less vscode-specific and more flexible and easy-to-use