diff --git a/README.md b/README.md index c8915f2940..24174e60b7 100644 --- a/README.md +++ b/README.md @@ -174,7 +174,7 @@ commandline by using the `CMAKE_ARGS` environment variable. `env CMAKE_ARGS="-DCMAKE_VAR=VALUE1 -DCMAKE_VAR_2=VALUE2" pip install .` -Additionaly, to reproduce CI failures regarding the file manifest, run: +Additionally, to reproduce CI failures regarding the file manifest, run: `make manifest` locally to run the python `check-manifest` program. ## C++ Coverage Builds diff --git a/docs/cxx/cxx.rst b/docs/cxx/cxx.rst index 259b44c059..708005f11f 100644 --- a/docs/cxx/cxx.rst +++ b/docs/cxx/cxx.rst @@ -38,7 +38,7 @@ straightforward and uncontroversial. Reminder: these `sample header files `_ -exist only to show the API; namespacing and other niceties are ommitted. +exist only to show the API; namespacing and other niceties are omitted. Starting Examples +++++++++++++++++ @@ -82,7 +82,7 @@ already defines properties ``name`` and ``metadata``: :: std::color _color; }; -The contructor takes four properties, two of which (``marked_range`` and +The constructor takes four properties, two of which (``marked_range`` and ``color``) are stored directly in ``Marker``, with the remaining two (``name`` and ``metadata``) handled by the base class ``SerializableObjectWithMetadata``. @@ -146,7 +146,7 @@ details above as appropriate for your case. Properties are written to the JSON file in the order they are written to from within ``write_to()``. But the reading code need not be in the same order, and changes in the ordering of either the reading or writing code will not - break compatability with previously written JSON files. + break compatibility with previously written JSON files. However, it is vital to invoke ``Parent::read_from()`` *after* reading all of the derived class properties, while for writing ``Parent::write_to()`` @@ -155,7 +155,7 @@ details above as appropriate for your case. .. Note:: Also note that the order of properties within a JSON file for data that is essentially a ``std::map<>`` (see ``AnyDictionary`` below) - is always alphebetical by key. This ensures deterministic JSON file + is always alphabetical by key. This ensures deterministic JSON file writing which is important for comparison and testing. Using Schemas @@ -193,7 +193,7 @@ to JSON is transported as a C++ ``any``. What can that ``any`` hold? First, the ``any`` can be empty, which corresponds with a ``null`` JSON value. The ``any`` could also hold any of the following "atomic" types: ``bool``, ``int``, ``double``, ``std::string``, ``RationalTime``, ``TimeRange`` and -``TimeTransform``. All but the last three are immediately expressable in JSON, +``TimeTransform``. All but the last three are immediately expressible in JSON, while the three Opentime types are read/written as compound structures with the same format that the current Python implementation delivers. The final "atomic" type that an ``any`` can hold is a ``SerializableObject*``, which @@ -323,7 +323,7 @@ Memory Management +++++++++++++++++ The final topic we must deal with is memory management. Languages like Python -and Swift natually make use of reference counted class instances. We considered +and Swift naturally make use of reference counted class instances. We considered such a route in C++, by requiring that manipulations be done not in terms of ``SerializableObject*`` pointers, but rather using ``std::shared_ptr`` (and the corresponding @@ -679,7 +679,7 @@ What makes this complicated is the following set of rules/constraints: virtue of a Python wrapper instance P being constructed from Python. Until that C++ object X is passed to C++ in some way, then X will exist only as long as P does. -How can we satisfy all these contraints, while ensuring we don't create retain +How can we satisfy all these constraints, while ensuring we don't create retain cycles (which might be fixable with Python garbage collection, but also might not)? Here is the solution we came up with; if you have an alternate suggestion, we would be happy to hear it. diff --git a/docs/tutorials/adapters.md b/docs/tutorials/adapters.md index e5f87da272..17091eecc2 100644 --- a/docs/tutorials/adapters.md +++ b/docs/tutorials/adapters.md @@ -12,7 +12,7 @@ The OpenTimelineIO native file format adapters that are present in the `opentime ## Batteries-Included Adapters -To also install a curated list of additional useful adapters, use the [OpenTimelineIO-Plugins ](https://pypi.org/project/OpenTimelineIO-Plugins/) python package. In addition to the OpenTimelineIO native adapters, you'll get aditional useful adapters including: +To also install a curated list of additional useful adapters, use the [OpenTimelineIO-Plugins ](https://pypi.org/project/OpenTimelineIO-Plugins/) python package. In addition to the OpenTimelineIO native adapters, you'll get additional useful adapters including: - [AAF](https://github.com/OpenTimelineIO/otio-aaf-adapter) - [ale](https://github.com/OpenTimelineIO/otio-ale-adapter) diff --git a/docs/tutorials/contributing.md b/docs/tutorials/contributing.md index dfc0e0c2e2..a2659c515b 100644 --- a/docs/tutorials/contributing.md +++ b/docs/tutorials/contributing.md @@ -19,7 +19,7 @@ Here are the two possible CLAs: Please follow the coding convention and style in each file and in each library when adding new files. ## Platform Support Policy -As recomended by the [VFX Platform](https://vfxplatform.com) (see "Support Guidance"), we support the intended calendar year of the release as well as the three prior years. +As recommended by the [VFX Platform](https://vfxplatform.com) (see "Support Guidance"), we support the intended calendar year of the release as well as the three prior years. ## Git Workflow Here is the workflow we recommend for working on OpenTimelineIO if you intend on contributing changes back: diff --git a/docs/tutorials/otio-filebundles.md b/docs/tutorials/otio-filebundles.md index b0f63e95b7..3e5a97d79f 100644 --- a/docs/tutorials/otio-filebundles.md +++ b/docs/tutorials/otio-filebundles.md @@ -62,7 +62,7 @@ When a bundle is read from disk using the OpenTimelineIO Python API (using the a For example, to view the timeline (not the media) of an otioz file in `otioview`, you can run: -`otioview sommething.otioz` +`otioview something.otioz` Because this will _only_ read the `content.otio` from the bundle, it is usually a fast operation to run. None of the media is decoded or unzipped during this process. diff --git a/docs/tutorials/otio-serialized-schema.md b/docs/tutorials/otio-serialized-schema.md index 6c966f1396..104d4a854d 100644 --- a/docs/tutorials/otio-serialized-schema.md +++ b/docs/tutorials/otio-serialized-schema.md @@ -70,8 +70,8 @@ An object that can be composed within a :class:`~Composition` (such as :class:`~ ``` parameters: -- *metadata*: -- *name*: +- *metadata*: +- *name*: ### Composition.1 @@ -88,12 +88,12 @@ Should be subclassed (for example by :class:`.Track` and :class:`.Stack`), not u ``` parameters: -- *effects*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *markers*: -- *metadata*: -- *name*: -- *source_range*: +- *markers*: +- *metadata*: +- *name*: +- *source_range*: ### Item.1 @@ -106,12 +106,12 @@ None ``` parameters: -- *effects*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *markers*: -- *metadata*: -- *name*: -- *source_range*: +- *markers*: +- *metadata*: +- *name*: +- *source_range*: ### MediaReference.1 @@ -124,10 +124,10 @@ None ``` parameters: -- *available_image_bounds*: -- *available_range*: -- *metadata*: -- *name*: +- *available_image_bounds*: +- *available_range*: +- *metadata*: +- *name*: ### SerializableObjectWithMetadata.1 @@ -140,8 +140,8 @@ None ``` parameters: -- *metadata*: -- *name*: +- *metadata*: +- *name*: ## Module: opentimelineio.hooks @@ -191,8 +191,8 @@ It can be rescaled into another :class:`~RationalTime`'s rate. ``` parameters: -- *rate*: -- *value*: +- *rate*: +- *value*: ### TimeRange.1 @@ -209,8 +209,8 @@ meaning that :meth:`end_time_inclusive` (last portion of a sample in the time ra ``` parameters: -- *duration*: -- *start_time*: +- *duration*: +- *start_time*: ### TimeTransform.1 @@ -223,9 +223,9 @@ parameters: ``` parameters: -- *offset*: -- *rate*: -- *scale*: +- *offset*: +- *rate*: +- *scale*: ## Module: opentimelineio.plugins @@ -244,7 +244,7 @@ Defines an OTIO plugin Manifest. or other features (in the case of adapters, what file suffixes they advertise support for). - For more information, consult the documenation. + For more information, consult the documentation. ``` @@ -289,14 +289,14 @@ Contains a :class:`.MediaReference` and a trim on that media reference. ``` parameters: -- *active_media_reference_key*: -- *effects*: +- *active_media_reference_key*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *markers*: -- *media_references*: -- *metadata*: -- *name*: -- *source_range*: +- *markers*: +- *media_references*: +- *metadata*: +- *name*: +- *source_range*: ### Effect.1 @@ -309,10 +309,10 @@ None ``` parameters: -- *effect_name*: +- *effect_name*: - *enabled*: If true, the Effect is applied. If false, the Effect is omitted. -- *metadata*: -- *name*: +- *metadata*: +- *name*: ### ExternalReference.1 @@ -325,11 +325,11 @@ None ``` parameters: -- *available_image_bounds*: -- *available_range*: -- *metadata*: -- *name*: -- *target_url*: +- *available_image_bounds*: +- *available_range*: +- *metadata*: +- *name*: +- *target_url*: ### FreezeFrame.1 @@ -342,10 +342,10 @@ Hold the first frame of the clip for the duration of the clip. ``` parameters: -- *effect_name*: +- *effect_name*: - *enabled*: If true, the Effect is applied. If false, the Effect is omitted. -- *metadata*: -- *name*: +- *metadata*: +- *name*: - *time_scalar*: Linear time scalar applied to clip. 2.0 means the clip occupies half the time in the parent item, i.e. plays at double speed, 0.5 means the clip occupies twice the time in the parent item, i.e. plays at half speed. @@ -363,12 +363,12 @@ None ``` parameters: -- *effects*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *markers*: -- *metadata*: -- *name*: -- *source_range*: +- *markers*: +- *metadata*: +- *name*: +- *source_range*: ### GeneratorReference.1 @@ -381,12 +381,12 @@ None ``` parameters: -- *available_image_bounds*: -- *available_range*: -- *generator_kind*: -- *metadata*: -- *name*: -- *parameters*: +- *available_image_bounds*: +- *available_range*: +- *generator_kind*: +- *metadata*: +- *name*: +- *parameters*: ### ImageSequenceReference.1 @@ -475,13 +475,13 @@ yield the first three target urls as: ``` parameters: -- *available_image_bounds*: -- *available_range*: +- *available_image_bounds*: +- *available_range*: - *frame_step*: Step between frame numbers in file names. - *frame_zero_padding*: Number of digits to pad zeros out to in frame numbers. -- *metadata*: +- *metadata*: - *missing_frame_policy*: Directive for how frames in sequence not found during playback or rendering should be handled. -- *name*: +- *name*: - *name_prefix*: Everything in the file name leading up to the frame number. - *name_suffix*: Everything after the frame number in the file name. - *rate*: Frame rate if every frame in the sequence were played back. @@ -501,10 +501,10 @@ A time warp that applies a linear speed up or slow down across the entire clip. ``` parameters: -- *effect_name*: +- *effect_name*: - *enabled*: If true, the Effect is applied. If false, the Effect is omitted. -- *metadata*: -- *name*: +- *metadata*: +- *name*: - *time_scalar*: Linear time scalar applied to clip. 2.0 means the clip occupies half the time in the parent item, i.e. plays at double speed, 0.5 means the clip occupies twice the time in the parent item, i.e. plays at half speed. @@ -531,8 +531,8 @@ parameters: - *color*: Color string for this marker (for example: 'RED'), based on the :class:`~Color` enum. - *comment*: Optional comment for this marker. - *marked_range*: Range this marker applies to, relative to the :class:`.Item` this marker is attached to (e.g. the :class:`.Clip` or :class:`.Track` that owns this marker). -- *metadata*: -- *name*: +- *metadata*: +- *name*: ### MissingReference.1 @@ -550,10 +550,10 @@ is not known. ``` parameters: -- *available_image_bounds*: -- *available_range*: -- *metadata*: -- *name*: +- *available_image_bounds*: +- *available_range*: +- *metadata*: +- *name*: ### SerializableCollection.1 @@ -577,8 +577,8 @@ references to a single file. ``` parameters: -- *metadata*: -- *name*: +- *metadata*: +- *name*: ### Stack.1 @@ -591,12 +591,12 @@ None ``` parameters: -- *effects*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *markers*: -- *metadata*: -- *name*: -- *source_range*: +- *markers*: +- *metadata*: +- *name*: +- *source_range*: ### TimeEffect.1 @@ -609,10 +609,10 @@ Base class for all effects that alter the timing of an item. ``` parameters: -- *effect_name*: +- *effect_name*: - *enabled*: If true, the Effect is applied. If false, the Effect is omitted. -- *metadata*: -- *name*: +- *metadata*: +- *name*: ### Timeline.1 @@ -625,10 +625,10 @@ None ``` parameters: -- *global_start_time*: -- *metadata*: -- *name*: -- *tracks*: +- *global_start_time*: +- *metadata*: +- *name*: +- *tracks*: ### Track.1 @@ -641,13 +641,13 @@ None ``` parameters: -- *effects*: +- *effects*: - *enabled*: If true, an Item contributes to compositions. For example, when an audio/video clip is ``enabled=false`` the clip is muted/hidden. -- *kind*: -- *markers*: -- *metadata*: -- *name*: -- *source_range*: +- *kind*: +- *markers*: +- *metadata*: +- *name*: +- *source_range*: ### Transition.1 @@ -662,8 +662,8 @@ dissolve or wipe. parameters: - *in_offset*: Amount of the previous clip this transition overlaps, exclusive. -- *metadata*: -- *name*: +- *metadata*: +- *name*: - *out_offset*: Amount of the next clip this transition overlaps, exclusive. - *transition_type*: Kind of transition, as defined by the :class:`Type` enum. diff --git a/docs/tutorials/quickstart.md b/docs/tutorials/quickstart.md index ffd98ff329..3d01011ab2 100644 --- a/docs/tutorials/quickstart.md +++ b/docs/tutorials/quickstart.md @@ -21,7 +21,7 @@ A default OTIO installation includes only the "Core" adapters, which include the A curated list of adapters for popular file formats like EDL, AAF, ALE, and FCP XML can be installed using the [OpenTimelineIO Plugins package in PyPI](https://pypi.org/project/OpenTimelineIO-Plugins/). These plugins can also be individually installed from their PyPI packages. -For mor information, see the [Adapters](./adapters) section. +For more information, see the [Adapters](./adapters) section. ## Run OTIOView diff --git a/docs/tutorials/write-a-hookscript.md b/docs/tutorials/write-a-hookscript.md index f9cd7d0a3f..cbcb192c71 100644 --- a/docs/tutorials/write-a-hookscript.md +++ b/docs/tutorials/write-a-hookscript.md @@ -86,14 +86,14 @@ del hook_list[1] ### Replacing part of a path for drive mapping -An example use-case would be to create a pre-write adapter hook that checks the argument map for a style being identified as nucoda and then preforms a path replacement on the reference url: +An example use-case would be to create a pre-write adapter hook that checks the argument map for a style being identified as nucoda and then performs a path replacement on the reference url: ```python def hook_function(in_timeline,argument_map=None): adapter_args = argument_map.get('adapter_arguments') if adapter_args and adapter_args.get('style') == 'nucoda': for in_clip in in_timeline.each_clip(): - ''' Change the Path to use windows drive letters ( Nucoda is not otherwise forward slash sensative ) ''' + ''' Change the Path to use windows drive letters ( Nucoda is not otherwise forward slash sensitive ) ''' if in_clip.media_reference: in_clip.media_reference.target_url = in_clip.media_reference.target_url.replace(r'/linux/media/path','S:') ``` diff --git a/docs/tutorials/write-an-adapter.md b/docs/tutorials/write-an-adapter.md index 3b52b73b4c..bae913e031 100644 --- a/docs/tutorials/write-an-adapter.md +++ b/docs/tutorials/write-an-adapter.md @@ -24,7 +24,7 @@ so we can add it to the list of [Tools and Projects Using OpenTimelineIO](https: Adapters may also be organized into their own independent Python project for subsequent [packaging](https://packaging.python.org/tutorials/packaging-projects/#generating-distribution-archives), [distribution](https://packaging.python.org/tutorials/packaging-projects/#uploading-the-distribution-archives) and [installation](https://packaging.python.org/tutorials/packaging-projects/#installing-your-newly-uploaded-package) by [`pip`](https://packaging.python.org/key_projects/#pip). -The easist way is to [otio-plugin-template repo](https://github.com/OpenTimelineIO/otio-plugin-template) and click "Use this template". This will get you started with plugin boilerplate and allow you to develop the adapter in your own GitHub account. +The easiest way is to [otio-plugin-template repo](https://github.com/OpenTimelineIO/otio-plugin-template) and click "Use this template". This will get you started with plugin boilerplate and allow you to develop the adapter in your own GitHub account. If you'd like to work from scratch, we recommend you organize your project like so: ``` diff --git a/examples/sample_plugin/setup.py b/examples/sample_plugin/setup.py index d7f925738f..9509af61ed 100644 --- a/examples/sample_plugin/setup.py +++ b/examples/sample_plugin/setup.py @@ -15,7 +15,7 @@ ``opentimelineio.plugins``. 2. Declaring that for the ``opentimelineio.plugins`` group, this module provides a plugin named ``track_counter`` and the module that should be - loaded for tha plugin is the ``otio_counter`` module. + loaded for that plugin is the ``otio_counter`` module. For more information about python plugins, see the python packaging guide: https://packaging.python.org/guides/creating-and-discovering-plugins/#using-package-metadata diff --git a/examples/util.h b/examples/util.h index 671397658b..924fbb38e4 100644 --- a/examples/util.h +++ b/examples/util.h @@ -9,7 +9,7 @@ namespace examples { -// Normalize path (change '\' path delimeters to '/'). +// Normalize path (change '\' path delimiters to '/'). std::string normalize_path(std::string const&); // Get the absolute path. @@ -25,4 +25,3 @@ std::vector glob(std::string const& path, std::string const& patter void print_error(opentimelineio::OPENTIMELINEIO_VERSION::ErrorStatus const&); } - diff --git a/readthedocs-conda.yml b/readthedocs-conda.yml index 031ff50c86..3b5c9b147c 100644 --- a/readthedocs-conda.yml +++ b/readthedocs-conda.yml @@ -1,4 +1,4 @@ -# YAML file for configurating the Conda environment in read the docs. +# YAML file for configuring the Conda environment in read the docs. name: opentimelineio-readthedocs dependencies: diff --git a/setup.py b/setup.py index 42ac6344d1..6f277ddbfa 100644 --- a/setup.py +++ b/setup.py @@ -113,7 +113,7 @@ def generate_cmake_arguments(self): '-DOTIO_PYTHON_INSTALL_DIR=' + install_dir, # turn off the C++ tests during a Python build '-DBUILD_TESTING:BOOL=OFF', - # Python modules wil be installed by setuptools. + # Python modules will be installed by setuptools. '-DOTIO_INSTALL_PYTHON_MODULES:BOOL=OFF', ] if self.is_windows(): diff --git a/src/opentimelineio/CORE_VERSION_MAP.cpp b/src/opentimelineio/CORE_VERSION_MAP.cpp index 60e160f7d7..1043902253 100644 --- a/src/opentimelineio/CORE_VERSION_MAP.cpp +++ b/src/opentimelineio/CORE_VERSION_MAP.cpp @@ -7,8 +7,8 @@ // version-map-update` and this file should be regenerated. // // This maps a "Label" to a map of Schema name to Schema version. The intent is -// that these sets of schemas can be used for compatability with future -// versions of OTIO, so that a newer version of OTIO can target a compatability +// that these sets of schemas can be used for compatibility with future +// versions of OTIO, so that a newer version of OTIO can target a compatibility // version of an older library. #include "opentimelineio/typeRegistry.h" diff --git a/src/opentimelineio/CORE_VERSION_MAP.last.cpp b/src/opentimelineio/CORE_VERSION_MAP.last.cpp index 257b693c18..a66c684d16 100644 --- a/src/opentimelineio/CORE_VERSION_MAP.last.cpp +++ b/src/opentimelineio/CORE_VERSION_MAP.last.cpp @@ -7,8 +7,8 @@ // version-map-update` and this file should be regenerated. // // This maps a "Label" to a map of Schema name to Schema version. The intent is -// that these sets of schemas can be used for compatability with future -// versions of OTIO, so that a newer version of OTIO can target a compatability +// that these sets of schemas can be used for compatibility with future +// versions of OTIO, so that a newer version of OTIO can target a compatibility // version of an older library. #include "opentimelineio/typeRegistry.h" diff --git a/src/opentimelineio/algo/editAlgorithm.cpp b/src/opentimelineio/algo/editAlgorithm.cpp index b0694264aa..b12d7a5d04 100644 --- a/src/opentimelineio/algo/editAlgorithm.cpp +++ b/src/opentimelineio/algo/editAlgorithm.cpp @@ -738,7 +738,7 @@ roll( RationalTime next_start_time = next_range.start_time(); RationalTime out_offset = delta_out; - // If avalable range, clamp to it. + // If available range, clamp to it. if (!(isEqual(available_range.duration().value(), 0.0))) { RationalTime available_start_time = diff --git a/src/opentimelineio/serializableObject.h b/src/opentimelineio/serializableObject.h index 63ccc0438a..a0ba2892a7 100644 --- a/src/opentimelineio/serializableObject.h +++ b/src/opentimelineio/serializableObject.h @@ -449,7 +449,7 @@ class SerializableObject private: ///@{ - /** Convience routines for converting various STL structures of specific + /** Convenience routines for converting various STL structures of specific types to a parallel hierarchy holding std::anys!. */ template diff --git a/src/py-opentimelineio/opentimelineio/console/otiotool.py b/src/py-opentimelineio/opentimelineio/console/otiotool.py index 1b1499b463..d6e055271c 100755 --- a/src/py-opentimelineio/opentimelineio/console/otiotool.py +++ b/src/py-opentimelineio/opentimelineio/console/otiotool.py @@ -26,7 +26,7 @@ def main(): """otiotool main program. - This function is resposible for executing the steps specified + This function is responsible for executing the steps specified by all of the command line arguments in the right order. """ diff --git a/src/py-opentimelineio/opentimelineio/plugins/manifest.py b/src/py-opentimelineio/opentimelineio/plugins/manifest.py index 62a4f06274..b0cf891ef7 100644 --- a/src/py-opentimelineio/opentimelineio/plugins/manifest.py +++ b/src/py-opentimelineio/opentimelineio/plugins/manifest.py @@ -87,7 +87,7 @@ class Manifest(core.SerializableObject): or other features (in the case of adapters, what file suffixes they advertise support for). - For more information, consult the documenation. + For more information, consult the documentation. """ _serializable_label = "PluginManifest.1" diff --git a/tests/baselines/plugin_module/otio_mockplugin/__init__.py b/tests/baselines/plugin_module/otio_mockplugin/__init__.py index 67c6073c0b..4b88e7f4fd 100644 --- a/tests/baselines/plugin_module/otio_mockplugin/__init__.py +++ b/tests/baselines/plugin_module/otio_mockplugin/__init__.py @@ -13,7 +13,7 @@ This would allow you to programmatically generate a manifest rather than have it be static on disk, allowing you to switch features on or off or do some -template substition or any other kind of procedural processing. +template substitution or any other kind of procedural processing. This unit test uses a very simple example that just reads the manifest from a non-standard json file path. diff --git a/tests/sample_data/nested_example.otio b/tests/sample_data/nested_example.otio index 3ae09d8d46..ff89c60553 100644 --- a/tests/sample_data/nested_example.otio +++ b/tests/sample_data/nested_example.otio @@ -287,7 +287,7 @@ "effects": [], "kind": "Video", "markers": [], - "eabled": true, + "enabled": true, "metadata": {}, "name": "Top Level Track", "source_range": null diff --git a/tests/sample_data/transition.otio b/tests/sample_data/transition.otio index eb869400d5..529692383f 100755 --- a/tests/sample_data/transition.otio +++ b/tests/sample_data/transition.otio @@ -23,7 +23,7 @@ "source_range": null, "effects": [], "markers": [], - "enabeld": true, + "enabled": true, "children": [ { "OTIO_SCHEMA": "Clip.1", diff --git a/tests/test_adapter_plugin.py b/tests/test_adapter_plugin.py index cd14f63927..f855f50e9a 100755 --- a/tests/test_adapter_plugin.py +++ b/tests/test_adapter_plugin.py @@ -82,7 +82,7 @@ def test_load_adapter_module(self): # call through the module accessor self.assertEqual(self.adp.module().read_from_file("foo").name, "foo") - # call through the convienence wrapper + # call through the convenience wrapper self.assertEqual(self.adp.read_from_file("foo").name, "foo") def test_has_feature(self): diff --git a/tests/test_opentime.py b/tests/test_opentime.py index 74143e29f1..16a564fe7f 100755 --- a/tests/test_opentime.py +++ b/tests/test_opentime.py @@ -235,7 +235,7 @@ def test_dropframe_timecode_2997fps(self): """Test drop frame in action. Focused on minute roll overs We nominal_fps 30 for frame calculation - For this frame rate we drop 2 frames per minute execpt every 10th. + For this frame rate we drop 2 frames per minute except every 10th. Compensation is calculated like this when below 10 minutes: (fps * seconds + frames - dropframes * (minutes - 1)) @@ -343,7 +343,7 @@ def test_timecode_ntsc_2997fps(self): tc = otio.opentime.to_timecode(t, rate_float, drop_frame=False) self.assertEqual(tc, '10:02:23:29') - # Detect DFTC from rate for backward compatability with old versions + # Detect DFTC from rate for backward compatibility with old versions tc_auto = otio.opentime.to_timecode(t, rate_float) self.assertEqual(tc_auto, '10:03:00;05') @@ -387,7 +387,7 @@ def test_timecode_2997(self): to_tc = otio.opentime.to_timecode(t, rate=ntsc_2997, drop_frame=False) to_auto_tc = otio.opentime.to_timecode(t, rate=ntsc_2997) - # 29.97 should auto-detect dftc for backward compatability + # 29.97 should auto-detect dftc for backward compatibility self.assertEqual(to_dftc, to_auto_tc) # check calculated against reference diff --git a/tests/test_timeline.py b/tests/test_timeline.py index e50eb8b05e..a5dbe14ab0 100755 --- a/tests/test_timeline.py +++ b/tests/test_timeline.py @@ -133,7 +133,7 @@ def test_big_integers(self): for (name, value) in supported_doubles: md[name] = value - # float('nan') != float('nan'), so need ot test isnan(value) instead + # float('nan') != float('nan'), so need to test isnan(value) instead if not math.isnan(value): self.assertEqual( md[name], @@ -171,7 +171,7 @@ def test_big_integers(self): ) except Exception as e: self.fail( - "A problem occured when attempting to serialize {} " + "A problem occurred when attempting to serialize {} " "with value: {}. Error message was: {}".format( name, value, @@ -186,7 +186,7 @@ def test_big_integers(self): ) except Exception as e: self.fail( - "A problem occured when attempting to serialize {} " + "A problem occurred when attempting to serialize {} " "with value: {}. Error message was: {}".format( name, value,