Re: newforms and encoding problems

is is the one I display in the template. 2 forms, yeah, that sucks, but I have not found any other way. Sorry, I don't speak a good english, just say it if you have not understood. Regards Baptiste. On 7 mar, 18:49, "Nuno Mariz" <[EMAIL PROTECTED]> wrote: > Hi, >

Re: newforms and encoding problems

Ah, data is request.POST, of course, and I create the form like that myForm(data). On 7 mar, 23:04, "Baptiste" <[EMAIL PROTECTED]> wrote: > I had the same problem (ticket 3630). > I solved that by passing my mySQL fields in UTF8, then by doing : > >

{% blocktrans %} doesn't allow inner block tags...

ample) : {% blocktrans with article.pub_date|date:"l d" as day and article.pub_date|date:"F" as month [...] %} Posted the {{ day }} {{ month }} (link : See the articles for the {{ day }} {{ month }} {% endblocktrans %} So there is my

Re: {% blocktrans %} doesn't allow inner block tags...

Thanks for your quick answer. Malcolm Tredinnick a écrit : > On Fri, 2007-03-09 at 15:29 +0000, Baptiste wrote: > > ... and that is really boring ! I don't understand why does this > > limitation exist. Sometimes, you need a little {% if %} in it... but > > you can&

Add a salt to the newforms fields names

paring it with fields names to make a new dictionary with correct names and values, what would allow the user to do again form['name']. It may sound a little bit confuse - it is. So please tell me what you think about that, and how you would do it. Regards Baptiste. --~--~-~--~-

Re: Add a salt to the newforms fields names

key in the data dictionary. On Mar 22, 10:06 pm, "Baptiste" <[EMAIL PROTECTED]> wrote: > Hello all, > > (Please apologize my bad English, don't mind about it and try to > understand... I'll do my best !) > > First, have a quick look on the spammer main

Re: Add a salt to the newforms fields names

remy, this approach is lesser efficient ;-) Regards Baptiste On Mar 22, 11:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-03-22 at 21:06 +, Baptiste wrote: > > Hello all, > > > (Please apologize my bad English, don't mind about it and t

Re: Add a salt to the newforms fields names

On Mar 23, 8:08 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Fri, 2007-03-23 at 06:48 +, Baptiste wrote: > > That feature would be unable by default, and the user could use it > > just for forms which didn't need to be autocompleted, eg. a comment >

Re: {% with %} tag

For me, yes, but I miss the "and" : {% with article.name as name and article.title as title %} But it is an useful tag. On Mar 24, 7:42 am, "SmileyChris" <[EMAIL PROTECTED]> wrote: > For a while I've been thinking that it would be nice to have a tag so > you could re-use an expression in a templa

Re: {% with %} tag

ECTED]> wrote: > On Mar 25, 8:00 am, "Aidas Bendoraitis" <[EMAIL PROTECTED]> > wrote: > > > Wouldn't it be more convenient not to have the closing {% endwith %}? > > Perhaps, but rather than "dirtying" up the context, this keeps the > varia

Re: {% with %} tag

It has been commited ; that is cool, but without any "and" or "," that is not cool. Like in my example, it is idiot to have to open a tag by variable... no? On Mar 27, 2:04 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Mon, 2007-03-26 at 17:06 -0500, Jacob Kaplan-Moss wrote: > > On 3/26/

Re: The with template tag with "and" operator

Of course I am +1 on this because I also wanted it, I think it would be really useful... repeating {% with %}{% endwith %} ten times if needed ten times really does not respect DRY principle... On 2 avr, 16:53, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi guys! > > I want to be able to use

Re: Edit inline in newforms-admin branch (ATTN: Joseph Kocherans)

that ;-) Great work anyway, go on. Baptiste. On 7 avr, 07:13, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > On 4/6/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > > I've documented a bunch of the changes here: > > http://code.djangoproject

Re: Edit inline in newforms-admin branch (ATTN: Joseph Kocherans)

I have found from where was the error coming. More details on http://code.djangoproject.com/ticket/3973. Thanks Baptiste On 8 avr, 19:07, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > On 4/7/07, Baptiste <[EMAIL PROTECTED]> wrote: > > > I don't know how

Newforms-admin : a better hook for admin pages (Adrian Holovaty)

27;s firepower. This change is backward compatible and wouldn't introduce any problem for the sites that work now. Except if I have forgotten something ;-) I may not explain very well since my English sucks, so if you want more precisions, just ask them. Regards Baptiste --~--~-~--~

Re: editable attribute limitation

Like I said, I wanted to do that this aftertoon and then I saw your patch... which fits exactly to what I needed. It is imo an useful change - and not only because I would need it - that should be integrated in the core. On 10 avr, 14:41, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Done: > >

Status of newforms-admin's admin (bad widgets, ...)

, ...). I know it is WIP, but I would like to know what is the status of the newforms-admin's admin. What things are still to do, when will they be done, can we help to make it working... ? Thanks Baptiste --~--~-~--~~~---~--~~ You received this message because yo

