[jira] [Commented] (MESOS-9058) ModuleNotFoundError: No module named 'nodeenv' when setting up support virtualenv.

["Kevin Klues (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537151#comment-16537151 ] 

Kevin Klues commented on MESOS-9058:
------------------------------------

{noformat}
commit d7eb8a9a96b7abadd9dd778604f16383567369f9
Author: Armand Grillet <ag...@mesosphere.io>
Date:   Mon Jul 9 18:03:30 2018 +0200

    Updated build-virtualenv to use Python 3 features.
    
    With Python 3, virtualenv is built-in. We thus remove the error
    messages if the script is run using Python 3 without virtualenv
    installed on the machine. We also use `python` instead of
    `virtualenv` to build the virtual environment.
    
    This change also fixes an issue on my computer where running
    `build-virtualenv` with Python 3 displayed an error message:
    `ModuleNotFoundError: No module named 'nodeenv'`.
    
    Review: https://reviews.apache.org/r/67853/
{noformat}

> ModuleNotFoundError: No module named 'nodeenv' when setting up support virtualenv.
> ----------------------------------------------------------------------------------
>
>                 Key: MESOS-9058
>                 URL: https://issues.apache.org/jira/browse/MESOS-9058
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>            Reporter: Armand Grillet
>            Assignee: Armand Grillet
>            Priority: Minor
>
> {code}
> apache-mesos (MESOS-8955) $ git rebase -i HEAD^^^^
> No C++ files to lint
> No JavaScript files to lint
> Checking 1 Python file
> Total errors found: 0
> The "pip-requirements.txt" file has changed.
> Rebuilding virtualenv...
> Traceback (most recent call last):
>   File "/Users/Armand/Code/apache-mesos/support/.virtualenv/bin/nodeenv", line 7, in <module>
>     from nodeenv import main
> ModuleNotFoundError: No module named 'nodeenv'
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)