allow packaging >=22.0,<23.0

[ellisvalentiner]

Description

Loosen dependency on packaging from 22.0 to <23.0

Related Issue

Motivation and Context

This change will allow prospector to be installed alongside other common tools (e.g. black) use packaging >22.0.

How Has This Been Tested?

This change was tested by running the pre-commit hooks and CI workflow.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change requires a change to the dependencies
• I have updated the dependencies accordingly
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[Pierre-Sassoulas]

Imo the dependency should be >= something to be compatible with the max number of over repositories. We seems to support everything from 0 to 22.x...

[ellisvalentiner]

Because of the dependency on requirements-detector, which requires packaging >=21.3, I set the lower bound to the same.

[Pierre-Sassoulas]

Shouldn't we let requirements-detector set it's own constraint and keep our constraint large or apply constraint on requirements-detector ? Do prospector actually needs "packaging" or is this just a transitive dependency brought by requirements-detector ?

[ellisvalentiner]

Per this comment on a previous PR, it seems that the version for requirements-detector should be set explicitly.

[Pierre-Sassoulas]

Huhuhu, right, let's listen to this guy he seems to knows what he's talking about.

[Pierre-Sassoulas]

Suggested change

	packaging = ">=21.0,<23.0"
	packaging = "*"

Because prospector itself does not have the constraint of its transitive dependencies. And let's not force us to open a MR each time a new packaging is out. Let's open one if packaging break something instead.

[carlio]

I'm looking into fixing the requirements-detector package from which this transitive dependency comes. However I have run into downstream issues with poetry-semver and python-semver so it'll take me a little while to get a decent release of requirements-detector out.

[carlio]

I have just released requirements-detector version 1.1.0 which has a much more lax constraint. I'm not sure why it was set to the range it was, I forget exactly. Anyway, now it won't be an issue for prospector.