[
https://issues.apache.org/jira/browse/CLIMATE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190155#comment-14190155
]
ASF GitHub Bot commented on CLIMATE-539:
----------------------------------------
Github user MJJoyce commented on the pull request:
https://github.com/apache/climate/pull/122#issuecomment-61103018
Looking good so far @lewismc. However, I think we should declare the
project dependencies in the setup.py before we merge this in if we're going to
host on PyPI. At the very least users will be notified if their lacking
something if they try to `pip install` the package then. At the moment this
will just pretend like everything is peachy and then die when they try to run
something and that doesn't feel terribly user friendly. Thoughts?
> Additionally, I suggest that we thoroughly test the egg which we would
download prior to pushing this with the next release of OODT.
Could you elaborate on what we would do with OODT here?? It's early so I
might just be a bit dense at the moment =)
> Get OCW on to PyPI
> ------------------
>
> Key: CLIMATE-539
> URL: https://issues.apache.org/jira/browse/CLIMATE-539
> Project: Apache Open Climate Workbench
> Issue Type: Improvement
> Components: build process
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Fix For: 0.5
>
>
> We could make it much easier for people to get running on the concept of
> consuming OCW as a library by making a PyPI entry.
> I found a nice wee blog post explaining everything we need to do.
> I've never published an entry into PyPI but it doesn't look too hard.
> http://peterdowns.com/posts/first-time-with-pypi.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
