Repository navigation
Add DeprecationWarnings for deprecated APIs in v0.7 release #548
Description
To avoid too much churn with the v0.7 release, some breaking changes allow fallback to old property names (e.g. passing framerate instead of the new frame_rate). We should upgrade these to runtime warnings in v0.8 so they can be fully removed in v0.9.
Activity
[common] Rename framerate -> frame_rate to be consistent across project
Breakthrough commentedon Jul 22, 2026
Moving to the 0.8 milestone to match the schedule described above: v0.7.x keeps the silent fallbacks (marked with TODO(#548) in the code), v0.8 upgrades them to runtime DeprecationWarnings, and v0.9 removes them.
MuhammadBilalKhan267 commentedon Aug 7, 2026
I’d like to take this. I found the #548 TODOs in FrameTimecode.framerate, equal_framerate, open_video, and the framerate aliases for the OpenCV/PyAV/MoviePy constructors. I’m planning to add DeprecationWarnings with stacklevel=2, preserve the existing alias/precedence behavior, and add/update tests for the warnings. Let me know if there are any additional v0.7 compatibility aliases you want included.
Breakthrough commentedon Aug 9, 2026
Thanks for the PR, left a quick review just now. For the CLI I want to see what it would take to allow both, since it's an exclusive option and can't be specified twice anyways.
Add deprecation warnings for legacy framerate aliases (#563)
Breakthrough commentedon Aug 10, 2026
Before closing this out let's also complete the merging of the CLI options so they just show up all together.
Make frame-rate CLI options aliases (Breakthrough#564)