Re: [Django] #10761: ModelAdmin.queryset() is missing a mechanism for specifying different querysets for changelist and change object views

[Django]

#10761: ModelAdmin.queryset() is missing a mechanism for specifying different
querysets for changelist and change object views
---+
  Reporter:  mrts  | Owner:  nobody 
Status:  new   | Milestone:  1.2
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords:  efficient-admin
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 #11848 requested this again.

-- 
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] #11848: Hook to be able to customize changelist_view

[Django]

#11848: Hook to be able to customize changelist_view
---+
  Reporter:  igors | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 #10761 is already open requesting this.

-- 
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] #11848: Hook to be able to customize changelist_view

[Django]

#11848: Hook to be able to customize changelist_view
--+-
 Reporter:  igors |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Currently, the changelist_view uses self.queryset to display the list of
 objects instances. So, to customize what changelist will use, you need to
 customise self.queryset. The bad point is that change_view also uses
 self.queryset, and maybe you don't wan't do affect it.

 For example: I have a list of Page objects, that could have subpages. The
 subpages are Pages too, but are not listed in changelist. But you should
 be able to edit subpages (since they are Page objects). I've attached an
 image of my admin with this use case.
 If I customize self.queryset to hide subpages (in changelist view), I
 can't access subpages form (change view) anymore.

 I've attached a patch fix this. Just creating a self.queryset_changelist
 hook. And changing ChangeList to use it. Now I can customize what
 changelist will show me, without affecting what I can edit.

-- 
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] #11847: FormWizard in urlconf is not reversable

[Django]

#11847: FormWizard in urlconf is not reversable
--+-
 Reporter:  r...@whidbey.com   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.formtools  | Version:  1.1   
 Keywords:  formwizard url reverse|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The recommended way to use a FormWizard is to embed the FormWizard into
 the urlconf (where it'll be called with __call__, and operates like a
 view).  However, any template that uses the "url" tag to reverse a view
 won't work with this.

 Fix: don't embed the FormWizard directly into urlconf; wrap it in a view
 (how?  haven't had any luck with this)
 Workaround: add another entry to urlconf for the _same_ url, pointing to a
 view that does nothing.  Use this view as the 'url' tag parameter in the
 template.

 I acknowledge this is really ugly.

-- 
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] #8764: Documentation should explain you can't mix args and **kwargs in reverse()

[Django]

#8764: Documentation should explain you can't mix args and **kwargs in reverse()
+---
  Reporter:  tolano | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  reverse function exception
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by vegas):

 Apologies on the crazy bolding there. My g1 inserted a bunch of single
 quotes and has some serious issues with editing textboxes. Also, karen on
 the mailing list already pointed me at the google group thread on this
 topic

-- 
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] #8764: Documentation should explain you can't mix args and **kwargs in reverse()

[Django]

#8764: Documentation should explain you can't mix args and **kwargs in reverse()
+---
  Reporter:  tolano | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  reverse function exception
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by vegas):

 I got directed here from the django-dev mailing list.  I don't see anyone
 making an actual c''ase that this is impossible, and I'm fairly
 certain that it is quite possible. There once was a language called Prolog
 that approached all computation as a solution to this problem, and there
 is still a slobbering beast called XSLT that does it for every function
 call.

 That being said, I'm not super familiar with the django source, so I buy
 that it might be an *engineering impossibility* at this point in time. I
 was debugging around in 1.1's guts yesterday, and noticed that it seems
 when an urlpattern with both positional groups and named groups is
 matched, the positional groups are dropped in the trash can.  I don't
 think this is the Re modules fault, but if it were that would be a good
 case for letting this sleeping bug lie. I'll investigate the matter and
 post back here with my findings and hopefully a patch.  Would love to hear
 any pointers anyone has.

-- 
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] #11846: field check does not wok

[Django]

#11846: field check does not wok
-+--
  Reporter:  ankit   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1-beta-1
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ankit):

 I am using postgres and my db column is double precision

-- 
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] #11846: field check does not wok

