Andreas Maier
Andreas Maier
### Description The safety package does not specify the supported Python versions in a pip-readable way. There are Trove classifiers that suggest the current version requires Python >=3.6, but that...
This addresses issue #464. Details: * The setup.cfg file already had a "python_requires" attribute, but it was in the "options.entry_points" section, from where it did not make its way into...
### Description If a library package supports a wide range of Python versions, there are cases where a vulnerability reported by safety can be fixed only for a subset of...
### Description Earlier versions of safety had a table output. That was very good to consume. The current report format is too verbose. The --short-format option also does not solve...
### Description If vulnerabilities have to be ignored for some reason (e.g. because the fixed version of the dependent package can only be used on a subset of Python versions),...
We maintain minimum constraints files in our projects that define the minimum versions with == and are used with the `-c` option of pip. That allows setting up a virtual...
I looked at some example playbooks and they all seem to be using variables deep inside some role, but there is no documentation about that. Are there any best practices...
Found a bug? Maybe our [Slack Community](https://slack.cloudposse.com) can help. [](https://slack.cloudposse.com) ## Describe the Bug When using the cloudposse/github-action-matrix-outputs-read@main action in a python:3 container on ubuntu-latest, the "jq" command is...
If the `:autosummary-inherited-members:` option is used on a class, the attribute and method summary tables generated by autodocsumm correctly include items for the inherited attributes and methods, but these items...
The standard Python `Exception` class exposes an `args` attribute, but that attribute is not included in the attribute summary table generated by autodocsumm. The `args` attribute is in the list...