Repository navigation
Add python bindings for the edit functions - #2077
darbyjohnston wants to merge 1 commit into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2077 +/- ##
==========================================
+ Coverage 83.61% 85.46% +1.84%
==========================================
Files 183 186 +3
Lines 13579 13742 +163
Branches 1261 1254 -7
==========================================
+ Hits 11354 11744 +390
+ Misses 2052 1824 -228
- Partials 173 174 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
The functions in algo/editAlgorithm.h (overwrite, insert, trim, slice, slip, slide, ripple, roll, fill and remove) and the ReferencePoint enum are available as otio.algorithms.edit. The tests check that each one can be called from Python; the algorithms are tested in C++. Signed-off-by: Darby Johnston <darbyjohnston@yahoo.com>
007d1b1 to
2d72e54
Compare
|
Fixes from the original PR split out here: |
|
@darbyjohnston is it worth setting up a CI job that checks the coverage of the C++ functions for python coverage going forwards, similar to the one that checks for test coverage and posting that as a comment? |
|
I think the edit functions didn't have Python bindings because they were considered experimental: They have been in C++ API for a few years now, so it seems reasonable to also include them with Python. |
I would agree with that assessment. |
This PR adds Python bindings for the editing functions:
src/opentimelineio/algo/editAlgorithm.hAssisted-by: Claude Code / Claude Opus 5.5