Re: [Django] #24444: Update contrib.admin visual theme to use django-flat-theme

[Django]

#2: Update contrib.admin visual theme to use django-flat-theme
-+-
 Reporter:  elky |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  django-admin,| Triage Stage:  Accepted
  redesign   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #25193: MultiWidget is_hidden is True if subwidgets are dynamically added during its render function

[Django]

#25193: MultiWidget is_hidden is True if subwidgets are dynamically added during
its render function
---+--
 Reporter:  meredithroman  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.7
 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 timgraham):

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


Comment:

 I could imagine not every user would want the behavior you desire, and it
 seems a bit of an edge case. Therefore, it might be better to continue
 using your own subclass.

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

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

Re: [Django] #25193: MultiWidget is_hidden is True if subwidgets are dynamically added during its render function

[Django]

#25193: MultiWidget is_hidden is True if subwidgets are dynamically added during
its render function
---+
 Reporter:  meredithroman  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Forms  |Version:  1.7
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by meredithroman):

 * Attachment "MultiWidget_is_hidden_patch.diff" 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/071.1c4bf09f49dc5eb1b0f9cf5d710db1b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25193: MultiWidget is_hidden is True if subwidgets are dynamically added during its render function

[Django]

#25193: MultiWidget is_hidden is True if subwidgets are dynamically added during
its render function
---+
 Reporter:  meredithroman  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Forms  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 I have a custom MultiWidget that dynamically adds subwidgets during its
 render function. I use this widget as part of a form builder that lets a
 user generate a checklist or radio field with as many options as they
 need. Because I don't know how many subwidgets the user will need, I am
 unable to set the subwidgets during form initializaiton.

 This is how I add subwidgets during the MultiWidget's render function:

 {{{
 def render(self, name, value, attrs=None):
   if not isinstance(value, list):
 value = self.decompress(value)
   self.widgets = []
   for option in value:
 self.widgets.append(forms.TextInput())
   return super(OptionsWidget, self).render(name, value, attrs)
 }}}

 This is the way that the MultiWidget is_hidden property is currently set:

 {{{
 @property
 def is_hidden(self):
   return all(w.is_hidden for w in self.widgets)
 }}}

 Because I do not have any subwidgets assigned to my widget at form
 initilaization, and because all() returns True on an empty iterable,
 is_hidden was set to True for my widget.

 I'm currently using this overwritten version of is_hidden for the widget:

 {{{
 @property
 def is_hidden(self):
   return False if self.widgets == [] else all(w.is_hidden for w in
 self.widgets)
 }}}

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

Re: [Django] #25193: MultiWidget is_hidden is True if subwidgets are dynamically added during its render function

[Django]

#25193: MultiWidget is_hidden is True if subwidgets are dynamically added during
its render function
---+
 Reporter:  meredithroman  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Forms  |Version:  1.7
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
UI/UX:  0  |
---+
Changes (by meredithroman):

 * Attachment "MultiWidget_is_hidden_patch.diff" 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/071.c3cac91cc579828d693c45be013fd2a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25144: No way to create tables for apps without migrations

[Django]

#25144: No way to create tables for apps without migrations
-+-
 Reporter:  MarkusH  |Owner:
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.9  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * keywords:   => 1.9
 * type:  Bug => New feature
 * severity:  Release blocker => Normal
 * 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/065.7944f15b63910d735326adaaa472a5ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25145: Models of apps w/o migrations don't have relational fields to other apps w/o migrations when applying migrations

[Django]

#25145: Models of apps w/o migrations don't have relational fields to other apps
w/o migrations when applying migrations
+--
 Reporter:  MarkusH |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timgraham):

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


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

Re: [Django] #25069: Make _unregister_lookup be public API

[Django]

#25069: Make _unregister_lookup be public API
-+-
 Reporter:  coldmind |Owner:  coldmind
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 timgraham):

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


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

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

Re: [Django] #25189: DateTimeField cannot validate isoformat() datetime strings.

[Django]

#25189: DateTimeField cannot validate isoformat() datetime strings.
-+
 Reporter:  kezabelle|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  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 timgraham):

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


Comment:

 I can't immediately think of anything that could go wrong.

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

Re: [Django] #25192: Can't Squash Migration that uses migrations.RunPython.noop in Python2

[Django]

#25192: Can't Squash Migration that uses migrations.RunPython.noop in Python2
+
 Reporter:  jpulec  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 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 timgraham):

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


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

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

Re: [Django] #25163: Add a hint to the admin login page when a user is redirected there due to lack of permissions

[Django]

#25163: Add a hint to the admin login page when a user is redirected there due 
to
lack of permissions
-+-
 Reporter:  adelton  |Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"635ffc3c37d58eb96ae17d5389dd50bf635413c6" 635ffc3c]:
 {{{
 #!CommitTicketReference repository=""
 revision="635ffc3c37d58eb96ae17d5389dd50bf635413c6"
 Fixed #25163 -- Added hint for non-staff users to admin login page.
 }}}

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

Re: [Django] #25163: Add a hint to the admin login page when a user is redirected there due to lack of permissions (was: When a user doesn't have permission to an admin page, raise 404 instead of redi

[Django]

#25163: Add a hint to the admin login page when a user is redirected there due 
to
lack of permissions
--+
 Reporter:  adelton   |Owner:
 Type:  Cleanup/optimization  |   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:  0
Easy pickings:  0 |UI/UX:  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.ec7940898962b2923488dc1f5f399e15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24917: Allow admindocs to show more than just methods that can be called from templates

[Django]

#24917: Allow admindocs to show more than just methods that can be called from
templates
---+
 Reporter:  zanderle   |Owner:  zanderle
 Type:  New feature|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admindocs  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * 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/066.3bb2cc3696dabf2c54503acf6d199c67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25192: Can't Squash Migration that uses migrations.RunPython.noop in Python2

[Django]

#25192: Can't Squash Migration that uses migrations.RunPython.noop in Python2
+
 Reporter:  jpulec  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 When trying to squash a set of migrations, if one of them uses
 migrations.RunPython.noop for a backwards or forward operation, a
 ValueError is raised due to an attempt to serialize an unbound method. Not
 sure if there should be a special check for that operation when attempting
 to run squashmigrations with Python2.

 Traceback:
 {{{
 Traceback (most recent call last):
   File "manage.py", line 17, in 
 execute_from_command_line(sys.argv)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 338, in
 execute_from_command_line
 utility.execute()
   File "/var/venv/local/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 393, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/core/management/base.py", line 444, in execute
 output = self.handle(*args, **options)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/core/management/commands/squashmigrations.py", line 141,
 in handle
 fh.write(writer.as_string())
   File "/var/venv/local/lib/python2.7/site-
 packages/django/db/migrations/writer.py", line 166, in as_string
 operation_string, operation_imports =
 OperationWriter(operation).serialize()
   File "/var/venv/local/lib/python2.7/site-
 packages/django/db/migrations/writer.py", line 124, in serialize
 _write(arg_name, arg_value)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/db/migrations/writer.py", line 87, in _write
 arg_string, arg_imports = MigrationWriter.serialize(_arg_value)
   File "/var/venv/local/lib/python2.7/site-
 packages/django/db/migrations/writer.py", line 435, in serialize
 % (value.__name__, module_name, get_docs_version()))
 ValueError: Could not find function noop in
 django.db.migrations.operations.special.
 Please note that due to Python 2 limitations, you cannot serialize unbound
 method functions (e.g. a method declared and used in the same class body).
 Please move the function into the main module body to use migrations.
 }}}

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

Re: [Django] #24305: Allow to override abstract model fields

[Django]

#24305: Allow to override abstract model fields
-+-
 Reporter:  knbk |Owner:  ar45
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

 * needs_better_patch:  1 => 0


Comment:

 There is a commit here with an alternate approach:
 https://github.com/knbk/django/commit/7ac5b58587ea2a153766d1601965734731609cdf
 (having difficulty finding what branch it's part of so I could create a
 pull request).

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

Re: [Django] #24305: Allow to override abstract model fields

[Django]

#24305: Allow to override abstract model fields
-+-
 Reporter:  knbk |Owner:  ar45
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 ar45):

 * status:  new => assigned
 * owner:  knbk => ar45


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

Re: [Django] #25191: Better error output for assertXMLEqual

[Django]

#25191: Better error output for assertXMLEqual
--+
 Reporter:  shelldweller  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  1 => 0
 * needs_docs:   => 0
 * type:  New feature => Cleanup/optimization
 * 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/070.7e5fd4e5f85db55faaea71e339c36736%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25188: inconsistent escaping in assertRaisesMessage test output

[Django]

#25188: inconsistent escaping in assertRaisesMessage test output
-+
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertRaisesMessage  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * Attachment "25188.diff" 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/067.d05d4c05dfd08e0c6a682d27b4c0151e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25188: inconsistent escaping in assertRaisesMessage test output

[Django]

#25188: inconsistent escaping in assertRaisesMessage test output
-+
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertRaisesMessage  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

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


Comment:

 The attached patch passes the test suite, however, it doesn't fail
 correctly when `assertRaisesMessage()` is used in a non-context manager
 context. If this issue can be solved, I don't see a reason not to use that
 approach.

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

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

