> I don't know that the name mangling is useful here **(or pretty much anywhere)**

I use the underscore prefix to differentiate attributes/methods that shouldn't (but can, obviously) be called from outside the class. Is that not the correct approach?

E.g. We shouldn't need to know what `Appliance._provider_name` or `Appliance._provider` or any other `Appliance._*` is, once we've provisioned an appliance. (I understand that the correct way to name them would be to use a double underscore, but since no amount of underscores is going to prevent anyone from accessing the private methods/attributes, I thought I may as well use just one)

Anyway, if this is wrong I can and will change it - that's not really an issue for me. I'd just like to know why it's wrong, so that I can make it right the next time, that's all.