You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uhm, so I started to introduce overwrite because I wanted this file to get updated when upgrading the library, to prevent weird bugs from occuring. It does produce a bit of IO… but it is quite negligible and this simplifies the maintenance of the package as otherwise I would need to read this file, compare the md5 with a reference md5 that I'd need to update whcn I change the file… bugs would inevitably occur. I can try to see if I can disable the warning without hidding all similar warnings, hopefully WarningFilter works locally.
I understand when user updating their texlive packages the python files in their document directories can become outdated.
For comparison: asymptote provides an asymptote.sty and a binary asy. They are both installed into the texmf tree and both get updated when I update my texlive installation. IMHO robust-externalize should provide them similarly.
Side effects:
I personally would prefer python code in python files to get full support when writing/editing them (linting/formatting/...) anyway.
When I use robust-externalize version 2.9, I get following warnings:
I would prefer it when I do not get warnings about things which IMHO I should not be warned about.
It is possible to silence the warnings with
which adds IMHO unnecessary lines of code to a manuscript.
Is the
overwrite
option for the environmentsfilecontents
really necessary?These files do not change when I recompile. Removing the
overwrite
option actually avoids unnecessary disc IO as well.The text was updated successfully, but these errors were encountered: