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
Currently, the import path of skimage.filters.lpi_filter, skimage.filters.ridges and skimage.filters.lpi_filter.forward_filter lack a leading underscore, which implies that they are part of our public API. However, both are not included in our API documentation.
I propose to be more explicit about this and make them private by renaming to _lpi_filter. Or do we have a good reason to break from the established default skimage.submodule.function pattern in this case?
lagru
changed the title
Are filters.lpi_filter, filters.ridges and forward_filter part of our public API?
Are lpi_filter, ridges and forward_filter part of our public API?
Oct 24, 2022
lagru
changed the title
Are lpi_filter, ridges and forward_filter part of our public API?
Are lpi_filter and ridges part of our public API?
Apr 13, 2023
Currently, the import path of
skimage.filters.lpi_filter
,skimage.filters.ridges
andlack a leading underscore, which implies that they are part of our public API. However, both are not included in our API documentation.skimage.filters.lpi_filter.forward_filter
I propose to be more explicit about this and make them private by renaming to
_lpi_filter
. Or do we have a good reason to break from the established defaultskimage.submodule.function
pattern in this case?Edit:
filter_forward
was addressed in #6883.The text was updated successfully, but these errors were encountered: