subject:"Re\: \[Django\] #16568\: require_debug_false does not work as intended \(backward incompatible\)"

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2013-06-06 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Please don't reopen closed/fixed ticket with no apparent reason.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.6391c3f9aed1662048eeea4e9fda3071%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2013-06-06 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by venu ):

 * cc: kulala.venu@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.75c7e3d0e7423a58cc0c7fb59e69725e%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2013-06-06 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by venu ):

 * status:  closed => new
 * resolution:  fixed =>


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.621aea3497d8f18f113bd64d04e0d79c%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-10-09 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+
 Reporter:  andreas_pelme|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  SVN
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by loewis):

 In [16950]:
 {{{
 #!CommitTicketReference repository="" revision="16950"
 Merged revisions
 
16743,16745,16747-16750,16752-16754,16756-16760,16770,16773-16800,16802-16804,16806,16808,16811,16813,16815,16817-16826,16829-16833,16835-16836,16838-16843,16845-16858,16860-16866,16868,16871-16877,16882-16890,16893-16947
 via svnmerge from
 https://code.djangoproject.com/svn/django/trunk

 
   r16743 | gabrielhurley | 2011-09-09 23:36:58 +0200 (Fr, 09 Sep 2011) | 2
 lines

   Fixed #16791 -- Updated a broken URL in the README file. Thanks to
 paulcwatts for the report and patch.
 
   r16745 | Alex | 2011-09-09 23:45:58 +0200 (Fr, 09 Sep 2011) | 1 line

   Switch to using explicit new-style division behavior, rather than
 relying on teh classic behavior.
 
   r16747 | SmileyChris | 2011-09-10 00:32:38 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fix and test for cleaning a non-string value in a URLField
 
   r16748 | gabrielhurley | 2011-09-10 00:33:28 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16786 -- Minor cleanups in the memcached section of the caching
 topic guide. Thanks to jamesp for the report and patch.
 
   r16749 | jbronn | 2011-09-10 00:34:23 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16408 -- Fixed conversion of dates, and other problems with the
 SpatiaLite backend.
 
   r16750 | jbronn | 2011-09-10 00:47:18 +0200 (Sa, 10 Sep 2011) | 1 line

   Removed extra call to `syncdb` that slipped in with r16749.
 
   r16752 | SmileyChris | 2011-09-10 00:57:12 +0200 (Sa, 10 Sep 2011) | 1
 line

   Fixes #16664 -- URLField's to_python method fails with ValueError on
 some urls on python 2.7. Based on patch by zigzag.
 
   r16753 | russellm | 2011-09-10 01:02:33 +0200 (Sa, 10 Sep 2011) | 1 line

   Added two pointless query repeats to work around a known issue with
 MySQL that was causing failures in our test suite.
 
   r16754 | gabrielhurley | 2011-09-10 01:25:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #16782 -- Corrected a broken cross-reference to the database
 engine setting in the tutorial. Thanks to mjumbewu for the report and
 patch.
 
   r16756 | kmtracey | 2011-09-10 02:05:48 +0200 (Sa, 10 Sep 2011) | 2
 lines

   Fixed #15722: ensure formsets evaluate to True even if they have no
 forms. Thanks mlavin.
 
   r16757 | jbronn | 2011-09-10 02:29:34 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #13670 -- Comparisons with the spatial adapter won't blow up in
 some corner cases.  Thanks, milosu for the bug report and jpaulett for the
 patch.
 
   r16758 | russellm | 2011-09-10 02:46:38 +0200 (Sa, 10 Sep 2011) | 1 line

   Added protection against spoofing of X_FORWARDED_HOST headers. A
 security announcement will be made shortly.
 
   r16759 | russellm | 2011-09-10 02:46:48 +0200 (Sa, 10 Sep 2011) | 1 line

   Corrected an issue which could allow attackers to manipulate session
 data using the cache. A security announcement will be made shortly.
 
   r16760 | russellm | 2011-09-10 02:47:00 +0200 (Sa, 10 Sep 2011) | 1 line

   Altered the behavior of URLField to avoid a potential DOS vector, and to
 avoid potential leakage of local filesystem data. A security announcement
 will be made shortly.
 
   r16770 | Alex | 2011-09-10 03:53:56 +0200 (Sa, 10 Sep 2011) | 1 line

   Make ``Formset.__getitem__`` O(1), rather than O(n).  If you override
 ``__iter__`` you now need to also override ``__getitem__`` for consistant
 behavior.  Thanks to Carl and Russ for the review.
 
   r16773 | Alex | 2011-09-10 04:42:05 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #11404.  Added ``FormSet.has_changed``, for consistancy with
 ``Form.has_changed``. Thanks to michelts for the patch.
 
   r16774 | Alex | 2011-09-10 04:52:37 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16793. Added more cross referencing to the load tag's
 documentation.  Thanks to bluejeansummer for the patch.
 
   r16775 | jbronn | 2011-09-10 05:04:30 +0200 (Sa, 10 Sep 2011) | 1 line

   Fixed #16790 -- Modified the geographic admin to work after r16594.
 Thanks, jdiego, for the bug report and patch.
 
   r16776 | carljm | 2011-09-10 05:26:13 +0200

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-20 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution:  fixed  |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by anonymous):

 Answer updated on stackoverflow question too.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-20 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution:  fixed  |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by andreas_pelme):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 I am not sure what your problem is exactly, but I do not think it is
 related to this ticket. The {{{CallbackFilter}}} was not added until after
 1.3, so it should not be import:able in a Django 1.3.x install. And this
 ticket actually removes {{{CallbackFilter}}} from the default settings.
 You probably have your settings files mixed up, your project is probably
 using a django-trunk-settings-file when the {{{CallbackFilter}}} was added
 to the settings template.

 You should probably add your settings file to the stackoverflow question.
 I have apparently not enough stackoverflow karma to post a comment, but
 that would be my advice to be able to help out!

 Im closing this ticket as I cannot see how your problem is possibly
 related to this bug, please reopen it with proper instructions for how to
 reproduce this if I am wrong!

 Please try the same commands as shown here (requires pip, virtualenv and
 virtualenvwrapper):
 {{{
 ~ $ mkvirtualenv t16568-regression
 New python executable in t16568-regression/bin/python
 Installing setuptoolsdone.
 Installing pip...done.
 virtualenvwrapper.user_scripts creating
 /Users/andreas/.virtualenvs/t16568-regression/bin/predeactivate
 virtualenvwrapper.user_scripts creating
 /Users/andreas/.virtualenvs/t16568-regression/bin/postdeactivate
 virtualenvwrapper.user_scripts creating
 /Users/andreas/.virtualenvs/t16568-regression/bin/preactivate
 virtualenvwrapper.user_scripts creating
 /Users/andreas/.virtualenvs/t16568-regression/bin/postactivate
 virtualenvwrapper.user_scripts creating
 /Users/andreas/.virtualenvs/t16568-regression/bin/get_env_details
 [t16568-regression] ~ $ pip install django==1.3.1
 Downloading/unpacking django==1.3.1
   Downloading Django-1.3.1.tar.gz (6.5Mb): 6.5Mb downloaded
   Running setup.py egg_info for package django

 Installing collected packages: django
   Running setup.py install for django
 changing mode of build/scripts-2.7/django-admin.py from 644 to 755

 changing mode of /Users/andreas/.virtualenvs/t16568-regression/bin
 /django-admin.py to 755
 Successfully installed django
 Cleaning up...
 [t16568-regression] ~ $ cd code/
 [t16568-regression] ~ $ django-admin.py startproject foo
 [t16568-regression] ~ $ cd foo/
 [t16568-regression] ~/foo $ python manage.py shell

 In [1]: import django; django.get_version()
 Out[1]: '1.3.1'

 In [2]: exit()
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-20 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by zengr):

 Reference to the bug on stackoverflow.com:
 http://stackoverflow.com/questions/7410151/valueerror-unable-to-configure-
 filter-require-debug-false-cannot-resolve-dja

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-20 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by tyre77@…):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I don't think this is actually fixed. With 1.3.1 installed, a simple
 python manage.py shell" produces the following:

 ValueError: Unable to configure filter 'require_debug_false': Cannot
 resolve 'django.utils.log.CallbackFilter': No module named CallbackFilter

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-16 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by andreas_pelme):

 * needs_better_patch:  1 => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-16 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by andreas_pelme):

 Yeah, it was a trivial change and a small merge conflict to update to
 latest trunk, anyways, here is a patch that applies cleanly on latest
 trunk.

 You can also pull branch t16568 from git://github.com/pelme/django.git if
 you like!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-16 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by carljm):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:5 andreas_pelme]:
 > I had a hard time figuring out how to properly write a test for this
 too. I will update the patch to current trunk with the changes you suggest
 soonish!

 I think the updates are pretty minor, I might just make them today and
 commit. If I don't get to it, feel free to update the patch, that'd be
 great.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-16 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by andreas_pelme):

 I had a hard time figuring out how to properly write a test for this too.
 I will update the patch to current trunk with the changes you suggest
 soonish!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-09-16 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by carljm):

 Just spent a while trying to write a proper end-to-end regression test for
 this failure case, and there really is no reliable way to do it, since we
 can't enforce that tests are run with no LOGGING setting. We'd need to
 able to save-modify-and-restore the entire global state of the logging
 module, which AFAICT there is no way to do.

 The `test_require_debug_no_logging_setting` test in the patch does test
 the added `RequireDebugFalse` filter, but the `setUp` and `tearDown`
 methods in that test case are pointless: temporarily overriding
 settings.LOGGING has no impact, because the setting will already long ago
 have been parsed and passed to logging.dictConfig.

 So I think we'll have to be satisfied with testing the filter and testing
 that `global_settings.LOGGING` has that filter in the config. This should
 be adequate.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-08-05 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by andreas_pelme):

 * has_patch:  0 => 1


Comment:

 I created another filter, django.utils.log.RequireDebugFalse which checks
 django.conf.settings.DEBUG directly and does not have the same problem.
 This also avoids the need to introduce callables into the settings file.

 That leaves the CallbackFilter unused, but I have left it as is.

 The attached patch contains tests and updates the docs accordingly.

 The patch is also available here:
 https://github.com/pelme/django/tree/t16568 /
 git://github.com/pelme/django.git

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-08-04 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+-
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by russellm):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 I'm not wild about having a method definition in global_settings.py like
 that, but not sure it's avoidable, either.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

2011-08-04 Thread Django

#16568: require_debug_false does not work as intended (backward incompatible)
-+--
   Reporter:  andreas_pelme  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Other)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+--
Changes (by andreas_pelme):

 * cc: djangoproject.com@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

Re: [Django] #16568: require_debug_false does not work as intended (backward incompatible)

16 matches

Site Navigation

Mail list logo

Footer information