You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@climate.apache.org by lewismc <gi...@git.apache.org> on 2016/10/21 02:09:39 UTC
[GitHub] climate pull request #415: CLIMATE-875 Upgrade to Podaacpy 1.4.0
GitHub user lewismc opened a pull request:
https://github.com/apache/climate/pull/415
CLIMATE-875 Upgrade to Podaacpy 1.4.0
Commit to address https://issues.apache.org/jira/browse/CLIMATE-875
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lewismc/climate CLIMATE-875
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/415.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #415
----
commit 088706d8209204869fbaf24d80c7cc7b7b9aeda3
Author: Lewis John McGibbney <le...@gmail.com>
Date: 2016-10-21T02:08:23Z
CLIMATE-875 Upgrade to Podaacpy 1.4.0
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] climate issue #415: CLIMATE-875 Upgrade to Podaacpy 1.4.0
Posted by OCWJenkins <gi...@git.apache.org>.
Github user OCWJenkins commented on the issue:
https://github.com/apache/climate/pull/415
Merged build triggered. Test Failed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] climate issue #415: CLIMATE-875 Upgrade to Podaacpy 1.4.0
Posted by agoodm <gi...@git.apache.org>.
Github user agoodm commented on the issue:
https://github.com/apache/climate/pull/415
I ran the example, LGTM.
Regarding the python 3 build issues most of the those errors are pretty trivial to fix, so I'll see if I can get around to doing that by the end of the week. The only think that might be difficult is `rcmed` since it uses urllib. We might have to learn by example from `podaacpy` and add `future` as a dependency here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] climate issue #415: CLIMATE-875 Upgrade to Podaacpy 1.4.0
Posted by lewismc <gi...@git.apache.org>.
Github user lewismc commented on the issue:
https://github.com/apache/climate/pull/415
OK folks, so this PR passes against Python 2.7... which is great. Thank you @agoodm for stabilizing and significantly simplifying our builds and packaging.
There are a number of issue here with Python 3.4 and 3.5 which we will address over on additional tickets. Note, that the podaac_datasource tests actually pass fine on subsequent versions of Python.
If anyone could review this clean PR it would be greatly appreciated.
Ta
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] climate pull request #415: CLIMATE-875 Upgrade to Podaacpy 1.4.0
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/climate/pull/415
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---