Re: [Django] #16193: Use qunit to test javascript in django source

[Django]

#16193: Use qunit to test javascript in django source
-+-
   Reporter:  mbraak@…   |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Testing framework
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  testing javascript
 Resolution: |  qunit
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  1  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by mbraak):

 I see that the sebleier/qunit branch is much further developed than I
 initially thought. I will add my tests to this branch.

-- 
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] #14206: contrib:admin dynamic list_display support

[Django]

#14206: contrib:admin dynamic list_display support
-+-
   Reporter: |  Owner:  cyrus
  gabejackson| Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone: |   Keywords:  list_display
Version:  1.2|  override dynamic admin
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by graveyboat):

 * ui_ux:   => 0


Comment:

 I ran across this ticket today, but I've created some similar
 functionality in the past.  One thing I ran across which doesn't seem to
 be handled here is the case where the field removed from list_display also
 happens to be in list_display_links.  For instance, in the test,
 list_display = ('name','parent').  In this case, list_display_links would
 be [ 'name' ].  The test case covers removing 'parent', but not 'name'.
 If you were to remove 'name', your change_list screen would be left with a
 list of results with no link.

 I don't want to be "that guy" that re-opens tickets, but if it needs to be
 re-opened, I'd be glad to submit a patch to fix 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-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] #16210: Model validation tests broken in Python 2.5 after [16348]

[Django]

#16210: Model validation tests broken in Python 2.5 after [16348]
-+-
   Reporter:  julien |  Owner:
   Type:  Bug| Status:  new
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:  with
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by julien):

 A patch wasn't absolutely necessary here, but it will make the fix that
 much quicker to be applied ;)

-- 
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] #7452: Settings for HTML4 or XHTML output

[Django]

#7452: Settings for HTML4 or XHTML output
-+-
   Reporter:  telenieko  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Core (Other)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * stage:  Accepted => 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-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] #7452: Settings for HTML4 or XHTML output

[Django]

#7452: Settings for HTML4 or XHTML output
---+--
   Reporter:  telenieko|  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Core (Other)
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by melinath):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 See http://groups.google.com/group/django-developers/msg/a65fbbc8effcd914.
 As is pointed out there, having a setting to switch between HTML and XHTML
 would be very irritating - and besides, moving forward we'll probably want
 to stick to HTML5. Can we close this as wontfix?

-- 
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] #16137: .get behaviour is inconsistent with .get_or_create when no kwargs are given (was: .get behaviour is inconsisten with .get_or_create)

[Django]

#16137: .get behaviour is inconsistent with .get_or_create when no kwargs are 
given
-+-
   Reporter:  wilfred@…  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by melinath):

 * ui_ux:   => 0


Comment:

 Removing that line causes no unexpected test failures.

-- 
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] #14930: `values_list()` fails on queryset ordered by extra column

[Django]

#14930: `values_list()` fails on queryset ordered by extra column
-+-
   Reporter:  lsaffre|  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by robin):

 * cc: robinchew@… (added)
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #16210: Model validation tests broken in Python 2.5 after [16348]

[Django]

#16210: Model validation tests broken in Python 2.5 after [16348]
-+-
   Reporter:  julien |  Owner:
   Type:  Bug| Status:  new
  Milestone: |  Component:  Testing framework
Version:  SVN|   Severity:  Release blocker
 Resolution: |   Keywords:  with
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * has_patch:  0 => 1
 * version:  1.3 => SVN
 * 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] #16210: Model validation tests broken in Python 2.5 after [16348]

[Django]

#16210: Model validation tests broken in Python 2.5 after [16348]
+---
   Reporter:  julien|  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  1.3   |   Severity:  Release blocker
 Resolution:|   Keywords:  with
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---
Changes (by melinath):

 * owner:  melinath =>
 * status:  assigned => new


Comment:

 It occurs to me that this may not need a patch since it's so trivial.

-- 
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] #16180: IGNORED_PARAMS customization

[Django]

#16180: IGNORED_PARAMS customization
---+---
   Reporter:  msaelices|  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  contrib.admin
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
Changes (by melinath):

 * has_patch:  0 => 1


Comment:

 I attached a patch with corrections to the docs for language and for
 clarity. However, I wonder if this is really the solution? Really,
 shouldn't lookup_params that aren't fields on the model always be ignored?
 They certainly aren't security risks the same way as other items.
 get_ignored_lookup_params should only be necessary if (for some reason)
 there's a conflict between the name of the lookup field you want to handle
 and one of the fields on the model.

-- 
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] #7783: PostgreSQL database introspection does not detect NULL columns

[Django]

#7783: PostgreSQL database introspection does not detect NULL columns
-+-
   Reporter:  bthomas@…  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Ready for  |   Keywords:
  checkin|  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by anonymous):

 * 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] #7783: PostgreSQL database introspection does not detect NULL columns

[Django]

#7783: PostgreSQL database introspection does not detect NULL columns
-+-
   Reporter:  bthomas@…  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 We tried to setup an environment using PostgreSQL 7.4.30 (the oldest one
 available for download)[1] to answer your question. Unfortunately when we
 run manage.py syncdb we received an error message stating that:

 "django.db.utils.DatabaseError: function pg_get_serial_sequence("unknown",
 "unknown") does not exist"

 Further research in the django-users mailing list revealed that version
 7.4 of PostgreSQL does not contain the function pg_get_serial_sequence.[2]
 A reply from django core developer Russell Keith-Magee says that in Django
 version 1.3 support for PostgreSQL 7.4 was abandoned.[3]

 [1]http://www.postgresql.org/ftp/source/
 [2]http://markmail.org/thread/pf4bmphpsv6m4djl
 [3]http://markmail.org/message/tp5czlz3ipy7vd5j

-- 
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] #16017: createsuperuser fails if Python can't detect default locale

[Django]

#16017: createsuperuser fails if Python can't detect default locale
-+-
   Reporter: |  Owner:  nobody
  prestontimmons | Status:  new
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  dceu2011
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by charstring):

 * needs_better_patch:  0 => 1


Comment:

 I think mocking both locale.getdefaultlocale and getpass is one mock to
 many.
 This boils down to testing wether if statements work in python.
 I'll attach a patch that also fixes the case of an unknown locale, that
 someone experienced today setting up his environment...

 Though, I don't know whether this last case should be fixed, I suspect it
 only happens on misconfigured boxes.
 But it does fit the title of the ticket.

 Someone '''should''' check if these test should be skipped on non *nix
 environments.

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

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

Re: [Django] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  1   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by julien):

 Sorry, `favorite_animal` has a default value and `unicorns` is a M2M, so
 no need to provide values to `UserProfile.objects.create` for those.

-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  1   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 OK, I've closed #16102 as a dupe.

 This patch is looking good, however a few improvements should be made in
 the code snippet about the `post_save` signal:

 * Do not say "perhaps in models.py", but instead provide specific examples
 of where this code could be placed.
 * Since a new user is created, it is unnecessary to use
 `UserProfile.objects.get_or_create`. `UserProfile.objects.create` can be
 used instead.
 * `unicorns` and `favorite_animal` are both required fields, so you need
 to either make them optional or provide values for them when creating the
 `UserProfile` instance.

-- 
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] #16209: Add alternative repositories to 'Installing the development version' in the docs.

[Django]

#16209: Add alternative repositories to 'Installing the development version' in 
the
docs.
-+---
   Reporter:  ShawnMilo  |  Owner:  ShawnMilo
   Type:  Uncategorized  | Status:  new
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+---
Changes (by ShawnMilo):

 * has_patch:  0 => 1


Comment:

 Patch added. I built the docs (html only) and checked to make sure it
 looked right and the links worked. I also added myself to AUTHORS since I
 have a handful of patches in. ^_^

-- 
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] #16210: Model validation tests broken in Python 2.5 after [16348]

[Django]

#16210: Model validation tests broken in Python 2.5 after [16348]
+---
   Reporter:  julien|  Owner:  melinath
   Type:  Bug   | Status:  assigned
  Milestone:|  Component:  Testing framework
Version:  1.3   |   Severity:  Release blocker
 Resolution:|   Keywords:  with
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+---
Changes (by melinath):

 * status:  new => assigned
 * owner:  nobody => melinath
 * keywords:   => with
 * stage:  Unreviewed => Accepted


-- 
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] #15279: Inheritance of rel fields from a single abstract base class through multiple abstract classes causes errors.

[Django]

#15279: Inheritance of rel fields from a single abstract base class through
multiple abstract classes causes errors.
-+-
   Reporter:  melinath   |  Owner:  melinath
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  abstract
Needs documentation:  0  |  inheritance
Patch needs improvement:  0  |  Has patch:  1
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by melinath):

 * keywords:   => abstract inheritance
 * status:  new => assigned
 * ui_ux:   => 0


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

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

Re: [Django] #16102: Link to the old django book + improving section

[Django]

#16102: Link to the old django book + improving section
-+-
   Reporter:  flocati@…  |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  duplicate  |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by julien):

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


Comment:

 This is actually taken care of by #16207 along with a few other doc
 improvements, so I'm closing this one as dupe.

-- 
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] #16150: Syndication Feed docs incorrectly describe tag.

[Django]

#16150: Syndication Feed docs incorrectly describe  tag.
+---
   Reporter:  melinath  |  Owner:  melinath
   Type:  Bug   | Status:  assigned
  Milestone:|  Component:  Documentation
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:  rss
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+---
Changes (by melinath):

 * status:  new => assigned
 * ui_ux:   => 0


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

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

Re: [Django] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by melinath):

 I already removed the link. Forgot to mention that, 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-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] #16196: Redundant or incorrect code in tests

[Django]

#16196: Redundant or incorrect code in tests
-+-
   Reporter: |  Owner:  melinath
  intelliyole| Status:  assigned
   Type: |  Component:  Uncategorized
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  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.

[Django] #16210: Model validation tests broken in Python 2.5 after [16348]

[Django]

#16210: Model validation tests broken in Python 2.5 after [16348]
+-
 Reporter:  julien  |Owner:  nobody
 Type:  Bug |   Status:  new
Milestone:  |Component:  Testing framework
  Version:  1.3 | Severity:  Release blocker
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
 Just need to add "`from __future__ import with_statement`" at the top of
 source:django/trunk/tests/modeltests/validation/test_unique.py

-- 
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] #16204: Remove unused functions in admin core.js (getCorrectYear and getISODate).

[Django]

#16204: Remove unused functions in admin core.js (getCorrectYear and 
getISODate).
-+-
   Reporter:  mbraak |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  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] #16195: Document the ModelAdmin.get_changelist

[Django]

#16195: Document the ModelAdmin.get_changelist
-+-
   Reporter:  msaelices  |  Owner:  msaelices
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  modeladmin
 Resolution: |  changelist
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * keywords:   => modeladmin changelist
 * has_patch:  0 => 1
 * type:  Bug => Cleanup/optimization
 * stage:  Accepted => Ready for checkin


Comment:

 Seems simple enough.

-- 
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] #16188: Added locale formats for swiss german language

[Django]

#16188: Added locale formats for swiss german language
-+-
   Reporter:  sspross|  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:
  Milestone: |  Internationalization
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  locale, formats
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by Merino):

 Add a new patch to the root of the project.

-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by julien):

 Replying to [comment:1 aaugustin]:
 > Yes, illustrating the text with code samples would help. The link to the
 Django Book may become redundant, then.

 Yep, the link to the Django book should be removed. See #16102. Both
 tickets could be fixed in one go.

-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---

Comment (by foxwhisper):

 Nice, thanks for the quick turn around on this guys!

-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:  userprofile
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by melinath):

 * keywords:   => userprofile
 * 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-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] #16193: Use qunit to test javascript in django source

[Django]

#16193: Use qunit to test javascript in django source
-+-
   Reporter:  mbraak@…   |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Testing framework
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  testing javascript
 Resolution: |  qunit
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  1  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by julien):

 Replying to [comment:4 jezdez]:
 > Well, the approach we took on Github (Sebleier's fork) is much more
 generic and prepared for app centric test running.

 I actually played a bit with that branch a couple of weeks ago and it's
 looking great. I was wondering if you guys had thought of a way to test
 the admin interface (e.g. dynamically adding or removing inlines)? This
 would require generating a DOM from the up-to-date admin templates and
 with some test data. Perhaps we need to introduce a management command to
 generate fresh HTML files from the latest admin codebase, so that these
 can be tested with the admin javascript via qunit. I haven't thought of it
 much beyond that, but I'll try to get to it next week.

-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  melinath
   Type:  Bug | Status:  assigned
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Accepted|  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by melinath):

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


-- 
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] #16193: Use qunit to test javascript in django source

[Django]

#16193: Use qunit to test javascript in django source
-+-
   Reporter:  mbraak@…   |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Testing framework
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  testing javascript
 Resolution: |  qunit
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  1  |Needs tests:  0
Patch needs improvement:  1  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_better_patch:  0 => 1


Comment:

 Well, the approach we took on Github (Sebleier's fork) is much more
 generic and prepared for app centric test running.

-- 
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] #16205: Beginners install guide for Windows

[Django]

#16205: Beginners install guide for Windows
---+--
   Reporter:  erlingbo |  Owner:
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Documentation
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:  install, windows
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by melinath):

 * owner:  melinath =>
 * status:  assigned => new


Comment:

 I ended up putting the tutorial in /howto/windows, parallel to
 /howto/jython, since it is a howto with a specific target audience rather
 than an exhaustive guide. However, I think that it still needs work. I
 would have tried, but I don't really use windows much. Things that I think
 need to be fixed:

 1. the guide installs easy_install *and* pip. Shouldn't easy_install be
 enough? Having both will probably confuse beginners who just want to get
 things installed.
 2. the guide assumes that the users have administrative access and want to
 use it in combination with a shell. On linux, easy_install has a --user
 option which installs to the user's directory (thus avoiding the need for
 admin access) - isn't there a similar option on windows?
 3. There is only one pitfall in "Common pitfalls" - perhaps rename the
 section? Also, what's the policy on linking to stackoverflow answers from
 django docs?

