- Poetry version: 1.4.0
- Python version: 3.11.2
- OS version and name: Windows 11 Pro
- pyproject.toml: see bellow
Issue
I have two local packages, pack-1 and pack-2. When I add the pack-1 to the pack-2 (poetry add --editable ../pack-1) the pack-1 is added to the pyproject.toml of the pack-2, but when I import the module pack_1 (in any of the pack-2 files) I have the error No module named 'pack_1'.
pack-1 pyproject.toml:
[tool.poetry]
name = "pack-1"
version = "0.1.0"
description = ""
authors = [""]
readme = "README.md"
packages = [{include = "pack_1"}]
[tool.poetry.dependencies]
python = "^3.11"
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
pack-2 pyproject.toml:
[tool.poetry]
name = "pack-2"
version = "0.1.0"
description = ""
authors = [""]
readme = "README.md"
packages = [{include = "pack_2"}]
[tool.poetry.dependencies]
python = "^3.11"
pack-1 = {path = "../pack-1", develop = true}
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
In MacOS the expected behavior (the module being available to pack-2) is successful. I've been only experiencing this on Windows 11.
Let me know if you need any more info.
-vvvoption) and have included the output below.Issue
I have two local packages,
pack-1andpack-2. When I add thepack-1to thepack-2(poetry add --editable ../pack-1) thepack-1is added to thepyproject.tomlof thepack-2, but when I import the modulepack_1(in any of thepack-2files) I have the errorNo module named 'pack_1'.pack-1 pyproject.toml:
pack-2 pyproject.toml:
In MacOS the expected behavior (the module being available to pack-2) is successful. I've been only experiencing this on Windows 11.
Let me know if you need any more info.