Hi I'm a lazy retard

And I would really appreciate it if you released versions of ComfyUI which had older Python interpreters E.G 3.10/3.11 and not just 3.12

At the very least, I've been advising people to reinstall comfy from scratch for the last 6 months, whenever there is a major issue with dependencies. Because for most people it is easier than trying to explain to them how to reinvent the wheel.

However this, I've now discovered, is totally the reason why nobody has been able to resolve their installation issues by following my previously sage advice :P

It would certainly save me, and others who troubleshoot ComfyUI for beginners, a lot of time and hassle explaining to individuals how to replace their Python Embed etc. if the options were simply available on hand with a simple choice of which portable version you choose to download.

I myself have already spent 2 days trying to figure out how to fix this issue, after believing that I had a physically broken copy of windows after resinstalling it a few months ago.

Maybe this is a me problem, but I had been mistakenly believing that it was simply not possible for me to run certain things without again reinstalling my operating system to fix these issues. And I cannot be the only person to have thought so.

The worst part of this is that if I had chosen to try and reinstall my operating system, as I had thought I needed to, it wouldn't have actually fixed the issue or helped me identify what was causing it.

Anyway, this is more of a rant about how confused I am that there are not other Python version options available in a portable package download, when the majority of nodes that are popular to use require an older version, which most people who've been making COmfyUI workflows would still be using by default.

The main problem I have right now is the disconnect this has created inside of the community between individual workflow creators who simply updated an older package version and those who downloaded a recently released package version.

Thereby making it much harder for content creators to troubleshoot issues with the workflows that they create for their community members and making those individuals feel like the problem is localized when in reality it is absolutely not a localized issue.