launchpad-dependencies shouldn't depend on python-imaging

Bug #559302 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad Dependencies
Fix Released
Undecided
Francis J. Lacoste

Bug Description

We'd like python-imaging (>=1.1.7) moved to launchpad-developer-dependencies:

<flacoste> it could be made a developer dependencies
<flacoste> but it would require a small code change
<flacoste> spriteutils import Image at the top-level
<flacoste> but it's only needed when rebuilding the sprite image file
<flacoste> which is only done by a developer
<mthaddon> and it's not needed for anything else in production?
<flacoste> so by moving it to be imported only when 'create-image' is invoked would allow us to move the dep
<flacoste> doesn't look like it

Related branches

Tom Haddon (mthaddon)
Changed in launchpad-foundations:
assignee: nobody → Francis J. Lacoste (flacoste)
Changed in launchpad-foundations:
status: New → In Progress
Changed in launchpad-foundations:
status: In Progress → Won't Fix
Changed in launchpad-foundations:
status: Won't Fix → In Progress
affects: launchpad-foundations → meta-lp-deps
Revision history for this message
Francis J. Lacoste (flacoste) wrote :

Actually, we are also using that dependency in the app server to validate the size and format of images uploaded by user. But I moved the requirements for 1.1.7 to launchpad-developer-dependancies, since that version is only required when rebuilding the sprites.

Changed in meta-lp-deps:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.