Re: [Django] #9532: min_num on formsets

[Django]

#9532: min_num on formsets
-+
 Reporter:  gsf  |Owner:  AnkitBagaria
 Type:  New feature  |   Status:  assigned
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:  1|UI/UX:  0
-+

Comment (by tback):

 Sorry, it's not fixed yet. BaseModelFormsets are still broken. The current
 state of my work is here: https://github.com/tback/django/tree/formset-
 min-num

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

Re: [Django] #15896: unittest docs say import django.utils, should be djanto.test

[Django]

#15896: unittest docs say import django.utils, should be djanto.test
---+--
 Reporter:  RoySmith   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 tuomas.salo@…):

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


Comment:

 A problem persists. The docs start by samples with `from django.utils
 import unittest`, but the example `tests.py` created by `python manage.py
 startapp` says `from django.test import TestCase`. That might confuse
 people starting to write tests. The docs do mention something about the
 difference,
 
[https://docs.djangoproject.com/en/dev/topics/testing/overview/#django.test.TestCase.client
 but only after a few pagefuls].

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

[Django] #19999: first app not running

[Django]

#1: first app not running
-+
 Reporter:  anonymous|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Wwhen i run the default app created it shows this error :

 C:\Users\dgupta\Documents\django\testproject\mysite>python -m  manage
 syncdb
 TypeError: Error when calling the metaclass bases
 __init__() keywords must be strings

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

Re: [Django] #19997: Custom EMPTY_VALUES for form fields.

[Django]

#19997: Custom EMPTY_VALUES for form fields.
--+
 Reporter:  loic84|Owner:  loic84
 Type:  Cleanup/optimization  |   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):

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

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

Re: [Django] #19998: loaddata --ignorenonexistent not working for XML based fixtures

[Django]

#19998: loaddata --ignorenonexistent not working for XML based fixtures
-+-
 Reporter:  sigi |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  master
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by sigi):

 * version:  1.5 => 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19983: Improving this part from confusion

[Django]

#19983: Improving this part from confusion
-+-
 Reporter:  fourmikichante@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   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
-+-
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19985: Suggested improvement for example with customizing templates

[Django]

#19985: Suggested improvement for example with customizing templates
---+--
 Reporter:  marvmolt@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  TEMPLATE_DIRS  | 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):

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


Comment:

 `TEMPLATE_DIRS` no longer appears in the default project template as of
 3f1c7b70537330435e2ec2fca9550f7b7fa4372e so this seems moot.

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

Re: [Django] #19951: Avoid ValueError in admin when passing a string as PK for an inherited model with an integer PK field

[Django]

#19951: Avoid ValueError in admin when passing a string as PK for an inherited
model with an integer PK field
-+-
 Reporter:  anonymous|Owner:  ikks
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin inheritance| Triage Stage:
  integer PK |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"e2ee02c5bd412a6a1b33353cac1a222be989d71f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2ee02c5bd412a6a1b33353cac1a222be989d71f"
 Fixed #19951 -- Admin: Invalid model PK values shouldn't cause 500 status.

 Avoid ValueError in admin when passing a string as PK for an inherited
 model with an integer PK field.

 Thanks ikks for the patch. See also #11191.
 }}}

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

[django/django] e2ee02: Fixed #19951 -- Admin: Invalid model PK values sho...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e2ee02c5bd412a6a1b33353cac1a222be989d71f
  
https://github.com/django/django/commit/e2ee02c5bd412a6a1b33353cac1a222be989d71f
  Author: Igor Támara 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

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

  Log Message:
  ---
  Fixed #19951 -- Admin: Invalid model PK values shouldn't cause 500 status.

Avoid ValueError in admin when passing a string as PK for an inherited
model with an integer PK field.

Thanks ikks for the patch. See also #11191.



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

[django/django] 9ba0e4: Fixed minor warnings in tests.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9ba0e4e4ee2725679ae5cb9e3dd637b0208e5ad3
  
https://github.com/django/django/commit/9ba0e4e4ee2725679ae5cb9e3dd637b0208e5ad3
  Author: Loic Bistuer 
  Date:   2013-03-05 (Tue, 05 Mar 2013)

  Changed paths:
M tests/forms_tests/tests/regressions.py
M tests/utils_tests/module_loading.py

  Log Message:
  ---
  Fixed minor warnings in tests.


  Commit: c31a9793c62457a68217326e9dfded8f0fb38d96
  
https://github.com/django/django/commit/c31a9793c62457a68217326e9dfded8f0fb38d96
  Author: Ramiro Morales 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M tests/forms_tests/tests/regressions.py
M tests/utils_tests/module_loading.py

  Log Message:
  ---
  Merge pull request #882 from loic/testfix

Fixed minor warnings in tests.


Compare: https://github.com/django/django/compare/876fc3912881...c31a9793c624

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

Re: [Django] #19543: SimpleLazyObject missing __repr__ proxy

[Django]

#19543: SimpleLazyObject missing __repr__ proxy
-+-
 Reporter:  spinus   |Owner:  fhahn
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  SimpleLazyObject | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"0ea5bf887fbdef7fe8d00162c9753565f5c0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0ea5bf887fbdef7fe8d00162c9753565f5c0"
 Fixed #19543 -- implemented SimpleLazyObject.__repr__

 Thanks to Florian Hahn for the patch
 }}}

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

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

[django/django] 0ea5bf: Fixed #19543 -- implemented SimpleLazyObject.__rep...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0ea5bf887fbdef7fe8d00162c9753565f5c0
  
https://github.com/django/django/commit/0ea5bf887fbdef7fe8d00162c9753565f5c0
  Author: Preston Holmes 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M django/utils/functional.py
M docs/releases/1.6.txt
M tests/utils_tests/simplelazyobject.py

  Log Message:
  ---
  Fixed #19543 -- implemented SimpleLazyObject.__repr__

Thanks to Florian Hahn for the patch


  Commit: 876fc3912881e15eda2b02c3b4933af313d0a498
  
https://github.com/django/django/commit/876fc3912881e15eda2b02c3b4933af313d0a498
  Author: Preston Holmes 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M django/utils/functional.py
M tests/utils_tests/simplelazyobject.py

  Log Message:
  ---
  PEP8 cleanup of functional.py


Compare: https://github.com/django/django/compare/c8e3a23d0f6d...876fc3912881

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

Re: [Django] #19541: Reversing URLs in response middleware or streamed responses won't use per-request urlconf

[Django]

#19541: Reversing URLs in response middleware or streamed responses won't use 
per-
request urlconf
---+-
 Reporter:  aaugustin  |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  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 loic84):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #19998: loaddata --ignorenonexistent not working for XML based fixtures

[Django]

#19998: loaddata --ignorenonexistent not working for XML based fixtures
-+-
 Reporter:  sigi |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  1.5
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by sigi):

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


Comment:

 https://github.com/chsigi/django/tree/ticket_19998

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

[Django] #19998: loaddata --ignorenonexistent not working for XML based fixtures

[Django]

#19998: loaddata --ignorenonexistent not working for XML based fixtures
--+--
 Reporter:  sigi  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (Serialization)  |Version:  1.5
 Severity:  Normal|   Keywords:  fixtures
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+--
 The new --ignorenonexistent commandline argument for loaddata is not
 working with XML based fixtures, because there is
 no code for it in django.core.serializers.xml_serializer.Deserializer.

 The patch adds code for ignoring nonexistent fields and a small test.

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

Re: [Django] #19995: [Django Testing Framework] Client.get() and UnicodeEncodeError

[Django]

#19995: [Django Testing Framework] Client.get() and UnicodeEncodeError
-+-
 Reporter:  david.delassus@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  test client unicode  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by claudep):

 Unfortunately, there is not enough information in the report to really
 tell what is happening. You should place a breakpoint at line 76 of
 encoding.py, so as you can see what is exactly that `s` variable that
 produces the exception. We know at least that this is not a string at this
 point of the code.

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

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

