Re: [Django] #6870: pre_delete should be sent before collecting ForeignKey relationships

2009-05-22 Thread Django 
#6870: pre_delete should be sent before collecting ForeignKey relationships
-+--
  Reporter:  wkornewald  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by semenov):

 While it actually '''is''' a symptom of a different (yet unsolved!)
 problem, the original suggestion makes sense per se. It shouldn't be
 disregarded just because that will magically allow to do some (useful)
 unrelated things, right?

-- 
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] #11186: Plural-Forms missing on po files generated by makemessages

2009-05-22 Thread Django 
#11186: Plural-Forms missing on po files generated by makemessages
---+
  Reporter:  dahool| Owner:  nobody
Status:  closed| Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Yes, currently the tool assumes the person doing the translation is in the
 best position to add the right plural form expression to the header of a
 newly created application-level `.po` message catalog. This is especially
 true when localizing to a language not already bundled with Django.

 For languages already included with Django, both #6505 and #11161 already
 report this and propose approaches to solving it.

 Thus I'm closing this as 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] #11160: Formset non_form_errors returns ErrorList() if is_valid is not called

2009-05-22 Thread Django 
#11160: Formset non_form_errors returns ErrorList() if is_valid is not called
-+--
  Reporter:  vbmendes| Owner:  nobody   
 
Status:  new | Milestone:   
 
 Component:  Forms   |   Version:  SVN  
 
Resolution:  |  Keywords:  formset non_form_errors 
validation
 Stage:  Unreviewed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: vbmen...@gmail.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
-~--~~~~--~~--~--~---

[Django] #11186: Plural-Forms missing on po files generated by makemessages

2009-05-22 Thread Django 
#11186: Plural-Forms missing on po files generated by makemessages
--+-
 Reporter:  dahool|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Internationalization  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The .po files generated using this command doesn't add a plural forms to
 the header ("Plural-Forms: nplurals=2; plural=(n != 1);\n"), so translator
 tools (like poedit or lokalize) doesn't recognize plurals strings.

-- 
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] #11084: After r10737, ImageField sets height and width on model creation, every lookup

2009-05-22 Thread Django 
#11084: After r10737, ImageField sets height and width on model creation, every
lookup
---+
  Reporter:  Mnewman   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by anonymous):

 * cc: sam...@lefora.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] #10808: Multiple inheritance (model-based) broken for __init__ of common fields in diamond inheritance

2009-05-22 Thread Django 
#10808: Multiple inheritance (model-based) broken for __init__ of common fields 
in
diamond inheritance
---+
  Reporter:  mikemintz | Owner:  jianhuang
Status:  assigned  | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Changes (by mikemintz):

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

[Django] #11185: Document how to customize widgets

2009-05-22 Thread Django 
#11185: Document how to customize widgets
---+
 Reporter:  bensmith   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords:  widget |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 It would be nice to have documentation on how to customize form widgets.
 Here's an example of something that I just figured out, and that would be
 nice to see in the documentation.

 You can customize how a widget is rendered by overriding it's
 renderer.render method.  This class renders radio buttons as a horizontal
 line, instead of in a list.
 {{{
 class HorizRadioRenderer(forms.RadioSelect.renderer):
 def render(self):
 """Outputs radios"""
 return mark_safe(u'\n'.join([u'%s\n' % w for w in self]))

 }}}

-- 
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] #11184: scripts/rpm-install.sh does not respect options passed to setup.py

2009-05-22 Thread Django 
#11184: scripts/rpm-install.sh does not respect options passed to setup.py
---+
 Reporter:  pgri...@gmail.com  |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Setuptools supports changing the target installation environment when
 building an RPM ({{{setup.py bdist_rpm}}}) with the {{{--python}}} or
 {{{--fix-python}}} options. These have the effect of changing the path to
 the python executable to invoke in the generated {{{.spec}}} file.

 However, Django's {{{setup.py}}} specifies a custom installation script in
 {{{scripts/rpm-install.sh}}}, which always invokes {{{python}}} directly:

 {{{
 ...
 # This is what dist.py normally does.
 python setup.py install --root=${RPM_BUILD_ROOT}
 --record="INSTALLED_FILES"
 ...
 }}}

 As a result, it's impossible to generate a Django install to target non-
 default environments.

-- 
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] #11183: BaseForm init leaves pointers pointing back to base_fields when widget is a Select

2009-05-22 Thread Django 
#11183: BaseForm init leaves pointers pointing back to base_fields when widget 
is a
Select
+---
 Reporter:  margieroginski  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Uncategorized   | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 == High Level Description ==
 When we create a form class, I think the deepcopy that is done does not do
 enough to correctly copy the class in the case when the widget is a Select
 widget.  The result is that parts of the class are left pointing back to
 the base_fields data, and when one tries to override the queryset at
 during render(), it is not possible due pointers that are incorrectly
 pointing back to base_fields data.

 == Detail ==
 When a base_field in a form points to a Select widget, the widget contains
 a choices attribute.  During initialiazation of a !ModelChoiceField, a
 !ModelChoiceIterator is created and the widget's choices attribute is set
 to point to it.  This is all done by the following line from
 !ModelChoiceField::__init__();
 self.queryset = queryset

 When BaseForm:__init__() runs, it does a deepcopy of self.base_fields.
 When copying the fields, we call the Widget::__deepcopy__() method.
 However, this method copies only the attributes and does not copy the
 !ModelChoiceIterator that a select widget points to.  I think that a copy
 should be made of this !ModelChoiceIterator, and furthermore, I think that
 after making the copy, the newly copied !ModelChoiceIterator's 'field'
 attribute needs to be updated so that it points to the copied field whose
 deepcopy caused it to be copied.

 I encountered this issue when I tried to override the queryset for a
 !ModelChoiceField with a line like this in the render() function of a
 widget that derives from a Select widget.  Here is some example code that
 my usage:

 {{{
 class OwnerSelectWidget(widgets.Select):
 def __init__(self, rel, attrs=None):
 self.rel = rel
 super(OwnerSelectWidget, self).__init__(attrs)


 def render(self, name, value, attrs=None):
 key = self.rel.get_related_field().name
 self.choices.field.queryset =
 self.rel.to._default_manager.filter(**{key: value})  <<=== important
 rendered = super(OwnerSelectWidget, self).render(name, value,
 attrs)

 }}}

 When the self.choices.field.queryset assignment is made, it references
 through the !ModelChoiceIterator to the field associated with the widget.
 In the current code base, at this point int the code, the widget has been
 copied, but it still references the original !ModelChoiceIterator, which
 references the !ModelChoiceField that is in base_fields, which references
 the original "base_fields" widget.  This is different than the 'self'
 widget, which is the copied version.  The result is that the
 self.choices.field.queryset assignment updates the wrong widget (the one
 from base_fields) with the new queryset.

 I made a patch to my code that seems to work.  However, I find the patch
 kind of ugly and I suspect someone that understands the code better than
 me might want to do this a different way.  I did two things:
   * Created a __deepcopy__() method for the Select widget, which does the
 same thin that Widget::__deepcopy__() does, but also calls copy on the
 self.choices field
   * Created a small loop that follows the deepcopy in BaseForm:__init__(),
 which runs through all fields that were copied, and if the field contains
 a'widget' attribute and  that widget attribute contains a 'choices'
 attribute and that 'choices' attribute contains a 'field' attribute, then
 it sets that 'field' attribute point to the newly copied field.  This is
 the part that I think is pretty ugly.

 The attached svn diff shows the patch.

 I ran the django testsuite with the command ./runtests.py
 --settings=settings and all tests passed and I have verified via my own
 debugging that this solves my problem.
 }}}

-- 
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] #10966: Management module imports project_module, considered evil

2009-05-22 Thread Django 
#10966: Management module imports project_module, considered evil
-+--
  Reporter:  patrys  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Comment (by c...@zetaweb.com):

 Discussion here:

   http://groups.google.com/group/django-
 developers/browse_thread/thread/9459e3cc441b47b3

-- 
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] #10966: Management module imports project_module, considered evil

2009-05-22 Thread Django 
#10966: Management module imports project_module, considered evil
-+--
  Reporter:  patrys  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * needs_docs:  0 => 1
  * has_patch:  0 => 1
  * needs_tests:  0 => 1

-- 
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] #10966: Management module imports project_module, considered evil

2009-05-22 Thread Django 
#10966: Management module imports project_module, considered evil
-+--
  Reporter:  patrys  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by c...@zetaweb.com):

  * needs_better_patch:  => 0
  * version:  1.0 => SVN
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I agree. I would like to use a Django project directory as the top-level
 directory for a website on the filesystem, but on the other hand I like to
 use the domain name of a website as its directory name. Domain names are
 not valid Python identifiers, so I can't have it both ways without hacking
 Django.

 This behavior is also present on trunk.

-- 
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] #11107: ManyToManyFields defined with keyword 'through' should not be manipulated as auto-generated m2m tables.

2009-05-22 Thread Django 
#11107: ManyToManyFields defined with keyword 'through' should not be 
manipulated
as auto-generated m2m tables.
---+
  Reporter:  j...@sdf.lonestar.org  | Owner:  jcd
Status:  assigned  | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Ready for checkin | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by jcd):

 Cool.  It also doesn't break anything on mysql, FWIW.

-- 
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] #11182: Wrong link in admin page

2009-05-22 Thread Django 
#11182: Wrong link in admin page
---+
  Reporter:  ericsk| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Dupe of #10061.  Please search before opening a new 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
-~--~~~~--~~--~--~---

[Django] #11182: Wrong link in admin page

2009-05-22 Thread Django 
#11182: Wrong link in admin page
--+-
 Reporter:  ericsk|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In the admin page, the change password and logout link are wrong.
 For example, the logout link should be /admin/logout, however the current
 source generates `/admin/admin/logout`

-- 
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] #11181: Make save faster

2009-05-22 Thread Django 
#11181: Make save faster
+---
  Reporter:  novalis| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Honza_Kral):

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

Comment:

 Constructing a queryset every {{{save()}}} (which your patch doesn't
 avoid) is not such an expensive operation that it would require caching.

 If you feel the need to do this in your model, do it in your {{{save}}}
 method and use the outcome to set {{{force_insert}}} or
 {{{force_update}}}.

-- 
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] #11180: django.contrib.comments/django.contrib.sites/django.contrib.admin don't cooperate on site_id

2009-05-22 Thread Django 
#11180: django.contrib.comments/django.contrib.sites/django.contrib.admin don't
cooperate on site_id
--+-
  Reporter:  jl6  | Owner:  nobody
Status:  closed   | Milestone:  1.1   
 Component:  django.contrib.comments  |   Version:  SVN   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

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

Comment:

 This is what the setting, {{{ SITE_ID }}} is for.  Please don't use the
 ticket tracker for asking support questions, use either #django on
 freenode, or the django-users mailing list.

-- 
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] #11181: Make save faster

2009-05-22 Thread Django 
#11181: Make save faster
---+
 Reporter:  novalis|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Save presently does a bunch of work each time to set up a manager for
 update.  This can be cached.  A patch is attached.

-- 
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] #11175: Automatic template inheritance

2009-05-22 Thread Django 
#11175: Automatic template inheritance
+---
  Reporter:  Denis Martinez   | 
Owner:  nobody
Status:  closed | 
Milestone:
 Component:  Uncategorized  |   
Version:  1.0   
Resolution:  wontfix|  
Keywords:
 Stage:  Unreviewed | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 This templatetag is impossible, neither the context nor the tag knows the
 name of the template being rendered.

-- 
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] #11175: Automatic template inheritance

2009-05-22 Thread Django 
#11175: Automatic template inheritance
+---
  Reporter:  Denis Martinez   | 
Owner:  nobody
Status:  new| 
Milestone:
 Component:  Uncategorized  |   
Version:  1.0   
Resolution: |  
Keywords:
 Stage:  Unreviewed | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Denis):

 This tag should exist at least for convenience; if you don't like it, you
 don't have to use it.

 If the functionality is correctly implemented, I don't know what kind of
 errors you're thinking about.
 The django code can (should) make sure that recursion problems will never
 happen.

 Your solution seems hackish to me, possibly more error-prone. In this case
 you are imposing a restriction on the parent directory's name, that we
 have to take in consideration when deploying on multiple servers.

-- 
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] #11180: django.contrib.comments/django.contrib.sites/django.contrib.admin don't cooperate on site_id

2009-05-22 Thread Django 
#11180: django.contrib.comments/django.contrib.sites/django.contrib.admin don't
cooperate on site_id
---+
   Reporter:  jl6  |Owner:  nobody
 Status:  new  |Milestone:  1.1   
  Component:  django.contrib.comments  |  Version:  SVN   
   Keywords:   |Stage:  Unreviewed
  Has_patch:  0|   Needs_docs:  0 
Needs_tests:  0|   Needs_better_patch:  0 
---+
 I'm not certain what the underlying cause of this issue is, or whether the
 summary above is an accurate diagnosis, but this is what happens:

 1. Install django.contrib.sites
 2. Create a Site.
 3. Delete it.
 4. Install django.contrib.comments
 5. Leave a comment using a comment form.
 6. The comments don't show up in the admin.

 I noticed that each comment was given site_id "1", even though that site
 had been deleted. Adding a new site, and changing its id directly in the
 database, was enough to "solve" this (i.e. the comments now show up in the
 admin).

-- 
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] #11175: Automatic template inheritance

2009-05-22 Thread Django 
#11175: Automatic template inheritance
+---
  Reporter:  Denis Martinez   | 
Owner:  nobody
Status:  new| 
Milestone:
 Component:  Uncategorized  |   
Version:  1.0   
Resolution: |  
Keywords:
 Stage:  Unreviewed | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by dc):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I think that implicity will lead to many strange errors.

 Better add parent dir to the TEMPLATE_DIRS and use
 {{{
 {% extends "base_template/index.html" %}
 {% block test %}{{block.super}}. It works!{% endblock %}
 }}}
 in derived_template/index.html

-- 
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] #11179: inspectdb should guess related_name on foreign keys

2009-05-22 Thread Django 
#11179: inspectdb should guess related_name on foreign keys
---+
 Reporter:  3gun   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py inspectdb  | Version:  1.0   
 Keywords:  related_name   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 It would be useful if inspectdb would guess related_name parameter on
 foreign keys using db_table, db_column and othermodel attributes.

 >> Accessor for field 'xxx' clashes with related field 'YYY.zzz_set'. Add
 a related_name argument to the definition for 'xxx'.
 >> Accessor for field 'aaa' clashes with related field 'YYY.zzz_set'. Add
 a related_name argument to the definition for 'aaa'.

 Thnx

-- 
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] #11177: widget attributes

2009-05-22 Thread Django 
#11177: widget attributes
-+--
  Reporter:  fback   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dc):

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

Comment:

 Use  which is
 valid HTML, XHTML and works with Django forms.

-- 
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] #10427: Bound field needs an easy way to get form value

2009-05-22 Thread Django 
#10427: Bound field needs an easy way to get form value
---+
  Reporter:  toxik | Owner:  nobody  
Status:  reopened  | Milestone:  
 Component:  Forms |   Version:  SVN 
Resolution:|  Keywords:  form field value
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by gabor):

 * cc: ga...@nekomancer.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] #11178: django.contrib.auth.views.login doesn't pass request to AuthenticationForm

2009-05-22 Thread Django 
#11178: django.contrib.auth.views.login doesn't pass request to 
AuthenticationForm
-+--
  Reporter:  Florian Reinhard   |  
   Owner:  nobody
Status:  new | 
Milestone:  1.1   
 Component:  Authentication  |  
 Version:  SVN   
Resolution:  |  
Keywords:
 Stage:  Unreviewed  | 
Has_patch:  1 
Needs_docs:  0   |   
Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Florian Reinhard ):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Authentication
  * 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
-~--~~~~--~~--~--~---

[Django] #11178: django.contrib.auth.views.login doesn't pass request to AuthenticationForm

2009-05-22 Thread Django 
#11178: django.contrib.auth.views.login doesn't pass request to 
AuthenticationForm
+---
 Reporter:  Florian Reinhard   |   Owner:  
nobody
   Status:  new |   Milestone:  
1.1   
Component:  Uncategorized   | Version:  
SVN   
 Keywords:  |   Stage:  
Unreviewed
Has_patch:  1   |  
+---
 as long as request isn't passed to
 django.contrib.auth.forms.AuthenticationForm you won't get an error for
 users with cookies disabled.

-- 
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] #11177: widget attributes

2009-05-22 Thread Django 
#11177: widget attributes
---+
 Reporter:  fback  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 There are at least two attributes (disabled and readonly, anything else?)
 for misc. form fields that don't have parameter. Because attrs is a
 dictionary, every key needs a value. When value is set to None, it finally
 renders to {{{attribute="None"}}}:

 There should be a way to pass attributes without value (maybe using None
 as a value?). Current e.g. {{{}}} works under every browser I was able to test, but it
 doesn't change the fact it's not valid html.

-- 
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] #2443: Add IntervalField to database models

2009-05-22 Thread Django 
#2443: Add IntervalField to database models
---+
  Reporter:  ben.tuc...@gmail.com  | Owner:  Gulopine   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
IntervalField interval duration DurationField
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by Adys):

 Any feedback on the DurationField patch? I still need to figure out the
 admin output.

-- 
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] #11173: Updating some spanish translation. (Months and days translation)

2009-05-22 Thread Django 
#11173: Updating some spanish translation. (Months and days translation)
---+
  Reporter:  meaksh| Owner:  meaksh 
   
Status:  closed| Milestone: 
   
 Component:  Translations  |   Version:  1.0
   
