On Sat, May 18, 2013 at 11:38 PM, Ramiro Morales wrote:
> Hi all,
>
> This is a proposal for fixing this small and old issue
> (https://code.djangoproject.com/ticket/9321):
>
> [...]
>
> Django 1.7:
> Simply stop forcing the hard-coded sentence. If users want to have it
> set or added to their hel
On 19 mai 2013, at 22:37, Erik Romijn wrote:
> The reason I ask, is that I'd like to volunteer for maintaining
> django-localflavor-nl.
Considering your track record of contributions to Django, that's a no brainer.
You now have commit access to django-localflavor-nl, congratulations!
--
Ayme
Hello all,
With the separation of django-localflavor-* from Django core, one of the
discussed advantages is that each localflavor package can have its own
maintainer(s). Have we established a process for signing up for this? I
couldn't find anything in docs or discussions.
The reason I ask, is
Le dimanche 19 mai 2013 09:40:25 UTC+2, Florian Apolloner a écrit :
>
> Hi,
>
> I don't think that the fix of #20246 [0] is correct. You started using
> \xa0 while Wikipedia clearly suggests that we should use a narrow space
> instead of a full-space (probably U+202F). This is something we learne
I agree with Anssi, repr should stay as-is. I do a lot of shell/pdb work
and I can't recall ever encountering a problem with "unsafe" repr. I think
many people would find it annoying if suddenly repr would tell you no more
than the pk of the object.
Karen
--
You received this message because you
Hi,
In my quest to solve Oracle bugs, I found the function datetime_cast_sql() in
the Oracle backend. It causes a problem these days, because it gets in the way
of querying a date as string (mydate__startswith='2005'). It is a function
that is defined as a no-op in the base backend, and overrid
18 maj 2013 18:48, "Anssi Kääriäinen" napisał(a):
> There was very similar discussion recently (maybe in some ticket, I
> don't remember where) about QuerySet.__repr__(). IIRC the conclusion
> was that executing SELECT queries as part of __repr__() is OK.
I've been bitten by that one already. At
On 19 mai 2013, at 07:12, Shai Berger wrote:
> Florian, Aymeric, or any Django/Oracle user in Kenya: How did you overcome
> this?
Install pytz.
I recently skipped these tests on MySQL when pytz wasn't installed, I shall do
the same for Oracle.
--
Aymeric.
--
You received this message beca
Hi Shai
On Sunday, May 19, 2013 7:12:12 AM UTC+2, Shai Berger wrote:
>
> Florian, Aymeric, or any Django/Oracle user in Kenya: How did you overcome
> this?
>
I have no idea, I just bang my head against the CI till it works or falls
completely apart (well not really, but you get the gist ;)).
Hi,
I don't think that the fix of #20246 [0] is correct. You started using \xa0
while Wikipedia clearly suggests that we should use a narrow space instead
of a full-space (probably U+202F). This is something we learned during our
physics courses too, so it's in line with what science department
Currently second approach with update is implemented.
W dniu niedziela, 19 maja 2013 09:34:18 UTC+2 użytkownik Karol Sikora
napisał:
>
> Hi,
>
> At djangocon sprints I implemented update_or_create method on QuerySet,
> Patch is ready to merge on: https://github.com/django/django/pull/1132
> Bu
Hi,
At djangocon sprints I implemented update_or_create method on QuerySet,
Patch is ready to merge on: https://github.com/django/django/pull/1132
But after some discussion with folks here and on bugtracker, we need design
decision.
First approach is to following get_or_create approach, passing
12 matches
Mail list logo
