• Consolidate Python examples notebook merging more examples from https://github.com/MTG/essentia-tutorial.

Also consider:

• TensorFlow auto-tagging and classification examples
• Audio problems algorithms examples
• Monophonic pitch detection
• SuperFlux
• Visualize various onset detection functions
• Constant-Q
• Real time analysis of an audio stream

https://www.python.org/dev/peps/pep-0257/ lists some conventions how dostrings should be formatted. Most of the docstrings are compatible already, some are not.

Some are descriptive which violate the rule that a docstring should prescribe the function or method's effect as a command "Do this", "Return that", instead of "Returns the pathname ...".

sklearn issued warning message for passing attributes to check_is_fitted as follows:

FutureWarning: Passing attributes to check_is_fitted is deprecated and will be removed in 0.23. The attributes argument is ignored.
"argument is ignored.", FutureWarning)

The sklearn version that issued this warning: 0.22

Ways to reproduce:

1. Use the package version above
2. Run f0 estimatio

If one boundary algorithm parameter has the same name as a labeling one, the labeling one overwrites the boundary one. This shouldn't happen.

Has anyone else noticed a persistent issue with the user-read-birthdate scope still appearing when using spotifyr::scopes? Using the underlying scopes snippet directly in RStudio produces the correct list of scopes:

scopes <- xml2::read_html("https://developer.spotify.com/documentation/general/guides/scopes/") %>%
+   html_nodes('code') %>%
+   html_text() %>%
+   unique()

But

phdoerfler/Strugatzki@6d689a0