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
I'm using pyreverse to visualize the structure of sympy which is a fairly large project, with a lot of relations modelled by classes, but also some functionality like iterators implemented via dunder methods.
I understand the decision behind not including private methods, but some of the special dunder methods, I'd argue, are part of the public API of an object and so they should be included in the diagram, wdyt?
Desired solution
Special methods (__next__, __iter__, __str__ etc.)should show up in diagrams as member methods, just like public methods do now
Additional context
No response
The text was updated successfully, but these errors were encountered:
Whoops, might've created the issue too early, I see -f SPECIAL_A does exactly what I wanted, though it isn't explicitly mentioned by the help message. I'll keep the issue open and fix up a PR with modified docs
edit: the output differs when using -fSPECIAL and -fSPECIAL_A, but pyreverse prints Unknown filter mode 'SPECIAL_A' when using the latter.
Current problem
I'm using pyreverse to visualize the structure of sympy which is a fairly large project, with a lot of relations modelled by classes, but also some functionality like iterators implemented via dunder methods.
I understand the decision behind not including private methods, but some of the special dunder methods, I'd argue, are part of the public API of an object and so they should be included in the diagram, wdyt?
Desired solution
Special methods (
__next__
,__iter__
,__str__
etc.)should show up in diagrams as member methods, just like public methods do nowAdditional context
No response
The text was updated successfully, but these errors were encountered: