Consolidate Development Dependencies in pyproject.toml

[markeyser]

Fixes #22

Title: Consolidate Development Dependencies in pyproject.toml

Description:

Summary

This pull request simplifies the management of development dependencies by consolidating all such dependencies into the [tool.poetry.dev-dependencies] section of our pyproject.toml. The change removes the previously separate dependency group and integrates all dependencies into a single, easily manageable list.

Changes Made

1. Removed [tool.poetry.group.dev.dependencies] Section:

   • The separate group that included toml and nbconvert has been eliminated to avoid unnecessary complexity and fragmentation in dependency management.

2. Updated [tool.poetry.dev-dependencies]:

   • Added toml and nbconvert to the main development dependencies list, ensuring that all related tools are grouped together for easier access and management.

Updated Configuration

The revised section of the pyproject.toml now includes:

[tool.poetry.dev-dependencies]
black = { version = "23.7.0", extras = ["jupyter"] }
hydra-core = "1.3.2"
ipykernel = "6.24.0"
mkdocs = "1.5.3"
mkdocs-git-revision-date-localized-plugin = "1.2.2"
mkdocs-material = "9.5.4"
mkdocs-mermaid2-plugin = "1.1.1"
mkdocstrings-python = "1.8.0"
pre-commit = "3.3.3"
pymarkdownlnt = "0.9.13.4"
pytest = "7.4.0"
pytest-benchmark = "4.0.0"
pytest-xdist = "3.3.1"
rope = "1.9.0"
ruff = "0.1.13"
dvc = "3.40.1"
toml = "^0.10.2"
nbconvert = "^7.8.0"

Rationale

• Simplicity: This change simplifies the pyproject.toml file, making it more approachable and easier to navigate for new contributors.
• Consistency: Having a single section for all development dependencies ensures consistency and reduces the likelihood of errors during project setup and updates.
• Efficiency: Streamlining dependency management enhances the efficiency of maintaining and upgrading the project environment as needed.

Impact

This update will make the project more accessible to newcomers and reduce maintenance overhead for ongoing development. It aligns with best practices for Python projects, promoting clarity and ease of use.