LemurPwned
commented
6 years ago Del operator only works if a reference goes out of scope. Reference to an doh objext does not go out of scope until it main window still has doh reference. The only reason for removing function (not object removal) in doh is that the object held in doh should be nullified as soon as it is not used -but still, references to doh should be held. We dont want to destroy doh objects but some of its contents . Obviously overwriting del operator is a bad idea in that case unless we would be in control of object deletion across its references. That is why doh was created to manage references and drop them easily for data structs that are no longer required. Another reason for that is that we dont want to risk the access of invalid data (the data that is still held in doh but is already outdated) About removing object it is true, it happens that I did not return inner funciton that is why it didnt work
Virtually same topic as #56
pawelkulig1
I think you haven't checked if function removeDataObject is working. Python has garbage collector that deletes object when there is 0 refs, but another thing is that Python releases this memory when it wants not when we want that. Using del operator for example is considered bad practice. If we truly want to delete some object from mem, we should restart program or, delete all references to object and wait until it's deleted (It may never happen). I don't think there is proper solution for that because Python seems to be smarter. Fortunately it seems that garbage collector is doing good job at runtime end.