roughcoat, I think you hit the nail on that head with that one.
Bozemoto and Sintex, I'm not sure if you guys are familiar with the "Pythonic way" stuff, but it can basically be summed up as:
Although you CAN use Python to write code similar to C (e.g. a for loop iterating using I and incrementing it), it's "Pythonic" to not do this and instead to use for something in some_collection: etc...
That's a contrived and probably pretty lackluster example but I'm tired right now... It gets a lot more heavy than that... For example using list comprehensions and lambdas to filter data and make little "inline functions" and so on... Basically, a lot of stuff I wouldn't find myself doing when programming in C regularly. Essentially, the Pythonic way of doing things is "use the most Python-specific constructs as possible and avoid traditional programming ways."
My cry in this post was partially due to having to work with third party library classes/instances, but also partially due to this "Pythonic" thinking. roughcoat's answer really wrang home with me in that what I should probably do is not worry too much about the Pythonic crap because the fact is, the few people who will be interacting with my program at work are also C programmers anyway, and we are not "shipping a production app" when we use Python... Rather, we are writing small tools, utilities, and plugins for internal use only.
So perhaps if I stop stressing about making things Pythonic (despite the Python guru's recommendations to do so), that will probably alleviate my qualms enough to where I can deal with the 3rd party object stuff as needed without too much headache.
Another closing example of what I meant by OOP mess is that where in C I would throw a struct on the heap and interact with it no problem, in Python, I found situations where I would write up a class, then be stressing about what needs to inherit from that class, then suddenly I need to compare the class object and thus needed to start writing "Python magic methods" (https://rszalski.github.io/magicmethods/
) and next thing I knew, I was spending more F'ing time with all of that, writing dozens of methods, when the entire point of using Python over C was to bang out a script real quick..
So hopefully that clears up the initial problem some more.