Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
-+-
 Reporter:  pluralschool |Owner:
 Type:   |  berabhishek
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 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 berabhishek):

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


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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
-+-
 Reporter:  pluralschool |Owner:
 Type:   |  berabhishek
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by berabhishek):

 New image added.
 Bug fixed on branch berabhishek:ticket_27085

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

Re: [Django] #17002: ManyToManyField through a model which extends some other model

[Django]

#17002: ManyToManyField through a model which extends some other model
-+-
 Reporter:  mitar|Owner:
 |  InvalidInterrupt
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by InvalidInterrupt):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * version:  1.9 => master


Comment:

 Patch work is occurring on my topic branch at
 [https://github.com/InvalidInterrupt/django/tree/ticket_17002]. I need to
 add tests to confirm proxy models are handled correctly.

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

Re: [Django] #25854: Remove deprecated usage of template.render() with RequestContext in docs

[Django]

#25854: Remove deprecated usage of template.render() with RequestContext in docs
---+-
 Reporter:  stephanm   |Owner:  alasdairnicol
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.8
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timgraham):

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


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

Re: [Django] #25854: Remove deprecated usage of template.render() with RequestContext in docs

[Django]

#25854: Remove deprecated usage of template.render() with RequestContext in docs
---+-
 Reporter:  stephanm   |Owner:  alasdairnicol
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"a033b351b5234db6170ca93ab102208cd9165820" a033b351]:
 {{{
 #!CommitTicketReference repository=""
 revision="a033b351b5234db6170ca93ab102208cd9165820"
 [1.10.x] Refs #25854 -- Completed a RequestContext docs example.

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

Re: [Django] #25854: Remove deprecated usage of template.render() with RequestContext in docs

[Django]

#25854: Remove deprecated usage of template.render() with RequestContext in docs
---+-
 Reporter:  stephanm   |Owner:  alasdairnicol
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Tim Graham ):

 In [changeset:"f8c338ec6a372841559e3134cf4d4329c460f8c7" f8c338ec]:
 {{{
 #!CommitTicketReference repository=""
 revision="f8c338ec6a372841559e3134cf4d4329c460f8c7"
 Refs #25854 -- Completed a RequestContext docs example.
 }}}

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

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

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"3342f24ff6f2314c5fc5352aa61c61bd0f43ca75" 3342f24f]:
 {{{
 #!CommitTicketReference repository=""
 revision="3342f24ff6f2314c5fc5352aa61c61bd0f43ca75"
 [1.10.x] Fixed #26807 -- Documented how to replicate SubfieldBase's
 assignment behavior.

 Backport of 518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497 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/061.599f6c1fc42a8b756f3451a4f5c684bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"717aa8843938035602148bd34f078583399967c5" 717aa884]:
 {{{
 #!CommitTicketReference repository=""
 revision="717aa8843938035602148bd34f078583399967c5"
 [1.8.x] Fixed #26807 -- Documented how to replicate SubfieldBase's
 assignment behavior.

 Backport of 518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497 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/061.53e13ab2e5f061e1be72b5f75c1c94b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497" 518eaf1f]:
 {{{
 #!CommitTicketReference repository=""
 revision="518eaf1fa2d86dc1b0ba7adba22b30bcc8f3a497"
 Fixed #26807 -- Documented how to replicate SubfieldBase's assignment
 behavior.
 }}}

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

Re: [Django] #22900: ugettext_lazy with arguments causes RuntimeError

[Django]

#22900: ugettext_lazy with arguments causes RuntimeError
--+
 Reporter:  Karmux|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Claude, do you think we need a documentation enhancement now that we have
 the "The translation infrastructure cannot be initialized before the apps
 registry is ready. Check that you don't make non-lazy gettext calls at
 import time." error message? If so, maybe you could suggest a location for
 that documentation and retitle the ticket to make it more suitable for
 beginners to contribute?

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

Re: [Django] #27068: Acquire form's initial data more consistently

[Django]

#27068: Acquire form's initial data more consistently
---+-
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"f5c6d3c8d9fa2158734858fa0a7ac917c384cb97" f5c6d3c8]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5c6d3c8d9fa2158734858fa0a7ac917c384cb97"
 Fixed #27068 -- Unified form field initial data retrieval.
 }}}

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

Re: [Django] #26040: Streaming Large CSV Files Example Incorrect

[Django]

#26040: Streaming Large CSV Files Example Incorrect
-+-
 Reporter:  przerull |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  csv streaming| Triage Stage:  Accepted
  documentation bug  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 The report never said why the example doesn't work. The example works for
 me on both Python 2.7 and Python 3.5, at least the CSV output looks fine.
 Is the problem that the response isn't streamed? If so, how do you test
 that?

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

Re: [Django] #23485: Add deeper bookmarks to Django Docs PDF

[Django]

#23485: Add deeper bookmarks to Django Docs PDF
-+-
 Reporter:  kutenai  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  pdf epub Docs| Triage Stage:  Accepted
  bookmarks  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kutenai):

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


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

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

Re: [Django] #23485: Add deeper bookmarks to Django Docs PDF

[Django]

#23485: Add deeper bookmarks to Django Docs PDF
-+-
 Reporter:  kutenai  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  pdf epub Docs| Triage Stage:  Accepted
  bookmarks  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by kutenai):

 I'm not going to be able to submit a patch for this, not with my current
 workload. I would agree with closing 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/065.25e5d3741744bbf4c2cf6a049ff74138%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23485: Add deeper bookmarks to Django Docs PDF

[Django]

#23485: Add deeper bookmarks to Django Docs PDF
-+-
 Reporter:  kutenai  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  pdf epub Docs| Triage Stage:  Accepted
  bookmarks  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Feel free to offer a patch if you feel additional headings would help in
 either context. I'm not opposed to closing this ticket as wontfix if it
 doesn't make sense.

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

Re: [Django] #25227: Promote modifying form.instance directly instead of using ModelForm.save(commit=False)

[Django]

#25227: Promote modifying form.instance directly instead of using
ModelForm.save(commit=False)
--+
 Reporter:  candeira  |Owner:  candeira
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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 timgraham):

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


Comment:

 There wasn't consensus to move forward with 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/066.1187ff05381200ae6d1a0e6cb418f5e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25258: ExpressionWrapper documentation should be expanded

[Django]

#25258: ExpressionWrapper documentation should be expanded
-+-
 Reporter:  tarkatronic  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 It looks like formal support for `Q` objects in expressions will be added
 in #27021, so I'll close this as a duplicate.

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

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

Re: [Django] #25344: Document that prefetch_related() cache doesn't change unless it's refetched from the database

[Django]

#25344: Document that prefetch_related() cache doesn't change unless it's 
refetched
from the database
--+
 Reporter:  TankOs|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  invalid
 Keywords:  prefetch_related  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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


Comment:

 The behavior change in #26706 invalidates this ticket.

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

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

Re: [Django] #25475: Database function strftime with argument %W fails in 1.9a1

[Django]

#25475: Database function strftime with argument %W fails in 1.9a1
--+
 Reporter:  vtbassmatt|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  func strftime | 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):

 Looking at this now, I'm not sure what the documentation note should say.
 Can anyone suggest something or at least give a simple description of 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/068.f02055fd47dc95c5bd5a13313d317cee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24650: Migration changing db_table and managed not creating new table

[Django]

#24650: Migration changing db_table and managed not creating new table
--+
 Reporter:  duduklein |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #26807: Document how to replicate SubfieldBase behavior of calling to_python on assignment

[Django]

#26807: Document how to replicate SubfieldBase behavior of calling to_python on
assignment
--+
 Reporter:  akx   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

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

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

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

Re: [Django] #25765: makemigrations and app_label are incompatible

[Django]

#25765: makemigrations and app_label are incompatible
--+
 Reporter:  ograycode |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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


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

Re: [Django] #25854: Remove deprecated usage of template.render() with RequestContext in docs

[Django]

#25854: Remove deprecated usage of template.render() with RequestContext in docs
---+-
 Reporter:  stephanm   |Owner:  alasdairnicol
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 Can we close out this ticket with
 [https://github.com/django/django/pull/7119 this 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/066.9aadc2078a051b38985b7a751cc083b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22414: Persistent connections not closed by LiveServerTestCase, preventing dropping test databases

[Django]

#22414: Persistent connections not closed by LiveServerTestCase, preventing
dropping test databases
-+-
 Reporter:  Koterpillar  |Owner:  cjerdonek
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  worksforme
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Feel free to reopen if you find that Django is at fault.

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

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

Re: [Django] #27018: Admin views in admindocs crash with AttributeError

[Django]

#27018: Admin views in admindocs crash with AttributeError
---+
 Reporter:  MarkusH|Owner:  helenst
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by MarkusH):

 Awesome Helen! A Python 3 solution would be fine and more than we have now
 :)

 For the tests I'd either go with

 {{{#!python
 if six.PY2:
 validate_stuff_py2()
 else:
 validate_stuff_py3()
 }}}

 or

 {{{#!python
 @unittest.skipIf(six.PY2, "Only supported for Python 3")
 def test_foo_py3(self):
 validate_stuff_py3()

 @unittest.skipIf(six.PY3, "Only supported for Python 2")
 def test_foo_py2(self):
 validate_stuff_py2()
 }}}

 The first might be easier to maintain (for the time where we still have
 general Python 2 support in Django).

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

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

Re: [Django] #27089: Add the database alias to InconsistentMigrationHistory message (was: Add the datbase alias to InconsistentMigrationHistory message)

[Django]

#27089: Add the database alias to InconsistentMigrationHistory message
-+-
 Reporter:  aholmback|Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 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
-+-
Description changed by aholmback:

Old description:

> In the file django/core/management/commands/makemigrations.py (line
> 97-100), an instance of MigrationLoader (loader) checks consistency on
> every database connection defined in settings.py.
>
> {{{
> for db in connection:
> connection = connection[db]
> if connection.settings_dict['ENGINE'] != 'django.db.backends.dummy':
> loader.check_consistent_history(connection)
> }}}
>
> The loader will then raise an InconsistentMigrationHistory exception for
> a connection whose migrations is not applied consistently, even if it's
> not to participate in the migration process.
>
> I didn't expect `makemigrations` would check connections that isn't to be
> migrated. Also, the error message "Migration xxx is applied before its
> dependency xxx" (line 285 in db/migrations/loader.py) didn't indicate
> checked connection.
>
> A more intuitive behavior would be to check only the connection that is
> to be migrated, or, if that isn't possible, include connection name in
> the error message.

New description:

 In the file django/core/management/commands/makemigrations.py (line
 97-100), an instance of MigrationLoader (loader) checks consistency on
 every database connection defined in settings.py.

 {{{
 for db in connections:
 connection = connection[db]
 if connection.settings_dict['ENGINE'] != 'django.db.backends.dummy':
 loader.check_consistent_history(connection)
 }}}

 The loader will then raise an InconsistentMigrationHistory exception for a
 connection whose migrations is not applied consistently, even if it's not
 to participate in the migration process.

 I didn't expect `makemigrations` would check connections that isn't to be
 migrated. Also, the error message "Migration xxx is applied before its
 dependency xxx" (line 285 in db/migrations/loader.py) didn't indicate
 checked connection.

 A more intuitive behavior would be to check only the connection that is to
 be migrated, or, if that isn't possible, include connection name in the
 error message.

--

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

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

Re: [Django] #27068: Acquire form's initial data more consistently

[Django]

#27068: Acquire form's initial data more consistently
---+-
 Reporter:  jdufresne  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Ready for checkin
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #27089: Add the datbase alias to InconsistentMigrationHistory message (was: commands/makemigrations.py runs MigrationLoader.check_consistent_history() for all database connections)

[Django]

#27089: Add the datbase alias to InconsistentMigrationHistory message
-+-
 Reporter:  aholmback|Owner:  timgraham
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Migrations   |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => timgraham
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 `makemigrations` doesn't run "per database" so that's why all connections
 are checked.

 Accepting on the basis that the database alias should appear in the
 message. Thanks for that suggestion.

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

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

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
-+-
 Reporter:  pluralschool |Owner:
 Type:   |  berabhishek
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by berabhishek):

 * owner:  nobody => berabhishek
 * 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/070.aefed27d608a879416038b23a9da922e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27089: commands/makemigrations.py runs MigrationLoader.check_consistent_history() for all database connections

[Django]

#27089: commands/makemigrations.py runs 
MigrationLoader.check_consistent_history()
for all database connections
+
 Reporter:  aholmback   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 In the file django/core/management/commands/makemigrations.py (line
 97-100), an instance of MigrationLoader (loader) checks consistency on
 every database connection defined in settings.py.

 {{{
 for db in connection:
 connection = connection[db]
 if connection.settings_dict['ENGINE'] != 'django.db.backends.dummy':
 loader.check_consistent_history(connection)
 }}}

 The loader will then raise an InconsistentMigrationHistory exception for a
 connection whose migrations is not applied consistently, even if it's not
 to participate in the migration process.

 I didn't expect `makemigrations` would check connections that isn't to be
 migrated. Also, the error message "Migration xxx is applied before its
 dependency xxx" (line 285 in db/migrations/loader.py) didn't indicate
 checked connection.

 A more intuitive behavior would be to check only the connection that is to
 be migrated, or, if that isn't possible, include connection name in the
 error message.

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

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

Re: [Django] #15902: Storing current language in session/cookie

[Django]

#15902: Storing current language in session/cookie
-+-
 Reporter:  msiedlarek   |Owner:
 |  msiedlarek
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  language i18n| Triage Stage:  Accepted
  session cookie |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1
 * version:  1.3 => master


Comment:

 This [https://github.com/django/django/pull/7117 PR] tries to depart from
 storing the user language in the session.

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

Re: [Django] #25871: Allow expressions in values() queryset method

[Django]

#25871: Allow expressions in values() queryset method
-+-
 Reporter:  jarshwah |Owner:  Ian-Foote
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"39f35d4b9de223b72c67bb1d12e65669b4e1355b" 39f35d4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="39f35d4b9de223b72c67bb1d12e65669b4e1355b"
 Fixed #25871 -- Added expressions support to QuerySet.values().
 }}}

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

Re: [Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by bpeschier):

 Just ran the tests at the mentioned commit on my macOS Sierra public beta
 with a fresh 3.5.2 python environment. No problems 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/067.0f6dff6a64483800d2d175a6ed83a167%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

[Django]

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

 * cc: urbaniak (added)
 * type:  Uncategorized => Bug
 * component:  Uncategorized => Internationalization


Comment:

 Krzysztof, could you triage this ticket since you worked on the
 `prefix_default_language` feature (#25933)?

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

Re: [Django] #27073: Overridden model managers shouldn't appear in _meta.managers

[Django]

#27073: Overridden model managers shouldn't appear in _meta.managers
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Loïc Bistuer ):

 In [changeset:"21f18e5372fe86090a82b696f3208e56c6a2aa80" 21f18e53]:
 {{{
 #!CommitTicketReference repository=""
 revision="21f18e5372fe86090a82b696f3208e56c6a2aa80"
 [1.10.x] Fixed #27073 -- Removed duplicated managers in
 `Model._meta.managers`.

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

Re: [Django] #27073: Overridden model managers shouldn't appear in _meta.managers

[Django]

#27073: Overridden model managers shouldn't appear in _meta.managers
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"d4eefc7e2af0d93283ed1c03e0af0a482982b6f0" d4eefc7e]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4eefc7e2af0d93283ed1c03e0af0a482982b6f0"
 Fixed #27073 -- Removed duplicated managers in `Model._meta.managers`.
 }}}

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

Re: [Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 You could check if the issue is present at the time that parallel test
 running was added in Django and if not, bisect to find the commit that
 introduced the problem.

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

Re: [Django] #27088: GEOSGeometry should accept Python 2.7 memoryview

[Django]

#27088: GEOSGeometry should accept Python 2.7 memoryview
+
 Reporter:  carljm  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  GIS |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  py2 | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * keywords:   => py2
 * stage:  Unreviewed => Accepted


Comment:

 Patches accepted by January 2017 at which point we're dropping Python 2
 support in master and could close this as wontfix.

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

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

Re: [Django] #27087: Document that flush does not affect unmanaged models

[Django]

#27087: Document that flush does not affect unmanaged models
-+-
 Reporter:  rjschave |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:
 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 timgraham):

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


Comment:

 The
 
[https://docs.djangoproject.com/en/stable/ref/models/options/#django.db.models.Options.managed
 docs for the `managed` option] makes it clear, I think. I don't think we
 need to duplicate that information in the `flush` command's 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/066.be4d180e469d81ca84266513fc7cd639%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27088: GEOSGeometry should accept Python 2.7 memoryview

[Django]

#27088: GEOSGeometry should accept Python 2.7 memoryview
--+
   Reporter:  carljm  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  GIS |Version:  1.10
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Django's custom `django.util.six` module has its own `memoryview` alias
 which is `buffer` on Py2 and `memoryview` on Py3, and `GEOSGeometry`
 enforces that its input (if any kind of buffer) be an instance of
 `django.util.six.memoryview`
 
