Re: [Django] #11678: ValueError when passing an extra parameter in URL

[Django]

#11678: ValueError when passing an extra parameter in URL
---+
  Reporter:  kberkhout | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  django.contrib.admin  |   Version:  1.1
 
Resolution:  duplicate |  Keywords:  ValueError, 
django.contrib.admin
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by mr.ksc...@gmail.com):

 Replying to [comment:3 Alex]:
 > What you've just said is orthagonal to the problem the reporter hsa.  If
 you believe there is a different bug please file a new ticket, this one is
 a duplicate.


 Ok, I just fixed how Django1.1 forward urls ... using the new
 get_urls(self) documented on
 http://docs.djangoproject.com/en/dev/ref/contrib/admin/#modeladmin-methods

 The old codes should be updated to use get_urls instead of __call__
 like...

 {{{

 def get_urls(self):
 from django.conf.urls.defaults import *

 urls = super(MyModelAdmin, self).get_urls()
 my_urls = patterns('',
 (r'search', auto_complete),
 )
 return my_urls + urls
 }}}

-- 
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] #11678: ValueError when passing an extra parameter in URL

[Django]

#11678: ValueError when passing an extra parameter in URL
---+
  Reporter:  kberkhout | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  django.contrib.admin  |   Version:  1.1
 
Resolution:  duplicate |  Keywords:  ValueError, 
django.contrib.admin
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 What you've just said is orthagonal to the problem the reporter hsa.  If
 you believe there is a different bug please file a new ticket, this one is
 a duplicate.

-- 
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] #11678: ValueError when passing an extra parameter in URL

[Django]

#11678: ValueError when passing an extra parameter in URL
---+
  Reporter:  kberkhout | Owner:  nobody 
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  1.1
 
Resolution:|  Keywords:  ValueError, 
django.contrib.admin
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by mr.ksc...@gmail.com):

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

Comment:

 this may not be a duplicate for #3785.

 as some of the auto-complete widgets for ForeginKeyField are using url
 like "/app/model/search..."
 in which the url is responded by ModelAdmin's __call__ as follow.

 {{{

 # forward request by url
 def __call__(self, request, url):
 if url is None:
 pass
 elif url == 'search':
 return auto_complete(request)
 return super(MyModelAdmin, self).__call__(request, url)
 }}}

 In Django 1.0.2, this works fine with the __call__ request forward. But in
 1.1, above exception raised.

-- 
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
-~--~~~~--~~--~--~---

[Django] #11794: Grammar and sentence fix

[Django]

#11794: Grammar and sentence fix
---+
 Reporter:  seemant|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 On the [http://docs.djangoproject.com/en/dev/topics/db/managers/ Managers
 doc page], you have this sentence:

 {{{
 In providing this functionality in your manager, there are a couple of
 things to be remember and that's the topic of this section.
 }}}

 I would suggest, instead:

 {{{
 In providing this functionality in your manager, there are a couple of
 things to remember.
 }}}

-- 
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] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
---+
  Reporter:  JayKlehr  | Owner:  stavros
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Replying to [comment:14 SmileyChris]:
 > Replying to [comment:12 stavros]:
 > > Any idea where the regression tests should go?
 >
 > Answering the initial question (Russ must have missed this after the
 second question threw him into a rage :)),

 Hulk Angry! Crush patch with no tests! :-)

 Apologies - you're right. I should have given some direction on test
 location.

 Chris' feedback is pretty much on the money, with one modification. Rather
 than putting the tests directly into in __init__.py, __init__.py should be
 used as a staging module to load the tests from other locations. See
 contrib.auth for an example of the way to organize the tests.

-- 
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] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
---+
  Reporter:  JayKlehr  | Owner:  stavros
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Comment (by SmileyChris):

 Replying to [comment:12 stavros]:
 > Any idea where the regression tests should go?

 Answering the initial question (Russ must have missed this after the
 second question threw him into a rage :)), put them in the contrib app
 itself. I'd suggest
 {{{
 /django/contrib/sitemaps/tests/__init__.py   <- put the test here
 /django/contrib/sitemaps/tests/urls.py   <- your unit test will need a
 custom urlconf
 }}}

 At the bare minimum, just write some tests to prove the new behaviour
 works. But feel free to add additional tests of base sitemap functionality
 for extra brownie points.

