Modernize Python package build system: Migrate to pyproject.toml

[brunohcfaria]

Current Status

The project currently uses an outdated package build configuration based on setup.py with several issues:

• Using outdated Python package build system (setup.py)
• Conflicting and outdated dependency specifications across multiple files
• Support for EOL Python versions
• Incomplete package requirements configuration
• Outdated development and testing dependencies

Proposed Changes

1. Migration to Modern Build System

• Replace setup.py, setup.cfg with pyproject.toml
• Implement modern build backend using uv, hatchling orpoetry-core
• Define clear dependency groups for runtime, development, and testing

2. Dependencies Cleanup

• Move all runtime dependencies from requirements.txt to pyproject.toml
• Update minimum Python version requirement to 3.10+
• Resolve conflicting package versions
• Remove support for EOL Python versions
• Update all development dependencies to current versions

3. Testing and CI Updates

• Modernize tox configuration for current Python versions (3.10-3.12)
• Update testing tools:
  • pytest >= 7.0
  • coverage >= 7.0
  • tox >= 4.0
• Add proper test coverage configuration
• Add GitHub Actions workflow for CI

[artistrea]

I would suggest using uv instead of those other backends. https://docs.astral.sh/uv/

"uv is backed by Astral, the creators of Ruff."

I am using it locally, and it is really fast and compact. Not as bloatware as conda, but also provides easy python version changes.

[artistrea]

@brunohcfaria Also, hard disagree on updating packages to most recent version as part of this issue. Things will break if such is done. It should be separated into another issue/PR since changes will need to be done deep in the simulator.

When running the project, numpy warning messages are clear "change this function call since it will be removed on next releases", shapely also gives out some warnings. Updating packages already breaks everything even when no warning message is given.

[brunohcfaria]

@brunohcfaria Also, hard disagree on updating packages to most recent version as part of this issue. Things will break if such is done. It should be separated into another issue/PR since changes will need to be done deep in the simulator.

When running the project, numpy warning messages are clear "change this function call since it will be removed on next releases", shapely also gives out some warnings. Updating packages already breaks everything even when no warning message is given.

That's true.
Let's create an issue for that, and another for analyzing the best build backend (potentially uv as you mentioned).