Re: Multiple template engines for Django - week 12

If I'm understanding your post correctly, any potential performance improvement that a special cased select_template would have would likely be negated by caching. Have you observed, or do you expect to see any significant performance hits to the test suite, which doesn't cache as intensely as live

Re: Migrations in Django 1.7 make unit testing models harder

At work we use a --no-migrate flag on our test runner. It's helpful when 1) we're developing a new app but the models aren't nailed down yet, and 2) it speeds up the test suite time significantly. The --keepdb option is sufficient for scenario 2, but doesn't do much for scenario 1. Admittedly t

Formalizing template loader and debug api's

Hi all, I've been working on #15053, which enables Django template loaders to extend templates of the same name recursively. The most common use-case for this is extending the admin templates without needing to copy the application templates into a project. To illustrate the new algorithm, here

Re: Multiple template engines for Django - week 12

I agree about the select_template() change as well. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsu

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky wrote: > > Hi all, > > When running a small, low traffic site on slow cloud servers (eg > DigitalOcean), it'd be useful to be able to cache pages, not because the > site might be taken down from too many request, but to improve > responsiveness.

Fellow Report - December 26, 2014

I spent a good chunk of time this week reviewing two of the major features for 1.8 (multiple template engines and _meta refactor), as well as fixing and researching release blockers (more on that in the "status of 1.8 release blockers" thread). With two weeks left until the scheduled alpha, I

Re: "stable API" misconception giving BaseManager and Manager as examples

In fact, there's an open ticket to create a reference of the public manager methods. There's a detailed comment from Loic about some ideas for that: https://code.djangoproject.com/ticket/20768 I think our existing policy about stable APIs being the ones that are documented works pretty well. I

Re: Multiple template engines for Django - week 12

I agree with your expected behavior for select_template() and the conclusions you drew. On Saturday, December 27, 2014 5:59:37 PM UTC-5, Aymeric Augustin wrote: > > Hello, > > My twelfth update is online: > https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 > > It comes with

"stable API" misconception giving BaseManager and Manager as examples

Hello, In Djnago 1.7 Manager class extends BaseManager (actually, it extends its proxy, created using from_queryset). BaseManager is not mentioned in official documentation, so it is not part of official ("stable") api, right? "All the public APIs (everything in this documentation) " (from here

Multiple template engines for Django - week 12

Hello, My twelfth update is online: https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 It comes with a question — should I drop `select_template` from the backend API? I think I should. Follow the link above for details. Looking forward to your feedback, -- Aymeric. > On

Re: status of 1.8 release blockers

Here is the second update with three weeks to go until alpha: #23861 - Fields referenced in migrations cannot be (re)moved, even if migrations have been squashed #23891

Re: Migrations in Django 1.7 make unit testing models harder

In pull request 3791 , I started working on the code removals for Django 1.9 to better understand how the database/migrations code will look and what APIs we still need to deprecate. The good news is that we can keep support for apps without migration

Optional separation of the concepts of how long server caches content and how long it tells client to cache it

Hi all, When running a small, low traffic site on slow cloud servers (eg DigitalOcean), it'd be useful to be able to cache pages, not because the site might be taken down from too many request, but to improve responsiveness. A non-trivial page that might take a few hundredth of a second to ser