[Django] #21990: ePub docs for 1.7a2 not valid?

[Django]

#21990: ePub docs for 1.7a2 not valid?
---+
 Reporter:  michal@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm trying to upload latest Django docs in ePub format to my Google Books
 but the import fails. Recommended online validator
 (http://validator.idpf.org/) shows errors in the ePub file. I didn't have
 this problem with docs for 1.7a1.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.dae33215d78d9a460aefaa38f6bb1002%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20784: RegexValidator should accept a new parameter to perform reversed validation

[Django]

#20784: RegexValidator should accept a new parameter to perform reversed 
validation
+
 Reporter:  devfeng |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Core (Other)|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  RegexValidator  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by devfeng):

 Replying to [comment:7 devfeng]:
 > Replying to [comment:6 timo]:
 > > Patch needs updating to merge cleanly.
 >
 > https://github.com/django/django/pull/2243

 PR updated per Tim's comments.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0b62777242508d163473b07703c63d59%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #27: Single form field for multiple database fields

[Django]

#27: Single form field for multiple database fields
-+-
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

 * ui_ux:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e7f356c145b351daf6584a09309a72ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #27: Single form field for multiple database fields

[Django]

#27: Single form field for multiple database fields
-+-
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by anonymous):

 * ui_ux:  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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.dc816d6ecb4d4097e889948db4240e7a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21989: AU locale has incorrect Day Of Week

[Django]

#21989: AU locale has incorrect Day Of Week
+
   Reporter:  russellm  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Internationalization  |Version:  1.6
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 The newly added AU locale sets FIRST_DAY_OF_WEEK to Monday.
 FIRST_DAY_OF_WEEK is primarily used to render calendars, and calendars in
 AU almost universally start weeks with Sunday.

 Opening this as a ticket rather than just fixing it because of the
 inevitable backlash.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.5fdcc1c1630bad763859097f30a3d177%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

[Django]

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by albertyw@…):

 * needs_better_patch:  1 => 0


Comment:

 Made patch pep8.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.1ed8014dae284ab034dcc77f5591c786%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21986: The documentation provides no indication as to why you might want to use indexes

[Django]

#21986: The documentation provides no indication as to why you might want to use
indexes
--+
 Reporter:  django-issues@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 django-issues@…):

 * cc: django-issues@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.753c33ef50b82303195ce71522b26e67%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21988: reverse() shouldn't require kwargs for uniquely determined named groups

[Django]

#21988: reverse() shouldn't require kwargs for uniquely determined named groups
-+--
 Reporter:  cjerdonek|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 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 cjerdonek):

 * cc: chris.jerdonek@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3cc58d8581704387ec859079fefceb13%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21988: reverse() shouldn't require kwargs for uniquely determined named groups

[Django]

#21988: reverse() shouldn't require kwargs for uniquely determined named groups
-+
 Reporter:  cjerdonek|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Core (URLs)  |Version:  1.6
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 For DRY purposes, it can be useful to capture a known substring in an URL
 for access from a view.  For example--

 {{{
 url(r'^(?Pcreate)/confirm/$', ConfirmCreateView.as_view(),
 name='confirm_create')
 url(r'^(?Pchange)/confirm/$', ConfirmChangeView.as_view(),
 name='confirm_change')
 }}}

 Calling `reverse()` for examples like the above still requires passing the
 keyword argument though (`action='create'` or `action='change'` in these
 examples), even though the value of the keyword argument isn't necessary
 to construct the corresponding URL.  This makes calling `reverse()` less
 DRY than it needs to be.

 I would like to suggest making `reverse()` not require the keyword
 arguments in cases where the corresponding named groups have only one
 possible value.  If this isn't possible to add, are there any suggestions
 for a DRY way to accomplish the same thing?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.57fa0f458055451157e5fd44e21cffb2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19373: Windows file locking requires pywin32

[Django]

#19373: Windows file locking requires pywin32
--+
 Reporter:  techtonik |Owner:  marfire
 Type:  Cleanup/optimization  |   Status:  closed
Component:  File uploads/storage  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Kevin Christopher Henry ):

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


Comment:

 In [changeset:"6fe26bd3ee75a6d804ca3861181ad61b1cca45ea"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6fe26bd3ee75a6d804ca3861181ad61b1cca45ea"
 Fixed #19373 -- Ported Windows file locking from PyWin32 to ctypes

 There wasn't any file locking under Windows unless PyWin32 was
 installed. This removes that (undocumented) dependency by using ctypes
 instead.

 Thanks to Anatoly Techtonik for writing the ctypes port upon which this
 is based.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.273518a00527f42cf4725d2ffd63ca51%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6fe26b: Fixed #19373 -- Ported Windows file locking from P...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6fe26bd3ee75a6d804ca3861181ad61b1cca45ea
  
https://github.com/django/django/commit/6fe26bd3ee75a6d804ca3861181ad61b1cca45ea
  Author: Kevin Christopher Henry 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/core/files/locks.py
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed #19373 -- Ported Windows file locking from PyWin32 to ctypes

There wasn't any file locking under Windows unless PyWin32 was
installed. This removes that (undocumented) dependency by using ctypes
instead.

Thanks to Anatoly Techtonik for writing the ctypes port upon which this
is based.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f6a5815657f_26307ddd4076017%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19966: Allow for silent or conditional loading of custom template tags

[Django]

#19966: Allow for silent or conditional loading of custom template tags
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 This would also help for the common requirement of loading `{% static %}`
 from `staticfiles` when it's available, from Django's default tags when it
 isn't.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c6fade8ee6f3b2d66581d93d94403a76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20377: BinaryField doesn't work on MySQL and Python 3

[Django]

#20377: BinaryField doesn't work on MySQL and Python 3
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Someday/Maybe
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 The solution may be #12500: Support for MySQL Connector/Python.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3bbe997276898ef8cda186487db214da%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20380: MySQL doesn't support dates below 1000 on Python 3.2

[Django]

#20380: MySQL doesn't support dates below 1000 on Python 3.2
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Someday/Maybe
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 The solution may be #12500: Support for MySQL Connector/Python.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3ffd7fa929bcf8f1ebcb7f9152e9d922%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20196: Better support for folder uploads

[Django]

#20196: Better support for folder uploads
-+-
 Reporter:  jonash   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Someday/Maybe
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:

 I still believe an external app is the way to go, at least at first.
 Please reopen if some code in Django needs to be changed to make this
 possible.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.96b77f66927271d2cce53c6874dc62e9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13663: Foreign Key to table in another database fails

[Django]

#13663: Foreign Key to table in another database fails
-+-
 Reporter:  berto|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.448d4eee8afe58afea2d3c284f3b0683%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13412: Exposing multiple db in admin interface is limited

[Django]

#13412: Exposing multiple db in admin interface is limited
---+-
 Reporter:  idle   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.2-beta
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Someday/Maybe
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:

 This ticket doesn't contain a actionable proposal.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.9bf6063f35642bd3eb548a2eff40f0ff%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14180: Creating redundant indexes on foreign keys for MySQL/InnoDB tables

[Django]

#14180: Creating redundant indexes on foreign keys  for MySQL/InnoDB tables
-+-
 Reporter:  zimnyx   |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.2
Component:  Database layer   |   Resolution:
  (models, ORM)  | 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):

 * stage:  Someday/Maybe => 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7ae51d586502dc52e5c7698065cef551%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8896: Routing according also to hostname

[Django]

#8896: Routing according also to hostname
-+-
 Reporter:  veena|Owner:  jshedd
 Type:  New feature  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  routing hostname | Triage Stage:
Has patch:  0|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This has been solved by external apps and I'm happy with that solution.

 Django should remain focused on the mainstream use cases.

 This one isn't unheard of, but it's hardly common.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.24214a179519e2fa26859073454d2b6e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11029: Model mocking support

[Django]

#11029: Model mocking support
-+-
 Reporter:  Almad|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  1.1-beta
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
Has patch:  0|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 This idea has been floating around for years. I'm not convinced it's
 useful to keep an open ticket without a concrete proposal.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.4969b8d677228f23127569debb79fb95%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13543: Enhancements to the Sitemaps Framework so it works better for large sites

[Django]

#13543: Enhancements to the Sitemaps Framework so it works better for large 
sites
-+-
 Reporter:  mlissner |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.sitemaps |  Version:  master
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
Has patch:  0|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Almost four years later, this still needs a concrete and actionable
 proposal.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ce4028a3ed31e3f27d8348a0aaf9c33a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7063: More robust debugging output for AJAX with simple print statements in debug.py

[Django]

#7063: More robust debugging output for AJAX with simple print statements in
debug.py
-+-
 Reporter:  fred.palmer@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ajax, debug, 500 | Triage Stage:
Has patch:  0|  Someday/Maybe
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Browser dev tools have improved a lot since this ticket was filed. Is it
 still relevant?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.17ee97ed16e23f182169b2ea4eb93ae3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #4991: contrib.admin does not escape help_text

[Django]

#4991: contrib.admin does not escape help_text
--+
 Reporter:  anonymous |Owner:  adrian
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  help_text escape  | 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):

 * component:  contrib.admin => Documentation
 * has_patch:  1 => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Someday/Maybe => Accepted


Comment:

 If we want to document the edge case on the edge of an edge case, we can
 do it now ;-)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.bb46c86a8199e4b6c0b60eddf8cc5ef5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20549: Refactor to take advantage of get_app_paths()

[Django]

#20549: Refactor to take advantage of get_app_paths()
-+-
 Reporter:  aaugustin|Owner:
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
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:   => wontfix


Comment:

 `get_app_paths()` was deprecated during the app-loading refactor. This
 isn't relevant any more.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.64beb940e943733219513a7e2f9f72fc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21902: Document search order for list_display

[Django]

#21902: Document search order for list_display
--+
 Reporter:  schrinaw@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  admin | 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):

 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.7275bcdfcd9319f0191b782ec80437af%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21969: Dependent apps do not handle fixture data properly when migration

[Django]

#21969: Dependent apps do not handle fixture data properly when migration
-+
 Reporter:  Ubercore |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.bba4c7afd80b0c9d7b86811455a9d560%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21968: Django doesn't detect initial migration when an app is a dependency

[Django]

#21968: Django doesn't detect initial migration when an app is a dependency
-+
 Reporter:  Ubercore |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.c5425b632fdc3950f3e178e9960ad723%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21955: Formset save_as_new=True causes "This QueryDict instance is immutable" error

[Django]

#21955: Formset save_as_new=True causes "This QueryDict instance is immutable"
error
+--
 Reporter:  robin   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 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):

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


Comment:

 Could you provide the full traceback please?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.54a37a2590c32379d097963ae93b951b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21896: makemigrations warning "trying to add a non-nullable field" is raised even when the table is empty

[Django]

#21896: makemigrations warning "trying to add a non-nullable field" is raised 
even
when the table is empty
-+-
 Reporter:  kunitoki |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 I agree with the first comment: this sounds fragile. I'm leaving the final
 say to Andrew.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a44363c4f23f8404b96199defbbfc04d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21841: Add DatabaseFeature to disable schema migrations

[Django]

#21841: Add DatabaseFeature to disable schema migrations
---+--
 Reporter:  manfre |Owner:
 Type:  New feature|   Status:  closed
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  schema migrations  | 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:   => wontfix


Comment:

 Mailing-list discussion: https://groups.google.com/d/msg/django-
 developers/Bo78V9UmbJI/h1ezPaaqCh8J

 If I remember correctly, the consensus was to reject this proposal. Thanks
 for bringing it up anyway!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.8aba4e4a35258bd4af70d0e87b0ce928%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21842: DatabaseFeature.max_index_name_length is redundant of DatabaseOperations.max_name_length

[Django]

#21842: DatabaseFeature.max_index_name_length is redundant of
DatabaseOperations.max_name_length
-+-
 Reporter:  manfre   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  schema migrations| Triage Stage:  Accepted
  database feature   |  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
 * severity:  Normal => Release blocker
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.57682f03cb5907b3b53dc7a26200b826%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21844: BaseDatabaseOperations.quote_parameter should be relocated to DatabaseSchemaEditor

[Django]

#21844: BaseDatabaseOperations.quote_parameter should be relocated to
DatabaseSchemaEditor
--+
 Reporter:  manfre|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  master
 Severity:  Release blocker   |   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
 * stage:  Unreviewed => Accepted
 * component:  Database layer (models, ORM) => Migrations
 * needs_tests:   => 0
 * needs_docs:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ceaa65ea1569d93a76c484af004b139b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21986: The documentation provides no indication as to why you might want to use indexes

[Django]

#21986: The documentation provides no indication as to why you might want to use
indexes
--+
 Reporter:  django-issues@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.c3ef0e705d3fcad44941c101517b4885%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21795: preserve_filter doesn't work on production server

[Django]

#21795: preserve_filter doesn't work on production server
---+--
 Reporter:  honyczek   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 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:  1
---+--
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.65cc444e6416ebe4ad88469c07610ff3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21906: dumpdata should not use router.allow_syncdb

[Django]

#21906: dumpdata should not use router.allow_syncdb
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.5
  commands)  |   Resolution:
 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
-+-

Comment (by aaugustin):

 Indeed, if `allow_syncdb` returns `False` for a given database and model,
 Django expects that this database will not contain a table storing
 instances of this model.

 I'm not particularly fond of the idea of renaming this method. Everyone
 would have to update its routers for a fairly small benefit.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.00d12af4f1d1aa9769e733c41bb62862%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21958: Migrations fail on adding ForeignKey field to User model

[Django]

#21958: Migrations fail on adding ForeignKey field to User model
-+---
 Reporter:  code22   |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-alpha-1
 Severity:  Release blocker  |   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
 * stage:  Unreviewed => Accepted
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This looks like a bug with swappable models.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6a7f799bfd86e5a6418930cb01b1eab1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21959: widthratio templatetag fails to handle NaN ratio

[Django]

#21959: widthratio templatetag fails to handle NaN ratio
-+-
 Reporter:  rmoe |Owner:  Aymeric
 Type:  Bug  |  Augustin 
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

 * status:  new => closed
 * owner:   => Aymeric Augustin 
 * resolution:   => fixed


Comment:

 In [changeset:"07ae47f7f8b5d5f80238ea3018163cad12917852"]:
 {{{
 #!CommitTicketReference repository=""
 revision="07ae47f7f8b5d5f80238ea3018163cad12917852"
 Fixed #21959 -- Handled Inf/NaN in widthratio tag.

 Thanks rmoe for the report and 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.b97c3c68681778f7dba4a3707150da37%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 07ae47: Fixed #21959 -- Handled Inf/NaN in widthratio tag.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 07ae47f7f8b5d5f80238ea3018163cad12917852
  
https://github.com/django/django/commit/07ae47f7f8b5d5f80238ea3018163cad12917852
  Author: Aymeric Augustin 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/template/defaulttags.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #21959 -- Handled Inf/NaN in widthratio tag.

Thanks rmoe for the report and the patch.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f68d475472f_24cfc33d402906b%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21959: widthratio templatetag fails to handle NaN ratio

[Django]

#21959: widthratio templatetag fails to handle NaN ratio
-+
 Reporter:  rmoe |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  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
-+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.80cae0056d3d23531008cb0d9b7f66fe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21928: updating .po files with 'django-admin.py makemessages' under windows with russian locale fail

[Django]

#21928: updating .po files with 'django-admin.py makemessages' under windows 
with
russian locale fail
-+-
 Reporter:  gurovic@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  Internationalization   |  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  encoding msgmerge| 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


Old description:

> django1.7, python 3.2, windows 7 64 bit russian
>
> ---
> I have Windows 7 Rus, default encoding is cp1251.
> If i have some translations in .po-file in russian (utf-8 encoding),
> and running makemessages again to add new phrases, it uses msgmerge.exe
> in function write_po_file,
> popen got output in cp1251 encoding instead utf-8 and crashes:
>
> Exception in thread Thread-63:
> Traceback (most recent call last):
>   File "c:\python32\lib\threading.py", line 740, in _bootstrap_inner
> self.run()
>   File "c:\python32\lib\threading.py", line 693, in run
> self._target(*self._args, **self._kwargs)
>   File "c:\python32\lib\subprocess.py", line 1013, in _readerthread
> buffer.append(fh.read())
>   File "c:\python32\lib\encodings\cp1251.py", line 23, in decode
> return codecs.charmap_decode(input,self.errors,decoding_table)[0]
> UnicodeDecodeError: 'charmap' codec can't decode byte 0x98 in position
> 1157: character maps to 
>
> Traceback (most recent call last):
>   File "c:\python32\Scripts\django-admin-script.py", line 9, in 
> load_entry_point('Django==1.7a1', 'console_scripts', 'django-
> admin')()
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\__init__.py", line
> 427, in execute_from_command_line
> utility.execute()
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\__init__.py", line
> 419, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\base.py", line
> 288, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\base.py", line
> 337, in execute
> output = self.handle(*args, **options)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\base.py", line
> 529, in handle
> return self.handle_noargs(**options)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\commands\makemessages.py",
> line 288, in handle_noargs
> self.write_po_file(potfile, locale)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\commands\makemessages.py",
> line 399, in write_po_file
> msgs, errors, status = popen_wrapper(args)
>   File "c:\python32\lib\site-
> packages\django-1.7a1-py3.2.egg\django\core\management\utils.py", line
> 25, in popen_wrapper
> output, errors = p.communicate()
>   File "c:\python32\lib\subprocess.py", line 813, in communicate
> return self._communicate(input)
>   File "c:\python32\lib\subprocess.py", line 1050, in _communicate
> stdout = stdout[0]
> IndexError: list index out of range
>
> popen runs for the following process:
> ['msgmerge', '-q',
> 'C:\\temp\\oluch\\oluch\\locale\\ru\\LC_MESSAGES\\django.po',
> 'C:\\temp\\oluch\\oluch\\locale\\django.pot']

New description:

 django1.7, python 3.2, windows 7 64 bit russian

 ---
 I have Windows 7 Rus, default encoding is cp1251.
 If i have some translations in .po-file in russian (utf-8 encoding),
 and running makemessages again to add new phrases, it uses msgmerge.exe in
 function write_po_file,
 popen got output in cp1251 encoding instead utf-8 and crashes:

 {{{
 Exception in thread Thread-63:
 Traceback (most recent call last):
   File "c:\python32\lib\threading.py", line 740, in _bootstrap_inner
 self.run()
   File "c:\python32\lib\threading.py", line 693, in run
 self._target(*self._args, **self._kwargs)
   File "c:\python32\lib\subprocess.py", line 1013, in _readerthread
 buffer.append(fh.read())
   File "c:\python32\lib\encodings\cp1251.py", line 23, in decode
 return codecs.charmap_decode(input,self.errors,decoding_table)[0]
 UnicodeDecodeError: 'charmap' codec can't decode byte 0x98 in position
 1157: character maps to 

 Traceback (most recent call last):
   File "c:\python32\Scripts\django-admin-script.py", line 9, in 
 

[Django] #21987: Allow Media objects to have their own MEDIA_TYPES

[Django]

#21987: Allow Media objects to have their own MEDIA_TYPES
-+
 Reporter:  Keryn Knight   |  Owner:  nobody
 Type:  Cleanup/optimization | Status:  new
Component:  Forms|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Currently,
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L35
 instances of Media] look to the module scope to get the known
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L31
 MEDIA_TYPES]. This makes it difficult to subclass `Media` to add extra
 `render_x`/`add_x` methods because `MEDIA_TYPES` is hardcoded in
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L45
 __init__],
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L56
 render],
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L83
 __getitem__] and
 
[https://github.com/django/django/blob/a2814846ca006b4fbf3a893ec52cd9d444b3a3eb/django/forms/widgets.py#L102
 __add__] and isn't easily available for a subclass to add to without
 monkeypatching the module constant. As far as I can tell, the only use of
 `MEDIA_TYPES` is in the widgets module, and could be shifted to the class
 itself, leaving the module level one to raise a deprecation warning.

 Rationale is that I want to be able to add `inline_css` and `inline_js`,
 or `text` (for JS templates etc) to a `Media` object, and currently that's
 more difficult than just adjusting a subclass' attribute and adding the
 appropriate methods.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.14c2ac60a12e7d4824603e3777e01f13%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21986: The documentation provides no indication as to why you might want to use indexes

[Django]

#21986: The documentation provides no indication as to why you might want to use
indexes
-+
 Reporter:  django-issues@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Documentation|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  1|  UI/UX:  0
-+
 Indexing is not an inherently straightforward and intuitive concept.
 There's plenty of material out there that suggests where you might want to
 apply database indexes, but the Django documentation doesn't suggest
 *anything*. [https://docs.djangoproject.com/en/dev/topics/db/optimization/
 Database access optimization] suggests that it is a number one priority,
 and that you should use the information you have gleaned from profiling to
 decide what to index, but provides no methodology for applying that
 information. It's left to the reader's imagination to decide if they
 should add indexes to fields they read a lot or fields they change a lot
 or fields they do lookups by a lot or fields that have fish puns in their
 names.

 I'd make some suggestions, but I am not qualified enough to write anything
 I'd be at all confident in.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4e9c41bc78f33ef2aa390716aaad0ff9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21674: django.utils.module_loading.import_by_path considered harmful

[Django]

#21674: django.utils.module_loading.import_by_path considered harmful
---+-
 Reporter:  aaugustin  |Owner:  berkerpeksag
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5d263dee304fdaf95e18d2f0619d6925984a7f02"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d263dee304fdaf95e18d2f0619d6925984a7f02"
 Fixed #21674 -- Deprecated the import_by_path() function in favor of
 import_string().

 Thanks Aymeric Augustin for the suggestion and review.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1968ed375861bd480315126b0922d7ca%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5d263d: Fixed #21674 -- Deprecated the import_by_path() fu...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5d263dee304fdaf95e18d2f0619d6925984a7f02
  
https://github.com/django/django/commit/5d263dee304fdaf95e18d2f0619d6925984a7f02
  Author: Berker Peksag 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M AUTHORS
M django/contrib/admin/tests.py
M django/contrib/auth/__init__.py
M django/contrib/auth/hashers.py
M django/contrib/auth/middleware.py
M django/contrib/formtools/wizard/storage/__init__.py
M django/contrib/messages/storage/__init__.py
M django/contrib/sessions/backends/base.py
M django/contrib/staticfiles/finders.py
M django/core/cache/__init__.py
M django/core/cache/backends/base.py
M django/core/files/storage.py
M django/core/files/uploadhandler.py
M django/core/handlers/base.py
M django/core/mail/__init__.py
M django/core/servers/basehttp.py
M django/core/signing.py
M django/db/migrations/state.py
M django/db/utils.py
M django/template/context.py
M django/template/loader.py
M django/utils/log.py
M django/utils/module_loading.py
M django/views/debug.py
M docs/internals/deprecation.txt
M docs/ref/utils.txt
M docs/releases/1.7.txt
M tests/file_storage/tests.py
M tests/staticfiles_tests/tests.py
M tests/utils_tests/test_module_loading.py
M tests/wsgi/tests.py

  Log Message:
  ---
  Fixed #21674 -- Deprecated the import_by_path() function in favor of 
import_string().

Thanks Aymeric Augustin for the suggestion and review.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f657e71bac3_c30fbfd3838618%40hookshot-fe8-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6344: Refactored manage.py inspectdb

[Django]

#6344: Refactored manage.py inspectdb
-+-
 Reporter:  Daniel Pope   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  inspectdb|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by WoLpH):

 So... it's been 6 and a half years now, any progress on this?

 After trying the inspectdb command I still notice a few issues that would
 be great to have fixed. For example the field `printableStyleTemplateId`
 should be named `printable_style_template_id` instead of
 `printablestyletemplateid`. Or maybe even `printable_style_template`, but
 something smarter at least :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/095.8c5fc667df2ca8a2eb9fa3c58ae15392%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19361: Link to object in message after creating/updating object in django admin

[Django]

#19361: Link to object in message after creating/updating object in django admin
-+-
 Reporter:  anonymous|Owner:  bak1an
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, messages, | Triage Stage:  Accepted
  update_object, create_object   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bak1an):

 * needs_better_patch:  0 => 1


Comment:

 needs rebase

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8e1d53d85e1d8b73b3d4d29be3cd1ecd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21856: Crash when DATABASES = {}

[Django]

#21856: Crash when DATABASES = {}
-+
 Reporter:  aaugustin|Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by mlavin):

 * has_patch:  0 => 1


Comment:

 I've sent a PR to fix this issue:
 https://github.com/django/django/pull/2244 This moves the check for
 unapplied migrations out of the runserver command and uses the new system
 checks framework instead.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fdd4a8eddd1ed6f805e67bc433079615%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21985: In some cases one-to-one health care is also provided in a nursing home, rehabilitation unit, hospital and assisted living facility. Here the staff is hired and paid by the client who

[Django]

#21985: In some cases one-to-one health care is also provided in a nursing home,
rehabilitation unit, hospital and assisted living facility. Here the staff
is hired and paid by the client who provides personalized care which is
otherwise not possible in these health organizations. Usually such health
care agencies are regulated by laws of the state in which they would be
allowed to prepare meals but not give injections.
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  ELITE TEST 360
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Eudaemonia is one of the most great aspects of our brio. Many importantly
 we cannot cooperation on it when it comes to our dearest ones. Our prompt
 paced lives oftentimes spares no dimension for our pedigree and old
 parents. Sometimes youngsters also need to move few toughened judgement of
 leaving their home and elderly parents in operation of surpass jobs. At
 this moment tho' they strength be earning six-figure salary but regress
 peace of purpose because there is no ELITE TEST 360

 How active having a individual welfare tutelage handler for your stock
 membersâ¬" especially old parents? It is truthful that elderly or sick
 fill penury an unscheduled aid and no gauge can be better than bag. When
 they are ill, sick from a surgery or harm they essential to order in a
 degage environment. It is not surprisingly anymore than 90% of major
 adults necessary to age at lodging. Smooth wellbeing experts bang united
 that it is such healthier and fulfilling. This is because there are umteen
 people who endure from variety of spring them enough repair they attempt
 services from a interior healthcare bureau.
 What are Health Mending Agencies?
 For lesson internal eudaemonia protection agencies in Maryland render
 individual aid to grownup adults and the displeased so that they can edict
 at the support of their domicile. Not exclusive this, they like their
 concealment which adds to their bathroom that too at such subordinate
 costs. This individualised upkeep grouping has been intentional to
 ameliorate the property of time and jade sadness of adult adults and the
 injured. They provide all indispensable scrutiny as shaft as non-medical
 eudaemonia attention services for their clients all in a incapacitated and
 postpartum. This proves to be a assistive livelihood when the clan members
 are not around to bang tutelage of the cause who needs scrutiny aid.
 Cognize Active their Services
 Home tutelage Annapolis MD offers determine of services like sociable
 society to skillful nursing which can allow injections to damage upkeep.
 They also do floaty housekeeping, modify meals, gift medication reminders,
 transferral, errands, resource for regular activities and remaining
 specialty services. These can allow harm want, chemotherapy, intravenous
 therapy and antibiotics to patients all in the keep of domicile. In way
 the health fix agencies render one-to-one rival with upbeat care agencies.
 ELITE TEST 360

 In several cases one-to-one upbeat upkeep is also provided in a nursing
 national, rehabilitation object, infirmary and assisted experience
 effortlessness. Here the staff is hired and professional by the guest who
 provides personalized fixture which is otherwise not likely in these
 welfare organizations. Usually specified eudaemonia mind agencies are
 thermostated by laws of the refer in which they would be allowed to change
 meals but not snap injections.
 [http://tryelitetest360.com/]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.3e305d79e60b1d0f45322f71fc29a69b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15318: A possibility to configure the language's cookie domain and expires.

[Django]

#15318: A possibility to configure the language's cookie domain and expires.
-+-
 Reporter:  sahid|Owner:
 Type:  New feature  |  sergeykolosov
Component:   |   Status:  assigned
  Internationalization   |  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  cookie, domain,  | Triage Stage:  Accepted
  language, settings |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 I've left comments for improvement on the PR. Please uncheck "Patch needs
 improvement" when it's updated.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.9738b2ae6b92b6b6906312571adfbc58%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19373: Windows file locking requires pywin32

[Django]

#19373: Windows file locking requires pywin32
--+
 Reporter:  techtonik |Owner:  marfire
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  File uploads/storage  |  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
--+
Changes (by timo):

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


Comment:

 Ok, I've asked for a rebase of the patch and possibly a mention in the
 release notes. Will merge it once that's done.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.eaa8a13dd92b0482e787dc23e03dd058%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fcc218: Removed extra backquote in field docs

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fcc21837dc691ba6465853c0b68927cb075a4591
  
https://github.com/django/django/commit/fcc21837dc691ba6465853c0b68927cb075a4591
  Author: Claude Paroz 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Removed extra backquote in field docs


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f62f94c086_ef7e9dd38143d6%40hookshot-fe7-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21051: Move cookie settings from standalone values to dictionaries

[Django]

#21051: Move cookie settings from standalone values to dictionaries
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cookie cookis csrf   |  Needs documentation:  0
  sesssion language  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by ramiro):

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


Comment:

 The described limitations seem unlikely fixable with urrent implementation
 of settings infrastructure. Closing for now.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c95ba8b9b26b015bf62de5fb7dd92a5d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20863: Clarify which session backends require django.contrib.sessions in INSTALLED_APPS

[Django]

#20863: Clarify which session backends require django.contrib.sessions in
INSTALLED_APPS
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| 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 timo):

 * easy:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/095.5e1651431e952535d75246bd87ca4fd6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21981: when I run this command ./manage.py syncdb I get the following errors. I am coding this for the 1st time I am not sure what modification needs to done. Can any one help me with it

[Django]

#21981: when I run this command ./manage.py syncdb I get the following errors. 
I am
coding this for the 1st time I am not sure what modification needs to done.
Can any one help me with it. Thank you.
-+-
 Reporter:  Rads19   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  *.djangoproject.com  |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by rads19):

 * component:  Uncategorized => *.djangoproject.com


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5aa880b24ee4dd5aa05287f93832a2b7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21981: when I run this command ./manage.py syncdb I get the following errors. I am coding this for the 1st time I am not sure what modification needs to done. Can any one help me with it

[Django]

#21981: when I run this command ./manage.py syncdb I get the following errors. 
I am
coding this for the 1st time I am not sure what modification needs to done.
Can any one help me with it. Thank you.
---+--
 Reporter:  Rads19 |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:  fixed
 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 rads19):

 * resolution:  invalid => fixed


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e6cce1ff58b07d207d9e41b235ed4e8a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

[Django]

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 Be sure to uncheck "Patch needs improvement" so the patch appears in the
 review queue. I've left some minor comments and will take another look
 after your update, 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.5ff3ff8d53336244832fe8f07de4fa4b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b04185: Allowed more easily subclassing of BlockNode tags.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b041850853188428ac3b843001603db8f8a69392
  
https://github.com/django/django/commit/b041850853188428ac3b843001603db8f8a69392
  Author: Mitar 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/template/loader_tags.py

  Log Message:
  ---
  Allowed more easily subclassing of BlockNode tags.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f6219b1776b_597310d7d3884323%40hookshot-fe11-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21949: Django doesn't log much at high verbosity levels

[Django]

#21949: Django doesn't log much at high verbosity levels
---+--
 Reporter:  gcc|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by smeatonj):

 > I have an expectation, based not on any law but on much positive
 experience, that applications should have a verbose mode where they log
 what they are actually doing, and at least log *something* whenever they
 are poked, so that you can tell that they haven't hung.

 I somewhat agree, but can't this be accomplished by application authors
 putting logging in their code? I wouldn't mind seeing some very basic
 logging in core, which would help identify user problems, but I think it'd
 be unnecessarily costly to dump everything django is doing.

 As a request passes through the many layers, a single log message should
 be enough, depending on the verbosity level anyway. INFO should say
 something like "Request Received" and *maybe* "Response Sent". DEBUG might
 have "Processing Middleware", "URL {0} Selected", "View {0} called",
 "Template {0} loaded".

 Additionally, it should be easier for site authors to dump the debug page
 content to logs, even if an error wasn't generated.

 But, as Russel has pointed out, you'd definitely want to benchmark the
 extra logging in any 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.49910c980a7fd7d3bfd58c0cae6b83ce%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21237: Add Australian English (en_AU) to locale conf

[Django]