Re: [Django] #19973: Management commands migration to argparse

[Django]

#19973: Management commands migration to argparse
-+-
 Reporter:  jose |Owner:  jose
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  optparse, argparse,  |  Patch needs improvement:  0
  basecommand|UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by carljm):

 We'll need to provide a deprecation path and migration strategy for
 authors of custom management commands, since optparse is exposed directly
 to them via the definition of additional options for a custom command.

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

Re: [Django] #19997: Custom EMPTY_VALUES for form fields.

[Django]

#19997: Custom EMPTY_VALUES for form fields.
--+
 Reporter:  loic84|Owner:  loic84
 Type:  Cleanup/optimization  |   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 claudep):

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


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

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

Re: [Django] #19946: If DEBUG mode is False and ALLOWED_HOSTS is empty you should get a console warning

[Django]

#19946: If DEBUG mode is False and ALLOWED_HOSTS is empty you should get a 
console
warning
---+-
 Reporter:  pydanny|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:  duplicate
 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 carljm):

 I think that's a reasonable suggestion, though there are some open
 questions, like what sort of warning -- logging? warnings.warn? -- and
 when it should be raised -- once at startup? whenever request.get_host()
 is called?

 You should probably open a new ticket for it, since it is clearly
 different from what was originally proposed here (you are proposing a
 warning when DEBUG is True, not when it is False), and there's already
 enough confusion in this ticket.

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

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

[Django] #19997: Custom EMPTY_VALUES for form fields.

[Django]

#19997: Custom EMPTY_VALUES for form fields.
--+
 Reporter:  loic84|  Owner:  loic84
 Type:  Cleanup/optimization  | Status:  new
Component:  Forms |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Form fields should be able to decide for themselves what value they
 consider empty rather than through the catch-all
 `validators.EMPTY_VALUES`.

 An example of this would be a `JSONField` that considers an empty `dict` a
 valid non-empty value.

 Model validation had the same issue, and it became problematic when the
 BinaryField was introduced, this has been addressed in #19989. Form fields
 would benefit from the same fix.

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

Re: [Django] #19996: Django-mssql link wrong in docs

[Django]

#19996: Django-mssql link wrong in docs
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"c8e3a23d0f6d6683c7d5d4f4107b0c716b879cf0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c8e3a23d0f6d6683c7d5d4f4107b0c716b879cf0"
 Merge pull request #884 from manfre/patch-1

 Fixed #19996 - Updated link to django-mssql project in docs.
 }}}

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

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

[django/django] bb998c: Update link to django-mssql project

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bb998c9fecb31db875418efb0b46a20bfa2ddea7
  
https://github.com/django/django/commit/bb998c9fecb31db875418efb0b46a20bfa2ddea7
  Author: Michael Manfre 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M docs/topics/install.txt

  Log Message:
  ---
  Update link to django-mssql project


  Commit: c8e3a23d0f6d6683c7d5d4f4107b0c716b879cf0
  
https://github.com/django/django/commit/c8e3a23d0f6d6683c7d5d4f4107b0c716b879cf0
  Author: Aymeric Augustin 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M docs/topics/install.txt

  Log Message:
  ---
  Merge pull request #884 from manfre/patch-1

Fixed #19996 - Updated link to django-mssql project in docs.


Compare: https://github.com/django/django/compare/2add24cc2c60...c8e3a23d0f6d

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

Re: [Django] #19996: Django-mssql link wrong in docs

[Django]

#19996: Django-mssql link wrong in docs
-+-
 Reporter:  manfre   |Owner:  manfre
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by manfre):

 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Documentation


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

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

Re: [Django] #19996: Django-mssql link wrong in docs

[Django]

#19996: Django-mssql link wrong in docs
---+--
 Reporter:  manfre |Owner:  manfre
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by manfre):

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


Comment:

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

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

[Django] #19996: Django-mssql link wrong in docs

[Django]

#19996: Django-mssql link wrong in docs
---+
 Reporter:  manfre |  Owner:  manfre
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Docs point to old Google code repository. Project has since moved to
 bitbucket.

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

Re: [Django] #19995: [Django Testing Framework] Client.get() and UnicodeEncodeError

[Django]

#19995: [Django Testing Framework] Client.get() and UnicodeEncodeError
-+-
 Reporter:  david.delassus@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  test client unicode  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by anonymous):

 * 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

[Django]

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by claudep):

 If we don't find any better solution, I think we'll fallback to
 `force_text(query, errors='replace')`. It's still better than crashing.

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

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

[Django]

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:4 marcel.ryser.ch@…]:
 > What about binary values who could be represented as UTF-8 characters
 but aren't characters? Then you have a wrong representation of a binary
 value, which are not characters, this could lead to confusion.

 You are right, but I didn't find any better solution for now.

 > Django generates the queries (prepared-statements?) by using the field
 datatype defined in the model, I guess. Why doesn't the logging starts
 there and not when it is all over? There you could easily decide which
 mode should be used to represent the value of a field in the log. Binary
 fields should really be represented as they are: binary and not converted
 to characters, because we don't know (on django side) what kind of binary
 data we are dealing with.

 Django is separately passing the query with placeholders and parameters to
 the database backend, it does not generate the full query itself. That's
 why Django uses the `cursor.last_executed_query` trick to retrieve the
 real query. But feel free to experiment and propose a better patch. I'm
 out of ideas currently :-(

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

[Django] #19995: [Django Testing Framework] Client.get() and UnicodeEncodeError

[Django]

#19995: [Django Testing Framework] Client.get() and UnicodeEncodeError
---+-
 Reporter:  david.delassus@…   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.4
 Severity:  Normal |   Keywords:  test client unicode
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 Hi,

 I'm use the Client API to test my views, and here is one of my test :

 {{{#!python
 def test_04_edit_page(self):
 # Verify the page doesn't exist
 response = self.client.get('/wiki/wiki-test-hehe/Page')

 self.assertEqual(response.status_code, 302) # if the page is not
 found, the wiki redirect the user to an edit page

 # Check GET on edit page
 response = self.client.get('/wiki/wiki-test-hehe/Page/edit')

 self.assertEqual(response.status_code, 200)

 # Now send data
 response = self.client.post('/wiki/wiki-test-hehe/Page/edit', {
 'path': 'Page',
 'content': u'Test héhé',
 'comment': u'Commentaire de test héhé',
 })

 self.assertEqual(response.status_code, 302) # after an edit, the
 wiki redirect the user to the page

 # And now, check that the new page exists
 response = self.client.get('/wiki/wiki-test-hehe/Page')

 self.assertEqual(response.status_code, 200)
 }}}

 The error raise at the last get request :

 {{{
 UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in
 position 1: ordinal not in range(128)
 }}}

 Here is the full traceback :

 {{{

 Traceback (most recent call last):
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/pompadour_wiki/apps/wiki/tests.py", line 98, in
 test_05_remove_page
 self.test_04_edit_page()
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/pompadour_wiki/apps/wiki/tests.py", line 93, in
 test_04_edit_page
 response = self.client.get('/wiki/wiki-test-hehe/Page')
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/test/client.py", line 439, in get
 response = super(Client, self).get(path, data=data, **extra)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/test/client.py", line 244, in get
 return self.request(**r)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/core/handlers/base.py", line 111, in get_response
 response = callback(request, *callback_args, **callback_kwargs)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/contrib/auth/decorators.py", line 20, in _wrapped_view
 return view_func(request, *args, **kwargs)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/pompadour_wiki/apps/utils/decorators.py", line 57, in
 wrapper
 return render_to_response(template, output,
 context_instance=RequestContext(request), mimetype=mimetype)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/shortcuts/__init__.py", line 20, in render_to_response
 return HttpResponse(loader.render_to_string(*args, **kwargs),
 **httpresponse_kwargs)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/template/loader.py", line 176, in render_to_string
 return t.render(context_instance)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/template/base.py", line 140, in render
 return self._render(context)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/test/utils.py", line 62, in instrumented_test_render
 return self.nodelist.render(context)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/template/base.py", line 823, in render
 bit = self.render_node(node, context)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/template/debug.py", line 74, in render_node
 return node.render(context)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/template/loader_tags.py", line 123, in render
 return compiled_parent._render(context)
   File "/home/david/Documents/projects/pompadour-
 wiki/pompadour_wiki/.venv/local/lib/python2.7/site-
 packages/django/test/utils.py", line 62, in instrumented_test_render
 return self

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

[Django]

#19373: Windows file locking requires pywin32
-+-
 Reporter:  techtonik|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  File |   Resolution:
  uploads/storage| Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by manfre):

 I'm not in a position to make a decision, but I'll share some of my
 insights.

 I've needed PyWin32 installed on every windows system because of django-
 mssql, the file locking support was secondary. The installation is easy
 and the project doesn't release new version very often.

 The only real downside to PyWin32 that I've encountered is that it doesn't
 play well with virtualenv because `--system-site-packages` is required.
 This requirement is not exclusive to PyWin32 and almost every binary
 package that drops DLLs needs to be installed globally and use `--system-
 site-packages` in virtualenvs. This can become a problem with maintaining
 an automated build system and for some deployment scenarios.

 If requiring `--system-site-packages` is an acceptable, then documenting
 PyWin32 would be the easiest path forward and I'd be happy to submit a
 patch. If Django doesn't want to force `--system-site-packages`, then
 definitely look for another option that only addresses the file locking
 issue, instead of all the other stuff that is rolled in to PyWin32.

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

Re: [Django] #17615: Unique field validation with multi-table inheritance

[Django]

#17615: Unique field validation with multi-table inheritance
-+-
 Reporter:  ungenio  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ramiro):

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


Comment:

 Please open an new ticket with a full and understandable description of
 what you are reporting. 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19989: Validating BinaryField against validators.EMPTY_VALUES raises UnicodeWarning

[Django]

#19989: Validating BinaryField against validators.EMPTY_VALUES raises
UnicodeWarning
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by Claude Paroz ):

 In [changeset:"2add24cc2c605a51695258d45d6d1b61556dec9f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2add24cc2c605a51695258d45d6d1b61556dec9f"
 One more EMPTY_VALUES replacement following 22be90dd17

 Thanks Loic Bistuer for catching this omission. Refs #19989.
 }}}

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

