-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
function signatures inaccurate #233
Comments
I'm not sure what the "issue" here. Is there a specific bit of code you wrote that doesn't work like the documentation says it should? |
The docs are out of sync with the code. |
Again, please give a minimal working (or non-working) example. |
I would point out that the documentation is not really wrong as it is just describing the signature. I do think it used to work to call the read/write functions that way but the canonical way to actually read/write something is to either instantiate a |
There are numerous typos in the docs. I should have been keeping a more careful list. This one is an actual function signature that was never updated, looks like.
http://www.clawpack.org/pyclaw/io.html has
read_<format>
andwrite_<format>
, but the actual way things are read and written is viaclawpack.pyclaw.fileio.<format>.read
andclawpack.pyclaw.fileio.<format>.write
.grep
is giving me nothing forread_ascii
, for example.The text was updated successfully, but these errors were encountered: