Matthew Tretter f289ff3199 Back ImageSpecFields with spec registry ... This marks a major step towards centralizing some of the "spec" logic and creating a single access point for them. Because `ImageSpecFields` are just alternative interfaces for defining and registering specs, they can be accessed and overridden in the same manner as other specs (like those used by template tags): via the spec registry.		2012-10-04 22:56:26 -04:00
..
imagecache	Remove print statement	2012-10-03 22:31:45 -04:00
management	Rename force flag to force-revalidation	2012-02-02 23:23:20 -05:00
models	Back ImageSpecFields with spec registry	2012-10-04 22:56:26 -04:00
processors	Add __init__ to Reflection processor; closes #141	2012-07-25 22:20:15 -04:00
templates/imagekit/admin	Proper handling of empty images and missing fields	2011-11-03 12:33:22 -04:00
templatetags	Move spec registry	2012-10-04 22:02:29 -04:00
__init__.py	Move spec classes to specs module	2012-10-04 21:58:22 -04:00
admin.py	Allow callables for AdminThumbnail image_field arg	2012-07-19 20:08:03 -04:00
conf.py	Create ImageSpecs; remove generators	2012-10-04 21:37:20 -04:00
exceptions.py	Move exceptions	2012-10-04 21:57:33 -04:00
files.py	Create ImageSpecs; remove generators	2012-10-04 21:37:20 -04:00
lib.py	Use cStringIO if available	2012-05-12 15:45:08 -04:00
specs.py	Back ImageSpecFields with spec registry	2012-10-04 22:56:26 -04:00
utils.py	Create ImageSpecs; remove generators	2012-10-04 21:37:20 -04:00