[django/django] 2add24: One more EMPTY_VALUES replacement following 22be90...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2add24cc2c605a51695258d45d6d1b61556dec9f
  
https://github.com/django/django/commit/2add24cc2c605a51695258d45d6d1b61556dec9f
  Author: Claude Paroz 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M django/db/models/base.py

  Log Message:
  ---
  One more EMPTY_VALUES replacement following 22be90dd17

Thanks Loic Bistuer for catching this omission. Refs #19989.



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

Re: [Django] #17615: Unique field validation with multi-table inheritance

[Django]

#17615: Unique field validation with multi-table inheritance
-+-
 Reporter:  ungenio  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by anonymous):

 * status:  closed => new
 * needs_better_patch:  0 => 1
 * version:  1.3 => 1.5
 * resolution:  fixed =>


Comment:

 Got an error:
 AttributeError: 'NoneType' object has no attribute 'attname'

 Because a model can be 'abstract = True' doesn't have a pk, but a form
 (also 'abstract = True') can be used for validation 'is_valid()'. I use it
 for Ajax validation of a single item in a form with multiple items.

 row 823-825:
 #model_class_pk = self._get_pk_val(model_class._meta)
 #if not self._state.adding and model_class_pk is not None:
 #qs = qs.exclude(pk=model_class_pk)

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

Re: [Django] #16205: Beginners install guide for Windows

[Django]

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

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


