On 24 February 2012 10:31, Paul McMillan <[email protected]> wrote: > The official Django position on the Python hash randomization issue is > that this Python bug has been fixed in Python. Users of Django should > explicitly enable hash randomization for versions of Python below 3.3. > We'll probably make a formal announcement and writeup for how to do > this once the changes have trickled down into more general > distribution channels. Users who cannot enable randomization or cannot > patch their versions of Python are advised to limit the size of > requests and the number of allowed parameters per request in their > webserver to the smallest practicable value for their use case, and > strictly limit the maximum runtime of any given process. > > Any failures of the Django test suite which are caused specifically by > this randomization change are bugs. Tickets and patches are welcome. > > -Paul >
Just run the testsuite latest Python 2.6.8 and -R option: Python 2.6.8rc1 (unknown, Feb 24 2012, 14:38:43) [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin with following results: Ran 4613 tests in 822.943s FAILED (failures=39, errors=1, skipped=109, expected failures=2) It's a bare install, so there may be more within the skipped ones. Most look harmless and only needs updating the testcases, so it doesn't require specific order. Created ticket https://code.djangoproject.com/ticket/17758 - I think this should be a release blocker. -- Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
