Re: [Django] #12525: ModelForm validation doesn't work like documented

[Django]

#12525: ModelForm validation doesn't work like documented
-+--
  Reporter:  Bernd Schlapsi   | Owner:  nobody   
 
Status:  closed  | Milestone:  1.2  
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  fixed   |  Keywords:  
Validators
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Comment (by korpios):

 Ah, excellent.  It's easy enough to work around, at least.

-- 
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] #1480: Don't Set TIME_ZONE unless it is explictly needed (or put it back to how you found it)

[Django]

#1480: Don't Set TIME_ZONE unless it is explictly needed (or put it back to how
you found it)
--+-
  Reporter:  i...@holsman.net  | Owner:  jedie
Status:  assigned | Milestone:  1.2  
 Component:  Core framework   |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  1
Needs_docs:  1|   Needs_tests:  1
Needs_better_patch:  1|  
--+-
Changes (by anonymous):

 * cc: b...@usagebot.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] #11077: Django's built-in tests fail when using url reverse tags in default registration templates

[Django]

#11077: Django's built-in tests fail when using url reverse tags in default
registration templates
-+--
  Reporter:  srosro  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Testing framework   |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by cmwslw):

 I've been thinking a little more about this, and I propose we could use
 the following options for "./manage.py test"

 --combine-urlconfs: tells the testing framework to combine the overridden
 URLConf with the ROOT_URLCONF. If --combine-urlconfs-with is specified,
 combine it with that instead of ROOT_URLCONF
 --combine-urlconfs-with: the URLConf to use for combining instead of
 ROOT_URLCONF. This is useful if you need to provide a minimal URL
 configuration for only the URLs you need to avoid conflicts.

 Most of the errors described here are because of auth and django-
 registration templates including a base.html that reverses to links such
 as the main index page, a login page, or an about us page (most of them
 do). --combine-urlconfs-with would be a useful option in that case because
 it would allow minimalistic URL schemes to be included for just those
 pages.

-- 
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] #11077: Django's built-in tests fail when using url reverse tags in default registration templates

[Django]

#11077: Django's built-in tests fail when using url reverse tags in default
registration templates
-+--
  Reporter:  srosro  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Testing framework   |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by cmwslw):

  * status:  closed => reopened
  * resolution:  fixed =>
  * stage:  Unreviewed => Design decision needed

-- 
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] #11077: Django's built-in tests fail when using url reverse tags in default registration templates

[Django]

#11077: Django's built-in tests fail when using url reverse tags in default
registration templates
+---
  Reporter:  srosro | Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:
Resolution:  fixed  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by cmwslw):

 This bug is still present. It's not a duplicate of either of the above
 mentioned cases (#10747, #10976).

 The same exact problem is happening for me using auth and django-
 registration. It doesn't matter whether I reference the URL using the view
 or it's name. The problem lies with the fact that the tests for both
 django.contrib.auth and django-registration set their
 [http://docs.djangoproject.com/en/dev/topics/testing/#django.test.TestCase.urls
 TestCase.urls] setting to override the default URLConf. This problem can
 be resolved by concatenating the test URL patterns and your root URL
 patterns. This is an unfeasible solution because it requires modifying the
 source code. As far as I know, this is the only real solution.

 After googling for hours, I've only found two references to this problem
 besides this ticket:

 [http://www.mail-archive.com/django-us...@googlegroups.com/msg78709.html]

 [http://recurser.com/articles/2009/11/10/noreversematch-custom-
 registration-templates-break-django-unit-tests/]

 The only solution they mention is using something like:
 {{{
 {% url home.views.index as index %}{{ index }}
 }}}
 instead of:
 {{{
 {% url home.views.index}
 }}}
 Although this workaround does not require a source code modification to
 auth or django-registration, it sucks bad because all reversing errors are
 suppressed whether or not it's during a test. I don't really see the point
 of testing if things like that need to be done.

 Apparently not many people use the test suite because this bug will affect
 anyone testing with a reverse() or 'url' tag in their template.

 Possible solution:
 If a
 [http://docs.djangoproject.com/en/dev/topics/testing/#django.test.TestCase.urls
 TestCase.urls] attribute '''is''' set, combine it with the ROOT_URLCONF
 instead of overwriting it. This could be an optional or default feature.

-- 
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] #12641: ManyToMany relationship with self, symmetrical=True, related_name='something' doesn't work

[Django]

#12641: ManyToMany relationship with self, symmetrical=True,
related_name='something' doesn't work
+---
  Reporter:  hwmrocker  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by hwmrocker):

 thanks for your clarification, and sorry for the invalid report

-- 
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] #12646: Flawed error display in admin when using fieldsets.

[Django]

#12646: Flawed error display in admin when using fieldsets.
+---
  Reporter:  schinckel  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by schinckel):

 Note: I haven't submitted a patch against django, as i am overriding the
 template in my project(s).

-- 
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] #12646: Flawed error display in admin when using fieldsets.

[Django]

#12646: Flawed error display in admin when using fieldsets.
+---
  Reporter:  schinckel  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by schinckel):

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

Comment:

 My replacement for the admin/includes/fieldset.html template, if it is
 useful:

 {{{
 
 {% if fieldset.name %}{{ fieldset.name }}{% endif %}
 {% if fieldset.description %}
 {{ fieldset.description|safe }}
 {% endif %}
 {% for line in fieldset %}
 
 {% for field in line %}
 
 {% if field.is_checkbox %}
 {{ field.field }}{{ field.label_tag }}
 {% else %}
 {{ field.label_tag }}
 {% if field.is_readonly %}
 {{ field.contents }}
 {% else %}
 {{ field.field }}
 {% endif %}
 {% endif %}
 {% if field.field.errors %}
 {{ field.field.errors }}
 {% endif %}
 {% if field.field.field.help_text %}
 {{
 field.field.field.help_text|safe }}
 {% endif %}
 
 {% endfor %}
 
 {% endfor %}
 

 }}}

-- 
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] #12646: Flawed error display in admin when using fieldsets.

[Django]

#12646: Flawed error display in admin when using fieldsets.
---+
 Reporter:  schinckel  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When using fieldsets within the admin, and an error occurs within one
 field of a line, then all fields within that line are marked as error by
 the css. That is, every field gets a red border, when really only the
 fields with actual errors should have a red border.

 Related, but less annoying: the error messages are piled up at the top of
 the fieldset line, rather than being close to the field with the error.

 I overcame both issues using a custom template for fieldset, and some
 extra css:
  - put an extra class on field.box when there are no errors for this
 field, and an entry in the admin-extra.css setting the border-color back.
  - remove the line.errors tag, and replace by appropriate
 field.field.errors tags within the for loop for fields within the line.

-- 
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] #8896: Routing according also to hostname

[Django]

#8896: Routing according also to hostname
-+--
  Reporter:  veena   | Owner:  jshedd  
Status:  new | Milestone:  1.2 
 Component:  Core framework  |   Version:  1.0 
Resolution:  |  Keywords:  routing hostname
 Stage:  Someday/Maybe   | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jshedd):

  * owner:  nobody => jshedd
  * milestone:  => 1.2

-- 
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] #12508: Feature: Dynamically adding inlines

[Django]

#12508: Feature: Dynamically adding inlines
---+
  Reporter:  zain  | Owner:  jezdez  
Status:  new   | Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  soc2009/admin-ui
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jezdez):

  * owner:  zain => jezdez
  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 FYI, my current status can be found here:
 http://github.com/jezdez/django/tree/admin-ui-combined

 ("combined" with the select-across feature of #12282 which I've ported to
 jQuery, as well)

-- 
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] #12282: Admin Actions: No Way to Select All

[Django]

#12282: Admin Actions: No Way to Select All
---+
  Reporter:  blinkylights  | Owner:  jezdez 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  admin actions 
change-list
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  1 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by jezdez):

 Correction, the latest updates are here:
 http://github.com/jezdez/django/tree/admin-ui-combined

-- 
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] #12525: ModelForm validation doesn't work like documented

[Django]

#12525: ModelForm validation doesn't work like documented
-+--
  Reporter:  Bernd Schlapsi   | Owner:  nobody   
 
Status:  closed  | Milestone:  1.2  
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  fixed   |  Keywords:  
Validators
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 Replying to [comment:6 korpios]:
 > This is a fairly significant backward-incompatible change that needs to
 be documented.

 I believe this is #12596, and as I understand it the proposal is to fix it
 to match the doc, not change the doc to match the new reality.

-- 
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] r12265 - django/trunk/django/contrib/auth

[noreply]

Author: jezdez
Date: 2010-01-19 16:19:26 -0600 (Tue, 19 Jan 2010)
New Revision: 12265

Modified:
   django/trunk/django/contrib/auth/admin.py
Log:
Fixed #12644 - Allow overriding the admin user creation form based on r12216. 
Thanks, minmax.

Modified: django/trunk/django/contrib/auth/admin.py
===
--- django/trunk/django/contrib/auth/admin.py   2010-01-19 18:09:03 UTC (rev 
12264)
+++ django/trunk/django/contrib/auth/admin.py   2010-01-19 22:19:26 UTC (rev 
12265)
@@ -62,11 +62,11 @@
 Use special form during user creation
 """
 defaults = {}
-if not obj:
-defaults = {
-'form': UserCreationForm,
-'fields': ['username'],
-}
+if obj is None:
+defaults.update({
+'form': self.add_form,
+'fields': admin.util.flatten_fieldsets(self.add_fieldsets),
+})
 defaults.update(kwargs)
 return super(UserAdmin, self).get_form(request, obj, **defaults)
 

-- 
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] #12644: Can not override UserAdmin.add_form in subclasses

[Django]

#12644: Can not override UserAdmin.add_form in subclasses
-+--
  Reporter:  minmax  | Owner:  jezdez
Status:  assigned| Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| 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] #12645: UnicodeEncodeError when validating forms with non-ascii field names

[Django]

#12645: UnicodeEncodeError when validating forms with non-ascii field names
-+--
  Reporter:  alanjds | Owner:  nobody 
Status:  new | Milestone:  1.2
 Component:  Forms   |   Version:  1.1
Resolution:  |  Keywords:  unicode
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by alanjds):

  * needs_better_patch:  => 0
  * summary:  UnicodeEncodeError when validating forms with non-ascii names
  => UnicodeEncodeError when validating forms
  with non-ascii field names
  * 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.

[Django] #12645: UnicodeEncodeError when validating forms with non-ascii names

[Django]

#12645: UnicodeEncodeError when validating forms with non-ascii names
-+--
 Reporter:  alanjds  |   Owner:  nobody
   Status:  new  |   Milestone:  1.2   
Component:  Forms| Version:  1.1   
 Keywords:  unicode  |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 I am creating forms dynamically, so users can type field names.

 Django is raising UnicodeEncodeError when some field name has a non-ascii
 name. Is simple not acceptable to constrain users to ASCII only.

 Baked example:
 {{{
 class UtilizacaoForm(forms.Form):
 pass

 ut = UtilizacaoForm()
 ut.fields[u'Diâmetro'] = forms.CharField(max_length=3)

 ut.is_valid()
 File "django/forms/forms.py" in is_valid
   120. return self.is_bound and not bool(self.errors)
 File "django/forms/forms.py" in _get_errors
   111. self.full_clean()
 File "django/forms/forms.py" in full_clean
   242. if hasattr(self, 'clean_%s' % name):

 Exception Type: UnicodeEncodeError at /novakoski/modelos/detalhe/1/
 Exception Value: ('ascii', u'clean_Di\xe2metro', 8, 9, 'ordinal not in
 range(128)')
 }}}

 Occurs because hasattr(obj, str) can't handle non-ascii at str, before
 preparing to call clean_fieldname.

 Bug found at 1.1.1 (r11612), but stays alive at actual TRUNK (r12264).

 Original traceback paste: http://dpaste.com/hold/147583/

 Quick fix 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] #12525: ModelForm validation doesn't work like documented

[Django]

#12525: ModelForm validation doesn't work like documented
-+--
  Reporter:  Bernd Schlapsi   | Owner:  nobody   
 
Status:  reopened| Milestone:  1.2  
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  |  Keywords:  
Validators
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by korpios):

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

Comment:

 Actually, there's a deeper problem here as well: if you don't call the
 super `.clean()` method from a `ModelForm` subclass that overrides
 `.clean()`, your `ModelForm` instance never gets updated with the values
 from your passed-in data(!).  This is because the update happens via a
 call to construct_instance in `ModelForm.clean()`, and `ModelForm.save()`
 assumes that cleaning has already happened and therefore passes
 `construct=False` to `save_instance`.  This is a fairly significant
 backward-incompatible change that needs to be documented.

-- 
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] #8160: ModelFormset ignores form properties

[Django]

#8160: ModelFormset ignores form properties
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  jkocherhans
Status:  assigned   | Milestone: 
 Component:  Forms  |   Version:  1.1-beta-1 
Resolution: |  Keywords:  formset
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  1  
Needs_better_patch:  0  |  
+---
Changes (by alanjds):

 * cc: alan.just...@yahoo.com.br (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] #8160: ModelFormset ignores form properties

[Django]

#8160: ModelFormset ignores form properties
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  jkocherhans
Status:  assigned   | Milestone: 
 Component:  Forms  |   Version:  1.1-beta-1 
Resolution: |  Keywords:  formset
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  1  
Needs_better_patch:  0  |  
+---
Comment (by alanjds):

 It looks like fixed at 1.1.1, but I cant run unittests.

 Replying to [comment:9 alanjds]:
 > Attached patch appears to target a very old revision. I will fix this
 bug in next 3 weeks (because I need it fixed), but for that I'm asking
 some guiedance to make not much mistakes. I will patch against 1.1-beta1.

-- 
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] #12644: Can not override UserAdmin.add_form in subclasses

[Django]

#12644: Can not override UserAdmin.add_form in subclasses
-+--
  Reporter:  minmax  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by minmax):

 * cc: minmax...@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] #12644: Can not override UserAdmin.add_form in subclasses

[Django]

#12644: Can not override UserAdmin.add_form in subclasses
-+--
  Reporter:  minmax  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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.

[Django] #12644: Can not override UserAdmin.add_form in subclasses

[Django]

#12644: Can not override UserAdmin.add_form in subclasses
+---
 Reporter:  minmax  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I want to do something like this:

 {{{
 class MyUseAdmin(UserAdmin):
 add_form = MyForm
 }}}

 But UserAdmin has a bug, it does not use attribute "add_form" in method
 "get_form"

-- 
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] #12628: readonly_fields in GenericInlineModelAdmin are ignored during save

[Django]

#12628: readonly_fields in GenericInlineModelAdmin are ignored during save
---+
  Reporter:  yedpodtrzitko | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  readonly_fields, 
generic
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  1 => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12628: readonly_fields in GenericInlineModelAdmin are ignored during save

[Django]

#12628: readonly_fields in GenericInlineModelAdmin are ignored during save
---+
  Reporter:  yedpodtrzitko | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  readonly_fields, 
generic
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by jezdez):

  * needs_better_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] #11696: validate command in 1.1 hides errors in models that used to be shown

[Django]

#11696: validate command in 1.1 hides errors in models that used to be shown
---+
  Reporter:  martin maney  | Owner:  lsaffre
Status:  assigned  | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Comment (by michael.john.k...@gmail.com):

 {{{
 Yeah, you can, just barely, distinguish the benign and evil failures,
 but it seems to require parsing the text of the exception import throws
 - "No module named models" vs anything else.
 Yuck.
 }}}

 the "yuck" solution.

 {{{
 #!python
 Index: django/db/models/loading.py
 ===
 --- django/db/models/loading.py (revision 12257)
 +++ django/db/models/loading.py (working copy)
 @@ -73,7 +73,11 @@
  self.nesting_level += 1
  try:
  models = import_module('.models', app_name)
 -except ImportError:
 +except ImportError, exc:
 +msg = exc.args[0]
 +if not msg.startswith('No module named') or 'models' not in
 msg:
 +raise
 +
  self.nesting_level -= 1
  if can_postpone:
  # Either the app has no models, or the package is still
 being
 }}}

-- 
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] r12264 - django/trunk/tests/modeltests/model_package

[noreply]

Author: ikelly
Date: 2010-01-19 12:09:03 -0600 (Tue, 19 Jan 2010)
New Revision: 12264

Modified:
   django/trunk/tests/modeltests/model_package/tests.py
Log:
Fixed an Oracle test failure introduced in [12226].

Modified: django/trunk/tests/modeltests/model_package/tests.py
===
--- django/trunk/tests/modeltests/model_package/tests.py2010-01-19 
16:55:22 UTC (rev 12263)
+++ django/trunk/tests/modeltests/model_package/tests.py2010-01-19 
18:09:03 UTC (rev 12264)
@@ -66,8 +66,10 @@
 >>> Article.publications.through._meta.fields[2].get_attname_column()
 ('publication_id', 'publication_id')
 
->>> Article._meta.get_field('publications').m2m_db_table()
-'model_package_article_publications'
+# The oracle backend truncates the name to 'model_package_article_publ233f'.
+>>> Article._meta.get_field('publications').m2m_db_table() \\
+... in ('model_package_article_publications', 'model_package_article_publ233f')
+True
 
 >>> Article._meta.get_field('publications').m2m_column_name()
 'article_id'

-- 
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] #12557: AnonymousUser has_perm should check backends has_perm

[Django]

#12557: AnonymousUser has_perm should check backends has_perm
-+--
  Reporter:  hvdklauw| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  has_perm AnonymousUser
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by jezdez):

 * cc: jezdez (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] #12643: Should mention to call parent clean method for modelForm in custom validation chapter

[Django]

#12643: Should mention to call parent clean method for modelForm in custom
validation chapter
--+-
 Reporter:  fgaudin   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.1   
 Keywords:  ModelForm, validation, clean  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I and some collegues always refer to
 http://docs.djangoproject.com/en/1.1/ref/forms/validation/#cleaning-and-
 validating-fields-that-depend-on-each-other to check how to do custom
 validation, I've been looking for a while before finding that I need to
 call the parent clean method for modelForm (to avoid postgres to raise the
 unique constraint error).

 I found later that it was written in ModelForm documentation. Just a
 warning with a link to this chapter would be great.

-- 
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] r12263 - in django/branches/releases/1.1.X: . django/db/models/fields tests/regressiontests/model_fields

[noreply]

Author: kmtracey
Date: 2010-01-19 10:55:22 -0600 (Tue, 19 Jan 2010)
New Revision: 12263

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/db/models/fields/__init__.py
   django/branches/releases/1.1.X/tests/regressiontests/model_fields/models.py
   django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py
Log:
[1.1.X] Fixed #10015 -- PostgreSQL 8.3+ no longer barfs when passing an integer 
as a filter() value for a CharField? or TextField?. Thanks, carljm 

Backport of r12150 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,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12151-12152,12220-12221,12229,12249,12253
   + 
/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,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253

Modified: django/branches/releases/1.1.X/django/db/models/fields/__init__.py
===
--- django/branches/releases/1.1.X/django/db/models/fields/__init__.py  
2010-01-19 01:25:30 UTC (rev 12262)
+++ django/branches/releases/1.1.X/django/db/models/fields/__init__.py  
2010-01-19 16:55:22 UTC (rev 12263)
@@ -435,6 +435,9 @@
 ugettext_lazy("This field cannot be null."))
 return smart_unicode(value)
 
+def get_db_prep_value(self, value):
+return self.to_python(value)
+
 def formfield(self, **kwargs):
 defaults = {'max_length': self.max_length}
 defaults.update(kwargs)
@@ -833,6 +836,11 @@
 def get_internal_type(self):
 return "TextField"
 
+def get_db_prep_value(self, value):
+if isinstance(value, basestring) or value is None:
+return value
+return smart_unicode(value)
+
 def formfield(self, **kwargs):
 defaults = {'widget': forms.Textarea}
 defaults.update(kwargs)

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/model_fields/models.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/model_fields/models.py 
2010-01-19 01:25:30 UTC (rev 12262)
+++ django/branches/releases/1.1.X/tests/regressiontests/model_fields/models.py 
2010-01-19 16:55:22 UTC (rev 12263)
@@ -52,6 +52,10 @@
 s = models.SlugField(max_length=255)
 
 
+class Post(models.Model):
+title = models.CharField(max_length=100)
+body = models.TextField()
+
 ###
 # ImageField
 

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py  
2010-01-19 01:25:30 UTC (rev 12262)
+++ django/branches/releases/1.1.X/tests/regressiontests/model_fields/tests.py  
2010-01-19 16:55:22 UTC (rev 12263)
@@ -6,7 +6,7 @@
 from django.db import models
 from django.core.exceptions import ValidationError
 
-from models import Foo, Bar, Whiz, BigD, BigS, Image
+from models import Foo, Bar, Whiz, BigD, BigS, Image, Post
 
 try:
 from decimal import Decimal
@@ -144,3 +144,17 @@
 bs = BigS.objects.create(s = 'slug'*50)
 bs = BigS.objects.get(pk=bs.pk)
 self.assertEqual(bs.s, 'slug'*50)
+
+class TypeCoercionTests(django.test.TestCase):
+"""
+Test that database lookups can accept the wrong types and convert
+them with no error: 

Re: [Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by iElectric):

 * cc: do...@dev.si (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] #12540: Add support for cross-database foreign keys and m2m

[Django]

#12540: Add support for cross-database foreign keys and m2m
---+
  Reporter:  russellm  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 The patch I've just uploaded is a first pass at implementing a fix for
 cross-database support. Feedback is welcome.

-- 
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] #12541: Add support for describing master/slave arrangements in multi-db

[Django]

#12541: Add support for describing master/slave arrangements in multi-db
---+
  Reporter:  russellm  | Owner:  nobody   
Status:  new   | Milestone:  1.2  
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 See the patch t12540-r12262.1.diff attached to #12540 - it includes a
 draft fix for this ticket.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.formtools  |   Version:  SVN
 
Resolution:|  Keywords:  session wizard 
forms
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by iElectric):

 Note about my usage of Nate's Session based Wizard:

 I needed option to not fill all forms until the last one, so I had to
 change the following parts:
 - in finish() form validation, force is_bound=True to override django
 default behaviour making empty forms not valid
 - add request parameter to is_last() function in order to inspect
 unexpected wizard finish

 Also note the following, which is very imporatant:
 - django upload handlers use cStringIO object which is NOT pickle-able.
 Use StringIO.StringIO instead.

-- 
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] #12540: Add support for cross-database foreign keys and m2m

[Django]

#12540: Add support for cross-database foreign keys and m2m
---+
  Reporter:  russellm  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 @zbraniecki: This is not a new idea - it has been made by several people
 over the history of multi-db development. Read up on the archives to see
 why it hasn't been 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] #10712: ModelAdmin.queryset() is undocumented.

[Django]

#10712: ModelAdmin.queryset() is undocumented.
+---
  Reporter:  mrts   | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords:  efficient-admin
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  1  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 See also #12642.

-- 
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] #12642: wiki:RowLevelPermissions should part of the official documentation

[Django]

#12642: wiki:RowLevelPermissions should part of the official documentation
+---
  Reporter:  MadeR  | Owner:  nobody
  
Status:  new| Milestone:  1.2   
  
 Component:  Documentation  |   Version:  1.2-alpha 
  
Resolution: |  Keywords:  wiki documentation row 
level permission admin modeladmin
 Stage:  Unreviewed | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 #10712 asks for docs for `queryset()` and contains a patch.

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

Re: [Django] #8363: Make it possible to specify tests to skip when running runtests.py

[Django]

#8363: Make it possible to specify tests to skip when running runtests.py
+---
  Reporter:  ramiro | Owner:  ramiro
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 I don't know is this is worth adding to the Django test infrastructure or
 belongs to a custom runner but has been very helpful when using the Django
 test suite to so I thought it could also be useful to others.

-- 
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] #10151: url tag causes TypeError: dict objects are unhashable

[Django]

#10151: url tag causes TypeError: dict objects are unhashable
+---
  Reporter:  pclerie| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by zack):

 This is caused by a programming error.

 I just had the same error message (Django 1.1.1)

 It was caused by an error in my url conf.

 I had a line like :
 {{{
 ('^huur/indoor/$', {},'huur_indoor'),
 }}}

 Which should have been like:

 {{{
 ('^huur/indoor/$', 'xl.views.huur_indoor', {},'huur_indoor'),
 }}}

-- 
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] #12642: wiki:RowLevelPermissions should part of the official documentation

[Django]

#12642: wiki:RowLevelPermissions should part of the official documentation
--+-
 Reporter:  MadeR |   
Owner:  nobody
   Status:  new   |   
Milestone:  1.2   
Component:  Documentation | 
Version:  1.2-alpha 
 Keywords:  wiki documentation row level permission admin modeladmin  |   
Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The page http://code.djangoproject.com/wiki/RowLevelPermissions contains
 simply documentation about django.contrib.admin
 All the class methods described in the page exists and are fully
 functional, so the page should be merged with the official documentation
 at http://docs.djangoproject.com/en/1.1/ref/contrib/admin/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12639: Download page should list checksums

[Django]

#12639: Download page should list checksums
--+-
  Reporter:  joerg| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Django Web site  |   Version:
Resolution:  duplicate|  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Clueless):

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

Comment:

 Duplicate of #12129

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