The future module is now needed (this could be relaxed if we didn't want a usage string to be printed to stderr);
The path variable defined in ionFRM.py is now determined automatically. This may or may not be useful, but that's what pull requests are for.
I had to remove "ionFR_2018" from a path in ionFRM.py to get the example to work (see the last diff shown in this PR). I assume that was not meant to be there.
With these changes, I get the same output (modulo floating-point-precision errors) in both python 2 and 3.
I also assume that the usage function used in ionFRM.py wants to use usage from rdalaz.py. Before these commits, no other usage function was available to ionFRM.py.
There are three important changes here:
stderr
);ionFRM.py
is now determined automatically. This may or may not be useful, but that's what pull requests are for.ionFRM.py
to get the example to work (see the last diff shown in this PR). I assume that was not meant to be there.With these changes, I get the same output (modulo floating-point-precision errors) in both python 2 and 3.
I also assume that the
usage
function used inionFRM.py
wants to useusage
fromrdalaz.py
. Before these commits, no otherusage
function was available toionFRM.py
.