[
https://issues.apache.org/jira/browse/YETUS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808417#comment-16808417
]
Allen Wittenauer edited comment on YETUS-841 at 4/3/19 6:48 AM:
----------------------------------------------------------------
-00:
* add support for processing requirements.txt via pip
* add support for setting which pip to use
* add support for using --user flag for pip
* alphabetize the options
* fix a longstanding bug with pylintops vs. pylintopts (!)
Something I'm not sure about is whether the PYTHONPATH setting is correct.
Might need to get smarter about that. In a quick test though, this does work,
at least in a docker container.
was (Author: aw):
-00:
* add support for processing requirements.txt via pip
* add support for setting which pip to use
* add support for using --user flag for pip
* alphabetize the options
* fix a longstanding bug with pylintops vs. pylintopts (!)
Something I'm not sure about is whether the PYTHONPATH setting is correct.
Might need to get smarter about that. In a quick test though, this does work.
> Support python's requirements.txt prior to pylint
> -------------------------------------------------
>
> Key: YETUS-841
> URL: https://issues.apache.org/jira/browse/YETUS-841
> Project: Yetus
> Issue Type: New Feature
> Components: Precommit
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.10.0
>
> Attachments: YETUS-841.00.patch
>
>
> A codebase I'm familiar with has requirements.txt files all over the place.
> In order to get proper pylint support, this means either making sure the
> modules are in the environment some how, such as building a container. But
> theoretically, pylint.py could install them into a scratch directory (e.g.,
> pip install --user or via venv or whatever) and then run pylint against the
> source with that in the path. This seems especially do-able in a docker
> container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
