On 01 Oct 2014, at 14:33, Collin Anderson wrote:
> In hindsight I regret not having pushed harder for integration of staticfiles
> into core instead, lots of confusion could have been prevented, IMO.
>
> Is it too late to move to core?
Good question, if we’d left the public API in django.con
On Thu, Oct 2, 2014 at 3:04 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> I've been thinking about providing built-in support for Jinja2 in Django.
> I found that supporting pluggable template engines, like Django does for
> databases, caches, etc. would be the mos
Hello,
I've been thinking about providing built-in support for Jinja2 in Django. I
found that supporting pluggable template engines, like Django does for
databases, caches, etc. would be the most elegant solution. The best summary I
have at this time is on the crowdfunding campaign's page:
htt
>
> In hindsight I regret not having pushed harder for integration of
> staticfiles into core instead, lots of confusion could have been prevented,
> IMO.
>
Is it too late to move to core?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Cont
2014-10-01 9:21 GMT+02:00 Florian Apolloner :
> Imo, this is mainly useful to rollback if no error occurred! The other use
> of this feature might work but is quite dangerous imo.
>
If you really know what you are doing, it might be possible to use it
safely while taking advantage of a database's
On Wednesday, October 1, 2014 6:58:28 AM UTC+2, Anssi Kääriäinen wrote:
>
> Django does allow to continue the transaction if you explicitly choose
> to do so. After handling the error, you must use set_rollback[1]. This
> is useful for those rare cases where you want to continue after error in
>
On Wednesday, October 1, 2014 6:58:28 AM UTC+2, Anssi Kääriäinen wrote:
>
> Django does allow to continue the transaction if you explicitly choose
> to do so. After handling the error, you must use set_rollback[1]. This
> is useful for those rare cases where you want to continue after error in
>
On 29 Sep 2014, at 22:46, Jeremy Dunck wrote:
> Right now, I think that static/media handling is fairly confused in the
> documentation, and a bit confused in the code itself.
Please make sure to open tickets about this, I've long lost the ability to see
at this code from the beginners perspe
