date:20091214

[Django] #12379: Simplified Chinese(CN) localflavor package

2009-12-14 Thread Django

#12379: Simplified Chinese(CN) localflavor package
+---
 Reporter:  xiaket  |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  django.contrib.localflavor  | Version:  SVN   
 Keywords:  CN localflavor  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 The attached patch contains:

 * CNProvinceSelect - Select widget for Chinese provinces
 * CNPostCodeField - Form field for Chinese post codes
 * CNIDCardField - Form field for Chinese ID Card numbers
 * CNPhoneNumberField - Form field for Chinese regular phone numbers
 * CNCellNumberField - Form field for Chinese cell phone numbers

 Documentation and tests are included!

-- 
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] #3569: extend Atom feed support for other fields

2009-12-14 Thread Django

#3569: extend Atom feed support for other fields
--+-
  Reporter:  jtau...@jtauber.com  | Owner:  nobody
Status:  new  | Milestone:  1.2   
 Component:  RSS framework|   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by kgrandis):

  * owner:  kgrandis => nobody
  * status:  assigned => new

-- 
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] #1105: [patch] simple_tag decorator enhancement

2009-12-14 Thread Django

#1105: [patch] simple_tag decorator enhancement
---+
  Reporter:  dja...@kieranholland.com  | Owner:  julien
Status:  new   | Milestone:
 Component:  Template system   |   Version:
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Comment (by twig):

 i agree with semenov.

 the reason i've found this ticket is because i was looking for a simpler
 way of accessing the context.

-- 
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] #12090: Show admin actions on the edit pages too

2009-12-14 Thread Django

#12090: Show admin actions on the edit pages too
---+
  Reporter:  apollo13  | Owner:  jezdez
Status:  assigned  | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * owner:  nobody => jezdez
  * status:  new => assigned

-- 
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] #10640: Add `add_form_template` option to ModelAdmin

2009-12-14 Thread Django

#10640: Add `add_form_template` option to ModelAdmin
---+
  Reporter:  dcramer   | Owner:  kmtracey
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:  0 |  
---+
Changes (by jcsackett):

  * owner:  jcsackett => kmtracey
  * needs_better_patch:  1 => 0
  * status:  assigned => new
  * needs_docs:  1 => 0

Comment:

 Updated patch includes modified documentation detailing the
 add_form_template and changing the documentation of the
 change_form_template attribute.

 Added the add_form.html template for the tests (forgot to svn add it
 before, kmtracey was right).

 I think this should have everything now.

-- 
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] #7501: template rendering doesn't reset cycle tag

2009-12-14 Thread Django

#7501: template rendering doesn't reset cycle tag
-+--
  Reporter:  mitsuhiko   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Resolved by [11862]

-- 
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] #12199: Give 'firstof' tag ability to assign result to context

2009-12-14 Thread Django

#12199: Give 'firstof' tag ability to assign result to context
--+-
  Reporter:  tiliv| Owner:  nobody  
Status:  new  | Milestone:  1.2 
 Component:  Template system  |   Version:  SVN 
Resolution:   |  Keywords:  firstof, as, context
 Stage:  Unreviewed   | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  1   
Needs_better_patch:  0|  
--+-
Comment (by alexr):

 I worked on this ticket during the sprint on 12/12/09.
 There was initially some concern that this ticket would accomplish the
 same thing as the proposed capture tag. They would do exactly the same
 thing though.

 Jacob is -0 on this ticket since we are making the tag a switch statement,
 but didn't want to veto it without discussion.

-- 
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] #12338: "Overriding predefined model methods": use *args, **kwargs in code sample

2009-12-14 Thread Django

#12338: "Overriding predefined model methods": use *args, **kwargs in code 
sample
+---
  Reporter:  blueyed| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by alexr):

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

Comment:

 I'm going to set this invalid since I think it won't work. Feel free to
 set it back if I am wrong.

-- 
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] #12338: "Overriding predefined model methods": use *args, **kwargs in code sample

2009-12-14 Thread Django

#12338: "Overriding predefined model methods": use *args, **kwargs in code 
sample
+---
  Reporter:  blueyed| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by alexr):

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

Comment:

 I'm not sure that you want to pass through all args and kwargs. If I pass
 anything other than force_insert or force_update to my function then I
 will get TypeError (unexpected keyword argument) when that argument is
 passed into the model's save method. The model's save method doesn't
 accept **kwargs, so passing that to it is asking for trouble.

 Just my 2 cents.
 Alex

-- 
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] #11632: show_hidden_initial=True produces invalid HTML

2009-12-14 Thread Django

#11632: show_hidden_initial=True produces invalid HTML
+---
  Reporter:  ge...@datacollect.com  | Owner:  kmtracey  
 
Status:  closed | Milestone:  1.2   
 
 Component:  Forms  |   Version:  1.1   
 
Resolution:  fixed  |  Keywords:  
show_hidden_initial
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by margieroginski):

 Replying to [comment:9 mlavin]:
 > While it's a shame that it doesn't help your jQuery selector I think
 using the 'initial-' prefix is a consistent with how the field names are
 generated. I added a patch that generates prefix to the id on the hidden
 initial field.  I think as long as it is clear and consistent how the
 names and ids will be generated people can make the rest of their project
 work as far as selecting the elements and not generating conflicting
 names/ids.

 Thanks for putting the patch in, Mark.  I agree that prefixing with
 initial- is a good and consistent fix.

-- 
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] #9475: add(), create(), etc. should be supported by intermedite ManyToMany model with extra attributes if extra fields can be calculated

2009-12-14 Thread Django

#9475: add(), create(), etc. should be supported by intermedite ManyToMany model
with extra attributes if extra fields can be calculated
---+
  Reporter:  o...@gezgin.com   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by anonymous):

 Replying to [comment:9 Travis Cline ]:
 > Replying to [comment:8 emulbreh]:
 > > Replying to [comment:7 Travis Cline ]:
 > > > Attached is an alternate approach. Will also attach a similar
 approach but with an attempt to fall back to a reasonable default.
 > >
 > > I don't believe the flag should be on `Meta`. The intermediary model
 doesn't know which FK fields are used for the m2m relation (at least in
 theory there may be more than one m2m relation through the same model).
 And you would introduce a model option that has no meaning for most
 models.
 >
 > Yeah, you're right. Not nearly the right place for that to live. I hope
 to follow up with a patch that isn't so whack soon.

 What's wrong with `9475.m2m_add_remove.r11739.diff` ?

-- 
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] #11373: Change list layout breaks if no actions_form

2009-12-14 Thread Django

#11373: Change list layout breaks if no actions_form
---+
  Reporter:  manuel_razzari| Owner: 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * owner:  jacob =>

-- 
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] #12017: UKPostcodeField doesn't shows provided custom "error_messages"

2009-12-14 Thread Django

#12017: UKPostcodeField doesn't shows provided custom "error_messages"
-+--
  Reporter:  vmagamedov  | Owner: 
Status:  new | Milestone:  1.2
 Component:  django.contrib.localflavor  |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * owner:  jacob =>

-- 
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] #12059: datetime to time conversion incorrect

2009-12-14 Thread Django

#12059: datetime to time conversion incorrect
---+
  Reporter:  wkornewald| Owner: 
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * owner:  jacob =>

-- 
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] #12102: Relative PYTHONPATH in the docs

2009-12-14 Thread Django

#12102: Relative PYTHONPATH in the docs
+---
  Reporter:  alexkon| Owner: 
Status:  new| Milestone:  1.2
 Component:  Documentation  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * owner:  jacob =>
  * 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-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] #12343: manage.py dbshell fails to launch mysql for unix socket

2009-12-14 Thread Django

#12343: manage.py dbshell fails to launch mysql for unix socket
-+--
  Reporter:  elyon...@gmail.com  | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Uncategorized   |   Version:  1.1  
Resolution:  |  Keywords:  dbshell mysql
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by sfllaw):

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

Comment:

 Here's a simple patch that works for me.  Socket detection should probably
 be better than just testing whether '/' is in the path.

-- 
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] #6623: commit_manually decorator: Better error message (show exception)

2009-12-14 Thread Django

#6623: commit_manually decorator: Better error message (show exception)
---+
  Reporter:  guettli   | Owner:  jacob
Status:  assigned  | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * owner:  nobody => jacob
  * status:  new => assigned

-- 
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] #10640: Add `add_form_template` option to ModelAdmin

2009-12-14 Thread Django

#10640: Add `add_form_template` option to ModelAdmin
---+
  Reporter:  dcramer   | Owner:  jcsackett
Status:  assigned  | Milestone:  1.2  
 Component:  django.contrib.admin  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  1 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by jcsackett):

  * owner:  nobody => jcsackett
  * status:  new => assigned

-- 
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] #5893: FilePathField doesn't support folders

2009-12-14 Thread Django

#5893: FilePathField doesn't support folders
---+
  Reporter:  Alex  | Owner:  Alex   
Status:  new   | Milestone: 
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords:  enhancement
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Comment (by kmtracey):

 Oh, and the doc changes need versionadded flags, don't they?

-- 
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] #5893: FilePathField doesn't support folders

2009-12-14 Thread Django

#5893: FilePathField doesn't support folders
---+
  Reporter:  Alex  | Owner:  Alex   
Status:  new   | Milestone: 
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords:  enhancement
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Changes (by kmtracey):

  * owner:  kmtracey => Alex
  * needs_better_patch:  0 => 1

Comment:

 Hey Alex -- First, the file containing the new test was just converted to
 unit tests.  Can you convert the new test?

 Also I'm not sure about the asserts. For the model field I'd expect that
 contradiction to be be caught during validation. I see there are a couple
 of asserts in that file for auto field stuff, but it seems most errors of
 this sort are caught instead in `get_validation_errors` in
 django/core/management/validate.py. Is there some reason you went with an
 assert here instead?

 For the form field, there are other such nonsensical argument combos that
 we just don't check for.  The user is left with a form that can't ever
 validate (e.g. !IntegerField with max_value lower than min_value), but
 that's what they asked for. Perhaps not as helpful as we could be, but
 using assert to catch invalid arg combos passed into Django just doesn't
 seem to fit in with the rest of the code...is there some reason this case
 is special and should be handled differently than other similar cases?

-- 
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] #12078: ValidationError(s) from specific fields not rendered on admin add/change form

2009-12-14 Thread Django

#12078: ValidationError(s) from specific fields not rendered on admin add/change
form
---+
  Reporter:  Killarny  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  
soc2009/model-validation
Resolution:|  Keywords: 
 
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by Killarny):

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

Comment:

 I opened this ticket two months ago, and it's still labeled "new" and
 "unreviewed". Is anyone watching this branch, or has model validation been
 dropped?

-- 
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] #9475: add(), create(), etc. should be supported by intermedite ManyToMany model with extra attributes if extra fields can be calculated

2009-12-14 Thread Django

#9475: add(), create(), etc. should be supported by intermedite ManyToMany model
with extra attributes if extra fields can be calculated
---+
  Reporter:  o...@gezgin.com   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by Travis Cline ):

 Replying to [comment:8 emulbreh]:
 > Replying to [comment:7 Travis Cline ]:
 > > Attached is an alternate approach. Will also attach a similar approach
 but with an attempt to fall back to a reasonable default.
 >
 > I don't believe the flag should be on `Meta`. The intermediary model
 doesn't know which FK fields are used for the m2m relation (at least in
 theory there may be more than one m2m relation through the same model).
 And you would introduce a model option that has no meaning for most
 models.

 Yeah, you're right. Not nearly the right place for that to live. I hope to
 follow up with a patch that isn't so whack soon.

-- 
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] #11797: Test Client Response content form value parsing

2009-12-14 Thread Django

#11797: Test Client Response content form value parsing
-+--
  Reporter:  Rupe| Owner:  nobody   

Status:  new | Milestone:  1.2  

 Component:  Testing framework   |   Version:  SVN  

Resolution:  |  Keywords:  test client 
content form post get
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by Rupe):

 Replying to [comment:6 rpbarlow]:
 > As per some discussion, it seems to be agreed that we shouldn't try to
 duplicate the functionality of projects like Twill. This patch is parsing
 HTML to get the form data. A more desirable solution is to use the request
 context to get the form. The down side to that approach is that not all
 form elements are always available in the context.

 I understand the concern about overlap though the context side doesn't
 seem to be really viable. In addition to not always having all of the
 elements as you point out (say you have a hard coded hidden field), you
 can also have conditional templates. You would then have to duplicate the
 template conditions in your testing logic and thus not test the template
 logic.

-- 
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] #10640: Add `add_form_template` option to ModelAdmin

2009-12-14 Thread Django

* owner: kmtracey => nobody
* needs_better_patch: 0 => 1
* needs_docs: 0 => 1

Comment:

Replying to [comment:6 jcsackett]:

Sorry I did not get a chance to look at this during the sprint. A couple
of things need to be fixed before this can be checked in. First the new
template file for the test isn't in the patch, so the test fails. To get
`svn diff` to include it you first need to `svn add` the file. (I'm
guessing you used svn based on the patch, but if you're using another vcs
likely you need to do something similar for the diff to pick up the added
file.)

Also, the description of `ModelAdmin.change_form_template` in
docs/ref/contrib/admin/index.txt (online here:

http://docs.djangoproject.com/en/1.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.change_form_template)
needs to be updated to reflect the change, and a new bit need to be added
to describe the new `add_form_tempalte` option.

If you can do both of those, upload a new diff, and update the needs doc
and patch needs improvement flags when its done I'll take another look.

--
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] #12378: Remove redundant test.

2009-12-14 Thread Django

#12378: Remove redundant test.
+---
  Reporter:  anonymous  | Owner:  jcd
Status:  new| Milestone:  1.2
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jcd):

  * has_patch:  0 => 1
  * component:  Uncategorized => Testing framework

-- 
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] #12378: Remove redundant test.

2009-12-14 Thread Django

#12378: Remove redundant test.
+---
  Reporter:  anonymous  | Owner:  jcd
Status:  new| Milestone:  1.2
 Component:  Uncategorized  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jcd):

  * owner:  nobody => jcd
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Oops.  Forgot to log in.  I reported 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.

[Django] #12378: Remove redundant test.

2009-12-14 Thread Django

#12378: Remove redundant test.
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 r11861 fixes #12367, but leaves a test that is now 100% redundant.
 OldAdminForeignKeyWidgetChangeList duplicates
 AdminForeignKeyWidgetChangeList, and urls2.py is only used by
 OldAdminForeignKeyWidgetChangeList.

 This patch removes that test and urlconf file.

-- 
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] #11753: Q objects using callables won't combine in 2.4

2009-12-14 Thread Django

#11753: Q objects using callables won't combine in 2.4
---+
  Reporter:  alexr | Owner:   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.1  
Resolution:|  Keywords:  Q, mq
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * owner:  ramiro =>

-- 
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] #4444: broken pipe issue

2009-12-14 Thread Django

#: broken pipe issue
+---
  Reporter:  vanderkerkoff  | Owner:  nobody
Status:  closed | Milestone:
 Component:  django-admin.py runserver  |   Version:  SVN   
Resolution:  wontfix|  Keywords:  broken pipe 32
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 Take it to the django-developers list, please.

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

[Changeset] r11865 - in django/branches/releases/1.1.X: . django/contrib/admin

2009-12-14 Thread noreply

Author: kmtracey
Date: 2009-12-14 10:05:28 -0600 (Mon, 14 Dec 2009)
New Revision: 11865

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/contrib/admin/options.py
Log:
[1.1.X] Made the message strings added in r11838 visible to makemessages. Refs 
#12281.

r11864 from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11808,11815,11817,11822,11826,11833,11835,11837,11839,11841,11844,11857
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11808,11815,11817,11822,11826,11833,11835,11837,11839,11841,11844,11857,11864

Modified: django/branches/releases/1.1.X/django/contrib/admin/options.py
===
--- django/branches/releases/1.1.X/django/contrib/admin/options.py  
2009-12-14 16:01:43 UTC (rev 11864)
+++ django/branches/releases/1.1.X/django/contrib/admin/options.py  
2009-12-14 16:05:28 UTC (rev 11865)
@@ -690,8 +690,8 @@
 selected = request.POST.getlist(helpers.ACTION_CHECKBOX_NAME)
 if not selected:
 # Reminder that something needs to be selected or nothing will 
happen
-msg = "Items must be selected in order to perform actions on 
them. No items have been changed."
-self.message_user(request, _(msg))
+msg = _("Items must be selected in order to perform actions on 
them. No items have been changed.")
+self.message_user(request, msg)
 return None
 
 response = func(self, request, queryset.filter(pk__in=selected))
@@ -704,8 +704,8 @@
 else:
 return HttpResponseRedirect(".")
 else:
-msg = "No action selected."
-self.message_user(request, _(msg))
+msg = _("No action selected.")
+self.message_user(request, msg)
 
 def add_view(self, request, form_url='', extra_context=None):
 "The 'add' admin view for this model."

--

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.

[Changeset] r11864 - django/trunk/django/contrib/admin

2009-12-14 Thread noreply

Author: kmtracey
Date: 2009-12-14 10:01:43 -0600 (Mon, 14 Dec 2009)
New Revision: 11864

Modified:
   django/trunk/django/contrib/admin/options.py
Log:
Made the message strings added in r11837 visible to makemessages.  Refs #12281.


Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2009-12-14 12:39:20 UTC 
(rev 11863)
+++ django/trunk/django/contrib/admin/options.py2009-12-14 16:01:43 UTC 
(rev 11864)
@@ -693,8 +693,8 @@
 selected = request.POST.getlist(helpers.ACTION_CHECKBOX_NAME)
 if not selected:
 # Reminder that something needs to be selected or nothing will 
happen
-msg = "Items must be selected in order to perform actions on 
them. No items have been changed."
-self.message_user(request, _(msg))
+msg = _("Items must be selected in order to perform actions on 
them. No items have been changed.")
+self.message_user(request, msg)
 return None
 
 response = func(self, request, queryset.filter(pk__in=selected))
@@ -707,8 +707,8 @@
 else:
 return HttpResponseRedirect(".")
 else:
-msg = "No action selected."
-self.message_user(request, _(msg))
+msg = _("No action selected.")
+self.message_user(request, msg)
 
 @csrf_protect
 @transaction.commit_on_success

--

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] #11753: Q objects using callables won't combine in 2.4

2009-12-14 Thread Django

#11753: Q objects using callables won't combine in 2.4
---+
  Reporter:  alexr | Owner:  ramiro
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:  Q, mq 
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by alexr):

 Ramiro,
 (We worked on this feature at a sprint over the weekend.)

 The deepcopy bug is triggered whenever deepcopy tries to copy an object
 that has a function as an attribute. (Deepcopy works with methods, but not
 with unbound function attributes.) All of the test case failures come from
 using a Model instance inside a Q object. Perhaps r11732 somehow added an
 unbound function to model instances? (I looked at that revision, but it
 isn't immediately obvious to me if it might have done that.)

 Adding the whole copy module from 2.6 seemed extreme to me at first. I
 tried modifying Q objects so that the init method changed and function
 arguments into classes with call methods instead. I had that working at
 one point, but it didn't fix the test cases. The model instances had
 callables, but not at the top level. Deepcopy was recursive, so the fix
 would have to recurse over the whole object also. At that point, we had to
 write a function that dynamically made classes (something that didn't
 quite work when we abandoned it) and also recursed over objects, avoiding
 circular refs and such.

 jdunck looked into messing with copy_reg to register a new handler for
 functions. However, functions are one of the standard types, and copy_reg
 doesn't allow you to register new handlers for them.

 In the end, we gave up and just added copy from 2.6. It seemed the
 simplest way to fix the problem.

 Alex

-- 
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] #12376: Nested blocks don't work inside an ifnotequal tag

2009-12-14 Thread Django

#12376: Nested blocks don't work inside an ifnotequal tag
---+
  Reporter:  Manuel Strehl   | Owner:  
nobody  
Status:  closed| Milestone: 
 
 Component:  Template system   |   Version:  
1.1 
Resolution:  duplicate |  Keywords:  
nested block
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

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

Comment:

 Duplicate of #6510.

-- 
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] #4444: broken pipe issue

2009-12-14 Thread Django

#: broken pipe issue
+---
  Reporter:  vanderkerkoff  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  django-admin.py runserver  |   Version:  SVN   
Resolution: |  Keywords:  broken pipe 32
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Loststylus):

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

Comment:

 Hm, but when i test on IE, i have to restart the development server
 periodically, because of the broken pipe error (the browser tries to get
 data, but gets stuck until a reload the server).

 Sorry, for reopening, i just want someone to pay attention to the problem.
 I don't think that server restart is a good idea.

 How should this be handled, anyway?

-- 
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] #373: Add support for multiple-column primary keys

2009-12-14 Thread Django

#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: alexis_m (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.

[Django] #12377: Make the makemessages command more open

2009-12-14 Thread Django

#12377: Make the makemessages command more open
---+
 Reporter:  Renskers   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django-admin.py| Version:  1.1   
 Keywords:  makemessages i18n  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I am using Jinja2 instead of the Django template system in a test project.
 Everything is working fine, but I am running into a small problem
 regarding i18n:

 The command "django-admin makemessages" doesn't find the translation
 strings, because the Jinja2 format differs from the Django format.

 Django syntax:
 {{{
 {% trans "Hello" %}
 {% blocktrans %}Hello{% endblocktrans %}
 }}}

 Jinj2 syntax:
 {{{
 {{ _('Hello') }}
 {% trans %}Hello{% endtrans %}
 }}}

 The underscore syntax work fine, but the trans/endtrans doesn't: the
 regular expressions used by makemessages don't account for different
 template tags. As far as I can see there is no possible way to configure
 the system so it can work with different tags. It seems like a good idea
 to open this up, so different template systems can be used more easily.

-- 
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] #12105: Admin querystring __isnull=False filter doesn't work

2009-12-14 Thread Django

#12105: Admin querystring __isnull=False filter doesn't work
---+
  Reporter:  marcob| Owner:   
Status:  new   | Milestone:  1.2  
 Component:  django.contrib.admin  |   Version:  1.1  
Resolution:|  Keywords:  isnull filter
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by mikepenn):

  * needs_better_patch:  1 => 0
  * needs_tests:  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-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] #12105: Admin querystring __isnull=False filter doesn't work

2009-12-14 Thread Django

#12105: Admin querystring __isnull=False filter doesn't work
---+
  Reporter:  marcob| Owner:   
Status:  new   | Milestone:  1.2  
 Component:  django.contrib.admin  |   Version:  1.1  
Resolution:|  Keywords:  isnull filter
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  1 |  
---+
Changes (by mikepenn):

  * owner:  mikepenn =>
  * needs_better_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-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] #5893: FilePathField doesn't support folders

2009-12-14 Thread Django

#5893: FilePathField doesn't support folders
---+
  Reporter:  Alex  | Owner:  kmtracey   
Status:  new   | Milestone: 
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords:  enhancement
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * owner:  kmtracy => kmtracey

Comment:

 Put this on my list to look at.

-- 
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] #12376: Nested blocks don't work inside an ifnotequal tag

2009-12-14 Thread Django

#12376: Nested blocks don't work inside an ifnotequal tag
--+-
 Reporter:  Manuel Strehl   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Template system   | Version:  1.1   
 Keywords:  nested block  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The blocks inside a 'master' block can't be overwritten, if they are
 inside an {% ifnotequal %} tag (and, I suspect, any other 'if'-like tag,
 too). Consider this master template for basic pagination:

 http://dpaste.com/hold/133172/

 If I want to overwrite {% block pagination_start %}, the extending
 template is ignored alltogether:

 http://dpaste.com/hold/133173/

 which displays exactly the same as the master template.

 Expected Output:

 The rendering should be like the master, but the first and the last list
 item should have vanished.

-- 
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] #9475: add(), create(), etc. should be supported by intermedite ManyToMany model with extra attributes if extra fields can be calculated

2009-12-14 Thread Django

#9475: add(), create(), etc. should be supported by intermedite ManyToMany model
with extra attributes if extra fields can be calculated
---+
  Reporter:  o...@gezgin.com   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by emulbreh):

 Replying to [comment:7 Travis Cline ]:
 > Attached is an alternate approach. Will also attach a similar approach
 but with an attempt to fall back to a reasonable default.

 I don't believe the flag should be on `Meta`. The intermediary model
 doesn't know which FK fields are used for the m2m relation (at least in
 theory there may be more than one m2m relation through the same model).
 And you would introduce a model option that has no meaning for most
 models.

-- 
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] #12375: updating QueryDict in another dict gives unexpected results.

2009-12-14 Thread Django

#12375: updating QueryDict in another dict gives unexpected results.
---+
 Reporter:  hvdklauw   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  HTTP handling  | Version:  1.1   
 Keywords:  QueryDict  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I noticed a small "bug" in the QueryDict.

 When I have an existing dict and want to add the get or postdata to it
 using my_dict.update(request.POST).
 This results in a dict with all the values as lists. I can understand why
 the QueryDict might work that way, the same key could have multiple
 values. Except that the QueryDict
 does some magic that when you iterate over it it returns the first item in
 the list.

 This limitation should be documented, and maybe a function should be added
 to the QueryDict to turn it into a normal dict.

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

[Changeset] r11861 - in django/trunk/tests/regressiontests: admin_widgets generic_inline_admin

2009-12-14 Thread noreply

Author: russellm
Date: 2009-12-14 05:19:40 -0600 (Mon, 14 Dec 2009)
New Revision: 11861

Modified:
   django/trunk/tests/regressiontests/admin_widgets/urls2.py
   django/trunk/tests/regressiontests/generic_inline_admin/urls.py
Log:
Fixed #12367 -- Modified test urls to avoid the DeprecationWarning caused by 
old-style admin inclusions. Thanks to Travis Cline for the patch.

Modified: django/trunk/tests/regressiontests/admin_widgets/urls2.py
===
--- django/trunk/tests/regressiontests/admin_widgets/urls2.py   2009-12-13 
22:15:08 UTC (rev 11860)
+++ django/trunk/tests/regressiontests/admin_widgets/urls2.py   2009-12-14 
11:19:40 UTC (rev 11861)
@@ -3,5 +3,5 @@
 import widgetadmin
 
 urlpatterns = patterns('',
-(r'^deep/down/admin/(.*)', widgetadmin.site.root),
+(r'^deep/down/admin/', include(widgetadmin.site.urls)),
 )

Modified: django/trunk/tests/regressiontests/generic_inline_admin/urls.py
===
--- django/trunk/tests/regressiontests/generic_inline_admin/urls.py 
2009-12-13 22:15:08 UTC (rev 11860)
+++ django/trunk/tests/regressiontests/generic_inline_admin/urls.py 
2009-12-14 11:19:40 UTC (rev 11861)
@@ -2,5 +2,5 @@
 from django.contrib import admin
 
 urlpatterns = patterns('',
-(r'^admin/(.*)', admin.site.root),
+(r'^admin/', include(admin.site.urls)),
 )

--

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] #11753: Q objects using callables won't combine in 2.4

2009-12-14 Thread Django

#11753: Q objects using callables won't combine in 2.4
---+
  Reporter:  alexr | Owner:  ramiro
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:  Q, mq 
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * owner:  => ramiro
  * has_patch:  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-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] #12233: Redirect logged in user

2009-12-14 Thread Django

#12233: Redirect logged in user
+---
  Reporter:  dmathieu   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Authentication |   Version:  1.1 
Resolution: |  Keywords:  authentication,login
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: nieproszeni...@gmail.com (removed)
 * cc: loginzd...@gmail.com (added)

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12233: Redirect logged in user

2009-12-14 Thread Django

#12233: Redirect logged in user
+---
  Reporter:  dmathieu   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Authentication |   Version:  1.1 
Resolution: |  Keywords:  authentication,login
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by nieproszenieja):

 * cc: nieproszeni...@gmail.com (added)

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

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11522: UnicodeEncodeError on redirect to non-ASCII Location

2009-12-14 Thread Django

#11522: UnicodeEncodeError on redirect to non-ASCII Location
+---
  Reporter:  semenov| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  HTTP handling  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Comment (by etzel):

 Got this problem too, any fix would be welcome. I'm going with
 simple_fix.diff for now.

-- 
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] #12372: passing ip to django.contrib.auth.views.password_reset email template

2009-12-14 Thread Django

#12372: passing ip to django.contrib.auth.views.password_reset email template
-+--
  Reporter:  lashni  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

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

Comment:

 I'm unconvinced that this is 'standard' - in the dozens of password reset
 e-mails I've just checked on my computer from the past 5 or 6 years, only
 two included IP address information, and none of the big players like
 Google, Paypal etc.  I certainly would never include it myself, because
 most users are not going to be able to do anything with that information.
 I'd classify it as 'unusual', not 'standard'.

 Backwards compatibility is also tricky.  At the very least, your patch
 would need to use something like `options['request'] = request` rather
 than the current positional argument.  But that would still leave the
 problem of custom `PasswordResetForm` implementations which do not have
 the `request` keyword argument (quite likely if they have followed the
 signature provided by Django).  These would throw an error if they were
 passed one.

 Given the backwards incompatibility, and the dubious usefulness of this
 addition, I'm closing WONTFIX.  (It is possible to work around the
 backward incompatibility by using function signature introspection, but
 it's a complicated addition which does not seem to be worth it for this
 use case).  You will have to provide your own view function as well as
 your own Form, sorry.

-- 
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] #12372: passing ip to django.contrib.auth.views.password_reset email template

2009-12-14 Thread Django

#12372: passing ip to django.contrib.auth.views.password_reset email template
-+--
  Reporter:  lashni  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

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

Comment:

 I'm unconvinced that this is 'standard' - in the dozens of password reset
 e-mails I've just checked on my computer from the past 5 or 6 years, only
 two included IP address information, and none of the big players like
 Google, Paypal etc.  I certainly would never include it myself, because
 most users are not going to be able to do anything with that information.
 I'd classify it as 'unusual', not 'standard'.

 Backwards compatibility is also tricky.  At the very least, your patch
 would need to use something like ``options['request'] = request`` rather
 than the current positional argument.  But that would still leave the
 problem of custom ``PasswordResetForm`` implementations which do not have
 the ``request`` keyword argument (quite likely if they have followed the
 signature provided by Django).  These would throw an error if they were
 passed one.

 Given the backwards incompatibility, and the dubious usefulness of this
 addition, I'm closing WONTFIX.  (It is possible to work around the
 backward incompatibility by using function signature introspection, but
 it's a complicated addition which does not seem to be worth it for this
 use case).  You will have to provide your own view function as well as
 your own Form, sorry.

-- 
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] #12373: Add keepdb option to test command

2009-12-14 Thread Django

#12373: Add keepdb option to test command
+---
  Reporter:  phuihock   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Each test *is* independent and starts with a clean database, which is
 exactly why --keepdb won't work. *All* the test data isn't retained in the
 test db - only the test data *from the last executed test* is retained,
 unless you're running doctests or standard unit tests, in which case it
 gets really messy to determine exactly what will be in the database at the
 end of the test run.

 As for the code that does this: you're looking for
 TransactionTestCase._fixture_setup() and TestCase._fixture_teardown() in
 django.test.testcases.

 If you want to inspect the test db during test execution, I recommend
 setting a debugger breakpoint in the test case you want to inspect.

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

50 matches

Mail list logo