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

Filter used to strip EXIF data from an image #1

Open
wants to merge 32 commits into
base: master
Choose a base branch
from

Conversation

m-breen
Copy link

@m-breen m-breen commented May 2, 2017

This filter removes any Exif information in the resulting image.
This is useful if you have set the configuration PRESERVE_EXIF_INFO = True but still wish to overwrite this behaviour in some cases (e.g. for image icons)

scorphus and others added 30 commits March 9, 2017 18:57
Aboard is an adverb, whereas onboard is an adjective.
Fixes thumbor#808

in case an exception is thrown inside the engine.read() method the
exception was either not caught properly (in case the THREADPOOL size
is >0) or the result was not a tuple and the unpacking waits for more
data while calling .result() (in case the THREADPOOL size is 0)

the ThreadPoolWorker is using _WorkerItems() wrapping the Future()
and using the Future().set_exception() method so the exception is
thrown at the Future().result() call so it is similar to what happens
when using the ThreadPoolWorker
Improvement to gifsicle error handling
upscale() works together with (adaptive-)fit-in like no_upscale()
together with either /WxH/ or (adaptive-)fit-in + filters:fill()
instead of an absolute timeout the curl http client also supports a
download-speed timeout (if for X seconds the download speed is below Y
bytes/s then abort)
this is now being configurable but disabled by default (and ignored if
the curl client isn't used)
added new timeout setting if using curl http client
In de1d96f, because of the API to engines, the
only way to preserve the EXIF data for storage is to change the global (effective
singleton) configuration. Unfortunately, if another request is doing an Engine.read
at the same time with the same configuration, it suddenly has its configuration
forced by this block. We change this instead to have quasi copy-on-write semantics.
just drop of python 2.6, which is already dropped by thumbor
Allow pillow 4 since there were no BC breaks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

7 participants