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

ASF GitHub Bot commented on CLIMATE-556:
----------------------------------------

Github user lewismc commented on the pull request:

    https://github.com/apache/climate/pull/255#issuecomment-151266282
  
    Hi @Omkar20895 , I like the new coloured guidance for the terminal prompts. 
There seems to be some issue thought with the terminal logging. When I run the 
osx script, there is no logging to stdout. This is not ideal as it is very 
useful to understand what is going on. Can you take a look into it? I see the 
following
    <img width="1440" alt="screen shot 2015-10-26 at 1 02 01 pm" 
src="https://cloud.githubusercontent.com/assets/1165719/10740809/835f1e06-7be1-11e5-890c-6a28e09b4550.png";>



> easy_install scripts should create a new virtualenv e.g. -e flag, by default
> ----------------------------------------------------------------------------
>
>                 Key: CLIMATE-556
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-556
>             Project: Apache Open Climate Workbench
>          Issue Type: Bug
>          Components: easy-ocw
>    Affects Versions: 0.4
>            Reporter: Lewis John McGibbney
>             Fix For: 1.2
>
>
> Having sat with people recently watching them install climate, it has become 
> obvious that the default behavior for the easy_install scripts should be 
> invoking the -e flag.
> The script specifically say
> {code}
> It is recommended that you pass -e when running this script. If you don't, 
> parts
> of this installation will pollute your global Python install. If you're 
> unsure,
> pass -e just to be safe!
> {code}
> A user never sees this message though unless they know that
>  * there is a -h flag to print it
>  * it is too late and that they have already messed up their environment!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to