Skip to content
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

import order bug fix #28

Merged
merged 1 commit into from Jan 5, 2019
Merged

import order bug fix #28

merged 1 commit into from Jan 5, 2019

Conversation

rossilhf
Copy link
Contributor

the order of import cause different cv2.imread() result, I don't know
reason. In current order, cv2.imread() returns None.
But after change the order of "import tensorflow as tf" and "import
cv2", the function works correctly.

the order of import cause different cv2.imread() result, I don't know
reason. In current order, cv2.imread() returns None.
But after change the order of "import tensorflow as tf" and "import
cv2", the function works correctly.
@rossilhf
Copy link
Contributor Author

http://stackoverflow.com/questions/43535134/why-different-import-order-effects-result-in-python
this is the page that I report the "import order" bug I encounted

@gliese581gg gliese581gg merged commit dbff8b9 into gliese581gg:master Jan 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants