[Django] #23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py

[Django]

#23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py
--+
 Reporter:  Arfrever  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Packaging |Version:  1.7
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Django (since 1.7) installs `/usr/bin/django-admin` and `/usr/bin/django-
 admin.py`.
 Both of them execute `django.core.management.execute_from_command_line()`.
 `/usr/bin/django-admin.py` does it directly, while `/usr/bin/django-admin`
 does it through `pkg_resources` module of Setuptools.

 `/usr/bin/django-admin.py`:
 {{{
 #!/usr/bin/python3.4
 from django.core import management

 if __name__ == "__main__":
 management.execute_from_command_line()
 }}}
 `/usr/bin/django-admin`:
 {{{
 #!/usr/bin/python3.4
 # EASY-INSTALL-ENTRY-SCRIPT: 'Django==1.7','console_scripts','django-
 admin'
 __requires__ = 'Django==1.7'
 import sys
 from pkg_resources import load_entry_point

 if __name__ == '__main__':
 sys.exit(
 load_entry_point('Django==1.7', 'console_scripts', 'django-
 admin')()
 )
 }}}
 `/usr/lib64/python3.4/site-packages/Django-1.7-py3.4.egg-
 info/entry_points.txt`:
 {{{
 [console_scripts]
 django-admin = django.core.management:execute_from_command_line

 }}}

 Installation of `/usr/bin/django-admin.py` is caused by
 `scripts=['django/bin/django-admin.py']` in `setup.py`.
 Installation of `/usr/bin/django-admin` is caused by
 `entry_points={'console_scripts': ['django-admin =
 django.core.management:execute_from_command_line',]}` in `setup.py`.

 I think that it would suffice to install only one of these scripts.

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

Re: [Django] #23432: /newticket Forbidden error

[Django]

#23432: /newticket Forbidden error
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Markush2010):

 Wha about redirecting the user to the login page and showing a
 notification with the reason?

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

Re: [Django] #23415: OneToField reference to default 'id' instead of actual primary key

[Django]

#23415: OneToField reference to default 'id' instead of actual primary key
+---
 Reporter:  sky-chen|Owner:  Markush2010
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  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 Markush2010):

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


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

Re: [Django] #23432: /newticket Forbidden error

[Django]

#23432: /newticket Forbidden error
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timgraham):

 Do you have a suggestion to address this? I think the "You are currently
 not logged in. You may want to do so now." message above is clear.

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

Re: [Django] #23350: mod_wsgi authentication/authorization docs result in extra memory usage

[Django]

#23350: mod_wsgi authentication/authorization docs result in extra memory usage
-+-
 Reporter:  GrahamDumpleton  |Owner:  x110dc
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  afraid-to-commit |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 I am not an expert, but reading through the ticket, it seems like a
 warning to the effect of "The use of `WSGIApplicationGroup %{GLOBAL}`
 presumes that your Apache instance is running only one Django application.
 If you are running more than Django application, please refer to the
 mod_wsgi docs for more information about this setting."

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

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

Re: [Django] #23418: Classes embedded inside other classes are not serialized correctly

[Django]

#23418: Classes embedded inside other classes are not serialized correctly
+--
 Reporter:  dlo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 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 dlo):

 @Andrew Any way we can prevent the migration itself from being created as
 well? Although the docs mention it now, the migration is still created and
 users won't encounter the error until after running it. Thoughts?

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

[Django] #23432: /newticket Forbidden error

[Django]

#23432: /newticket Forbidden error
-+
 Reporter:  collinanderson   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  *.djangoproject.com  |Version:
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 there are a bunch of links around the site to /newticket, and that now
 says "forbidden" if you are not logged in.

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

Re: [Django] #23432: /newticket Forbidden error

[Django]

#23432: /newticket Forbidden error
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by collinanderson):

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


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

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

Re: [Django] #22161: Document that sending an email with no recipients fails silently

[Django]

#22161: Document that sending an email with no recipients fails silently
--+
 Reporter:  ian@… |Owner:  oromero
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"414e3fc59dcb429d9d96a91348f7c0eb661d70fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="414e3fc59dcb429d9d96a91348f7c0eb661d70fa"
 [1.6.x] Fixed #22161 -- Documented send() with no recipients won't raise
 an exception.

 Backport of 0f0a5c07f9 from master
 }}}

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

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

[django/django] af28f3: [1.7.x] Fixed #22161 -- Documented send() with no ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: af28f3c17515a1de9abb668942e896d777b67cba
  
https://github.com/django/django/commit/af28f3c17515a1de9abb668942e896d777b67cba
  Author: oromero 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/topics/email.txt

  Log Message:
  ---
  [1.7.x] Fixed #22161 -- Documented send() with no recipients won't raise an 
exception.

Backport of 0f0a5c07f9 from master


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

Re: [Django] #22161: Document that sending an email with no recipients fails silently

[Django]

#22161: Document that sending an email with no recipients fails silently
--+
 Reporter:  ian@… |Owner:  oromero
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"af28f3c17515a1de9abb668942e896d777b67cba"]:
 {{{
 #!CommitTicketReference repository=""
 revision="af28f3c17515a1de9abb668942e896d777b67cba"
 [1.7.x] Fixed #22161 -- Documented send() with no recipients won't raise
 an exception.

 Backport of 0f0a5c07f9 from master
 }}}

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

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

[django/django] 414e3f: [1.6.x] Fixed #22161 -- Documented send() with no ...

[GitHub]

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 414e3fc59dcb429d9d96a91348f7c0eb661d70fa
  
https://github.com/django/django/commit/414e3fc59dcb429d9d96a91348f7c0eb661d70fa
  Author: oromero 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/topics/email.txt

  Log Message:
  ---
  [1.6.x] Fixed #22161 -- Documented send() with no recipients won't raise an 
exception.

Backport of 0f0a5c07f9 from master


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

Re: [Django] #22161: Document that sending an email with no recipients fails silently

[Django]

#22161: Document that sending an email with no recipients fails silently
--+
 Reporter:  ian@… |Owner:  oromero
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  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:"0f0a5c07f9f0f4d18d4c048ed6d9554965f79d5b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0f0a5c07f9f0f4d18d4c048ed6d9554965f79d5b"
 Fixed #22161 -- Documented send() with no recipients won't raise an
 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/072.c9d965653623128a3bfd27e0f7381dbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0f0a5c: Fixed #22161 -- Documented send() with no recipien...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0f0a5c07f9f0f4d18d4c048ed6d9554965f79d5b
  
https://github.com/django/django/commit/0f0a5c07f9f0f4d18d4c048ed6d9554965f79d5b
  Author: oromero 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/topics/email.txt

  Log Message:
  ---
  Fixed #22161 -- Documented send() with no recipients won't raise an exception.


-- 
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/540a57eb8bb4e_60083f80e459f2a07072f%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] fee499: [1.7.x] Fixed #23430 -- simplified gunicorn deploy...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: fee499c80b479873685530c24d6a9bd1eb9f49a0
  
https://github.com/django/django/commit/fee499c80b479873685530c24d6a9bd1eb9f49a0
  Author: Collin Anderson 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

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

  Log Message:
  ---
  [1.7.x] Fixed #23430 -- simplified gunicorn deployment docs.

Backport of 77b3907d6d from master


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

Re: [Django] #23430: simplify gunicorn deployment docs

[Django]

#23430: simplify gunicorn deployment docs
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"77b3907d6dcd5ab0da01a782bb4b94bd6ca82b63"]:
 {{{
 #!CommitTicketReference repository=""
 revision="77b3907d6dcd5ab0da01a782bb4b94bd6ca82b63"
 Fixed #23430 -- simplified gunicorn deployment docs.
 }}}

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

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

[django/django] 77b390: Fixed #23430 -- simplified gunicorn deployment doc...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 77b3907d6dcd5ab0da01a782bb4b94bd6ca82b63
  
https://github.com/django/django/commit/77b3907d6dcd5ab0da01a782bb4b94bd6ca82b63
  Author: Collin Anderson 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

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

  Log Message:
  ---
  Fixed #23430 -- simplified gunicorn deployment docs.


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

Re: [Django] #23430: simplify gunicorn deployment docs

[Django]

#23430: simplify gunicorn deployment docs
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"fee499c80b479873685530c24d6a9bd1eb9f49a0"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fee499c80b479873685530c24d6a9bd1eb9f49a0"
 [1.7.x] Fixed #23430 -- simplified gunicorn deployment docs.

 Backport of 77b3907d6d from master
 }}}

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

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

Re: [Django] #23431: Regression in security patch for _to_field param filtering in admin

[Django]

#23431: Regression in security patch for _to_field param filtering in admin
-+-
 Reporter:  a1tus|Owner:  charettes
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.7
 Severity:  Release blocker  |   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):

 * status:  new => assigned
 * severity:  Normal => Release blocker
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => charettes
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
-+-
 Reporter:  jacinda  |Owner:  jacinda
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  *.djangoproject.com  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In
 [changeset:"5e260618a99d9d688dffb15563db008a37bf/djangoproject.com"]:
 {{{
 #!CommitTicketReference repository="djangoproject.com"
 revision="5e260618a99d9d688dffb15563db008a37bf"
 Fixed #23428 -- Added "Login with GitHub" link to account creation 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.ed4288e3feb320cce9140d50282f4ac5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22951: Adding 'deconstruct' method breaks serialization of type

[Django]

#22951: Adding 'deconstruct' method breaks serialization of type
-+-
 Reporter:  Sam Hartsfield   |Owner:
   |  jambonrose
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-1
 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 collinanderson):

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

Re: [Django] #23350: mod_wsgi authentication/authorization docs result in extra memory usage

[Django]

#23350: mod_wsgi authentication/authorization docs result in extra memory usage
-+-
 Reporter:  GrahamDumpleton  |Owner:  x110dc
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  afraid-to-commit |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by collinanderson):

 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


Comment:

 GrahamDumpleton approves the change, though doesn't address aaugustin's
 concerns.

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

[Django] #23431: Regression in security patch for _to_field param filtering in admin

[Django]

#23431: Regression in security patch for _to_field param filtering in admin
---+
 Reporter:  a1tus  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 After installing 1.7 release with this security patch I've found several
 issues concerned with raw_id widget and inlines in contrib.admin.

 `DisallowedModelAdminToField` exception was raised in both cases and
 django admin returned `HTTP code 400: Bad Request`.

 

 1st case

 The problem is that with this (whole) security fix all not registered in
 admin models can't be referenced. Though they may present in admin as
 inlines. I mean if I have models A and B that are registered in admin and
 model C which is a relation that is not registered as a separate admin
 class, I can't make my inline C_Inline class to work with raw_id_fields.
 Consider the following gist:
 https://gist.github.com/a1tus/95cd43e8eceffb8ad7fa

 

 2nd case

 Another one concerned with ManyToManyField and through model:
 https://gist.github.com/a1tus/abe1d9ffa756cf83a968

 

 See also this pull request (with some discussion and patch for this
 issue):
 https://github.com/django/django/pull/3096

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

Re: [Django] #23424: Verbatim tag fails to render curly braces

[Django]

#23424: Verbatim tag fails to render curly braces
-+-
 Reporter:  stephband|Owner:
 Type:  Bug  |  mountainpaul
Component:  Template system  |   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  verbatim template|   Resolution:
  tag| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mountainpaul):

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


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