-- 
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] #16182: TimestampSigner should use a more precise timestamp

[Django]

#16182: TimestampSigner should use a more precise timestamp
-+-
   Reporter:  floguy |  Owner:  floguy
   Type:  Bug| Status:  new
  Milestone: |  Component:  Core (Other)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_better_patch:  0 => 1


Comment:

 time_func should it be.

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

[Changeset] r16351 - in django/trunk: django/core docs/ref tests/modeltests/validators

[noreply]

Author: SmileyChris
Date: 2011-06-09 16:51:03 -0700 (Thu, 09 Jun 2011)
New Revision: 16351

Modified:
   django/trunk/django/core/validators.py
   django/trunk/docs/ref/validators.txt
   django/trunk/tests/modeltests/validators/tests.py
Log:
Fixes #13511 -- make regex parameter to RegexValidator to be optional. Also 
tidies up related docs (parameters aren't attributes). Thanks for the patch 
work, davidfischer.

Modified: django/trunk/django/core/validators.py
===
--- django/trunk/django/core/validators.py  2011-06-09 23:15:42 UTC (rev 
16350)
+++ django/trunk/django/core/validators.py  2011-06-09 23:51:03 UTC (rev 
16351)
@@ -29,8 +29,9 @@
 if code is not None:
 self.code = code
 
+# Compile the regex if it was not passed pre-compiled.
 if isinstance(self.regex, basestring):
-self.regex = re.compile(regex)
+self.regex = re.compile(self.regex)
 
 def __call__(self, value):
 """

Modified: django/trunk/docs/ref/validators.txt
===
--- django/trunk/docs/ref/validators.txt2011-06-09 23:15:42 UTC (rev 
16350)
+++ django/trunk/docs/ref/validators.txt2011-06-09 23:51:03 UTC (rev 
16351)
@@ -60,26 +60,31 @@
 
 ``RegexValidator``
 --
-.. class:: RegexValidator(regex, [message=None, code=None])
+.. class:: RegexValidator([regex=None, message=None, code=None])
 
+:param regex: If not ``None``, overrides :attr:`regex`. Can be a regular
+expression string or a pre-compiled regular expression.
+:param message: If not ``None``, overrides :attr:`.message`.
+:param code: If not ``None``, overrides :attr:`code`.
+
 .. attribute:: regex
 
 The regular expression pattern to search for the provided ``value``,
 or a pre-compiled regular expression. Raises a
-:exc:`~django.core.exceptions.ValidationError` with :attr:`.message`
-and :attr:`.code` if no match is found.
+:exc:`~django.core.exceptions.ValidationError` with :attr:`message`
+and :attr:`code` if no match is found. By default, matches any string
+(including an empty string).
 
 .. attribute:: message
 
-The error message used by 
:exc:`~django.core.exceptions.ValidationError`
-if validation fails. If no :attr:`.message` is specified, a generic
-``"Enter a valid value"`` message is used. Default value: ``None``.
+The error message used by
+:exc:`~django.core.exceptions.ValidationError` if validation fails.
+Defaults to ``"Enter a valid value"``.
 
 .. attribute:: code
 
 The error code used by :exc:`~django.core.exceptions.ValidationError`
-if validation fails. If :attr:`.code` is not specified, ``"invalid"``
-is used. Default value: ``None``.
+if validation fails. Defaults to ``"invalid"``.
 
 ``URLValidator``
 
@@ -90,16 +95,19 @@
 404 status code). Raises an error code of ``'invalid'`` if it doesn't look
 like a URL, and a code of ``'invalid_link'`` if it doesn't exist.
 
+:param verify_exists: Sets :attr:`verify_exists`. Defaults to ``False``.
+:param validator_user_agent: Sets :attr:`validator_user_agent`. Defaults to
+:setting:`URL_VALIDATOR_USER_AGENT` or, if that setting is set to a
+null value, ``"Django (http://www.djangoproject.com/)"``.
+
 .. attribute:: verify_exists
 
-Default value: ``False``. If set to ``True``, this validator checks
-that the URL actually exists.
+If set to ``True``, this validator checks that the URL actually exists.
 
 .. attribute:: validator_user_agent
 
-If :attr:`.verify_exists` is ``True``, Django uses the value of
-:attr:`.validator_user_agent` as the "User-agent" for the request. This
-defaults to :setting:`settings.URL_VALIDATOR_USER_AGENT 
`.
+If :attr:`verify_exists` is ``True``, Django uses this value as the
+"User-agent" for the request.
 
 ``validate_email``
 --

Modified: django/trunk/tests/modeltests/validators/tests.py
===
--- django/trunk/tests/modeltests/validators/tests.py   2011-06-09 23:15:42 UTC 
(rev 16350)
+++ django/trunk/tests/modeltests/validators/tests.py   2011-06-09 23:51:03 UTC 
(rev 16351)
@@ -112,6 +112,11 @@
 (BaseValidator(True), True, None),
 (BaseValidator(True), False, ValidationError),
 
+(RegexValidator(), '', None),
+(RegexValidator(), 'x1x2', None),
+(RegexValidator('[0-9]+'), 'xx', ValidationError),
+(RegexValidator('[0-9]+'), '1234', None),
+(RegexValidator(re.compile('[0-9]+')), '1234', None),
 (RegexValidator('.*'), '', None),
 (RegexValidator(re.compile('.*')), '', None),
 (RegexValidator('.*'), 'x', None),

-- 
You received this message 

Re: [Django] #13511: RegexValidator pattern is optional and should be required

[Django]

#13511: RegexValidator pattern is optional and should be required
-+-
   Reporter: |  Owner:  davidfischer
  davidfischer   | Status:  closed
   Type: |  Component:  Core (Other)
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  validators,regexvalidator
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by SmileyChris):

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


Comment:

 In [16351]:
 {{{
 #!CommitTicketReference repository="" revision="16351"
 Fixes #13511 -- make regex parameter to RegexValidator to be optional.
 Also tidies up related docs (parameters aren't attributes). Thanks for the
 patch work, davidfischer.
 }}}

-- 
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] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  jgelens
  Wassmann | Status:  assigned
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jgelens):

 TODO: use column instead of given name. Will fix 2nd sprint day.

-- 
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] #16208: natural key YAML deserialization using non-list natural keys broken (with fixing patch)

[Django]

#16208: natural key YAML deserialization using non-list natural keys broken 
(with
fixing patch)
+--
   Reporter:  jeff.k@…  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Core (Serialization)
Version:  1.2   |   Severity:  Normal
 Resolution:|   Keywords:  yaml
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+--

Comment (by jeff.k@…):

 Here's an example.  This is modeled on the natural key use case in the
 docs.  The important difference is that the natural key is a singleton
 field (name), not a list of fields (first_name, last_name)

 {{{#!python
 from django.db import models

 class AuthorManager(models.Manager):
 def get_by_natural_key(self, name):
 return self.get(name=name)

 class Author(models.Model):
 objects = AuthorManager()
 name = models.CharField(max_length=100, unique=True)

 class Book(models.Model):
 title = models.CharField(max_length=100)
 author = models.ForeignKey(Author)
 }}}

 Here's the YAML data which fails to import into the resulting db


 {{{
 - {model: appname.author, pk: 1, fields: {name: Hemingway}}
 - {model: appname.book, pk: 1, fields: {title: "For Whom the Bell Tolls",
 author: Hemingway}}
 }}}

 The incorrect behavior is to reject this data, complaning that "Hemingway"
 isn't an integer (which foreign keys need to be), because when the
 serialized data being loaded is a singleton, the get_by_natural_key()
 method is not employed to implement the mapping to the key value.  I think
 the bug was just confusion about if/else indentation.  It's kind of hairy
 in there.

-- 
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] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  jgelens
  Wassmann | Status:  assigned
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jgelens):

 * owner:  nobody => jgelens
 * 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-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] #16205: Beginners install guide for Windows

[Django]

#16205: Beginners install guide for Windows
---+--
   Reporter:  erlingbo |  Owner:  melinath
   Type:  New feature  | Status:  assigned
  Milestone:   |  Component:  Documentation
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:  install, windows
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by melinath):

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


Comment:

 Going to make this 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-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.

[Changeset] r16350 - in django/trunk: django/core/handlers django/http django/views tests/regressiontests/requests

[noreply]

Author: lukeplant
Date: 2011-06-09 16:15:42 -0700 (Thu, 09 Jun 2011)
New Revision: 16350

Modified:
   django/trunk/django/core/handlers/modpython.py
   django/trunk/django/core/handlers/wsgi.py
   django/trunk/django/http/__init__.py
   django/trunk/django/views/debug.py
   django/trunk/tests/regressiontests/requests/tests.py
Log:
Fixed #16178 - Cleanup request classes' `__repr__()`

Thanks to julien for the patch.

Modified: django/trunk/django/core/handlers/modpython.py
===
--- django/trunk/django/core/handlers/modpython.py  2011-06-09 20:01:28 UTC 
(rev 16349)
+++ django/trunk/django/core/handlers/modpython.py  2011-06-09 23:15:42 UTC 
(rev 16350)
@@ -45,32 +45,6 @@
 self._stream = self._req
 self._read_started = False
 
-def __repr__(self):
-# Since this is called as part of error handling, we need to be very
-# robust against potentially malformed input.
-try:
-get = pformat(self.GET)
-except:
-get = ''
-if self._post_parse_error:
-post = ''
-else:
-try:
-post = pformat(self.POST)
-except:
-post = ''
-try:
-cookies = pformat(self.COOKIES)
-except:
-cookies = ''
-try:
-meta = pformat(self.META)
-except:
-meta = ''
-return 
smart_str(u''
 %
- (self.path, unicode(get), unicode(post),
-  unicode(cookies), unicode(meta)))
-
 def get_full_path(self):
 # RFC 3986 requires self._req.args to be in the ASCII range, but this
 # doesn't always happen, so rather than crash, we defensively encode 
it.

Modified: django/trunk/django/core/handlers/wsgi.py
===
--- django/trunk/django/core/handlers/wsgi.py   2011-06-09 20:01:28 UTC (rev 
16349)
+++ django/trunk/django/core/handlers/wsgi.py   2011-06-09 23:15:42 UTC (rev 
16350)
@@ -157,31 +157,6 @@
 self._stream = self.environ['wsgi.input']
 self._read_started = False
 
-def __repr__(self):
-# Since this is called as part of error handling, we need to be very
-# robust against potentially malformed input.
-try:
-get = pformat(self.GET)
-except:
-get = ''
-if self._post_parse_error:
-post = ''
-else:
-try:
-post = pformat(self.POST)
-except:
-post = ''
-try:
-cookies = pformat(self.COOKIES)
-except:
-cookies = ''
-try:
-meta = pformat(self.META)
-except:
-meta = ''
-return '' % \
-(get, post, cookies, meta)
-
 def get_full_path(self):
 # RFC 3986 requires query string arguments to be in the ASCII range.
 # Rather than crash if this doesn't happen, we encode defensively.

Modified: django/trunk/django/http/__init__.py
===
--- django/trunk/django/http/__init__.py2011-06-09 20:01:28 UTC (rev 
16349)
+++ django/trunk/django/http/__init__.py2011-06-09 23:15:42 UTC (rev 
16350)
@@ -134,6 +134,53 @@
 
 RAISE_ERROR = object()
 
+
+def build_request_repr(request, path_override=None, GET_override=None,
+   POST_override=None, COOKIES_override=None,
+   META_override=None):
+"""
+Builds and returns the request's representation string. The request's
+attributes may be overridden by pre-processed values.
+"""
+# Since this is called as part of error handling, we need to be very
+# robust against potentially malformed input.
+try:
+get = (pformat(GET_override)
+   if GET_override is not None
+   else pformat(request.GET))
+except:
+get = ''
+if request._post_parse_error:
+post = ''
+else:
+try:
+post = (pformat(POST_override)
+if POST_override is not None
+else pformat(request.POST))
+except:
+post = ''
+try:
+cookies = (pformat(COOKIES_override)
+   if COOKIES_override is not None
+   else pformat(request.COOKIES))
+except:
+cookies = ''
+try:
+meta = (pformat(META_override)
+if META_override is not None
+else pformat(request.META))
+except:
+meta = ''
+path = path_override if path_override is not None else request.path
+return 
smart_str(u'<%s\npath:%s,\nGET:%s,\nPOST:%s,\nCOOKIES:%s,\nMETA:%s>' %
+ 

Re: [Django] #16178: Cleanup request classes' __repr__()

[Django]

#16178: Cleanup request classes' __repr__()
-+-
   Reporter:  julien |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  HTTP handling
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by lukeplant):

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


Comment:

 In [16350]:
 {{{
 #!CommitTicketReference repository="" revision="16350"
 Fixed #16178 - Cleanup request classes' `__repr__()`

 Thanks to julien for the patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #16204: Remove unused functions in admin core.js (getCorrectYear and getISODate).

[Django]

#16204: Remove unused functions in admin core.js (getCorrectYear and 
getISODate).
-+-
   Reporter:  mbraak |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * has_patch:  0 => 1


Comment:

 There actually isn't a way (that I could see at least) to download the raw
 diff from github. So here's one made from applying the patch to my django.

-- 
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] #16198: model_forms tests are still doctests.

[Django]

#16198: model_forms tests are still doctests.
-+-
   Reporter: |  Owner:  nobody
  gregmuellegger | Status:  new
   Type: |  Component:  Testing framework
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  model_forms,
Version:  1.3|  doctests
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * stage:  Accepted => Ready for checkin


Comment:

 Applies cleanly & tests pass. Yay!

-- 
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] #16196: Redundant or incorrect code in tests

[Django]

#16196: Redundant or incorrect code in tests
-+-
   Reporter: |  Owner:  melinath
  intelliyole| Status:  assigned
   Type: |  Component:  Uncategorized
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * needs_better_patch:  1 => 0
 * version:  1.3 => SVN


Comment:

 Made the fixes suggested by aaugustin.

-- 
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] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  nobody
  Wassmann | Status:  new
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jgelens):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #10498: Passing ugettext_lazy to related object's create() doesn't work

[Django]

#10498: Passing ugettext_lazy to related object's create() doesn't work
-+-
   Reporter: |  Owner:  ojii
  mtredinnick| Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by ojii):

 Possible solution: In django.db.models.base.Model.__init__, check if
 'val's that are set onto the model are django.utils.functional.Promise
 instances, and if so, force_unicode them before setting the attribute.

-- 
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] #16031: Custom comment form is incomplete and wrong.

[Django]

#16031: Custom comment form is incomplete and wrong.
-+-
   Reporter:  ddshore@…  |  Owner:  teraom
   Type: | Status:  assigned
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-

Comment (by julien):

 The code snippet just above the "Flagging" section in
 https://docs.djangoproject.com/en/dev/ref/contrib/comments/example/ should
 also be fixed as part of 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-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] #10498: Passing ugettext_lazy to related object's create() doesn't work

[Django]

#10498: Passing ugettext_lazy to related object's create() doesn't work
-+-
   Reporter: |  Owner:  ojii
  mtredinnick| Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by ojii):

 * owner:  nobody => ojii
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #16196: Redundant or incorrect code in tests

[Django]

#16196: Redundant or incorrect code in tests
-+-
   Reporter: |  Owner:  melinath
  intelliyole| Status:  assigned
   Type: |  Component:  Uncategorized
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-
Changes (by melinath):

 * owner:  nobody => melinath
 * 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-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] #14695: Field's `name` kwarg gets paved over

[Django]

#14695: Field's `name` kwarg gets paved over
-+-
   Reporter:  erikrose   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Ready for  |   Keywords:  dceu2011
  checkin|  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by ojii):

 * 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] #14695: Field's `name` kwarg gets paved over

[Django]

#14695: Field's `name` kwarg gets paved over
-+-
   Reporter:  erikrose   |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  dceu2011
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by willhardy):

 * owner:  willhardy => nobody
 * needs_better_patch:  1 => 0
 * keywords:   => dceu2011
 * status:  assigned => new
 * 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-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] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  nobody
  Wassmann | Status:  new
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-

Comment (by charstring):

 We're almost there.. fixed the count case.. Now for the join case...

 What would be the usecase for the
 queryset.distinct('othertable__somefield')

-- 
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] #15775: Can't enter scientific notation in decimal fields

[Django]

#15775: Can't enter scientific notation in decimal fields
+
   Reporter:  gregthe1  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Forms
Version:  1.2   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  1 |  Easy pickings:  0
  UI/UX:  0 |
+
Changes (by aaugustin):

 * needs_better_patch:  0 => 1


Comment:

 I suggest the following changes to the patch, by order of decreasing
 importance.

 You should use `TestCase` from `django.utils.unittest`, which is already
 imported, and not from `django.test`, since you're not using the extra
 features of `django.test.TestCase`.

 {{{
 f.validate(Decimal('1E+2'))  # Ensure that scientific notation
 with positive exponent is accepted (#15775)
 }}}
 would be more readable as:
 {{{
 # regression test for #15775: scientific notation with
 positive exponent is valid
 f.validate(Decimal('1E+2'))
 }}}

 You may try to re-wrap a bit `django/forms/fields.py`. It's hard to read
 140-chars lines — the coding rules recommend wrapping at 80 chars.

 You're missing a `\n` at the end of the file (look at your patch in Trac).

-- 
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] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
-+-
   Reporter:  danbrwn|  Owner:  mitsuhiko
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  foreign,key,quoted,dceu2011
Patch needs improvement:  0  |  Has patch:  1
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ojii):

 * keywords:  foreign,key,quoted => foreign,key,quoted,dceu2011
 * has_patch:  0 => 1
 * ui_ux:   => 0
 * easy:  1 => 0


Comment:

 Fixed this by raising a more useful exception, see patch. Discussed this
 with Alex and Andrew and they agreed that this is a reasonable solution
 for 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-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] #14695: Field's `name` kwarg gets paved over

[Django]

#14695: Field's `name` kwarg gets paved over
-+-
   Reporter:  erikrose   |  Owner:  willhardy
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  1
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by willhardy):

 * status:  new => assigned
 * owner:  erikrose => willhardy
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #16195: Document the ModelAdmin.get_changelist

[Django]

#16195: Document the ModelAdmin.get_changelist
-+---
   Reporter:  msaelices  |  Owner:  msaelices
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+---
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


-- 
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] #16192: Make unique_together error messages in ModelForms customizable

[Django]

#16192: Make unique_together error messages in ModelForms customizable
-+-
   Reporter: |  Owner:  nobody
  leahculver | Status:  new
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * component:  Forms => Database layer (models, ORM)


-- 
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] #16192: Make unique_together error messages in ModelForms customizable

[Django]

#16192: Make unique_together error messages in ModelForms customizable
---+
   Reporter:  leahculver   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Forms
Version:  1.3  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
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] #16200: __init__ of TemplateIfParser has return statement

[Django]

#16200: __init__ of TemplateIfParser has return statement
-+-
   Reporter:  traff  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 The patch is all right, except for the fact that it contains `\r\n` end-
 of-lines. It's still possible to apply it as-is.

-- 
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] #16200: __init__ of TemplateIfParser has return statement

[Django]

#16200: __init__ of TemplateIfParser has return statement
+-
   Reporter:  traff |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Template system
Version:  1.3   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 This `return` statement was harmless because `super(...)` returned `None`
 anyvway.

 But it's better to remove it, since `__init__` is not allowed to return a
 value .

-- 
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] #16209: Add alternative repositories to 'Installing the development version' in the docs.

[Django]

#16209: Add alternative repositories to 'Installing the development version' in 
the
docs.
-+---
   Reporter:  ShawnMilo  |  Owner:  ShawnMilo
   Type:  Uncategorized  | Status:  new
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+---
Changes (by ShawnMilo):

 * owner:  nobody => ShawnMilo


-- 
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] #16199: Create a secure cookie-based session backend

[Django]

#16199: Create a secure cookie-based session backend
-+-
   Reporter:  floguy |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.sessions
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by aaugustin):

 (not marking as Accepted because this is a large change and I haven't seen
 a decision by a core developer yet)

-- 
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] #16199: Create a secure cookie-based session backend

[Django]

#16199: Create a secure cookie-based session backend
-+-
   Reporter:  floguy |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.sessions
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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-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] #16198: model_forms tests are still doctests.

[Django]

#16198: model_forms tests are still doctests.
-+-
   Reporter: |  Owner:  nobody
  gregmuellegger | Status:  new
   Type: |  Component:  Testing framework
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:  model_forms,
Version:  1.3|  doctests
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


-- 
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] #16208: natural key YAML deserialization using non-list natural keys broken (with fixing patch)

[Django]

#16208: natural key YAML deserialization using non-list natural keys broken 
(with
fixing patch)
+--
   Reporter:  jeff.k@…  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Core (Serialization)
Version:  1.2   |   Severity:  Normal
 Resolution:|   Keywords:  yaml
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+--
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 1
 * stage:  Unreviewed => Accepted


Comment:

 I just attached a patch in the proper format, identical to the first one
 otherwise.

 Jeff, could you provide an example of your problem? That would really help
 us reproduce it, and write a test case.

-- 
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] #16209: Add alternative repositories to 'Installing the development version' in the docs.

[Django]

#16209: Add alternative repositories to 'Installing the development version' in 
the
docs.
-+---
   Reporter:  ShawnMilo  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Milestone: |  Component:  Documentation
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+---
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
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] #16207: UserProfile documentation (not extensive enough)

[Django]

#16207: UserProfile documentation (not extensive enough)
--+---
   Reporter:  foxwhisper  |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Accepted|  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Yes, illustrating the text with code samples would help. The link to the
 Django Book may become redundant, then.

-- 
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] #16190: django.views.debug.technical_500_response() not much helpful for AJAX request

[Django]

#16190: django.views.debug.technical_500_response() not much helpful for AJAX
request
-+-
   Reporter:  zimnyx |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Core (Other)
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  1  |
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Core (Other)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * ui_ux:  0 => 1
 * 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-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] #15775: Can't enter scientific notation in decimal fields

[Django]

#15775: Can't enter scientific notation in decimal fields
+
   Reporter:  gregthe1  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Forms
Version:  1.2   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
Changes (by samufuentes):

 * needs_tests:  1 => 0


Comment:

 The second file includes 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] #16205: Beginners install guide for Windows

[Django]

#16205: Beginners install guide for Windows
---+--
   Reporter:  erlingbo |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Documentation
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:  install, windows
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by aaugustin):

 * needs_docs:   => 0
 * needs_better_patch:   => 1
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Setting "patch needs improvement" because the attachement is not actually
 a patch. This file must be added in `docs`, and linked to from other
 pages.

 IMO https://docs.djangoproject.com/en/dev/topics/install/ is an
 appropriate entry point.

-- 
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] #16202: Localflavor support for Slovenia (si)

[Django]

#16202: Localflavor support for Slovenia (si)
-+-
   Reporter:  Jure   |  Owner:  nobody
  Cuhalev | Status:  new
   Type:  New|  Component:  contrib.localflavor
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
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] #16204: Remove unused functions in admin core.js (getCorrectYear and getISODate).

[Django]

#16204: Remove unused functions in admin core.js (getCorrectYear and 
getISODate).
-+-
   Reporter:  mbraak |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I confirm the functions are no longer used.

-- 
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] #16203: 'servers' test fails on Windows

[Django]

#16203: 'servers' test fails on Windows
---+---
   Reporter:  intelliyole  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Milestone:   |  Component:  Uncategorized
Version:  1.3  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Should os.path.normcase should be added in the code, as suggested by the
 patch, or in the test case?

-- 
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] #11989: Allow @register.inclusion_tag to take a template as well as a template name

[Django]

#11989: Allow @register.inclusion_tag to take a template as well as a template 
name
-+-
   Reporter:  jdunck |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  1.1|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by danielquinn):

 * cc: danielquinn (added)
 * stage:  Accepted => Ready for checkin


Comment:

 I applied his patch and it passed the tests and then checked out the
 result in the documentation.  All looks good to me.

-- 
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] #8161: ManyToManyField with relation to self not saved in admin when using inheritance

[Django]

#8161: ManyToManyField with relation to self not saved in admin when using
inheritance
-+-
   Reporter:  Mathijs|  Owner:  ojii
  de Bruin   | Status:  closed
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  invalid|   Keywords:  newforms newforms-
   Triage Stage:  Accepted   |  admin admin inheritance manytomany
Needs documentation:  0  |  self
Patch needs improvement:  0  |  Has patch:  0
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ojii):

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


Comment:

 can't reproduce, ran both admin and the python code.

-- 
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] #16128: cascade delete does not work for proxy models

[Django]

#16128: cascade delete does not work for proxy models
-+-
   Reporter:  xkennyx@…  |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  cascade delete
Needs documentation:  0  |  proxy meta
Patch needs improvement:  0  |  Has patch:  0
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by Jarek):

 * cc: Jarek (added)


Comment:

 sorry, previous comment was mistage (I cannot delete 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] #16031: Custom comment form is incomplete and wrong.

[Django]

#16031: Custom comment form is incomplete and wrong.
-+-
   Reporter:  ddshore@…  |  Owner:  teraom
   Type: | Status:  assigned
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-

Comment (by aaugustin):

 Could you make your patch relative to the `trunk` directory of the svn
 repo? Like this: `cd trunk; svn di > your_patch.diff`.

 We expect to be able to apply it with `cd trunk; patch -p0 <
 your_patch.diff` (or -p1 if you're using git).

 Also, when you upload a new patch that take into account the reviewers'
 remarks, you can uncheck "patch needs improvement".

 Thanks!

-- 
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] #11989: Allow @register.inclusion_tag to take a template as well as a template name

[Django]

#11989: Allow @register.inclusion_tag to take a template as well as a template 
name
---+-
   Reporter:  jdunck   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Template system
Version:  1.1  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+-
Changes (by tcoenen):

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


Comment:

 I updated the patch to apply to the current Django. The patch
 inclusion_template2.diff now includes documentation and tests for this new
 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-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] #15077: Error in documentation for running Django on a shared-hosting provider with Apache

[Django]

#15077: Error in documentation for running Django on a shared-hosting provider 
with
Apache
-+-
   Reporter:  MarkusH|  Owner:  Horst Gutmann
   Type:  Bug|  
  Milestone: | Status:  new
Version:  1.2|  Component:  Documentation
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  htaccess
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by Horst Gutmann ):

 * 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-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] #16201: When Content-Length is 0, MultiPartParser violates RFC2616

[Django]

#16201: When Content-Length is 0, MultiPartParser violates RFC2616
-+-
   Reporter:  albsen |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  HTTP handling
Version:  1.3-rc1|   Severity:  Normal
 Resolution: |   Keywords:  http multipart
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by russellm):

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


Comment:

 The change being proposed here makes Django's HTTP implementation RFC
 compliant -- content-length == 0 is explicitly given as an allowed length.
 The fact that we have historically rejected content-length == 0 is a bug,
 not something that needs to be document.

-- 
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] #6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()

[Django]

#6422: Support for 'DISTINCT ON' queries with QuerySet.distinct()
-+-
   Reporter:  Manfred|  Owner:  nobody
  Wassmann | Status:  new
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-

Comment (by jgelens):

 True, fixing the things you mentioned

-- 
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] #8161: ManyToManyField with relation to self not saved in admin when using inheritance

[Django]

#8161: ManyToManyField with relation to self not saved in admin when using
inheritance
-+-
   Reporter:  Mathijs|  Owner:  ojii
  de Bruin   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  newforms newforms-
   Triage Stage:  Accepted   |  admin admin inheritance manytomany
Needs documentation:  0  |  self
Patch needs improvement:  0  |  Has patch:  0
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ojii):

 * owner:  nobody => ojii
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #16128: cascade delete does not work for proxy models

[Django]

#16128: cascade delete does not work for proxy models
-+-
   Reporter:  xkennyx@…  |  Owner:  nobody
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  cascade delete
Needs documentation:  0  |  proxy meta
Patch needs improvement:  0  |  Has patch:  0
  UI/UX:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by xkennyx@…):

 * ui_ux:   => 0


Comment:

 There is one funny thing, I need also a way to invocate the bug :) Eg.
 delete child but do not delete parent. This is now possible with
 inheriting from proxy model, but after fixing .. is there way ?

-- 
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] #16209: Add alternative repositories to 'Installing the development version' in the docs.

[Django]

#16209: Add alternative repositories to 'Installing the development version' in 
the
docs.
---+---
 Reporter:  ShawnMilo  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Documentation
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+---
 https://docs.djangoproject.com/en/dev/topics/install/#installing-
 development-version

 The current page only refers to the subversion repo, but there are
 official github and bitbucket repos which some users will find more
 convenient.

-- 
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] #4212: badly-defined ForeignKey to self does not cause an exception

[Django]

#4212: badly-defined ForeignKey to self does not cause an exception
-+-
   Reporter:  Forest |  Owner:  ojii
  Bond | Status:  closed
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  invalid|   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by ojii):

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


Comment:

 Can't reproduce this issue, works fine for me.

-- 
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] #16135: Model 'Child' is inherited from 'Parent', expecting to get only Child results with Parent.objects.filter(child__isnull=False), but does not work.

[Django]

#16135: Model 'Child' is inherited from 'Parent', expecting to get only Child
results with Parent.objects.filter(child__isnull=False), but does not work.
-+-
   Reporter:  robin  |  Owner:  desh
   Type:  Bug| Status:  assigned
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by desh):

 * owner:  nobody => desh
 * status:  new => assigned
 * ui_ux:   => 0


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

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

Re: [Django] #16185: Allow to override TEST_RUNNER setting with a command-line option to 'manage.py 'test'

[Django]

#16185: Allow to override TEST_RUNNER setting with a command-line option to
'manage.py 'test'
-+-
   Reporter: |  Owner:  nobody
  intelliyole| Status:  new
   Type:  New|  Component:  Testing framework
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  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] #5450: save_m2m should raise an exception for unsaved models

[Django]

#5450: save_m2m should raise an exception for unsaved models
-+-
   Reporter:  Øyvind |  Owner:  ojii
  Saltvik  | Status:  closed
   Type: |  Component:  Database layer
  Cleanup/optimization   |  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution:  invalid|  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ojii):

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


Comment:

 Closed this issue with the wrong resolution, it wasn't fixed but rather
 the proposed solution (raising an exception) is already there.

-- 
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] #5450: save_m2m should raise an exception for unsaved models

[Django]

#5450: save_m2m should raise an exception for unsaved models
-+-
   Reporter:  Øyvind |  Owner:  ojii
  Saltvik  | Status:  reopened
   Type: |  Component:  Database layer
  Cleanup/optimization   |  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by ojii):

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


-- 
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] #4212: badly-defined ForeignKey to self does not cause an exception

[Django]

#4212: badly-defined ForeignKey to self does not cause an exception
-+-
   Reporter:  Forest |  Owner:  ojii
  Bond | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by ojii):

 * owner:  nobody => ojii
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #15077: Error in documentation for running Django on a shared-hosting provider with Apache

[Django]

#15077: Error in documentation for running Django on a shared-hosting provider 
with
Apache
-+-
   Reporter:  MarkusH|  Owner:  Horst Gutmann
   Type:  Bug|  
  Milestone: | Status:  new
Version:  1.2|  Component:  Documentation
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  htaccess
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by Horst Gutmann ):

 * owner:  nobody => Horst Gutmann 
 * ui_ux:   => 0
 * easy:   => 0


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

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

Re: [Django] #10933: Avoid " TypeError: Cannot convert Decimal("0.0000") to Decimal " when the decimal module has been reloaded

[Django]

#10933: Avoid " TypeError: Cannot convert Decimal("0.") to Decimal  " when 
the
decimal module has been reloaded
-+-
   Reporter:  gagravarr  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  dceu2011
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  1
  UI/UX:  0  |  Easy pickings:  0
-+-

Comment (by willhardy):

 This is a problem when you combine `isinstance` with reload. Because we
 can't avoid using `isinstance` in the decimal model, I've created a new
 decimal object when `TypeError` is raised, using the `as_tuple()`.

-- 
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] #10933: Avoid " TypeError: Cannot convert Decimal("0.0000") to Decimal " when the decimal module has been reloaded

[Django]

#10933: Avoid " TypeError: Cannot convert Decimal("0.") to Decimal  " when 
the
decimal module has been reloaded
-+-
   Reporter:  gagravarr  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  dceu2011
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  1
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by willhardy):

 * keywords:   => dceu2011
 * needs_better_patch:  1 => 0
 * ui_ux:   => 0


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

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

Re: [Django] #5831: Template Debug highlights wrong {% for %} tag

[Django]

#5831: Template Debug highlights wrong {% for %} tag
-+-
   Reporter:  Charmless  |  Owner:  vladmos
   | Status:  new
   Type:  Bug|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  debug for toplevel
 Resolution: |  nesting
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by vladmos):

 Chanded order if and try..except statements. Now try..except is performed
 only when settings.TEMPLATE_DEBUG is true, so it shouldn't slower
 rendering with debugger disabled.

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

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

Re: [Django] #5831: Template Debug highlights wrong {% for %} tag

[Django]

#5831: Template Debug highlights wrong {% for %} tag
-+-
   Reporter:  Charmless  |  Owner:  vladmos
   | Status:  new
   Type:  Bug|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  debug for toplevel
 Resolution: |  nesting
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-

Comment (by vladmos):

 Chanded order if and try..except statements. Now try..except is performed
 only when settings.TEMPLATE_DEBUG is true, so it shouldn't slower
 rendering with debugger disabled.

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

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

Re: [Django] #16197: Rewrite contrib auth to use class based views

[Django]

#16197: Rewrite contrib auth to use class based views
-+-
   Reporter:  hvdklauw   |  Owner:  hvdklauw
   Type: | Status:  new
  Cleanup/optimization   |  Component:  contrib.auth
  Milestone:  1.4|   Severity:  Normal
Version:  SVN|   Keywords:  dceu2011
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by hvdklauw):

 * stage:  Design decision needed => Accepted


Comment:

 After talking with Russel and Alex we decided there was no nice way to do
 this, except in the same way the admin urls handling was changed before.
 Alex has some idea's for a Class Based View Collection which basically is
 a class with class based views that handles the urls.

 We'll look into it some more

-- 
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] #16031: Custom comment form is incomplete and wrong.

[Django]

#16031: Custom comment form is incomplete and wrong.
-+-
   Reporter:  ddshore@…  |  Owner:  teraom
   Type: | Status:  assigned
  Cleanup/optimization   |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  1  |
  UI/UX:  0  |
-+-

Comment (by danielquinn):

 After talking to one of the Elder Nerds here at DjangoCon, we agreed that
 the {% csrf_token %} should be in there, so I've added a new 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-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] #16155: Drop support for Python 2.4

[Django]

#16155: Drop support for Python 2.4
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  closed
  Cleanup/optimization   |  Component:  Documentation
  Milestone:  1.4|   Severity:  Release blocker
Version:  1.3|   Keywords:
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 In [16349]:
 {{{
 #!CommitTicketReference repository="" revision="16349"
 Fixed #16155 -- Removed Python 2.4 compatibility constructs from code and
 mentions from docs. Thanks Aymeric Augustin for the report and 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-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.

[Changeset] r16349 - in django/trunk: . django/core/cache django/db/backends/oracle django/db/models django/http django/utils django/utils/translation docs/faq docs/internals/contributing/writing-cod

[noreply]

Author: ramiro
Date: 2011-06-09 13:01:28 -0700 (Thu, 09 Jun 2011)
New Revision: 16349

Modified:
   django/trunk/INSTALL
   django/trunk/django/core/cache/__init__.py
   django/trunk/django/db/backends/oracle/base.py
   django/trunk/django/db/models/base.py
   django/trunk/django/http/__init__.py
   django/trunk/django/utils/hashcompat.py
   django/trunk/django/utils/http.py
   django/trunk/django/utils/itercompat.py
   django/trunk/django/utils/translation/trans_real.py
   django/trunk/docs/faq/install.txt
   django/trunk/docs/internals/contributing/writing-code/branch-policy.txt
   django/trunk/docs/intro/install.txt
   django/trunk/docs/ref/contrib/gis/install.txt
   django/trunk/docs/releases/1.4.txt
   django/trunk/docs/topics/db/transactions.txt
   django/trunk/docs/topics/install.txt
   django/trunk/docs/topics/logging.txt
   django/trunk/docs/topics/testing.txt
   django/trunk/tests/regressiontests/admin_scripts/tests.py
   django/trunk/tests/regressiontests/httpwrappers/tests.py
Log:
Fixed #16155 -- Removed Python 2.4 compatibility constructs from code and 
mentions from docs. Thanks Aymeric Augustin for the report and patch.

Modified: django/trunk/INSTALL
===
--- django/trunk/INSTALL2011-06-09 19:35:44 UTC (rev 16348)
+++ django/trunk/INSTALL2011-06-09 20:01:28 UTC (rev 16349)
@@ -1,6 +1,6 @@
 Thanks for downloading Django.
 
-To install it, make sure you have Python 2.4 or greater installed. Then run
+To install it, make sure you have Python 2.5 or greater installed. Then run
 this command from the command prompt:
 
 python setup.py install
@@ -9,8 +9,9 @@
 site-packages directory, which is located wherever your Python installation
 lives. Some places you might check are:
 
+/usr/lib/python2.7/site-packages (Unix, Python 2.7)
+/usr/lib/python2.6/site-packages (Unix, Python 2.6)
 /usr/lib/python2.5/site-packages (Unix, Python 2.5)
-/usr/lib/python2.4/site-packages (Unix, Python 2.4)
 C:\\PYTHON\site-packages (Windows)
 
 For more detailed instructions, see docs/intro/install.txt.

Modified: django/trunk/django/core/cache/__init__.py
===
--- django/trunk/django/core/cache/__init__.py  2011-06-09 19:35:44 UTC (rev 
16348)
+++ django/trunk/django/core/cache/__init__.py  2011-06-09 20:01:28 UTC (rev 
16349)
@@ -29,8 +29,7 @@
 # Python 2.6 and greater
 from urlparse import parse_qsl
 except ImportError:
-# Python 2.5, 2.4.  Works on Python 2.6 but raises
-# PendingDeprecationWarning
+# Python 2.5.  Works on Python 2.6 but raises PendingDeprecationWarning
 from cgi import parse_qsl
 
 __all__ = [

Modified: django/trunk/django/db/backends/oracle/base.py
===
--- django/trunk/django/db/backends/oracle/base.py  2011-06-09 19:35:44 UTC 
(rev 16348)
+++ django/trunk/django/db/backends/oracle/base.py  2011-06-09 20:01:28 UTC 
(rev 16349)
@@ -176,12 +176,6 @@
 # classes to normalize values from the database (the to_python
 # method is used for validation and isn't what we want here).
 elif isinstance(value, Database.Timestamp):
-# In Python 2.3, the cx_Oracle driver returns its own
-# Timestamp object that we must convert to a datetime class.
-if not isinstance(value, datetime.datetime):
-value = datetime.datetime(value.year, value.month,
-value.day, value.hour, value.minute, value.second,
-value.fsecond)
 if field and field.get_internal_type() == 'DateTimeField':
 pass
 elif field and field.get_internal_type() == 'DateField':

Modified: django/trunk/django/db/models/base.py
===
--- django/trunk/django/db/models/base.py   2011-06-09 19:35:44 UTC (rev 
16348)
+++ django/trunk/django/db/models/base.py   2011-06-09 20:01:28 UTC (rev 
16349)
@@ -915,10 +915,5 @@
 return cls.__new__(cls)
 model_unpickle.__safe_for_unpickle__ = True
 
-if sys.version_info < (2, 5):
-# Prior to Python 2.5, Exception was an old-style class
-def subclass_exception(name, parents, unused):
-return types.ClassType(name, parents, {})
-else:
-def subclass_exception(name, parents, module):
-return type(name, parents, {'__module__': module})
+def subclass_exception(name, parents, module):
+return type(name, parents, {'__module__': module})

Modified: django/trunk/django/http/__init__.py
===
--- django/trunk/django/http/__init__.py2011-06-09 19:35:44 UTC (rev 
16348)
+++ django/trunk/django/http/__init__.py2011-06-09 20:01:28 UTC (rev 
16349)
@@ -17,13 +17,12 @@
 # Python 2.6 and greater