Re: [Django] #12028: Generic Inline doesn't validate unique_together

[Django]

#12028: Generic Inline doesn't validate unique_together
---+
  Reporter:  diverman  | Owner: 
 
Status:  new   | Milestone: 
 
 Component:  Contrib apps  |   Version:  SVN
 
Resolution:|  Keywords:  content type generic 
inline unique validation formset admin modeladmin model
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by cmarrero):

 this bug is still open, anyone on 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-upda...@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] #3400: Support for lookup separator with list_filter admin option

[Django]

#3400: Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  DrMeers
 
Status:  assigned  | Milestone:  1.3
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by DrMeers):

  * owner:  jakub_vysoky => DrMeers
  * needs_better_patch:  1 => 0
  * status:  new => assigned
  * needs_tests:  1 => 0

Comment:

 OK, here is my draft patch. I have not tested it thoroughly; there may
 still be a few issues to smooth out, so test-drivers would be appreciated.

 A few notes:

 * Reverse relationships work
 * You can now use any field path that search_filters will accept
 * I have removed the strict validation in favour of letting
 setup_joins catch any issues, as search_fields does. We could perhaps look
 at adding admin validation for field paths for both instead.
 * I played around with combining multiple limit_choices_to clauses
 based on the models in the field path, however discovered that in practise
 it really doesn't make sense to apply any before the final model in the
 field path
 * limit_choices_to is respected for AllValuesFilterSpec, and a utility
 function is provided if other filterspecs wish to do likewise
 * There are some basic tests included in the patch

-- 
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-upda...@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] #14082: modelform_factory should use the form's metaclass

[Django]

#14082: modelform_factory should use the form's metaclass
+---
   Reporter:  jspiros   |   
 Owner:  nobody
 Status:  new   |
Milestone:
  Component:  Forms |  
Version:  SVN   
   Keywords:  ModelForm, ModelFormMetaclass, modelform_factory  |   
 Stage:  Unreviewed
  Has_patch:  1 |   
Needs_docs:  0 
Needs_tests:  1 |   
Needs_better_patch:  0 
+---
 Currently, django.forms.models.modelform_factory always uses
 ModelFormMetaclass to create the returned form class, even in cases when
 the provided form class has specified its own metaclass. I've attached a
 patch which fixes this. Even though __metaclass__ will always be set for
 ModelForm subclasses, I retained the default functionality should there
 have been a case where a form class without a metaclass was provided to
 modelform_factory.

-- 
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-upda...@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] #14078: Template tag to set context variable to output from tag's rendered content

[Django]

#14078: Template tag to set context variable to output from tag's rendered 
content
--+-
  Reporter:  mitar| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by ericholscher):

 This is essentially a duplicate of #6378 -- I'm wondering if that one
 should be closed as wontfix as well? It was included on the 1.2 feature
 list as a "low priority":
 http://code.djangoproject.com/wiki/Version1.2Features#Lowpriority

-- 
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-upda...@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] #14081: Tutorial 3, when 'decoupling', leaves apparently redundant code

[Django]

#14081: Tutorial 3, when 'decoupling',  leaves apparently redundant code
+---
  Reporter:  nickd  | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  1.2 
Resolution:  duplicate  |  Keywords:  Tutorial
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by lrekucki):

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

Comment:

 Yet another duplicate of #3941.

-- 
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-upda...@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] #14081: Tutorial 3, when 'decoupling', leaves apparently redundant code

[Django]

#14081: Tutorial 3, when 'decoupling',  leaves apparently redundant code
---+
 Reporter:  nickd  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords:  Tutorial   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 at the end of tutorial 3:
 http://docs.djangoproject.com/en/dev/intro/tutorial03/#decoupling-the-
 urlconfs

 It talks about 'decoupling' the poll-app from the base site. After moving
 the URLconf to the app, it leaves in the code:

 {{{urlpatterns = patterns('mysite.polls.views'}}}

 This still leaves it coupled to the base site installation (and every app
 you use would need to be tailored to this). Changing this to use just an
 app-relative reference i.e.

 {{{urlpatterns = patterns('polls.views',}}}

 appears to work fine, and achieves the decoupling from the base project.
 Either this is deliberate, and unexplained, or unintentional.

-- 
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-upda...@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] #717: If-Modified-Since checked for exact match

[Django]

#717: If-Modified-Since checked for exact match
--+-
  Reporter:  Maniac   | Owner:  
adrian   
Status:  closed   | Milestone:  
 
 Component:  HTTP handling|   Version:  
 
Resolution:  wontfix  |  Keywords:  
http middleware conditional get if-modified-since
 Stage:  Unreviewed   | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  1   
 
Needs_better_patch:  0|  
--+-
Changes (by lrekucki):

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

Comment:

 Django's policy is that you shouldn't reopen tickets resolved as "won't
 fix" without prior discussion on django-developers mailing list. Please
 post there describing why this ticket should be accepted. It's also a good
 idea to describe problem with current behavior in more detail.

-- 
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-upda...@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] #14080: Flatpages pt-br translation