Re: [Django] #22951: Adding 'deconstruct' method breaks serialization of type

[Django]

#22951: Adding 'deconstruct' method breaks serialization of type
-+-
 Reporter:  Sam Hartsfield   |Owner:
   |  jambonrose
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-1
 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
-+-

Comment (by jambonrose):

 I have just issued [https://github.com/django/django/pull/3177 pull-
 request 3177] to fix the 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/103.6762e78d712a11f123b2f18ab945ab90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23350: mod_wsgi authentication/authorization docs result in extra memory usage

[Django]

#23350: mod_wsgi authentication/authorization docs result in extra memory usage
--+
 Reporter:  GrahamDumpleton   |Owner:  x110dc
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by x110dc):

 I made the changes listed above here:
 https://github.com/django/django/pull/3176

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

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

[Django]

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
--+
 Reporter:  charettes |Owner:  baylee
 Type:  Bug   |   Status:  closed
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f7d3a6255c7ae3beb9ccdf6d20f6598061cd1bff"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f7d3a6255c7ae3beb9ccdf6d20f6598061cd1bff"
 Fixed #23380 -- Fixed flaky test:
 admin_filters.tests.ListFiltersTests.test_relatedfield
 }}}

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

[django/django] f7d3a6: Fixed #23380 -- Fixed flaky test: admin_filters.te...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f7d3a6255c7ae3beb9ccdf6d20f6598061cd1bff
  
https://github.com/django/django/commit/f7d3a6255c7ae3beb9ccdf6d20f6598061cd1bff
  Author: Baylee Feore 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M tests/admin_filters/tests.py

  Log Message:
  ---
  Fixed #23380 -- Fixed flaky test: 
admin_filters.tests.ListFiltersTests.test_relatedfield


-- 
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/540a4fe9b663e_ffd3f85c06f92a0126510%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23285: Non-deterministic test: admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model_admin_reverse

[Django]

#23285: Non-deterministic test:
admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model_admin_reverse
---+
 Reporter:  timgraham  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 timgraham):

 The second failure has been addressed in #23380.

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

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  docs tutorial| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"d4ef9a4a21ecf897ebcbdc49737fdb5b210fbb98"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4ef9a4a21ecf897ebcbdc49737fdb5b210fbb98"
 [1.7.x] Fixed #23427 -- Documented migrate is required before runserver
 for default projects.

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

[django/django] d4ef9a: [1.7.x] Fixed #23427 -- Documented migrate is requ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: d4ef9a4a21ecf897ebcbdc49737fdb5b210fbb98
  
https://github.com/django/django/commit/d4ef9a4a21ecf897ebcbdc49737fdb5b210fbb98
  Author: Patrick Beeson 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  [1.7.x] Fixed #23427 -- Documented migrate is required before runserver for 
default projects.

Backport of fb545e5a27 from master


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

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  docs tutorial| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"fb545e5a27369570076d0d34626f3c7e916ee2e4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb545e5a27369570076d0d34626f3c7e916ee2e4"
 Fixed #23427 -- Documented migrate is required before runserver for
 default projects.
 }}}

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

[django/django] fb545e: Fixed #23427 -- Documented migrate is required bef...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb545e5a27369570076d0d34626f3c7e916ee2e4
  
https://github.com/django/django/commit/fb545e5a27369570076d0d34626f3c7e916ee2e4
  Author: Patrick Beeson 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Fixed #23427 -- Documented migrate is required before runserver for default 
projects.


-- 
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/540a4e519d04a_3533ff3330832a05819a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23340: naturaltime documentation doesn't match behavior

[Django]

#23340: naturaltime documentation doesn't match behavior
--+--
 Reporter:  zachborboa|Owner:  blackguest
 Type:  Bug   |   Status:  assigned
Component:  contrib.humanize  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--

Comment (by collinanderson):

 converted patch into a pull request
 https://github.com/django/django/pull/3175

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

Re: [Django] #23430: simplify gunicorn deployment docs

[Django]

#23430: simplify gunicorn deployment docs
-+-
 Reporter:  collinanderson   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by collinanderson):

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


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

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

[Django] #23430: simplify gunicorn deployment docs

[Django]

#23430: simplify gunicorn deployment docs
--+
 Reporter:  collinanderson|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 https://github.com/django/django/pull/3174

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

Re: [Django] #23340: naturaltime documentation doesn't match behavior

[Django]

#23340: naturaltime documentation doesn't match behavior
--+--
 Reporter:  zachborboa|Owner:  blackguest
 Type:  Bug   |   Status:  assigned
Component:  contrib.humanize  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by blackguest):

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

Re: [Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
-+-
 Reporter:  jacinda  |Owner:  jacinda
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  *.djangoproject.com  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by collinanderson):

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

Re: [Django] #23424: Verbatim tag fails to render curly braces

[Django]

#23424: Verbatim tag fails to render curly braces
-+-
 Reporter:  stephband|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  verbatim template| Triage Stage:  Accepted
  tag|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mountainpaul):

 This occurs because the {{ and }} are the starting and ending delimiters
 for variables. This also affects block tag delimters, {% and %}, and
 comment tag delimiters, {# and #}. In all cases they must be matching.

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

Re: [Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
--+
 Reporter:  jacinda   |Owner:  jacinda
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  *.djangoproject.com   |  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 jacinda):

 * has_patch:  0 => 1


Comment:

 Pull request here: https://github.com/django/djangoproject.com/pull/83

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

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

[Django]

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
--+
 Reporter:  charettes |Owner:  baylee
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by baylee):

 See pull request here: https://github.com/django/django/pull/3173

 Unable to duplicate the Jenkins failure locally, but visual inspection
 says this should work for the list ordering 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/067.7ec94cfbe159c8b3185b4d0871cc63fa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23350: mod_wsgi authentication/authorization docs result in extra memory usage

[Django]

#23350: mod_wsgi authentication/authorization docs result in extra memory usage
--+
 Reporter:  GrahamDumpleton   |Owner:  x110dc
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by x110dc):

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


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

Re: [Django] #23307: max_num limits total number of forms, not empty forms

[Django]

#23307: max_num limits total number of forms, not empty forms
--+
 Reporter:  velle |Owner:  Octowl
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Octowl):

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


Comment:

 I'm picking this up at the don't be afraid to commit workshop in the
 djangocon sprints

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

Re: [Django] #22161: Document that sending an email with no recipients fails silently

[Django]

#22161: Document that sending an email with no recipients fails silently
--+
 Reporter:  ian@… |Owner:  oromero
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by oromero):

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


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

[django/django] de3a30: [1.7.x] Fix Python 3 incompatability

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: de3a3096d89581729d140172a50b3aab6541710f
  
https://github.com/django/django/commit/de3a3096d89581729d140172a50b3aab6541710f
  Author: Andrew Godwin 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M tests/migrations/test_graph.py

  Log Message:
  ---
  [1.7.x] Fix Python 3 incompatability


-- 
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/540a3dcd7e40c_19123fa5860752b87621c%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3ab36d: Fix Python 3 incompatability

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3ab36d00462ed2f0563ad9f4dd3be23e3567d481
  
https://github.com/django/django/commit/3ab36d00462ed2f0563ad9f4dd3be23e3567d481
  Author: Andrew Godwin 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M tests/migrations/test_graph.py

  Log Message:
  ---
  Fix Python 3 incompatability


-- 
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/540a3db44ccac_17db3fcaa9f2b29c82560%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22882: UnicodeDecodeError in command flush

[Django]

#22882: UnicodeDecodeError in command flush
-+-
 Reporter:  djbaldey |Owner:  fcurella
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  flush|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by fcurella):

 * has_patch:  0 => 1
 * version:  1.6 => master
 * needs_tests:  0 => 1


Comment:

 I've taken the liberty to create a PR implementing the fixes mentioned in
 the description

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

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

Re: [Django] #22882: UnicodeDecodeError in command flush

[Django]

#22882: UnicodeDecodeError in command flush
-+-
 Reporter:  djbaldey |Owner:  fcurella
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.6
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  flush|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by fcurella):

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


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

[django/django] 4ca44d: [1.7.x] switch out recursive dfs for stack based a...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 4ca44d5e10936f9dc2b370b965a91ccc75fb0955
  
https://github.com/django/django/commit/4ca44d5e10936f9dc2b370b965a91ccc75fb0955
  Author: Ben Reilly 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M django/db/migrations/graph.py
M tests/migrations/test_graph.py

  Log Message:
  ---
  [1.7.x] switch out recursive dfs for stack based approach, to avoid possibly 
hitting the recursion limit


-- 
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/540a3bd711e40_1853fae7110d2b8366ca%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23418: Classes embedded inside other classes are not serialized correctly

[Django]

#23418: Classes embedded inside other classes are not serialized correctly
+--
 Reporter:  dlo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 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 Andrew Godwin ):

 In [changeset:"e5cdfb151039cdd22a17480f0f1fb9ccbad5eb56"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e5cdfb151039cdd22a17480f0f1fb9ccbad5eb56"
 [1.7.x] Update docs to be more clear about nested classes (refs #23418)
 }}}

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

[django/django] e5cdfb: [1.7.x] Update docs to be more clear about nested ...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: e5cdfb151039cdd22a17480f0f1fb9ccbad5eb56
  
https://github.com/django/django/commit/e5cdfb151039cdd22a17480f0f1fb9ccbad5eb56
  Author: Andrew Godwin 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/topics/migrations.txt

  Log Message:
  ---
  [1.7.x] Update docs to be more clear about nested classes (refs #23418)


-- 
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/540a3b44be81d_70163fda86e552b83456d%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] b878c7: switch out recursive dfs for stack based approach...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b878c73fc34e661e1cc30fc96171ce09918efced
  
https://github.com/django/django/commit/b878c73fc34e661e1cc30fc96171ce09918efced
  Author: Ben Reilly 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M django/db/migrations/graph.py
M tests/migrations/test_graph.py

  Log Message:
  ---
   switch out recursive dfs for stack based approach, to avoid possibly hitting 
the recursion limit


  Commit: 2145a7782a2a0a4902b3cc4bc769010d4e2c337a
  
https://github.com/django/django/commit/2145a7782a2a0a4902b3cc4bc769010d4e2c337a
  Author: Andrew Godwin 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M django/db/migrations/graph.py
M tests/migrations/test_graph.py

  Log Message:
  ---
  Merge pull request #3171 from ClipCard/master

Prevent possible recursion limit issue in migration planning


Compare: https://github.com/django/django/compare/45768e6b7260...2145a7782a2a

-- 
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/540a3b1da0a1c_337c3faad40652c0567fd%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23429: UnicodeDecodeError raised when printing a message from runserver

[Django]

#23429: UnicodeDecodeError raised when printing a message from runserver
--+
 Reporter:  fcurella  |Owner:  fcurella
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by collinanderson):

 * stage:  Unreviewed => Accepted


Comment:

 I can confirm that the PR fixes the problem. needed for #23398

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

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.6
 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 collinanderson):

 depends on #23429.

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

Re: [Django] #23429: UnicodeDecodeError raised when printing a message from runserver

[Django]

#23429: UnicodeDecodeError raised when printing a message from runserver
-+-
 Reporter:  fcurella |Owner:  fcurella
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by fcurella):

 * needs_docs:   => 0
 * has_patch:  0 => 1
 * version:  1.6 => master
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 PR up at https://github.com/django/django/pull/3170

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

Re: [Django] #23405: Blank-able CharFields require default=''

[Django]

#23405: Blank-able CharFields require default=''
+--
 Reporter:  yuvadm  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 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 yuvadm):

 Replying to [comment:5 andrewgodwin]:
 > We should just modify the SchemaEditor to use "" as a default value if
 the field is stringable and NOT NULL. I'm pretty sure most code to do this
 already exists.

 Cool. Would you mind if I take a stab at this and try to patch this
 myself?

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

[Django] #23429: UnicodeDecodeError raised when printing a message from runserver

[Django]

#23429: UnicodeDecodeError raised when printing a message from runserver
--+--
 Reporter:  fcurella  |  Owner:  fcurella
 Type:  Cleanup/optimization  | Status:  new
Component:  HTTP handling |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 split from https://code.djangoproject.com/ticket/23398

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

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 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 andrewgodwin):

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


Comment:

 This is a limitation of the signalling system we use to create
 ContentTypes; if we fixed this to work, there would then be issues where
 the ContentTypes were created too early.

 I would suggest that the data migration uses
 ContentType.objects.get_for_model to get the ContentType before making the
 Permission, as this creates the ContentType if necessary and has internal
 caching too.

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

[django/django] 45768e: Update docs to be more clear about nested classes ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 45768e6b72607b4bc913358c560830454f3336a7
  
https://github.com/django/django/commit/45768e6b72607b4bc913358c560830454f3336a7
  Author: Andrew Godwin 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/topics/migrations.txt

  Log Message:
  ---
  Update docs to be more clear about nested classes (refs #23418)


-- 
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/540a32683d063_67193fbee07d529c2059a%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23418: Classes embedded inside other classes are not serialized correctly

[Django]

#23418: Classes embedded inside other classes are not serialized correctly
+--
 Reporter:  dlo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 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 Andrew Godwin ):

 In [changeset:"45768e6b72607b4bc913358c560830454f3336a7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="45768e6b72607b4bc913358c560830454f3336a7"
 Update docs to be more clear about nested classes (refs #23418)
 }}}

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

Re: [Django] #23365: makemigrations with a new not nullable DateTimeField leads to RuntimeWarning

[Django]

#23365: makemigrations with a new not nullable DateTimeField leads to
RuntimeWarning
-+
 Reporter:  rasca|Owner:  rmutter
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-3
 Severity:  Normal   |   Resolution:
 Keywords:  migration| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by rmutter):

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


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

Re: [Django] #23418: Classes embedded inside other classes are not serialized correctly

[Django]

#23418: Classes embedded inside other classes are not serialized correctly
+--
 Reporter:  dlo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 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 andrewgodwin):

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


Comment:

 Unfortunately, this is unserializable, as there's no way to get the
 reference to the surrounding class from the inner class. I'll update the
 docs to mention this, but the only fix for you is to move
 InvalidFormatString to the outer scope.

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

Re: [Django] #23408: Automaticly created migration calls callable for default only once

[Django]

#23408: Automaticly created migration calls callable for default only once
+
 Reporter:  Harper04|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:  invalid
 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 andrewgodwin):

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


Comment:

 This is exactly as designed; when creating columns databases only take a
 single argument for the DEFAULT clause, so we can only provide a single
 value, so we only call a callable once. If you want unique values per row,
 you'll need to populate them in RunPython as Markush2010 suggests.

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

Re: [Django] #23407: makemigrations doesn't use --noinput

[Django]

#23407: makemigrations doesn't use --noinput
--+
 Reporter:  bmispelon |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  1.7
 Severity:  Release blocker   |   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 andrewgodwin):

 Agree that implementing a new questioner is the best way, though I think
 some of the questions we can give sensible answers to (e.g. rename,
 rename_model should probably just be False as rename detection is not
 guaranteed anyway)

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

Re: [Django] #23406: Migrations not found when only .pyc files are available (e.g. in a frozen environment)

[Django]

#23406: Migrations not found when only .pyc files are available (e.g. in a 
frozen
environment)
-+-
 Reporter:  danielmenzel |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrations, .pyc,| Triage Stage:  Accepted
  frozen, cx_Freeze  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 Well, there's definitely a call here to have the underlying implementation
 (i.e. `MigrationLoader`) take a list of extensions to allow, and then I
 think we may as well go the extra leg and add a --pyc flag; I'd hate to
 have people have to override the entire command just to get this
 behaviour.

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

Re: [Django] #21661: Password reset part of django.auth isn't documented

[Django]

#21661: Password reset part of django.auth isn't documented
-+-
 Reporter:  cortex@… |Owner:
 Type:   |  chriscauley
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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:  1|UI/UX:  0
-+-
Changes (by chriscauley):

 * owner:  mrchrisadams => chriscauley


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

Re: [Django] #23405: Blank-able CharFields require default=''

[Django]

#23405: Blank-able CharFields require default=''
+--
 Reporter:  yuvadm  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 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 andrewgodwin):

 The original author is correct, CharFields are unique in their behaviour
 that the empty value for new NOT NULL instances is assumed to "", much
 like BooleanFields used to be False (but of course, that's the database
 default anyway).

 We should just modify the SchemaEditor to use "" as a default value if the
 field is stringable and NOT NULL. I'm pretty sure most code to do this
 already exists.

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

Re: [Django] #23392: Django runs all migration operations but only marks 0001 as completed

[Django]

#23392: Django runs all migration operations but only marks 0001 as completed
+--
 Reporter:  owais   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7-rc-3
 Severity:  Normal  |   Resolution:  invalid
 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 andrewgodwin):

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


Comment:

 We don't support monkeypatching models like this, so I'm going to have to
 close as INVALID. If you can reproduce it on a separate, fresh app we can
 reopen, but I suspect it's the very overloading of the model itself that's
 causing 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/063.b298031b9f0a9505f1321bfd2425fdc0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by collinanderson):

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

Re: [Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
--+
 Reporter:  jacinda   |Owner:  jacinda
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  *.djangoproject.com   |  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 jacinda):

 * status:  new => assigned


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

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by collinanderson):

 * needs_tests:  1 => 0


Comment:

 sorry i merge-confliced your change :)

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

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 fcurella):

 * needs_tests:  1 => 0


Comment:

 unchecked 'needs tests' as this might be too hard to test for, or not
 worth 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/071.d8936d8541a4e85ee30ab85146492029%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  docs tutorial| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by collinanderson):

 * has_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 "has patch" is the proper state, currently. you shouldn't "ready for
 checkin" your own 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/071.611bbcb8baf3e42bd1b621f209e27c18%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23366: Workaround for `ValueError: Dependency on app with no migrations` in #22848 may need attention

[Django]

#23366: Workaround for `ValueError: Dependency on app with no migrations` in 
#22848
may need attention
+
 Reporter:  stevejalim  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-3
 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
+

Comment (by stevejalim):

 Yes, my typo. It would have been `./manage migrate --list` (I have aliases
 set up, so conflated the terms).

 Interesting that you can't reproduce it. Will try to find time to
 replicate it in a standalone proj

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

Re: [Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
--+
 Reporter:  jacinda   |Owner:  jacinda
 Type:  Cleanup/optimization  |   Status:  new
Component:  *.djangoproject.com   |  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 freakboy3742):

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


Comment:

 Looks like we missed this as part of the transition to GitHub logins.

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

Re: [Django] #23365: makemigrations with a new not nullable DateTimeField leads to RuntimeWarning

[Django]

#23365: makemigrations with a new not nullable DateTimeField leads to
RuntimeWarning
-+
 Reporter:  rasca|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-3
 Severity:  Normal   |   Resolution:
 Keywords:  migration| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by andrewgodwin):

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

[Django] #23428: Link to Login with Github account from the Signup Page

[Django]

#23428: Link to Login with Github account from the Signup Page
--+-
 Reporter:  jacinda   |  Owner:  jacinda
 Type:  Cleanup/optimization  | Status:  new
Component:  *.djangoproject.com   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+-
 There are several places in the documentation that link to this account
 creation page: https://www.djangoproject.com/accounts/register/

 However, several of these links don't mention that you can login with a
 Github account.  I think just adding a link to login with Github to the
 account creation page would be the DRYest 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/050.1391787cef43ed36237c6b85a3222b74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23422: Cannot add Permission to Group in data migration

[Django]

#23422: Cannot add Permission to Group in data migration
+--
 Reporter:  tjwalch |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by chriscauley):

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


Comment:

 I'm a bit new to the migrations system, but I was able to verify this. I
 created a new app called "my_app" and a model called "MyModel". I created
 the first migration and then the following data migration:


 {{{
 # -*- coding: utf-8 -*-
 from __future__ import unicode_literals

 from django.db import models, migrations

 def make_permissions(apps,schema_editor):
 Group = apps.get_model("auth","Group")
 Permission = apps.get_model("auth","Permission")
 my_new_group = Group(name="test_group")
 my_new_group.save()
 my_new_group.permissions.add(
 Permission.objects.get(codename='add_mymodel',content_type__app_label='my_app')
 )

 class Migration(migrations.Migration):

 dependencies = [
 ('my_app', '0001_initial'),
 ('auth', '0001_initial'),
 ]

 operations = [
 migrations.RunPython(make_permissions,reverse_code=lambda
 *args,**kwargs: True)
 ]
 }}}

 If I run these separately (`python manage.py migrate my_app 0001;python
 manage.py migrate my_app 0002`), everything is cool. Together it breaks
 (`python manage.py migrate my_app`). You could solve this yourself by
 doing a get_or_create on the content type and on the permission, but that
 is by no means an adequate solution.

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

