Especially during the installation of Python, the AlphaPeptDeep library build feels like it shows a lot of LongWaitDlgs. The ideal is to show just one such form that progresses through everything the user is waiting for. It is somewhat bad form to pop up a new long wait, and especially bad form when each lasts a fraction of a second as they do in the Python installation.

I can see that library building itself uses multiple LongWaitDlgs for library loading, iRT training, etc.

It is likely quite a lot of work to get this all down to the ideal where there is just one between the user clicking a button and the next time they can interact with the UI, but it is also probably worthwhile to set a breakpoint on the LongWaitDlg constructor and try to get the number of times it gets called between those two events down as much as possible, certainly at least the click of "Finish" and the form saying that Python is successfully installed should be made on LongWaitDlg.