-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify how dependencies are defined #3702
Comments
Hi @PyDeps The The real dependency is defined in |
Just wondering out loud here (so to speak). Having spent a lot of time looking through source code of several Ansible core and community repos lately, I've also noticed these differences between specified versions in multiple files in the same repo. If something odd like this is being done on purpose ("for dependabot only", in this case), wouldn't documenting this prominently in the files themselves make the intention more clear and reduce situations where well-intentioned contributors invest a lot of time, possibly needlessly? Could the |
Sorry to make you confused.
It is self-explanatory at the top of The
No
Supporting |
No, I'm sorry. You did not confuse me. I only responded to the comment thread (without taking the additional time to look at the actual file) and thus I did miss (as you point out) the comment about auto-generation. |
Hi, In molecule, inappropriate dependency versioning constraints can cause risks.
Below are the dependencies and version constraints that the project is using
The version constraint == will introduce the risk of dependency conflicts because the scope of dependencies is too strict.
The version constraint No Upper Bound and * will introduce the risk of the missing API Error because the latest version of the dependencies may remove some APIs.
After further analysis, in this project,
The version constraint of dependency ansible-compat can be changed to >=0.2.0,<=2.2.1.
The version constraint of dependency cookiecutter can be changed to >=0.5,<=2.1.1.
The version constraint of dependency enrich can be changed to >=1.1,<=1.2.7.
The version constraint of dependency jsonschema can be changed to >=2.0.0,<=4.6.0.
The version constraint of dependency pluggy can be changed to >=0.3.0,<=1.0.0.dev0.
The version constraint of dependency rich can be changed to >=0.2.0,<=12.6.0a2.
The above modification suggestions can reduce the dependency conflicts as much as possible,
and introduce the latest version as much as possible without calling Error in the projects.
The invocation of the current project includes all the following methods.
The calling methods from the ansible-compat
The calling methods from the cookiecutter
The calling methods from the enrich
The calling methods from the jsonschema
The calling methods from the pluggy
The calling methods from the rich
The calling methods from the all methods
@developer
Could please help me check this issue?
May I pull a request to fix it?
Thank you very much.
The text was updated successfully, but these errors were encountered: