Join Slack
Powered by
is there a reason TypeConstraint is defined in `en...
# development
a
aloof-angle-91616
04/20/2018, 7:43 AM
is there a reason TypeConstraint is defined in
engine/addressable.py
instead of
util/objects.py
? phrased differently, would there be an issue if it were to be moved there? the only import used by TypeConstraint or any of its subclasses is
AbstractClass
3
Views
Open in Slack
Previous
Next