(https://github.com/django/django/blob/master/django/contrib/gis/geos/geometry.py#L73).

 However, Python 2.7 has backported the Py3 `memoryview` type, and its use
 is preferred over Py2 `buffer` for cross-compatible code:
 https://docs.python.org/2/c-api/buffer.html

 `GEOSGeometry` should accept Py2 `memoryview` instances.

 (For backwards-compatibility reasons, even though Python 2.7 is now the
 minimum supported version, we probably can't remove
 `django.util.six.memoryview` or change it to refer to `memoryview` on Py2,
 because Py2 `buffer` and `memoryview` don't have fully compatible APIs.)

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

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

Re: [Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by cjerdonek):

 8, but it also happens when I pass `--parallel 2`. To narrow it down, it
 happens when I run the following (I believe the test setup executes, but
 it never gets to running the tests):

 {{{
 $ ./runtests.py servers.tests.LiveServerDatabase
 servers.tests.LiveServerViews
 }}}

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

Re: [Django] #27073: Overridden model managers shouldn't appear in _meta.managers (was: Checks framework doesn't ignore overridden model managers)

[Django]

#27073: Overridden model managers shouldn't appear in _meta.managers
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

[Django] #27087: Document that flush does not affect unmanaged models

[Django]

#27087: Document that flush does not affect unmanaged models
--+
 Reporter:  rjschave  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The documentation for the flush command does not make it clear that the
 flush command will not delete records from unmanaged models.

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

Re: [Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+--
 Reporter:  cjerdonek  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 I can't reproduce on Ubuntu 14.04, Python 3.5.2. Just in case, how many
 parallel process do you have? I have 4 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/067.577fb329c67274d461cb366a57a97a54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27018: Admin views in admindocs crash with AttributeError

[Django]

#27018: Admin views in admindocs crash with AttributeError
---+
 Reporter:  MarkusH|Owner:  helenst
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timgraham):

 I don't mind if the fix is Python 3 only. Python 2 raising a 404 as
 happened in older versions of Django would be okay.

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

Re: [Django] #27084: Admin site does not listen to database routers when adding objects

[Django]

#27084: Admin site does not listen to database routers when adding objects
-+-
 Reporter:  Jibodeah |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  1.10
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin, database, | Triage Stage:
  router |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Probably a duplicate of #26170.

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cjerdonek):

 Also, for future reference, an argument for putting the logic in the base
 implementation is that it's the base implementation that sets
 `self.connection` to `None` in the first place (in the finally block of
 its `close()` method, when not in an atomic block). See
 
[https://github.com/django/django/blob/76ab8851181675a59425f9637bdbf3f2de95f6f1/django/db/backends/base/base.py#L266
 here] for the code.

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

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 See also [https://docs.djangoproject.com/en/dev/internals/contributing
 /writing-documentation/#minimizing-images Minimizing images] for post
 processing to do on the image.

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bmispelon):

 * easy:  0 => 1


Comment:

 Regenerating the image will be tricky because we want to match the style
 of the others.

 However, in this instance we should be able to use an image-editing
 software to crop out the word "TEXT" and replace it with a solid gray
 backround.

 The image to edit is located in `docs/intro/_images/admin04t.png`.

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

[Django] #27086: running servers.tests hangs in parallel mode

[Django]

#27086: running servers.tests hangs in parallel mode
---+
 Reporter:  cjerdonek  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 From master (97513269d73520d10722bbd10404be6ac4d48d07), running the
 following command from the tests directory hangs for me after a couple
 tests:

 {{{
 $ ./runtests.py servers.tests
 }}}

 This is with Python 3.5.2 on Mac OSX.

 There is no error message. It just hangs. It works okay when passing
 `--parallel 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/052.3a5b10a5b851578cfa534cb578d7c971%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 Indeed, the screenshot in the tutorial is incorrect.

 Thanks for spotting that.

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
-+-
 Reporter:  pluralschool |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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 pluralschool):

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


Old description:

> Hi
>
> Here's reporting UI Discrepancy in "Writing your first Django app, part
> 2" tutorial.
>
> As per https://docs.djangoproject.com/en/1.10/intro/tutorial02/, "Home ›
> Polls › Questions" is shown displaying Check Box: "QUESTION TEXT".
> However, the actual out from the code displays Check Box: "QUESTION". The
> code was run on the following environments:
>
> CentOS 7.1 64-Bit
> Django 1.9.6
> Python 2.7.5
> pip 8.1.1
>
> Windows 8.1 64-Bit
> Django 1.10
> Python 2.7.11
> pip 8.1.2
>
> Windows 7 64-Bit
> Django 1.8.2
> Python 3.4.3
>
> Thanks

New description:

 Hi

 Here's reporting UI Discrepancy in "Writing your first Django app, part 2"
 tutorial. Please refer to the screenshots (Tutorial.JPG and Actual.JPG).

 As per https://docs.djangoproject.com/en/1.10/intro/tutorial02/, "Home ›
 Polls › Questions" is shown displaying Check Box: "QUESTION TEXT"(vide
 Tutorial.JPG). However, the actual out from the code displays Check Box:
 "QUESTION" (vide Actual.JPG). The code was run on the following
 environments:

 CentOS 7.1 64-Bit
 Django 1.9.6
 Python 2.7.5

 Windows 8.1 64-Bit
 Django 1.10
 Python 2.7.11

 Windows 7 64-Bit
 Django 1.8.2
 Python 3.4.3

 Thanks

--

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

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal| Resolution:
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by pluralschool):

 * Attachment "Actual.JPG" added.


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

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

Re: [Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal| Resolution:
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by pluralschool):

 * Attachment "Tutorial.JPG" added.


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

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

[Django] #27085: UI Discrepancy in "Writing your first Django app, part 2"

[Django]

#27085: UI Discrepancy in "Writing your first Django app, part 2"
--+
 Reporter:  pluralschool  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi

 Here's reporting UI Discrepancy in "Writing your first Django app, part 2"
 tutorial.

 As per https://docs.djangoproject.com/en/1.10/intro/tutorial02/, "Home ›
 Polls › Questions" is shown displaying Check Box: "QUESTION TEXT".
 However, the actual out from the code displays Check Box: "QUESTION". The
 code was run on the following environments:

 CentOS 7.1 64-Bit
 Django 1.9.6
 Python 2.7.5
 pip 8.1.1

 Windows 8.1 64-Bit
 Django 1.10
 Python 2.7.11
 pip 8.1.2

 Windows 7 64-Bit
 Django 1.8.2
 Python 3.4.3

 Thanks

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

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

Re: [Django] #27073: Checks framework doesn't ignore overridden model managers

[Django]

#27073: Checks framework doesn't ignore overridden model managers
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 loic):

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

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

Re: [Django] #27018: Admin views in admindocs crash with AttributeError

[Django]

#27018: Admin views in admindocs crash with AttributeError
---+
 Reporter:  MarkusH|Owner:  helenst
 Type:  Bug|   Status:  assigned
Component:  contrib.admindocs  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by helenst):

 I've fixed this but it's a Python 3 only fix due to the use of
 `__qualname__` to find out which class the view comes from and therefore
 generate the correct URL.

 There are ways to emulate `__qualname__` in py2, but kind of hacky. I see
 in migrations/serializers.py qualname is also used and a message generated
 for py2 users. Is a Python 3 only solution acceptable here? In Python 2 it
 will continue to just not work (and could be tidied up to raise a 404
 rather than an error).

 I am not sure what is the best thing here, so some input would be good!
 All is pushed to the branch linked above.

 There is also the issue of ensuring the tests pass (i.e. I have added test
 cases but they only pass for python 3).

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cjerdonek):

 Also, rather than checking for `connection is None` in advance, using
 [https://docs.python.org/3/glossary.html#term-eafp EAFP] and checking for
 `None` in an `except` block (e.g. handling AttributeError) is probably
 more Pythonic.

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by boblefrag):

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

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by cjerdonek):

 I believe the trickiest part of the patch will be handling / dealing with
 the fact that there are multiple backend implementations of `is_usable()`.

 Ideally, I think one would want to put the logic in the base
 implementation and call `super()` as appropriate. Alternatively, it looks
 like it would be sufficient to include the logic in all three non-trivial
 implementations: mysql, oracle, and postgresql. Those each look like the
 following:

 {{{#!python
 def is_usable(self):
 try:
 self.connection.ping()
 except Database.Error:
 return False
 else:
 return True
 }}}

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

[Django] #27084: Admin site does not listen to database routers when adding objects

[Django]

#27084: Admin site does not listen to database routers when adding objects
---+-
 Reporter:  Jibodeah   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.10
 Severity:  Normal |   Keywords:  admin, database, router
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+-
 == Steps to reproduce ==

 1. Use django-admin to start a new project. `django-admin startproject
 bugtest`
 2. In bugtest/settings.py rename the 'default' entry in DATABASES to
 'foobar'
 a. (also add a dummy 'default' entry which is an empty dict)


 {{{
 #!python
 DATABASES = {
 'default': {},
 'foobar': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
 }
 }
 }}}


 3. Run migrations on foobar. `./manage.py migrate --database foobar`
 4. Add a router that unconditionally maps read and write to foobar.


 {{{
 #!python
 import threading

 class Router(object):
 def db_for_read(self, model, **hints):
 database = 'foobar'
 print("Told thread {} to use {}".format(threading.get_ident(),
 database))
 return database

 def db_for_write(self, model, **hints):
 return self.db_for_read(model, **hints)
 }}}


 5. Create a superuser on foobar. `./manage.py createsuperuse --database
 foobar`
 6. Run the server and navigate to /admin, login with the superuser.
 7. Click on any 'add' link to be taken to any page to add a instance of a
 model.

 == Expected Results ==

 The page for adding an instance of a model shows up and can be used to add
 models to the foobar database.

 == Actual Results ==
 The following error is raised:

 {{{
 Traceback (most recent call last):
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/core/handlers/exception.py", line 39, in inner
 response = get_response(request)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/core/handlers/base.py", line 187, in _get_response
 response = self.process_exception_by_middleware(e, request)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/core/handlers/base.py", line 185, in _get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/contrib/admin/options.py", line 544, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/utils/decorators.py", line 149, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/views/decorators/cache.py", line 57, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/contrib/admin/sites.py", line 211, in inner
 return view(request, *args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/contrib/admin/options.py", line 1509, in add_view
 return self.changeform_view(request, None, form_url, extra_context)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/utils/decorators.py", line 67, in _wrapper
 return bound_func(*args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/utils/decorators.py", line 149, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/utils/decorators.py", line 63, in bound_func
 return func.__get__(self, type(self))(*args2, **kwargs2)
   File "/usr/lib64/python3.5/contextlib.py", line 29, in inner
 with self._recreate_cm():
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/db/transaction.py", line 158, in __enter__
 if not connection.get_autocommit():
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/db/backends/base/base.py", line 365, in get_autocommit
 self.ensure_connection()
   File "/home/jibodeah/.virtualenvs/test/lib/python3.5/site-
 packages/django/db/backends/dummy/base.py", line 21, in complain
 raise ImproperlyConfigured("settings.DATABASES is improperly
 configured. "
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.
 }}}

 Implying that the admin site is trying to use the `default` database,
 ignoring the router's suggestion.

--
Ticket URL: 
Django 
The Web framework for 

Re: [Django] #26998: admin.E013 check false positive on django-taggit

[Django]

#26998: admin.E013 check false positive on django-taggit
---+
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jonathanmorgan):

 * cc: jonathan.morgan.007@… (added)


Comment:

 Ok.  To start, I'll grab source, run tests, make the change, then run the
 tests again and see if any fail that passed before.  More soon.

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

Re: [Django] #25181: Move views.generic.dates.timezone_today() to utils.timezone

[Django]

#25181: Move views.generic.dates.timezone_today() to utils.timezone
-+
 Reporter:  timgraham|Owner:  kswiat
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by bmispelon):

 Closed #27082 as a duplicated.

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Utilities|  Version:  1.10
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by bmispelon):

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


Comment:

 Thanks for your input Aymeric.

 I think #25181 is a duplicate (I should really have searched before) so
 I'll close this one.
 There's a lengthy discussion on the PR in the other ticket.

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

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 aaugustin):

 Replying to [comment:3 jdufresne]:
 > I don't think this is about naive vs aware, but about accuracy.
 I would say that it's mostly a matter of providing a complete, but not
 redundant or overwhelming set of date/time/zones related APIs.

 > If a server's time zone is different than  `settings.TIME_ZONE`, then it
 is important to be able to answer the question "what is today in the the
 timezone of `settings.TIME_ZONE`?" accurately.

 Actually the server's time zone doesn't matter for Django on Unix/Linux
 because Django sets the process' time zone to the value defined by
 `TIME_ZONE`, and that's the default time zone for the application.

 There are two cases where the server's time zone matters:
 - on Windows, it must match `TIME_ZONE` because Windows doesn't support
 setting a process' time zone
 - if `TIME_ZONE = None`, Django uses the server time zone

 > Near midnight different time zones will have different values for
 "today".

 Yes, I guess that's the reason why Baptiste filed this ticket.

 > I have the following two convenience functions in my application to help
 make this job easier. For my application, they are always preferred over
 `datetime.date.today()`, etc. They are heavily used.
 >
 > {{{
 > def local_date():
 > return timezone.localtime(timezone.now()).date()
 >
 >
 > def local_time():
 > return timezone.localtime(timezone.now()).time()
 > }}}

 Since `django.utils.timezone.localtime` is currently used to convert an
 aware datetime to a specific time zone, we have a bit of a naming problem
 here, but I'm +0 for adding the first of these two functions (under a name
 to be defined).

 I'm not +1 because I believe that it's hard to get that kind of code right
 if you don't understand what you're doing, and writing these two one-
 liners is a good way to make sure the developer knows what's going on.

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 aaugustin):

 Yes, that's the ticket I was referring to when I mentioned `localdate`. (I
 have very spotty mobile connectivity this week, I can barely submit a
 comment and most pages don't load, so it's hard to research related
 discussions.)

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

Re: [Django] #27081: Allow migrations to serialize methods on pypy (was: DateField with current date intitialisation pypy migration issue)

[Django]

#27081: Allow migrations to serialize methods on pypy
+
 Reporter:  Kurdakov|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by timgraham):

 * type:  Uncategorized => Bug
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted
 * component:  Uncategorized => Migrations


Comment:

 Seems okay. That proposed change fixes these existing test failures on
 pypy, so I guess no new tests are needed:
 {{{
 ==
 ERROR: test_serialize_datetime (migrations.test_writer.WriterTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/tests/migrations/test_writer.py", line 330,
 in test_serialize_datetime
 self.assertSerializedEqual(datetime.datetime.utcnow)
   File "/home/tim/code/django/tests/migrations/test_writer.py", line 194,
 in assertSerializedEqual
 self.assertEqual(self.serialize_round_trip(value), value)
   File "/home/tim/code/django/tests/migrations/test_writer.py", line 190,
 in serialize_round_trip
 string, imports = MigrationWriter.serialize(value)
   File "/home/tim/code/django/django/db/migrations/writer.py", line 293,
 in serialize
 return serializer_factory(value).serialize()
   File "/home/tim/code/django/django/db/migrations/serializer.py", line
 388, in serializer_factory
 "topics/migrations/#migration-serializing" % (value,
 get_docs_version())
 ValueError: Cannot serialize: >
 There are some values Django cannot serialize into migration files.
 For more, see https://docs.djangoproject.com/en/dev/topics/migrations
 /#migration-serializing

 ==
 ERROR: test_simple_migration (migrations.test_writer.WriterTests)
 --
 Traceback (most recent call last):
   File "/home/tim/code/django/tests/migrations/test_writer.py", line 542,
 in test_simple_migration
 output = writer.as_string()
   File "/home/tim/code/django/django/db/migrations/writer.py", line 163,
 in as_string
 operation_string, operation_imports =
 OperationWriter(operation).serialize()
   File "/home/tim/code/django/django/db/migrations/writer.py", line 120,
 in serialize
 _write(arg_name, arg_value)
   File "/home/tim/code/django/django/db/migrations/writer.py", line 72, in
 _write
 arg_string, arg_imports = MigrationWriter.serialize(item)
   File "/home/tim/code/django/django/db/migrations/writer.py", line 293,
 in serialize
 return serializer_factory(value).serialize()
   File "/home/tim/code/django/django/db/migrations/serializer.py", line
 43, in serialize
 item_string, item_imports = serializer_factory(item).serialize()
   File "/home/tim/code/django/django/db/migrations/serializer.py", line
 228, in serialize
 return self.serialize_deconstructed(path, args, kwargs)
   File "/home/tim/code/django/django/db/migrations/serializer.py", line
 100, in serialize_deconstructed
 arg_string, arg_imports = serializer_factory(arg).serialize()
   File "/home/tim/code/django/django/db/migrations/serializer.py", line
 388, in serializer_factory
 "topics/migrations/#migration-serializing" % (value,
 get_docs_version())
 ValueError: Cannot serialize: >
 There are some values Django cannot serialize into migration files.
 For more, see https://docs.djangoproject.com/en/dev/topics/migrations
 /#migration-serializing
 }}}
 [https://github.com/django/django/pull/7113 PR]

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

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 bmispelon):

 Are you talking about #25181 ?

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 aaugustin):

 Ah you're right.

 `datetime.date.today()` uses the default time zone, not the current time
 zone. (I'm saying "default time zone" to mean "the time zone defined by
 settings.TIME_ZONE", which may be different from the system time zone.)
 That's because Django calls `time.tzset(settings.TIME_ZONE)` on start up,
 but doesn't call `time.tzset` when changing the active time zone.

 So, yeah, `timezone.localtime(timezone.now()).date()` is the best you can
 do at this point.

 I think there's a ticket or a PR discussing
 `timezone.localdate(aware_datetime) -> date` somewhere.
 `timezone.localnow` has also been proposed in the past. I suppose we
 should add one or both.

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 jdufresne):

 I don't think this is about naive vs aware, but about accuracy. If a
 server's time zone is different than  `settings.TIME_ZONE`, then it is
 important to be able to answer the question "what is today in the the
 timezone of `settings.TIME_ZONE`?" accurately. Near midnight different
 time zones will have different values for "today". This becomes useful
 when comparing other stored dates against "today", displaying "today", or
 storing "today" in the database. I have the following two convenience
 functions in my application to help make this job easier. For my
 application, they are always preferred over `datetime.date.today()`, etc.
 They are heavily used.

 {{{
 def local_date():
 return timezone.localtime(timezone.now()).date()


 def local_time():
 return timezone.localtime(timezone.now()).time()
 }}}

 So I personally also see some value to this suggestion.

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by boblefrag):

 My bad, I was testing with sqlite3. I can reproduce with postgresql

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

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

Re: [Django] #27083: Problems with ETag parsing and comparison

[Django]

#27083: Problems with ETag parsing and comparison
---+
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 bmispelon):

 Doesn't `datetime.date.today()` use the system's timezone and not the
 active one?

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Unless I missed something, this code matches the trackback reported above,
 so the issue likely still exists.

 The fix might be as simple as returning False `if self.connection is None`
 (assuming that doesn't break tests).

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

[Django]

#27054: makemigrations tries to create django_migrations in external database
--+
 Reporter:  SydneyUniLibrary-Jim  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.10
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"16f032e69fb9c06fd0d9feda35bba12195651214" 16f032e6]:
 {{{
 #!CommitTicketReference repository=""
 revision="16f032e69fb9c06fd0d9feda35bba12195651214"
 [1.10.x] Fixed #27054 -- Fixed makemigrations crash with a read-only
 database.

 Backport of 76ab8851181675a59425f9637bdbf3f2de95f6f1 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/078.ed933c31f71b85296f692ddfed0e9da2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
-+--
 Reporter:  bmispelon|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  1.10
 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 aaugustin):

 To get the current date in the context of the active timezone, just use
 `datetime.date.today()`. Dates are always naive, so there's no reason to
 provide an alternate constructor such as `django.utils.timezone.now()` vs
 `datetime.datetime.(utc)now()`.

 `localtime()` is intended to be a conversion function, thus `value` is
 mandatory. It exists because the `datetime.astimezone` API isn't
 sufficient to implement conversions; pytz suggests a more complicated
 pattern which `localtime()` encapsulates.

 Please let me know if this addresses your needs or if you still think
 improvements are needed.

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

Re: [Django] #27054: makemigrations tries to create django_migrations in external database

[Django]

#27054: makemigrations tries to create django_migrations in external database
--+
 Reporter:  SydneyUniLibrary-Jim  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Migrations|  Version:  1.10
 Severity:  Release blocker   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"76ab8851181675a59425f9637bdbf3f2de95f6f1" 76ab885]:
 {{{
 #!CommitTicketReference repository=""
 revision="76ab8851181675a59425f9637bdbf3f2de95f6f1"
 Fixed #27054 -- Fixed makemigrations crash with a read-only database.
 }}}

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

Re: [Django] #27083: Problems with ETag parsing and comparison

[Django]

#27083: Problems with ETag parsing and comparison
---+--
 Reporter:  marfire|Owner:  marfire
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by marfire):

 * status:  new => assigned
 * cc: k@… (added)
 * needs_better_patch:   => 1
 * needs_tests:   => 1
 * owner:  nobody => marfire
 * needs_docs:   => 1
 * has_patch:  0 => 1


Comment:

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

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

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

[Django] #27083: Problems with ETag parsing and comparison

[Django]

#27083: Problems with ETag parsing and comparison
---+
 Reporter:  marfire|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There are a number of problems with the way Django currently parses and
 compares ETags. The main issue is that we don't properly distinguish
 between weak and strong ETags. Specifically:

 - Since we don't distinguish between weak and strong ETags, all of our
 comparisons are implicitly weak (see
 [https://tools.ietf.org/html/rfc7232#section-2.3.2 section 2.3.2 of RFC
 7232]). The specification, however, says that we "MUST use the strong
 comparison function when comparing entity-tags for `If-Match`" (section
 3.1).
 - There's no way to supply a weak ETag via the `condition()` decorator.
 - If the developer specifies a weak ETag directly (by assigning to the
 `ETag` header in the response), we don't parse it properly and it will
 never match.
 - We interpret the ETag format and implement the matching algorithm based
 on the old specification (RFC 2616), not the new one (RFC 7232). They are
 somewhat different.

 Correcting this is mostly straightforward. The only tricky issue is what
 to do about the ETags returned from `etag_func()` in the `condition()`
 decorator. We currently treat these as unquoted (and implicitly strong)
 ETags. We can't suddenly require these to be quoted ETags since that would
 break backwards compatibility.

 Instead we can allow either quoted or unquoted ETags to be returned. Since
 quotes are not an allowed character in the unquoted part of the ETag under
 the new specification, there won't be any ambiguity. Existing code will
 work as before, but it will now be possible for someone to provide an
 `etag_func()` that returns a weak ETag.

 There is still the possibility of a backwards incompatibility, though,
 since as noted above the current ETag specification is slightly
 incompatible with the old one (having to do with changing from an escaped
 string to an opaque string). That is, there exist ETags that would have
 been valid and would have matched under the old specification that will
 not match after this change. I would expect actual use of such ETags to be
 rare or nonexistent, and since the problem would be caused by user code
 that is incompatible with the HTTP specification this doesn't seem like a
 fatal problem.

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

Re: [Django] #27074: connection.is_usable() raises AttributeError after the connection is closed

[Django]

#27074: connection.is_usable() raises AttributeError after the connection is 
closed
-+-
 Reporter:  cjerdonek|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by boblefrag):

 * cc: boblefrag@… (added)


Comment:

 This is no longer the case on django master branch:

 {{{
 def is_usable(self):
 try:
 # Use a psycopg cursor directly, bypassing Django's utilities.
 self.connection.cursor().execute("SELECT 1")
 except Database.Error:
 return False
 else:
 return True
 }}}

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

Re: [Django] #25476: Use pg_catalog tables to introspect constraints

[Django]

#25476: Use pg_catalog tables to introspect constraints
-+-
 Reporter:  heasus   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  psycopg2 fetchall| Triage Stage:  Accepted
  inspectdb permissions  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by socram):

 I've tweaked a bit the PR to support unique_together, too. Seems to be
 working fine on every case now.

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

[Django] #27082: Make timezone.localtime() default to timezone.now() when no value is given

[Django]

#27082: Make timezone.localtime() default to timezone.now() when no value is 
given
---+
   Reporter:  bmispelon|  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Utilities|Version:  1.10
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Sometimes I find that I need to get the current date in the context of the
 active time zone.

 As far as I understand, the correct way to do this is
 `timezone.localtime(timezone.now()).date()`.

 It'd be nice if we `localtime` would default to using `timezone.now()` is
 no value is given, so that I could simply do
 `timezone.localtime().date()`.


 This should be straightforward to implement, except for the case where
 `settings.USE_TZ = False` because `timezone.now()` would then return a
 naive datetime and `localtime()` would throw an error.

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

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