[Django]

#14080: Flatpages pt-br translation
--+-
 Reporter:  canassa   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The FlatPage model from django.contrib.flatpages is being translated as
 "Páginas planas" when using the 'pt-br' language code. This translation is
 incorrect, it should be "Páginas estáticas" instead.

 References:[[BR]]
  *
 
[http://pt.wikipedia.org/wiki/Servidor_web#P.C3.A1ginas_Din.C3.A2micas_e_P.C3.A1ginas_Est.C3.A1ticas][[BR]]
  * [http://en.wikipedia.org/wiki/Static_web_page]

-- 
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-upda...@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] #717: If-Modified-Since checked for exact match

[Django]

#717: If-Modified-Since checked for exact match
--+-
  Reporter:  Maniac   | Owner:  
adrian   
Status:  reopened | Milestone:  
 
 Component:  HTTP handling|   Version:  
 
Resolution:   |  Keywords:  
http middleware conditional get if-modified-since
 Stage:  Unreviewed   | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  1   
 
Needs_better_patch:  0|  
--+-
Changes (by julianb):

  * status:  closed => reopened
  * component:  django.contrib.admin => HTTP handling
  * needs_tests:  0 => 1
  * keywords:  => http middleware conditional get if-modified-since
  * has_patch:  0 => 1
  * resolution:  wontfix =>

Comment:

 After 5 years, I propose we tackle this. Currently it's not in line with
 the RFC (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).

 I have observed Google to often check with a newer Last-Modified date, and
 Django replying with "Oh, sure it got modified, but long time before what
 you ask, here's the resource anyways: 200 OK"

-- 
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-upda...@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] #9015: Signal Connection Decorators

[Django]

#9015: Signal Connection Decorators
+---
  Reporter:  zvoase | Owner:  brosner
Status:  assigned   | Milestone: 
 Component:  Core framework |   Version:  SVN
Resolution: |  Keywords:  signals
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by jezdez):

 Removed the needs tests and docs flags referring to brosner's patch.

-- 
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-upda...@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] #9015: Signal Connection Decorators

[Django]

#9015: Signal Connection Decorators
+---
  Reporter:  zvoase | Owner:  brosner
Status:  assigned   | Milestone: 
 Component:  Core framework |   Version:  SVN
Resolution: |  Keywords:  signals
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jezdez):

  * needs_docs:  1 => 0
  * needs_tests:  1 => 0
  * stage:  Accepted => Ready for checkin

-- 
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-upda...@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] #14078: Template tag to set context variable to output from tag's rendered content

[Django]

#14078: Template tag to set context variable to output from tag's rendered 
content
--+-
  Reporter:  mitar| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by mitar):

 I agree that view logic should not be put in the template. But designing
 HTML and injecting translation to be used in other blocks does belong to
 template language.

 Maybe it would be enough to extend `blocktrans` tag with `{% blocktrans as
 var_name with ... %}` where translated string would be put into context?
 This is in fact the problem I am trying to solve with my tag, I just
 generalized it also to other situations.

-- 
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-upda...@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] #13679: ModelForms (and hence the admin) no longer honor the default value for a ForeignKey

[Django]

#13679: ModelForms (and hence the admin) no longer honor the default value for a
ForeignKey
-+--
  Reporter:  3point2 | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by 3point2):

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

Comment:

 i've attached a simple test case: it's a tarball of a django project
 called modelform, which contains an app called testing.

 the only files i've modified from the defaults created by "django-admin.py
 startproject" and "./manage.py startapp" are settings.py (db is set to
 sqlite), models.py, and tests.py.

 running "./manage.py test" passes under django 1.1.1 and fails under 1.1.2
 and 1.2.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-upda...@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] #14078: Template tag to set context variable to output from tag's rendered content

[Django]

#14078: Template tag to set context variable to output from tag's rendered 
content
--+-
  Reporter:  mitar| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.2   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 This kind of tag has been omitted from django's template language on
 purpose. Django's template language is not intended to be a Turing
 complete programming language; a "set variable" tag only serves to
 encourage the introduction of view logic into the template (where it
 doesn't belong).

-- 
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-upda...@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] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by 3point2):

 just wanted to +1 this, I think it would be a powerful feature (and I have
 a current need for 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-upda...@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] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by 3point2):

 * cc: 3point2 (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-upda...@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.