https://travis-ci.org/pandas-dev/pandas/jobs/223491099
..................sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=1 mode='w' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=1 mode='w' encoding='UTF-8'>
Comment From: jreback
cc @gfyoung if you have a chance (this is the 3.6 build). not 100% sure these are the parser, but obviously an io component.
Comment From: gfyoung
Sure thing. Quick question: is there a way to get pytest to error if a ResourceWarning is produced?
Comment From: TomAugspurger
With https://pypi.python.org/pypi/pytest-warnings it looks like this might work
pytest -W ignore -W error::ResourceWarning
Comment From: gfyoung
I can't seem to track it down. Not sure where this is occurring. Interesting though, I broke a bunch of tests by including that test command @TomAugspurger provided (see here).
For reference, here is the commit I made to get these failures here.
Comment From: gfyoung
Can anyone reproduce the warnings locally? Although I got things to break as seen above, that's way too many to match the warnings seen originally.
Comment From: TomAugspurger
I tried and was unable to reproduce them (python 3.6).
On Thu, Apr 20, 2017 at 10:48 AM, gfyoung notifications@github.com wrote:
Can anyone reproduce the warnings locally? Although I got things to break as seen above https://github.com/pandas-dev/pandas/issues/16055#issuecomment-295438196, that's way too many to match the warnings seen originally.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pandas-dev/pandas/issues/16055#issuecomment-295787309, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQHImxz6q6I0HioTu9LWqnI5rxM3ejnks5rx343gaJpZM4NBeH_ .
Comment From: gfyoung
Hmm...without anyone able to reproduce this, it's very difficult to tell if this is a parser issue. The thing that makes me weary about that is because the filename is sys instead of a Python file.
Thoughts on how to proceed?
Comment From: jreback
make sure you define this: PANDAS_TESTING_MODE="deprecate" and -s when you run the tests. I only think this occurs on linux-64. doesn't repro on osx. will take a look tomorrow there. It might be because of the multiprocessing (in pytest-xdist), thought not sure.
Comment From: gfyoung
@jreback : Any insights on this? Just wondering.
Comment From: jreback
nope. it shows on the travis build but I cannot repro locally. will just close this.