Hi,
Fixed in 1.4.3, see PyPI. Thanks for pointing this out.
best regards
Pavel Cisar
IBPhoenix
Dne 14.11.2014 v 11:42 Dominik Psenner dominik.psen...@topcontrol.it
[firebird-python] napsal(a):
Hi Pavel,
great to hear that you have got this release out of the door so quickly.
However, I’m
Ah, you were faster than I could write. Sorry for me being so persistent.
Unfortunately I am unable to post a file in the bug tracker now that the issue
is resolved, therefore I write you here.
The good thing is, 1.4.3 improved the situation. One cyclic reference has gone
away but there’s
Well, 1.4.3 is already out.
Dne 14.11.2014 v 12:06 Dominik Psenner dominik.psen...@topcontrol.it
[firebird-python] napsal(a):
Awesome! Thanks for the fast responses, you’re doing a good job. ☺ If you
feel like sending me a patch that I can apply before you push 1.4.3 out of
the door, I’ll
I refreshed the package and it looks like the memory leak is almost gone. I can
observe that the number of EventBlock’s left in memory are equal to the count
of errors raised with the invoke of begin() (namely one of: unknown ISC error
0, error reading from connection, error writing to
Hi,
Can you try to add a call to self.close() before exception is raised in
__wait_for_events ? Does it helps?
if db_api_error(self._isc_status):
self.close()
raise exception_from_status(DatabaseError, self._isc_status, Error
while waiting for events:)
best regards
Pavel
Dne 14.11.2014
*hm* .. not really.. then an AttributeError pops up:
2014-11-14 15:15:08.498000 50/51 (1|50:51|3|0)
event_conduit(['TC_IMPORT_QUEUE_UPDATED'])Exception in thread Thread-6:
Traceback (most recent call last):
File C:\Python27\lib\threading.py, line 810, in __bootstrap_inner
self.run()
File
