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

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

GitHub user agoodm opened a pull request:

    https://github.com/apache/climate/pull/365

    CLIMATE-817 - More informative error messages for data_source.load_file()

    This change will now show the filename string that gets passed into the 
function in the error message.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/agoodm/climate CLIMATE-817

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/climate/pull/365.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 #365
    
----
commit fc61608a931da03050925bd629765036559eaf87
Author: Alex Goodman <ago...@users.noreply.github.com>
Date:   2016-06-23T23:27:24Z

    CLIMATE-817 - More informative error messages for data_source.load_file()

----


> More informative error messages for data_source.load_file()
> -----------------------------------------------------------
>
>                 Key: CLIMATE-817
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-817
>             Project: Apache Open Climate Workbench
>          Issue Type: Improvement
>          Components: data sources
>            Reporter: Alex Goodman
>            Assignee: Alex Goodman
>            Priority: Trivial
>             Fix For: 1.1
>
>
> The error message in {{data_source.load_file()}} should be more informative. 
> In particular, the string entered by the user for the {file_path} argument 
> should at least be shown, especially if this input is passed by another 
> calling function (eg {{load_dataset_from_multiple_netcdf_files()}}) instead 
> of directly by the user.



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

Reply via email to