New issue 962: Unit warnings and errors should reference locations higher on the stack https://bitbucket.org/yt_analysis/yt/issue/962/unit-warnings-and-errors-shou...
Warnings like these aren't useful:
These warnings are happening when we invoke numpy on the array data - normally these warnings would be issued wherever we are manipulating numpy arrays elsewhere, but since we access numpy indireactly via YTArray, the warnings show up as function calls in YTArray.
We should be doing these superclass calls in try/except blocks to catch the warnings and if they happen manipulate them so the warning corresponds to a useful place in the call stack - probably a call or two higher.
yt-dev mailing list firstname.lastname@example.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org