Re: [Django] #16260: Ability to change dismissRelatedLookupPopup on custom callback function

[Django]

#16260: Ability to change dismissRelatedLookupPopup on custom callback function
--+
 Reporter:  alekam|Owner:  alekam
 Type:  New feature   |   Status:  assigned
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  admin javascript  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+

Comment (by julien):

 I'm not entirely sold on the implementation but I do want to include this
 new feature. So I'll chew on it a bit more. In the meantime I've the patch
 to apply to current 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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bruth):

 I am sure everyone has mused over this many times, but this is a quick
 outline I came up with, derived from my use case including the primary
 goals, and a few scenarios/setups with a list of possible solutions (best
 first).

 - Goals
   - ability to use a non-default schema given the backend
   - transparently route models to their respective schemas given a
 database
   - handle schema creation (?, on the fence about this)
 - Scenarios
- single database, one schema
  - use the database backend default schema (out-of-box)
  - override the `DATABASES['default']['SCHEMA']`
  - override `DEFAULT_SCHEMA` in settings (this is kind of silly to
 have since it's ''so'' simple to define the schema in the database
 settings above)
  - define each model's `db_schema` meta option (in my mind, this is
 only really useful for models that are not intended to be reusable outside
 a company/guidlines/etc.)
   - single database, multiple schemas
 - define a router that implements `schema_for_db` which returns a
 valid schema name or `None` if no preference
   - takes a `model`, `db`, and `**hints`
   - in case there is some funky setup where a separate set of database
 settings is not enough, this provides a generic solution which allows re-
 use of models/app regardless of the database structure, nothing hard-coded
 on the models themselves
 - set each model's `db_schema` meta option for ones not in the default
 schema (garbage)
   - multiple databases
 - non-issue since schemas do not span across databases

-- 
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] #18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's cursor

[Django]

#18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's
cursor
--+
 Reporter:  reames@…  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 A little bit of context: I'm trying to run django 1.4 on Google AppEngine
 using CloudSQL, vanilla django 1.4 (and pytz) are in my project directory.

 So, in theory, I should be able to use django unmodified. Not the case
 I've found. I was getting a traceback when doing syncdb to
 "last_executed_query" in the mysql backend.

 My workaround, or fix as it may be, is to change around line 238 in
 db/backends/mysql/base.py
 from
 {{{
 #!python
 def last_executed_query(self, cursor, sql, params):
 # With MySQLdb, cursor objects have an (undocumented)
 "_last_executed"
 # attribute where the exact query sent to the database is saved.
 # See MySQLdb/cursors.py in the source distribution.
 return cursor._last_executed
 }}}
 to
 {{{
 #!python
 def last_executed_query(self, cursor, sql, params):
 # With MySQLdb, cursor objects have an (undocumented)
 "_last_executed"
 # attribute where the exact query sent to the database is saved.
 # See MySQLdb/cursors.py in the source distribution.
 return getattr(cursor, '_last_executed', None)
 }}}

-- 
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] #18591: Missing crucial info in Apache conf (httpd.conf) to serve static files

[Django]

#18591: Missing crucial info in Apache conf (httpd.conf) to serve static files
-+-
 Reporter:  rschuon@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  Apache, mod-wsgi,|  Unreviewed
  uWSGI, Static, Media   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by msopacua):

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


Comment:

 Replying to [ticket:18591 rschuon@…]:

 > Also, the line:
 >
 > {{{
 > Alias /static/ /usr/local/wsgi/static/
 > }}}
 >
 > Should actually look like this:
 >
 > {{{
 > Alias /static /usr/local/wsgi/static/
 > }}}
 >
 > Without the trailing slash on the alias.

 That's incorrect. It ''should'' have the slash. Read up on mod_speling if
 you want a directory listing without having to type an extra slash, but
 the correct way is to map the trailing slash to the directory.

-- 
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] #18537: Error in calculation of check digit in ARCUITField

[Django]

#18537: Error in calculation of check digit in ARCUITField
-+-
 Reporter:  mmoya@…  |Owner:
 Type:  Bug  |  foxyNinja7
Component:  contrib.localflavor  |   Status:  assigned
 Severity:  Normal   |  Version:  1.4
 Keywords:  ARCUITField, |   Resolution:
  localflavor.ar | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by foxyNinja7):

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


-- 
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] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by seanl):

 * cc: sean@… (added)


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

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

Re: [Django] #18574: `BaseFormSet.is_valid` should call it's underlying forms' `is_valid`

[Django]

#18574: `BaseFormSet.is_valid` should call it's underlying forms' `is_valid`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  form formset | Triage Stage:  Accepted
  is_valid   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by charettes):

 Here's the workaround I use while this is not fixed:
 {{{#!python

 from django.forms.formsets import BaseFormSet


 class BaseValidateFormSet(BaseFormSet):

 def is_valid(self):
 is_valid = super(BaseValidateFormSet, self).is_valid()
 for form in self:
 is_valid &= form.is_valid() or (self.can_delete and
 self._should_delete_form(form))
 return is_valid

 }}}

-- 
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] #11263: Bug in lookup with generic relation in model inheritance

[Django]

#11263: Bug in lookup with generic relation in model inheritance
-+-
 Reporter:  veena|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  generic relations,   |  Needs documentation:  1
  model inheritance  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by jaklaassen):

 There are two separate issues:

  * The original reporter's issue with invalid SQL
  * The issue raised by nator with filtering concrete model subclasses
 based on a generic relation in the parent.

 Patch is here: https://github.com/jaklaassen/django/compare/ticket_11263

 The original issue appears to be fixed in trunk and the patch includes a
 passing test for this.

 The second issue happens because the incorrect content_type_id is used in
 the query.
 This is still happening in trunk, and is fixed by 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] #9245: Using choices in a mode field forces use of TypedChoiceField in a form field

[Django]

#9245: Using choices in a mode field forces use of TypedChoiceField in a form
field
+
 Reporter:  Tarken  |Owner:  badri
 Type:  Bug |   Status:  reopened
Component:  Forms   |  Version:  1.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by dgouldin):

 * cc: dgouldin (added)


Comment:

 Julien, this patch will not work as-is. Your new Field.choices_formfield
 function is called from Field.formfield using **defaults, but defaults
 will never include form_class. This means that Field.choices_formfield
 will always be called with its default value for form_class (None unless
 overridden by a custom Field subclass) even when the user's intent was to
 provide a custom form_class for that model field. So for this model:

 {{{
 class Foo(models.Model):
 bar = models.IntegerField(choices=bar_choices,
 form_class=MyCustomFormClass)
 }}}

 MyCustomFormClass would never make it to bar's Field.choices_formfield,
 and so an instance of it would not be returned by Field.formfield.

 However, it also not work to simply call
 self.choices_formfield(form_class=form_class, **defaults) from
 Field.formfield. Subclasses of Field (such as IntegerField) frequently
 override formfield() and call super's formfield() with a form_class kwarg.
 This means that calling Field.choices_formfield with Field.formfield's
 form_class would break models like this:


 {{{
 class Foo(models.Model):
 bar = models.IntegerField(choices=bar_choices)
 }}}

 In this case, IntegerField.formfield would call Field.formfield with
 form_class=forms.IntegerField, which would then be passed through to
 Field.choices_formfield, causing forms.TypedChoiceField not to be used as
 was intended.

 As the implementation sits currently, Field has no way to determine
 whether the intent of the user was to specify their own form_class or
 whether the Field subclass injected its own form_class before calling
 Field.formfield. This is broken, plain and simple. In order for
 Field.formfield to make a good decision about which class to use when
 instantiating a form field, it needs both pieces of information: the model
 field's default form_class, and the user's override of that default (if
 provided). Here's the solution I propose:

 {{{
 class Field(object):
 default_form_class = forms.CharField

 # ...

 def formfield(self, form_class=None, **kwargs):
 if self.choices:
 form_class = form_class or forms.TypedChoiceField
 # ...
 else:
 form_class = form_class or self.default_form_class


 class IntegerField(Field):
 default_form_class = forms.IntegerField
 }}}

 This allows Field.formfield to have both pieces of information, and it
 alleviates the need for IntegerField to override formfield. It is not
 backwards compatible, as any model field subclasses which use this
 formfield override approach would need to be changed to fit the new
 default_form_class property approach.

-- 
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] #18591: Missing crucial info in Apache conf (httpd.conf) to serve static files

[Django]

#18591: Missing crucial info in Apache conf (httpd.conf) to serve static files
-+-
 Reporter:  rschuon@…|  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.4
Component:  Documentation|   Keywords:  Apache, mod-wsgi,
 Severity:  Normal   |  uWSGI, Static, Media
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Your page:
 https://docs.djangoproject.com/en/1.3/howto/deployment/modwsgi/

 To get Apache to be able to serve files statically, the handler (mod-wsgi,
 or uWSGI) must be disabled for those folders.  So, you need another
 directive under the ones you list, that looks like this:
 {{{
 
 SetHandler default-handler
 
 }}}

 I believe the /static location directive must occur after the / Location
 directive to turn the handler off correctly.
 This allows the request to be caught by Apache rather than uWSGI, and
 redirected to the static file folder.

 Also, the line:

 {{{
 Alias /static/ /usr/local/wsgi/static/
 }}}

 Should actually look like this:

 {{{
 Alias /static /usr/local/wsgi/static/
 }}}

 Without the trailing slash on the alias.

-- 
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] #17978: Minor layout issue when an inline contains a filter horizontal widget

[Django]

#17978: Minor layout issue when an inline contains a filter horizontal widget
---+
 Reporter:  aaugustin  |Owner:  julien
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 Julien Phalip ):

 In [9a2ca4266ad3a58af7db3ecbf9b99270519bb8f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a2ca4266ad3a58af7db3ecbf9b99270519bb8f2"
 [1.4.x] Fixed #17978 -- Fixed a minor layout issue when an inline contains
 a filter horizontal widget. Thanks to Aymeric Augustin for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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/django] 9a2ca4: [1.4.x] Fixed #17978 -- Fixed a minor layout issue...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 9a2ca4266ad3a58af7db3ecbf9b99270519bb8f2
  
https://github.com/django/django/commit/9a2ca4266ad3a58af7db3ecbf9b99270519bb8f2
  Author: Julien Phalip 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M django/contrib/admin/static/admin/css/widgets.css

  Log Message:
  ---
  [1.4.x] Fixed #17978 -- Fixed a minor layout issue when an inline contains a 
filter horizontal widget. Thanks to Aymeric Augustin for the report.



-- 
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] #17978: Minor layout issue when an inline contains a filter horizontal widget

[Django]

#17978: Minor layout issue when an inline contains a filter horizontal widget
---+
 Reporter:  aaugustin  |Owner:  julien
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:  fixed
 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 Julien Phalip ):

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


Comment:

 In [8015593bc1f2f226e7979bfdee8b7e88658d0e74]:
 {{{
 #!CommitTicketReference repository=""
 revision="8015593bc1f2f226e7979bfdee8b7e88658d0e74"
 Fixed #17978 -- Fixed a minor layout issue when an inline contains a
 filter horizontal widget. Thanks to Aymeric Augustin for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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/django] 801559: Fixed #17978 -- Fixed a minor layout issue when an...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8015593bc1f2f226e7979bfdee8b7e88658d0e74
  
https://github.com/django/django/commit/8015593bc1f2f226e7979bfdee8b7e88658d0e74
  Author: Julien Phalip 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M django/contrib/admin/static/admin/css/widgets.css

  Log Message:
  ---
  Fixed #17978 -- Fixed a minor layout issue when an inline contains a filter 
horizontal widget. Thanks to Aymeric Augustin for the report.



-- 
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] #18072: ChangeList shouldn't use hardcoded urls

[Django]

#18072: ChangeList shouldn't use hardcoded urls
--+
 Reporter:  kmike |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.4
 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 julien):

 * type:  Uncategorized => Cleanup/optimization


-- 
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] #18568: django admin interface not behaving properly in firefox.

[Django]

#18568: django admin interface not behaving properly in firefox.
-+-
 Reporter:  chs2048@…|Owner:  Chris2048
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.3-rc1
 Severity:  Normal   |   Resolution:
 Keywords:  django firefox IE| Triage Stage:
  admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by julien):

 I'm afraid I can't reproduce this. Your code samples were incomplete so
 I've made some guesses and used the following:

 {{{#!python
 # models.py

 from django.db import models

 class Role(models.Model):
 name = models.CharField(max_length=255)

 class Group(models.Model):
 name = models.CharField(max_length=255)

 class UserRoleClientGroupMembership(models.Model):
 group = models.ForeignKey('Group')
 user = models.ForeignKey('User')

 class UserRoleClientMembership(models.Model):
 role = models.ForeignKey('Role')
 user = models.ForeignKey('User')

 class User(models.Model):
 user_name = models.CharField(max_length=1024)
 roles = models.ManyToManyField(Role,
 through='UserRoleClientMembership')
 def __unicode__(self):
 return self.user_name


 # admin.py

 from django.contrib import admin
 from models import *

 class UserRoleClientMembershipInline(admin.TabularInline):
 model = UserRoleClientMembership
 extra = 1

 class UserRoleClientGroupMembershipInline(admin.TabularInline):
 model = UserRoleClientGroupMembership
 extra = 1

 class UserAdmin(admin.ModelAdmin):
 inlines = [UserRoleClientMembershipInline,
 UserRoleClientGroupMembershipInline]

 admin.site.register(User, UserAdmin)
 }}}

 Could you please provide more specific code samples and instructions to
 reproduce the problem?

-- 
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] #18511: Admin Site: Error Message displays different for Changeforms and the Password Change screen.

[Django]

#18511: Admin Site: Error Message displays different for Changeforms and the
Password Change screen.
-+-
 Reporter:  serge_spaolonzi  |Owner:
 Type:   |  serge_spaolonzi
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 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:  1
-+-

Comment (by julien):

 Thank you, the patch looks good. However, I'm wondering, why have two
 different variables (`content_title` and `title`)? Can't we just have one
 that is used both in `` and ``?

-- 
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] #18164: startapp error: no such option

[Django]

#18164: startapp error: no such option
--+
 Reporter:  nikita@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 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 Claude Paroz ):

 In [fd88fe657b42cf314bcd23bf79edf71c378520f4]:
 {{{
 #!CommitTicketReference repository=""
 revision="fd88fe657b42cf314bcd23bf79edf71c378520f4"
 [1.4.x] Fixed #18164 -- Precised startapp template context content

 Backport of 249c445446 from master.
 }}}

-- 
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/django] fd88fe: [1.4.x] Fixed #18164 -- Precised startapp template...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: fd88fe657b42cf314bcd23bf79edf71c378520f4
  
https://github.com/django/django/commit/fd88fe657b42cf314bcd23bf79edf71c378520f4
  Author: Claude Paroz 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.4.x] Fixed #18164 -- Precised startapp template context content

Backport of 249c445446 from master.



-- 
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] #18467: Login in from admin logout page should not logout again

[Django]

#18467: Login in from admin logout page should not logout again
---+
 Reporter:  etienned   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by julien):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Yes that's right, that's what I meant :)

-- 
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] #18164: startapp error: no such option

[Django]

#18164: startapp error: no such option
--+
 Reporter:  nikita@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 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 Claude Paroz ):

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


Comment:

 In [249c445446f0811d6396cfd3053aed33edf2e7b3]:
 {{{
 #!CommitTicketReference repository=""
 revision="249c445446f0811d6396cfd3053aed33edf2e7b3"
 Fixed #18164 -- Precised startapp template context content
 }}}

-- 
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/django] 249c44: Fixed #18164 -- Precised startapp template context...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 249c445446f0811d6396cfd3053aed33edf2e7b3
  
https://github.com/django/django/commit/249c445446f0811d6396cfd3053aed33edf2e7b3
  Author: Claude Paroz 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  Fixed #18164 -- Precised startapp template context content



-- 
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] #8363: Make it possible to specify tests to skip when running runtests.py

[Django]

#8363: Make it possible to specify tests to skip when running runtests.py
---+
 Reporter:  ramiro |Owner:  ramiro
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  master
 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
---+

Comment (by julien):

 I think this would actually need some deeper refactoring of the test
 discovery system to make it work more like other frameworks (e.g. pytest,
 nose). I think carljm and alex have got some initial thoughts on that. It
 would be a pretty large effort, but one that would solve many problems at
 once by doing things right.

-- 
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] #13299: Handicapped objects passed to models signals during loaddata

[Django]

#13299: Handicapped objects passed to models signals during loaddata
---+
 Reporter:  patrys |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.2-beta
 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 julien):

 See also #8399 which suggests adding a new `pre_loaddata ` signal.

-- 
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] #8399: loaddata management command should provide option to disable signals

[Django]

#8399: loaddata management command should provide option to disable signals
-+-
 Reporter:  chrisdpratt@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   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|
-+-

Comment (by julien):

 See also #13299 which suggests to document `raw=True` in the `loaddata`
 doc.

-- 
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] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
-+-
 Reporter:  aaugustin|Owner:  httpdss
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.syndication  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 If there's a patch attached, no need to add an identical pull request.
 There is no more value (and no less) in a pull request than an attached
 patch. Personally, I will always push the patch myself until Github
 supports fast-forward merges.

-- 
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] #18112: contrib.syndication.views: Add hook for getting extra context in feed templates

[Django]

#18112: contrib.syndication.views: Add hook for getting extra context in feed
templates
-+
 Reporter:  slinkp   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+

Comment (by slinkp):

 I can see how this is confusing.
 Those names were not chosen by me, they are in the current implementation,
 as the old part of the diff shows.


 If you look in the local scope of where I'm invoking this method, the old
 implementation
 has these :


   `obj` -  the object returned by get_object().

This was not being made available to the templates; I added it as the
 'obj' kwarg
to get_context_data(), which by default ignores it; but I'm passing it
 so at least it's possible to use it
in your subclass if you want.

   `item` - the current feed item from this iteration of obj.items().
This was already being made available to the template context as, very
 unfortunately, 'obj'.
That kind of sucks, as it's easy to confuse with the one returned by
 get_object().
But it *has* to be named 'obj' in the template context or we'll break
 existing templates.


 Any thoughts on how to make this less confusing without breaking backward
 compatibility?

-- 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bruth):

 @akaariai just an FYI I forked your repo and am attempting to fix these
 issues myself. The latter issue I mention above seems to be more deeply
 rooted in that the ```sql*``` commands seem to not take in account
 database routers (since it is not technically a ```syncdb``` command).
 This is further confusing since the ```sql*``` commands take a
 ```--database``` parameter. Your concern above regarding third-party apps
 could be resolved by users defining a router. The ```db_for_*``` methods
 are suitable since multiple database entries can be defined for simply
 defining separate schemas.

 I am going to give integrating the database routers a whack.

-- 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bruth):

 @akaariai Thanks for the patch! I have a project where I have multiple
 schemas and some of the tables have foreign keys between them. My
 environment consists of PostgreSQL and my settings contain multiple
 entries in ``DATABASES`` with their own schema defined (as suppose to
 hard-coded schemas in the model ``Meta`` classes). I ran the ``./manage.py
 sqlall`` command and noticed a couple things:

 - there are redundant ``CREATE SCHEMA`` statements before each ``CREATE
 TABLE``
 - foreign keys to tables from other schemas do not output the correct
 schema

-- 
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] #17257: Comment that contradicts code in django.contrib.syndication.views

[Django]

#17257: Comment that contradicts code in django.contrib.syndication.views
-+-
 Reporter:  aaugustin|Owner:  httpdss
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.syndication  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by httpdss):

 this same patch was contributed by me 2 months ago with a pull request
 https://github.com/django/django/pull/63 ...
 what kind of workflow are you using?

 Replying to [comment:12 Claude Paroz ]:
 > In [8dafd04c45a66ff60f0503da1ebea14628322b45]:
 > {{{
 > #!CommitTicketReference repository=""
 revision="8dafd04c45a66ff60f0503da1ebea14628322b45"
 > Fixed #17257 - Removed outdated comment in syndication view
 >
 > Thanks krzysiumed 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] #18245: Error in documentation of date based generic views

[Django]

#18245: Error in documentation of date based generic views
---+-
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+-

Comment (by mateusgondim):

 Oh ok, 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] #18590: Remove workaround for a Python 2.4 bug in Model.__reduce__

[Django]

#18590: Remove workaround for a Python 2.4 bug in Model.__reduce__
-+-
 Reporter:  konk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by konk):

 Actually, what I meant was that someone should test against 2.6 on Mac to
 make sure 2.6 is no longer affected…

-- 
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] #18590: Remove workaround for a Python 2.4 bug in Model.__reduce__

[Django]

#18590: Remove workaround for a Python 2.4 bug in Model.__reduce__
-+-
 Reporter:  konk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by charettes):

 All tests passes on Python 2.7.3rc1 - SQLite here as well.

 @konk I think we're dropping Python 2.5 support for 1.5?

-- 
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] #18590: Remove workaround for a Python 2.4 bug in Model.__reduce__

[Django]

#18590: Remove workaround for a Python 2.4 bug in Model.__reduce__
-+-
 Reporter:  konk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by konk):

 Passes here as well. We still need someone to verify it passes on Mac;
 according to #12121, on the bug was present in the Mac version of 2.5.

-- 
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] #11688: verbose_name should allow dynamical translation based on a number

[Django]

#11688: verbose_name should allow dynamical translation based on a number
--+
 Reporter:  mitar |Owner:  nobody
 Type:  New feature   |   Status:  reopened
Component:  Internationalization  |  Version:  1.1
 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 sirex):

 * cc: sirexas@… (added)
 * needs_better_patch:  0 => 1


Comment:

 I just merged this patch with latest master branch, result is committed to
 cloned branch at https://github.com/sirex/django

 All tests passes.

 I'm planning to look at this issue more in details, test it more deeply.
 Also, I'm planning to extend it not only to support multiple plural forms,
 but also different model name forms by context where model name is used.
 For example, Lithuanian language (same with Russian), has 7 noun forms,
 each form is used depending on context, for example „Add book“ in
 Lithuanian is displayed as „Pridėti knyga“ (in first form), but instead,
 second form should be used: „Pridėti knygą“. Without these forms, Django
 admin looks really corrupted.

 I'm planning to fix these context issues by using pgettext:
 https://docs.djangoproject.com/en/dev/topics/i18n/translation/#contextual-
 markers

-- 
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] #18374: ImageField not validating due to missing libraries

[Django]

#18374: ImageField not validating due to missing libraries
-+-
 Reporter:  fabian@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * 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] #18374: ImageField not validating due to missing libraries

[Django]

#18374: ImageField not validating due to missing libraries
-+-
 Reporter:  fabian@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 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] #18590: Remove workaround for a Python 2.4 bug in Model.__reduce__

[Django]

#18590: Remove workaround for a Python 2.4 bug in Model.__reduce__
-+-
 Reporter:  konk |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 Sure, less code is better. Attached patch passes all tests on Python 2.6 -
 SQLite.

-- 
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] #18523: Add getvalue to HttpResponse

[Django]

#18523: Add getvalue to HttpResponse
---+
 Reporter:  claudep|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 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 claudep):

 I think http://docs.python.org/library/io.html?highlight=stream#io.IOBase
 lists basic API for streams.

-- 
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] #18356: Test Client response does not contain Context with nested requests

[Django]

#18356: Test Client response does not contain Context with nested requests
-+-
 Reporter:  bmihelac |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by bmihelac):

 Accidentally posted this as anonymous.

-- 
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] #18377: Django Hanging with older Pylibmc

[Django]

#18377: Django Hanging with older Pylibmc
---+
 Reporter:  andrew@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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 aaugustin):

 I suppose it's https://github.com/lericson/pylibmc/issues/34, which is a
 duplicate of https://github.com/lericson/pylibmc/pull/19.

 This is the "Fixed GIL issues" item of version 1.2.0.  So the requirement
 would be pylibmc >= 1.2.

 I don't know exactly how often the problem happens. Is it systematic under
 mod_wsgi?

-- 
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] #18377: Django Hanging with older Pylibmc

[Django]

#18377: Django Hanging with older Pylibmc
---+
 Reporter:  andrew@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Do you know which version of pylibmc fixed the problem?

 If this issue is well documented, we could add a check on the version of
 pylibmc and refuse to start with a buggy version.

-- 
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] #18404: SuspiciousOperation exception is thrown if application static path contains non-ascii characters

[Django]

#18404: SuspiciousOperation exception is thrown if application static path 
contains
non-ascii characters
-+-
 Reporter:  andkit@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by jezdez):

 I can't reproduce the problem, can you provide a test case demonstrating
 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] #18374: ImageField not validating due to missing libraries

[Django]

#18374: ImageField not validating due to missing libraries
--+
 Reporter:  fabian@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 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 aaugustin):

 I just attached a proposal. What do you think?

-- 
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] #18374: ImageField not validating due to missing libraries

[Django]

#18374: ImageField not validating due to missing libraries
--+
 Reporter:  fabian@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 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


Comment:

 Well, this won't help debug the issue when it happens in production. I'm
 going to improve the docs a bit.

-- 
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] #18468: Define COMMENT in table / colomns

[Django]

#18468: Define COMMENT in table / colomns
-+-
 Reporter:  mrechte  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by niwi):

 I understand your opinion! In any case, I'll write an email to the list
 which I think is useful.
 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] #18577: Undocumented lazy middleware initialization

[Django]

#18577: Undocumented lazy middleware initialization
-+-
 Reporter:  makuro@… |Owner:
 Type:  Bug  |  LukaszBalcerzak
Component:  Documentation|   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:  middleware,  |   Resolution:
  settings   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

 * 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] #18523: Add getvalue to HttpResponse

[Django]

#18523: Add getvalue to HttpResponse
---+
 Reporter:  claudep|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 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


Comment:

 Good idea.

 Do Python's docs provide a list of the methods that a "stream object" must
 support? While we're there, we should also check that HttpRequest objects
 support all the methods that make sense.

-- 
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] #18567: readonly_fields for ModelForms

[Django]

#18567: readonly_fields for ModelForms
-+--
 Reporter:  Lacrymology  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by aaugustin):

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


Comment:

 Duplicate of #17031.

-- 
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] #18581: Admin actions documentation needs a new screenshot

[Django]

#18581: Admin actions documentation needs a new screenshot
---+
 Reporter:  msopacua   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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 claudep):

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


Comment:

 There are 3 images on
 https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/

 Am I bikeshedding or should we have a similar look for those images?

-- 
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] #18569: Enable L expressions in `queryset.extra`

[Django]

#18569: Enable L expressions in `queryset.extra`
-+-
 Reporter:  jbzdak@… |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 `extra` often creates more problem than it solves. The current trend is to
 deprecate it rather than extend it.

 The recommended way to achieve your goal is to use raw SQL.

-- 
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] #18552: Django test client should not use MULTIPART_CONTENT for POST-requests by default.

[Django]

#18552: Django test client should not use MULTIPART_CONTENT for POST-requests by
default.
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 I don't see how this is a problem either.

-- 
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] #18589: Typo in class-based generic views doc

[Django]

#18589: Typo in class-based generic views doc
--+
 Reporter:  cpthomas@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  documentation, typo   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [d94cfdcfae92fd4409cd1b5e14eebc75033266fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="d94cfdcfae92fd4409cd1b5e14eebc75033266fd"
 Fixed #18589 -- Typo in generic CBV docs.

 Thanks cpthomas for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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/django] d94cfd: Fixed #18589 -- Typo in generic CBV docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d94cfdcfae92fd4409cd1b5e14eebc75033266fd
  
https://github.com/django/django/commit/d94cfdcfae92fd4409cd1b5e14eebc75033266fd
  Author: Aymeric Augustin 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/topics/class-based-views/generic-display.txt

  Log Message:
  ---
  Fixed #18589 -- Typo in generic CBV docs.

Thanks cpthomas for the report.



-- 
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] #18589: Typo in class-based generic views doc

[Django]

#18589: Typo in class-based generic views doc
--+
 Reporter:  cpthomas@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  documentation, typo   | 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] #18081: Proxy model foreign keys not created properly by syncdb

[Django]

#18081: Proxy model foreign keys not created properly by syncdb
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 charettes):

 * cc: charette.s@… (added)


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

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

Re: [Django] #18588: Django-Python instalation error on django-admin.py (init.py options = filter(lambda (x, v): x not in prev_opts, options)-syntax error

[Django]

#18588: Django-Python instalation error on django-admin.py (init.py options =
filter(lambda (x,v): x not in prev_opts, options)-syntax error
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 Trac isn't a support forum — see TicketClosingReasons/UseSupportChannels

 You might be using a version of Python that isn't supported by 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.

[Django] #18590: Remove workaround for a Python 2.4 bug in Model.__reduce__

[Django]

#18590: Remove workaround for a Python 2.4 bug in Model.__reduce__
--+
 Reporter:  konk  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 `Model.__reduce__` contains a workaround for a buggy implementation of
 pickling/unpickling where calling `super(Model, self).__reduce__()`
 resulted in infinite recursion.

 With Python 2.6 and 2.7 this seems no longer to be relevant, which means
 the workaround can probably be removed.

-- 
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] #18169: NoReverseMatch silenced in template Variable

[Django]

#18169: NoReverseMatch silenced in template Variable
+
 Reporter:  jasisz  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Template system |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  template exception  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by aaugustin):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Design decision needed => 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] #11929: manage.py dumpdata outputs YAML in unhelpful order

[Django]

#11929: manage.py dumpdata outputs YAML in unhelpful order
-+-
 Reporter:  sampablokuper|Owner:
 Type:  Bug  |  ladyrassilon
Component:  Core |   Status:  new
  (Serialization)|  Version:  1.1
 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 ladyrassilon):

 * owner:  nobody => ladyrassilon


-- 
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] #18356: Test Client response does not contain Context with nested requests

[Django]

#18356: Test Client response does not contain Context with nested requests
-+-
 Reporter:  bmihelac |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 Changeset that fixes this issue is:

 
https://github.com/bmihelac/django-1/commit/86a374e4d149b9a11aedc69753ce91b46669d16e

 (branch has test case and fix)

 BTW, i found this issue while trying to fix django-test-utils, which has
 middleware that records context for every request made. Testing that
 necessarily leads to nesting requests in 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] #18581: Admin actions documentation needs a new screenshot

[Django]

#18581: Admin actions documentation needs a new screenshot
-+-
 Reporter:  msopacua |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by riquito):

 * cc: riccardo@… (added)
 * stage:  Accepted => Ready for checkin


Comment:

 New screenshot uploaded

-- 
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] #18589: Typo in class-based generic views doc

[Django]

#18589: Typo in class-based generic views doc
--+-
 Reporter:  cpthomas@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  documentation, typo
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+-
 On this page: https://docs.djangoproject.com/en/dev/topics/class-based-
 views/generic-display/, under the Dynamic Filtering heading, there is a
 typo in the 3rd code example

 PublisherBookListView should be PublisherBookList to match the previous
 code examples.

 Existing:
 {{{
 def get_context_data(self, **kwargs):
 # Call the base implementation first to get a context
 context = super(PublisherBookListView,
 self).get_context_data(**kwargs)
 # Add in the publisher
 context['publisher'] = self.publisher
 return context

 }}}

 Revised:

 {{{
 # ...

 def get_context_data(self, **kwargs):
 # Call the base implementation first to get a context
 context = super(PublisherBookList, self).get_context_data(**kwargs)
 # Add in the publisher
 context['publisher'] = self.publisher
 return context
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #18588: Django-Python instalation error on django-admin.py (init.py options = filter(lambda (x, v): x not in prev_opts, options)-syntax error

[Django]

#18588: Django-Python instalation error on django-admin.py (init.py options =
filter(lambda (x,v): x not in prev_opts, options)-syntax error
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I am having issues when running the django-admin.py startptoject
 newproject method on windows 7:

 Specificaly-the error relates to the init.py file, where a syntaxt error
 is registered on line 327 (after the a in Lambda and on brackets on x):

 (init.py options = filter(lambda (x,v): x not in prev_opts, options)

  Please make my day and provide the solution,.

  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] #18169: NoReverseMatch silenced in template Variable

[Django]

#18169: NoReverseMatch silenced in template Variable
-+-
 Reporter:  jasisz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  template exception   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * stage:  Unreviewed => Design decision needed


Comment:

 I tried the attached code and I got the reported exception.

-- 
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] #18384: KyngChaos section of GeoDjango instructions is confusing

[Django]

#18384: KyngChaos section of GeoDjango instructions is confusing
---+
 Reporter:  AnnaPS |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 OK — it's a minor change.

-- 
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/django] bbc590: Removed Django 1.0-specific sections.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bbc590697a8cde2faf067b124d08fe9488db4905
  
https://github.com/django/django/commit/bbc590697a8cde2faf067b124d08fe9488db4905
  Author: Aymeric Augustin 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/ref/contrib/gis/install.txt
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Removed Django 1.0-specific sections.



-- 
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] #18365: remind in the "set languages redirection view" that the i18n template context processor should be set

[Django]

#18365: remind in the "set languages redirection view" that the i18n template
context processor should be set
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 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
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Indeed, this is necessary to put `LANGUAGES` in the context.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #18419: Language code is not correct for Chinese

[Django]

#18419: Language code is not correct for Chinese
-+-
 Reporter:  Olli Wang|Owner:  nobody
     |   Status:  new
 Type:  Bug  |  Version:  1.4
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  i18n, chinese, zh|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 I'm going to accept this ticket, but we need a good plan to address
 backwards compatibility before this can move forward.

 You could start a discussion on the django-i18n mailing list to get more
 input.

-- 
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] #18360: Database router example improvement

[Django]

#18360: Database router example improvement
--+
 Reporter:  sbaechler |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  multiple database | 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


Comment:

 I agree that the class name is misleading.

-- 
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] #18356: Test Client response does not contain Context with nested requests

[Django]

#18356: Test Client response does not contain Context with nested requests
-+-
 Reporter:  bmihelac |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Design decision needed


Comment:

 Well, the test client wasn't designed to be used from within a view.

 Could you show us the patch that would fix this problem?

-- 
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] #18158: Mix FormView with ListView functionality

[Django]

#18158: Mix FormView with ListView functionality
---+--
 Reporter:  emyller|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Generic views  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 The generic class based views aren't intended to be arbitrarily combinable
 blocks. Rather, they're ready-to-use examples for trivial cases. This is
 [https://docs.djangoproject.com/en/dev/topics/class-based-views/generic-
 display/#extending-generic-views explained in the documentation].

-- 
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] #18521: Add appropriate reST role to templates named in view docs

[Django]

#18521: Add appropriate reST role to templates named in view docs
-+-
 Reporter:  benspaulding |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  contrib.admindocs|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  admindocs|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 The pull request was merged in 8855f9380e93d759eea93c32cdf25b76b72e15c4.

-- 
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] #18587: Error in example code for custom management commands

[Django]

#18587: Error in example code for custom management commands
---+
 Reporter:  frankwiles |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  0
UI/UX:  0  |
---+

Comment (by Aymeric Augustin ):

 In [f1e416566a2e09f25b75a379f31a71962fa66437]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1e416566a2e09f25b75a379f31a71962fa66437"
 [1.4x] Fixed #18587 -- Typo in management command example

 Thanks Frank Wiles.

 Backport of 29ca3d3c4b3d330337cce8713196ef7eea956dc9 from master.
 }}}

-- 
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/django] f1e416: [1.4x] Fixed #18587 -- Typo in management command ...

[GitHub]

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: f1e416566a2e09f25b75a379f31a71962fa66437
  
https://github.com/django/django/commit/f1e416566a2e09f25b75a379f31a71962fa66437
  Author: Aymeric Augustin 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/howto/custom-management-commands.txt

  Log Message:
  ---
  [1.4x] Fixed #18587 -- Typo in management command example

Thanks Frank Wiles.

Backport of 29ca3d3c4b3d330337cce8713196ef7eea956dc9 from master.



-- 
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] #18587: Error in example code for custom management commands

[Django]

#18587: Error in example code for custom management commands
---+
 Reporter:  frankwiles |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  1.4
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by Aymeric Augustin ):

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


Comment:

 In [29ca3d3c4b3d330337cce8713196ef7eea956dc9]:
 {{{
 #!CommitTicketReference repository=""
 revision="29ca3d3c4b3d330337cce8713196ef7eea956dc9"
 Fixed #18587 -- Typo in management command example

 Thanks Frank Wiles.
 }}}

-- 
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/django] 29ca3d: Fixed #18587 -- Typo in management command example

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 29ca3d3c4b3d330337cce8713196ef7eea956dc9
  
https://github.com/django/django/commit/29ca3d3c4b3d330337cce8713196ef7eea956dc9
  Author: Aymeric Augustin 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M docs/howto/custom-management-commands.txt

  Log Message:
  ---
  Fixed #18587 -- Typo in management command example

Thanks Frank Wiles.



-- 
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] #13867: Feature request: Comments in Django models saved to database schema

[Django]

#13867: Feature request: Comments in Django models saved to database schema
-+-
 Reporter:  rjalves  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 #18468 is a duplicate with 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.

Re: [Django] #18468: Define COMMENT in table / colomns

[Django]

#18468: Define COMMENT in table / colomns
-+-
 Reporter:  mrechte  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This is a duplicate of #13867, which lingered in DDN for two years until I
 wontfix'd it.

 The only argument I've seen is "it'd be nice if...". But I'm against
 adding features to Django just because we can; there must be a use case.

 Could you start a thread on the mailing-list, as recommended in the
 [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/#requesting-features contributing guide], to see if there is
 support for this idea?

 If there's a good explanation of why you need this, I can reconsider my
 decision.

-- 
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] #6517: manage.py dbshell does not get charset from database_options

[Django]

#6517: manage.py dbshell does not get charset from database_options
-+-
 Reporter:  tvrg |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jpichon):

 * cc: julie@… (added)


Comment:

 I adapted tvrg's patch to the current codebase -
 https://github.com/jpichon/django/compare/ticket_6517

 I also tested dbshell with the sqlite3 and postgresql backends, and it
 works with UTF-8 characters without patching.

 There are other ways to get the MySQL backend to play nicely with UTF-8
 that don't require changing the code. You can add "default-character-set =
 utf8" to /etc/mysql/my.cnf on the server side, or create an option file
 with the UTF-8 charset config and update the settings to point to it in
 the "read_default_file" database options (as seen on
 https://docs.djangoproject.com/en/dev/ref/databases/#connecting-to-the-
 database)

 {{{
 [client]
 default-character-set = utf8
 }}}

 If the patch option is preferred, I'm happy to work on the tests if
 someone could let me know where the dbshell tests live.

-- 
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/django] 52a9e1: Fixed a regression in the user admin page introduc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 52a9e15794ac050afb17837a34407722e7249854
  
https://github.com/django/django/commit/52a9e15794ac050afb17837a34407722e7249854
  Author: Florian Apolloner 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M django/contrib/auth/forms.py

  Log Message:
  ---
  Fixed a regression in the user admin page introduced in 
a92e7f37c4ae84b6b8d8016cc6783211e9047219.

a92e7f37c4ae84b6b8d8016cc6783211e9047219 switched most of the internal stuff
to format_html. Using format_html in the `render` method of
`ReadOnlyPasswordHashWidget` caused it to generate `SafeString` instances.
Later these safe strings where returned from `BoundField.__unicode__` which
caused force_unicode to loose the "safe" information. This commit fixes that by
ensuring that the render method returns `SafeUnicode` instead of `SafeString`.


  Commit: a4bb7dd552cf9e45cdd0b38938b18c576419fd8d
  
https://github.com/django/django/commit/a4bb7dd552cf9e45cdd0b38938b18c576419fd8d
  Author: Florian Apolloner 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M django/contrib/staticfiles/templatetags/staticfiles.py
M django/templatetags/static.py
M docs/ref/contrib/staticfiles.txt
M docs/ref/templates/builtins.txt
M tests/regressiontests/staticfiles_tests/tests.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Merge branch 'master' of github.com:django/django


Compare: https://github.com/django/django/compare/0a68a2994be1...a4bb7dd552cf

-- 
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] #18254: Add support for `as ` to the staticfiles {% static %} template tag.

[Django]

#18254: Add support for `as ` to the staticfiles {% static %} template
tag.
-+
 Reporter:  melinath |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Jannis Leidel ):

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


