Skip to content

Conversation

@AbhinavPradeep
Copy link
Contributor

Summary

In the case that we cannot find a pyproject.toml, a ["build-system", "requires"] inside pyproject.toml, or we have the existence of setup.py/cfg files, we infer the version of setuptools that is chronologically the likeliest to have been used based on the package's publish datetime.

Description of changes

  1. Modified pypi_registry.py to provide functionality to retrieve the chronologically likeliest setuptools version for a given package. Made a small refactor to the constructor of PyPIPackageJsonAsset.
  2. Modified pypi_spec.py to use this.
  3. Modified all instantiations of PyPIPackageJsonAsset to match its constructor refactor

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Dec 5, 2025
@AbhinavPradeep AbhinavPradeep changed the title Abhinav/infer chronologically likeliest setuptools version feat: infer chronologically likeliest setuptools version Dec 5, 2025
…en necessary

Signed-off-by: Abhinav Pradeep <abhinav.pradeep@oracle.com>
@AbhinavPradeep AbhinavPradeep force-pushed the abhinav/infer-chronologically-likeliest-setuptools-version branch from e523da9 to 179e7ca Compare December 7, 2025 23:44
@AbhinavPradeep AbhinavPradeep marked this pull request as ready for review December 8, 2025 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant