Fix pytest ModuleNotFoundError: No module named 'src'

[Copilot]

Tests in tests/test_hodgkin_huxley_dynamics.py fail to collect because src is not on sys.path when pytest runs — despite the project root containing the src/ package directory.

Change

Added [tool.pytest.ini_options] to pyproject.toml with pythonpath = ["."] to instruct pytest to add the project root to sys.path:

[tool.pytest.ini_options]
pythonpath = ["."]

This makes from src.signal_processing.hodgkin_huxley_model import HodgkinHuxleyModel resolvable without modifying test files or the package structure.

[Copilot]

Pull request overview

Adds pytest configuration to ensure the repository root is added to sys.path during test runs, resolving ModuleNotFoundError: No module named 'src' during collection in environments that don’t install the project as a package.

Changes:

• Add [tool.pytest.ini_options] to pyproject.toml.
• Configure pythonpath = ["."] so src.* imports resolve under pytest.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

pythonpath = ["."] makes import src.* work when running tests from the repo checkout, but it also cements src as an importable top-level package. This conflicts with the existing setuptools packages.find where = ["src"] (src-layout), where installed code would typically be imported as signal_processing... / dascient_suite... (without the src. prefix). Consider aligning the import strategy by either (a) switching pytest pythonpath to ["src"] and updating tests to import the real packages, or (b) adjusting the packaging config to actually ship a top-level src package if that’s the intended public import path.

Suggested change

	pythonpath = ["."]
	pythonpath = ["src"]