-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bugfix in AutoPopulate.progress() #176
Conversation
…ndencies have not been initialized by a call to erd ot populate()
I don't understand why we need this. The problem in progress must be the call to |
Every call of |
Then I think it would be best to have a switch in dependencies that indicates whether they were loaded already and a |
@fabiansinz What's the advantage of using the decorator |
I find that more explicit. Since we don't load the dependencies once the object is created, but some function do require loaded dependencies at the same time, I think it is cleaner to mark those functions that need loaded dependencies with that decorator. I guess it's a matter of style. I like using decorators to make sure some conditions are satisfied and then just use that conditions inside the function instead of ensuring it in the function itself which might serve an entirely different purpose. Argument checking is a classic example. If you put it explicitly in a function, the lines for argument checking can completely clutter the code in which the actual computations of the function happen. |
I'm going to go ahead and accept the pull request, but we still have to decide on a good strategy to load the dependency when needed. @dimitri-yatsenko removed call to |
bugfix in AutoPopulate.progress()
No description provided.