#21237: Add Australian English (en_AU) to locale conf
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"114b70ccf8dcd7af86d5cd464d66aa7761400884"]:
 {{{
 #!CommitTicketReference repository=""
 revision="114b70ccf8dcd7af86d5cd464d66aa7761400884"
 Fixed #21237 -- Added Australian English (en_AU) to locale conf

 Adds Australian English (en_AU) to locale conf, which differs from
 American English in date formatting and spelling, and continues
 to diverge from British English in spelling (and first-day-of-week
 according to the current en_GB locale format.py).

 The transifex language project to match this patch has been requested.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9ce465abc60cab49311639254b27cd91%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 114b70: Fixed #21237 -- Added Australian English (en_AU) t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 114b70ccf8dcd7af86d5cd464d66aa7761400884
  
https://github.com/django/django/commit/114b70ccf8dcd7af86d5cd464d66aa7761400884
  Author: Tom Fifield 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/conf/global_settings.py
M django/conf/locale/__init__.py
A django/conf/locale/en_AU/__init__.py
A django/conf/locale/en_AU/formats.py

  Log Message:
  ---
  Fixed #21237 -- Added Australian English (en_AU) to locale conf

Adds Australian English (en_AU) to locale conf, which differs from
American English in date formatting and spelling, and continues
to diverge from British English in spelling (and first-day-of-week
according to the current en_GB locale format.py).

The transifex language project to match this patch has been requested.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f6203098f21_5a5e1179d40996c8%40hookshot-fe11-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18541: Infinite Lock With Caching Backend

[Django]

#18541: Infinite Lock With Caching Backend
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  caching  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6c5a30b4e7f51e8c255dc104714d5748e5b5870c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6c5a30b4e7f51e8c255dc104714d5748e5b5870c"
 Added tests for LocalMemCache deadlocks. refs #20613 and refs #18541.

 Thanks Zach Smith 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9e0f55e97e65257391d86837254bc47e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6c5a30: Added tests for LocalMemCache deadlocks. refs #206...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6c5a30b4e7f51e8c255dc104714d5748e5b5870c
  
https://github.com/django/django/commit/6c5a30b4e7f51e8c255dc104714d5748e5b5870c
  Author: Tim Graham 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M tests/cache/tests.py

  Log Message:
  ---
  Added tests for LocalMemCache deadlocks. refs #20613 and refs #18541.

Thanks Zach Smith for the patch.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f60c5debd68_24cfc33d402402b%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20613: LocMem cache may cause deadlocks

[Django]

#20613: LocMem cache may cause deadlocks
-+
 Reporter:  rafales  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"6c5a30b4e7f51e8c255dc104714d5748e5b5870c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6c5a30b4e7f51e8c255dc104714d5748e5b5870c"
 Added tests for LocalMemCache deadlocks. refs #20613 and refs #18541.

 Thanks Zach Smith 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9c145a522b6a707a871489028b079330%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18541: Infinite Lock With Caching Backend

[Django]

#18541: Infinite Lock With Caching Backend
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  caching  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Duplicate of #20613, I'll merge the test that's included in this PR though
 as tests weren't added with that ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8f5309777dcde13b65f319bfdbb58037%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18373: Thoroughly misleading error page when resolve() fails on a different URL

[Django]

#18373: Thoroughly misleading error page when resolve() fails on a different URL
--+
 Reporter:  anonymous |Owner:  gnosek
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (URLs)   |  Version:  1.3
 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 timo):

 * needs_better_patch:  0 => 1


Comment:

 The patch no longer merges cleanly.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.933bfab3b10d6b539c5d2fad926d637f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18714: Add an option to compilemessages to compile fuzzy translations

[Django]

#18714: Add an option to compilemessages to compile fuzzy translations
-+-
 Reporter:  rasca|Owner:  bak1an
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  compilemessages  |  Needs documentation:  0
  fuzzy msgfmt   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer merges cleanly.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.aff6313ce3c4a454f4c29e45d8a80fe9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19434: Some QuerySet methods not aware of fields added on "extra"

[Django]

#19434: Some QuerySet methods not aware of fields added on "extra"
-+-
 Reporter:  hcarvalhoalves   |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:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer merges cleanly.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.97503a2607d308dc7e26a01fc7945e29%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 02add4: Fixed #21417 -- Expanded TEMPLATE_STRING_IF_INVALI...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 02add43568b694ef25afeae474b5b1da883826c6
  
https://github.com/django/django/commit/02add43568b694ef25afeae474b5b1da883826c6
  Author: Claude Paroz 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/templatetags/i18n.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Fixed #21417 -- Expanded TEMPLATE_STRING_IF_INVALID in blocktrans

Thanks keturn for the reporti, Chris Medrela for details and
Tim Graham for the review.
Refs #19915.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f602348fae9_21c61431d44317d6%40hookshot-fe12-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21417: use TEMPLATE_STRING_IF_INVALID format string in blocktrans

[Django]

#21417: use TEMPLATE_STRING_IF_INVALID format string in blocktrans
-+-
 Reporter:  keturn   |Owner:  Claude
 Type:  Bug  |  Paroz 
Component:  Template system  |   Status:  closed
 Severity:  Normal   |  Version:  1.6
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

 * status:  new => closed
 * owner:   => Claude Paroz 
 * resolution:   => fixed


Comment:

 In [changeset:"02add43568b694ef25afeae474b5b1da883826c6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02add43568b694ef25afeae474b5b1da883826c6"
 Fixed #21417 -- Expanded TEMPLATE_STRING_IF_INVALID in blocktrans

 Thanks keturn for the reporti, Chris Medrela for details and
 Tim Graham for the review.
 Refs #19915.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7b398cf5527237ba71c759c00911872d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19915: templatetag "blocktrans" ignores the TEMPLATE_STRING_IF_INVALID setting

[Django]

#19915: templatetag "blocktrans" ignores the TEMPLATE_STRING_IF_INVALID setting
-+-
 Reporter:  nessita  |Owner:  matiasb
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  blocktrans,template_string_if_invalid|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"02add43568b694ef25afeae474b5b1da883826c6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02add43568b694ef25afeae474b5b1da883826c6"
 Fixed #21417 -- Expanded TEMPLATE_STRING_IF_INVALID in blocktrans

 Thanks keturn for the reporti, Chris Medrela for details and
 Tim Graham for the review.
 Refs #19915.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3ccc3bd5f3e1561c31adefbabd3ed2f7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16192: Make unique_together error messages in ModelForms customizable

[Django]

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

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


Comment:

 In [changeset:"8847a0c601e4261823b1726b2db73eec2ac17940"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8847a0c601e4261823b1726b2db73eec2ac17940"
 Fixed #16192 -- Made unique error messages in ModelForm customizable.

 Overriding the error messages now works for both unique fields,
 unique_together
 and unique_for_date.

 This patch changed the overriding logic to allow customizing
 NON_FIELD_ERRORS
 since previously only fields' errors were customizable.

 Refs #20199.

 Thanks leahculver for the suggestion.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.fee24833bfe1590768b5d10965aa7dd0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8847a0: Fixed #16192 -- Made unique error messages in Mode...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8847a0c601e4261823b1726b2db73eec2ac17940
  
https://github.com/django/django/commit/8847a0c601e4261823b1726b2db73eec2ac17940
  Author: Loic Bistuer 
  Date:   2014-02-08 (Sat, 08 Feb 2014)

  Changed paths:
M django/db/models/base.py
M django/db/models/fields/__init__.py
M django/forms/forms.py
M django/forms/models.py
M docs/ref/exceptions.txt
M docs/ref/models/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/options.txt
M docs/releases/1.7.txt
M docs/topics/forms/modelforms.txt
M tests/model_forms/tests.py

  Log Message:
  ---
  Fixed #16192 -- Made unique error messages in ModelForm customizable.

Overriding the error messages now works for both unique fields, unique_together
and unique_for_date.

This patch changed the overriding logic to allow customizing NON_FIELD_ERRORS
since previously only fields' errors were customizable.

Refs #20199.

Thanks leahculver for the suggestion.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/52f60035b23ac_67158efd3c10049%40hookshot-fe10-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20199: Allow ModelForm to override error messages defined in model fields.

[Django]

#20199: Allow ModelForm to override error messages defined in model fields.
-+
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"8847a0c601e4261823b1726b2db73eec2ac17940"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8847a0c601e4261823b1726b2db73eec2ac17940"
 Fixed #16192 -- Made unique error messages in ModelForm customizable.

 Overriding the error messages now works for both unique fields,
 unique_together
 and unique_for_date.

 This patch changed the overriding logic to allow customizing
 NON_FIELD_ERRORS
 since previously only fields' errors were customizable.

 Refs #20199.

 Thanks leahculver for the suggestion.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3eba05009641fe27e7bc6e6466e6d466%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21928: updating .po files with 'django-admin.py makemessages' under windows with russian locale fail

[Django]

#21928: updating .po files with 'django-admin.py makemessages' under windows 
with
russian locale fail
-+-
 Reporter:  gurovic@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:
  Internationalization   |  1.7-alpha-1
 Severity:  Release blocker  |   Resolution:
 Keywords:  encoding msgmerge| Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Is this a regression from Django 1.6?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.3ec4921bbdc4678ba5c87ae651f3963a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21984: Weight Lose Fast

[Django]

#21984: Weight Lose Fast
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  cleanse fx
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 you have equal time here they come along and just down is like a soft spot
 and it's just a net fingers should cover [http://cleansefxcanadanow.com/
 Cleanse Fx]etc eight markets so it just that underneath eight palm paid
 it's just couple of inches down when your bra strap would be ladies and
 guide them so you don't have grass that's the best description I can get
 and that might be a bit slow response tucking in there antonym outside
 little finger not the ring finger.
 [[Image(http://marketersmedia.com/wp-content/uploads/2013/07/weigt-
 loss-5-womn-400-x-2001.jpg)]]
  I’ll explain later out some until out syntax out of town and finally the
 comments but which ones down the ring finger interested so that's point
 one three four five six seven eight nine ten eleven there's two back and
 won three four five obsolete got a few six saffron topic Austin there to
 give me seven eight nine Levin twelve so to give me about that guys just
 washing through this very quickly exhibit a busy day today but will put
 this together now okay so I’m waiting to get rid of this weight now this
 is my works not yours you can use reminds unwilling to drop this right now
 and on Ticketmaster I love it just because I think that b_-ten doesn’t
 make me I’m willing to lose the whites naturally in dace_ ticket.
  I’m willing to use this link not release any I love my booty ornament
 booty I’m willing to lose this weight naturally easily unacceptably sir
 unwilling to use the slight naturally acceptance remember these are my
 words you cried the copy them or not that go with what you're thinking I
 was born actually close to being feeling seeking now you may find you
 feelings are beginning to change it I’m willing to let this way come off
 main actually in the city and uh... kick myself I fully accept myself as a
 stream of Hudson I can see myself as a slim except myself system I’m going
 to be fabulous asking person I have for this moment and I choose tube
 fantastic we cannot shake out think happy cheering such as happy birthday
 to you and when you're ready to the process again two eight two or three
 times.
 http://cleansefxcanadanow.com/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.020f3f7088a4f02f3ff546635623715f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21845: Deprecate .py suffix for django-admin.py (was: Deprecate django-admin.py)

[Django]

#21845: Deprecate .py suffix for django-admin.py
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Release blocker  |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.57f80487ebb016db9034e7ae07623ff9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21976: Hidden field in TabularInline breaks table layout

[Django]

#21976: Hidden field in TabularInline breaks table layout
-+-
 Reporter:  yliharma |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.6
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin, inlines,  | Triage Stage:
  hiddenfield|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Fixed in #18263 (will be in 1.7).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8958015ce937696a95ba1494bf777595%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21983: weight loss permantly1 65

[Django]

#21983: weight loss permantly1 65
+---
 Reporter:  anonymous   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  GIS |Version:  1.6
 Severity:  Normal  |   Keywords:  GARCINIUM
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+---
 their life and tell them that lifestyles actually hurting you more than
 it's helping you it's threatening to Rachel's mom and that's the last
 thing I want people all want the same thing we've all-white Rachel's
 family to be happy and healthy to have this incredible future together
 that they were in a deal stock it out makes you got all the right foods in
 [http://garciniumpuregarcinia.com/ GARCINIUM] the house phase one is done
 is time for Rachel to take this moment to men carried on into Phase two
 after next month I do have Google hey your six-month call it's going to be
 still is 55 pounds 55 pounds may seem so easy compared to the eighty
 pounds but we're getting down to the nitty-gritty this is the next phase
 for your face to go and call it a milestone it’s it's physical monster
 really actually getting appreciate and and experiences the body you been
 working we're different now memory California so you want to be 203
 Verizon mass it's not set in yet that he's that I'm doing this on my own
 now and I have that nervousness and Fatima summit I believe in %um by
 because when I'm usually by myself Icon acquit you got this Rachel but I'm
 going to go into it and I'm going to give it my all and I'm going to do my
 best to you me this next go in and get ready for my mouse on unbelievable
 on mental illness here in the last time I had a real vacation and now I'm
 getting to spend in Greece remember other and I get to spend it at 289
 pounds fees beautiful but again I'm at this is such a beautiful place I
 just want to learn know what to experience you know the whole thing and we
 began a Greek salad where now dollars it was extremely hard to be while on
 vacation and everything you have to go out to eat everything on male my
 time on that in a minute home there ‘seven a whole lot better when it
 comes to sing special daily he's already dropped like fifteen-pound the
 bank and then they bring us out these complimentary dessert oh my god I
 separated you're going to hurt their feelings if we don't need it
 Louisiana where you be in order I how long the manager got your email
 Immigrated from you when you can even one child my head narrated seriously
 does not bother no original it was extremely difficult and kind of very
 far away if we don't do desserts anymore great other honored as Martha has
 been paying arch map for right here live from my hero all the way up here
 it's so tight so hard take this very in rabbit diagram as tight as I can
 this is really difficult to have these injuries into be trying to kid to
 have certain point in being held back by in rage on three months and
 today's the day in six months weighing and I can't wait to see your
 preachy which he was walking up she look good she’s just got this big
 beautiful smile on her face and its so called the feed health she's
 changing haven't seen in three months I get there I know and I'm good
 there someone Enzowoke up and I Carl even get a I go to walk and I can’t
 even once I just got back on the bed and waited so offer like quit hurting
 that bad I got talked about that because before we leave and I've got some
 bad news for I yeah I talked to doctor shot and the results came in from
 your X-ray you got tendinitis and at nasal case fighter fish eyes in your
 face yes cut that were not becoming that way but what
 http://garciniumpuregarcinia.com/

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.e0c39ef6e97beb9955e7d90f9e17030a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21982: Multiple dates in single date field

[Django]

#21982: Multiple dates in single date field
---+--
 Reporter:  harjot mann|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.6
 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_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 This isn't a bug in Django, please see
 TicketClosingReasons/UseSupportChannels.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.8209a7f8cde5d000680f84a75941acbd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.