Nitin Madnani
Nitin Madnani
We haven’t really tried it yet :)
Is this still an issue @jbiggsets ?
Thank you so much for taking this on @srhrshr! I'll take a look next week!
This is actually addressed in the Python [logging HOWTO](https://docs.python.org/3/howto/logging.html): > warnings.warn() in library code if the issue is avoidable and the client application should be modified to eliminate the warning....
On a related note, we should be using `FutureWarning` for deprecation warnings and not `DeprecationWarning` since that's what the Python documentation [recommends](https://docs.python.org/3/library/exceptions.html#FutureWarning) and this is what scikit-learn has recently done.
@aloukina this is done right?
Great idea! May be we should also have an overall verbose/quiet option on the command line for the `run` command that propagates all the way down into the code and...
Do we still need to address this?
Sounds like a temporary file isn't being closed properly in a test.
@aloukina do you see this warning on your Mac or in the TravisCI build?