Re: Trac components cleanup

Hi all, Now that 1.3 has been released (yay!), I'm reviving this thread to see if we can make Trac a little more efficient on our way to 1.4. I'll try to summarise what's been suggested so far in regard to improving and clarifying the "Component" field: * The "Contrib apps" component would be

Re: Proposal: Add current_app to request and pass it to template loaders.

Now that 1.3 is out, does any core dev have an opinion, feedback or suggestions on this? I've solved my immediate need with two template loaders (subclasses of the app_directories loader) that use thread locals. One prefixes the requested template name with the app name and the other prefixes it

Re: Complains about FileField not deleting files in 1.3.

On Sun, Mar 27, 2011 at 5:42 AM, -RAX- wrote: > I am referring to this: > http://docs.djangoproject.com/en/dev/releases/1.3/#filefield-no-longer-deletes-files > Instead of preventing the data loss from happening a very usefull > feature has been removed. I'm sorry this

Re: Complains about FileField not deleting files in 1.3.

On 03/27/2011 06:42 AM, -RAX- wrote: > I am referring to this: > http://docs.djangoproject.com/en/dev/releases/1.3/#filefield-no-longer-deletes-files > Instead of preventing the data loss from happening a very usefull > feature has been removed. Well, it does also prevent the data loss from

Complains about FileField not deleting files in 1.3.

I am referring to this: http://docs.djangoproject.com/en/dev/releases/1.3/#filefield-no-longer-deletes-files Instead of preventing the data loss from happening a very usefull feature has been removed. Why not simply letting the developer decide when to enable or disable it with a constructor