Pilgram module not found
Hi. I keep getting this message:
File "\ComfyUI_windows_portable\ComfyUI\custom_nodes\was-node-suite-comfyui\WAS_Node_Suite.py", line 4125, in image_blending_mode import pilgram ModuleNotFoundError: No module named 'pilgram'
I do a pip install pilgram and it tells me it is already installed. I have a folder ComfyUI_Pilgram in \custom-nodes\
What can i do to fix? thanks
ComfyUI_Pilgram is probably a conflict. My suite uses pilgram package and that custom_node may be overriding it in the namespace, not sure. But all it's doing is importing pilgram, so if it can't import it something is wrong with the environment setup.
cheers. i believe i have found the issue. If running a portable version of comfyui then in was-node-suite you need to run the install.bat This has fixed the issue for me however now i have new issues in different parts of the workflow. hahaha. Not related i think.
I solved this like this in 2025.
in powershell
- activate venv
-
cd /custom-nodes/was-node-suite/ -
set SETUPTOOLS_USE_DISTUTILS=stdlib- this installation is using a zipped standard library, and the _distutils_hack choked on it. Some packages like setuptools or pip assume distutils is a regular directory, not bundled up in a .zip. -
.\install.bat
I solved this like this in 2025.
in powershell
1. activate venv 2. `cd /custom-nodes/was-node-suite/` 3. `set SETUPTOOLS_USE_DISTUTILS=stdlib` - this installation is using a zipped standard library, and the _distutils_hack choked on it. Some packages like setuptools or pip assume distutils is a regular directory, not bundled up in a .zip. 4. `.\install.bat`
Pilgram is pretty ancient now, and we're all running newer Python versions.
Wonder if this is something to even keep. Most these filters could be reproduced for the pack itself, or removed. Though I recently saw someone relying on it and monitor effect nodes so not sure.
I just encountered this problem and solved it using the same technique I applied to my "insightface" issue. I'll try to explain clearly (English isn't my first language, and I'm not a programmer).
- Navigate to your ComfyUI root folder. In the address bar, type
cmdand press Enter to open the command prompt. Then run:
pip install pilgram
- Locate your Windows Python installation folder and find the pilgram files folders (
pilgramandpilgram-1.2.1.dist-info). They're typically in:
C:\Users<yourusername>\AppData\Local\Programs\Python\Python311\Lib\site-packages
- Copy these two folders and paste them into your ComfyUI installation's embedded Python folder:
~~\ComfyUI\python_embeded
- Restart ComfyUI - this should resolve the issue.
I just encountered this problem and solved it using the same technique I applied to my "insightface" issue. I'll try to explain clearly (English isn't my first language, and I'm not a programmer).
- Navigate to your ComfyUI root folder. In the address bar, type
cmdand press Enter to open the command prompt. Then run:pip install pilgram
- Locate your Windows Python installation folder and find the pilgram files folders (
pilgramandpilgram-1.2.1.dist-info). They're typically in:C:\Users<yourusername>\AppData\Local\Programs\Python\Python311\Lib\site-packages
- Copy these two folders and paste them into your ComfyUI installation's embedded Python folder:
~~\ComfyUI\python_embeded
- Restart ComfyUI - this should resolve the issue.
You can also do like: C:\ComfyUI\python_embeded\python.exe -m pip install pilgram
The issue may be using newer Python versions that it can accept. Pilgram was written a long time ago, and now ComfyUI is compatible with Python 3.13
You can also do like:
C:\ComfyUI\python_embeded\python.exe -m pip install pilgramThe issue may be using newer Python versions that it can accept. Pilgram was written a long time ago, and now ComfyUI is compatible with Python 3.13
This doesn't work for most people who encounter this problem. You're right, the problem is related to the Python version, but for other modes, we sometimes need to run Python 3.13.
Python 3.13 is not recommended for ComfyUI, as written on its readme. ComfyUI itself is compatible but 90% of custom nodes were written for 3.11 and 3.12. It's best you find alternatives to whatever reason you think you need python 3.13.