-
Notifications
You must be signed in to change notification settings - Fork 805
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
OSX and sudo install requirements #34
Comments
You can try However, the root of this issue lies in MacOS or in how some of its package managers handle Python installations. I'm not too famialiar with all the MacOS weirdness, but the I have no access to a Mac currently, but this should be pretty easy to test with a dummy package. Moving the licenses to |
This might be of interest: |
In would think that the licenses should be
The installation prefix here is
But this issue can probably be solve by using |
Yes, I agree that moving the files into Note that the Travis builds are currently broken (I don't know yet why) but I'm going try to fix the issue asap since OpenCV 3.3.0 release is getting closer. |
I am not sure where to include them. Should the files be installed in the cv2 folder? |
I'm not sure either, but I would like to keep the license files in the root of this project so that they can be found easily. I would have used Option 1 Add
to Option 2 Copy the license files during build to Please comment if you have any better ideas. For some reason Python's packaging tools make these simple looking things unbelievably complex. |
Submitted a pull request for package_data. |
When trying to install
opencv-python
on OS X (python3 installed via Homebrew), installing as an unprivileged user failed with the following message:After installing with
sudo -H pip3 install opencv-python
, the package worked.Can the sudo requirement be eliminated by not writing the license to
/usr/local/
?The text was updated successfully, but these errors were encountered: