Johan van der Knijff

Hi Aaron, Not using valgrind myself, but definitely looks like something that's worth checking out. Meanwhile, could you post a link to the image that is causing the error?

Reminder for myself on compilation of Python for the analysis, based on: * * * ## Setting up Python from source Get source distribution from [here](https://www.python.org/downloads/source/). Then following steps: 1....

Addition, this thread describes some alternative (and in this case probably better) ways to detect memory leaks in Python (ht @WillemJan):

Don't know if we can close this. Any ideas @carlwilson?

First step could be to simplify handling of glob patterns, following: (In this case the OS takes care of the glob expansion on Linux-based platforms) Stand-alone test script here:

UPDATE: this also happens if jpylyzer is run as a script, so it is not specific to the binaries.

Reverted back to original line, which gets rid of the warning:

UPDATE: similar warnings occurs if the --mix option is used, this time referring to 3 lines in mix.py. On closer inspection it turns out the warnings (including the one in...

For now just accept warnings with --mix option under Py 2.7, then after Py 2.7 is dead and buried implement everything according to Pylint for Py 3. To be addressed...

Minimal support for missing marker segments added in 1.7.0. Full support to follow later ..