Re: [Django] #23318: Management command dbshell does not use DATABASE[...]['OPTIONS'] to set env PGOPTIONS

[Django]

#23318: Management command dbshell does not use DATABASE[...]['OPTIONS'] to set 
env
PGOPTIONS
-+-
 Reporter:  benjaoming   |Owner:  fcurella
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by fcurella):

 * has_patch:  0 => 1
 * version:  1.7-rc-2 => master
 * easy:  0 => 1


Comment:

 PR up at https://github.com/django/django/pull/3168

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

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

[Django]

#23273: MigrationRecorder does not obey db_router allow_migrate rules
+
 Reporter:  froomzy |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-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 andrewgodwin):

 dperetti: Just like syncdb, migrate only runs on one database at a time,
 so you must execute it individually for each database, as you suggest.
 This is by design.

 froomzy: Yes, this is likely a test runner issue, that would be doing this
 kind of migrate-on-everything. I think the suggested fix of refusing to
 migrate databases where allow_migrate on the migration model returns False
 will still work, as long as it errors in a way we can catch in the test
 runner.

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

Re: [Django] #23340: naturaltime documentation doesn't match behavior

[Django]

#23340: naturaltime documentation doesn't match behavior
--+--
 Reporter:  zachborboa|Owner:  blackguest
 Type:  Bug   |   Status:  assigned
Component:  contrib.humanize  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by blackguest):

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


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

Re: [Django] #23366: Workaround for `ValueError: Dependency on app with no migrations` in #22848 may need attention

[Django]

#23366: Workaround for `ValueError: Dependency on app with no migrations` in 
#22848
may need attention
+
 Reporter:  stevejalim  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-3
 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
+

Comment (by x110dc):

 I have no particular expertise here but I'm at the DjangoCon sprint so I
 thought I'd see if I could help. :-)  There's two things on this ticket
 that confuse me: (1) there's no `--list` option to `makemigrations`.  Did
 you mean `migrate`?  Or has this changed since the ticket was created? and
 (2) I can't reproduce the error.  I started a new (empty) Django project,
 added the sample custom User model from #22848, tried a `migrate --list`
 and didn't get any errors.  Can you show exactly what sequence created the
 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/068.ce3516ad1cd157b23d23a5aaca335c52%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23318: Management command dbshell does not use DATABASE[...]['OPTIONS'] to set env PGOPTIONS

[Django]

#23318: Management command dbshell does not use DATABASE[...]['OPTIONS'] to set 
env
PGOPTIONS
-+-
 Reporter:  benjaoming   |Owner:  fcurella
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.7-rc-2
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by fcurella):

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


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

Re: [Django] #23380: Transient failure of admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey

[Django]

#23380: Transient failure of
admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey
--+
 Reporter:  charettes |Owner:  baylee
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by baylee):

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


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

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by fcurella):

 not sure how or even where to look for existing tests that could be
 extended. Any pointer is appreciated

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

Re: [Django] #23398: Attempting to access a manage.py runserver instance over HTTPS raises UnicodeDecodeError

[Django]

#23398: Attempting to access a manage.py runserver instance over HTTPS raises
UnicodeDecodeError
---+
 Reporter:  coredumperror  |Owner:  fcurella
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by fcurella):

 * owner:  nobody => fcurella
 * status:  new => assigned
 * has_patch:  1 => 0


Comment:

 initial PR up at https://github.com/django/django/pull/3167

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

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  docs tutorial| Triage Stage:  Ready for
Has patch:  0|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by patrickbeeson):

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

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  docs tutorial| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by patrickbeeson):

 Pull request issued for release docs update:
 https://github.com/django/django/pull/3166

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

Re: [Django] #22951: Adding 'deconstruct' method breaks serialization of type

[Django]

#22951: Adding 'deconstruct' method breaks serialization of type
-+-
 Reporter:  Sam Hartsfield   |Owner:
   |  jambonrose
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7-rc-1
 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 jambonrose):

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


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

[django/django] 5e2f33: [1.7.x] Fixed #23414 -- Updated version numbers in...

[GitHub]

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 5e2f336f69f21e12fbafe6f5a4c0493258547e8a
  
https://github.com/django/django/commit/5e2f336f69f21e12fbafe6f5a4c0493258547e8a
  Author: Tim Graham 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/internals/release-process.txt

  Log Message:
  ---
  [1.7.x] Fixed #23414 -- Updated version numbers in release process doc.

Thanks jaap3 for the report.

Backport of 5c5011ce68 from master


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

Re: [Django] #23414: Release process docs are outdated

[Django]