Re: [Django] #25163: When a user doesn't have permission to an admin page, raise 404 instead of redirecting to login

[Django]

#25163: When a user doesn't have permission to an admin page, raise 404 instead 
of
redirecting to login
--+
 Reporter:  adelton   |Owner:
 Type:  Cleanup/optimization  |   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:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by lvisintini):

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


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

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

[Django] #25191: Better error output for assertXMLEqual

[Django]

#25191: Better error output for assertXMLEqual
---+
 Reporter:  shelldweller   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Testing framework  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 It is difficult to understand test failures when comparing XML files.
 Currently error message shows the beginning of each XML string and output
 looks something like this:

 {{{
 AssertionError: '\n
 Blue
 sky != 
 Blue
 dye
   
   Blue
 - sky
 + dye
 }}}

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

Re: [Django] #21961: ForeignKey.on_delete supports database-level cascading options

[Django]

#21961: ForeignKey.on_delete supports database-level cascading options
-+-
 Reporter:  Xof  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 carljm):

 I think we should consider introducing this feature as a totally separate
 kwarg (`on_delete_db`) rather than conflating it with the existing Python-
 level `on_delete`. The various edge cases and implicit fallbacks in the
 existing proposal worry me, and I think it would be better to be more
 explicit and clear about what is happening on the database level vs the
 Python level.

 Right now the contract of `on_delete` is very simple: it takes a Python
 callable which will be called when a delete cascades. There is nothing at
 all special about the built-in callables, they are just conveniences for
 common cases. The current API proposal complicates that contract
 dramatically: now you have an `on_delete` kwarg which sometimes accepts
 Python callables but can also accept magical constants which do something
 entirely different (and also have an implicit fallback relationship with
 one of the built-in callables).

 So under my proposal, if you want database-level cascade, you would
 specify `on_delete=models.DO_NOTHING, on_delete_db=models.DB_CASCADE` or
 similar. Sure this is a bit more verbose, but I think that's worth it for
 the gains in clarity and simplicity.

 For similar reasons, I feel pretty strongly that we should NOT
 automatically fallback from db-cascade to non-db-cascade depending on the
 backend capabilities. It introduces too many differences in behavior
 depending on db backend. Trying to claim to provide cross-db portability
 when we can't really do so consistently is worse than simply not claiming
 to provide it at all. DB-level cascade (like many other "advanced" db-
 level features) is something you should only take advantage of when you
 know your code will be running on a database that supports it, full stop.
 Use of `on_delete_db` on a backend that can't support it should be an
 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/061.c24df0a2a674b2edbe08e6ea27d7a920%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25183: Non-deterministic GeoIP test: GeoIPTest.test03_country

[Django]

#25183: Non-deterministic GeoIP test: GeoIPTest.test03_country
---+--
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  GIS|  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 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 timgraham):

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


Comment:

 This hasn't reoccurred.

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

Re: [Django] #25190: Deprecate callable_obj parameter to assertRaisesMessage

[Django]

#25190: Deprecate callable_obj parameter to assertRaisesMessage
-+-
 Reporter:  timgraham|Owner:  timgraham
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Testing framework|  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 timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5065 PR]

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

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

[Django] #25190: Deprecate callable_obj parameter to assertRaisesMessage

[Django]

#25190: Deprecate callable_obj parameter to assertRaisesMessage
-+-
   Reporter:  timgraham  |  Owner:  timgraham
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Testing|Version:  master
  framework  |
   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  |
-+-
 It was deprecated in Python in
 https://hg.python.org/cpython/rev/ac13f0390866 and those warnings were
 fixed in c2bc1cefdcbbf074408f4a4cace88b315cf9d652. Then I realized
 `callable_obj` was a documented parameter so I added backwards
 compatibility in e89c3a46035e9fe17c373a6c9cd63b9fd631d596 and updated the
 docs in a0175724b086127a4e13612042961d3ba88d6bd9.

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

Re: [Django] #25185: Support for serialization of `functools.partial` objects in migrations

[Django]

#25185: Support for serialization of `functools.partial` objects in migrations
-+-
 Reporter:  pipermerriam |Owner:
 |  pipermerriam
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"537818af8783a4f9f239ed6277b1f810c1666839" 537818a]:
 {{{
 #!CommitTicketReference repository=""
 revision="537818af8783a4f9f239ed6277b1f810c1666839"
 Fixed #25185 -- Added support for functools.partial serialization in
 migrations
 }}}

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

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

Re: [Django] #25188: inconsistent escaping in assertRaisesMessage test output

[Django]

