On 10 tammi, 09:27, Wim Feijen wrote:
> Hi,
>
> Ticket 19326 has been marked as ready for check-in for some time. Can
> some-one have a look at it?
>
> https://code.djangoproject.com/ticket/19326
>
> Thanks,
>
> Wim
I did some more polish to the patch. There is now also .last() method,
and if th
On Thursday 03 January 2013, Jani Tiainen wrote:
> 31.12.2012 14:18, Shai Berger kirjoitti:
> > On Sunday 30 December 2012 21:54:52 Anssi Kääriäinen wrote:
> >> Seems like you are correct [...]. Please open a bug.
> >
> > For anyone interested that isn't on the new-bugs list, it's
> > https://code
On Thursday 17 January 2013, Anssi Kääriäinen wrote:
> On 17 tammi, 15:50, Shai Berger wrote:
> > Besides these two, I would like to continue the discussion on PR #402[3];
> > it suggests adding a flag to Oracle's DATABASE_OPTIONS, to control how
> > it returns explicit expressions from raw sql ("
Yes, it's a wart from HTML. Even if we were inclined to alter the name to
make it idiomatic Python (which isn't necessarily a good idea in this case
-- the HTML naming convention makes sense), it would be impractical to
change it at this point in Django's lifecycle - there is so much code
depending
It's probably just a wart from HTML. The XyzInput widgets correspond more
or less to tags, but the Textarea widget corresponds to
. There's only two tags like this that are HTML form elements but
are not tags, the other being , whose widget "Select"
similarly has one capital letter and no "Input"
Hi guys,
I was just wondering, and maybe my English language skills are
insufficient.
Django defines several widgets, like:
TextInput
PasswordInput
HiddenInput
DateInput
DateTimeInput
TimeInput
Textarea
Why isn't Textarea CamelCased: TextArea, like the other widgets? It seems
inconsistent. Bu
