date:20170106

Re: [Django] #27432: showmigrations --plan should show migrations that would be applied for the given app_labels

2017-01-06 Thread Django

#27432: showmigrations --plan should show migrations that would be applied for 
the
given app_labels
-+-
 Reporter:  Will Hardy   |Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 ):

 * owner:  (none) => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8b734d2f990063df2988143dfb5f4449b60b9ca3" 8b734d2f]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b734d2f990063df2988143dfb5f4449b60b9ca3"
 Fixed #27432 -- Made app_label arguments limit showmigrations --plan
 output.
 }}}

--
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.7e0bf9d07e8d898a5e4c9fa08e81477e%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

2017-01-06 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
-+-
 Reporter:  David Szotten|Owner:  Romain
 |  Garrigues
 Type:  Bug  |   Status:  assigned
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 Some cosmetic comments for improvement are on the 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/070.0a4ee6f961c152cc988def2b3f918bb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27257: Use the ->> operator when filtering builtin text lookups on JSONField keys

2017-01-06 Thread Django

#27257: Use the ->> operator when filtering builtin text lookups on JSONField 
keys
-+-
 Reporter:  Nick Stefan  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  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
-+-

Comment (by Simon Charette ):

 In [changeset:"d976760260c2d8371c1535a7bdeba9a2e0568a34" d9767602]:
 {{{
 #!CommitTicketReference repository=""
 revision="d976760260c2d8371c1535a7bdeba9a2e0568a34"
 Fixed #27693, Refs #27257 -- Fixed iexact lookup on JSONField keys.

 Thanks Harris Lapiroff for the report.
 }}}

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

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

Re: [Django] #27693: Case insensitive lookups on JSONField nested values

2017-01-06 Thread Django

#27693: Case insensitive lookups on JSONField nested values
-+-
 Reporter:  Harris Lapiroff  |Owner:  Simon
 |  Charette 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  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 Simon Charette ):

 * owner:  (none) => Simon Charette 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"d976760260c2d8371c1535a7bdeba9a2e0568a34" d9767602]:
 {{{
 #!CommitTicketReference repository=""
 revision="d976760260c2d8371c1535a7bdeba9a2e0568a34"
 Fixed #27693, Refs #27257 -- Fixed iexact lookup on JSONField keys.

 Thanks Harris Lapiroff for the report.
 }}}

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

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

Re: [Django] #27698: Add django.test.utils.ContextList.get()

2017-01-06 Thread Django

#27698: Add django.test.utils.ContextList.get()
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8516f7c49bfaeb1fa75d16509e05ba5d0933dc58" 8516f7c]:
 {{{
 #!CommitTicketReference repository=""
 revision="8516f7c49bfaeb1fa75d16509e05ba5d0933dc58"
 Fixed #27698 -- Added django.test.utils.ContextList.get()
 }}}

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

Re: [Django] #27698: Add django.test.utils.ContextList.get()

2017-01-06 Thread Django

#27698: Add django.test.utils.ContextList.get()
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 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 Simon Charette):

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

Re: [Django] #9198: Make the {% include %} strip a trailing newline (was: templatetag include adds new line)

2017-01-06 Thread Django

#9198: Make the {% include %} strip a trailing newline
--+
 Reporter:  Javier de la Rosa |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.0
 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 Tim Graham):

 * status:  closed => new
 * resolution:  duplicate =>
 * type:  New feature => Cleanup/optimization


Comment:

 We might reconsider changing this as discussed on
 [https://groups.google.com/d/topic/django-
 developers/QQy31BrJBm8/discussion django-developers]. The implementation
 with respect to backwards-compatibility is still to be decided.

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

Re: [Django] #9198: templatetag include adds new line

2017-01-06 Thread Django

#9198: templatetag include adds new line
---+-
 Reporter:  Javier de la Rosa  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Template system|  Version:  1.0
 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
---+-

Comment (by Tim Graham ):

 In [changeset:"12cefee5d84b3569ccbde03167c7853e8dac638f" 12cefee5]:
 {{{
 #!CommitTicketReference repository=""
 revision="12cefee5d84b3569ccbde03167c7853e8dac638f"
 Refs #15667 -- Prevented newlines in attrs.html widget rendering.

 Removed the trailing newline from widget attrs.html template.
 The solution may be revisited by fixing refs #9198 but not
 for Django 1.11.

 Thanks Dmitry Ivanchenko for the report and Preston Timmons for advice.
 }}}

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

Re: [Django] #15667: Implement template-based widget rendering

2017-01-06 Thread Django

#15667: Implement template-based widget rendering
+
 Reporter:  Bruno Renié |Owner:  (none)
 Type:  New feature |   Status:  closed
Component:  Forms   |  Version:  master
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  form-rendering  | 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:"12cefee5d84b3569ccbde03167c7853e8dac638f" 12cefee5]:
 {{{
 #!CommitTicketReference repository=""
 revision="12cefee5d84b3569ccbde03167c7853e8dac638f"
 Refs #15667 -- Prevented newlines in attrs.html widget rendering.

 Removed the trailing newline from widget attrs.html template.
 The solution may be revisited by fixing refs #9198 but not
 for Django 1.11.

 Thanks Dmitry Ivanchenko for the report and Preston Timmons for advice.
 }}}

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

Re: [Django] #11574: Allow extra blank rows for adding new records when using list_editable in admin change list view

2017-01-06 Thread Django

#11574: Allow extra blank rows for adding new records when using list_editable 
in
admin change list view
-+-
 Reporter:  Ryan Fugger  |Owner:  Adonys
 |  Alea Boffill
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  list_editable extra  | Triage Stage:  Accepted
  rows add   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tim Graham):

 I have some reservations about this. It seems unlikely that
 `list_editable` will include enough fields to create a complete object in
 most cases, and it's yet another feature that increases the complexity of
 the admin. I'd like to see a discussion on the DevelopersMailingList to
 see if there's any prior art and to see if there's consensus to add this
 feature.

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

Re: [Django] #11574: Allow extra blank rows for adding new records when using list_editable in admin change list view

2017-01-06 Thread Django

#11574: Allow extra blank rows for adding new records when using list_editable 
in
admin change list view
-+-
 Reporter:  Ryan Fugger  |Owner:  Adonys
 |  Alea Boffill
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  list_editable extra  | Triage Stage:  Accepted
  rows add   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Adonys Alea Boffill):

 * status:  new => assigned
 * owner:  (none) => Adonys Alea Boffill


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

Re: [Django] #27432: showmigrations --plan should show migrations that would be applied for the given app_labels

2017-01-06 Thread Django

#27432: showmigrations --plan should show migrations that would be applied for 
the
given app_labels
-+-
 Reporter:  Will Hardy   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 Tim Graham):

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

Re: [Django] #27690: remove sleep before dropping test db?

2017-01-06 Thread Django

#27690: remove sleep before dropping test db?
-+-
 Reporter:  David Szotten|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  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 Tim Graham ):

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


Comment:

 In [changeset:"7a6863c3380c85c6d93003a31c4fa3d83826832b" 7a6863c]:
 {{{
 #!CommitTicketReference repository=""
 revision="7a6863c3380c85c6d93003a31c4fa3d83826832b"
 Fixed #27690 -- Removed time.sleep(1) before dropping the test database.

 Uncertain if this is needed, but no failures have appeared so far.
 }}}

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

Re: [Django] #23908: XHTML breaks admin site

2017-01-06 Thread Django

#23908: XHTML breaks admin site
-+-
 Reporter:  Brian May|Owner:  Anton
 |  Samarchyan
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  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 Anton Samarchyan):

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


Comment:

 Added [https://github.com/django/django/pull/7807 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/063.5cce70048ad6bde62d88272ec9814c6a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27686: calls to request.user.is_authenticated returns vary by cookie header for all users

2017-01-06 Thread Django

#27686: calls to request.user.is_authenticated returns vary by cookie header for
all users
-+-
 Reporter:  Jeff Willette|Owner:  Jeff
 |  Willette
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:  invalid
 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 Carl Meyer):

 If you need a shared-cacheable response, then you simply need to avoid
 ever checking the session at all: the response must be the same for ALL
 users, regardless of their session or lack thereof. If you need a small
 user-specific portion (e.g. a logged-in notice in the top right or
 whatnot) in an otherwise shared-cacheable e.g. landing page, one technique
 is to populate that user-specific portion with a separate Ajax request.

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

Re: [Django] #27686: calls to request.user.is_authenticated returns vary by cookie header for all users

2017-01-06 Thread Django

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

Comment:

I don't think the analysis in this ticket is correct. If we leave out the
`Vary: Cookie` for responses to unauthenticated users, when the view
checked the session (e.g. even just by calling
`request.is_authenticated()`), then a cache could incorrectly serve the
unauthed version of the response to an authenticated user.

Fundamentally, if your view ever checks the session and modifies the
response according to its contents (or lack thereof), then that response
is cookie-dependent and should have `Vary: Cookie` set. Whether the
session was empty or not is irrelevant; if a different session cookie
could have resulted in a different response, we need `Vary: Cookie`.

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

Re: [Django] #23908: XHTML breaks admin site

2017-01-06 Thread Django

#23908: XHTML breaks admin site
-+-
 Reporter:  Brian May|Owner:  Anton
 |  Samarchyan
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anton Samarchyan):

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

Re: [Django] #27692: Remember scroll position in list screen after coming back from edit screen - remove autofocus from search field

2017-01-06 Thread Django

#27692: Remember scroll position in list screen after coming back from edit 
screen
- remove autofocus from search field
-+-
 Reporter:  Ciske Boekelo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  Remember scroll  | Triage Stage:  Accepted
  position autofocus search field|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I started [https://groups.google.com/d/topic/django-
 developers/CPfN3XLH95s/discussion a thread].

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

Re: [Django] #27692: Remember scroll position in list screen after coming back from edit screen - remove autofocus from search field

2017-01-06 Thread Django

#27692: Remember scroll position in list screen after coming back from edit 
screen
- remove autofocus from search field
-+-
 Reporter:  Ciske Boekelo|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  Remember scroll  | Triage Stage:  Accepted
  position autofocus search field|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ciske Boekelo):

 Thanks for your swift reply, Graham!
 Would you like me to ask the question on the Django Developers Mailing
 List or have/will you?

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

Re: [Django] #27698: Add django.test.utils.ContextList.get()

2017-01-06 Thread Django

#27698: Add django.test.utils.ContextList.get()
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

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

[Django] #27698: Add django.test.utils.ContextList.get()

2017-01-06 Thread Django

#27698: Add django.test.utils.ContextList.get()
+--
   Reporter:  Tim Graham|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  assigned
  Component:  Testing framework |Version:  master
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 A django-formtools test breaks with Django 1.11 because of template-widget
 rendering causing a test client response to be `ContextList` rather than
 `RequestContext`. Adding `ContextList.get()` would restore compatibility.

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

Re: [Django] #24423: Combine i18n template tag tests

2017-01-06 Thread Django

#24423: Combine i18n template tag tests
-+-
 Reporter:  Preston Timmons  |Owner:  Andy
 Type:   |  Craze
  Cleanup/optimization   |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 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:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"97c1931c4f610e80053430d0297d51e1bed1e7ae" 97c1931c]:
 {{{
 #!CommitTicketReference repository=""
 revision="97c1931c4f610e80053430d0297d51e1bed1e7ae"
 Fixed #24423 -- Reorganized i18n tag 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/072.66516c4807b43a556a0294facca92a93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27696: Email line length limiting does not work properly with Cyrillic strings

2017-01-06 Thread Django

#27696: Email line length limiting does not work properly with Cyrillic strings
-+-
 Reporter:  Pavel Pokrovskiy |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  Version:  1.10
 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 Claude Paroz ):

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


Comment:

 In [changeset:"9390533951efa2c5d0113f82850192113afda543" 93905339]:
 {{{
 #!CommitTicketReference repository=""
 revision="9390533951efa2c5d0113f82850192113afda543"
 Fixed #27696 -- Measured email long lines on encoded content

 Thanks Pavel Pokrovskiy for the report and Tim Graham for the review.
 }}}

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

Re: [Django] #8936: Add view (read-only) permission to admin

2017-01-06 Thread Django

#8936: Add view (read-only) permission to admin
---+---
 Reporter:  simon  |Owner:  Petr Dlouhý
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  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
---+---
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 There are comments for improvement from Nick Pope on the 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/063.8f17cb8e2549990152071c095a1e95c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27696: Email line length limiting does not work properly with Cyrillic strings

2017-01-06 Thread Django

#27696: Email line length limiting does not work properly with Cyrillic strings
-+-
 Reporter:  Pavel Pokrovskiy |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.10
 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 Tim Graham):

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

[Django] #27697: JSONField with blank=True is rendered as non-required field in a ModelForm

2017-01-06 Thread Django

#27697: JSONField with blank=True is rendered as non-required field in a
ModelForm
+--
Reporter: aruseni | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres |Version: 1.10
Severity: Normal| Keywords: postgres
Triage Stage: Unreviewed| Has patch: 0
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+--
Try adding a JSONField with blank=True and without null=True to your
model, and then use this model in the admin, the field will be rendered as
a non-required field, and if you specify {} as the value, everything saves
just fine.

If you don’t specify any value though, an error occurs:

{{{
null value in column "json" violates not-null constraint
}}}

If you just use a zero-configuration JSONField without blank=True, then
the form will not validate when an empty dictionary is specified.

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

Re: [Django] #24688: Add Oracle support for new-style GIS functions

2017-01-06 Thread Django

#24688: Add Oracle support for new-style GIS functions
-+-
 Reporter:  Claude Paroz |Owner:  Jani
 |  Tiainen
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  oracle   | 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 GitHub ):

 In [changeset:"ad7f3c0b7baad3d2b46bebc4809e90d4853bc3c6" ad7f3c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad7f3c0b7baad3d2b46bebc4809e90d4853bc3c6"
 Refs #24688, #27497 -- Corrected docs: distance's 'spheroid' option isn't
 PostGIS specific.
 }}}

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

Re: [Django] #27497: make Area function, Distance function and lookups work with geodetic coordinates on SpatiaLite

2017-01-06 Thread Django

#27497: make Area function, Distance function and lookups work with geodetic
coordinates on SpatiaLite
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  closed
Component:  GIS  |  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
-+-

Comment (by GitHub ):

 In [changeset:"ad7f3c0b7baad3d2b46bebc4809e90d4853bc3c6" ad7f3c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="ad7f3c0b7baad3d2b46bebc4809e90d4853bc3c6"
 Refs #24688, #27497 -- Corrected docs: distance's 'spheroid' option isn't
 PostGIS specific.
 }}}

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

Re: [Django] #27696: Email line length limiting does not work properly with Cyrillic strings (was: Fix for #22561 does not work properly with Cyrillic strings)

2017-01-06 Thread Django

#27696: Email line length limiting does not work properly with Cyrillic strings
--+
 Reporter:  Pavel Pokrovskiy  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Mail)   |  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 Tim Graham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/7803 PR] from Claude.

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

Re: [Django] #27693: Case insensitive lookups on JSONField nested values

2017-01-06 Thread Django

#27693: Case insensitive lookups on JSONField nested values
-+-
 Reporter:  Harris Lapiroff  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  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 Tim Graham):

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

Re: [Django] #22561: EmailMessage should respect RFC2822 on max line length

2017-01-06 Thread Django

