Hi Gabor Kovacs [X], would you be willing to review this 200-line refactoring? Thanks!

Running test_squashMetadataTask.py as a standalone script falis and then complains about leaking objects, please see attachment. This is not produced as part of a pytest run.

The failure seems to be fixed by changing "import unittest" to "import unittest.mock".

The memory leaking in case of an exit with Python exceptions suggests a lower-level problem at the C++ wrapping.

Otherwise, the changes look all right.

Actually, it suggests a problem with the memory leak tests, which, among other flaws, do not distinguish between unreachable objects and objects that have been "stashed" unexpectedly. All it takes is a single reference on the Python side (including references held by the unit test framework itself), and your object leaks. See RFC-280 for more details.

Though I'll admit I'm curious why these tests need to create a PropertySet in the first place.

Thanks for the review!