Re: [Django] #25361: Unpickling of QuerySet fails in presence of abstract intermediate model

[Django]

#25361: Unpickling of QuerySet fails in presence of abstract intermediate model
-+-
 Reporter:  Torsten Bronger  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Samuel Spencer):

 I just got bit by this and I can't say I've come across the best solution,
 but I was able to resolve it with this code in
 {{{/django/db/models/fields/__init__.py}}}:

 {{{
 --- __init__.py 2016-09-22 06:07:36.167725186 +
 +++ __init__.py.old 2016-09-22 06:08:19.175742789 +
 @@ -66,11 +66,6 @@
  return apps.get_model(app_label,
 model_name)._meta.get_field(field_name)


 -def _load_field_for_abstract(app_label, model_name, field_name):
 -from django.utils.module_loading import import_string
 -return import_string('%s.models.%s'%(app_label,
 model_name))._meta.get_field(field_name)
 -
 -
  # A guide to Field parameters:
  #
  #   * name:  The name of the field specified in the model.
 @@ -508,11 +503,7 @@
  # Deferred model will not be found from the app registry.
 This
  # could be fixed by reconstructing the deferred model on
 unpickle.
  raise RuntimeError("Fields of deferred models can't be
 reduced")
 -if self.model._meta.abstract:
 -func = _load_field_for_abstract
 -else:
 -func = _load_field
 -return func, (self.model._meta.app_label,
 self.model._meta.object_name,
 +return _load_field, (self.model._meta.app_label,
 self.model._meta.object_name,
   self.name)

  def get_pk_value_on_save(self, instance):
 }}}

 {{{__init__.py.old}}} is the original from Django 1.8.14. I'm not sure
 where to begin with submitting and testing this, but I'd like to help if
 someone could give me some pointers.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.ff1778b4dec0e897327e798f4d3ec25e%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

[Django]

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

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7279 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/068.e977fc97b8fdf41a3d57ac05ed2ddf41%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 (was: regex and iregex lookups crash on JSONField)

[Django]

#27257: Use the ->> operator when filtering builtin text lookups on JSONField 
keys
-+-
 Reporter:  Nick Stefan  |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * keywords:  QuerySet.extra =>
 * owner:  nobody => Simon Charette
 * version:  1.9 => master
 * status:  new => assigned


Comment:

 The operator precedence crash was fixed by
 2eb7d6e6d41480f21305fc6abe2f1a443491ddec but we should really be using the
 `->>` for text lookups as `::text` will use the text representation of the
 accessed key.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.1bf08c34de8190084aa192c7ae351b1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27234: Clarify the type of the django.server logger's 'request' extra context

[Django]

#27234: Clarify the type of the django.server logger's 'request' extra context
-+-
 Reporter:  Ben Whale|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  django.request   | Triage Stage:  Accepted
  runserver WSGIRequest socket   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ben Whale):

 Agreed, and even if it was possible it'd be along way off. The additional
 work required for beginners to get up and running would also need to be
 considered.

 It might be possible to replace the calls to django.server with calls to
 django.request without removing {{{runserver}}} or do you think
 django.server is too tightly integrated? Such a change might make it
 easier to remove {{{runserver}}} in the future?

 As a side point, would you be against including a comment in the django
 logging documentation that certain kinds of logging (e.g. all incoming
 requests) are better handled by the actual webserver (e.g. Apache or
 Nginx) in a production or remote development environment?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.23a77d14781567f24b40052f4f662bb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20705: Allow customizing the email field name for PasswordResetForm

[Django]

#20705: Allow customizing the email field name for PasswordResetForm
--+-
 Reporter:  Cloudream |Owner:  mlevental
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.0576c9220d5a1e074d51fd0da2058f72%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27257: regex and iregex lookups crash on JSONField

[Django]

#27257: regex and iregex lookups crash on JSONField
--+
 Reporter:  Nick Stefan   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  QuerySet.extra| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Nick Stefan):

 Replying to [comment:1 Tim Graham]:
 > Is the discussion from #26511 relevant here? I'd at least call it a bug
 that a lookup is available that crashes.

 Yes! That other discussion is relevant. Especially this comment:
 https://code.djangoproject.com/ticket/26511#comment:10

 The error I got was distinct, but the needed solution is similar.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f9be7d7dedfc65cc070bdd2b1b49e1a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27056: changing dim property for geometries does not generate correct migration on PostgreSQL (was: changing dim property for gemotries does not generate correct migration)

