[Django] #27043: Testing Two

[Django]

#27043: Testing Two
-+
 Reporter:  chitrasem|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Template system  |Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I just want to test it, Can I?

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

Re: [Django] #27034: Make makemessages independent of USE_I18N

[Django]

#27034: Make makemessages independent of USE_I18N
-+-
 Reporter:  claudep  |Owner:  claudep
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 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 chitrasem):

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

[Django] #27042: Chitra

[Django]

#27042: Chitra
-+
 Reporter:  chitrasem|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Core (URLs)  |Version:  1.10
 Severity:  Normal   |   Keywords:  1
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  1
-+
 This is my first try

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

Re: [Django] #21278: Using dumpdata to create unit test fixtures causes duplicate foreign keys for auth permissions. Excluding auth causes other referenced auth models to be missing.

[Django]

#21278: Using dumpdata to create unit test fixtures causes duplicate foreign 
keys
for auth permissions.  Excluding auth causes other referenced auth models
to be missing.
--+
 Reporter:  ellisd23@…|Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.auth  |  Version:  1.5
 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 powderflask):

 In case anyone finds this ticket, searching for an answer, this seems to
 be fixed in django1.9
 I was having the problem described here, but it was resolved when I did my
 dump with:
 dumpdata --natural-foreign --natural-primary

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

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

Re: [Django] #26905: Add possibility to pass MultiValueDict-like objects as a form's data

[Django]

#26905: Add possibility to pass MultiValueDict-like objects as a form's data
--+
 Reporter:  marcinn   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"74bb013cc1edb0f2fcf24c750d4d942cae507765" 74bb013]:
 {{{
 #!CommitTicketReference repository=""
 revision="74bb013cc1edb0f2fcf24c750d4d942cae507765"
 Fixed #26905 -- Allowed using MultiValueDict-like objects as form data.
 }}}

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

[Django]

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "27039-test.diff" added.


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

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

[Django]

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I'd like to hear more about the use case. It might be argued that defaults
 should only apply to the population of initial forms and that if a user
 removes that value and submits a blank form, Django shouldn't transform it
 back to the default. Of course if we decide on that resolution, we'll have
 to document the change. If we decide to keep the old behavior, I'm
 attaching a regression test.

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

Re: [Django] #27025: Python 3.6 compatibility

[Django]

#27025: Python 3.6 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Django's test are passing with master @
 2b759c94c562c9ee9b6ca970739be15014050fda and cpython master @
 47f6c10084ed9aa8a08dbac20d5f6b814063c2df.

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

Re: [Django] #26952: Mention the need to install libffi-dev prior to installing packages for tests

[Django]

#26952: Mention the need to install libffi-dev prior to installing packages for
tests
--+
 Reporter:  edmorley  |Owner:  an0o0nym
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 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
--+

Comment (by Tim Graham ):

 In [changeset:"7c04223c018bf445efe62806deef3520ab3c89c0" 7c04223]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c04223c018bf445efe62806deef3520ab3c89c0"
 [1.10.x] Fixed #26952 -- Added tips for installing test suite
 dependencies.

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

Re: [Django] #26952: Mention the need to install libffi-dev prior to installing packages for tests

[Django]

#26952: Mention the need to install libffi-dev prior to installing packages for
tests
--+
 Reporter:  edmorley  |Owner:  an0o0nym
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 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 Tim Graham ):

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


Comment:

 In [changeset:"2b759c94c562c9ee9b6ca970739be15014050fda" 2b759c94]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b759c94c562c9ee9b6ca970739be15014050fda"
 Fixed #26952 -- Added tips for installing test suite dependencies.
 }}}

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

Re: [Django] #27025: Python 3.6 compatibility

[Django]

#27025: Python 3.6 compatibility
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by GitHub ):

 In [changeset:"a7a7ecd2b026c61a39a46d2d7eced0e06a92c970" a7a7ecd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="a7a7ecd2b026c61a39a46d2d7eced0e06a92c970"
 Refs #27025 -- Fixed a couple timezone tests for Python 3.6.

 Reflects behavior changes in PEP 495 (Local Time Disambiguation).
 }}}

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

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

[Django]

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 romgar):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #13312: Add a way to customize the order_by() of null fields

[Django]

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  binary   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering, order_by,  | Triage Stage:  Accepted
  null   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Comments for improvement are on the PR. Please uncheck "Patch needs
 improvement" after you update it an add documentation (see our
 PatchReviewChecklist).

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

Re: [Django] #27007: Handle non-UTF-8 bytes objects for text/* attachments

[Django]

