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 }}
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
Hi, thanks for the great package and your efforts to maintain it!
If I mark a class as private, its methods are also considered private. So _Foo.bar doesn't need the documentation string.
But if I mark a package as private, its modules aren't considered private as well. So it's still required to put a documentation string on top of _foo/bar.py.
Is it intended behavior?
Have a good day 🎉
Best regards,
Artem.
The text was updated successfully, but these errors were encountered:
Probably a duplicate of #323
Hi, thanks for the great package and your efforts to maintain it!
If I mark a class as private, its methods are also considered private. So
_Foo.bar
doesn't need the documentation string.But if I mark a package as private, its modules aren't considered private as well. So it's still required to put a documentation string on top of
_foo/bar.py
.Is it intended behavior?
Have a good day 🎉
Best regards,
Artem.
The text was updated successfully, but these errors were encountered: