[
https://issues.apache.org/jira/browse/CLIMATE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012816#comment-14012816
]
ASF GitHub Bot commented on CLIMATE-448:
----------------------------------------
GitHub user MBoustani opened a pull request:
https://github.com/apache/climate/pull/49
CLIMATE-448 Use 'dateutil.relativedelta' to get 'next-month' datetime in...
... decode_time_values' function and fixed unittest.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MBoustani/climate CLIMATE-448
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/49.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 #49
----
commit 32d648be0eb821cee5595d3ec632e2eaf9f84208
Author: Maziyar Boustani <maziyar...@yahoo.com>
Date: 2014-05-29T20:09:03Z
CLIMATE-448 Use 'dateutil.relativedelta' to get 'next-month' datetime in
decode_time_values' function and fixed unittest.
----
> 'decode_time_values' on utils.py should be more accurate to get 'next-month'
> ----------------------------------------------------------------------------
>
> Key: CLIMATE-448
> URL: https://issues.apache.org/jira/browse/CLIMATE-448
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Reporter: Maziyar Boustani
> Assignee: Maziyar Boustani
>
> 'dateutil.relativedelta' library does better on getting 'next-month'
> dateitme, so need to be replaced with code below.
>
> {code}
> for time_val in time_data:
> print time_val
> num_days = 30 * time_val
> times.append(time_base + dt.timedelta(days=num_days))
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
