Re: Ticket #7817: Extending "with" and "include" tags.

2010-12-02 Thread Russell Keith-Magee
2010/12/3 Łukasz Rekucki : > On 30 November 2010 16:38, Jacob Kaplan-Moss wrote: >> On Thu, Nov 18, 2010 at 9:47 AM, Russell Keith-Magee >> wrote: >>> However, given the Unless Jannis is willing to downgrade his -1 to a >>> -0, I think a BDFL judgement is called for here. >> >> Let's go with {% w

Re: formsets should be iterable: closed [WONTFIX] -- why

2010-12-02 Thread Russell Keith-Magee
On Fri, Dec 3, 2010 at 3:47 AM, KentH wrote: > I completed the upload of patch, tests & docs a few weeks ago. As I > think it's complete, I was hoping review might make the sprint this > weekend. It's still assigned to "Pandres", but I think that was just > from when it was initially closed "Wontf

Localization fix

2010-12-02 Thread Klaas van Schelven
Hi all, Subtly drawing attention to http://code.djangoproject.com/ticket/14807 A minor fix including test. Klaas -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To

Re: Ticket #7817: Extending "with" and "include" tags.

2010-12-02 Thread Łukasz Rekucki
On 30 November 2010 16:38, Jacob Kaplan-Moss wrote: > On Thu, Nov 18, 2010 at 9:47 AM, Russell Keith-Magee > wrote: >> However, given the Unless Jannis is willing to downgrade his -1 to a >> -0, I think a BDFL judgement is called for here. > > Let's go with {% with a=foo b=bar %}. Does this mean

Re: formsets should be iterable: closed [WONTFIX] -- why

2010-12-02 Thread KentH
I completed the upload of patch, tests & docs a few weeks ago. As I think it's complete, I was hoping review might make the sprint this weekend. It's still assigned to "Pandres", but I think that was just from when it was initially closed "Wontfix". Pls let me know if there's something else I shou

old session data revived?

2010-12-02 Thread Martin Cole
I am trying to store a python object in the session data, which holds lots of parameter values from various previously visited forms. All of the submit actions push to the same view function. After seeing that data appear to be randomly wrong, I am managing the saving of this data myself with cP

Re: DatabaseError swallowed?

2010-12-02 Thread Jonas H.
On 12/02/2010 04:27 PM, Dan Fairs wrote: I was wondering whether the bug still exists in Python 2.x because I take it only AttributeError and TypeError should be ignored while calling __len__ in list() -- if that's the case, the bug is definitely still present. True - I'll give it a try in 2.

Re: Need help w/ sql.where.WhereNode tree

2010-12-02 Thread Jonas H.
On 12/01/2010 08:04 AM, Waldemar Kornewald wrote: In the end JOINs will be a rather complicated solution. I thought that's why you wanted to extend the ORM directly to handle embedded fields in a special way. That should be easier and cleaner. That's what I'm up to, but I have to know how to re

Re: DatabaseError swallowed?

2010-12-02 Thread Dan Fairs
> I tested it on my machine and it raises ValueError on: > > * Python 2.4.6 > * Python 2.5.5 > * Python 2.6.6 > * Python 2.7.0+ > * Python 3.1.2 > > If you have version 2.6.1, you should upgrade. I don't think Django > should support a Python bug that was fixed almost 2 years ago. > Cool

Re: DatabaseError swallowed?

2010-12-02 Thread Łukasz Rekucki
On 2 December 2010 15:43, Dan Fairs wrote: > Hi, > > Apologies for the slightly lengthy email. > > I'm working on getting ticket #2705 (Add optional FOR UPDATE clause to > QuerySets) into shape, primarily by adding tests to the patch. I'm writing a > test for a backend's FOR UPDATE NOWAIT, and h

Re: DatabaseError swallowed?

2010-12-02 Thread Dan Fairs
Hi, > On 12/02/2010 03:43 PM, Dan Fairs wrote: >> My gut feeling is that this boils down to this vastly simplified >> demonstration of how list() works: >> > class Foo(object): >> ... def __len__(self): >> ... print 'len called' >> ... raise ValueError >> ... def __iter__(self):

Re: DatabaseError swallowed?

2010-12-02 Thread Jonas H.
Hi Dan, On 12/02/2010 03:43 PM, Dan Fairs wrote: My gut feeling is that this boils down to this vastly simplified demonstration of how list() works: class Foo(object): ... def __len__(self): ... print 'len called' ... raise ValueError ... def __iter__(self): ... return iter([

DatabaseError swallowed?

2010-12-02 Thread Dan Fairs
Hi, Apologies for the slightly lengthy email. I'm working on getting ticket #2705 (Add optional FOR UPDATE clause to QuerySets) into shape, primarily by adding tests to the patch. I'm writing a test for a backend's FOR UPDATE NOWAIT, and have come across some interesting behaviour where Databa

Re: #11675:Pyblic+Memcache changes, Draft #1

2010-12-02 Thread Robert Coup
On Thu, Dec 2, 2010 at 4:50 PM, Jacob Burch wrote: > What I"m doing now (returning None) is already fairly magical. Isn't that broken? set(KEY, "a", timeout=100) set(KEY, "b", timeout=0) get(KEY) won't returning None from the set(..., 0) instead of sending the instant-expire through to memcac