Short answer: yes — bumping Prefect’s minimum pydocket to a version that handles fakeredis>=2.35 is the right fix. What we’ve seen: - Prefect 3.x currently allows

pydocket>=0.17.7

. With

fakeredis>=2.35.0

, server startup can fail due to an ImportError in pydocket’s memory backend. - This is tracked here: Broken prefect_test_harness with new subdependency fakeredis 2.35.0. There’s also a related server-startup error thread: redis.exceptions.ResponseError: unknown command evalsha. - As an interim workaround, Prefect pinned

fakeredis<2.35.0

to avoid the startup error. - A newer pydocket release addresses the compatibility so the fakeredis pin can be dropped. The recommended path forward is to bump Prefect’s requirement to a pydocket version that includes the fix (>=0.19.0), then remove the fakeredis pin. Recommended action: - Upstream: bump Prefect’s requirement to

pydocket>=0.19.0

and drop the

fakeredis<2.35.0

pin. - If you’re blocked today: either pin

fakeredis<2.35.0

or install a fixed pydocket (>=0.19.0) in your environment to restore compatibility. If you want, I can link you to the PR once it’s public/merged or help validate a local constraints file to get you unblocked immediately. What Prefect version are you running and are you hitting the

fakeredis.aioredis FakeConnection

ImportError on startup?