date:20130806

Re: [Django] #3871: Use custom managers in reverse relations

2013-08-06 Thread Django

#3871: Use custom managers in reverse relations
-+-
 Reporter:  EspenG   |Owner:  v1v3kn
 Type:  New feature  |   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 akaariai):

 The patch in r17204-custom-reverse-managers.diff uses
 MyModel.m2mfield.manager('somemanager') while the call based syntax is
 MyModel.m2mfield('somemanager'). I am not sure which one is better.
 Opinions?

 I think either the `__call__` or .manager() based syntax should be
 adopted. Some solution would be welcome to this long standing issue.

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
--+
 Reporter:  ezra  |Owner:  ezra
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by charettes):

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


Comment:

 @ezra in this case I suggest you read the documentation regarding
 [https://docs.djangoproject.com/en/1.5/topics/http/views/#http-internal-
 server-error-view handling of runtime exceptions]. You should be able to
 inform your users something went wrong this way.

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

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

Re: [Django] #3871: Use custom managers in reverse relations

2013-08-06 Thread Django

#3871: Use custom managers in reverse relations
-+-
 Reporter:  EspenG   |Owner:  v1v3kn
 Type:  New feature  |   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 loic84):

 * cc: loic@… (added)


Comment:

 Proof of concept following discussion with @akaariai on IRC:

 [https://github.com/loic/django/compare/manager.__call__]

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2013-08-06 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by heppner.mark@…):

 There was a ternary operator in the {{{ __unicode__ }}} function where one
 option wasn't being cast as a unicode string. I missed it the first time.
 However, I still couldn't figure out why it was throwing the error only in
 the popup. Adding the object through the separate admin page worked fine.
 This error only appeared after updating from 1.4 to 1.5.

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

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

[Django] #20872: Bad error message if INITIAL_FORMS/TOTAL_FORMS > MAX_NUM_FORMS

2013-08-06 Thread Django

#20872: Bad error message if INITIAL_FORMS/TOTAL_FORMS > MAX_NUM_FORMS
+
Reporter: russellm | Owner: nobody
Type: Bug | Status: new
Component: Forms |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 |
+
Formset handling currently enforces a MAX_NUM_FORMS check on incoming form
data. However, there is no checking or validation that MAX_NUM_FORMS is
actually equal to or greater than INITIAL_FORMS/TOTAL_FORMS.

As a result, it's possible to construct and display a formset, but then
have that formset fail (with a "list index out of range error") on form
submission.

This manifested for me as the following: A model in the admin with
inlines; the inline was filled with 2023 inline objects, and the default
MAX_NUM_FORMS (1000 was in use. The page takes a long time to load, but it
*does* load; when you hit submit, you get the "list index out of range"
error as a 500 page, with no suggestion of the underlying problem.

I haven't tested, but AFAICT, the same problem will manifest with a lot
less data if you set MAX_NUM_FORMS to a lower value.

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

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

Re: [Django] #9532: Add min_num and validate_min on formsets (was: Add min_num on formsets)

2013-08-06 Thread Django

#9532: Add min_num and validate_min on formsets
-+-
 Reporter:  gsf  |Owner:  yokomizor
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rogério Yokomizo ):

 * cc: me@… (added)


Comment:

 Patch rebased.

 Could someone please review?

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

 About backward problematic, I don't know how can I do that. Any
 suggestions?

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

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

Re: [Django] #13252: Use the natural key instead of the primary key when serializing

2013-08-06 Thread Django

#13252: Use the natural key instead of the primary key when serializing
-+-
 Reporter:  SmileyChris  |Owner:
 Type:  New feature  |  mtredinnick
Component:  Core |   Status:  new
  (Serialization)|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mrmachine):

 * needs_better_patch:  1 => 0


Comment:

 Rebased onto master and changes for feedback integrated.

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
--+
 Reporter:  ezra  |Owner:  ezra
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by ezra):

 I don't know Django core code well enough to recommend the correct way to
 fix this, however I'd love to inform my users if something goes wrong
 while they were trying to do something.

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

Re: [Django] #19844: Uniqueness validation of USERNAME_FIELD should be overridable.

2013-08-06 Thread Django

#19844: Uniqueness validation of USERNAME_FIELD should be overridable.
--+
Reporter: josh@…|Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.auth | Version: master
Severity: Normal| Resolution:
Keywords:| Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
--+
Changes (by russellm):

* status: closed => new
* cc: gsoc2013-checks (added)
* resolution: wontfix =>
* version: 1.5-rc-1 => master
* type: Bug => Cleanup/optimization
* stage: Design decision needed => Accepted

Comment:

I'm going to reopen this in the context of the GSoC project reworking
validation.

Previously, we were in a position where we could only issue errors, and it
was sufficiently important to raise *any* notification for this problem
that an error was called for.

Part of the remit for the GSoC project is to introduce "warnings". Given
that this will give us extra flexibility to raise attention about problems
without preventing progress, I think a warning may be called for here
rather than a hard error.

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

Re: [Django] #20871: Can't login with pressing enter

2013-08-06 Thread Django

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

Comment:

Can't reproduce this myself. I can log in using the enter key on both the
admin login screen, and a login screen based on Django's auth login view.

It sounds like there's something going on with either your browser, or
you've got some interesting override in place in local templates.

In order to confirm this is a Django problem, you'll need to reproduce
this on a *clean* Django install (i.e., admin login screen out of the box
-- no local modifications, just start a clean project and activate the
admin interface), on a browser *without* any plugins or extensions. If you
can still reproduce, let us know the exact details of your platform,
operating system, browser, etc.

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
--+
 Reporter:  ezra  |Owner:  ezra
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by charettes):

 Thinking of it I'm not sure we should fix this at the form level.

 I think that returning a 500 and triggering an admin report (mail_admin,
 sentry, ...) is the correct way to handle this.

 If we choose to display the user a message we must make sure the exception
 is still triggering an exception report.

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

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

Re: [Django] #20112: UnicodeDecodeError with not UTF-8 charset database connection

2013-08-06 Thread Django

#20112: UnicodeDecodeError with not UTF-8 charset database connection
--+
 Reporter:  err   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  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:  0 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 Closing given OP's comment and no clear consensus on what to do.

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

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
--+
 Reporter:  ezra  |Owner:  ezra
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Thanks for the patch, however, I think it's a bad idea to introduce a
 dependency of `contrib.messages` in `contrib.auth`. This would also
 require a test for the new feature.

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

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

Re: [Django] #20870: django.utils.functional.cached_property should be documented

2013-08-06 Thread Django

#20870: django.utils.functional.cached_property should be documented
---+--
 Reporter:  EvilDMP|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by MarkusH):

 * cc: info@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #20871: Can't login with pressing enter

2013-08-06 Thread Django

#20871: Can't login with pressing enter
---+
 Reporter:  mightyiam  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+
 Hi,
 Pressing enter in the admin login form doesn't seem to do anything.
 It would be nice, and is expected of a form, to be able to type in
 credentials and press enter.

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

[Django] #20870: django.utils.functional.cached_property should be documented

2013-08-06 Thread Django

