If someone has some spare time. Take a look at this ticket:
https://code.djangoproject.com/ticket/20434
The implementation is finished and consists of 4 patches. See the ticket
for more information. Thanks!
--
You received this message because you are subscribed to the Google Groups
"Django de
No worries, that's always been one of the most awkward gotchas in python.
It's made doubly so by the fact that iterating over a string gives more
strings.
On Jun 5, 2013 4:29 PM, "Cal Leeming [Simplicity Media Ltd]" <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hi Noah,
>
> Sorry yes I remember
Hi Noah,
Sorry yes I remember discussing this last time now, it wasn't until I hit
send that I remembered about 5 seconds after.
I think I'm having a bit of a stupid day - my apologies.
Cal
On Wed, Jun 5, 2013 at 8:57 PM, Noah Kantrowitz wrote:
>
> On Jun 5, 2013, at 12:56 PM, Cal Leeming [Si
On Jun 5, 2013, at 12:56 PM, Cal Leeming [Simplicity Media Ltd] wrote:
> Hello,
>
> The following;
> class Meta:
> ordering = ('hostname')
>
> Results in;
> amber.reseller: "ordering" refers to "h", a field that doesn't exist.
> amber.reseller: "ordering" refers to "o", a field that
Okay, please ignore the below, it was because I used a tuple rather than a
list in my test.
>>> lol = ('hostname')
>>> print lol[0]
h
Cal
On Wed, Jun 5, 2013 at 8:56 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hello,
>
> The following;
> class Met
Hello,
The following;
class Meta:
ordering = ('hostname')
Results in;
amber.reseller: "ordering" refers to "h", a field that doesn't exist.
amber.reseller: "ordering" refers to "o", a field that doesn't exist.
amber.reseller: "ordering" refers to "s", a field that doesn't exist.
amber
I've reached out to a lawyer friend to see if he can give us some
guidance. Until then, let's avoid making a recommendation either way.
Jacob
On Wed, Jun 5, 2013 at 10:01 AM, Aymeric Augustin
wrote:
> 2013/5/10 Aymeric Augustin
>>
>> > Also actively developed by @geertjanvdk at Oracle so he may
2013/5/10 Aymeric Augustin
> > Also actively developed by @geertjanvdk at Oracle so he may be able to
> > help with any issues?
>
> If he has the power to switch to a license that makes it possible to use
> his code, like the LGPL, that would be fantastic. I can't tell if he chose
> the GPL to ma
On Wed, Jun 5, 2013 at 5:59 AM, Sebastian Goll wrote:
> As an alternative to the explicit way, how about making the context
> dictionary memoizable, i.e. let Django cache each value's object
> transparently the first time it is retrieved?
I think that caching is a developer decision. If I want
On Tue, 4 Jun 2013 17:44:36 +0100
"Daniele Procida" wrote:
> What about my earlier suggestion that this be dealt with in Python, not in
> templates - that the Python programmer decides, for a particular method (or
> class, because I guess a class could have an expensive __init__()) whether
> t
I think Shai correctly seperates the concerns.
On Tue, Jun 4, 2013 at 11:03 PM, Shai Berger wrote:
> But I think that most suggestions focused more on the other issue: How to
> enable the only-do-pre-and-post-if-body-not-empty semantics with a
> succinct,
> clear syntax.
>
And considering the a
11 matches
Mail list logo
