Releases: roboflow/roboflow-python
1.1.8
1.1.7
Updated python version requirements to >=3.8 from 3.6 in setup.py and Readme. Python 3.8 is now the earliest version Roboflow supports because it’s the earliest version supported by our dependencies. Here’s roboflow/supervision#180 from when supervision dropped support for 3.7 a few months ago.
1.1.6
What's Changed
- Add input continue warning for wrong ultralytics version in model deploy by @SolomonLake in #185
Full Changelog: v1.1.15...v1.1.6
v1.1.4
bugfix: project.upload()
was using a wrong parameter name for is_prediction
v1.1.3
Upload of large datasets with workspace.upload_dataset()
is more reliable.
- Doesn't break upload in the middle even if it gets unexpected responses from the backend
- Better separation of output to stdout and stderr (stderr should only have the list of problematic files)
- Ability to resume uploads to the same project (if the workspace has a project with a matching name)
v1.1.2
Fixed logging for the version deploy method.
v1.1.1
In this release we add API support for search.
v1.1.0
v1.0.9
Adding local
param functionality to instance segmentation Version
s.
v1.0.8
add prediction parameter to annotation upload
Adds a new optional is_prediction parameter to the upload functions on projects.
passing is_prediction=True to the upload function when uploading images with annotations allows you to indicate that the annotation data you are adding is a prediction (e.g. from another model or other active learning workflow).
If the annotation is added as a prediction the image will stay in the batch or annotation job it already is in, rather than being added to the dataset for training as part of uploading the annotation data.
bug fixes
minor bug fix for properly using the OBJECT_DETECTION_URL
env variable to override inference endpoint to use for object-detection models