fix(flux): decouple modular flux from classic and qwenimage imports#13958
fix(flux): decouple modular flux from classic and qwenimage imports#13958akshan-main wants to merge 1 commit into
Conversation
|
Hi @akshan-main, thanks for the PR! It does not appear to link an issue it fixes. If this PR addresses an existing issue, please add a closing keyword (e.g. |
Hey! You're right the standard-counterpart imports are the normal pattern (qwenimage, flux2, all do it), so the FluxPipeline and Kontext ones are fine. The one I'd still flag is flux/inputs.py importing from ..qwenimage, the only cross-family import in modular_pipelines. I can narrow this to just that, or close it if you and @yiyixuxu prefer it all as-is. |
What does this PR do?
Addresses Issue 6 of the flux review (#13584). The modular Flux blocks imported
FluxPipeline._pack_latentsand_prepare_latent_image_ids, the classic KontextPREFERRED_KONTEXT_RESOLUTIONSconstant, and two QwenImage modular helpers. This replaces those cross-imports with flux-modular-local copies, followingdecoders.py.The coupling check from the issue returns nothing and the modular flux tests pass.
Before submitting
Who can review?
@DN6 @sayakpaul @yiyixuxu