Re: FR: Setting for CSRF Header (pull-request included)

The main problem I see with this approach is that it would no longer be straightforward for 3rd party code to access these settings. You'd need something akin to get_user_model() to retrieve the currently installed CSRF middleware so you could access its settings. Take a look here for examples

Re: [1.7-RC] Using coverage with migrated app slow down test-suite execution by 6 times.

Hi Stan, It seems like there's two separate issues here: - One of the migrations takes 30s to run. What is the migrations that's so slow, and what database are you running it on? You might be able to squash the migrations to increase performance (a fully squashed set of migrations should be no w

Re: Per-country URLs

2014-07-08 18:22 GMT+02:00 Max Arnold : I had quite similar need some time ago: > https://code.djangoproject.com/ticket/20125 > > My approach was to add full locale in the form LL-CC (language-country) to > each url > and set per-request locale based on this prefix (probably with some > mapping).

Re: Per-country URLs

On Tue, Jul 08, 2014 at 04:42:14PM +0200, Aymeric Augustin wrote: > Hello, > > Since Django 1.4, it's possible to localize URL patterns with > i18n_patterns. I have a slightly different use case. I need URLs in the > form /// in order to implement country-specific behavior > (eg. taxes, local regu

Per-country URLs

Hello, Since Django 1.4, it's possible to localize URL patterns with i18n_patterns. I have a slightly different use case. I need URLs in the form /// in order to implement country-specific behavior (eg. taxes, local regulations, etc.). The hard part is to get URL reversing to work correctly witho

[1.7-RC] Using coverage with migrated app slow down test-suite execution by 6 times.

Hi devs, Since Django-1.7-RC, apps containing models that inherit from "migrated" must be "migrated". My project (*fab4*) contains 7 apps and only 1 (*parametrage*) has been migrated (as explained in the doc )