Factor out song retrieval and printing. Allow request() to benefit from '|' operator. #10

Request should now allow 2nd_needle

One thing that sticks out to me is that _return_song_results() is called in two places(search()and request()), and in both cases, there might be no songs as a result of the search, and both calling functions assume that _return_song_results() will print the result of the search ("None found") in that case. Importantly, search() and request() will only call _print_song_results() if songs != None (and request() only calls if there's more than one).

But in the case where there are multiple songs, "Multiple found" is printed in _print_song_results(). "Multiple found" could just as easily be printed from _return_song_results(). Or maybe you'd rather put the "None found" in _print_song_results().
The main reason I didn't do the latter is because there are two versions "None found" (the other being "None found after '|' "), and I would rather not return a variable and then pass it to _print_song_results() in order to have the two versions of "None found", because that feels unnecessarily messy and possibly not pythonic.

I can't think of a better way to architect this. Maybe it's somewhat a matter of taste. As mentioned above, _print_song_results() only gets called when there are results from a search. Perhaps if this "code invariant" were somehow made more clear, then the rest would make sense too. I don't think I like the idea of renaming _return_song_results() as _return_song_results_and_or_print_none_found() or renaming _print_song_results() as _print_song_results_only_if_there_are_results(). But maybe you do. Or maybe you like commenting code in a case like this.

The diff isn't super pretty, but the code itself feel pretty good to me.

Thanks
👍 💯