Ensure Compatibility with pip ≥25.3 by Adding pyproject.toml #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with pip version 25.3, support for legacy setup.py develop installations has been deprecated in favor of the modern PEP 517/518 standards. This shift can cause installation issues if a proper build backend is not defined, especially when running pip install -r requirements.txt.
To address this, the following changes have been made:
Added a pyproject.toml file to define the build system in compliance with PEP standards.
Removed the outdated pip install -r requirements.txt instruction from the README, as it is no longer applicable under the new configuration.
These updates ensure compatibility with recent versions of pip and modern Python packaging practices.