magic-removal: from django.parts.media.photos import get_thumbnail_url
4 views
Skip to first unread message
Jeremy Jones
Mar 15, 2006, 5:50:51 AM3/15/06
to Django Users, Django Developers
Sorry for cross-posting, but I thought this would be relevant for
both groups. I'm reworking a simple store with the magic removal branch
and running into a bit of a snag. When I create a record in the admin
interface for a model which has an ImageField, I get an import error in
admin_list.py on ``from django.parts.media.photos import
get_thumbnail_url``. 0.91 has a parts.media.photos module, but
magic-removal doesn't. I dropped in the ``parts`` directory from 0.91
into my magic-removal branch and it seems to work fine without
modification. Is this something that's going to be added back in as
is (so that I can just move forward with my dropped in code)?
both groups. I'm reworking a simple store with the magic removal branch
and running into a bit of a snag. When I create a record in the admin
interface for a model which has an ImageField, I get an import error in
admin_list.py on ``from django.parts.media.photos import
get_thumbnail_url``. 0.91 has a parts.media.photos module, but
magic-removal doesn't. I dropped in the ``parts`` directory from 0.91
into my magic-removal branch and it seems to work fine without
modification. Is this something that's going to be added back in as
is (so that I can just move forward with my dropped in code)?
- jmj
Adrian Holovaty
Mar 15, 2006, 9:51:25 PM3/15/06
to django-d...@googlegroups.com
On 3/15/06, Jeremy Jones <zane...@bellsouth.net> wrote:
> I'm reworking a simple store with the magic removal branch
> and running into a bit of a snag. When I create a record in the admin
> interface for a model which has an ImageField, I get an import error in
> admin_list.py on ``from django.parts.media.photos import
> get_thumbnail_url``. 0.91 has a parts.media.photos module, but
> magic-removal doesn't. I dropped in the ``parts`` directory from 0.91
> into my magic-removal branch and it seems to work fine without
> modification. Is this something that's going to be added back in as
> is (so that I can just move forward with my dropped in code)?
> I'm reworking a simple store with the magic removal branch
> and running into a bit of a snag. When I create a record in the admin
> interface for a model which has an ImageField, I get an import error in
> admin_list.py on ``from django.parts.media.photos import
> get_thumbnail_url``. 0.91 has a parts.media.photos module, but
> magic-removal doesn't. I dropped in the ``parts`` directory from 0.91
> into my magic-removal branch and it seems to work fine without
> modification. Is this something that's going to be added back in as
> is (so that I can just move forward with my dropped in code)?
Thanks for pointing this out. django.parts appears to have been
removed while I was on vacation. I'm investigating.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
Joseph Kocherhans
Mar 15, 2006, 10:15:58 PM3/15/06
to django-d...@googlegroups.com
On 3/15/06, Adrian Holovaty <holo...@gmail.com> wrote:
>
> Thanks for pointing this out. django.parts appears to have been
> removed while I was on vacation. I'm investigating.
>
> Thanks for pointing this out. django.parts appears to have been
> removed while I was on vacation. I'm investigating.
I removed django.parts after moving it's contents to
django.contrib.auth. However, django.parts.media was removed long
before that.
Joseph
Joseph Kocherhans
Mar 15, 2006, 10:20:51 PM3/15/06
to django-d...@googlegroups.com
Rudolph
Apr 2, 2006, 5:44:51 PM4/2/06
to Django developers
Will django.parts.media get dropped in again soon? I would like it if
the ImageField fully works again.
the ImageField fully works again.
Cheers,
Rudolph
Reply all
Reply to author
Forward
0 new messages