#23414: Release process docs are outdated
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Cleanup/optimization  |   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 Tim Graham ):

 In [changeset:"5e2f336f69f21e12fbafe6f5a4c0493258547e8a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e2f336f69f21e12fbafe6f5a4c0493258547e8a"
 [1.7.x] Fixed #23414 -- Updated version numbers in release process doc.

 Thanks jaap3 for the report.

 Backport of 5c5011ce68 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/063.9a3df22ba25ff64747f62d0ff442d3c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23414: Release process docs are outdated

[Django]

#23414: Release process docs are outdated
--+
 Reporter:  jaap3 |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5c5011ce6892392e6fd2d900ec87a6c5287ae711"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c5011ce6892392e6fd2d900ec87a6c5287ae711"
 Fixed #23414 -- Updated version numbers in release process doc.

 Thanks jaap3 for the report.
 }}}

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

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

[django/django] 5c5011: Fixed #23414 -- Updated version numbers in release...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5c5011ce6892392e6fd2d900ec87a6c5287ae711
  
https://github.com/django/django/commit/5c5011ce6892392e6fd2d900ec87a6c5287ae711
  Author: Tim Graham 
  Date:   2014-09-05 (Fri, 05 Sep 2014)

  Changed paths:
M docs/internals/release-process.txt

  Log Message:
  ---
  Fixed #23414 -- Updated version numbers in release process doc.

Thanks jaap3 for the report.


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

Re: [Django] #23427: Doc update to account for runserver behavior when starting project

[Django]

#23427: Doc update to account for runserver behavior when starting project
-+-
 Reporter:  patrickbeeson|Owner:
 Type:   |  patrickbeeson
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  docs tutorial| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by collinanderson):

 If it helps, it's only an issue if you already have a `sessionid` cookie
 for the domain, so it shouldn't be an issue for everyone.

 As a side note, probably not possible with just middleware, but it would
 be nice if the session authentication check was done the first time
 `get_user(request)` is called, instead of every request, as it creates
 unnecessary session and user queries on pages where user is not used. It
 would be nice if there were a way to override the `get_user(request)`
 logic to put this check there.

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

Re: [Django] #17551: Namespaces declared in different places

[Django]

#17551: Namespaces declared in different places
-+-
 Reporter:  Kronuz   |Owner:  gnosek
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.4-alpha-1
 Severity:  Normal   |   Resolution:  invalid
 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):

 * resolution:  duplicate => invalid


Comment:

 It's [https://docs.djangoproject.com/en/dev/topics/http/urls/#term-
 instance-namespace documented] that "Instance namespaces should be unique
 across your entire project." That seems to be the issue here.

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

Re: [Django] #23048: Add the ability to make RemoveField reversible for non-null fields

[Django]

#23048: Add the ability to make RemoveField reversible for non-null fields
+
 Reporter:  harrislapiroff  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Migrations  |  Version:  1.7-rc-1
 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 andrewgodwin):

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


Comment:

 Adding a default on the model field or on the field in the migration
 should solve this, as it'll be able to populate the new field with that
 when it makes it. The only other option is to prompt people for a default
 every time they *remove* a not null field, which really confused people in
 South, so let's not do that.

 Closing as WONTFIX, as the solution is a simple edit to the migration.

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

Re: [Django] #23034: Add migrations support for adding ManyToMany "through" model

[Django]

#23034: Add migrations support for adding ManyToMany "through" model
-+-
 Reporter:  lorinkoz@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by andrewgodwin):

 * stage:  Accepted => Someday/Maybe


Comment:

 Triaging this to "someday/maybe". It would be nice, but it's a complex
 thing to add.

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

Re: [Django] #22951: Adding 'deconstruct' method breaks serialization of type

[Django]

#22951: Adding 'deconstruct' method breaks serialization of type
-+-
 Reporter:  Sam Hartsfield   |Owner:  nobody
   |   Status:  new
 Type:  Bug  |  Version:  1.7-rc-1
Component:  Migrations   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by andrewgodwin):

 * easy:  0 => 1


Comment:

 This should be an easy change to deep_deconstruct to change "doesn't have
 deconstruct: return" to "doesn't have deconstruct or is a type: return".

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

Re: [Django] #22931: Migrations cannot rename intermediate models

[Django]

#22931: Migrations cannot rename intermediate models
-+-
 Reporter:  JockeTF  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-rc-2
 Severity:  Normal   |   Resolution:
 Keywords:  migrations migrate   | Triage Stage:  Accepted
  makemigrations rename  |  Needs documentation:  0
  intermediate model |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 On the detecting of the rename: Django does not guarantee to detect
 renames, it's just a courtesy we offer if we can, so that in itself is not
 a bug. It can probably be improved, sure, but it's unrelated to this
 issue.

 It looks to me that the likely cause is RenameModel not taking care of all
 the state changes on related fields - notably, it fixes all "to"
 references, but no "through" references, so making it do that will likely
 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.9ebb8042d62ac93e208865a57858def0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22831: Migrations should provide a way to dumpdata to an initial data migration

[Django]

#22831: Migrations should provide a way to dumpdata to an initial data migration
-+
 Reporter:  gcbirzan |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

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


Comment:

 I don't see what's being asked for here. Django 1.7 and migrations don't
 support initial data fixtures, and in addition you're encouraged to do
 data migrations using the ORM and RunPython rather than calling loaddata
 (I don't want to have to make loaddata take an Apps object to get the
 right set of models).

 If you have existing South data migrations, you can literally do a find-
 and-replace to make the same code work inside RunPython - just exchange
 orm['app.Model'] for apps.get_model('app', '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/066.af32eea5f2897990f38827202a05e9c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.