Simplify Poetry workaround
What does this MR do?
Simplifies the Poetry workaround discussed in the poetry.lock support for Dependency Scanning issue onwards.
How to setup and validate locally
Example below:
- Start with a Python project
- Enable dependency scanning
- Add the new code to .gitlab-ci.yml
- Verify that the
gemnasium-python-dependency_scanningjob runs successfully.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
The main risk is to differently configured projects, where this workaround might not work, or might break things where the original code did not. See this comment mentioning unspecified potential issues with Python 3.6, which I have not looked into.
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.