Comment:

 In [0a68a2994be17ed2669accead331881cb0be41dd]:
 {{{
 #!CommitTicketReference repository=""
 revision="0a68a2994be17ed2669accead331881cb0be41dd"
 Fixed #18254 -- Added ability to the static template tags to store the
 result in a contextt variable. Many thanks to Andrei Antoukh for the
 initial 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.

[django/django] 0a68a2: Fixed #18254 -- Added ability to the static templa...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0a68a2994be17ed2669accead331881cb0be41dd
  
https://github.com/django/django/commit/0a68a2994be17ed2669accead331881cb0be41dd
  Author: Jannis Leidel 
  Date:   2012-07-07 (Sat, 07 Jul 2012)

  Changed paths:
M django/contrib/staticfiles/templatetags/staticfiles.py
M django/templatetags/static.py
M docs/ref/contrib/staticfiles.txt
M docs/ref/templates/builtins.txt
M tests/regressiontests/staticfiles_tests/tests.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Fixed #18254 -- Added ability to the static template tags to store the result 
in a contextt variable. Many thanks to Andrei Antoukh for the initial patch.



-- 
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] #13958: There is an error, when a source file with backslash-r returns is interpreted by the Python error report page.

[Django]

#13958: There is an error, when a source file with backslash-r returns is
interpreted by the Python error report page.
-+
 Reporter:  petrvanblokland  |Owner:  nessita
 Type:  Bug  |   Status:  reopened
Component:  Core (Other) |  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:  1|UI/UX:  0
-+

Comment (by riquito):

 Updated the patch and refactored the test 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] #18505: bad link from definitive guide to Dj web dev done right

[Django]

#18505: bad link from definitive guide to Dj web dev done right
-+-
 Reporter:  jacanterbury@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Djangoproject.com|   Resolution:  fixed
  Web site   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * component:  Uncategorized => Djangoproject.com Web site
 * version:  1.4 => master
 * type:  Uncategorized => Cleanup/optimization


-- 
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] #18505: bad link from definitive guide to Dj web dev done right

[Django]

#18505: bad link from definitive guide to Dj web dev done right
+
 Reporter:  jacanterbury@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Uncategorized   |  Version:  1.4
 Severity:  Normal  |   Resolution:  fixed
 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):

 * status:  new => closed
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => fixed
 * stage:  Unreviewed => Accepted


Comment:

 I just added a redirect. Thanks for the report.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #18490: Datefield input format options don't match the docs

[Django]

#18490: Datefield input format options don't match the docs
---+
 Reporter:  david@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  date input format  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by aaugustin):

 * has_patch:  0 => 1


Comment:

 Yes, it is, but don't forget to set the "has patch" flag.

-- 
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] #18587: Error in example code for custom management commands

[Django]

#18587: Error in example code for custom management commands
---+
 Reporter:  frankwiles |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Pretty self explanatory, but the example code uses 'self' in the class
 definition.

-- 
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] #18577: Undocumented lazy middleware initialization

[Django]

#18577: Undocumented lazy middleware initialization
-+-
 Reporter:  makuro@… |Owner:
 Type:  Bug  |  LukaszBalcerzak
Component:  Documentation|   Status:  assigned
 Severity:  Normal   |  Version:  1.3
 Keywords:  middleware,  |   Resolution:
  settings   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by LukaszBalcerzak):

 * 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] #18487: CachedStaticFilesStorage raises an exception when trying to deal with a url() starting with //

[Django]

#18487: CachedStaticFilesStorage raises an exception when trying to deal with a
url() starting with //
-+-
 Reporter:  kitsunde |Owner:
 Type:  Bug  |  LukaszBalcerzak
Component:  contrib.staticfiles  |   Status:  assigned
 Severity:  Normal   |  Version:  1.4
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by LukaszBalcerzak):

 * status:  new => assigned
 * 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] #18490: Datefield input format options don't match the docs

[Django]

#18490: Datefield input format options don't match the docs
---+
 Reporter:  david@…|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  date input format  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+

Comment (by david@…):

 Is a Github pull request sufficient as a patch?

 https://github.com/django/django/pull/191

-- 
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] #17549: Add link to open URL from URLField

[Django]

#17549: Add link to open URL from URLField
---+
 Reporter:  gcc|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  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:  1
---+
Changes (by UloPe):

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


Comment:

 I've turned the ad-hoc code in the description into a proper patch for
 AdminURLFieldWidget and added tests as well as a short mention of this new
 feature in the docs.

 Code at: https://github.com/django/django/pull/190

-- 
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] #18081: Proxy model foreign keys not created properly by syncdb

[Django]

#18081: Proxy model foreign keys not created properly by syncdb
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (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 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] #18112: contrib.syndication.views: Add hook for getting extra context in feed templates

[Django]

#18112: contrib.syndication.views: Add hook for getting extra context in feed
templates
-+
 Reporter:  slinkp   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.syndication  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by aaugustin):

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


Comment:

 I don't really understand the `obj` vs. `item` dance; could you clarify
 why you chose this implementation?

 Otherwise, this looks like a good idea.

-- 
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] #18088: Add a "supports_foreign_key" database feature to ease testing

[Django]

#18088: Add a "supports_foreign_key" database feature to ease testing
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Design decision needed


Comment:

 Sqlite 3.6.19 was released nearly three years ago. Debian stable ships
 Sqlite 3.7.3.

 Shouldn't we at some point:
 - have a minimal version requirement for Sqlite,
 - deprecate support for MySQL + MyISAM,
 and support only "sane" databases -- that is, databases that enforce
 foreign keys?

 This is well beyond the scope of this ticket, but I'm not thrilled by the
 idea of adding code to deal with broken databases. Make that a -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] #10504: Consistency between HttpResponse* params and render_to_response

[Django]

#10504: Consistency between HttpResponse* params and render_to_response
--+
 Reporter:  bhagany   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  reopened
Component:  HTTP handling |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * status:  closed => reopened
 * needs_better_patch:  0 => 1
 * resolution:  invalid =>


Comment:

 In [da200c5e35cd], we didn't address the `render_to_response`
 inconsistency, so I think that the attached patch still makes sense. We
 should however introduce a deprecation path for the mimetype argument
 also.

-- 
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] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
--+
 Reporter:  konk  |Owner:  judy2k
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  unit tests| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by judy2k):

 * owner:  anonymous => judy2k
 * status:  assigned => new


Comment:

 Last attempt to get the status of this ticket correct.

-- 
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] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  unit tests   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by judy2k):

 * owner:  judy2k => anonymous
 * status:  new => assigned
 * 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] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:  judy2k
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  unit tests   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by judy2k):

 * owner:  anonymous => judy2k
 * status:  assigned => new


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #18586: Rewrite unit tests migrated from doctests

[Django]

#18586: Rewrite unit tests migrated from doctests
-+-
 Reporter:  konk |Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  unit tests   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by anonymous):

 * owner:  nobody => anonymous
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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.