[Django]

#27056: changing dim property for geometries does not generate correct 
migration on
PostgreSQL
-+-
 Reporter:  Bill Durr|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango postgres   | Triage Stage:  Ready for
  postgis|  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


Comment:

 Looks good, pending a few cosmetic issues.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.47c072a5b0b76e15fc28d9e52b5980e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27257: regex and iregex lookups crash on JSONField (was: JSONB regex and iregex)

[Django]

#27257: regex and iregex lookups crash on JSONField
--+
 Reporter:  Nick Stefan   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  QuerySet.extra| 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):

 * needs_better_patch:   => 0
 * component:  Database layer (models, ORM) => contrib.postgres
 * needs_tests:   => 0
 * easy:  1 => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Is the discussion from #26511 relevant here? I'd at least call it a bug
 that a lookup is available that crashes.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.a64d3d9e841a4039fc24b2161ded0dae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27256: Change the selected attribute of select form tags to use HTML5 boolean syntax

[Django]

#27256: Change the selected attribute of select form tags to use HTML5 boolean
syntax
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"2c716c1dc721e74ef14b2ac25e3510024c79e070" 2c716c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c716c1dc721e74ef14b2ac25e3510024c79e070"
 Fixed #27256 -- Changed Select widget's selected attribute to use HTML5
 boolean syntax.
 }}}

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

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

[Django] #27257: JSONB regex and iregex

[Django]

#27257: JSONB regex and iregex
--+
 Reporter:  Nick Stefan   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Normal|   Keywords:  QuerySet.extra
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 Given a model with a jsonb field, 'content', and it has a key called
 'altText'.


 {{{
 queryset.filter(content__altText__iregex="bob")

 }}}

 creates this SQL

 {{{
 "content" -> 'altText'::text ~* 'bob'
 }}}

 Which creates a type error

 {{{
 ERROR:  operator does not exist: jsonb ~* unknown at character 2792
 postgres| HINT:  No operator matches the given name and argument
 type(s). You might need to add explicit type casts.
 }}}



 SQL actually needed is


 {{{
 content ->> altText ~* 'bob'
 }}}


 So I had to use:

 {{{
 queryset.extra(where=['content ->> %s ~* %s'], params=['altText', 'bob'])
 }}}

 Is this something to be filed under QuerySet.extra or is this more of a
 bug just with JSONField ?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.8ad439327a0cb4f74b3f4356ba0dc1be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26210: Make the SMTP more efficient if an error passes silently when creating a connection

[Django]

