🔧 Missing `pyproject.toml` Configuration for the Package

[MEHRSHAD-MIRSHEKARY]

Description:

The package lacks a proper pyproject.toml configuration file, which is essential for managing the project's build system, dependencies, and other configurations in a standardized and modern way. The absence of this file can lead to issues with dependency management, build consistency, and integration with tools like Poetry, Black, and linters.

Problems Identified:

1. No Build System Specification:

   • Without a pyproject.toml, the package doesn't specify its build system. This is necessary for modern Python packaging tools like pip to understand how to build and install the package. It can lead to:
     • Inconsistent builds or failed builds on different environments.
     • Difficulty for contributors to install the package and dependencies.

2. No Dependency Management:

   • The lack of a pyproject.toml file means the package cannot take advantage of modern dependency management systems like Poetry. This can lead to:
     • Version conflicts in dependencies.
     • Harder management of development vs production dependencies.
     • No clear way to lock dependencies to specific versions for consistency across environments.

3. Lack of Configuration for Code Quality Tools:

   • pyproject.toml can centralize configurations for tools like Black, Flake8, isort, and others. Without it, configuration might be scattered across multiple files or missing entirely, leading to:
     • Inconsistent code formatting.
     • Lack of automated linting and testing standards.
     • Manual configuration of tools for contributors.

4. Difficulty Integrating with CI/CD Pipelines:

   • In CI/CD pipelines (e.g., GitHub Actions), missing the pyproject.toml can complicate the installation of dependencies and the build process. Having a pyproject.toml standardizes this process and integrates smoothly with modern CI tools.