#jython IRC Log (v0.9)

Index

IRC Log for 2016-08-20

Timestamps are in GMT/BST.

[2:14] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[2:18] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 250 seconds)
[2:19] * xemdetia (xemdetia@nat/ibm/x-wahllvazuqtyrlcw) Quit (Ping timeout: 250 seconds)
[3:52] * stewori (~stefan@5.146.129.76) Quit (Quit: Leaving.)
[6:15] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[6:20] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 250 seconds)
[6:54] * eregon_ (~quassel@eregon.me) has joined #jython
[7:00] * eregon (~quassel@eregon.me) Quit (*.net *.split)
[10:17] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[10:21] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 250 seconds)
[13:21] <_MylesC> I don't suppose there's a way to reduce finalizers being used in Jython?
[13:24] <_MylesC> 121mb is being used for finalizers when I run a python script
[13:25] <_MylesC> which after researching it states how memory heavy they are
[14:18] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[14:23] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 250 seconds)
[16:51] * AndyBotwin (~Gustavo@unaffiliated/andybotwin) Quit (Ping timeout: 265 seconds)
[17:06] * AndyBotwin (~Gustavo@unaffiliated/andybotwin) has joined #jython
[18:20] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[18:24] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 250 seconds)
[20:09] * cyraxjoe (~joe@2607:f0d0:1103:106:e::12c) Quit (Remote host closed the connection)
[20:10] * cyraxjoe (~joe@2607:f0d0:1103:106:e::12c) has joined #jython
[20:25] * cyraxjoe (~joe@2607:f0d0:1103:106:e::12c) Quit (Remote host closed the connection)
[20:42] * cyraxjoe (~joe@2607:f0d0:1103:106:e::12c) has joined #jython
[22:09] * pjenvey (pjenvey@underboss.org) Quit (Ping timeout: 252 seconds)
[22:09] * lazybear (~lazybear@radium.atom.fi) Quit (Ping timeout: 252 seconds)
[22:11] * pjenvey (pjenvey@underboss.org) has joined #jython
[22:15] * lazybear (~lazybear@radium.atom.fi) has joined #jython
[22:21] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) has joined #jython
[22:26] * TomA (~TomA@2601:402:500:8e98:a1fa:3a47:29a6:1c56) Quit (Ping timeout: 258 seconds)
[23:39] * stewori (~stefan@5.146.129.76) has joined #jython
[23:40] <stewori> _MylesC: Finalizers are only created for objects that implement __del__. Avoid using __del__ should reduce finalizers.
[23:41] <stewori> (or __del_builtin__)
[23:57] <stewori> I guess you wouldn't have asked if your script caused the unexpectedly high finalizer load due to massive use of __del__. So how did you measure the amount of memory accounted for finalizers? Would there be a way to tell of which type the objects are? (IIRC there are not so many base types implementing __del_builtin__, PyFile, BasIO, PyGenerator or so)
[23:58] <stewori> (PyClass doesn't count, because it internally checks again whether __del__ is in the dict)
[23:59] <stewori> (so do derived types)

Index

These logs were automatically created by JythonLogBot_ on irc.freenode.net using a slightly modified version of the Java IRC LogBot (github).