I think Nvda developpers should have think of this mess.
As if they haven't already warned users that it would be?
1. Python2.7 is officially at its end of life. Move on.
2. NVDA2019.3 was in desperate need of Python3's new potential as everyone knew. This port was no small weekend project, so don't go assuming it was one and that no thought went into this. Here's something to think about though. Their hard work still isn't your free lunch. Even if you can't donate, you are generally expected to assist the project in however way you can, which can and should be as simple as testing the alphas/betas, contributing feedback, and contacting NVDA addon developers during the months before when you had plenty of time to. Even then, there are genuine concerns about addons, which are definitely justified, indeed I can't upgrade myself because Sibiac, but I have been keeping 2019.3 betas around as portable for who knows how long. When they release these and ask for feedback, they actually, are looking, for feedback. These are people doing the project more or less grant/donation funded, and feedback makes a huge, huge difference. Some people really need to be, not necessarily more grateful, but cut the negligence a bit, i.e. waiting to the absolute last minute tto install 2019.3 instead of testing the betas and reporting this stuff. I don't suppose any of the legitimate complainers have any mission critical stuff to worry about, and even if they did, you literally have nothing to lose with a portable installation.
The, quote, addon mess, is not NVDA's fault. The final release hasn't been out for one freaking week yet. Give it time before saying they should have thought about this mess.
I'm the only adventure at c: master hahahaha I have unlocked just about everything!