#22561: EmailMessage should respect RFC2822 on max line length
-+-
 Reporter:  notsqrt  |Owner:  levkowetz
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  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
-+-

Comment (by Pavel Pokrovskiy):

 Replying to [comment:16 Claude Paroz]:
 > Instead of reopening the fixed ticket, could you please create a new one
 (where you can mention this ticket)?
 > I already have a pull request ready to fix your issue.

 #27696
 Appreciated

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

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

[Django] #27696: Fix for #22561 does not work properly with Cyrillic strings

2017-01-06 Thread Django

#27696: Fix for #22561 does not work properly with Cyrillic strings
+
   Reporter:  Pavel Pokrovskiy  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Mail)   |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 |
+
 Fix for #22561 does not work properly on Cyrillic strings.

 Tried it out with following snippet:

 https://gist.github.com/ppokrovsky/d06d0d9e3c8f55bf15984ecd22954683

 with body set to {{{ test_body_lat }}}, the {{{has_long_lines}}} flag in
 {{{ django.core.mail.message.SafeMIMEText() }}} is set to {{{ True }}} and
 therefore correctly applies 'quoted-printable' encoding, while when body
 is set to {{{ test_body_ru }}}, it leaves {{{has_long_lines}}} as {{{
 False }}} therefore leaving default charset, which results in broken email
 body.

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

Re: [Django] #22420: Postgresql connections not being dropped between tests?

2017-01-06 Thread Django

Comment (by Paul Bormans):

I'm seeing the same issue running a test suite that contains
"TransactionTestCase" cases. Further more i'm running django 1.9.10 and
postgres 9.3.

The odd thing is that the testcase causing the trouble ran fine before
using default TestCase base class. But for reasons unknown to me (maybe
upgrade some libs?) a worker thread part of the testcase started to yield
no results from the orm that should be initialized using fixtures. It ran
fine again after a switched to TransactionTestCase but that gave the
mentioned issue:

django.db.utils.OperationalError: database "" is being accessed by
other users
DETAIL: There is 1 other session using the database.

I tried the cleanup decorator and it does close 1 connection but the error
message remains.

I double checked that each of the Thread instances is properly closed
(there is an explicit join() before the testcase ends).

Does each thread have its own session? Could i explicitly close it in a
finally block?

Paul

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

Re: [Django] #27688: Django message framework add_message() should prefer ducktyping over isinstance

2017-01-06 Thread Django

#27688: Django message framework add_message() should prefer ducktyping over
isinstance
--+
 Reporter:  Raffaele Salmaso  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.messages  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  messages  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Raffaele Salmaso):

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

Re: [Django] #27688: Django message framework add_message() should prefer ducktyping over isinstance

2017-01-06 Thread Django

#27688: Django message framework add_message() should prefer ducktyping over
isinstance
--+
 Reporter:  Raffaele Salmaso  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.messages  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  messages  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Raffaele Salmaso):

 Update the PR (mostly rewritten).
 Now it is similar to original behaviour.

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

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

Re: [Django] #22561: EmailMessage should respect RFC2822 on max line length

2017-01-06 Thread Django

#22561: EmailMessage should respect RFC2822 on max line length
-+-
 Reporter:  notsqrt  |Owner:  levkowetz
 Type:  Bug  |   Status:  closed
Component:  Core (Mail)  |  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 Claude Paroz):

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


Comment:

 Instead of reopening the fixed ticket, could you please create a new one
 (where you can mention this ticket)?
 I already have a pull request ready to fix your 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/065.a86c683a80a1090aa8c07893129dc685%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27090: pg_get_serial_sequence is broken on postgres, use a lookup in information_schema.columns instead

2017-01-06 Thread Django

#27090: pg_get_serial_sequence is broken on postgres, use a lookup in
information_schema.columns instead
-+-
 Reporter:  Hanne Moa|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgres sequence| Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Hanne Moa):

 Tom Lane's suggestion is what we will be going with.

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

37 matches

Mail list logo