-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Package libjpeg and libpng within torchvision #2291
Comments
It may right now I think, we really need to improve that situation. It would also force the users to mix channels. |
@fmassa said that size of the wheels isn't critical, and just bundling in |
@fmassa, is it possible to have assignment permissions on this repository? |
@jjhelmus is it possible to update libjpeg-turbo to the latest version on the default channel in Anaconda? It seems that the current version (1.2.1) is older than the one found on conda-forge. |
libjpeg-turbo is provided as a CDT in |
Is there a way to force the system to use a system libraries for instance libjpeg instead of the one with Pillow (default)? I am asking this because the libjpeg library available in Pillow does not have debug symbols available which makes it hard to profile. |
With the addition of image-reading functions enabled by default in torchvision #1632 #1881 #1909, we will need to properly package libjpeg and libpng (and other libraries will be used soon as well, like ffmpeg) so that users of {Windows, Linux, OSX} x {pip, conda, source} can use those new functionalities in torchvision without issues.
I believe the current recommended way that PyTorch deals with 3rd-party libraries is the following:
conda-forge
channel would bring problems due to conflicts with other libraries we use.We will also need to make sure our CI (which is fairly tied to binary builds) is updated.
cc @seemethere @rgommers
The text was updated successfully, but these errors were encountered: