We are using megatron-bridge 0.3.0, megatron-core 0.16.0, and megatron-energon 7.3.0 on the NGC NeMo 26.02 image. We upgraded energon from 6.1 to 7.3 in the image and it works at runtime.
However, the [dev] extra of megatron-core on PyPI declares megatron-energon~=6.0 (i.e. <7.0), and megatron-bridge depends on megatron-core[dev]. This makes it impossible to install all three packages together via pip/uv without --no-deps:
Because megatron-core[dev]==0.16.0 depends on megatron-energon[av-decode]>=6.0,<7.dev0,
and megatron-bridge==0.3.0 depends on megatron-core[dev]>=0.15.0a0,
your requirements are unsatisfiable when combined with megatron-energon>=7.3.0.
Energon 7.0 was released in June 2025. Would it be possible to update the megatron-core[dev] constraint to support energon 7.x? Would love to hear your thoughts.
We are using megatron-bridge 0.3.0, megatron-core 0.16.0, and megatron-energon 7.3.0 on the NGC NeMo 26.02 image. We upgraded energon from 6.1 to 7.3 in the image and it works at runtime.
However, the
[dev]extra ofmegatron-coreon PyPI declaresmegatron-energon~=6.0(i.e.<7.0), andmegatron-bridgedepends onmegatron-core[dev]. This makes it impossible to install all three packages together via pip/uv without--no-deps:Energon 7.0 was released in June 2025. Would it be possible to update the
megatron-core[dev]constraint to support energon 7.x? Would love to hear your thoughts.