coremltools
coremltools copied to clipboard
apple
Ultralytics YOLOv8 exports require `protobuf>3.20.x`
Hi! Thank you to the maintainers for your great work on coremltools.
I'm the author of YOLOv5 and YOLOv8. We strive to create the world's best AI models and make them available to everyone in nearly all possible export formats in a single environment. This task is made very difficult/impossible due to the coremltools protobuf<3.20.x pin currently in place. I see this has been covered in other issues but I feel the issue is not resolved and is getting worse.
- https://github.com/apple/coremltools/issues/1499
- https://github.com/apple/coremltools/issues/1497
protobuf is now at version 4.24.2 and is used by many packages, some of which have requirements for more recent versions which directly conflict with Apple's outdated pin that is currently in place, making a common environment that supports YOLOv8 export to i.e. ONNX, OpenVINO, TensorRT, TFLite, CoreML, Paddle and NCNN not possible to create or maintain.
coremltools is one of the only format generating version conflicts for protobuf due to this restrictive pin in place.
https://github.com/glenn-jocher/ultralytics/actions/runs/6064473145/job/16452960161?pr=5
It would be very useful to Ultralytics and any other company that is exporting to not just CoreML but other formats for the restrictions in place to be lifted. Thank you.
Hi, is there a plan to upgrade the supported protobuf version to > 4.22 ? The world seems to be split in half at the moment, there are those "sitting" on the old protobuf 3 and the ones who already moved to protobuf 4. Since more and more projects depend now on the latter - coremltools becomes hard to use in new projects...
Thanks in advance!
Also really looking forward to this. I have several libraries I need to use that require >4, so I have to use outdated libraries to get coremltools to work
We are running into similar issues in our Python environment when trying to upgrade from Python 3.8 (Security support ending on 31 Oct 2024). Any update on this?
This issue should be fixed in the 8.0b2 release. Please give it a try.