Resolution:  invalid   |  Keywords:  months, days, day, month, 
spanish, translation
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by telenieko):

 The right thing to do here would be to ensure that the "|capfirs"t filter
 is used when month names appear at the beggining of sentences, etc. So all
 those Latin languages could benefit from proper casing.

 That's not only with months but also other things like weekdays, even
 places as not *all* place names are uppercased (at least in Spanish). Only
 Countries.

 But that's a story for another 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] #10327: Pass document.domain to popup windows in admin

2009-05-22 Thread Django 
#10327: Pass document.domain to popup windows in admin
---+
  Reporter:  jcassee   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by jcassee):

 Replying to [comment:5 s.federici]:
 > Patches proposed breaks the Admin ForingnKey javascript
 (/media/js/admin/RelatedObjectLookups.js)
 Funny, the patch was supposed to ''fix'' the admin !ForeignKey problem.
 I'll look into it, thanks for the heads-up.

 > I have changed my prospectives, all static resources affected by this
 bug, for the "Same origin policy", will be served by central site.
 Sorry, I don't really understand this sentence.

-- 
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] #11176: add user brocken, if TEMPLATE_STRING_IF_INVALID != ""

2009-05-22 Thread Django 
#11176: add user brocken, if TEMPLATE_STRING_IF_INVALID != ""
---+
  Reporter:  jedie | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jedie):

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

Comment:

 Sorry, dup of #9051, #5532, #4279, and #3579

-- 
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] #11176: add user brocken, if TEMPLATE_STRING_IF_INVALID != ""

2009-05-22 Thread Django 
#11176: add user brocken, if TEMPLATE_STRING_IF_INVALID != ""
--+-
 Reporter:  jedie |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In the django admin panel is the "add user" view broken, if
 settings.TEMPLATE_STRING_IF_INVALID is not empty.

 The view used template '''admin/auth/user/add_form.html''' this file used
 '''{% extends "admin/change_form.html" %}''' In this file the form would
 be insert with:

 {{{
 http://code.djangoproject.com/ticket/11176>
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] #11175: Automatic template inheritance

2009-05-22 Thread Django 
#11175: Automatic template inheritance
---+
 Reporter:  Denis Martinez   |   Owner:  nobody   
 
   Status:  new|   Milestone:   
 
Component:  Uncategorized  | Version:  1.0  
 
 Keywords: |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 Sometimes I have templates in my framework that I would like to override
 (Satchmo for example).

 So I copy the .html in my template directory.
 The drawback is that I can't create a template.html in my project and
 extend with {% extends "template.html" %}, because that would mean
 recursive includes.

 Copying is bad for maintainability and it duplicates template code. So I
 suggest a templatetag {% autoextends %} that would search the next
 template directories for a template to extend, with the same filename.
 Like so:

 base_template/index.html:
 {{{
 {% block test %}Test{% endblock %}
 }}}

 derived_template/index.html:
 {{{
 {% autoextends %}
 {% block test %}{{block.super}}. It works!{% endblock %}
 }}}

-- 
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] #10327: Pass document.domain to popup windows in admin

2009-05-22 Thread Django 
#10327: Pass document.domain to popup windows in admin
---+
  Reporter:  jcassee   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by s.federici):

  * needs_better_patch:  0 => 1

Comment:

 Patches proposed breaks the Admin ForingnKey javascript
 (/media/js/admin/RelatedObjectLookups.js)

 I have changed my prospectives, all static resources affected by this bug,
 for the "Same origin policy", will be served by central site.

-- 
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] #11173: Updating some spanish translation. (Months and days translation)

2009-05-22 Thread Django 
#11173: Updating some spanish translation. (Months and days translation)
---+
  Reporter:  meaksh| Owner:  meaksh 
   
Status:  closed| Milestone: 
   
 Component:  Translations  |   Version:  1.0
   
Resolution:  invalid   |  Keywords:  months, days, day, month, 
spanish, translation
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by meaksh):

  * status:  assigned => closed
  * resolution:  => invalid

Comment:

 Ok, that true!

 After a little research I found this page from "Official Real Academy of
 Spanish Language"
 
(http://www.rae.es/rae/gestores/gespub18.nsf/(voAnexos)/arch8100821B76809110C12571B80038BA4A/$File/CuestionesparaelFAQdeconsultas.htm#ap32)
 where this case is described and say that months, days and seasons are
 lowercase (except when puntuations requires uppercase)

 I'm spanish and the reason for this ticket was that here in Spain this
 language rule is not use for everyone. The people use lower and upper in
 this cases without following any rule.

 Excuse me for this confusion. I turn the ticket to "invalid".

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