You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2018/08/31 08:20:00 UTC
[jira] [Assigned] (MESOS-8206) Add the pip-requirements from other
modules to the pylint virtual environment
[ https://issues.apache.org/jira/browse/MESOS-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bannier reassigned MESOS-8206:
---------------------------------------
Shepherd: Benjamin Bannier (was: Kevin Klues)
Assignee: Armand Grillet
Sprint: Mesosphere Sprint 2018-28
> Add the pip-requirements from other modules to the pylint virtual environment
> -----------------------------------------------------------------------------
>
> Key: MESOS-8206
> URL: https://issues.apache.org/jira/browse/MESOS-8206
> Project: Mesos
> Issue Type: Improvement
> Reporter: Armand Grillet
> Assignee: Armand Grillet
> Priority: Major
>
> We have a virtual environment in {{/support}} that is used by Pylint and ESlint. Pylint will then lint modules that need a different set of dependencies to work. If we do not pull the pip-requirements from other modules to the linter virtual environment, we will see {{import-error}}s when linting Python files.
> One solution would be to use the {{--init-hook}} flag of Pylint in {{PyLinter}}. When using {{run_lint}}, we would group the modified files per module and then run pylint for all the modified files of each module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)