-- 
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] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
---+
  Reporter:  JayKlehr  | Owner:  stavros
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Replying to [comment:12 stavros]:
 > Any idea where the regression tests should go? There are no preexisting
 tests.

 Then now is the time to write some.

 > Does this code even need tests? It's pretty straightforward (I'm pretty
 sure this will come back to bite me in the ass).

 Yes, tests are required. Tests are not optional. You need to provide a
 very compelling reason that tests are either impractical or impossible
 before you get a pass on writing tests.

-- 
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
-~--~~~~--~~--~--~---

[Django] #11793: i18n documentation makemessages format doesn't work

[Django]

#11793: i18n documentation makemessages format doesn't work
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords:  i18n   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The i18n docs give the following command line to specify multiple file
 extensions to examine:

 django-admin.py makemessages -l=de -e=html,txt -e xml

 However, the =-signs don't seem to be allowed. I noticed this trying to
 examine html and txt files, when -e=html,txt only examined txt files.
 Also, making messages with -l=de, I get a =de directory in locale dir.

-- 
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] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
---+
  Reporter:  JayKlehr  | Owner:  stavros
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Comment (by stavros):

 Any idea where the regression tests should go? There are no preexisting
 tests.

 Does this code even need tests? It's pretty straightforward (I'm pretty
 sure this will come back to bite me in the ass).

-- 
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] #11792: incorrect activation of the code for admin site in urls.py

[Django]

#11792: incorrect activation of the code for admin site in urls.py
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 If you could not get the

 {{{
 #!python
 # Uncomment the next line to enable the admin:
 (r'admin/', include(admin.site.urls)),
 }}}

 version to work then I suspect you were not using 1.1.  It is definitely
 the correct code for 1.1, as it was added for 1.1. (The earlier
 `admin.site.root` code will still work with 1.1 though it is on its way to
 being deprecated.)

 You say you downloaded 1.1 -- are you sure you do not also have some
 earlier version installed that is getting picked up instead of the one you
 just retrieved (and, I assume, installed somewhere)?

-- 
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
-~--~~~~--~~--~--~---

[Django] #11792: incorrect activation of the code for admin site in urls.py

[Django]

#11792: incorrect activation of the code for admin site in urls.py
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I downloaded Django-1.1 and while going trough the tutorial, the code
 under the section "Activate the admin site" didn't work.
 I found that the correct code was
 -
 from django.conf.urls.defaults import *
 from django.contrib import admin

 admin.autodiscover()

 urlpatterns = patterns('',
 # Example:
 # (r'^mysite/', include('mysite.foo.urls')),

 # Uncomment this for admin:
  (r'^admin/(.*)', admin.site.root),
 )
 

 which is different from the one exposed in the page as:
 --
 from django.conf.urls.defaults import *

 # Uncomment the next two lines to enable the admin:
 from django.contrib import admin
 admin.autodiscover()

 urlpatterns = patterns('',
 # Example:
 # (r'^mysite/', include('mysite.foo.urls')),

 # Uncomment the admin/doc line below and add
 'django.contrib.admindocs'
 # to INSTALLED_APPS to enable admin documentation:
 # (r'^admin/doc/', include('django.contrib.admindocs.urls')),

 # Uncomment the next line to enable the admin:
 (r'^admin/', include(admin.site.urls)),
 )
 

-- 
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] #7150: patch to implement view pemission in admin

[Django]

#7150: patch to implement view pemission in admin
+---
  Reporter:  Antonio Gallo   | Owner:  
nobody   
Status:  closed | Milestone:
   
 Component:  django.contrib.admin   |   Version:  