#20870: django.utils.functional.cached_property should be documented
---+
 Reporter:  EvilDMP|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 It's a very common pattern in Django to find oneself calling a method in a
 view to check something - `if MyModel.mymethod():` - then a moment later
 in the template `{% for things in mymodel.mymethod %}` - so `mymethod()`
 gets called twice.

 If ``mymethod()` is very expensive, this could be a problem.

 `django.utils.functional.cached_property` already exists and solves the
 problem. Doesn't it deserve to be documented so that we can all enjoy it?

 https://github.com/django/django/blob/master/django/utils/functional.py#L38

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
--+
 Reporter:  ezra  |Owner:  ezra
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by charettes):

 * has_patch:  0 => 1
 * type:  Uncategorized => New feature
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #12288: Validate that values in INSTALLED_APPS are unique

2013-08-06 Thread Django

Comment (by charettes):

As answered on [https://groups.google.com/d/msg/django-core-
mentorship/pv824RuH_IQ/W2bKS60lXkUJ Django Core Membership] (message has
been deleted for no reasons):

There's already a check in `django.conf.Settings` to make sure
`INSTALLED_APPS` is not a string so I'd suggest you add this check at the
same place.

Concerning the tests I suggest you take a look at the `settings_tests`
test application. However you might have to move the check to
`BaseSettings.__setattr__` if you want to use the testing strategy used in
`settings_tests.TrailingSlashURLTests`.

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

Re: [Django] #16989: Problem with DEFAULT_DB_ALIAS in settings

2013-08-06 Thread Django

#16989: Problem with DEFAULT_DB_ALIAS in settings
-+-
 Reporter:  sergeybe@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.3
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  DEFAULT_DB_ALIAS | Triage Stage:
  settings   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 Thought I'd chime in -- the DEFAULT_DB_ALIAS constant is required when
 using the python package "south".

 https://pypi.python.org/pypi/South/

 Not really a setting, but it IS a required constant when using South and
 running "syncdb", but clearly it is not a django issue.

 Definitely invalid, but if anyone happens to find this know that it's a
 South thing and I'm pretty sure it's behaving as expected.

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

Re: [Django] #15363: get_queryset & get_query_set

2013-08-06 Thread Django

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

Comment:

@asteinlein I disagree with your ''people will be thinking'' assertion. I
think most of Django users will be referring to

[https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.list_filter
the documentation] when subclassing `SimpleListFilter` since it's a newly
introduced feature.

However I agree that the whole `ListFilter` method names (missing `get_`)
might be confusing for people used to override `BaseModelAdmin` methods
thus I suggest you open new ticket suggesting to prefix `ListFilter`
methods. It should be easy to write a patch using the `RenameMethodsBase`
and we should be more confident shipping another method rename once people
got their hands on Django 1.6 and played with the `get_query_set` one.

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

Re: [Django] #20836: to_field lost when adding via raw_id_fields

2013-08-06 Thread Django

#20836: to_field lost when adding via raw_id_fields
+--
 Reporter:  CollinAnderson  |Owner:  CollinAnderson
 Type:  Bug |   Status:  assigned
Component:  contrib.admin   |  Version:  1.6-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timo):

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

Re: [Django] #20699: Extra blank choice '-----' when using models.fields.NullBooleanField with custom choices.

2013-08-06 Thread Django

#20699: Extra blank choice '-' when using models.fields.NullBooleanField 
with
custom choices.
-+-
 Reporter:  tomas.krajca@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  NullBooleanField |  Needs documentation:  0
  extra blank choice |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I believe this is fixed by #20649 (the extra blank choice will no longer
 appear).

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

Re: [Django] #20865: admin raw_id_fields does not call value in limit_choices_to

2013-08-06 Thread Django

#20865: admin raw_id_fields does not call value in limit_choices_to
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e3e0cf8a0f75ae18bc401182bfbdea2c27bb0244"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e3e0cf8a0f75ae18bc401182bfbdea2c27bb0244"
 [1.6.x] Fixed #20865 -- Fixed raw_id_fields to work with callable
 limit_choices_to.

 Backport of d53e574676 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/072.ecafe178955a282bf1c16e5605412f8c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e3e0cf: [1.6.x] Fixed #20865 -- Fixed raw_id_fields to wor...

2013-08-06 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e3e0cf8a0f75ae18bc401182bfbdea2c27bb0244
  
https://github.com/django/django/commit/e3e0cf8a0f75ae18bc401182bfbdea2c27bb0244
  Author: Collin Anderson 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M django/contrib/admin/widgets.py
M tests/admin_widgets/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #20865 -- Fixed raw_id_fields to work with callable 
limit_choices_to.

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

[django/django] d53e57: Fixed #20865 -- Fixed raw_id_fields to work with c...

2013-08-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d53e574676ba0809394017f1f3a5bc24512e5bed
  
https://github.com/django/django/commit/d53e574676ba0809394017f1f3a5bc24512e5bed
  Author: Collin Anderson 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M django/contrib/admin/widgets.py
M tests/admin_widgets/tests.py

  Log Message:
  ---
  Fixed #20865 -- Fixed raw_id_fields to work with callable limit_choices_to.



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

Re: [Django] #20865: admin raw_id_fields does not call value in limit_choices_to

2013-08-06 Thread Django

#20865: admin raw_id_fields does not call value in limit_choices_to
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d53e574676ba0809394017f1f3a5bc24512e5bed"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d53e574676ba0809394017f1f3a5bc24512e5bed"
 Fixed #20865 -- Fixed raw_id_fields to work with callable
 limit_choices_to.
 }}}

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

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

Re: [Django] #16282: CommentTemplateTagTests.testRenderCommentFormFromObjectWithQueryCount fails on MySQL

2013-08-06 Thread Django

#16282: CommentTemplateTagTests.testRenderCommentFormFromObjectWithQueryCount 
fails
on MySQL
---+
 Reporter:  ojii   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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:   => wontfix


Comment:

 Marking as won't fix in light of no recent activity and the fact that
 `contrib.comments` is deprecated.

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

Re: [Django] #20866: Password Reset does not catch exception from send_mail

2013-08-06 Thread Django

#20866: Password Reset does not catch exception from send_mail
---+--
 Reporter:  ezra   |Owner:  ezra
 Type:  Uncategorized  |   Status:  assigned
Component:  contrib.auth   |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by ezra):

 * owner:  nobody => ezra
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Attached a potential 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.5263e17bf14b5669d6af81b6376d306d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20218: Default authorization backend returns False when queried for object level permissions

2013-08-06 Thread Django

#20218: Default authorization backend returns False when queried for object 
level
permissions
---+
 Reporter:  soren@…|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  contrib.auth   |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  auth   | 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):

 * component:  Uncategorized => contrib.auth


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

Re: [Django] #20865: admin raw_id_fields does not call value in limit_choices_to

2013-08-06 Thread Django

#20865: admin raw_id_fields does not call value in limit_choices_to
-+-
 Reporter:  CollinAnderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:
 Severity:  Normal   |  1.6-beta-1
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by loic84):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good to me.

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

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

Re: [Django] #14286: Support for BigAutoField

2013-08-06 Thread Django

#14286: Support for BigAutoField
-+-
 Reporter:  hongrich |Owner:  mmcnickle
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ludo):

 * cc: ludo@… (added)


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

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

Re: [Django] #20865: admin raw_id_fields does not call value in limit_choices_to

2013-08-06 Thread Django

#20865: admin raw_id_fields does not call value in limit_choices_to
+--
 Reporter:  CollinAnderson  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by CollinAnderson):

 * needs_tests:  1 => 0


Comment:

 pull request now has a test https://github.com/django/django/pull/1442

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

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

[Django] #20869: Prevent repetitive output to counter BREACH-type attacks

2013-08-06 Thread Django

#20869: Prevent repetitive output to counter BREACH-type attacks
---+
Reporter: patrys | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.csrf |Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
Currently the CSRF middleware sets the cookie value to the plain value of
the token. This makes it possible to try to guess the token by trying
longer and longer prefix matches. An effective countermeasure would be to
prevent repetitive output from appearing in case a guess matches the CSRF
prefix.

As it's a prefix-based attack that relies mostly on the server's response,
one way to counter it would be to salt the token with a random prefix and
when validating discard all but the last n characters of both the cookie
and the hidden field value. This would also keep the currently suggested
AJAX solution working (JS would just submit the salted value along with
the randomized payload).

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

[django/django] 4c9008: [1.6.x] Added section labels in cache docs

2013-08-06 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 4c90081b5b296bc2d7d9689609bfe1857e35b091
  
https://github.com/django/django/commit/4c90081b5b296bc2d7d9689609bfe1857e35b091
  Author: Leandro Regueiro 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  [1.6.x] Added section labels in cache docs

Backport of 709cd2c4b7 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/52011cd9ac4f5_206b13e3d4c389e0%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 709cd2: Added section labels in cache docs

2013-08-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 709cd2c4b751bcdfed7c8a27306778a758523658
  
https://github.com/django/django/commit/709cd2c4b751bcdfed7c8a27306778a758523658
  Author: Leandro Regueiro 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  Added section labels in cache docs



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

[django/django] d4c19a: [1.5.x] Added section labels in cache docs

2013-08-06 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d4c19a6e7e45f3ff4dbbb2424904b726709bb24f
  
https://github.com/django/django/commit/d4c19a6e7e45f3ff4dbbb2424904b726709bb24f
  Author: Leandro Regueiro 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M docs/topics/cache.txt

  Log Message:
  ---
  [1.5.x] Added section labels in cache docs

Backport of 709cd2c4b7 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/52011cbe2e109_208b1469d48579f1%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20863: Sessions backend changing could be clearer

2013-08-06 Thread Django

#20863: Sessions backend changing could be clearer
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #20856: Error with admin popups: expected a character buffer object

2013-08-06 Thread Django

#20856: Error with admin popups: expected a character buffer object
-+-
 Reporter:  heppner.mark@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.5
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  admin, str,  | Triage Stage:
  character, inline, popup   |  Unreviewed
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:   => needsinfo


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

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

Re: [Django] #20865: admin raw_id_fields does not call value in limit_choices_to

2013-08-06 Thread Django

#20865: admin raw_id_fields does not call value in limit_choices_to
+--
 Reporter:  CollinAnderson  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timo):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

2013-08-06 Thread Django

#20003: URLValidator does not accept urls with usernames or passwords in them
--+
 Reporter:  marshall@…|Owner:  matiasb
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  URLValidator  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  0 => 1


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

[django/django] 80b95a: [1.6.x] Fixed #19918 -- Modified select_for_update...

2013-08-06 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 80b95a2b1fc8c8425a81a23706af971061dc238f
  
https://github.com/django/django/commit/80b95a2b1fc8c8425a81a23706af971061dc238f
  Author: Alex Cucu 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M django/db/models/query.py
M tests/select_for_update/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #19918 -- Modified select_for_update to run on the write 
database.

Backport of 1c64a0f29e 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/52010f22700a3_20aac6fd549808%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19918: select_for_update runs on db_for_read rather than db_for_write

2013-08-06 Thread Django

#19918: select_for_update runs on db_for_read rather than db_for_write
-+-
 Reporter:   |Owner:  kux
  alexandruioan.cucu@…   |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"80b95a2b1fc8c8425a81a23706af971061dc238f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="80b95a2b1fc8c8425a81a23706af971061dc238f"
 [1.6.x] Fixed #19918 -- Modified select_for_update to run on the write
 database.

 Backport of 1c64a0f29e 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/086.addb0258c9d932bb9d45e0b98701364d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20868: Security policy mentions nothing about sending emails to django-announce

2013-08-06 Thread Django

#20868: Security policy mentions nothing about sending emails to django-announce
--+
 Reporter:  garrison  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 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 garrison):

 Thanks, guys!

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

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

Re: [Django] #20868: Security policy mentions nothing about sending emails to django-announce

2013-08-06 Thread Django

#20868: Security policy mentions nothing about sending emails to django-announce
--+
 Reporter:  garrison  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 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 russellm):

 Jacob has just posted an announcement to django-announce; I'll leave this
 ticket open as a note that we should modify the text for our security
 policy to indicate django-announce is a channel that will be used.

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

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

Re: [Django] #20868: Security policy mentions nothing about sending emails to django-announce

2013-08-06 Thread Django

#20868: Security policy mentions nothing about sending emails to django-announce
--+
 Reporter:  garrison  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by russellm):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Thanks for the suggestion, @garrison.

 This particular announcement is a bit of an unusual case - to my
 knowledge, this is the first time we've made a security announcement that
 *hasn't* involved a new release of Django.

 However, your point is a fair one -- we maintain django-announce as a low
 traffic mailing list specifically so that important messages get out
 there, and this is definitely an important message. I'll raise this with
 Jacob.

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

[Django] #20868: Security policy mentions nothing about sending emails to django-announce

2013-08-06 Thread Django

#20868: Security policy mentions nothing about sending emails to django-announce
---+
 Reporter:  garrison   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 This morning I happened to notice that Jacob posted a security
 announcement to the Django development blog, and I was surprised I had not
 received an email about it (like most other such announcements before it).
 I re-read the documentation on Django's security policies:

 > On the day of disclosure, we will take the following steps:
 >
 > 1. Apply the relevant patch(es) to Django’s codebase. The commit
 messages for these patches will indicate that they are for security
 issues, but will not describe the issue in any detail; instead, they will
 warn of upcoming disclosure.
 > 2. Issue the relevant release(s), by placing new packages on the Python
 Package Index and on the Django website, and tagging the new release(s) in
 Django’s git repository.
 > 3. Post a public entry on the official Django development blog,
 describing the issue and its resolution in detail, pointing to the
 relevant patches and new releases, and crediting the reporter of the issue
 (if the reporter wishes to be publicly identified).

 To my surprise, I realized that emails to django-announce are only
 //incidentally// triggered if the security issue happens to result in a
 new release of Django.  But yet I had come to rely on such emails,
 assuming it was the preferred avenue for learning of Django security
 announcements.  Despite having read the security policy document several
 times in my life, I never noticed this fine detail in it.

 I think there are two potential solutions here:

 * Add a note to the above list, saying all security issues will be sent to
 django-announce as well; or,
 * Add a note above explicitly mentioning that only security issues that
 trigger a new release will be reported on django-announce

 I of course prefer the first option, as it keeps in line with expectations
 people (including myself) may have developed.

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

[django/django] 1c64a0: Fixed #19918 -- Modified select_for_update to run ...

2013-08-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1c64a0f29e47a3da1dfac06b04ef84280bd809a7
  
https://github.com/django/django/commit/1c64a0f29e47a3da1dfac06b04ef84280bd809a7
  Author: Alex Cucu 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M django/db/models/query.py
M tests/select_for_update/tests.py

  Log Message:
  ---
  Fixed #19918 -- Modified select_for_update to run on the write database.



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

Re: [Django] #19918: select_for_update runs on db_for_read rather than db_for_write

2013-08-06 Thread Django

#19918: select_for_update runs on db_for_read rather than db_for_write
-+-
 Reporter:   |Owner:  kux
  alexandruioan.cucu@…   |   Status:  closed
 Type:  Bug  |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1c64a0f29e47a3da1dfac06b04ef84280bd809a7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1c64a0f29e47a3da1dfac06b04ef84280bd809a7"
 Fixed #19918 -- Modified select_for_update to run on the write database.
 }}}

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

Re: [Django] #15511: MultiValueField should allow subfield requirement

2013-08-06 Thread Django

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

Comment:

In [changeset:"12806758347dfd63a3cd1bfc0d925c09fdbd9cff"]:
{{{
#!CommitTicketReference repository=""
revision="12806758347dfd63a3cd1bfc0d925c09fdbd9cff"
Fixed #15511 -- Allow optional fields on ``MultiValueField` subclasses.

The `MultiValueField` class gets a new ``require_all_fields`` argument
that
defaults to ``True``. If set to ``False``, individual fields can be made
optional, and a new ``incomplete`` validation error will be raised if any
required fields have empty values.

The ``incomplete`` error message can be defined on a `MultiValueField`
subclass or on each individual field. Skip duplicate errors.
}}}

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

[django/django] 128067: Fixed #15511 -- Allow optional fields on ``MultiVa...

2013-08-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 12806758347dfd63a3cd1bfc0d925c09fdbd9cff
  
https://github.com/django/django/commit/12806758347dfd63a3cd1bfc0d925c09fdbd9cff
  Author: Tai Lee 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M django/forms/fields.py
M docs/ref/forms/fields.txt
M docs/releases/1.7.txt
M tests/forms_tests/tests/test_forms.py

  Log Message:
  ---
  Fixed #15511 -- Allow optional fields on ``MultiValueField` subclasses.

The `MultiValueField` class gets a new ``require_all_fields`` argument that
defaults to ``True``. If set to ``False``, individual fields can be made
optional, and a new ``incomplete`` validation error will be raised if any
required fields have empty values.

The ``incomplete`` error message can be defined on a `MultiValueField`
subclass or on each individual field. Skip duplicate errors.



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

Re: [Django] #20867: Allow Form.clean() to target specific fields when raising ValidationError.

2013-08-06 Thread Django

#20867: Allow Form.clean() to target specific fields when raising 
ValidationError.
-+--
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+--
Changes (by loic84):

 * status:  new => assigned
 * needs_better_patch:   => 1
 * needs_tests:   => 0
 * owner:  nobody => loic84
 * needs_docs:   => 1
 * has_patch:  0 => 1


Comment:

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

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

[Django] #20867: Allow Form.clean() to target specific fields when raising ValidationError.

2013-08-06 Thread Django

#20867: Allow Form.clean() to target specific fields when raising 
ValidationError.
-+
 Reporter:  loic84   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Forms|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 The goal would be to unlock the following API:

 {{{
 def clean(self):
 errors = {}
 if condition1:
 errors['field1'] = ValidationError('message1', code='code')
 if condition2:
 errors['field2'] = ValidationError('message2', code='code')
 raise ValidationError(errors)
 }}}

 Most of the groundwork has been done for #20199.

 We would need to document passing a `dict` to `ValidationError`, just like
 we already document passing a `list` in
 [https://docs.djangoproject.com/en/dev/ref/forms/validation/#raising-
 validationerror ref/forms/validation/#raising-validationerror].

 This would probably deprecate or reduce the need for the pattern discussed
 in [https://docs.djangoproject.com/en/dev/ref/forms/validation/#form-
 subclasses-and-modifying-field-errors ref/forms/validation/#form-
 subclasses-and-modifying-field-errors].

 Refs #20199 #16986.

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

Re: [Django] #20852: Apostrophes after code markup render as left quote

2013-08-06 Thread Django

#20852: Apostrophes after code markup render as left quote
---+-
 Reporter:  icedream91@…   |Owner:  dominicrodger
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"c33d1ca1d98003de29cdecb6080b52c5c52139bd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c33d1ca1d98003de29cdecb6080b52c5c52139bd"
 Fixed #20852 - Fixed incorrectly generated left quotes in docs.

 Sphinx generates left single quotes for apostrophes after
 code markup, when right single quotes are required. The
 easiest way to fix this is just by inserting the unicode
 character for a right single quote.

 Instances of the problem were found by looking for
 ">‘" in the generated HTML.
 }}}

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

[django/django] c33d1c: Fixed #20852 - Fixed incorrectly generated left qu...

2013-08-06 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c33d1ca1d98003de29cdecb6080b52c5c52139bd
  
https://github.com/django/django/commit/c33d1ca1d98003de29cdecb6080b52c5c52139bd
  Author: Dominic Rodger 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M docs/howto/custom-management-commands.txt
M docs/howto/error-reporting.txt
M docs/intro/tutorial05.txt
M docs/ref/class-based-views/mixins-date-based.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/auth.txt
M docs/ref/contrib/comments/moderation.txt
M docs/ref/django-admin.txt
M docs/ref/models/options.txt
M docs/ref/models/querysets.txt
M docs/ref/settings.txt
M docs/ref/templates/api.txt
M docs/releases/1.3.txt
M docs/releases/1.6.txt
M docs/releases/1.7.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/db/managers.txt
M docs/topics/db/queries.txt
M docs/topics/db/tablespaces.txt
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  Fixed #20852 - Fixed incorrectly generated left quotes in docs.

Sphinx generates left single quotes for apostrophes after
code markup, when right single quotes are required. The
easiest way to fix this is just by inserting the unicode
character for a right single quote.

Instances of the problem were found by looking for
">‘" in the generated HTML.



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

Re: [Django] #19320: Ability to leverage cache key generation for cache templatetag

