Re: Status of issue 17758: dict ordering bugs

2012-03-22 Thread Łukasz Rekucki
Hi, Thanks Aymeric for committing the ORM related fix. As Ramiro suggested, I created a separate ticket for the bug in dependency_order() function - #17954. While it's always nice to have more bugfixes, it doesn't qualify as a release blocker anymore. Looking forward to 1.4 final soon :) -- Łuka

Re: Status of issue 17758: dict ordering bugs

2012-03-22 Thread Łukasz Rekucki
On 22 March 2012 16:54, Aymeric Augustin wrote: > Le 22 mars 2012 13:22, Łukasz Rekucki a écrit : >> If the whole patch can't be merged, lets at least fix that bug[2]. Is >> there any work I can do to make it happen? >> [2]: >> https://github.com/lqc/django/commit/84dc450ec861e34de068fde891537f0

Re: Status of issue 17758: dict ordering bugs

2012-03-22 Thread Aymeric Augustin
Le 22 mars 2012 13:22, Łukasz Rekucki a écrit : > If the whole patch can't be merged, lets at least fix that bug[2]. Is > there any work I can do to make it happen? > [2]: > https://github.com/lqc/django/commit/84dc450ec861e34de068fde891537f0481342ef7 Hi Łukasz, Let's try to get this fix in 1.4

Re: Status of issue 17758: dict ordering bugs

2012-03-22 Thread Łukasz Rekucki
On 22 March 2012 13:38, Ramiro Morales wrote: > 2012/3/22 Łukasz Rekucki : > > Maybe we should split these problem reports in their own tickets? > I can do it later today. There probably should be 3 tickets: the ORM bug, the dependency_order() bug and the test suite fixes (which can be split furt

Re: Status of issue 17758: dict ordering bugs

2012-03-22 Thread Ramiro Morales
2012/3/22 Łukasz Rekucki : > Hi, > > I got a sad message today, that it's most likely that issue #17758 > won't go in to 1.4; While most of the problems addressed by this > ticket are harmless, I really don't think it's a good idea to ship 1.4 > without resolving the ORM bug. The hash randomization

Status of issue 17758: dict ordering bugs

2012-03-22 Thread Łukasz Rekucki
Hi, I got a sad message today, that it's most likely that issue #17758 won't go in to 1.4; While most of the problems addressed by this ticket are harmless, I really don't think it's a good idea to ship 1.4 without resolving the ORM bug. The hash randomization is a security fix. Right now, people