Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project (v1.0.0 and above) adheres to Semantic Versioning.
WARNING: currently the
landingai
library is in alpha version, and it's not strictly following Semantic Versioning. Breaking changes will result a minor version bump instead of a major version bump. Feature releases will result in a patch version bump.
[0.3.0] - 2023-10-04
Major changes
Migration Guide
Whenever you iterate over an image source (NetworkedCamera
, Webcam
, etc), each iteration yields a single Frame
, and not a FrameSet
.
But most FrameSet
operations were migrated to Frame
class, so you can still use the same API to manipulate the Frame
object with very minor changes:
- On
for frame in image_source:
, don't useframe.frames[0]
anymore. Instead, you should just use theframe
object directly (to do resize, check predictions, overlay predictions, etc). Frame.save_image
receives a direct file path to where the frame image should be saved (not just a prefix, as it happens withFrameSet
).
[0.2.0] - 2023-07-12
Major changes
Migration Guide
- The
landingai.vision_pipeline
module was migrated tolandingai.pipeline.FrameSet
- All the image sources were consolidated under
landingai.pipeline.image_source
in particularNetworkedCamera
read_file
is now inlandingai.storage.data_access
and now returns a dictionary. The file contents can be found under "content".
[0.1.0] - 2023-07-06
Major changes
Migration Guide
Below section shows you how to fix the backward incompatible changes when you upgrade the version to 0.1.0
.
- Generate your v2 API key from LandingLens. See here for more information.
-
The
api_secret
parameter is removed in thePredictor
andOcrPredictor
class.api_key
is a named parameter now, which means you must specify the parameter name, i.e.api_key
, if you want to pass it to aPredictor
as an argument. See below code as an example:Before upgrade to
After upgrade to0.1.0
0.1.0