[Bug]: Pillow 11.x breaks Gradio 3.x

[iwr-redmond]

Checklist

• The issue has not been resolved by following the troubleshooting guide
• The issue exists on a clean installation of FooocusPlus
• The issue exists in the current version of FooocusPlus
• The issue has not been reported before recently
• The issue has been reported before but has not been fixed yet

What happened?

Dependency resolution breaks when pillow==11.0.0

Steps to reproduce the problem

1. Fresh download of FooocusPlus on Linux
2. pip install -r requirements_versions.txt

What should have happened?

Pillow will need to be downgraded to pillow<11.0.0 in requirements_versions.txt

What browsers do you use to access FooocusPlus?

Mozilla Firefox

Where are you running FooocusPlus?

Locally

What operating system are you using?

Ubuntu 24.04

Console logs

INFO: pip is looking at multiple versions of gradio to determine which version is compatible with other requirements. This could take a while.

The conflict is caused by:
    The user requested pillow==11.0.0
    diffusers 0.32.2 depends on Pillow
    gradio 3.43.2 depends on pillow<11.0 and >=8.0

Additionally, some packages in these conflicts have no matching distributions available for your environment:
    pillow

Additional information

Upstream requirements.txt file

[DavidDragonsage]

@iwr-redmond How curious - no complaints from anyone on the Windows platform. It looks like I should be able to restore Pillow 11.0.0 with the Gradio upgrade. It is now scheduled for FooocusPlus 1.1.0, at the same time as the Comfy upgrade. Let's take all the bad tasting medicine at once!

Ooh, this is a bad downgrade! Pillow is so essential that if the downgrade fails then the user is locked out from running requirements.txt again - it just happened to me. Maybe I need to start upgrading to Gradio 6 today. I will push #314 out right now and start investigating the Gradio upgrade.

[iwr-redmond]

🤞

[iwr-redmond]

@iwr-redmond How curious - no complaints from anyone on the Windows platform.

It's because pip allows you to break packages when doing single installations. It only fails when jointly installing incompatible packages.

Log snippet

pip install 'gradio==3.43.2' 'pillow==11.0.0'

ERROR: Cannot install gradio==3.43.2 and pillow==11.0.0 because these package versions have conflicting dependencies.

pip install 'gradio==3.43.2'

Successfully installed aiofiles-23.2.1 altair-5.5.0 annotated-doc-0.0.4 annotated-types-0.7.0 anyio-4.12.1 exceptiongroup-1.3.1 fastapi-0.128.0 ffmpy-1.0.0 gradio-3.43.2 gradio-client-0.5.0 h11-0.16.0 hf-xet-1.2.0 httpcore-1.0.9 httpx-0.28.1 huggingface-hub-1.3.1 importlib-resources-6.5.2 narwhals-2.15.0 orjson-3.11.5 pydantic-2.12.5 pydantic-core-2.41.5 pydub-0.25.1 python-multipart-0.0.21 starlette-0.50.0 typer-slim-0.21.1 typing-extensions-4.15.0 typing-inspection-0.4.2 uvicorn-0.40.0 websockets-11.0.3

pip install 'pillow==11.0.0'

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
gradio 3.43.2 requires pillow<11.0,>=8.0, but you have pillow 11.0.0 which is incompatible.
Successfully installed pillow-11.0.0

pip show gradio pillow

Name: gradio
Version: 3.43.2
---
Name: pillow
Version: 11.0.0

[DavidDragonsage]

@iwr-redmond How curious - no complaints from anyone on the Windows platform.

It's because pip allows you to break packages when doing single installations. It only fails when jointly installing incompatible packages.
Log snippet

pip install 'gradio==3.43.2' 'pillow==11.0.0'

ERROR: Cannot install gradio==3.43.2 and pillow==11.0.0 because these package versions have conflicting dependencies.

pip install 'gradio==3.43.2'

Successfully installed aiofiles-23.2.1 altair-5.5.0 annotated-doc-0.0.4 annotated-types-0.7.0 anyio-4.12.1 exceptiongroup-1.3.1 fastapi-0.128.0 ffmpy-1.0.0 gradio-3.43.2 gradio-client-0.5.0 h11-0.16.0 hf-xet-1.2.0 httpcore-1.0.9 httpx-0.28.1 huggingface-hub-1.3.1 importlib-resources-6.5.2 narwhals-2.15.0 orjson-3.11.5 pydantic-2.12.5 pydantic-core-2.41.5 pydub-0.25.1 python-multipart-0.0.21 starlette-0.50.0 typer-slim-0.21.1 typing-extensions-4.15.0 typing-inspection-0.4.2 uvicorn-0.40.0 websockets-11.0.3

pip install 'pillow==11.0.0'

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
gradio 3.43.2 requires pillow<11.0,>=8.0, but you have pillow 11.0.0 which is incompatible.
Successfully installed pillow-11.0.0

pip show gradio pillow

Name: gradio
Version: 3.43.2

Name: pillow
Version: 11.0.0

Well that's pretty annoying! Pip is kind of a useless program if it allows you to install incompatible libraries.

[iwr-redmond]

It may be necessary to consider building a constraints.txt file to prevent the default behavior. A more permanent solution in the future would be to implement an update notifier rather than using Git for updates (option 2 from #110). This would insulate users from dependency hell by distributing built packages rather than just the source code plus a requirements.txt file.

[DavidDragonsage]

It may be necessary to consider building a constraints.txt file to prevent the default behavior.

I don't know if I understood the docs, but does this mean you would somehow have to research all the possible incompatibilities yourself? I'm don't think the developer would even know all the possible bad combinations. And if there was an incompatibility listed between Pillow and Gradio it sure wasn't obvious. Actually I used Google AI to determine the best version of Pillow to use after the very latest version failed. Google AI reported that Pillow 11.0.0 had the best chance of success.

[iwr-redmond]

A constraints file mostly just restates the requirements.txt list. In this instance, you would restate gradio==3.43.2 to prevent Pillow 11.x from being installed. You would not have to know that Gradio might be impacted.

[DavidDragonsage]

Ah, so the process is automatic. Just make a copy of requirements.txt and call it constraints.txt. I'm surprised there isn't a switch in Pip to do the same thing, but anyway that simple enough.