$EDITOR?$EDITOR?Of course it's a lie. The shell function itself should set the prompt without needing Python. 
Honestly? Less time than I *used* to spend desperately trying to find out how to disable whatever unwanted, clumsy annoyances had been added and automatically enabled in Visual Studio Code literally every other time I opened it, however vehemently I tried to opt-out of automatic new-stuff, @ed1conf
And both time-costs would be many orders of magnitude less than the time-cost of the unpredictable, surprise derailments of my plan to actually get work done: the reason I opened the editor in the first place!
I never open my editor to go hunting for new, unwanted stuff to battle against so any kind of "new stuff" is always surprising and disruptive.
Every second spent customising my Neovim configuration does actually constitute value that belongs to me, too, because those customisations aren't just lost or overridden on the next update, either, and I learn more about the editor with every tweak, too.