-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
DOC/TST: doctests leaving extraneous files #23201
Comments
prob from some of the doc-tests |
Didn't realize, but likely to be from the doctests. Not sure what's the best option here, what comes to my mind:
Any other idea? I think the first option is probably the best, even if it's not ideal. |
Is using a tempfile / namedtempfile not an option? |
yes these should use a named temp file i think |
In terms of cleaning up after running the doctests there is no doubt that using Python stdlib
we show:
|
How about we add Writing to Anything with cleaning up or writing to a StringIO will, I think, just muddy the example. We shouldn't compromise on the documentation here. |
+1 on |
Working on it! |
after running
LINT=1 ci/code_check.sh
we get some garbage left around
The text was updated successfully, but these errors were encountered: