No __init__ method in Corpus class about i-analyzer HOT 4 CLOSED

Ah, ok, after some experimentation I now realize that __init__ was probably left out on purpose, such that the NotImplementedErrors are exposed. Init would put some values into these fields, which is apparently not the desired behaviour. For the export of the database structure in json, it would have been neat to query the structure of the Corpus object in the same way as of each Field object, with a call to __dict__. But there are other ways, so no worries.

from i-analyzer.

I think it is left out for the reason that it is not needed. Do you see a reason why it should be there?

from i-analyzer.

An init would make it possible to query the structure of the class with __dict__.

from i-analyzer.

I you need to add the __init__, please go ahead and do it. I can't think of a reason why it should be left out. If it breaks something, we'll notice soon enough.

(Though I don't understand how __init__ facilitates structure querying with dict. How does that work? Besides, what do you need that for?)

from i-analyzer.