#25188: inconsistent escaping in assertRaisesMessage test output
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertRaisesMessage  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cjerdonek):

 Since only a plain string comparison is needed, is there a reason the
 method needs to be using `assertRaisesRegex`?  For example, couldn't the
 implementation bypass `assertRaisesRegex` and go something like this?
 (This is just an idea so shouldn't be taken as is.)

 {{{#!python
 @contextmanager
 def assertRaisesMessage(self, expected_exception, expected_message):
 with self.assertRaises(expected_exception) as cm:
 yield
 err = cm.exception
 self.assertEqual(str(err), expected_message)
 }}}

 An implementation like this would have the further advantage that in the
 case of a string mismatch the test output would show ''where'' the strings
 differ by using unittest's `assertEqual`, which is better equipped for
 this and has this added functionality.

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

Re: [Django] #10933: Avoid " TypeError: Cannot convert Decimal("0.0000") to Decimal " when the decimal module has been reloaded

[Django]

#10933: Avoid " TypeError: Cannot convert Decimal("0.") to Decimal  " when 
the
decimal module has been reloaded
-+-
 Reporter:  gagravarr|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  dceu2011 | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 As noted in comment 25, I think this is probably related to incorrect
 server configuration. If it's still an issue, we need much more specific
 information about how to reproduce it.

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

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

Re: [Django] #11329: get_count generates incorrect SQL for query sets with extra 'select' and 'where'

[Django]

#11329: get_count generates incorrect SQL for query sets with extra 'select' and
'where'
-+-
 Reporter:  bogklug  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  sql, extra select,   | Triage Stage:  Accepted
  extra where, get_count |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I agree that the `aggregate()` and `annotate()` methods should be used
 these days, so I don't see much value in fixing this 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/065.11d92b59449b8f69a9d637b60a977d1f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #11523: ORM/MySQL backend doesn't set pk when Warning exception is raised

[Django]

#11523: ORM/MySQL backend doesn't set pk when Warning exception is raised
-+-
 Reporter:  TomaszZielinski  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 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 timgraham):

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


Comment:

 As of #23871, Django no longer promotes warnings to exceptions, so I think
 this issue is obsolete.

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

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

[Django]

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  t2y  |Owner:
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 #20301 is a duplicate.

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

Re: [Django] #20301: Unique field validation with multiple DB connections.

[Django]

#20301: Unique field validation with multiple DB connections.
-+-
 Reporter:  SardarNL |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #15130

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

Re: [Django] #21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to the DB backend

[Django]

#21257: ForeignKey on_delete functionality should traverse (cascade, ha ha) to 
the
DB backend
-+-
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #21961

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

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

[Django]

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  megaumi
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5045 PR]

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

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

Re: [Django] #25188: inconsistent escaping in assertRaisesMessage test output

[Django]

#25188: inconsistent escaping in assertRaisesMessage test output
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  assertRaisesMessage  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I don't see an easy way to address this issue. The expected message is
 passed through `re.escape(expected_message)` before it's passed to
 `six.assertRaisesRegex`. It seems we would have to reimplement large parts
 of `six.assertRaisesRegex`  in order to unescape the pattern in the error
 message.

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

Re: [Django] #24917: Allow admindocs to show more than just methods that can be called from templates

[Django]

#24917: Allow admindocs to show more than just methods that can be called from
templates
---+
 Reporter:  zanderle   |Owner:  zanderle
 Type:  New feature|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admindocs  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by zanderle):

 * needs_tests:  1 => 0


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

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

Re: [Django] #24917: Allow admindocs to show more than just methods that can be called from templates

[Django]

#24917: Allow admindocs to show more than just methods that can be called from
templates
---+
 Reporter:  zanderle   |Owner:  zanderle
 Type:  New feature|   Status:  assigned
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admindocs  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by zanderle):

 * needs_better_patch:  1 => 0
 * 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/066.48bd2d79b600582a659bf51c96748338%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25189: DateTimeField cannot validate isoformat() datetime strings.

[Django]

#25189: DateTimeField cannot validate isoformat() datetime strings.
-+
 Reporter:  kezabelle|  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
-+
 given:
 {{{
 from datetime import datetime
 dt = datetime.now()
 formatted = dt.isoformat()
 f = forms.DateTimeField()
 f.clean(value=formatted)
 }}}
 a ValidationError will be raised because the default `sep` for isoformat
 is `T` and that format isn't in the default `DATETIME_INPUT_FORMATS`.

 I came across this while looking to serialize a `form.cleaned_data`
 dictionary to JSON using the internal `DjangoJSONEncoder` - to work around
 it in what is ostensibly a re-usable app, I had to subclass the
 `DjangoJSONEncoder` to handle datetimes before going to the `super()`

 I have a unit test and patch available, if 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/052.e2109038262772b76117053b4fbc7e30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.