You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Yetus QA (JIRA)" <ji...@apache.org> on 2019/04/03 06:51:00 UTC
[jira] [Commented] (YETUS-841) Support python's requirements.txt
prior to pylint
[ https://issues.apache.org/jira/browse/YETUS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808421#comment-16808421 ]
Yetus QA commented on YETUS-841:
--------------------------------
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/990/console in case of problems.
> 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)