Re: [Django] #14099: modelformset not using _should_delete_form

[Django]

#14099: modelformset not using _should_delete_form
+---
   Reporter:  kenth | Owner:  nobody   
 Status:  new   | Milestone:   
  Component:  Forms |   Version:  SVN  
 Resolution:|  Keywords:  sprintSep2010
   Triage Stage:  Accepted  | Has patch:  1
Needs documentation:  0 |   Needs tests:  1
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


Comment:

 This isn't RFC. It doesn't contain any tests.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13577: New Polish L10N formats file

[Django]

#13577: New Polish L10N formats file
+---
   Reporter:  ludwik| Owner:  lrekucki
 Status:  new   | Milestone:  1.3 
  Component:  Translations  |   Version:  1.2 
 Resolution:|  Keywords:  
   Triage Stage:  Accepted  | Has patch:  1   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  1 |  
+---
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1


Comment:

 FYI - The only thing holding this back from 1.3 is a consensus on the
 right solution. The patch is still using a dot; discussion seems to
 suggest that Polish standards indicate a nonbreakable space is
 appropriate.

 If someone can resolve this discussion (and update the patch if required),
 please mark RFC and I'll commit.

-- 
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] #14768: es-MX locale, formats.py contribution

[Django]

#14768: es-MX  locale, formats.py contribution
--+-
   Reporter:  bautvill@…  | Owner:  nobody 
 Status:  new | Milestone:  1.3
  Component:  Translations|   Version:  1.2
 Resolution:  |  Keywords:  locale es es-MX
   Triage Stage:  Ready for checkin   | Has patch:  0  
Needs documentation:  0   |   Needs tests:  0  
Patch needs improvement:  0   |  
--+-
Changes (by russellm):

  * 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-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] #15227: Updated Slovenian localization

[Django]

#15227: Updated Slovenian localization
-+--
   Reporter:  gasperzejn | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Translations   |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => 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-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] #15228: TEMPLATE_STRING_IF_INVALID breaks admin

[Django]

#15228: TEMPLATE_STRING_IF_INVALID breaks admin
+---
   Reporter:  CarlFK| Owner:  nobody  
 Status:  closed| Milestone:  
  Component:  django.contrib.admin  |   Version:  1.3-beta
 Resolution:  duplicate |  Keywords:  
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by mattmcc):

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


Comment:

 Yes, it does break the admin.  This is documented behavior, but #3579
 tracks resolving the dependency.

-- 
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] #15228: TEMPLATE_STRING_IF_INVALID breaks admin (was: admin/.../password/template_error)

[Django]

#15228: TEMPLATE_STRING_IF_INVALID breaks admin
+---
   Reporter:  CarlFK| Owner:  nobody  
 Status:  new   | Milestone:  
  Component:  django.contrib.admin  |   Version:  1.3-beta
 Resolution:|  Keywords:  
   Triage Stage:  Unreviewed| Has patch:  0   
Needs documentation:  0 |   Needs tests:  0   
Patch needs improvement:  0 |  
+---
Changes (by CarlFK):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * component:  Authentication => django.contrib.admin
  * needs_tests:  => 0


Comment:

 in my settings.py:

 TEMPLATE_STRING_IF_INVALID = 'template_error'

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15228: admin/.../password/template_error

[Django]

#15228: admin/.../password/template_error
+---
 Reporter:  CarlFK  |  Owner:  nobody
   Status:  new |  Milestone:
Component:  Authentication  |Version:  1.3-beta  
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 stock django user auth, trying to change password = error.

 http://localhost:8080/admin/auth/user/1/
 "Use '[algo]$[salt]$[hexdigest]' or use the _change password form_"  click
 abcabc click done:

 RuntimeError at /admin/auth/user/1/password/template_error

 You called this URL via POST, but the URL doesn't end in a slash and you
 have APPEND_SLASH set. Django can't redirect to the slash URL while
 maintaining POST data. Change your form to point to
 localhost:8080/admin/auth/user/1/password/template_error/ (note the
 trailing slash), or set APPEND_SLASH=False in your Django settings.

-- 
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] #15227: Updated Slovenian localization

[Django]

#15227: Updated Slovenian localization
--+-
 Reporter:  gasperzejn|  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  Translations  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Hi,

 attached is a diff of a modified django/conf/locale/sl/formats.py against
 r15432 (current trunk).


 Slovenian Django users would be delighted to see it included in Django 1.3
 release.

 Kind regards,
 Gasper Zejn

-- 
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] #14711: MonthMixin.get_previous_month incorrect under certain conditions

[Django]

#14711: MonthMixin.get_previous_month incorrect under certain conditions
-+--
   Reporter:  msundstr   | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Generic views  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by julien):

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

[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
   Triage Stage:  Accepted  | Has patch:  0 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---
Changes (by rupa108):

 * cc: rupa108 (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] #15220: replace SelectFilter2.js with a jQuery plugin

[Django]

#15220: replace SelectFilter2.js with a jQuery plugin
+---
   Reporter:  slurms| Owner:  slurms
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---

Comment (by slurms):

 I think {{{ BoundField }}} has an {{{ auto_id }}} property but I'm not
 sure how to go about using it, so I'm hoping the approach I took was ok
 (using {{{ attrs.get('id', 'id_%s' % name) }}}).

-- 
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] #13376: Messages should have an "expire" flag

[Django]

#13376: Messages should have an "expire" flag
--+-
   Reporter:  ryanshow@…  | Owner:  marekw2143  
 Status:  assigned| Milestone:  
  Component:  Contrib apps|   Version:  1.2-beta
 Resolution:  |  Keywords:  messages, expire
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  0   
Patch needs improvement:  0   |  
--+-
Changes (by bpeschier):

  * has_patch:  0 => 1


Comment:

 Pretty substantial patch, looks good at first sight, might take a deeper
 look 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-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] #12460: inspectdb and field names ending with underscores

[Django]

#12460: inspectdb and field names ending with underscores
--+-
   Reporter:  3gun| Owner:  
nobody
 Status:  new | Milestone:  
  
  Component:  django-admin.py inspectdb   |   Version:  
1.1   
 Resolution:  |  Keywords:  
inspectdb underscore characters digits
   Triage Stage:  Accepted| Has patch:  
1 
Needs documentation:  0   |   Needs tests:  
1 
Patch needs improvement:  0   |  
--+-
Changes (by ramiro):

  * 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] #15226: SelectDateWidget always renders label associated with the month field

[Django]

#15226: SelectDateWidget always renders label associated with the month field
+---
   Reporter:  ramiro| Owner:  nobody
 Status:  new   | Milestone:
  Component:  Forms |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Description changed by ramiro:

Old description:

> A small one: This widget has the ability to layout the three select HTML
> controls ordered according to the locale DATE_FORMAT when USE_I10N is in
> use.
>
> The [X]HTML LABEL tag for is rendered always associated with the month
> select control even when USE_I10N=True and a format spec/locale where
> month doesn't come first as in English is in use.

New description:

 A small one: This widget has the ability to layout the three select HTML
 controls ordered according to the locale DATE_FORMAT when USE_L10N is in
 use.

 The [X]HTML LABEL tag for is rendered always associated with the month
 select control even when USE_L10N=True and a format spec/locale where
 month doesn't come first as in English is in use.

--

-- 
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] #15226: SelectDateWidget always renders label associated with the month field

[Django]

#15226: SelectDateWidget always renders label associated with the month field
--+-
   Reporter:  ramiro  | Owner:  nobody  
 Status:  new | Milestone:  
  Component:  Forms   |   Version:  SVN 
   Keywords:  |  Triage Stage:  Accepted
  Has patch:  0   |   Needs documentation:  0   
Needs tests:  0   |   Patch needs improvement:  0   
--+-
 A small one: This widget has the ability to layout the three select HTML
 controls ordered according to the locale DATE_FORMAT when USE_I10N is in
 use.

 The [X]HTML LABEL tag for is rendered always associated with the month
 select control even when USE_I10N=True and a format spec/locale where
 month doesn't come first as in English is in use.

-- 
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] #15053: [patch] Make templates more reusable by Improving template loading algorithm to avoid extending infinite recursion

[Django]

#15053: [patch] Make templates more reusable by Improving template loading
algorithm to avoid extending infinite recursion
---+
   Reporter:  pmartin  | Owner:  nobody
 Status:  reopened | Milestone:
  Component:  Template system  |   Version:  1.2   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+

Comment (by pmartin):

 Sorry for the delay. Here is the [attachment:patch.15426.diff patch] to
 the revision 15426 of trunk. I hope you like it.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15220: replace SelectFilter2.js with a jQuery plugin

[Django]

#15220: replace SelectFilter2.js with a jQuery plugin
+---
   Reporter:  slurms| Owner:  slurms
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---

Comment (by slurms):

 The instantiation code could probably be a bit cleaner without the
 anonymous function, but it won't change it too much. It was mostly to
 avoid typing django.jQuery(etc..) twice (once for the document.ready and a
 second time for invoking the plugin)..

 I'll upload a patch to fix the TODO shortly. Cheers.

-- 
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] #14986: TestCase: increase verbosity for TestCase.fixtures usage

[Django]

#14986: TestCase: increase verbosity for TestCase.fixtures usage
-+--
   Reporter:  carsten| Owner:  nobody  
 Status:  closed | Milestone:  
  Component:  Testing framework  |   Version:  1.2 
 Resolution:  wontfix|  Keywords:  fixtures
   Triage Stage:  Unreviewed | Has patch:  0   
Needs documentation:  0  |   Needs tests:  0   
Patch needs improvement:  0  |  
-+--

Comment (by Darius Damalakas ):

 Here's an exact link to the line:
 
http://code.djangoproject.com/browser/django/trunk/django/test/testcases.py#L589

-- 
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] #14986: TestCase: increase verbosity for TestCase.fixtures usage

[Django]

#14986: TestCase: increase verbosity for TestCase.fixtures usage
-+--
   Reporter:  carsten| Owner:  nobody  
 Status:  closed | Milestone:  
  Component:  Testing framework  |   Version:  1.2 
 Resolution:  wontfix|  Keywords:  fixtures
   Triage Stage:  Unreviewed | Has patch:  0   
Needs documentation:  0  |   Needs tests:  0   
Patch needs improvement:  0  |  
-+--

Comment (by darius.damalakas):

 I just stumbled upon the same issue today. I debugged deep into Django
 internals until i understood how fixtures are loaded by testing system.
 What i realised is that my fixtures where loaded, but as the original
 author said, it did not print the output to console.

 This is pretty confusing for newcomers (bingo, that's me), especially if
 you fall into the scenario, where you deliberately create several fixtures
 in the hope of that some will be loaded.  And then you would see "Multiple
 fixtures ..." warning, but if you leave only single fixture, no messages
 would be printed at all, which had me to scratch head as to why Django
 sees my fixture, but does not install.

 So to sum up, it is an important issue.


 As for actual resolution:
 Everything boils to this line: testcases.py  line 589
 verbosity is explicitly beeing passed as zero.

 I do not know the exact solution for problems pointed by russellm.   At
 the moment i will just change manually verbosity from 0 to 1, which will
 help me learn Django. Hope this info is useful.

-- 
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] #11639: Can't remove prepopulated fields from fieldset in ModelAdmin

[Django]

#11639: Can't remove prepopulated fields from fieldset in ModelAdmin
+---
   Reporter:  leanmeandonothingmachine  | Owner:  nobody
 
 Status:  new   | Milestone:  1.4   
 
  Component:  django.contrib.admin  |   Version:  1.2   
 
 Resolution:|  Keywords:  
sprintnov13
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  1 |   Needs tests:  1 
 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * needs_docs:  0 => 1
  * needs_tests:  0 => 1
  * milestone:  1.3 => 1.4


Comment:

 That's a useful feature, but unfortunately it is too late for 1.3.

-- 
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] #15175: bug when validate chilean national identification number

[Django]

#15175: bug when validate chilean national identification number
--+-
   Reporter:  rvimer  | Owner:  ersame  
   
 Status:  assigned| Milestone:  
   
  Component:  django.contrib.localflavor  |   Version:  SVN 
   
 Resolution:  |  Keywords:  
localflavor
   Triage Stage:  Accepted| Has patch:  1   
   
Needs documentation:  0   |   Needs tests:  0   
   
Patch needs improvement:  0   |  
--+-
Changes (by ersame):

  * owner:  nobody => ersame
  * needs_better_patch:  1 => 0
  * status:  new => assigned
  * needs_tests:  1 => 0


Comment:

 Hi,

 This is my first patch and my hello to django developper.

 It's an easy ticket and I would like to know if I have done it well.

 Regards.

-- 
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] #14895: USE_THOUSAND_SEPARATOR causes error on group admin operations

[Django]

#14895: USE_THOUSAND_SEPARATOR causes error on group admin operations
+---
   Reporter:  Tuttle| Owner:  nobody
 
 Status:  new   | Milestone:  1.3   
 
  Component:  django.contrib.admin  |   Version:  SVN   
 
 Resolution:|  Keywords:  l10n 
localization thousands
   Triage Stage:  Ready for checkin | Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin


Comment:

 Thanks for the suggestion, Russell. This feels much cleaner! :)

-- 
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] #8809: Better error message when can't import url callback

[Django]

#8809: Better error message when can't import url callback
--+-
   Reporter:  TP  | Owner:  nobody   
 Status:  new | Milestone:   
  Component:  Core framework  |   Version:  SVN  
 Resolution:  |  Keywords:  error message
   Triage Stage:  Accepted| Has patch:  1
Needs documentation:  0   |   Needs tests:  1
Patch needs improvement:  1   |  
--+-

Comment (by bpeschier):

 Well, this one makes the information slightly more reliable. When a
 pattern is created without an url()-call, line-information is not reliable
 so it only shows the module. Included a set of tests.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14895: USE_THOUSAND_SEPARATOR causes error on group admin operations

[Django]

#14895: USE_THOUSAND_SEPARATOR causes error on group admin operations
+---
   Reporter:  Tuttle| Owner:  nobody
 
 Status:  new   | Milestone:  1.3   
 
  Component:  django.contrib.admin  |   Version:  SVN   
 
 Resolution:|  Keywords:  l10n 
localization thousands
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * stage:  Ready for checkin => Accepted


Comment:

 This sort of problem is the exact reason that we introduced the unlocalize
 filter. I suspect that this patch is actually pretty close to being RFC,
 mod that little 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-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] #14895: USE_THOUSAND_SEPARATOR causes error on group admin operations

[Django]

#14895: USE_THOUSAND_SEPARATOR causes error on group admin operations
+---
   Reporter:  Tuttle| Owner:  nobody
 
 Status:  new   | Milestone:  1.3   
 
  Component:  django.contrib.admin  |   Version:  SVN   
 
 Resolution:|  Keywords:  l10n 
localization thousands
   Triage Stage:  Ready for checkin | Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin


Comment:

 In this patch, the {{{stringformat}}} template filter forces the id to be
 rendered without USE_THOUSAND_SEPARATOR getting in the way. I'm not sure
 whether it is the most elegant solution though, so you might have a better
 fix to suggest.

 Cheekily RFC'ing so it gets a core dev's attention for 1.3  ;)

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