You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using direnv with it's layout python to create a python virtual environment at .direnv/python-<version>.
After that, I'm using poetry to install my dependencies and my package into the virtual environment.
I am pretty sure that the inclusion of "" in sys.path triggers this behaviour. I am also provided the same suggestions under module.thing and src.module.thing.
I understand that having the current directory on the include path is expected, but this is very annoying, and a lot of libraries use a src layout and should thus suffer from this, right?
Or do I have something misconfigured?
For context:
I have python installed through a nix devshell
"Propert" poetry project with `packages = [ { include = "pkg", from = "src" }]
python-lsp-server and plugins installed via [tool.poetry.group.dev.dependencies]
The text was updated successfully, but these errors were encountered:
As it says in the title.
I'm using direnv with it's
layout python
to create a python virtual environment at.direnv/python-<version>
.After that, I'm using poetry to install my dependencies and my package into the virtual environment.
I am pretty sure that the inclusion of
""
insys.path
triggers this behaviour. I am also provided the same suggestions undermodule.thing
andsrc.module.thing
.I understand that having the current directory on the include path is expected, but this is very annoying, and a lot of libraries use a
src
layout and should thus suffer from this, right?Or do I have something misconfigured?
For context:
[tool.poetry.group.dev.dependencies]
The text was updated successfully, but these errors were encountered: