On 2 July 2010 05:44, hcarvalhoalves wrote:
> Besides that, I don't see the need for anything to integrate inside a
> single "clean" command. It's not like the management commands provided
> by Django are hooks, you can and should be making yours for each
> specific need.
My intention was to make
On 2 July 2010 05:44, hcarvalhoalves wrote:
> Besides that, I don't see the need for anything to integrate inside a
> single "clean" command. It's not like the management commands provided
> by Django are hooks, you can and should be making yours for each
> specific need.
I agree with this.
Ma
applications provide
>> their own management command for this (cleanup_thumbnail,
>> cleanup_registrations...) - IMO there should be a better way to only
>> need one cronjob that can do all the work.
>>
>> My suggestion is to add a cleanup signal that is called in dj
Until yet most applications provide
> their own management command for this (cleanup_thumbnail,
> cleanup_registrations...) - IMO there should be a better way to only
> need one cronjob that can do all the work.
>
> My suggestion is to add a cleanup signal that is called in djang
ay to only
need one cronjob that can do all the work.
My suggestion is to add a cleanup signal that is called in django's
cleanup management command. This would make custom cleanup code easier
to use.
What are your opinions about a cleanup signal?
Maybe it would even make sense to have a mo