1.0  
Resolution:  duplicate  |  Keywords:  
admin permissions
 Stage:  Unreviewed | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by Russ Ryba ):

 I added this to the 1.2 wiki features for further discussion.  I agree
 with get and buriy above.  This seems incredibly useful and relatively
 easy to implement in the core, yet adding the same feature elsewhere
 requires thorough knowledge of django and python in general.

 Regarding this comment:

 {{{
 As such, there are no plans to add this feature; consider wiring up some
 generic views and applying permission-based decorators if you truly have
 a need for "administrators" who don't administer anything.
 }}}

 You're misunderstanding the request I believe.  Think of it more as easily
 allowing more sophisticated application level administrators in a large
 organization.  We are not requesting administrators who don't administer
 anything, although I suppose that would be a possibility if it were
 implemented.

 If the thinking is administrators should have total access then why
 implement permissions in the first place?  I don't understand why it's
 rejected.

 Basically we have need for administrators who don't administer
 '''everything'''.

-- 
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] #342: Add a way for fields to be displayed in the admin without being editable

[Django]

#342: Add a way for fields to be displayed in the admin without being editable
---+
  Reporter:  Bless | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  newforms-admin
Resolution:|  Keywords:  djangocon 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: russr...@gmail.com (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 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] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

[Django]

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+--
  Reporter:  mrmachine   | Owner:  ccahoon  
 
Status:  new | Milestone:  1.2  
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  |  Keywords:  stream 
HttpResponse Content-Length
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by lukeplant):

 FYI - the use of `HttpResponse.content` in the CSRF middleware should
 hopefully go away completely in Django 1.4.  Before then (Django 1.2
 hopefully), it will be isolated in a deprecated middleware, replaced by a
 streaming friendly method.  See CsrfProtection for more.

-- 
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] #342: Add a way for fields to be displayed in the admin without being editable

[Django]

#342: Add a way for fields to be displayed in the admin without being editable
---+
  Reporter:  Bless | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  newforms-admin
Resolution:|  Keywords:  djangocon 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by nix):

 * cc: listu...@peternixon.net (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 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] #11394: Should have a Form Variable for the Login method in Auth.Views

[Django]

#11394: Should have a Form Variable for the Login method in Auth.Views
---+
  Reporter:  o...@toxicdesign.com  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Authentication|   Version:  1.0   
Resolution:|  Keywords:  views 
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by megaman...@gmail.com):

 I second this. It would be much easier to just add a form variable to the
 login view rather than having to copy / paste the login view just to
 change the form out.

-- 
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
-~--~~~~--~~--~--~---

[Django] #11791: Incorrect HTML Code rendered in list_editable enabled changelists

[Django]

#11791: Incorrect HTML Code rendered in list_editable enabled changelists
---+
 Reporter:  pa...@fragstore.net|   
Owner:  nobody
   Status:  new|   
Milestone:
Component:  Contrib apps   | 
Version:  1.1   
 Keywords:  list_editable, admin_list.py, items_for_result, opera  |   
Stage:  Unreviewed
Has_patch:  0  |  
---+
 items_for_result in django.contrib.admin.templatetags.admin_list.py
 appends the hidden field for the form-id to the output which, in the case
 of the multiple forms in the change form, results in an input field right
 after the last field which has been rendered:

 Example:
 {{{
 http://127.0.0.1:8199/media/img/admin/icon-no.gif;
 alt="False" />http://127.0.0.1:8199/media/img/admin
 /icon-no.gif" alt="0" />
 }}}

 As far as I know that type of HTML element isn't allowed between the
 closing tags of TD and TR. This results in corrupted output when using
 Opera to view such a change list - it renders an empty blue line on top of
 the change list for every item in the change list.


 A quick fix would be to let items_for_result "inject" the hidden input
 right after the last field itself, inside its TD, not outside.

-- 
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] #11790: problem with component filed in Ticket

[Django]

