[
https://issues.apache.org/jira/browse/CLIMATE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125308#comment-15125308
]
Omkar Reddy commented on CLIMATE-383:
-------------------------------------
Hello,
I tried running $ python setup.py install and importing the ocw as import ocw
in python script. It imported the module successfully, I am confused what this
issue is really about. Please let me know clearly.
Thanks.
> Add 'scripts' to the setup.py to support ocw-ui, and ocw-cli
> ------------------------------------------------------------
>
> Key: CLIMATE-383
> URL: https://issues.apache.org/jira/browse/CLIMATE-383
> Project: Apache Open Climate Workbench
> Issue Type: Improvement
> Components: build process, command line interface, webapp
> Affects Versions: 0.3-incubating
> Reporter: Cameron Goodale
> Assignee: Cameron Goodale
> Fix For: 1.2
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> After seeing the following presentation at my local Python User Group:
> http://slid.es/edwardliaw/python-packaging
> I started thinking of all the ways that OCW's setup.py can be used to make it
> easier for new users to make use of the OCW CLI and WebApp.
> The goal for this issue is having a setup.py where a user can download the
> source code and run:
> {code}
> $ python setup.py install
> {code}
> That will install ocw into their python's location for 3rd party libs,
> meaning people can write python programs that can simply import ocw.
> The other goal is to enable users to also run common commands as scripts on
> their machine without worrying about being in the 'right location'.
> The two scripts I want to add in are:
> ocw_ui # Launches the WebApp
> ocw_cli # Launches the Command Line Interface
> Documentation on how to perform these actions will also be part of this JIRA,
> and will be added to the CLIMATE wiki page.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
