Hi there,
This is not a question which is really related to n8n, but it’s indirectly linked…somehow.
So, last month I installed n8n locally through Docker and the self starter kit to get started with this fantastic tool. You see, I have a long term project in mind, and ai image creation (also locally ) is involved.
For this, I need to use comfyui and it works best with python 3.12.
However, I have noticed that I have now two python versions installed, python 3.10 (insalled last year) and python 3.13 (automatically pushed through the starter kit I assume). They are installed on different paths.
Python 3.10 was needed to be able to use automatic1111, but I’m moving to comfyui.
Question :
- Can I uninstall python 3.10 without concerns so that it doesn’t affect n8n ?
Should there be no concern, I would then go ahead and install the portable version of comfyui which has its own embeded python 3.12 version, which should not be affected by version 3.13.
I am fully aware that this is not a n8n related question, but I don’t want to muck-up anything on my system, well, my son’s pc lol 
Kind regards,
Ken
Hey Ken, hope all is well.
Lots to unpack here.
So you have a system where multiple python versions are installed, you would like to remove 3.10.
First, I don’t believe that self starter kit will install any python version to your operating system, as self starter kit runs in docker and all its files (oversimplification, but still) are stored in these containers. Docker and n8n do not call python.exe from your host OS. They run their own isolated environments inside the container.
Next, removing 3.10 should not affect your n8n, but that doesn’t mean there isn’t another software that won’t be affected. By default your system will use Python 3.13, as it is showing in your where python output first and this means it’s currently first in your PATH.
Hi jabbson,
Thanks for your quick reply, all fine here, hope you too mate.
Yes, I was “accusing” the starter kit, since I can see that version 3.13 was installed in July this year, and it was right on those dates where I had some issues with the whole installation of Docker & starter kit., which you helped me to solve 
The only SW which is using v. 3.10 is a1111 as far as I know. But since I’m not 100% sure if there’s other SW using it, I’ll just go for the portable comfy version and that should solve the issue with conflicting versions (if any) I assume. I’ll leave v 3.10 installed, had no issues so far…
Cheers,
Ken
All well here too, thank you!
This sounds like a solid plan. Alternatively you could always delete it and then re-install if you later discover that something isn’t working. Especially since 3.10 is not going to be used by default in your system (in favour of 3.13, given the order in which they appeared in the output you provided).
Cheers!