Comment:

 I'll work on the documentation. My job wants me to update our internal
 wiki's "Setting up a developer laptop" page, which has a large section on
 getting up and running with 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b3aa85: Used more precise test assertions.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b3aa853ec536926c4fd2739c8d39091fe48e51c9
  
https://github.com/django/django/commit/b3aa853ec536926c4fd2739c8d39091fe48e51c9
  Author: Aymeric Augustin 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M tests/select_for_update/tests.py

  Log Message:
  ---
  Used more precise test assertions.



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

Re: [Django] #19822: USERNAME_FIELD should be validated as unique=True

[Django]

#19822: USERNAME_FIELD should be validated as unique=True
--+
 Reporter:  russellm  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  1.5-rc-1
 Severity:  Release blocker   |   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 anonymous):

 > [...] Of course, this points at a design problem on their end; [...]

 I must disagree on that (and yes, I got the surprise since everything was
 working fine with the release candidate). I actually ran into a scenario
 where the username alone should not be unique. I am currently implementing
 a system where a reseller can have labels and labels have users. In this
 specific case, a user must be unique for a label (which is basically a
 company), but not for a reseller. Users don't have to know that 2 labels
 are owned by a single reseller. In short; our unique constraint is based
 on the label and the USERNAME_FIELD.

 I can imagine there are more valid cases where this validation check would
 be blocking. Wouldn't it be better to make this validation option optional
 by i.e. a config setting?

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

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

[Django]

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (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 marcel.ryser.ch@…):

 What about binary values who could be represented as UTF-8 characters but
 aren't characters? Then you have a wrong representation of a binary value,
 which are not characters, this could lead to confusion.

 Django generates the queries (prepared-statements?) by using the field
 datatype defined in the model, I guess. Why doesn't the logging starts
 there and not when it is all over? There you could easily decide which
 mode should be used to represent the value of a field in the log. Binary
 fields should really be represented as they are: binary and not converted
 to characters, because we don't know (on django side) what kind of binary
 data we are dealing 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.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Django]

#16986: Model.clean cannot report errors on individual fields
-+
 Reporter:  davidfstr|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:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by jpichon):

 * cc: julie@… (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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19994: Typo on deployment docs

[Django]

#19994: Typo on deployment docs
---+
 Reporter:  akshar |  Owner:  nobody
 Type:  Bug| Status:  closed
Component:  Documentation  |Version:  1.5
 Severity:  Normal | Resolution:  fixed
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"d1a5fe07ed96794864d9aa69502ed056bb7a561b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d1a5fe07ed96794864d9aa69502ed056bb7a561b"
 Fixed #19994 -- Typo.

 Thanks akshar for the report.
 }}}

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

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

[django/django] d1a5fe: Fixed #19994 -- Typo.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d1a5fe07ed96794864d9aa69502ed056bb7a561b
  
https://github.com/django/django/commit/d1a5fe07ed96794864d9aa69502ed056bb7a561b
  Author: Aymeric Augustin 
  Date:   2013-03-06 (Wed, 06 Mar 2013)

  Changed paths:
M docs/howto/deployment/wsgi/index.txt

  Log Message:
  ---
  Fixed #19994 -- Typo.

Thanks akshar for the report.



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

[Django] #19994: Typo on deployment docs

[Django]

#19994: Typo on deployment docs
---+
 Reporter:  akshar |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/

 Search for 'environnemnt'. This is a typo and should be changed to
 'environment'.

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

Re: [Django] #10327: Pass document.domain to popup windows in admin

[Django]

#10327: Pass document.domain to popup windows in admin
---+
 Reporter:  jcassee|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by gvangool):

 This could be solved now with the changes from #19773.

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

Re: [Django] #3108: Add Form.as_dl() to newforms

[Django]

#3108: Add Form.as_dl() to newforms
-+--
 Reporter:  adrian   |Owner:  adrian
 Type:  enhancement  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by anonymous):

 I'm new to Django, this is one of the things I want to do. Formatting a
 form using dl is the way to go. See the Twitter Bootstrap for example.

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