For some reason, the super()
method is not always behaving as expected, opting to return:
TypeError('super(type, obj): obj must be an instance or subtype of type)'
I understand what the error means. I do not understand why it is coming up as an error. Here's the snippet of code that is breaking. All objects in the system are new style objects.
What's really interesting is that this error does not always show up. I don't know what's causing it. The super()
method in Retrieval
is passing the Retrieval
class, and then itself as an object, which is, as far as I'm aware,exactly how super()
is supposed to be invoked.
Any thoughts at all?
In file DBConnection.py:
class DBAdminConnection(object):
def __init__(self):
self.user = DBUserConnection().user
self.submissions = DBSubmissionConnection()
In file Retrieval.py
class Retrieval(DBConnection.DBAdminConnection):
def __init__(self, username=None, password=None, unique_key=None):
super(Retrieval,self).__init__()
if username and password:
self.username = username
self.user.login(username,password, config.DATABASE)
if self.user.error:
raise UserLoginError(username)
self.unique_key = unique_key
If you are using reload() as part of your workflow, you apparently need to also use
super(self.__class__, self).__init__
for inheritance initialization.I suspect you will find this bug coincides with
id(self.__class__) ==id(Retrieval)
failing.Are you reloading modules somehow in the middle of things? If so, that may explain this error.
isinstance(self,DBAdminConnection)
may become false after reloading modules because of the changes to memory references, apparently.Edit: if you're running your web.py app under mod_wsgi, make sure you're disabling autoreload:
I'm not sure why the error is happening, but as an aid to debugging you could wrap the call to
super
in atry/except
block and do a data dump when the exception is raised. Something like this:I had the same error then i noticed that i had duplicate class (my mistake) within the same file.py. Error disappeared when i renamed the second class A to class B
I just had the same problem, running my code in jupyter notebook. I was using reload, so I restarted my kernel to follow up on Eduardo Ivanec's response to try and see if this was the problem. Then my code broke. I discovered my problem was related to several layers of inheritance, where the bottom layer was defined above the second bottom layer in the module.
When I moved MyClass4 underneath MyClass3, it fixed the problem.
This is probably a rookie mistake, so it probably won't resolve the cause of the original problem above, but I thought I would post in case there are other rookies out there, like me, who are making the same mistake.
(Apologies if my style is wrong, this is my first post on Stack Overflow. :))