-
Notifications
You must be signed in to change notification settings - Fork 6
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
documentation of surrounding setup/caching of outputs #4
Comments
I'm currently on holidays. I'll look into this next week. |
Thanks for the update and have a great holiday |
i did some more investigation, and i'm under the impression that to replace regendoc as intended, also some ieda of "entangled project home might be needed" where temporary files drop and commands can run
|
I have a plan to integrate a small build utility into Entangled, to replace the current |
i was wondering if/how to use this tool as replacement for the https://github.com/pytest-dev/regendoc/ hack
we currently use for pytest
off hand and without reading too deep into the project, its not clear to me how the examples written out in the docs play well together with output of tools that may take a while to run (and are best updated occasionally with choice)
in the case of pytest specifically, we also keep a cleaned up version of the output in the files
so its easy to take note of unintended changes
FYI there are no immediate plans to change the documentation tooling of pytest, but i'm starting to investigate reasonable alternatives to ensure our use-cases can be covered or replaced in a sensible manner so eventually something nice can be proposed
The text was updated successfully, but these errors were encountered: