You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
gitlog doesn't work with dynamically generated classes #1
As I suspected, this is triggered by the fact that the decorator inspects the class to discover the name of the file in which the class is defined. When used on dynamically generated class, this returns a path to a temporary file which is naturally part of a Git repo. It would make sense for gitlog to take in an optional argument that can directly specify path that is part of a Git repo (e.g. passing in __file__ from the context in which the class is dynamically generated). This also has the benefit of allowing the user to link the table class to be linked to an arbitrary Git repo of choice.
Activity
eywalker commentedon Mar 12, 2017
As I suspected, this is triggered by the fact that the decorator inspects the class to discover the name of the file in which the class is defined. When used on dynamically generated class, this returns a path to a temporary file which is naturally part of a Git repo. It would make sense for gitlog to take in an optional argument that can directly specify path that is part of a Git repo (e.g. passing in
__file__from the context in which the class is dynamically generated). This also has the benefit of allowing the user to link the table class to be linked to an arbitrary Git repo of choice.