Re: #3527 - better debug traceback with code executing...

I am +10 on this patch. If this debugger was disabled if DEBUG is False, that wouldn't solve the problem ? I mean, are they people who use DEBUG mode in production ? On 14 avr, 15:38, Marek Kubica <[EMAIL PROTECTED]> wrote: > Hi, > > I'm bringing this question up again, as no decision has been ma

Re: #3527 - better debug traceback with code executing...

Oh, and maybe we can check if request.user.is_authenticated() and request.user.is_staff() before enabling it ? On 15 avr, 19:58, "Baptiste" <[EMAIL PROTECTED]> wrote: > I am +10 on this patch. > If this debugger was disabled if DEBUG is False, that wouldn't solve >

Re: #3527 - better debug traceback with code executing...

to be able to debug the code paths that run for all > requests, not just authenticated/staff/superuser? > > On 4/15/07, SmileyChris <[EMAIL PROTECTED]> wrote: > > > > > Or even require a superuser? > > > On Apr 16, 6:00 am, "Baptiste" <[EMAIL PRO

Re: #3527 - better debug traceback with code executing...

w if there is any > way to easily check that? I suppose you might want a specific setting as > well to enable/disable it even for that limited environment, if there's a > chance people would not want it active, or if there's a chance people are > using the development serve

Re: editable attribute limitation

The current admin (and the newforms one) doesn't allow enough customization to make it user-friendly. That may be a feature, but that is really boring to need to write its own admin because of the limitations of the existing one. In my case, I just have a ForeignKey to an User. At the first save,

Re: #3527 - better debug traceback with code executing...

debug text input, but whatever you type, if you have not entered something like 'e1desFrde2D', the output is 'Please enter the debug password'. On 16 avr, 14:10, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On 4/16/07, Baptiste <[EMAIL PROTECTED]> wrot

values() through ForeignKey

move the select_related() if values() managed the relationship between models... Regards, Baptiste --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send ema

Re: Unicode branch - last call for comments(?)

Well if I have understood what you say, it is exactly what is explained here .. Anyway, that is a great news. But I have changed all my code and I have just read that you wasn't going to update newforms-admin

A way to filter related fields in new-admin (#3987)

editor.objects.filter(group__in=request.user.groups.all()) What do you think about this feature ? Regards, Baptiste [1]: http://code.djangoproject.com/attachment/ticket/3987/diff-dynamic.3.diff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: Proposal: customtags, a higher-level API for template tags

I have tried to read this patch, but its presentation is really awful.. But even if I have stopped to read, that seems to be a very big work! I would like to see it from Trac or I don't know what but from something that makes him legible ;-) Anyway, congratulations Baptiste On 12 juil,

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

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

his fix (and use a workaround or a private fork until then) * Find a good argument as to why this particular fix should be backported ("all the tests pass" is a good start but it's not enough). I hope that makes sense. Thanks, Baptiste On 12/01/2014 03:49 PM, Yann Fouillat wrot

Re: ANN: Django website redesign launched

with my by email or on IRC (#django-websites on Freenode). Have a nice day, Baptiste On 12/17/2014 11:28 AM, Jorge C. Leitão wrote: Dear Django community, I would like to congratulate you very much for this. I'm very pleased to see that the work in Django is much better presented to the

Re: ANN: Django website redesign launched

sive community here, so toxic and insulting behavior is not simply ignored. In this instance, I think Daniele's response was appropriate and I stand by it too. I hope that answers your question. Cheers, Baptiste PS: The mailing list is publicly viewable at https://groups.google.com/fo

Renaming the postgresql_psycopg2 backend

e was more than one postgres backend. Could we at least make it an alias of a more simply named "postgresql" backend? Thanks, Baptiste -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" g

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

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 las

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/t

Re: version number in Django documentation URLs

project.com/en/stable/internals/release-process/ works, but I'm not sure that it's documented anywhere. Baptiste -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving

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

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

n get_queryset() to return instances of Book, not of Publisher. I'm not sure why I didn't backport that commit to the 1.5 branch when I made it. I'll do so now and the fix should appear online soon. Thanks for catching this. Baptiste On 01/20/2014 10:24 PM, Leonardo Borges Ave

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

Re: Wrong translation in Brazillian portuguese

e 1.7 translations is still open so if you fix the translation on transifex, it should make its way into the final 1.7 release. Thanks, Baptiste On 04/07/2014 04:45 PM, Bruno Ribeiro da Silva wrote: Hi everyone, I found a wrong translation in Brazillian portuguese that affects django 1.7 and

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" <mailto:ja...@jacobian.org>> wrote: +1. Aymeric, I can't tha

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

e cover all supported HTTP methods. Thanks, Baptiste On 11/21/2016 08:11 PM, Markus Holtermann wrote: Hi all, As it turned out [1], due to their complexity, using class-based generic views for security-sensitive functionality can result in unintended behavior. Essentially, the reset token was on

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 contribu