-C / --directory equivalent for the toml conf?

[alchemicalkube]

I don't know if I'm being stupid or have missed something in the docs so apologies in advance (I am extremely tired) but I would like to know if it's possible to set a scripts working directory when run from the toml config. Example, my project setup tree is like so:

├── Dockerfile
├── LICENSE
├── README.md
├── SETUP.md
├── bot
│   ├── __init__.py
│   ├── commands
│   │   ├── __init__.py
│   │   ├── admin
│   │   │   └── __init__.py
│   │   ├── controller.py
│   │   ├── dev
│   │   │   └── __init__.py
│   │   ├── mod
│   │   │   ├── __init__.py
│   │   │   └── kick.py
│   │   └── user
│   │       ├── __init__.py
│   │       ├── dadjoke.py
│   │       └── ping.py
│   ├── conf
│   │   └── neo.yaml
│   ├── config.py
│   ├── globals.py
│   ├── log.py
│   ├── logs
│   └── neo.py
├── docker-compose.yml
├── poetry.lock
└── pyproject.toml

My toml config:

[project]
name = "neo"
version = "1.0.0"
description = "Modular, template Discord bot"

authors = [{ name = "xeckt" }]

license = { text = "GNU GPL" }

readme = "README.md"

requires-python = ">=3.10,<3.14"

dependencies = [
    "disnake (>=2.10.1,<3.0.0)",
    "requests (>=2.32.3,<3.0.0)",
    "pyyaml (>=6.0.2,<7.0.0)",
    "python-dotenv (>=1.0.1,<2.0.0)",
]

#[tool.poetry]
#packages = [{ include = "./bot" }]

[tool.poetry.scripts]
neo = "bot.neo:main"

[build-system]
requires = ["poetry-core>=2.0.0,<3.0.0"]
build-backend = "poetry.core.masonry.api"

[tool.poetry.group.devel.dependencies]
flake8 = "^7.1.1"

Now, what I want to happen, is when I'm in the project root, i.e outside the bot folder, to be able to run poetry run neo and it resolves all modules etc inside as if it was running from the bot directory. But, it doesn't, because it's evidently running from the working directory I am running the command from, resulting in things such as:

> $ poetry run neo                                                                                                                 ⬡ 23.4.0 [±main ●]
Traceback (most recent call last):
  File "<string>", line 1, in <module>
    import sys; from importlib import import_module; sys.argv = ['/Users/node/Documents/repositories/neo/.venv/bin/neo']; sys.exit(import_module('bot.neo').main())
                                                                                                                                   ~~~~~~~~~~~~~^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/Users/node/Documents/repositories/neo/bot/neo.py", line 4, in <module>
    import globals
ModuleNotFoundError: No module named 'globals'

To remediate that for now I can do poetry -C ./bot run neo and it works just fine, but can I do something inside the poetry config to set it so whenever this script is run it makes it so the bot folder is the current working directory?

[dexhunter]

There isn't a per-script working-directory setting in Poetry's entry-point configuration. For the traceback shown, change the import in bot/neo.py:

from . import globals
# or: from bot import globals

import globals searches for a top-level module named globals; it doesn't mean the sibling bot/globals.py. The entry point imports bot.neo as part of the bot package, so a package-relative import works from the project root. Apply the same change to sibling imports elsewhere in bot. See Python's package-relative imports.

Also uncomment your package selection, since the distribution is named neo but its import package is bot:

[tool.poetry]
packages = [{ include = "bot" }]

Keep neo = "bot.neo:main", run poetry install, then poetry run neo.

For files such as bot/conf/neo.yaml, resolve the path relative to the module rather than the launch directory:

from pathlib import Path

config_path = Path(__file__).resolve().parent / "conf" / "neo.yaml"

Changing directory with -C makes the current imports happen to work, but fixing the imports and file paths also lets the installed command run from elsewhere.