fortpy
fortpy copied to clipboard
rosenbrockc
Python Emacs Intellisense and Unit Testing Support for Fortran
1. When sending saved shell sessions around, the absolute path to the test results is not as useful. Can we get by with a relative path? 2. Need to separate...
When using analyze.py failures it doesn't currently tell you what tests failed and how. It would be nice if failures did an analysis of the out.compare files and then let...
Although everything is already automated quite well, the developer still has to generate model input files at the very least in order to get the tests setup. For most scientific...
At the moment, if a code file's accompanying XML file is changed, a re-parse is triggered and the code base is considered altered, _even_ if the code file itself didn't...
Look at line 130 of `tester.py`. If the model output does not exist, then we just save `None`, which is worthless. Also the failures list never gets saved to a...
Traceback (most recent call last): File "/Users/wileymorgan/.virtualenvs/fortpy/bin/runtests.py", line 91, in initialize() File "/Users/wileymorgan/.virtualenvs/fortpy/bin/runtests.py", line 51, in initialize print_result(idk, result[idk].percent, timestr, result[idk].common) File "/Users/wileymorgan/.virtualenvs/fortpy/lib/python2.7/site-packages/fortpy/testing/tester.py", line 302, in percent return float(total) /...
The full documentation for a subroutine/function can be called up using `M-?` in emacs. However, it currently only works for executables that are defined in the same module as the...
When the first argument is an instance of a user-derived type in a subroutine/function, we remove it because fortpy assumes that the subroutine is _embedded_ in the type; but that...
We need to show a warning when a unit test is defined for a subroutine or function that is declared inside of another subroutine. Since they are buried, they can't...
Metadata
Owner
Metadata
Python Emacs Intellisense and Unit Testing Support for Fortran