#11790: problem with component filed in Ticket
+---
  Reporter:  ramesh | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * status:  new => closed
  * needs_better_patch:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This doesn't look like it's a Django problem - it sounds like you're
 having problems with a Trac install. This isn't a help forum, and it isn't
 a forum for Trac configuration.

-- 
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
-~--~~~~--~~--~--~---

[Django] #11790: problem with component filed in Ticket

[Django]

#11790: problem with component filed in Ticket
---+
 Reporter:  ramesh |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hi,

 Am facing problem with component filed in Ticket ,Mr.X created ticket by
 selecting the component TEST1, and assigned to Mr.Y, (he is having trac
 modify rights), While updating the ticket he changed the component to
 TEST2.
 I want to restrict this. Addition to this i want setup access restriction
 for creating ticket. While creating/modify the ticket i want to restrict
 users Mr. X to select the component TEST1 .

 Will you please give me some suggestion and solution to overcome this
 issue.

 Thanks,
 Ramesh V

-- 
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
-~--~~~~--~~--~--~---

[Django] #11789: Aggregates ignore none()

[Django]

#11789: Aggregates ignore none()
--+-
 Reporter:  alexr |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  aggregates|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 Model.objects.all().aggregate(Max('field'))
 }}}
 and
 {{{
 Model.objects.none().aggregate(Max('field'))
 }}}
 seem to return the same thing. Aggregates pay attention to filters, but
 they seem to ignore the none() method. This isn't a common use, so it
 might not be worth fixing, except for correctness.

-- 
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
-~--~~~~--~~--~--~---

[Django] #11788: cache_page decorator doesn't work with HttpResponses whose content is an iterator

[Django]

#11788: cache_page decorator doesn't work with HttpResponses whose content is an
iterator
+---
 Reporter:  RaceCondition   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 To reproduce:

 {{{
 @cache_page(60*15)
 def foo(request):
 return HttpResponse(i for i in ('resp', 'onse'))
 }}}

 Responds with emptiness. Outcomment {...@cache_page(60*15)}}} or replace
 {{{i for i in ('resp', 'onse')}}} with {{{'response'}}} and it's fine.

 The documentation for {{{HttpResponse}}} is clear about this: "content can
 be an iterator or a string."

-- 
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] #8898: `required` validation bypassed when using `DateTimeField` with `SplitDateTimeWidget`.

[Django]

#8898: `required` validation bypassed when using `DateTimeField` with
`SplitDateTimeWidget`.
-+--
  Reporter:  mrmachine   | Owner:  nobody   

Status:  new | Milestone:   

 Component:  Forms   |   Version:  SVN  

Resolution:  |  Keywords:  DateTimeField 
SplitDateTimeWidget
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Changes (by gvangool):

 * cc: gertvang...@gmail.com (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 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] #11698: Add Django Debug Toolbar to contrib

[Django]

#11698: Add Django Debug Toolbar to contrib
---+
  Reporter:  russellm  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 Can some of the improvements by dcramer, in particular profiling support
 which is very useful, be also integrated? See http://github.com/dcramer
 /django-debug-toolbar/tree/master

-- 
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
-~--~~~~--~~--~--~---

[Django] #11787: additional fields

[Django]

#11787: additional fields
+---
 Reporter:  Hinnack |   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.localflavor  | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I wonder if the following fields do not belong here, too:
 - money sign (printable and iso) => EUR and €
 - money format (even negative)
 - number format (even negative)
 - date format(s)
 - timezones available in the country

 maybe even:
 - country names in local language
 - international phone number prefixes

-- 
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] #5390: Add signals to ManyRelatedManager

[Django]

#5390: Add signals to ManyRelatedManager
--+-
  Reporter:  Ludovico Magnocavallo   | Owner:  
rvdrijst   
Status:  assigned | Milestone:  
   
 Component:  Database layer (models, ORM) |   Version:  SVN 
   
Resolution:   |  Keywords:  
manytomanyfield feature signals
 Stage:  Design decision needed   | Has_patch:  1   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by eromirou):

 * cc: eromirou (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 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
-~--~~~~--~~--~--~---