> So my question, and this is something I've been thinking about a lot
> of the proposals lately is: why should this be in Django itself.
I couldn't agree with your sentiment more, in the whole. In fact, to
me, until now all of the proposals aside from Simon's seem better
outside of Django than
On Mon, Sep 28, 2009 at 6:26 PM, maxi wrote:
>
> Hi,
> I'm working on implementation of firebird backend for django [1]
> I've an issue related of icontains filter option. Firebird uses
> CONTAINING sql clause for this, which is case insesitive.
>
> The problem is that the output generated (where
On Tue, Sep 29, 2009 at 9:29 AM, Alex Gaynor wrote:
>
> On Mon, Sep 28, 2009 at 9:24 PM, SeanOC wrote:
>>
>> Hello All,
>>
>> During the Djangocon sprints I started to work on a patch which would
>> add a nicer interface for dealing with raw SQL queries. While there I
>> talked to RKM about whe
On Tue, Sep 29, 2009 at 12:44 AM, Johannes Dollinger
wrote:
>
>>> Variable and FilterExpression will be deprecated as they require the
>>> caller to know the length of the expression in advance.
>>
>> I'm not sure I follow this assertion. I have no problem believing
>> FilterExpression can be mad
Hi,
I'm working on implementation of firebird backend for django [1]
I've an issue related of icontains filter option. Firebird uses
CONTAINING sql clause for this, which is case insesitive.
The problem is that the output generated (where clause) is wrong.
It return:
WHERE "TABLE"."FIELD
On Mon, Sep 28, 2009 at 9:24 PM, SeanOC wrote:
>
> Hello All,
>
> During the Djangocon sprints I started to work on a patch which would
> add a nicer interface for dealing with raw SQL queries. While there I
> talked to RKM about where it should fit into the ORM API and where in
> the code base
Hello All,
During the Djangocon sprints I started to work on a patch which would
add a nicer interface for dealing with raw SQL queries. While there I
talked to RKM about where it should fit into the ORM API and where in
the code base should live. I've finally gotten around to finishing
the cod
Hi all,
Today I filed #11957 [1], and because it is questioning an earlier
bugfix, I was asked to bring up the issue for discussion here.
Under the dev server, if an error occurs while importing an app's
admin.py, the error will show up on the first request, and then
disappear. On all subsequent
On Sep 28, 6:57 pm, Rob Hudson wrote:
> For lack of knowing about anything better, I keep falling back to
> Werkzeug's HTMLBuilder class[1]. Pulled out and stripped of comments,
> it weighs in at 77 lines of code...
That's not so bad. I was worried about pulling in a large dependency,
but 77 li
On Mon, Sep 28, 2009 at 6:38 AM, Russell Keith-Magee
wrote:
> By way of greasing the wheels towards trunk: if the outcome of this
> mailing list thread was a wiki page that digested all the ideas,
> concerns and issues into a single page, it will make the final
> approval process much easier. Luk
On Sep 26, 7:33 pm, Simon Willison wrote:
> 1. a {% selfclose %} template tag:
>
>
>
> {% selfclose %} outputs either blank or " /" depending on the doctype.
I've added an experimental {% slash %} tag to django-html to address
the reusable XHTML/HTML templates problem. It's actually not as
On Sep 28, 5:20 pm, Max Battcher wrote:
> I really don't see what the fuss here is about. If we are worried about
> forwards-compatibility, HTML 5 takes care of it. If we are worried about
> better backwards-compatibility with HTML 4, everyone else is saying that
> the future is now and the focus
On Sat, Sep 26, 2009 at 11:33 AM, Simon Willison
wrote:
> I don't think it would involve form widgets being rendered with
> templates simply because of the performance overhead - even with the
> template caching improvements it's still a lot of work just to output
> an input tag. It might involve
>> Variable and FilterExpression will be deprecated as they require the
>> caller to know the length of the expression in advance.
>
> I'm not sure I follow this assertion. I have no problem believing
> FilterExpression can be made cleaner, but Variable takes an expression
> like 'article.section'
Simon Willison wrote:
> On Sep 26, 10:17 am, Max Battcher wrote:
>> Furthermore, support for XHTML "5" (which is indeed a part of the HTML 5
>> standard) shows that XHTML 1's principles are still around and still
>> respected. Django's XHTML output can't be "out of date" if XHTML 5 is
>> consider
On Fri, Aug 28, 2009 at 9:41 PM, Johannes Dollinger
wrote:
>
> The proposal and motivation are essentially the same as in the last
> thread [1] and the ticket description [2]. I put it on the 1.2 feature
> list.
> I tried to split my patch into smaller, more readable commits here:
> http://gith
On Sun, Sep 27, 2009 at 1:34 AM, Rob Hudson wrote:
>
> On Sat, Sep 26, 2009 at 2:13 AM, Simon Willison
> wrote:
>> Yes - I looked briefly at how much work was involved in doing this and
>> it's not insubstantial, which is why I opted for string replacement
>> just to demonstrate the API. I'm co
Hi
I was hoping someone could take a look at this bug at some point, and
make a decision about the best course of action to take.
http://code.djangoproject.com/ticket/11877
Cheers
Tom
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Hi,
is there a particular reason why Lighttpd documentation advices user
to create a separate script (for example, an init script) to create
the socket with manage.py? Why not let the Lighttpd take care of
spawning processes as needed?
If no-one is against it, I could file a ticket about this an
This is unrelated Andreas. HTML5 has the exact same syntax as HTML4,
just new tags.
This thread is about syntax.
By the way, neither html4 nor xhtml are deprecated. HTML5 is still not
"officially released".
J. Leclanche / Adys
On Mon, Sep 28, 2009 at 12:12 PM, Andreas wrote:
>
> html4 is dere
html4 is derecated.
xhtml is deprecated.
With google chrome frame out there theres absolutly no reason to not
begin with html5 already.
The longer we wait, the longer it will take before html5 becomes "the
it".
On Sep 27, 1:46 pm, Simon Willison wrote:
> On Sep 27, 10:49 am, veena wrote:
>
21 matches
Mail list logo
