date:20130729

Re: [Django] #20826: Move `Manager.raw()` and `Manager._insert()` to the QuerySet class.

2013-07-29 Thread Django

#20826: Move `Manager.raw()` and `Manager._insert()` to the QuerySet class.
-+-
 Reporter:  loic84   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

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


Comment:

 PR https://github.com/django/django/pull/1411

-- 
Ticket URL: 
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.646997282c6f1d14a85a4d4dd80c882f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20826: Move `Manager.raw()` and `Manager._insert()` to the QuerySet class.

2013-07-29 Thread Django

#20826: Move `Manager.raw()` and `Manager._insert()` to the QuerySet class.
--+
Reporter: loic84| Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Database layer (models, ORM) |Version: master
Severity: Normal| Keywords:
Triage Stage: Unreviewed| Has patch: 0
Easy pickings: 0 | UI/UX: 0
--+
After the introduction of #20625, most methods that involve a DB query
have been removed from `Manager` and are automatically proxied to
`QuerySet`, only `raw()` and `_insert()` remain. After discussion with
@akaariai on IRC we came to the conclusion that it would make sense to
move these to the `QuerySet` class as well.

The previous goal was for `QuerySet` to focus on retrieval, but this has
somewhat failed as most methods that could belong to `Manager` (like
`create()`) already live on the `QuerySet` class. The introduction of
hybrid methods like `get_or_create()` or `update_or_create()` also
demonstrates that the distinction between the different kinds of queries
is not obvious to make.

If this ticket is accepted, the new objective would be defined as follows:
- Anything "query" belongs to `QuerySet`.
- `Manager` is responsible for the integration between a `Model` and a
`QuerySet`.
- `Manager` works as a hook to pre/post-process or even replace `QuerySet`
methods when needed. (See current implementation of `Manager.all()` or
`RelatedManager.create()`).

--
Ticket URL:
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/049.b7512f7f01676f25cb2a1a6831edb4de%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-29 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Thank you for fixing my mess, and sorry.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.e42d822a0c9a4f21b4133b0c47c05bfa%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20825: Make cookies use the HTTPOnly flag by default

2013-07-29 Thread Django

#20825: Make cookies use the HTTPOnly flag by default
-+
Reporter: julien | Owner: julien
Type: New feature| Status: new
Component: HTTP handling |Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-+
The `HttpOnly` cookie flag helps prevent the most common types of XSS
attacks (see https://www.owasp.org/index.php/HttpOnly). Thus it would be
preferable for Django to use it by default.

This change would be backwards-incompatible, in particular for
applications that rely on cookies being accessible from genuine client-
side Javascript code. Therefore this change should be clearly explained in
the release notes.

Some information about the benefits and caveats of using this flag should
also be added to the security section of the documentation.

This change is somewhat dependent on a resolution being found for #20755,
as the Python standard library's `cookies` module's management of
`HttpOnly` is inconsistent.

--
Ticket URL:
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/049.9981f4cf5a69d87474c63e982c5d7ea9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20818: "Enter a valid email address." the msgid was changed on stable/1.5.x which caused its msgstr empty.

2013-07-29 Thread Django

#20818: "Enter a valid email address." the msgid was changed on stable/1.5.x 
which
caused its msgstr empty.
-+-
 Reporter:  gzerone@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Translations |  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  zh_CN translation| Triage Stage:
  email field|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by anonymous):

 Replying to [comment:1 claudep]:
 > Hi, translation issues are not tracked by this bug tracker. And
 unfortunately, this translation was added too late on Transifex to enter
 the 1.5 release. It will be translated in 1.6, though.

 Okey, 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.3ab43665fdae7ab494ab8b22d6b5e07d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20824: User Auth: A Complete Solution for Email Login Handling

2013-07-29 Thread Django

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

Comment:

I'm going to accept this as a new feature. I'm almost certain I've heard
Jacob advocate for this (can't put my finger on a specific reference for
this, though, so I'll stand corrected). Regardless, I think it's the next
logical step -- both in terms of making a common use case easy, and
providing a clear worked example for "how to do it" if you want to roll
your own User model.

In terms of implementation -- this should be provided as a separate
contrib app that just contains the email-based user (plus any necssary
forms, admin etc), which is in all other respects an exact analog of the
default auth.User.

--
Ticket URL:
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.53d0a83376240ccb29b1f34e71b1ba13%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 17e632: [1.6.x] Fixed #20785 -- Corrected exception caught...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 17e632929cdf9575f538c1f98379adac8698c288
  
https://github.com/django/django/commit/17e632929cdf9575f538c1f98379adac8698c288
  Author: Shai Berger 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/db/backends/oracle/base.py

  Log Message:
  ---
  [1.6.x] Fixed #20785 -- Corrected exception caught for Oracle LIKE operator 
detection

The code that tests to see which LIKE expressions to use now runs
using non-error-wrapped cursor, so cx_Oracle exceptions need to be caught
rather than Django DatabaseErrors.

Thanks Trac user ludo for report and initial 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/51f70f21bf878_289d127fd48126786%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-29 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger ):

 In [changeset:"17e632929cdf9575f538c1f98379adac8698c288"]:
 {{{
 #!CommitTicketReference repository=""
 revision="17e632929cdf9575f538c1f98379adac8698c288"
 [1.6.x] Fixed #20785 -- Corrected exception caught for Oracle LIKE
 operator detection

 The code that tests to see which LIKE expressions to use now runs
 using non-error-wrapped cursor, so cx_Oracle exceptions need to be caught
 rather than Django DatabaseErrors.

 Thanks Trac user ludo for report and initial patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.7c9e7ad628467f829ae7b5628209d7a2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6ed579: Fixed #20785 -- Corrected exception caught for Ora...

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6ed579e7eb6e1eda3dd1b0afb306d58b9498bfa0
  
https://github.com/django/django/commit/6ed579e7eb6e1eda3dd1b0afb306d58b9498bfa0
  Author: Shai Berger 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/db/backends/oracle/base.py

  Log Message:
  ---
  Fixed #20785 -- Corrected exception caught for Oracle LIKE operator detection

The code that tests to see which LIKE expressions to use now runs
using non-error-wrapped cursor, so cx_Oracle exceptions need to be caught
rather than Django DatabaseErrors.

Thanks Trac user ludo for report and initial 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/51f70f11eccde_276e8bdd501878da%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-29 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  shai
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shai Berger ):

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


Comment:

 In [changeset:"6ed579e7eb6e1eda3dd1b0afb306d58b9498bfa0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6ed579e7eb6e1eda3dd1b0afb306d58b9498bfa0"
 Fixed #20785 -- Corrected exception caught for Oracle LIKE operator
 detection

 The code that tests to see which LIKE expressions to use now runs
 using non-error-wrapped cursor, so cx_Oracle exceptions need to be caught
 rather than Django DatabaseErrors.

 Thanks Trac user ludo for report and initial patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.533f120b0fd70fffaf1f24f35edfaf0c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20824: User Auth: A Complete Solution for Email Login Handling

2013-07-29 Thread Django

#20824: User Auth: A Complete Solution for Email Login Handling
--+
 Reporter:  JJZolper  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.auth  |Version:  1.5
 Severity:  Normal|   Keywords:  User Auth Email Login Handling
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 With Django 1.5 more support has been given to those Django developers who
 wish to have the Email as the username. However, I think we can continue
 to push onwards to a point where Django can realize a complete solution.
 By following the user login with username handling but porting it for
 email handling I think we can solve this issue once and for all. Currently
 I have been just going online and putting together my own solution, but my
 hope is with this ticket we can get everyone working together and a
 finalized solution merged into Django.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.6aee9c0308af46efb0ce2d042ce8e651%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20785: [oracle] ORA-01425: escape character must be character string of length 1

2013-07-29 Thread Django

#20785: [oracle] ORA-01425: escape character must be character string of length 
1
-+-
 Reporter:  ludo |Owner:  shai
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-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 shai):

 * owner:  nobody => shai
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Having read the related tickets and discussions (and code) more carefully,
 it seems I was a little confused, and your solution appears correct --
 except for the part that `utils.DatabaseError` is actually not necessary
 at all there.

 The regression was introduced in
 [59a352087591a26023412cbcb830cd1d34fc9b99] which refactored the wrapping
 of database exceptions -- and made it so that this code runs with a "bare"
 (non-wrapped) cursor.

-- 
Ticket URL: 
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.685b904f55ae772e08a6ebe937f73a1d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20817: Add support for html email messages through django.core.mail.send_mail()

2013-07-29 Thread Django

#20817: Add support for html email messages through django.core.mail.send_mail()
-+--
Reporter: jmichalicek |Owner: nobody
Type: New feature | Status: closed
Component: Core (Mail) | Version: master
Severity: Normal | Resolution: fixed
Keywords: mail, send_mail | Triage Stage: Unreviewed
Has patch: 1| Needs documentation: 0
Needs tests: 0| Patch needs improvement: 1
Easy pickings: 0|UI/UX: 0
-+--

Comment (by russellm):

For the sake of completeness -- yes, I've got the git blame attribution
for the "frozen" comments, but I wasn't the original author. The original
author of those comments was Malcolm

[https://code.djangoproject.com/changeset/ac0955876089002f0f60857d09fe1c94d67eca4f
d5d2072bbfc38015a93d6e13136c3f1dbf125d87]. He made that change because the
intention was to discourage people from using send_mail, and encourage the
use of EmailMessage instead. The intention was that Django should only
have the bare minimum tools for sending mail; if you wanted more, you
should be using Python native features. We had a lot of feature requests
on django-users/django-dev to add extra arguments to send_mail; the
comment in the code was an attempt to stop those requests.

However, since that time, the world has changed a bit. We've introduced
mail backends, which massively increased the scope of the mail APIs in
Django. We fixed #10863, which added HTML mail functionality to some (but
not all) of the internal mail sending tools. More generally, HTML mails
have become a lot more common/acceptable.

--
Ticket URL:
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.effa64247f149e124315d69a7be577fe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e82846: [1.6.x] Fixed #20823 -- Typo in docs/ref/forms/val...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e82846a9aa38bcc3db7e1820d11c7fa9a5f79449
  
https://github.com/django/django/commit/e82846a9aa38bcc3db7e1820d11c7fa9a5f79449
  Author: Tim Graham 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  [1.6.x] Fixed #20823 -- Typo in docs/ref/forms/validation.txt

Backport of 05ea5a2139 from master



-- 
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/51f6efd68d48e_2c37885d4c1494ca%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20823: Typo on form and field validation doc page

2013-07-29 Thread Django

#20823: Typo on form and field validation doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+

Comment (by Tim Graham ):

 In [changeset:"05ea5a213935b6f1c02f634b6a7674bd2f296458"]:
 {{{
 #!CommitTicketReference repository=""
 revision="05ea5a213935b6f1c02f634b6a7674bd2f296458"
 Fixed #20823 -- Typo in docs/ref/forms/validation.txt
 }}}

-- 
Ticket URL: 
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.63fb83e540d03f7fa536700be3e7a4ea%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 05ea5a: Fixed #20823 -- Typo in docs/ref/forms/validation....

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 05ea5a213935b6f1c02f634b6a7674bd2f296458
  
https://github.com/django/django/commit/05ea5a213935b6f1c02f634b6a7674bd2f296458
  Author: Tim Graham 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/ref/forms/validation.txt

  Log Message:
  ---
  Fixed #20823 -- Typo in docs/ref/forms/validation.txt



-- 
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/51f6efd795dad_2061851d581645c%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20823: Typo on form and field validation doc page

2013-07-29 Thread Django

#20823: Typo on form and field validation doc page
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  closed
Component:  Documentation  |Version:  master
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e82846a9aa38bcc3db7e1820d11c7fa9a5f79449"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e82846a9aa38bcc3db7e1820d11c7fa9a5f79449"
 [1.6.x] Fixed #20823 -- Typo in docs/ref/forms/validation.txt

 Backport of 05ea5a2139 from master
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.55999752c1a22d4e4989000689be96f1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20823: Typo on form and field validation doc page

2013-07-29 Thread Django

#20823: Typo on form and field validation doc page
---+
 Reporter:  anonymous  |  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
---+
 Typo: Error has 3 Rs

 https://docs.djangoproject.com/en/dev/ref/forms/validation/
 {{{
 Putting it all together:

 raise ValidationErrror(
 _('Invalid value: %(value)s'),
 code='invalid',
 params={'value': '42'},
 )
 }}}

-- 
Ticket URL: 
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.a854506cf6eff35b22662c19b1d7045c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19877: Allowing running management commands without colorized output

2013-07-29 Thread Django

#19877: Allowing running management commands without colorized output
-+-
 Reporter:  josh@…   |Owner:  jose
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 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|
-+-

Comment (by jose):

 Thanks, Tim, for your attention. I will say that seems a good idea for me
 to call the option `--no-color`, since it only prevents colorizing the
 output.

-- 
Ticket URL: 
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/071.321117a1cfa5de0c845e4f8a1a55b922%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-07-29 Thread Django

#8620: ModelForm.Meta.exclude only excludes model fields, not form fields
-+--
 Reporter:  levity   |Owner:  shimonrura
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by loic84):

 This may or may not be the right solution to this issue, but this PR
 allows shadowing a declarative field and would enable the `username =
 None` example from the previous comment:
 https://github.com/django/django/pull/1382.

-- 
Ticket URL: 
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.5025d61621009be776bf8ba5ff14b8a9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20708: QuerySet.update() ignores order_by() clause

2013-07-29 Thread Django

#20708: QuerySet.update() ignores order_by() clause
-+-
 Reporter:  jrief|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  needsinfo
 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 anonymous):

 Just to complete this issue:

 To compare ORM's I did some tests with SQLAlchemy. On invokation of
 {{{
 query.order_by('position').update()
 sqlalchemy.exc.InvalidRequestError: Can't call Query.update() when
 order_by() has been called
 }}}
 Im comparison to that, the Django ORM just ignores the order_by() clause.

 Then I tested with SQLite. Here we have the same problem as with MySQL,
 you can't update a table with a unique column, with a statement as above.
 Even worse, SQLite does not accept an ORDER BY clause during updates.
 {{{
 sqlite> UPDATE users SET position=position+1 ORDER BY position;
 Error: near "ORDER": syntax error
 }}}
 To conclude this issue, Postgres is the only of the 3 supported databases,
 which does it "right", ie. in one transaction.

-- 
Ticket URL: 
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.5ada0c0ca01533e385bf5bc9f14c2230%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5c1143: Removed most of absolute_import imports

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5c1143910e071c73671424036408c4548742d24f
  
https://github.com/django/django/commit/5c1143910e071c73671424036408c4548742d24f
  Author: Claude Paroz 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/contrib/admindocs/tests/test_fields.py
M django/contrib/comments/views/comments.py
M django/contrib/comments/views/moderation.py
M django/contrib/formtools/tests/urls.py
M django/contrib/gis/geoip/__init__.py
M django/contrib/gis/tests/distapp/tests.py
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/geoadmin/tests.py
M django/contrib/gis/tests/geoapp/feeds.py
M django/contrib/gis/tests/geoapp/sitemaps.py
M django/contrib/gis/tests/geoapp/test_feeds.py
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/geoapp/test_sitemaps.py
M django/contrib/gis/tests/geoapp/tests.py
M django/contrib/gis/tests/geoapp/urls.py
M django/contrib/gis/tests/geogapp/tests.py
M django/contrib/gis/tests/inspectapp/tests.py
M django/contrib/gis/tests/layermap/tests.py
M django/contrib/gis/tests/relatedapp/tests.py
M django/contrib/messages/__init__.py
M django/core/cache/utils.py
M django/core/management/utils.py
M django/core/serializers/json.py
M django/db/models/sql/__init__.py
M django/db/models/sql/where.py
M django/forms/__init__.py
M django/forms/extras/__init__.py
M django/forms/fields.py
M django/forms/forms.py
M django/forms/formsets.py
M django/forms/models.py
M django/forms/widgets.py
M django/http/cookie.py
M django/http/request.py
M django/http/response.py
M django/template/base.py
M tests/admin_changelist/admin.py
M tests/admin_changelist/tests.py
M tests/admin_custom_urls/tests.py
M tests/admin_docs/urls.py
M tests/admin_filters/tests.py
M tests/admin_inlines/admin.py
M tests/admin_inlines/tests.py
M tests/admin_inlines/urls.py
M tests/admin_ordering/tests.py
M tests/admin_registration/tests.py
M tests/admin_scripts/complex_app/admin/foo.py
M tests/admin_scripts/complex_app/models/bar.py
M tests/admin_scripts/simple_app/models.py
M tests/admin_util/tests.py
M tests/admin_validation/tests.py
M tests/admin_views/admin.py
M tests/admin_views/customadmin.py
M tests/admin_views/tests.py
M tests/admin_views/urls.py
M tests/admin_widgets/tests.py
M tests/admin_widgets/urls.py
M tests/admin_widgets/widgetadmin.py
M tests/aggregation/tests.py
M tests/aggregation_regress/tests.py
M tests/app_loading/tests.py
M tests/backends/tests.py
M tests/basic/tests.py
M tests/bug639/tests.py
M tests/bug8245/admin.py
M tests/bulk_create/tests.py
M tests/cache/tests.py
M tests/choices/tests.py
M tests/comment_tests/tests/__init__.py
M tests/comment_tests/tests/test_app_api.py
M tests/comment_tests/tests/test_comment_form.py
M tests/comment_tests/tests/test_comment_utils_moderators.py
M tests/comment_tests/tests/test_comment_view.py
M tests/comment_tests/tests/test_feeds.py
M tests/comment_tests/tests/test_models.py
M tests/comment_tests/tests/test_moderation_views.py
M tests/comment_tests/tests/test_templatetags.py
M tests/comment_tests/urls.py
M tests/conditional_processing/views.py
M tests/contenttypes_tests/models.py
M tests/contenttypes_tests/tests.py
M tests/contenttypes_tests/urls.py
M tests/context_processors/urls.py
M tests/custom_columns/tests.py
M tests/custom_columns_regress/tests.py
M tests/custom_managers/tests.py
M tests/custom_managers_regress/tests.py
M tests/custom_methods/tests.py
M tests/custom_pk/models.py
M tests/custom_pk/tests.py
M tests/datatypes/tests.py
M tests/dates/tests.py
M tests/datetimes/tests.py
M tests/defer/tests.py
M tests/defer_regress/tests.py
M tests/delete/tests.py
M tests/delete_regress/tests.py
M tests/dispatch/tests/__init__.py
M tests/distinct_on_fields/tests.py
M tests/empty/tests.py
M tests/expressions/tests.py
M tests/expressions_regress/tests.py
M tests/extra_regress/tests.py
M tests/field_defaults/tests.py
M tests/field_subclassing/models.py
M tests/field_subclassing/tests.py
M tests/file_storage/tests.py
M tests/file_uploads/tests.py
M tests/file_uploads/urls.py
M tests/file_uploads/views.py
M tests/files/tests.py
M tests/fixtures/tests.py
M tests/fixtures_regress/models.py
M tests/fixtures_regress/tests.py
M tests/force_insert_update/tests.py
M tests/forms_tests/tests/__init__.py
M tests/forms_tests/tests/test_error_messages.py
M tests/forms_tests/tests/test_extra.py
M tests/forms_tests/tests/tests.py
M tests/generic_inline_admin/admin.py
M tests/generic_inline_admin/tests.p

Re: [Django] #17413: Serialization or getting non-HTML version of form errors is not easy

2013-07-29 Thread Django

#17413: Serialization or getting non-HTML version of form errors is not easy
-+-
 Reporter:  kmike|Owner:  merb
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  form errors  | Triage Stage:  Accepted
  serialization  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by merb):

 As i asked here: https://github.com/django/django/pull/1406
 What's better, to have a errors_dict or a to_json() in the ErrorDict()

 the first would make some things like this happen: json.dumps(errors_dict)
 the second would be form.errors.to_json()

-- 
Ticket URL: 
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.f9f416e2a6dcd467bf5ebc7549dbddf2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19877: Allowing running management commands without colorized output (was: call_command provides no method to set output style)

2013-07-29 Thread Django

#19877: Allowing running management commands without colorized output
-+-
 Reporter:  josh@…   |Owner:  jose
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 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 timo):

 * version:  1.4 => master


Comment:

 I was able to write a test and updated the
 [https://github.com/django/django/pull/1410 PR] to merge cleanly. I think
 it may be more intuitive to call the option "no-color" rather than "no-
 style", but I'll let others chime in before committing this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/071.89f798567e495e7a4c2f0cfc2302e62c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14850: 1.3 release notes typo STATICFILES_ROOT should be STATIC_ROOT

2013-07-29 Thread Django

#14850: 1.3 release notes typo STATICFILES_ROOT should be STATIC_ROOT
---+--
 Reporter:  Ciantic|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.3-alpha
 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 timo):

 * resolution:  fixed => invalid
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Above commit is for ticket #14580.

-- 
Ticket URL: 
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.cb58f58018c8a732a99fbf7e34d35d7a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14580: Clean up duplicate code in admin formset handling

2013-07-29 Thread Django

#14580: Clean up duplicate code in admin formset handling
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


Comment:

 In 402b4a7a20a4f00fce0f01cdc3f5f97967fdb935:

 Fixed #14580 -- Cleaned up duplicate code in admin formset handling.

 Thanks apollo13 for the report 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/066.e61a8be0a5318f746801563a4ee34c01%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 402b4a: Fixed #14850 -- Cleaned up duplicate code in admin...

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 402b4a7a20a4f00fce0f01cdc3f5f97967fdb935
  
https://github.com/django/django/commit/402b4a7a20a4f00fce0f01cdc3f5f97967fdb935
  Author: Tim Graham 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/contrib/admin/options.py

  Log Message:
  ---
  Fixed #14850 -- Cleaned up duplicate code in admin formset handling.

Thanks apollo13 for the report 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/51f69a6d1b7a2_214c591d48815bb%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14850: 1.3 release notes typo STATICFILES_ROOT should be STATIC_ROOT

2013-07-29 Thread Django

#14850: 1.3 release notes typo STATICFILES_ROOT should be STATIC_ROOT
-+--
   Reporter:  Ciantic|Owner:  nobody
   Type: |   Status:  closed
  Component:  Documentation  |  Version:  1.3-alpha
   Severity: |   Resolution:  fixed
   Keywords: | Triage Stage:  Unreviewed
  Has patch:  0  |  Needs documentation:  0
Needs tests:  0  |  Patch needs improvement:  0
-+--
Changes (by Tim Graham ):

 * resolution:  invalid => fixed


Comment:

 In [changeset:"402b4a7a20a4f00fce0f01cdc3f5f97967fdb935"]:
 {{{
 #!CommitTicketReference repository=""
 revision="402b4a7a20a4f00fce0f01cdc3f5f97967fdb935"
 Fixed #14850 -- Cleaned up duplicate code in admin formset handling.

 Thanks apollo13 for the report 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/065.26fbc7927f4ba6dd675296cca1d77b57%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13603: module_has_submodule fails when package is of type module

2013-07-29 Thread Django

#13603: module_has_submodule fails when package is of type module
---+
 Reporter:  Eruquen@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

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


Comment:

 Looks like this was addressed in the commit for #15525.

-- 
Ticket URL: 
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.278e1eba2a122cd02677951f9ef1723d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20771: importlib: more verbosity please

2013-07-29 Thread Django

#20771: importlib: more verbosity please
--+
 Reporter:  lu.nemec@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  1.5
 Severity:  Normal|   Resolution:  wontfix
 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 timo):

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


Comment:

 This is actually a copy of what's implemented in Python 2.7+ and the copy
 in Django has been deprecated as of
 fdd7a355bf053217d25b8d2189e37069c1304283.

-- 
Ticket URL: 
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.cd5a84ed75aeb721fd35a5be0ca420c2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20702: Using ModelAdmin.get_formsets() to filter inlines is broken.

2013-07-29 Thread Django

#20702: Using ModelAdmin.get_formsets() to filter inlines is broken.
-+-
 Reporter:  stanislas.guerra@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  admin inlines| Triage Stage:  Accepted
  get_formsets   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 apollo13 also noticed this in #14580. We at least need a doc update
 pointing out that you'll need to drop the inline using
 `get_inline_instances()`. Possibly we can make the code in
 `contrib.admin.options` a bit more sophisticated to detect this so it's
 not necessary to override both.

-- 
Ticket URL: 
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/084.3dcb49bc5499d5732fd37ff58169b9ac%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20802: List filter in admin with multidatabase setup uses default db

2013-07-29 Thread Django

#20802: List filter in admin with multidatabase setup uses default db
-+-
 Reporter:  engrost@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  invalid
 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 ramiro):

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


Comment:

 There is no `MultiDBModelAdmin` in Django code. If it's part of an
 external project please report the issue to its bug tracker.

-- 
Ticket URL: 
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.f2aed2446472c09337c9e6bc319fff61%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20822: Content type of default error pages should be always "text/html"

2013-07-29 Thread Django

DEFAULT_CONTENT_TYPE = 'application/xhtml+xml'

And every view defined in the project conforms to the that. For instance,
I have defined a custom 404 error page, and there is no issue, because I
wrote it as valid XHTML.

The problem is that the default error pages that comes in Django are, too,
being served with the content type I choose in my settings. The simple
default error 500 page content "Server Error (500)" is being
server as XHTML, what is obviously wrong and fails to render in the
browsers.

Default error pages should use specific content type for what it its, in
this case, text/html, for the case the default content type has been
overridden.

--
Ticket URL:
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/049.bf028833ac42b41e194643e62f932d69%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] fdd7a3: Deprecated django.utils.importlib

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fdd7a355bf053217d25b8d2189e37069c1304283
  
https://github.com/django/django/commit/fdd7a355bf053217d25b8d2189e37069c1304283
  Author: Claude Paroz 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/conf/__init__.py
M django/conf/urls/__init__.py
M django/contrib/admin/__init__.py
M django/contrib/admindocs/views.py
M django/contrib/auth/hashers.py
M django/contrib/comments/__init__.py
M django/contrib/formtools/tests/wizard/storage.py
M django/contrib/formtools/tests/wizard/test_forms.py
M django/contrib/gis/geometry/backend/__init__.py
M django/contrib/sessions/management/commands/clearsessions.py
M django/contrib/sessions/middleware.py
M django/contrib/staticfiles/storage.py
M django/core/cache/__init__.py
M django/core/management/__init__.py
M django/core/management/commands/flush.py
M django/core/management/commands/startapp.py
M django/core/management/commands/startproject.py
M django/core/management/commands/syncdb.py
M django/core/serializers/__init__.py
M django/core/servers/fastcgi.py
M django/core/urlresolvers.py
M django/db/backends/__init__.py
M django/db/models/loading.py
M django/db/utils.py
M django/template/base.py
M django/template/loaders/app_directories.py
M django/test/client.py
M django/test/simple.py
M django/utils/formats.py
M django/utils/importlib.py
M django/utils/module_loading.py
M django/utils/translation/trans_real.py
M django/views/i18n.py
M docs/internals/deprecation.txt
M docs/releases/1.7.txt
M tests/i18n/tests.py
M tests/test_runner/tests.py
M tests/utils_tests/test_module_loading.py

  Log Message:
  ---
  Deprecated django.utils.importlib

This was a shim for pre-Python 2.7 support.


  Commit: e4937b6dde5c30f34c8a65960d7d48b5d7ade356
  
https://github.com/django/django/commit/e4937b6dde5c30f34c8a65960d7d48b5d7ade356
  Author: Claude Paroz 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Add utf-8 preamble to admin_scripts temp settings file

As some settings are copied from current user settings, we cannot
be sure the characters are pure ascii.


Compare: https://github.com/django/django/compare/ac0955876089...e4937b6dde5c

-- 
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/51f6866ba41aa_2888c49d4875144%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20821: Permission names can be longer than the select box they are in

2013-07-29 Thread Django

#20821: Permission names can be longer than the select box they are in
---+
 Reporter:  django@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In the edit group / user pages, permission names are often larger than the
 select box they are placed in, which results in you being unable to see
 what permissions you are adding without some form of ugly workaround such
 as making the box larger with chromes inspect element. I've attached a
 screenshot demonstrating this issue.

 Some possible ideas to fix this...
 1) Make the select box resizeable
 2) Make the select box larger
 3) Make the select box have a horizontal scroll bar if required
 4) Display the full permission name in a tool tip on mouse over

-- 
Ticket URL: 
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.53c3dc696a50976314221145680e76ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20693: Add timezone support to built-in time filter

2013-07-29 Thread Django

#20693: Add timezone support to built-in time filter
-+-
 Reporter:  warren@… |Owner:  wsmith323
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by estebistec):

 * stage:  Accepted => Ready for checkin


Comment:

 Ready for checkin/final review by core dev.

-- 
Ticket URL: 
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.06077bdb557f2f7de67ba8552a37f16a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16630: Support for HTML5 input types

2013-07-29 Thread Django

#16630: Support for HTML5 input types
-+
 Reporter:  jonash   |Owner:  claudep
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html5| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 I don't think so. Specialized input types should be left to third-party
 apps.

-- 
Ticket URL: 
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.f50622757bf20cdb6477e750c7dfc05a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16630: Support for HTML5 input types

2013-07-29 Thread Django

#16630: Support for HTML5 input types
-+
 Reporter:  jonash   |Owner:  claudep
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  html5| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by anonymous):

 Is ColorInput available as a widget yet? Do you want a patch for it?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.c9a5b506a51c526195dd0dbceb6c5ce9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-07-29 Thread Django

Comment (by mjtamlyn):

At the moment, I'm definitely -0 on this change in functionality. I
believe that `fields` and `exclude` are shortcuts and are secondary to
actually defining the fields - i.e. the field definitions on the form
should *always* take precedence. I believe that the subclassing issue can
be solved by setting `username = None`on the subclass.

In particular this introduces a disparity between `Form` and `ModelForm` -
I don't want to recommend this as a subclassing route if it doesn't
actually work in the general 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/064.3a020b0a66c2ddd3fc96c42e4e78193f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20817: Add support for html email messages through django.core.mail.send_mail()

2013-07-29 Thread Django

#20817: Add support for html email messages through django.core.mail.send_mail()
-+--
 Reporter:  jmichalicek  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mail, send_mail  | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ac0955876089002f0f60857d09fe1c94d67eca4f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ac0955876089002f0f60857d09fe1c94d67eca4f"
 Fixed #20817 -- Added html_message parameter to
 django.core.mail.send_mail()
 }}}

-- 
Ticket URL: 
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.152795c13539114b39c58b590e71851e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ac0955: Fixed #20817 -- Added html_message parameter to dj...

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ac0955876089002f0f60857d09fe1c94d67eca4f
  
https://github.com/django/django/commit/ac0955876089002f0f60857d09fe1c94d67eca4f
  Author: Justin Michalicek 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/core/mail/__init__.py
M docs/releases/1.7.txt
M docs/topics/email.txt
M tests/mail/tests.py

  Log Message:
  ---
  Fixed #20817 -- Added html_message parameter to django.core.mail.send_mail()



-- 
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/51f6785bc2967_2c0512cbd4c971f1%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19716: Support microsecond precision in MySQL ORM DateTimeField

2013-07-29 Thread Django

#19716: Support microsecond precision in MySQL ORM DateTimeField
-+-
 Reporter:  erik@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by allcaps):

 I tested as Erik but on MySQL 5.4.6 and had the same. The datetime with
 fractions get stored in db (column datatime(6)) but get NoneType returned.

 {{{
 In [5]: get_object_or_404(MyModel, pk=1).dt_millis.__class__
 Out[5]: NoneType #This should be datetime.datetime
 }}}

 I created a custom model to create the datetime([1-6]) column. This way a
 developer has a choice on what type of datetime to use:

 {{{
 class DateTimeFractionField(models.DateTimeField):
 description = "Datetimefield with fraction second. Requires MySQL
 5.4.3 or greater"

 def __init__(self, precision, *args, **kwargs):
 self.precision = precision
 super(DateTimeFractionField, self).__init__(*args, **kwargs)

 def db_type(self, connection):
 return 'DATETIME(%s)' % self.precision

 class MyModel(models.Model):
 dt_micros  = DateTimeFractionField(6)
 }}}

 The current backend 'strips' the milliseconds with
 .replace(microsecond=0). So microseconds aren't gone. They are 0. The
 MySQL docs state that < MySQL 5.4.3 discards any fractional part.  So I
 assume that removing all .replace(microseconds=0) from the MySQL backend
 is a good beginning. Doing so let's MySQL decide if the value's get stored
 or not.

 I also tried to store datetime with fractions in Postgresql. The buildin
 datetimefield works. But I needed to modify the formfield clean method to
 submit and admin widget to display the fracrions in the admin.

 This is my first contribution. I'd like to collaborate to get this ticket
 closer to 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/077.b5fb7b30bb1370c4869fdb76b3007b7d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20817: Add support for html email messages through django.core.mail.send_mail()

2013-07-29 Thread Django

#20817: Add support for html email messages through django.core.mail.send_mail()
-+--
 Reporter:  jmichalicek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  mail, send_mail  | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+--
Changes (by jmichalicek):

 * stage:  Accepted => Unreviewed


Comment:

 Thanks, I've updated the docs as noted in the 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/069.3eb26056676fa2bfa7de386f1ea5cf1d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20749: get_FOO_display does not return proper value or warn for inconsistent type

2013-07-29 Thread Django

#20749: get_FOO_display does not return proper value or warn for inconsistent 
type
-+-
 Reporter:  ellisd23@…   |Owner:  ellisd23
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 It seems to me this introduces a performance penalty (iterating through
 choices to calling `to_python`) which in most cases shouldn't be necessary
 as long as users declare their models correctly. I would tend to favor the
 model validation solution. I wonder if the idea of using `to_python` might
 work there.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.134b445d9c3402d6030927da7b7ae3e7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20749: get_FOO_display does not return proper value or warn for inconsistent type

2013-07-29 Thread Django

#20749: get_FOO_display does not return proper value or warn for inconsistent 
type
-+-
 Reporter:  ellisd23@…   |Owner:  ellisd23
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ellisd23):

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


Comment:

 I've added a test.  The specific commit is here:
 
https://github.com/dellis23/django/commit/c3098afb0ba240e1195d4dce03146089717fe74e

-- 
Ticket URL: 
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.139f8aceb5342678418c9c89aeb1f929%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20817: Add support for html email messages through django.core.mail.send_mail()

2013-07-29 Thread Django

#20817: Add support for html email messages through django.core.mail.send_mail()
-+
 Reporter:  jmichalicek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Mail)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  mail, send_mail  | 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):

 * cc: timograham@… (added)
 * needs_better_patch:   => 1
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Given that Russ seemed to accept the ticket in the mailing list and was
 the one who committed the original change which included the comment about
 the API being frozen, I assume this is fine.

 I left minor doc comments on the
 [https://github.com/django/django/pull/1408 PR].

-- 
Ticket URL: 
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.5cf99ea4013eae2e58f178558c10f86c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-07-29 Thread Django

#8620: ModelForm.Meta.exclude only excludes model fields, not form fields
-+--
 Reporter:  levity   |Owner:  shimonrura
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by timo):

 I think this should be fine backwards compatibility-wise, but a posted a
 [https://github.com/django/django/pull/1409 PR] just to give greater
 visibility to the patch before I commit it.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.50381ae73027e9ffb275f4638599321d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20768: Create a reference of public Manager methods

2013-07-29 Thread Django

#20768: Create a reference of public Manager methods
---+
 Reporter:  ramiro |Owner:  nobody
 Type:  New feature|   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:  0  |UI/UX:  0
---+

Comment (by loic84):

 While addressing this, we should account for @ramiro's
 
[https://github.com/django/django/commit/31fadc120213284da76801cc7bc56e9f32d7281b#commitcomment-3725813
 on the PR]. Probably by removing the custom `__init__` altogether.

-- 
Ticket URL: 
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.6e61537de379fa15691e4a5ed0bc7fcf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 382c53: Fixed #18213 -- Allowed empty fixtures (emit a war...

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 382c53d7d88da70a3645c6db063995382f61dc45
  
https://github.com/django/django/commit/382c53d7d88da70a3645c6db063995382f61dc45
  Author: Przemek Lewandowski 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/core/management/commands/loaddata.py
M docs/releases/1.7.txt
M tests/fixtures_regress/tests.py

  Log Message:
  ---
  Fixed #18213 -- Allowed empty fixtures (emit a warning rather than raising an 
exception).



-- 
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/51f65b7e434ce_786d107dd4c1579%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18213: loaddata should allow empty fixtures

2013-07-29 Thread Django

#18213: loaddata should allow empty fixtures
-+-
 Reporter:  lsaffre  |Owner:  haxoza
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"382c53d7d88da70a3645c6db063995382f61dc45"]:
 {{{
 #!CommitTicketReference repository=""
 revision="382c53d7d88da70a3645c6db063995382f61dc45"
 Fixed #18213 -- Allowed empty fixtures (emit a warning rather than raising
 an exception).
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.8477bab0e9218cbe12b157a8b34e2446%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] bf4c8d: [1.5.x] Fixed qs ordering related randomly failing...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: bf4c8d8c9810b2c21cfc2fd619fcdf2f5ad5c7fd
  
https://github.com/django/django/commit/bf4c8d8c9810b2c21cfc2fd619fcdf2f5ad5c7fd
  Author: Anssi Kääriäinen 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M tests/regressiontests/aggregation_regress/tests.py

  Log Message:
  ---
  [1.5.x] Fixed qs ordering related randomly failing test

The failure wasn't present in 1.6+, so this is not a backpatch.



-- 
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/51f64e16d31c5_2bf3837d5432798%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 518faa: [1.6.x] Misc doc cleanups.

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 518faa19c1f9212cbbbfaca6ef605fd02acd3abb
  
https://github.com/django/django/commit/518faa19c1f9212cbbbfaca6ef605fd02acd3abb
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/ref/forms/widgets.txt
M docs/topics/templates.txt

  Log Message:
  ---
  [1.6.x] Misc doc cleanups.

Backport of 70c080fcdb from master



-- 
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/51f64cc87358e_2db5fb9d4811066c%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 70c080: Misc doc cleanups.

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 70c080fcdb7acbc4c3f86ee85ea84b5861c26bb9
  
https://github.com/django/django/commit/70c080fcdb7acbc4c3f86ee85ea84b5861c26bb9
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/ref/forms/widgets.txt
M docs/topics/templates.txt

  Log Message:
  ---
  Misc doc cleanups.



-- 
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/51f64ca8d7a8c_6044d13d50111025%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b5ac25: [1.5.x] Misc doc cleanups.

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b5ac25dc0c1d2d66b70451c551b271b920b85455
  
https://github.com/django/django/commit/b5ac25dc0c1d2d66b70451c551b271b920b85455
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/ref/forms/widgets.txt
M docs/topics/templates.txt

  Log Message:
  ---
  [1.5.x] Misc doc cleanups.

Backport of 70c080fcdb from master



-- 
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/51f64cc3de4e1_2be1b71d581099c2%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5f8bf4: [1.6.x] Allowed overriding variables in docs/Makef...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5f8bf4368d79324f3fa076e1d7e810f53ddf4801
  
https://github.com/django/django/commit/5f8bf4368d79324f3fa076e1d7e810f53ddf4801
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/Makefile

  Log Message:
  ---
  [1.6.x] Allowed overriding variables in docs/Makefile.

Backport of c694e6220e from master



-- 
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/51f649988ad23_61d6fb9d48121831%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f8e643: [1.5.x] Allowed overriding variables in docs/Makef...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f8e6434912784b8055ba33ca110047f5b5bb2856
  
https://github.com/django/django/commit/f8e6434912784b8055ba33ca110047f5b5bb2856
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/Makefile

  Log Message:
  ---
  [1.5.x] Allowed overriding variables in docs/Makefile.

Backport of c694e6220e from master



-- 
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/51f64991c16af_3deb1247d58797e1%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c694e6: Allowed overriding variables in docs/Makefile.

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c694e6220ec78ed28ec7f621035ec21c8923a0c1
  
https://github.com/django/django/commit/c694e6220ec78ed28ec7f621035ec21c8923a0c1
  Author: minusf 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/Makefile

  Log Message:
  ---
  Allowed overriding variables in docs/Makefile.



-- 
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/51f6496a40aa8_7866b89d54480f3%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20820: Loaddata on dumpdata'd subclass fails

2013-07-29 Thread Django

#20820: Loaddata on dumpdata'd subclass fails
-+
 Reporter:  jeroen.pulles@…  |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.6-beta-1
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I have a problem with loaddata on a subclass of contrib.auth.User. The
 dumpdata generates data that looks fine. The JSON I get is identical to
 Django 1.5 which loads just fine. Loaddata in 1.6b1 fails to load that
 data, however. I get the impression that it is caused by subclassing, as
 none of the other relations in the models cause trouble. I have attached a
 small sample project with just the subclass to reproduce the problem
 ("sample.zip").

 Loaddata crashes with this exception ''ValueError: Problem installing
 fixture '/Volumes/prj/myapp/fixtures/ennu.json': "" needs to
 have a value for field "user" before this many-to-many relationship can be
 used.'' (This is the user-permission related manager complaining, by the
 way)

 This is what the MiniUser model looks like:

 {{{
 class MiniUser(User):
 mini = models.IntegerField()
 }}}

 This is a snippet from dumpdata:

 {{{
 ...
   {
 "pk": 1,
 "model": "myapp.miniuser",
 "fields": {
   "user_permissions": [],
   "mini": 123,
   "groups": []
 }
 ...
 }}}

 When I remove the "user_permissions" and "groups" properties (from
 auth.User) from the myapp.miniuser json, loaddata completes just fine.

-- 
Ticket URL: 
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/070.0fe33a6fa494eb68ff802d932a9ba75b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17413: Serialization or getting non-HTML version of form errors is not easy

2013-07-29 Thread Django

#17413: Serialization or getting non-HTML version of form errors is not easy
-+-
 Reporter:  kmike|Owner:  merb
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  form errors  | Triage Stage:  Accepted
  serialization  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by merb):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.b55b867f9b6bbb09aa50ebf25ca0ed1e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-29 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
--+
 Reporter:  loic84|Owner:  jezdez
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  localflavor   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Jannis Leidel ):

 In [changeset:"02ac44b29a25632fb6ae3ad40ed83f08565f51e9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="02ac44b29a25632fb6ae3ad40ed83f08565f51e9"
 [1.5.x] Fixed #20774 -- Mention the new django-localflavor app as a
 replacement for the contrib app. Backport from master.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.10a12036455dbaf1f4cdd505205a9f45%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20815: daemonize.py: unbuffered text IO error (python3)

2013-07-29 Thread Django

#20815: daemonize.py: unbuffered text IO error (python3)
--+
 Reporter:  alex01@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  python3 runfcgi open  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Note that FastCGI is deprecated 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/074.d1b490a1dbb5b07a43d5dcfa44a875ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 02ac44: [1.5.x] Fixed #20774 -- Mention the new django-loc...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 02ac44b29a25632fb6ae3ad40ed83f08565f51e9
  
https://github.com/django/django/commit/02ac44b29a25632fb6ae3ad40ed83f08565f51e9
  Author: Jannis Leidel 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M django/contrib/localflavor/__init__.py
M docs/ref/contrib/localflavor.txt

  Log Message:
  ---
  [1.5.x] Fixed #20774 -- Mention the new django-localflavor app as a 
replacement for the contrib app. Backport from master.



-- 
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/51f63ead70c10_60ba4b1d4c78670%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-29 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
--+
 Reporter:  loic84|Owner:  jezdez
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  localflavor   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Jannis Leidel ):

 In [changeset:"c456a277255e1b63ba4dcf6ed894e37ac4f05b63"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c456a277255e1b63ba4dcf6ed894e37ac4f05b63"
 [1.6.x] Fixed #20774 -- Mention the new django-localflavor app as a
 replacement for the contrib app. Backport from master.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.687f996be07bd231694285a2b71702a8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c456a2: [1.6.x] Fixed #20774 -- Mention the new django-loc...

2013-07-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: c456a277255e1b63ba4dcf6ed894e37ac4f05b63
  
https://github.com/django/django/commit/c456a277255e1b63ba4dcf6ed894e37ac4f05b63
  Author: Jannis Leidel 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/topics/localflavor.txt

  Log Message:
  ---
  [1.6.x] Fixed #20774 -- Mention the new django-localflavor app as a 
replacement for the contrib app. Backport from master.



-- 
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/51f63e997a182_215d581140ba%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 33e6cf: Fixed #20774 -- Mention the new django-localflavor...

2013-07-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 33e6cf5ec324bb1154ae1a0379f9c9ef6ff51420
  
https://github.com/django/django/commit/33e6cf5ec324bb1154ae1a0379f9c9ef6ff51420
  Author: Jannis Leidel 
  Date:   2013-07-29 (Mon, 29 Jul 2013)

  Changed paths:
M docs/topics/localflavor.txt

  Log Message:
  ---
  Fixed #20774 -- Mention the new django-localflavor app as a replacement for 
the contrib app.



-- 
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/51f63d9f4d963_620c753d4811098f%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20774: Update the localflavor topic guide when django-localflavor is ready

2013-07-29 Thread Django

#20774: Update the localflavor topic guide when django-localflavor is ready
--+
 Reporter:  loic84|Owner:  jezdez
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  localflavor   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Jannis Leidel ):

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


Comment:

 In [changeset:"33e6cf5ec324bb1154ae1a0379f9c9ef6ff51420"]:
 {{{
 #!CommitTicketReference repository=""
 revision="33e6cf5ec324bb1154ae1a0379f9c9ef6ff51420"
 Fixed #20774 -- Mention the new django-localflavor app as a replacement
 for the contrib app.
 }}}

-- 
Ticket URL: 
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.fb1af13f1ca3a1347cd07deae93859c7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20810: IOError raised when using EPS file in ImageField

2013-07-29 Thread Django

#20810: IOError raised when using EPS file in ImageField
-+-
 Reporter:  imatusov |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.5
  uploads/storage|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 "Won't fix" the issue with PIL & "needs info" as to whether or not it's a
 problem with Pillow.

-- 
Ticket URL: 
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.8e9dd912f47dd7fc20d8a84d2ebeefa0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20300: Django 1.5.1, update sql trouble

2013-07-29 Thread Django

#20300: Django 1.5.1, update sql trouble
-+-
 Reporter:  hjcnbckfd@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  update, orm, mysql,  | Triage Stage:
  postgresql |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by yann.malet@…):

 I stumble on this issue too earlier today on django 1.5.1.

 It is a mysql limitation (see the [http://dev.mysql.com/doc/refman/5.0/en
 /subquery-errors.html last bullet point])

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/077.f66a9e7176f9b805797cb45735240406%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20818: "Enter a valid email address." the msgid was changed on stable/1.5.x which caused its msgstr empty.

2013-07-29 Thread Django

#20818: "Enter a valid email address." the msgid was changed on stable/1.5.x 
which
caused its msgstr empty.
-+-
 Reporter:  gzerone@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Translations |  Version:  1.5
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  zh_CN translation| Triage Stage:
  email field|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by claudep):

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


Comment:

 Hi, translation issues are not tracked by this bug tracker. And
 unfortunately, this translation was added too late on Transifex to enter
 the 1.5 release. It will be translated in 1.6, though.

-- 
Ticket URL: 
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.8ead58dc0e9ca695faf72205922d47c2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20810: IOError raised when using EPS file in ImageField

2013-07-29 Thread Django

#20810: IOError raised when using EPS file in ImageField
-+-
 Reporter:  imatusov |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.5
  uploads/storage|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 @timo, could you just explain your "wontfix"? Did someone establish that
 this was not a problem with Pillow?

-- 
Ticket URL: 
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.bf42a306c66eda12df5d566b729e0b7f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20815: daemonize.py: unbuffered text IO error (python3)

2013-07-29 Thread Django

#20815: daemonize.py: unbuffered text IO error (python3)
--+
 Reporter:  alex01@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  python3 runfcgi open  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


Old description:

> When trying to run fcgi server I get "ValueError: can't have unbuffered
> text I/O"
>
> My python version and django version:
>
> $ python --version
> Python 3.2.3
>
> >>> django.get_version()
> '1.7.dev20130726184538'
>
> Can't start server:
> (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
> host=127.0.0.1 port=8100
> Traceback (most recent call last):
>   File "manage.py", line 10, in 
> execute_from_command_line(sys.argv)
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/management/__init__.py", line 397, in
> execute_from_command_line
> utility.execute()
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/management/__init__.py", line 390, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/management/base.py", line 240, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/management/base.py", line 283, in execute
> output = self.handle(*args, **options)
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/management/commands/runfcgi.py", line 22, in handle
> runfastcgi(args)
>   File "/home/jsmith/virtenv02/django-
> trunk/django/core/servers/fastcgi.py", line 176, in runfastcgi
> become_daemon(our_home_dir=options["workdir"], **daemon_kwargs)
>   File "/home/jsmith/virtenv02/django-trunk/django/utils/daemonize.py",
> line 28, in become_daemon
> so = open(out_log, 'a+', 0)
> ValueError: can't have unbuffered text I/O
>
> Server starts successfully and works if I give it daemonize=False option:
> (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
> host=127.0.0.1 port=8100 daemonize=False
>
> As far as I understand, this issue is specific to python3 and is related
> to changes in open function introduced in pep-3116
>
> Alex

New description:

 When trying to run fcgi server I get "ValueError: can't have unbuffered
 text I/O"

 My python version and django version:
 {{{
 $ python --version
 Python 3.2.3

 >>> django.get_version()
 '1.7.dev20130726184538'

 Can't start server:
 (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
 host=127.0.0.1 port=8100
 Traceback (most recent call last):
   File "manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/__init__.py", line 397, in
 execute_from_command_line
 utility.execute()
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/__init__.py", line 390, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/base.py", line 240, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/base.py", line 283, in execute
 output = self.handle(*args, **options)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/management/commands/runfcgi.py", line 22, in handle
 runfastcgi(args)
   File "/home/jsmith/virtenv02/django-
 trunk/django/core/servers/fastcgi.py", line 176, in runfastcgi
 become_daemon(our_home_dir=options["workdir"], **daemon_kwargs)
   File "/home/jsmith/virtenv02/django-trunk/django/utils/daemonize.py",
 line 28, in become_daemon
 so = open(out_log, 'a+', 0)
 ValueError: can't have unbuffered text I/O
 }}}
 Server starts successfully and works if I give it daemonize=False option:
 (virtenv02)jsmith@thinkpad01:~/virtenv02/mysite$ python manage.py runfcgi
 host=127.0.0.1 port=8100 daemonize=False

 As far as I understand, this issue is specific to python3 and is related
 to changes in open function introduced in pep-3116

 Alex

--

Comment:

 Unfortunately, this is old untested code. I wonder if the solution would
 be to simply forget the `0` argument (unbuffered) of the `open` call.
 Maybe someone more knowledgeable about buffered/unbuffered output may
 chime in to enlighten us?

-- 
T

Re: [Django] #20819: `staticfiles.views.serve` should return 404 response instead of raising `ImproperlyConfigured`

2013-07-29 Thread Django

#20819: `staticfiles.views.serve` should return 404 response instead of raising
`ImproperlyConfigured`
-+-
 Reporter:  mrmachine|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  contrib.staticfiles  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  staticfiles serve|  Needs documentation:  0
  ImproperlyConfigured   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by jezdez):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.ff78ef6340b28459bdb31c13302f8212%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20819: `staticfiles.views.serve` should return 404 response instead of raising `ImproperlyConfigured`

2013-07-29 Thread Django

#20819: `staticfiles.views.serve` should return 404 response instead of raising
`ImproperlyConfigured`
-+-
 Reporter:  mrmachine|  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.5
Component:  contrib.staticfiles  |   Keywords:  staticfiles serve
 Severity:  Normal   |  ImproperlyConfigured
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I use this view to serve static files without having to `collectstatic`
 all the time during development, but I don't want to have code like this
 to create my root urlconf:

 {{{
 urlpatterns = patterns('',
 # urls
 )

 if 'runserver' in sys.argv:
 urlpatterns += patterns('',
 url(r'^static/(.*)', 'django.contrib.staticfiles.views.serve',
 name='static'),
 )

 urlpatterns += patterns('',
 # more urls. e.g. a catch-all that includes the URLs of another app at
 the root level.
 url(r'^', include('myapp.urls')),
 )
 }}}

 The above example also means that the `static` URL cannot be reversed by
 name, because it's only present during development. In some cases it can
 be convenient to simply reverse a URL name like this directly from a
 template or Python code.

 If I leave the URL in my root urlconf and deploy to production to avoid
 these issues, and I forget to `collectstatic` after an update or if
 visitors request a static file that really doesn't exist, I get an HTTP
 500 error emailed to me.

 This view shouldn't do anything in production, but I think it should be
 sufficient to simply return a 404 error instead of raising
 `ImproperlyConfigured`. This is still an accurate error (static files that
 do exist will be served by the front-end server), and developers should
 know that a 404 for static media in production means they need to run
 `collectstatic`.

 I discussed this briefly with jezdez on IRC who seemed OK with this idea,
 as long as the documentation was clear that this view would return a 404
 and not return static files if used in production.

-- 
Ticket URL: 
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.510b4c581703caa09fe1c2cfed26adcc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20818: "Enter a valid email address." the msgid was changed on stable/1.5.x which caused its msgstr empty.

2013-07-29 Thread Django

#20818: "Enter a valid email address." the msgid was changed on stable/1.5.x 
which
caused its msgstr empty.
--+---
 Reporter:  gzerone@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.5
 Severity:  Normal|   Keywords:  zh_CN translation email field
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+---
 I have to post the bug here since Transifex didn't resolve it.

 File: django/conf/locale/zh_CN/LC_MESSAGES/django.po
 The msgid was "Enter a valid e-mail address." in stable/1.4.x.
 And now:

 {{{
 #: core/validators.py:104 forms/fields.py:464
 msgid "Enter a valid email address."
 msgstr ""
 }}}

 On branch: stable/1.5.x and master

 The msgstr is missing. Please make up the string: "输入一个有效的 Email 地
 址。"

 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/060.c5e5295ba98aae86cc6b12d1bb7ab122%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

74 matches

Mail list logo