-
-
Notifications
You must be signed in to change notification settings - Fork 16.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monkey patching cv2 methods crashes own scripts #7285
Comments
👋 Hello @janzumsteg, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution. If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you. If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available. For business inquiries or professional support requests please visit https://ultralytics.com or email [email protected]. RequirementsPython>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started: git clone https://github.com/ultralytics/yolov5 # clone
cd yolov5
pip install -r requirements.txt # install EnvironmentsYOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
StatusIf this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), validation (val.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit. |
@janzumsteg good news 😃! Your original issue may now be fixed ✅ in PR #7287. This PR updates the patched function to accept a second argument just like the original function, and the code to reproduce the error now runs without issue: To receive this update:
Thank you for spotting this issue and informing us of the problem. Please let us know if this update resolves the issue for you, and feel free to inform us of any other issues you discover or feature requests that come to mind. Happy trainings with YOLOv5 🚀! |
Hi @glenn-jocher, I have been playing with >>> import cv2
>>> help(cv2.imread)
Help on built-in function imread:
imread(...)
imread(filename[, flags]) -> retval
(...)
>>> import yolov5
>>> help(cv2.imread)
Help on function imread in module yolov5.utils.general:
imread(path, flags=1)
I proposed fix here I would personally prefer if these methods are not monkey-patched each time I import yolov5 though, I can prepare a PR if this is something you would consider. |
Hi @grzegorzk 👋, it's great to hear your feedback on the monkey-patched Regarding the monkey-patching, I totally understand your concern. We are currently evaluating different options to reduce the impact of monkey-patching on user-defined scripts. Your willingness to submit a PR to help address this is much appreciated! We'd certainly be open to reviewing your solution. Thank you for your contribution and for helping make YOLOv5 even better 🙌! |
Search before asking
YOLOv5 Component
PyTorch Hub
Bug
The current master branch contains monkey patches of
cv2.imread
,cv2.imwrite
andcv2.imshow
(seeyolov5/utils/general.py
Line 944 in ea72b84
torch.hub.load
), the respective methods in my own scripts will also be overwritten without any hints. Moreover, the signature ofcv2.imread
changed with these monkey patches resulting inTypeError: imread() takes 1 positional argument but 2 were given
.Related PRs:
cv2.imwrite
on non-ASCII paths #7139np.fromfile()
Chinese image paths fix #6979Environment
No response
Minimal Reproducible Example
Additional
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: