whatever tool you are using is telling you there is a ResourceClosedError. That
error message should be accompanied by a stack trace. if you're running unit
tests in Python, as opposed to you're on some remote system and looking in log
files, these should be very obvious as every unit test runne
Ok, I see that. Could you give me some hint how could I provide the useful
stack trace? What tool should I use?
W dniu czwartek, 16 stycznia 2020 01:24:52 UTC+1 użytkownik Mike Bayer
napisał:
>
> there's no way to tell from here, information like the stack trace, and
> how the tests are being r
there's no way to tell from here, information like the stack trace, and how the
tests are being run (like what test runner, any multiprocessing in use, etc.)
would be places to start.
On Mon, Jan 13, 2020, at 9:35 AM, Mirek Morek wrote:
> Hello,
> I use sqlalchemy to execute my tests on Postgr
Hello,
I use sqlalchemy to execute my tests on Postgres Database. I run like ~200
tests, every test uses its own setup and teardown. creates a connection and
closes it after all.
I sometimes get *ResourceClosedError *(*"StatementError:
(sqlalchemy.exc.ResourceClosedError) This Connection is clo