[Django]

#11846: field check does not wok
-+--
  Reporter:  ankit   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1-beta-1
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ankit):

 But in the DB table it is being stored as -0.I know that this will not
 have any problem but logically there is no number  as -0.Well to  overcome
 this problem i am using abs value while saving

-- 
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  closed   | Milestone:  1.1
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:  fixed|  Keywords:  comment preview
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by hitcliff):

 thanks a lot for this great article! I really liked what this tutorial has
 to offer! having not much experience in tnis sphere I really appreciate
 every piece of advice I can get. have used to download great books with
 useful information from http://www.picktorrent.com , but always search for
 smth new. thanks!

-- 
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] #11846: field check does not wok

[Django]

#11846: field check does not wok
-+--
  Reporter:  ankit   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1-beta-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
  * needs_tests:  => 0
  * needs_docs:  => 0
  * resolution:  => invalid

Old description:

> I am having a class which is defined as
>

> class ABC(models.Model):
> id = models.CharField(max_length=100, primary_key=True)
> pub = models.ForeignKey(WapUser, null=True)
> brief_description = models.TextField(null=True,blank=True)
> status = models.CharField(max_length=12, null=True,
> help_text='Select the appropriate status and click on save',
> choices=SITE_STATUS_CHOICES )
> created_on = models.DateTimeField(null=True)
> pub_share =
> models.DecimalField('site_rev_share',max_digits=4,decimal_places=2,null=True)
> require_full_size_banner = models.IntegerField("Full Size Banner
> Ads", choices=BOOLEAN_CHOICES, default = 0,null=True)
> modified_on =
> models.DateTimeField(auto_now=True,auto_now_add=True,verbose_name
> ='Last_modified_on')
> critical_nfr =
> models.DecimalField(max_digits=5,decimal_places=3,default='60',help_text='Plesae
> Enter in the range of (0-100)')
> class Meta:
> db_table = u'wap_abc'
> verbose_name_plural= "ABC"
> managed = False
> def __unicode__(self):
> return self.status
> def get_absolute_url(self):
> return "/abc/%i/" % self.id
>

>

> And form.py looks like
>

> class SiteForm(ModelForm):
> class Meta:
> model = ABC
> reason_for_reject =
> CharField(widget=forms.Textarea,max_length=500,help_text='Please enter if
> the reason is not in the list',required=False)
>

>  def clean(self):
> cleaned_data = self.cleaned_data
> newStatus = self.cleaned_data.get('status')
> id_a = self.cleaned_data.get('id')
> critical_nfr = self.cleaned_data.get('critical_nfr')
>
> if new_pub_share == 0 or new_pub_share >=100:
> raise forms.ValidationError('You cannot set
> pub_share either equal to 0% or greater than equal to 100% !')
> if critical_nfr <0  and critical_nfr is not None:
> raise forms.ValidationError('You cannot set
> critical_nfr less than Zero !')
> if self.instance and self.instance.status=='pending':
> if newStatus =='activated' or newStatus ==
> 'rejected':
>
> if newStatus == 'rejected':
> if rejection_code is None and
> new_rejection_reason=='':
> raise
> forms.ValidationError('Please select a reason to reject or else write in
> the box given below  !')
> if rejection_code != None and
> new_rejection_reason!='':
> raise
> forms.ValidationError('You cannot select both, either select a reason or
> write it !')
>

>
> now if i enter the value of critical_nfr<0,it gives error but if i give
> '-0' then it does not give any error.WHy .-0 is not any number

New description:

 I am having a class which is defined as

 {{{
 #!python
 class ABC(models.Model):
 id = models.CharField(max_length=100, primary_key=True)
 pub = models.ForeignKey(WapUser, null=True)
 brief_description = models.TextField(null=True,blank=True)
 status = models.CharField(max_length=12, null=True,
 help_text='Select the appropriate status and click on save',
 choices=SITE_STATUS_CHOICES )
 created_on = models.DateTimeField(null=True)
 pub_share =
 models.DecimalField('site_rev_share',max_digits=4,decimal_places=2,null=True)
 require_full_size_banner = models.IntegerField("Full Size Banner
 Ads", choices=BOOLEAN_CHOICES, default = 0,null=True)
 modified_on =
 models.DateTimeField(auto_now=True,auto_now_add=True,verbose_name
 ='Last_modified_on')
 critical_nfr =
 
models.DecimalField(max_digits=5,decimal_places=3,default='60',help_text='Plesae
 Enter in the range of (0-100)')
 class Meta:
 db_table = u'wap_abc'
 verbose_name_plural= "ABC"
 managed = False
 def __unicode__(self):
 return self.status
 def get

[Django] #11846: field check does not wok

[Django]

#11846: field check does not wok
---+
 Reporter:  ankit  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  1.1-beta-1
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I am having a class which is defined as


 class ABC(models.Model):
 id = models.CharField(max_length=100, primary_key=True)
 pub = models.ForeignKey(WapUser, null=True)
 brief_description = models.TextField(null=True,blank=True)
 status = models.CharField(max_length=12, null=True,
 help_text='Select the appropriate status and click on save',
 choices=SITE_STATUS_CHOICES )
 created_on = models.DateTimeField(null=True)
 pub_share =
 models.DecimalField('site_rev_share',max_digits=4,decimal_places=2,null=True)
 require_full_size_banner = models.IntegerField("Full Size Banner
 Ads", choices=BOOLEAN_CHOICES, default = 0,null=True)
 modified_on =
 models.DateTimeField(auto_now=True,auto_now_add=True,verbose_name
 ='Last_modified_on')
 critical_nfr =
 
models.DecimalField(max_digits=5,decimal_places=3,default='60',help_text='Plesae
 Enter in the range of (0-100)')
 class Meta:
 db_table = u'wap_abc'
 verbose_name_plural= "ABC"
 managed = False
 def __unicode__(self):
 return self.status
 def get_absolute_url(self):
 return "/abc/%i/" % self.id




 And form.py looks like


 class SiteForm(ModelForm):
 class Meta:
 model = ABC
 reason_for_reject =
 CharField(widget=forms.Textarea,max_length=500,help_text='Please enter if
 the reason is not in the list',required=False)


  def clean(self):
 cleaned_data = self.cleaned_data
 newStatus = self.cleaned_data.get('status')
 id_a = self.cleaned_data.get('id')
 critical_nfr = self.cleaned_data.get('critical_nfr')

 if new_pub_share == 0 or new_pub_share >=100:
 raise forms.ValidationError('You cannot set
 pub_share either equal to 0% or greater than equal to 100% !')
 if critical_nfr <0  and critical_nfr is not None:
 raise forms.ValidationError('You cannot set
 critical_nfr less than Zero !')
 if self.instance and self.instance.status=='pending':
 if newStatus =='activated' or newStatus ==
 'rejected':

 if newStatus == 'rejected':
 if rejection_code is None and
 new_rejection_reason=='':
 raise
 forms.ValidationError('Please select a reason to reject or else write in
 the box given below  !')
 if rejection_code != None and
 new_rejection_reason!='':
 raise
 forms.ValidationError('You cannot select both, either select a reason or
 write it !')



 now if i enter the value of critical_nfr<0,it gives error but if i give
 '-0' then it does not give any error.WHy .-0 is not any number

-- 
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] #11845: minor typo in code example (tutorial pt 3)

[Django]

#11845: minor typo in code example (tutorial pt 3)
+---
  Reporter:  jimr   | 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:

 No, the trailing comma there is not an error.  It's common practice to
 make adding items easier since you don't have to remember to add a comma
 to the previous line when you add a new line.  If removing it fixed a
 syntax error for you then there is some other error in what you've got
 that is causing it.

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:13 paul.h...@gmail.com]:
 > I just noticed that the empty string quotes after nome= and name= did
 not get through to the last comment that I posted.

 They were interpreted as Wiki formatting characters which turned on, and
 then off, italics.  To avoid this you should mark code blocks as
 preformatted text:
 http://code.djangoproject.com/wiki/WikiFormatting#Preformattedtext.  Also
 checking how the comment will look via Preview before hitting Submit is
 always a good idea.

-- 
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] #11845: minor typo in code example (tutorial pt 3)

[Django]

#11845: minor typo in code example (tutorial pt 3)
---+
 Reporter:  jimr   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In the {{{mysite/urls.py}}} code sample in
 http://docs.djangoproject.com/en/dev/intro/tutorial03/#design-your-urls,
 there's an extra comma at the end of the {{{urlpatterns}}} declaraion:

 {{{(r'^admin/', include(admin.site.urls)),}}}

 which causes a syntax error. Removing the comma fixes the issue.

-- 
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] #11844: Select_related() and defer()

[Django]

#11844: Select_related() and defer()
--+-
 Reporter:  krylatij  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  selected_related,defer|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Invalid field values when you use select_related() and defer().
 See sample below.
 May be it clashes with ticket #11606

 #models.py


 {{{
 class Author(models.Model):
 name = models.CharField(max_length=20, default='author')
 text1 = models.CharField(default='text1', max_length=10)
 text2 = models.CharField(default='text2', max_length=10)

 def __unicode__(self):
 return u'%s' % self.name

 class Work(models.Model):
 name = models.CharField(max_length=20, default='work')
 author = models.ForeignKey(Author)

 def __unicode__(self):
 return u'%s' % self.name
 }}}


 #manage.py shell

 {{{
 from test.myapp.models import *
 a = Author()
 a.save()
 w = Work()
 w.author = a
 w.save()
 w =
 Work.objects.filter(id=1).select_related('author').defer('author__text1')[0]
 print w.author.text1
 >> u'text2'  !!! ERROR

 }}}

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Comment (by paul.h...@gmail.com):

 I just noticed that the empty string quotes after nome= and name= did not
 get through to the last comment that I posted.

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Comment (by paul.h...@gmail.com):

 Line 182 of the patch to django/contrib/admin/widgets.py currently reads:
 def label_for_value(self, value, nome=''):
 but this is probably meant be:
 def label_for_value(self, value, name=''):
 This would not cause any tests to fail since the arg is not (currently)
 used.

-- 
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] #11824: {% with %} tag to support tuples

[Django]

#11824: {% with %} tag to support tuples
--+-
  Reporter:  semenov  | Owner:  nobody 
Status:  closed   | Milestone: 
 Component:  Template system  |   Version:  1.1
Resolution:  wontfix  |  Keywords:  with, tuple
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by iapain):

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

Comment:

 @semenov its better proposal, I'd recommend you to discuss it on django-
 dev mailing list and then create a new proposal ticket.

-- 
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] #11824: {% with %} tag to support tuples

[Django]

#11824: {% with %} tag to support tuples
--+-
  Reporter:  semenov  | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  1.1
Resolution:   |  Keywords:  with, tuple
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by semenov):

 That's true, the Python's ``with`` statement doesn't support that syntax.
 Moreover, there is no statement in Python which would do that. In order to
 unpack a tuple in Python, one would do that manually:
 {{{
 #!python
 x, y = point
 }}}

 Trying to mimic the Python syntax, we would invent a new tag like:
 {{{
 {% with object.get_last_point as point %}
 {% unzip point to x, y %}
 There is a point at {{ x }},{{ y }}
 {% endwith %}
 }}}
 or even (which is less imperative and more declarative):
 {{{
 {% with object.get_last_point as point %}
 {% unzip point as x, y %}
 There is a point at {{ x }},{{ y }}
 {% endunzip %}
 {% endwith %}
 }}}

 I think my original suggestion is better. It does solve the (I believe not
 so infrequent) problem, it is backward compatible, and, in my personal
 opinion, the syntax is quite logical and even makes sense when read as an
 English language statement.

 Your observation makes perfect sense, though, so that's up to the
 commiters to decide which of the solutions would be more Django-way.

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