Re: [Django] #23626: Change coding style for sql, params return lines

[Django]

#23626: Change coding style for sql, params return lines
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by AmiZya):

 * cc: amizya@… (added)


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

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

Re: [Django] #23558: document slugify limitations

[Django]

#23558: document slugify limitations
--+
 Reporter:  kmike |Owner:  dhoffman
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 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
--+
Changes (by dhoffman):

 * has_patch:  0 => 1


Comment:

 Pull request: https://github.com/django/django/pull/3349

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

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

Re: [Django] #23558: document slugify limitations

[Django]

#23558: document slugify limitations
--+
 Reporter:  kmike |Owner:  dhoffman
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by dhoffman):

 * status:  new => assigned
 * owner:  nobody => dhoffman


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

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

Re: [Django] #22608: migrations slow (due to double working?)

[Django]

#22608: migrations slow (due to double working?)
-+-
 Reporter:  davids   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-beta-2
 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 claudep):

 On my system, I realized that each migration added to the Django test
 suite adds up 3.5 sec. to the initial test database initialization (both
 with SQLite and PostgreSQL).

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

Re: [Django] #23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark

[Django]

#23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark
-+-
 Reporter:  contact@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  send_mail, smtp, | Triage Stage:  Ready for
  malformed, packet  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Apolloner ):

 In [changeset:"bc13a08f89b4a9b7980588b013f358b2721c42a6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bc13a08f89b4a9b7980588b013f358b2721c42a6"
 [1.7.x] Fixed #23063 -- Convert \n and \r to \r\n when using the SMTP
 backend as per RFC.

 Backport of 8d789449c7861b8cf8b10d244f26d9d354989aaf from master.
 }}}

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

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

Re: [Django] #23641: Apps.set_installed_apps causes signals registered with apps as senders not to be received

[Django]

#23641: Apps.set_installed_apps causes signals registered with apps as senders 
not
to be received
--+
 Reporter:  wrwrwr|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 I believe it was mostly a workaround for the pre-1.4 project layout that
 could result in duplicate imports.

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

Re: [Django] #23641: Apps.set_installed_apps causes signals registered with apps as senders not to be received

[Django]

#23641: Apps.set_installed_apps causes signals registered with apps as senders 
not
to be received
--+
 Reporter:  wrwrwr|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by loic):

 Somewhat transversal but do we still need `dispatch_uid` when registering
 signals in `AppConfig.ready()`?

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

Re: [Django] #23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark

[Django]

#23063: send email 1.6.5 OK, 1.7c1 malformed packet in wireshark
-+-
 Reporter:  contact@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  send_mail, smtp, | Triage Stage:  Ready for
  malformed, packet  |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #23638: Django raises exceptions on unicode in cookies/headers

[Django]

#23638: Django raises exceptions on unicode in cookies/headers
---+
 Reporter:  defcube|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.7
 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):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #23638: Django raises exceptions on unicode in cookies/headers

[Django]

#23638: Django raises exceptions on unicode in cookies/headers
---+
 Reporter:  defcube|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.7
 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 claudep):

 * needs_better_patch:   => 0
 * component:  Uncategorized => HTTP handling
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Your cookie content seems really garbage, it's unlikely that Django
 produced it.

 Anyway, Django should not crash. I'll suggest a patch to fix this.

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

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

Re: [Django] #22977: No validation error when ForeignKey related_name clashes with manager name.

[Django]

#22977: No validation error when ForeignKey related_name clashes with manager 
name.
--+
 Reporter:  russellm  |Owner:  kswiat
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.6
 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 kswiat):

 * status:  new => assigned
 * owner:  nobody => kswiat


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

Re: [Django] #21113: django_admin_log table stores messages in different languages depending on which language was active while editing.

[Django]

#21113: django_admin_log table stores messages in different languages depending 
on
which language was active while editing.
-+
 Reporter:  dimyur27@…   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin logs i18n  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 Replying to [comment:9 jooyous]:
 (...)
 > If having history messages displayed in different languages is a
 priority, I would recommend restructuring the logging functionality
 entirely, and have the messages be saved in an unambiguously delimited
 format (yaml? json? something!) so that they can be formed into
 translatable sentences after they are extracted from the database. I would
 be willing to work on this if an issue gets made!

 Yes, I think that this would be the right 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/076.8a0a6223ce933065c011aba9026d7d50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23642: LocMemCache.incr is not thread safe

[Django]

#23642: LocMemCache.incr is not thread safe
-+
 Reporter:  tchaumeny|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Loic Bistuer ):

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


Comment:

 In [changeset:"6448dd833524ac3fc503506b624841c9d642de8a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6448dd833524ac3fc503506b624841c9d642de8a"
 Fixed #23642 -- Made LocMemCache.incr() thread-safe as documented
 }}}

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

Re: [Django] #23640: StaticLiveServerTestCase does not properly respect data migrations

[Django]

#23640: StaticLiveServerTestCase does not properly respect data migrations
-+-
 Reporter:  eldamir  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  data migration,  | Triage Stage:  Accepted
  functional tests   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 I can reproduce the reported issue and it does appear to be a bug indeed.

 Thanks.

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

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

Re: [Django] #23643: Have debug page show "During handling of this exception, another exception occurred.."

[Django]

#23643: Have debug page show "During handling of this exception, another 
exception
occurred.."
-+
 Reporter:  cool-RR  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Python 3 |  Version:  1.7
 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 bmispelon):

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


Comment:

 I like this idea.

 I find that it really helps with debugging (especially when Django has a
 bad habit of masking exceptions).

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

[Django] #23643: Have debug page show "During handling of this exception, another exception occurred.."

[Django]

#23643: Have debug page show "During handling of this exception, another 
exception
occurred.."
-+
 Reporter:  cool-RR  |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Python 3 |Version:  1.7
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Python 3 has this thing where exceptions have optional `__cause__` and
 `__context__`, which is useful when an exception causes another exception.
 When you get a Python 3 traceback, you see tracebacks for all the
 exceptions in the tree. Currently it seems that the Django debug page
 ignores this information. It would be nice if it would display a separate
 traceback for each such exception.

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

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

Re: [Django] #23641: Apps.set_installed_apps causes signals registered with apps as senders not to be received

[Django]

#23641: Apps.set_installed_apps causes signals registered with apps as senders 
not
to be received
--+
 Reporter:  wrwrwr|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by wrwrwr):

 Thanks for the quick response. Good news is that scanning the source for
 ".connect(", "@receiver(" and "sender=" didn't reveal any other cases of
 using `AppConfig` as a sender, so for consistency I've only also moved
 `post_migrate` registration for `auth` and `contenttypes` to `ready` (both
 need to be called for every migration, not just their app migration, so
 don't specify any sender to `connect`).

 On the other hand, theoretically the issue can be triggered without
 directly using `set_installed_apps`; the following test fails as is, but
 succeeds if you comment out the `modify_settings` decorator:
 {{{#!python
 from django.apps import apps
 from django.dispatch import Signal, receiver
 from django.test import TestCase, modify_settings

 some_signal = Signal()
 app_label = 'auth'  # Something installed.
 handler_called = False

 @receiver(some_signal, sender=apps.get_app_config(app_label))
 def signal_handler(sender, **kwargs):
 global handler_called
 handler_called = True

 @modify_settings(INSTALLED_APPS={})
 class Test(TestCase):
 def test_handler(self):
 some_signal.send(apps.get_app_config(app_label))
 self.assertTrue(handler_called)
 }}}

 This is probably an edge case no one will ever run into, nevertheless the
 behavior may be somewhat surprising.

 How about adding a note to the docs, say something like:
   If you provide an `AppConfig` instance as the sender argument, please
 ensure that the signal is registered in `AppConfig.ready` as app configs
 can be reinstantiated during testing.
 at the [https://docs.djangoproject.com/en/dev/ref/signals/#management-
 signals `pre/post_migrate/syncdb` documentation] (seems unlikely that
 anyone would use an app config as a sender for any other signal)?

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

[Django]

#11313: list_editable fields don't support 'save' in multiuser environment
+
 Reporter:  margieroginski  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1-beta
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by patjlm):

 Looking very quickly into the code, I think that this can be solved by
 replacing the following in contrib/admin/options.py changelist_view

 replace (line 1526 in 1.7 / line 1382 in 1.6.7)
   formset = cl.formset = FormSet(request.POST, request.FILES,
 queryset=cl.result_list)
 by
   formset = cl.formset = FormSet(request.POST, request.FILES)

 in this test section:
   # Handle POSTed bulk-edit data.
   if (request.method == "POST" and cl.list_editable and '_save' in
 request.POST and not action_failed):

 I am not used to generate patches nor am I knowledgeable enough in Django
 to assess if this change has a more global impact.
 Could anyone have a look?

 Thanks!

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

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

Re: [Django] #23639: Doc error in RegexValidator.regex

[Django]

#23639: Doc error in RegexValidator.regex
---+---
 Reporter:  claudep|Owner:  doriczapari
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+---

Comment (by Baptiste Mispelon ):

 In [changeset:"d2a2af67f7c2c41a831acd33cd8cba5875c216cf"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d2a2af67f7c2c41a831acd33cd8cba5875c216cf"
 [1.7.x] Fixed #23639 -- Fixed doc error in RegexValidator.regex

 Thanks to @claudep for the report and the original patch.

 Backport of c48a29a02a457cfdb1cff11009401459ba24e870 from master.
 }}}

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

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

Re: [Django] #23639: Doc error in RegexValidator.regex

[Django]

#23639: Doc error in RegexValidator.regex
---+---
 Reporter:  claudep|Owner:  doriczapari
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"c48a29a02a457cfdb1cff11009401459ba24e870"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c48a29a02a457cfdb1cff11009401459ba24e870"
 Fixed #23639 -- Fixed doc error in RegexValidator.regex

 Thanks to @claudep for the report and the original patch.
 }}}

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

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

Re: [Django] #23639: Doc error in RegexValidator.regex

[Django]

#23639: Doc error in RegexValidator.regex
---+---
 Reporter:  claudep|Owner:  doriczapari
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  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
---+---
Changes (by doriczapari):

 * has_patch:  0 => 1


Comment:

 Here's the pull request: https://github.com/django/django/pull/3346

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

Re: [Django] #23639: Doc error in RegexValidator.regex

[Django]

#23639: Doc error in RegexValidator.regex
---+---
 Reporter:  claudep|Owner:  doriczapari
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by doriczapari):

 * status:  new => assigned
 * owner:  nobody => doriczapari


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

Re: [Django] #23642: LocMemCache.incr is not thread safe

[Django]

#23642: LocMemCache.incr is not thread safe
-+
 Reporter:  tchaumeny|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Cache system)  |  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 loic):

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

[Django]

#11313: list_editable fields don't support 'save' in multiuser environment
+
 Reporter:  margieroginski  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1-beta
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by patjlm):

 * cc: patjlm (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/072.96f552d340d07ea86b9eab1c06edbd7d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23624: Regression in ManyToManyField with through, runtime-generated models

[Django]

#23624: Regression in ManyToManyField with through, runtime-generated models
-+-
 Reporter:  ludoo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ludoo):

 Replying to [comment:5 bmispelon]:
 > I've bisected the error to this commit:
 9f13c3328199d2fa70235cdc63bb06b1efc5b117

 Fantastic. The commit points to the solution: a run-time generated models
 module does not belong to any app, so its models are not used to resolve
 complex relations.

 Creating an AppConfig instance at runtime with the correct name, and a
 module with a 'models' attribute pointing to the run-time generated models
 module is not enough though, as one also needs to do some of the stuff
 that gets done in the app registry's populate method when it's
 initialized. It's a few lines of code but it feels weird and unclean, it
 would be ideal if the apps registry had a way to register apps after it
 has been initialized.

 > Still not sure if this is a bug in Django or if your use-case is just
 not supported. It certainly looks weird.

 I admit the use-case is a bit specialized, but it's something that used to
 work in 1.6, and it can be easily made to work in 1.7 with the steps
 outlined above. The only problem I see is that finding *how* it works is
 almost impossible for a regular person (it took your involvement to
 pinpoint the correct commit, etc.). Having a way to register dynamically
 generated apps/models, and somewhere in the docs that states how to do it
 would be enough for the few people needing it, I guess.

 BTW, my use-case is the Wordpress multi-blog database (each blog has its
 own set of tables, etc), so it's probably a db design used in lots of
 other legacy databases.

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

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