#26210: Make the SMTP more efficient if an error passes silently when creating a
connection
-+-
 Reporter:  Antonis  |Owner:  mlevental
  Christofides   |
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Mail)  |  Version:  1.9
 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:"42dc9d04006c0bdecba6e0c8a29038b01d5a62d7" 42dc9d04]:
 {{{
 #!CommitTicketReference repository=""
 revision="42dc9d04006c0bdecba6e0c8a29038b01d5a62d7"
 Fixed #26210 -- Prevented SMTP backend from trying to send mail after a
 connection failure.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.713bb7ba8af8e54deea91ef51a27616b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16682: KeyboardInterrupt not handled properly in transaction aborting

[Django]

#16682: KeyboardInterrupt not handled properly in transaction aborting
-+-
 Reporter:  Malcolm Tredinnick   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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
 * has_patch:  0 => 1
 * resolution:   => fixed
 * stage:  Accepted => Ready for checkin


Comment:

 I created a [https://github.com/django/django/pull/7276 PR] and Aymeric
 indicated that adding the test is useful.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.41cafe7b4523989b8e14636485248e1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14336: list_display should be able to contain sortable references to annotated fields (was: list_display should be able to contain sortable references to extra and/or annotated fields)

[Django]

#14336: list_display should be able to contain sortable references to annotated
fields
+--
 Reporter:  Paul McLanahan  |Owner:  Jon Culver
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  1.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham):

 I'm removing consideration of "extra" fields from the summary because
 `QuerySet.extra()` is now discouraged and likely to be deprecated in the
 future.

 #27229 is a related ticket that suggests allowing aggregations in
 `list_display`. I hope to figure out a suitable path forward for this on
 the [https://groups.google.com/d/topic/django-
 developers/T1-80RV8b5g/discussion django-developers mailing list] thread.
 Jon, sorry you didn't get any feedback from your original work. Feel free
 to chime in here if you still have time and interest in working on 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/068.09f9595350cc72a2d5fecb3abc578b0d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20705: Allow customizing the email field name for PasswordResetForm

[Django]

#20705: Allow customizing the email field name for PasswordResetForm
--+-
 Reporter:  Cloudream |Owner:  mlevental
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 mlevental):

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

Re: [Django] #26610: Add a citext field for contrib.postgres

[Django]

#26610: Add a citext field for contrib.postgres
-+-
 Reporter:  Shadow   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  index charfield  | Triage Stage:  Accepted
  textfield case insensitive |
  optimisation db-indexes|
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:"094d630ae8d8e5e68817c313da0fd737898b216b" 094d630]:
 {{{
 #!CommitTicketReference repository=""
 revision="094d630ae8d8e5e68817c313da0fd737898b216b"
 Fixed #26610 -- Added CITextField to contrib.postgres.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.881a8e53bd14cdc59019004adfa1a99a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24941: Add get_exclude() hook to BaseModelAdmin

[Django]

#24941: Add get_exclude() hook to BaseModelAdmin
--+---
 Reporter:  Peter J. Farrell  |Owner:  Zach Borboa
 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:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Zach Borboa):

 * owner:  Ola Sitarska => Zach Borboa
 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/7252 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.bc93fec1f7de3683746e547023f9b133%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:  Tim Graham|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 Tim Graham):

 cpython fixed compatibility with sqlparse in
 https://hg.python.org/cpython/rev/1a2b8398f045/ so a new sqlparse release
 isn't needed and all tests are passing as of now.

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

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

Re: [Django] #27254: Detect web server context

[Django]

#27254: Detect web server context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Jimmy Merrild Krag):

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


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

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

Re: [Django] #27254: Detect web server context

[Django]

#27254: Detect web server context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Jimmy Merrild Krag):

 `python manage.py runserver` during development, but you make a valid
 point. Need to test if I can run my things there then, and then i guess
 developers must just run a management command manually to build
 documentation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.118106c6b2e5320db94d349a9d009be5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16679: Speed up signals by caching the receivers per sender (was: Speed up signals by caching the reveicers per sender)

[Django]

#16679: Speed up signals by caching the receivers per sender
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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
-+-

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.36e6ba23af1635a7373b2aaf6fdc860d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27254: Detect web server context

[Django]

#27254: Detect web server context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Aymeric Augustin):

 AFAIK the three supported ways to use Django are:

 1. running a WSGI server with the documented WSGI API
 2. running management commands with django-admin (or manage.py)
 3. `django.setup(); do_stuff()`

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.cc283776f353b6a59e0fdf48cc60585d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27254: Detect web server context

[Django]

#27254: Detect web server context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham):

 How else do you run a project?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.9df00b8eb49d8f2a6053733fd88c9a4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27254: Detect web server context (was: Detect web server command context)

[Django]

#27254: Detect web server context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.328d363b9641515e6c91a236a9cfbf67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27256: Change the selected attribute of select form tags to use HTML5 boolean syntax

[Django]

#27256: Change the selected attribute of select form tags to use HTML5 boolean
syntax
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * stage:  Unreviewed => Ready for checkin


Comment:

 Looks good!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.de50e3f5785fd07f6f6086c0fa8cf7d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27254: Detect web server command context

[Django]

#27254: Detect web server command context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Jimmy Merrild Krag):

 But what if the project is not served through wsgi?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.b24f2f26dc82a3950fef801fe0d10a50%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27254: Detect web server command context (was: Detect management command context)

[Django]

#27254: Detect web server command context
+--
 Reporter:  Jimmy Merrild Krag  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Uncategorized   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this 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.f11ed773eefd29cf847d4003917ecd07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.