Re: [Django] #24112: Inconsistency in TestCase.assertInHTML

[Django]

#24112: Inconsistency in TestCase.assertInHTML
---+
 Reporter:  plumdog|Owner:  adamzap
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  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 adamzap):

 PR is updated with an attempt at an actual fix, not just a cleanup of
 plumdog's original PR

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

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

Re: [Django] #25109: MigrationLoader.load_disk hides ImportError for invalid MIGRATION_MODULES

[Django]

#25109: MigrationLoader.load_disk hides ImportError for invalid 
MIGRATION_MODULES
+
 Reporter:  blueyed |Owner:  berkerpeksag
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  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 charettes):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/7171 Proposed 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/065.8ce8c57d6607738f5a9e80f2557130cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27139: ImportError: No module named 'polls.apps.PollsConfig'

[Django]

#27139: ImportError: No module named 'polls.apps.PollsConfig'
---+
 Reporter:  pjime032   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.10
 Severity:  Normal |   Keywords:  apps
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In tutorial 02, Writing your first Django app, part 2, typing in


 {{{
 INSTALLED_APPS = [
 'polls.apps.PollsConfig',

 }}}


 will cause an ImportError: No module named 'polls.apps.PollsConfig';
 'polls.apps' is not a package

 This is resolved by instead putting


 {{{
 INSTALLED_APPS = [
 'polls',

 }}}

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

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

Re: [Django] #27132: Test PyLibMCCache on Jenkins

[Django]

#27132: Test PyLibMCCache on Jenkins
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Cache system)   |  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 Tim Graham ):

 In [changeset:"5d978c46216df53884fbca590a9abe660a739774" 5d978c46]:
 {{{
 #!CommitTicketReference repository=""
 revision="5d978c46216df53884fbca590a9abe660a739774"
 Refs #27132 -- Added pylibmc to test requirements.
 }}}

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

Re: [Django] #27137: Document how to disable migrations for an application

[Django]

#27137: Document how to disable migrations for an application
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 It's a new feature in Django 1.9 documented in
 [https://docs.djangoproject.com/en/stable/ref/settings/#migration-modules
 settings.MIGRATION_MDOULES]. Is it sufficient?

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

Re: [Django] #27136: Change auth forms' autofocus attribute to HTML5 boolean syntax

[Django]

#27136: Change auth forms' autofocus attribute to HTML5 boolean syntax
-+-
 Reporter:  jdufresne|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 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 GitHub ):

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


Comment:

 In [changeset:"ae98d40c358af2e14bac03d9a3a2dc99701aa13a" ae98d40c]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae98d40c358af2e14bac03d9a3a2dc99701aa13a"
 Fixed #27136 -- Changed auth forms' autofocus attribute to HTML5 boolean
 syntax.
 }}}

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  andkon
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by jdufresne):

 I found the above to be insufficient. Adding `MIGRATION_MODULES` as the
 only change to avoid the auth tables fails during migrations with the
 following trace:

 {{{
 Traceback (most recent call last):
   File ".../manage.py", line 9, in 
 execute_from_command_line(sys.argv)
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/__init__.py", line 367, in
 execute_from_command_line
 utility.execute()
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/__init__.py", line 359, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/base.py", line 305, in run_from_argv
 self.execute(*args, **cmd_options)
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/base.py", line 356, in execute
 output = self.handle(*args, **options)
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/commands/migrate.py", line 222, in handle
 self.verbosity, self.interactive, connection.alias,
 apps=post_migrate_apps, plan=plan,
   File ".../venv/lib64/python3.5/site-
 packages/django/core/management/sql.py", line 53, in
 emit_post_migrate_signal
 **kwargs
   File ".../venv/lib64/python3.5/site-
 packages/django/dispatch/dispatcher.py", line 191, in send
 response = receiver(signal=self, sender=sender, **named)
   File ".../venv/lib64/python3.5/site-
 packages/django/contrib/auth/management/__init__.py", line 75, in
 create_permissions
 "content_type", "codename"
   File ".../venv/lib64/python3.5/site-packages/django/db/models/query.py",
 line 256, in __iter__
 self._fetch_all()
   File ".../venv/lib64/python3.5/site-packages/django/db/models/query.py",
 line 1085, in _fetch_all
 self._result_cache = list(self.iterator())
   File ".../venv/lib64/python3.5/site-packages/django/db/models/query.py",
 line 125, in __iter__
 for row in compiler.results_iter():
   File ".../venv/lib64/python3.5/site-
 packages/django/db/models/sql/compiler.py", line 789, in results_iter
 results = self.execute_sql(MULTI)
   File ".../venv/lib64/python3.5/site-
 packages/django/db/models/sql/compiler.py", line 835, in execute_sql
 cursor.execute(sql, params)
   File ".../venv/lib64/python3.5/site-
 packages/django/db/backends/utils.py", line 79, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File ".../venv/lib64/python3.5/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File ".../venv/lib64/python3.5/site-packages/django/db/utils.py", line
 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File ".../venv/lib64/python3.5/site-packages/django/utils/six.py", line
 685, in reraise
 raise value.with_traceback(tb)
   File ".../venv/lib64/python3.5/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 django.db.utils.ProgrammingError: relation "auth_permission" does not
 exist
 LINE 1: ...ntent_type_id", "auth_permission"."codename" FROM "auth_perm...
 }}}

 This fails becuase the auth's `AppConfig`
 
[https://github.com/django/django/blob/38cf9ef390eb0cd0703d99893f826153865f6ba6/django/contrib/auth/apps.py#L15-L18
 adds a post_migrate callback] that requires the `auth_permission` table to
 exist. A project could avoid this by overriding the auth's `AppConfig`. I
 think this could be easier for projects if the auth's `AppConfig` was
 split into two classes, one base version that can be used without the auth
 tables and one that matches the current implementation. This would be a
 backwards compatible change that would allow the `MIGRATION_MODULES`
 change noted above. For example:

 {{{
 class BaseAuthConfig(AppConfig):
 name = 'django.contrib.auth'
 verbose_name = _("Authentication and Authorization")

 def ready(self):
 checks.register(check_user_model, checks.Tags.models)

 class AuthConfig(BaseAuthConfig):
 def ready(self):
 post_migrate.connect(
 create_permissions,
 dispatch_uid="django.contrib.auth.management.create_permissions"
 )
 

Re: [Django] #27128: A method model.objects.get(pk=obj.pk) returns many objects, but in a database is one.

[Django]

#27128: A method model.objects.get(pk=obj.pk) returns many objects, but in a
database is one.
-+-
 Reporter:  setivolkylany|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  GenericRelation, | Triage Stage:
  Testing, Models|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shaib):

 Replying to [comment:7 setivolkylany]:

 Hi,

 You are unlikely to get any more responses on this ticket -- it looks like
 your original problem is not caused by a bug in Django, and now you have
 started to ask about a different issue.

 Please use the support channels (#django IRC channel, django-users mailing
 list)  to ask more questions.

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

Re: [Django] #27062: Add support for for_update for MSSQL

[Django]

#27062: Add support for for_update for MSSQL
-+-
 Reporter:  denisenkom   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mssql for_update | Triage Stage:  Accepted
  database orm   |
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


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

Re: [Django] #15143: Document how to set the language for the test client

[Django]

#15143: Document how to set the language for the test client
---+-
 Reporter:  claudep|Owner:  mscott250
 Type:  New feature|   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 mscott250):

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


Comment:

 I'm interested in contributing to Django and have been advised to start
 with some of the 'easy pickings' tasks, so I'll try picking up this issue
 to get started.

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

Re: [Django] #11331: Memcached backend closes connection after every request

[Django]

#11331: Memcached backend closes connection after every request
--+
 Reporter:  booink@…  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Cache system)   |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by edmorley):

 * owner:  nobody => edmorley
 * cc: emorley@… (added)
 * status:  new => assigned


Comment:

 I'm going to open a new PR for this - however one question:

 We definitely need to `disconnect_all()` for python-memcached (since it's
 why this behaviour was added in #5133), and definitely don't want it for
 pylibmc (see pylibmc owner's comment here:
 https://github.com/django/django/pull/4866#issue-88649865) -- but what
 about third party backends? (eg python-binary-memcached and pymemcache)

 ie: should I move the `disconnect_all()` from the base class to the
 python-memcached backend (`MemcachedCache`), or make it a no-op only for
 the `PyLibMCCache` backend?

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

Re: [Django] #27063: Regex url routing + Localization (prefix_default_language)

[Django]

#27063: Regex url routing + Localization (prefix_default_language)
--+
 Reporter:  keithhackbarth|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.10
 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 keithhackbarth):

 Thanks @urbaniak. I'll test and get comments sometime this week.

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

[Django]

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|Owner:  edmorley
 Type:  Bug  |   Status:  assigned
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 edmorley):

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


Comment:

 This is fixed by the PR in #27132.

 For the first failing test in comment 4, I went with option (a) after
 splitting the test into two.
 For the second test, I also went with its option (a).

 For more details, see the comments added to the tests in the PR:
 https://github.com/django/django/pull/7168

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

Re: [Django] #27132: Test PyLibMCCache on Jenkins

[Django]

#27132: Test PyLibMCCache on Jenkins
--+
 Reporter:  edmorley  |Owner:  edmorley
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Cache system)   |  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 edmorley):

 * cc: emorley@… (added)
 * status:  new => assigned
 * has_patch:  0 => 1
 * owner:  nobody => edmorley


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

Re: [Django] #27138: timezone.localtime accepts naive datetimes on Python ≥ 3.6

[Django]

#27138: timezone.localtime accepts naive datetimes on Python ≥ 3.6
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  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 aaugustin):

 * component:  Uncategorized => Utilities
 * 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.3fb335aeead397cb733a3c17a4da62d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27138: timezone.localtime accepts naive datetimes on Python ≥ 3.6

[Django]

#27138: timezone.localtime accepts naive datetimes on Python ≥ 3.6
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 `timezone.localtime` is documented not to accept naive datetimes, however,
 it does on Python ≥ 3.6, cf. a7a7ecd2b026c61a39a46d2d7eced0e06a92c970.

 For the sake of consistency across Python versions, I think it would be
 best to implement one of the following two options:

 1. maintain the current API, check for naive datetimes and raise an
 exception,
 2. accept naive datetimes, convert them to aware datetimes with a warning
 (like Django does in other places) and update the documentation
 accordingly.

 See https://github.com/django/django/pull/7134#issuecomment-241388846 for
 a longer discussion of option 2.

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

Re: [Django] #19914: MemcachedCacheTests failing on pylibmc

[Django]

#19914: MemcachedCacheTests failing on pylibmc
-+
 Reporter:  bpeschier|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 edmorley):

 * status:  closed => new
 * resolution:  invalid =>
 * stage:  Unreviewed => Accepted


Comment:

 Reopening, since a test suite should be green on master, even if the
 underlying library is at fault.

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

[Django] #27137: Document how to disable migrations for an application

[Django]

#27137: Document how to disable migrations for an application
-+
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Apparently it's possible to pass "None" to MIGRATION_MODULES to disable
 migrations for a given app, see:

 - https://code.djangoproject.com/ticket/26401#comment:9
 - https://code.djangoproject.com/ticket/22986#comment:7

 This special value wasn't mentioned in #22032.

 I think it's a reasonable and useful behavior that we should be able to
 maintain in the future, so it would be good to document 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/052.8562d7502f5346e772d85df119da5971%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22986: Allow disabling session model database table creation if not used by session engine

[Django]

#22986: Allow disabling session model database table creation if not used by
session engine
--+--
 Reporter:  timo  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  worksforme
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by aaugustin):

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


Comment:

 Since Django 1.7 we have a clean way to prevent the creation of database
 tables, which is the crux of the issue here:

 {{{
 MIGRATION_MODULES = {
 'sessions': None
 }
 }}}

 On one hand, it's a slightly convoluted way to declare that you aren't
 using the Session model. On the other hand, it's a reasonable way to tell
 Django not to run migrations that create the table backing the Session
 model.

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  andkon
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by aaugustin):

 Great! Thanks for reporting back.

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