2013-08-06 Thread Django

#19320: Ability to leverage cache key generation for cache templatetag
-+-
 Reporter:  Alex hayes   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Duplicate of #19253

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

Re: [Django] #16986: Model.clean cannot report errors on individual fields

2013-08-06 Thread Django

#16986: Model.clean cannot report errors on individual fields
-+
 Reporter:  davidfstr|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Marc Tamlyn ):

 In [changeset:"0b771fcf2923cef1b0d759fda79907c39ad733b4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0b771fcf2923cef1b0d759fda79907c39ad733b4"
 Merge pull request #1441 from loic/ticket16986

 Fixed #16986 -- Model.clean() can report errors on individual fields.
 }}}

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

[django/django] 71093d: Fixed #16986 -- Model.clean() can report errors on...

2013-08-06 Thread GitHub

Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 71093d22b62548fc2667468f1ae9e28f4fef30db

https://github.com/django/django/commit/71093d22b62548fc2667468f1ae9e28f4fef30db
Author: Loic Bistuer
Date: 2013-08-05 (Mon, 05 Aug 2013)

Changed paths:
M tests/model_forms/models.py
M tests/model_forms/tests.py

Log Message:
---
Fixed #16986 -- Model.clean() can report errors on individual fields.

This commit provides the tests for this issue but the actual problem was solved
by the ValidationError refactor in f34cfec and ee77d4b.

Refs #20199.

Commit: 0b771fcf2923cef1b0d759fda79907c39ad733b4

https://github.com/django/django/commit/0b771fcf2923cef1b0d759fda79907c39ad733b4
Author: Marc Tamlyn
Date: 2013-08-06 (Tue, 06 Aug 2013)

Changed paths:
M tests/model_forms/models.py
M tests/model_forms/tests.py

Log Message:
---
Merge pull request #1441 from loic/ticket16986

Fixed #16986 -- Model.clean() can report errors on individual fields.

Compare: https://github.com/django/django/compare/263b873599a5...0b771fcf2923

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

Re: [Django] #16986: Model.clean cannot report errors on individual fields

2013-08-06 Thread Django

#16986: Model.clean cannot report errors on individual fields
-+
 Reporter:  davidfstr|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Loic Bistuer ):

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


Comment:

 In [changeset:"71093d22b62548fc2667468f1ae9e28f4fef30db"]:
 {{{
 #!CommitTicketReference repository=""
 revision="71093d22b62548fc2667468f1ae9e28f4fef30db"
 Fixed #16986 -- Model.clean() can report errors on individual fields.

 This commit provides the tests for this issue but the actual problem was
 solved
 by the ValidationError refactor in f34cfec and ee77d4b.

 Refs #20199.
 }}}

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

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

2013-08-06 Thread Django

#20199: Allow ModelForm to override error messages defined in model fields.
-+
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Loic Bistuer ):

 In [changeset:"71093d22b62548fc2667468f1ae9e28f4fef30db"]:
 {{{
 #!CommitTicketReference repository=""
 revision="71093d22b62548fc2667468f1ae9e28f4fef30db"
 Fixed #16986 -- Model.clean() can report errors on individual fields.

 This commit provides the tests for this issue but the actual problem was
 solved
 by the ValidationError refactor in f34cfec and ee77d4b.

 Refs #20199.
 }}}

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

Re: [Django] #15511: MultiValueField should allow subfield requirement

2013-08-06 Thread Django

#15511: MultiValueField should allow subfield requirement
-+
 Reporter:  jdunck   |Owner:  nobody
 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
-+
Changes (by mrmachine):

 * needs_better_patch:  1 => 0


Comment:

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

Re: [Django] #19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName) syntax

2013-08-06 Thread Django

#19182: ModelAdmin.lookup_allowed should also check for ('fieldname', ClassName)
syntax
-+-
 Reporter:  gauss|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  modeladmin   | Triage Stage:  Accepted
  lookup_allowed |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by julien):

 Most tests for `list_filter` should normally be in
 https://github.com/django/django/blob/master/tests/admin_filters/tests.py

 After a quick look it seems there are also a few in `admin_views`, for
 example:
 
https://github.com/django/django/blob/1b47508ac88c1b1ee6ae71f032abb268395ac00e/tests/admin_views/tests.py#L411-L480

 It would be very helpful to write a failing test reproducing the
 `SuspiciousOperation` error.

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

Re: [Django] #17424: Using exclude on a queryset with an annotate field gives attribute error.

2013-08-06 Thread Django

#17424: Using exclude on a queryset with an annotate field gives attribute 
error.
-+-
 Reporter:  joseph.helfer@…  |Owner:  lrekucki
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   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
-+-

Comment (by akaariai):

 I am going to investigate the join_type issue. Maybe there are other cases
 where None could be promoted accidentally, like combining two querysets
 with |.

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

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

[django/django] 363b81: [1.6.x] Fixed ordering related test failure

2013-08-06 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 363b81c59cc0252f605de7d30433934b4662cfb3
  
https://github.com/django/django/commit/363b81c59cc0252f605de7d30433934b4662cfb3
  Author: Anssi Kääriäinen 
  Date:   2013-08-06 (Tue, 06 Aug 2013)

  Changed paths:
M tests/foreign_object/models.py
M tests/foreign_object/tests.py

  Log Message:
  ---
  [1.6.x] Fixed ordering related test failure

Also PEP8 + python_2_unicode_compatible cleanup done.

Backport of 263b873599 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/5200a3104120d_67a9c09d4c1804b%40hookshot-fe5-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

63 matches

Mail list logo