#27007: Handle non-UTF-8 bytes objects for text/* attachments
-+-
 Reporter:  Feuermurmel  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Mail)  |  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):

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


Comment:

 Pending some small documentation edits.

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

Re: [Django] #27035: DiscoverRunner's setup_test_environment() hard-codes settings.DEBUG to False

[Django]

#27035: DiscoverRunner's setup_test_environment() hard-codes settings.DEBUG to
False
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a3a5ef4d0e3bf10ff80b26dd2635e40679156a2f" a3a5ef4d]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3a5ef4d0e3bf10ff80b26dd2635e40679156a2f"
 Fixed #27035 -- Eased changing settings.DEBUG for DiscoverRunner.
 }}}

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

Re: [Django] #13809: FileField open method is only accepting 'rb' modes

[Django]

#13809: FileField open method is only accepting 'rb' modes
-+-
 Reporter:  canassa  |Owner:  csinchok
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ac1975b18b5a33234284bec86e5a5bb44a4af976" ac1975b1]:
 {{{
 #!CommitTicketReference repository=""
 revision="ac1975b18b5a33234284bec86e5a5bb44a4af976"
 Fixed #13809 -- Made FieldFile.open() respect its mode argument.
 }}}

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

Re: [Django] #13809: FileField open method is only accepting 'rb' modes

[Django]

#13809: FileField open method is only accepting 'rb' modes
-+-
 Reporter:  canassa  |Owner:  csinchok
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  master
  uploads/storage|
 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


Comment:

 [https://github.com/django/django/pull/6938 PR]. I marked #26398 as a
 duplicate and will include the test from the PR for that ticket 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/065.ef44a2b3809da48ad846ebb1d6728b5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26398: FieldFile open() ignores the mode, always opening the file for reading

[Django]

#26398: FieldFile open() ignores the mode, always opening the file for reading
-+-
 Reporter:  koterpillar  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  File |  Version:  1.8
  uploads/storage|
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #13809

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

Re: [Django] #26511: Document how to do a substring search in JSONField

[Django]

#26511: Document how to do a substring search in JSONField
--+
 Reporter:  eoinmurray|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  postgres, jsonb   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 Here's a [https://github.com/django/django/compare/master...charettes
 :jsonb-fts POC] of what I had in mind.

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

Re: [Django] #26511: Document how to do a substring search in JSONField

[Django]

#26511: Document how to do a substring search in JSONField
--+
 Reporter:  eoinmurray|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  postgres, jsonb   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by charettes):

 It looks like what we really need here is support for the `->>` operator
 as `(lhs -> key)::text` is the JSON representation of the string
 (`('"foo"'::jsonb)::text` yields `'"foo"'`).

 I believe this should be done by introducing a new expression for this
 purpose and documenting it.

 In the meantime we could document using `Func('data',
 template="%(expressions)s ->> 'hobby'", output_field=models.TextField())`.

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

Re: [Django] #27037: 'required' attribute on prefilled ClearableFileInput prevents valid form submissions

[Django]

#27037: 'required' attribute on prefilled ClearableFileInput prevents valid form
submissions
-+-
 Reporter:  gasman   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 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 claudep):

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

Re: [Django] #26818: Django Admin Responsive

[Django]

#26818: Django Admin Responsive
---+--
 Reporter:  henriquechehad |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.9
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  admin, responsive  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by timgraham):

 Lets get a consensus on the DevelopersMailingList. We likely don't have
 people who could provide feedback about this monitoring Trac.

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

Re: [Django] #27019: DiscoverRunner does not restore old settings.DEBUG value in teardown

[Django]

#27019: DiscoverRunner does not restore old settings.DEBUG value in teardown
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  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
-+-

Comment (by timgraham):

 Yes, I think switching things over to `_SavedSettings` and then using
 `@mock.patch('django.test.utils._SavedSettings')` (or whatever the correct
 incantation of that is) might be the way to go.

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

Re: [Django] #26818: Django Admin Responsive

[Django]

#26818: Django Admin Responsive
---+--
 Reporter:  henriquechehad |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.9
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  admin, responsive  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by olivierdalang):

 I'm no expert at css at all, but isn't there something between "fully
 responsive  with own css framework" and "not responsive at all" ?

 I think we could improve usability on mobile without going too far in
 modifying the admin. There's already a sensible change just by adding a
 viewport meta and removing some fixed width elements.

 Wouldn't that be a valid strategy ? (improving instead of changing)
 If so, could this ticket be reopened ?

 Thanks !

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

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

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  makemigrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by charettes):

 It looks like it might have something to do with the field's
 `verbose_name`.

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

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  makemigrations  | 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):

 Take look at `django/db/migrations/autodetector.py`'s
 `generate_altered_fields()` method and see how `old_field_dec` and
 `new_field_dec` differ.

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

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  makemigrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by rserrano):

 Well, if you are going to close it at least tell me how to debug it. How
 do I know why is it finding differences between the models? Everything
 else works fine, those fields work fine.

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

Re: [Django] #26830: Issue with combination of 'with', 'ifchanged' and 'cycle' templatetags in templates.

[Django]

#26830: Issue with combination of 'with', 'ifchanged' and 'cycle' templatetags 
in
templates.
-+-
 Reporter:  flupzor  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3ae3a1f9fad800d73892b14ac8a576e817a2da55" 3ae3a1f9]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ae3a1f9fad800d73892b14ac8a576e817a2da55"
 Fixed #26830 -- Prevented the 'with' templatetag from resetting the cycle
 variable to its initial state.
 }}}

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

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  makemigrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by rserrano):

 Of course. This is the squashed migration.

 {{{#!python
 # -*- coding: utf-8 -*-
 # Generated by Django 1.9.7 on 2016-08-09 00:17
 from __future__ import unicode_literals

 import django.core.validators
 from django.db import migrations, models
 import django.db.models.deletion
 import django.utils.timezone
 import studies.model_mixins


 class Migration(migrations.Migration):

 replaces = [(b'studies', '0055_auto_20160713_1637'), (b'studies',
 '0056_auto_20160713_2229'), (b'studies', '0057_auto_20160714_2357'),
 (b'studies', '0058_auto_20160728_2032'), (b'studies',
 '0059_auto_20160801_2020'), (b'studies', '0060_auto_20160805_1655'),
 (b'studies', '0061_auto_20160808_2135')]

 dependencies = [
 ('studies', '0054_auto_20160711_0144'),
 ]

 operations = [

 migrations.CreateModel(
 name='Layer3D',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('last_modified', models.DateTimeField(auto_now=True)),
 ('info', models.TextField(default=b'{}',
 verbose_name='layer info')),
 ],
 options={
 'ordering': ['name'],
 },
 ),
 migrations.CreateModel(
 name='Layer3dProjection',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('name', models.CharField(default=b'', max_length=40,
 unique=True,
 validators=[django.core.validators.RegexValidator(message='Name should
 only contain letters, numbers, spaces, underscores and dots.',
 regex=b"^[A-Za-z0-9][A-Za-z0-9' _\\.-]*[A-Za-z0-9']$")],
 verbose_name='name')),
 ('distance', models.FloatField(default=-1,
 verbose_name='distance to search lines')),
 ('last_modified', models.DateTimeField(auto_now=True)),
 ('layer3d',
 models.ForeignKey(on_delete=django.db.models.deletion.CASCADE,
 to='studies.Layer3d', verbose_name='layer3d to project')),
 ('llist',
 models.ForeignKey(on_delete=django.db.models.deletion.CASCADE,
 to='studies.LayerList', verbose_name='layer list')),
 ],
 options={
 'ordering': ['name'],
 },
 bases=(models.Model,
 studies.model_mixins.Layer3dProjectionMixin),
 ),
 migrations.AlterUniqueTogether(
 name='layer3dprojection',
 unique_together=set([('llist', 'name')]),
 ),
 ]
 }}}

 Sorry I had not seen the reply.

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

Re: [Django] #26830: Issue with combination of 'with', 'ifchanged' and 'cycle' templatetags in templates.

[Django]

#26830: Issue with combination of 'with', 'ifchanged' and 'cycle' templatetags 
in
templates.
-+-
 Reporter:  flupzor  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"31e053edfa01e47c26dfa03834beeba77e09403a" 31e053ed]:
 {{{
 #!CommitTicketReference repository=""
 revision="31e053edfa01e47c26dfa03834beeba77e09403a"
 Refs #26830 -- Added a test for a named cycle template tag inside an
 ifchanged block and a for loop.
 }}}

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

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  makemigrations  | 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:   => needsinfo


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

Re: [Django] #27041: Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

[Django]

#27041: Note that middleware included with Django is compatible with both
MIDDLEWARE and MIDDLEWARE_CLASSES
-+-
 Reporter:  scop |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * type:  Uncategorized => Cleanup/optimization


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

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

Re: [Django] #26511: Document how to do a substring search in JSONField (was: Django 1.9 and Postgres 9.4 jsonb string containment inside JSONField)

[Django]

#26511: Document how to do a substring search in JSONField
--+
 Reporter:  eoinmurray|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  postgres, jsonb   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Marking as "Patch needs improvement" per Simon's comment, "Searching a
 whole JSON blob seems like a bad practice to me." The technique described
 in comment:3 doesn't work, so it's possible some code changes might also
 be needed to allow the desired 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/068.3435e92d4d174f6f61ad413cdd6130b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27041: Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

[Django]

#27041: Note that middleware included with Django is compatible with both
MIDDLEWARE and MIDDLEWARE_CLASSES
---+--
 Reporter:  scop   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"630613d7194007004c9b62cf614caad2492d0ad7" 630613d7]:
 {{{
 #!CommitTicketReference repository=""
 revision="630613d7194007004c9b62cf614caad2492d0ad7"
 [1.10.x] Fixed #27041 -- Documented that built-in middleware are
 compatible with MIDDLEWARE and MIDDLEWARE_CLASSES.

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

Re: [Django] #27041: Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

[Django]

#27041: Note that middleware included with Django is compatible with both
MIDDLEWARE and MIDDLEWARE_CLASSES
---+--
 Reporter:  scop   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham ):

 In [changeset:"f95bd89e827d6ee46cc6c736dadc25a10ae25fc9" f95bd89e]:
 {{{
 #!CommitTicketReference repository=""
 revision="f95bd89e827d6ee46cc6c736dadc25a10ae25fc9"
 Fixed #27041 -- Documented that built-in middleware are compatible with
 MIDDLEWARE and MIDDLEWARE_CLASSES.
 }}}

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

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

Re: [Django] #27035: DiscoverRunner's setup_test_environment() hard-codes settings.DEBUG to False

[Django]

#27035: DiscoverRunner's setup_test_environment() hard-codes settings.DEBUG to
False
-+-
 Reporter:  cjerdonek|Owner:  cjerdonek
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by cjerdonek):

 * has_patch:  0 => 1


Comment:

 Pull request added [https://github.com/django/django/pull/7052 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.08bb3de034a821594fbfe7590ebb42dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27030: Add support for GIN indexes

[Django]

#27030: Add support for GIN indexes
--+
 Reporter:  akki  |Owner:  akki
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  db-indexes| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by akki):

 * status:  new => assigned
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

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

 Some minor finishing changes left, will try to complete it today.

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

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

Re: [Django] #27041: Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

[Django]

#27041: Note that middleware included with Django is compatible with both
MIDDLEWARE and MIDDLEWARE_CLASSES
---+--
 Reporter:  scop   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by scop):

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


Comment:

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

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

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

Re: [Django] #27040: {%trans 'String' %} does not translate

[Django]

#27040: {%trans 'String' %} does not translate
---+--
 Reporter:  pbalazek   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.8
 Severity:  Normal |   Resolution:  worksforme
 Keywords:  translate  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

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


Comment:

 When I refreshed the website, the translation appeared for a second, then
 the basic string returned

 Looks like a client-side JS issue. I doubt that Django is at fault here,
 unless you can prove us the contrary.

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

[Django] #27041: Note that middleware included with Django is compatible with both MIDDLEWARE and MIDDLEWARE_CLASSES

[Django]

#27041: Note that middleware included with Django is compatible with both
MIDDLEWARE and MIDDLEWARE_CLASSES
---+
 Reporter:  scop   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.10
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I could not find a note in the docs that would say that all middleware
 included with Django is compatible with both MIDDLEWARE and
 MIDDLEWARE_CLASSES. This is useful information to have in case one is
 migrating to 1.10 but has some middleware which has not yet been migrated
 to the new style.

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

Re: [Django] #27039: ModelFields with 'default' value set and 'required'=False in form does not use default value

[Django]

#27039: ModelFields with 'default' value set and 'required'=False in form does 
not
use default value
-+-
 Reporter:  devbis   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.10
 Severity:  Release blocker  |   Resolution:
 Keywords:  default non- | Triage Stage:  Accepted
  required modelform |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thanks, but a test is still missing in the 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/064.3eaa80bab955aee8ce01b4c12cb68f08%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27038: Migration being created even when no change was made.

[Django]

#27038: Migration being created even when no change was made.
+--
 Reporter:  rserrano|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  makemigrations  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by claudep):

 Could you at least find the previous CreateField/AlterField for this field
 in the previous migrations? This would help us find what part of the field
 is triggering the change (name, on_delete, to, ...). Without further
 information, it's not possible for us to debug 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.721fcc4177e17002909afdef1258de51%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.