Re: Good practices for production settings

Hi, I like the patch and I think it's a welcome addition to the documentation. I spotted one minor spelling mistake: "an hostile environment" should be "a hostile environment" (L5 of checklist.txt). Good work, Cheers, Baptiste -- You received this message because you are subscribed to the G

Re: I have an issue which is fixed in master but not in stable/1.7.x

Hi Yann, The policy we use for backporting is described there: https://docs.djangoproject.com/en/1.7/internals/release-process/#supported-versions > The rule of thumb is that fixes will be backported to the last major release for bugs that would have prevented a release in the first place (r

Re: ANN: Django website redesign launched

Hi Jorge, First off, thank you for your feedback, it's very much appreciated. Regarding your question about Trac, the differences in UI that you list are definitely not intended. Ola Sitarska and me did some work to try and adapt the new design to Trac but it's proven to be difficult. Coul

Re: ANN: Django website redesign launched

Hi Torsten, As far as I know, it's not often that people get kicked out of this mailing list (note that Christian was kicked out, not banned, so he can join back if he'd like) so I'm not sure what's "customary". However, we strive to create a friendly and inclusive community here, so toxic a

Renaming the postgresql_psycopg2 backend

Hi everyone, After starting a new project recently and failing three times to type the name of the postgres backend correctly, I was wondering if there's really any value in keeping around this strange name. From what I understand, it's a historical artifact from a time when there was more t

Re: Renaming the postgresql_psycopg2 backend

resql" in their DATABASE_URL scheme. Maybe we could support all three? :) On Wednesday, July 15, 2015 at 9:17:30 AM UTC-4, Baptiste Mispelon wrote: Hi everyone, After starting a new project recently and failing three times to type the name of the postgres backend correctly

Re: User notification by email of account detail changes

For your djangoproject account, you can change your display name and email there: https://www.djangoproject.com/accounts/edit/. Baptiste On 11/15/2015 02:46 PM, Daniele Procida wrote: I've been discussing with Florian on IRC a suggestion for improved account security. On many sites, you wi

Re: User notification by email of account detail changes

I don't think it's documented anywhere. I found the link by going to https://www.djangoproject.com/~bmispelon/ (replace by your username) and there was a link to it in the right side bar. Baptiste On 11/15/2015 02:57 PM, Daniele Procida wrote: On Sun, Nov 15, 2015, Baptist

Re: Can you remove a model's last field of SQLite3 in Django 1.8?

Hi, I believe the issue you're describing has already been reported: https://code.djangoproject.com/ticket/24424 This ticket is still open and there is a long discussion on it (30 comments). Baptiste On 11/29/2015 06:15 PM, KwangYoun Jung wrote: Can you remove a model's last field of SQ

Re: Django documentation: Using mixins with class-based views

Hi, I believe you're right, this code is incorrect. Would you mind opening a ticket for this on https://code.djangoproject.com/newticket ? Thanks, Baptiste On 06/23/2013 05:29 PM, Michal Slįdek wrote: Hello! I tried to use following examples: https://docs.djangoproject.com/en/dev/topics/cla

Re: version number in Django documentation URLs

On 08/30/2013 12:10 AM, Daniele Procida wrote: RTFD.org can use "latest" for the version number in docs - why don't we? It would be nice to be able to refer for example to . Daniele https://docs.djangoproject.com/en/stable/i

Re: Why not use @classmethod decorator consitently in django/utils/functional.py?

Hi Adam, Django 1.6 only supports Python 2.6 and older [1] and Django 1.7 will support Python 2.7 onwards [2]. [1] https://docs.djangoproject.com/en/1.6/releases/1.6/#python-compatibility [2] https://docs.djangoproject.com/en/dev/releases/1.7/#python-compatibility Cheers, Baptiste On 11/20/2

Re: Is it a mistake on docs for django 1.5?

Hi, It's actually a bit trickier than that (making the example work required some serious contortions and I wouldn't recommend it in practice). As noted in one of the comments that I added, we can't rely on the default implementation of get_object() because we've overridden get_queryset() to r

Re: [GSoC 2014 proposal]. Improving admin translation and formalizing Meta objects.

Hi, Regarding the translation issues, there's a lengthy discussion on https://code.djangoproject.com/ticket/11688 which you might find interesting. -- Baptiste On 03/13/2014 10:00 AM, Алексей Сидаш wrote: How so? Can you provide a few examples -- I know that numbering can be a prob

Re: Wrong translation in Brazillian portuguese

Hi, Django's translations are managed on a separate website called transifex. You can find more information on the translation process on our documentation at https://docs.djangoproject.com/en/1.6/internals/contributing/localizing/#translations. As far as I know, the window for the 1.7 transl

Re: error in "makemessages" command on latest django version (1.8dev)

Hi, No need for apologies: your message is completely appropriate for this mailing list. I can reproduce the issue you're describing and it does look like a bug. It seems to have been introduced by this commit: https://github.com/django/django/commit/0707b824fe77e08ca8b75fcc3738ada694f2a3a6.

Re: Updating the organization of the Django Project

Another big +1 from me. Thanks for yet another awesome refactor, Baptiste On 07/27/2014 03:52 PM, Honza Král wrote: +1 Thanks for pushing for this! On Jul 25, 2014 5:22 PM, "Jacob Kaplan-Moss" > wrote: +1. Aymeric, I can't thank you enough for taking t

Re: Consider reverting or adding guidelines on how to use class based views for security sensitive features

Hi Markus, Thanks for your clear description and for bringing this up for discussion. I don't agree with your conclusions though. 1) Keeping around two implementations of auth views seems counter-productive to me in terms of security because it effectively doubles the potential for bugs or s

Re: Unable to run tests with git bisect run

Hi, You need to put the `PYTHONPATH=...` thing at the beginning of the line, like so: PYTHONPATH=..:$PYTHONPATH git bisect run ./runtests.py flattened-prefetch Baptiste On 12/01/2016 04:46 PM, Vimarsh Chaturvedi wrote: Hey folks, This is the first time I'm trying to contribute to Djang