Re: [Django] #26485: Small Type in tutorial07

[Django]

#26485: Small Type in tutorial07
+--
 Reporter:  denisra |Owner:  denisra
 Type:  Bug |   Status:  assigned
Component:  Documentation   |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  typo, tutorial  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by denisra):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * owner:   => denisra
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #26485: Small Type in tutorial07

[Django]

#26485: Small Type in tutorial07
---+
 Reporter:  denisra|  Owner:
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:  typo, tutorial
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 There is a small type in the paragraph below:

 You’ll follow this pattern – create a model admin class, then pass it as
 the second argument to admin.site.register() – any time you need to change
 the admin options for '''an''' model.

 Which should read: '''a''' model.

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

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

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

[Django]

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

 I can confirm marfire's findings.

 1/ For example even with this router applied:

 {{{
 class testerouter(object):
 def allow_migrate(self, db, app_label, model_name=None, **hints):
 return False
 }}}


 And then executing:
 {{{
 migrate --database=replica
 }}}
 All apps and models migrations get applied to this replica database, while
 according to the router nothing should happen at all.

 2/ From the documentation it is not clear whether it is possible to
 isolate certain models from certain databases, or whether isolation can
 only be done on the app-level. From the description in the documentation,
 it seems possible to use the model_name argument for this, but by the way
 django stores its migrations, I don't see how that could work.

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

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

Re: [Django] #26359: explain dual ticket tracking system

[Django]

#26359: explain dual ticket tracking system
--+
 Reporter:  beckastar |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by kaifeldhoff):

 * cc: kai@… (added)
 * owner:  kaifeldhoff =>
 * status:  assigned => new


Comment:

 Maybe someone has a better idea to solve 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/067.24762df6bd4e7137780c898d356ed066%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

[Django]

#26484: Add a helpful message in manage.py when Django cannot be imported
-+-
 Reporter:  timgraham|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 I [https://github.com/django/django/pull/6438 implemented Shai's
 suggestion] to catch the original exception, then try `import django` and
 display the helpful message if that fails or reraise the original
 exception if not.

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

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

Re: [Django] #25847: Make User.is_authenticated() and User.is_anonymous() "callable properties"

[Django]

#25847: Make User.is_authenticated() and User.is_anonymous() "callable 
properties"
---+
 Reporter:  skorokithakis  |Owner:  jlaine
 Type:  New feature|   Status:  closed
Component:  contrib.auth   |  Version:  1.9
 Severity:  Normal |   Resolution:  fixed
 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 ):

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


Comment:

 In [changeset:"c1aec0feda73ede09503192a66f973598aef901d" c1aec0fe]:
 {{{
 #!CommitTicketReference repository=""
 revision="c1aec0feda73ede09503192a66f973598aef901d"
 Fixed #25847 -- Made User.is_(anonymous|authenticated) properties.
 }}}

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

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

[Django] #26484: Add a helpful message in manage.py when Django cannot be imported

[Django]

#26484: Add a helpful message in manage.py when Django cannot be imported
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   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 |
+
 As discussed [https://github.com/django/django/pull/6314 on a pull
 request] and [https://groups.google.com/d/topic/django-
 developers/aXF1j55hb2Q/discussion on django-developers].

 The first commit is 724a279849a5cd09cdb5ef201fe6958a4c26fe73 but the issue
 is reopened after some concerns about the possibility of masking imports
 on Python 2.

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

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

Re: [Django] #26390: order_by('?') unexpectedly breaking queryset aggregation

[Django]

#26390: order_by('?') unexpectedly breaking queryset aggregation
-+-
 Reporter:  uranusjr |Owner:  uranusjr
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Some test additions are still needed.

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

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

Re: [Django] #26479: Add "is not" comparison to the if template tag

[Django]

#26479: Add "is not" comparison to the if template tag
-+-
 Reporter:  alasdairnicol|Owner:  alasdairnicol
 Type:  New feature  |   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:"c16b9dd8e0ae757616e9accbaffecc521191ee98" c16b9dd]:
 {{{
 #!CommitTicketReference repository=""
 revision="c16b9dd8e0ae757616e9accbaffecc521191ee98"
 Fixed #26479 -- Added 'is not' operator to the if tag.
 }}}

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

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

Re: [Django] #26085: contenttypes.views.shortcut fails if a FK to Site returns None

[Django]

#26085: contenttypes.views.shortcut fails if a FK to Site returns None
--+
 Reporter:  jaap3 |Owner:  jibaku
 Type:  Bug   |   Status:  assigned
Component:  contrib.contenttypes  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26145: Made the debug context processor return queries for all databases

[Django]

#26145: Made the debug context processor return queries for all databases
-+-
 Reporter:  inoks|Owner:
 Type:   |  MounirMesselmeni
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sql_queries  | 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:"03e1cc930c6a5fbe993fb120e4403f3dd8a7c211" 03e1cc93]:
 {{{
 #!CommitTicketReference repository=""
 revision="03e1cc930c6a5fbe993fb120e4403f3dd8a7c211"
 Fixed #26145 -- Made debug context processor return queries for all
 databases.
 }}}

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

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

Re: [Django] #26466: set_language with next unset and a urlencoded HTTP_REFERER fails redirection

[Django]

#26466: set_language with next unset and a urlencoded HTTP_REFERER fails
redirection
--+
 Reporter:  miikkas   |Owner:  miikkas
 Type:  Bug   |   Status:  closed
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 Keywords:  set_language  | 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:"9e3f141701b96b6974b3386f83dc76e70a41377d" 9e3f1417]:
 {{{
 #!CommitTicketReference repository=""
 revision="9e3f141701b96b6974b3386f83dc76e70a41377d"
 Fixed #26466 -- Added HTTP_REFERER decoding to i18n set_language() view.
 }}}

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

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

Re: [Django] #26401: Allow auth machinery to be used without installing auth app

[Django]

#26401: Allow auth machinery to be used without installing auth app
--+
 Reporter:  satchamo  |Owner:  satchamo
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  auth  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_tests:  0 => 1


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

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

Re: [Django] #26403: "Invalid block tag" message is English except for one word

[Django]

#26403: "Invalid block tag" message is English except for one word
--+
 Reporter:  interDist |Owner:  amureki
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Template system   |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  1
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f8bbba80607435c68f34207bc1e9a133a3f9ffee" f8bbba80]:
 {{{
 #!CommitTicketReference repository=""
 revision="f8bbba80607435c68f34207bc1e9a133a3f9ffee"
 Fixed #26403 -- Removed translated content in "Invalid block tag" message.
 }}}

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

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

Re: [Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

[Django]

#26455: Add lookups and database functions to check for valid geometries and
repairing them.
-+-
 Reporter:  yellowcap|Owner:  yellowcap
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  isvalid, makevalid,  | Triage Stage:  Ready for
  valid, geometry|  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:"c12a00e554c8b4b93931b520bb94a479c5ba8706" c12a00e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c12a00e554c8b4b93931b520bb94a479c5ba8706"
 Fixed #26455 -- Allowed filtering and repairing invalid geometries.

 Added the IsValid and MakeValid database functions, and the isvalid
 lookup,
 all for PostGIS.

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

Re: [Django] #26464: Add a link to the OWASP Top 10 in "Security in Django" doc

[Django]

#26464: Add a link to the OWASP Top 10 in "Security in Django" doc
-+-
 Reporter:  CrazyPython  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  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 timgraham):

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


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

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

Re: [Django] #26479: Add "is not" comparison to the if template tag

[Django]

#26479: Add "is not" comparison to the if template tag
-+-
 Reporter:  alasdairnicol|Owner:  alasdairnicol
 Type:  New feature  |   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
-+-
Changes (by alasdairnicol):

 * has_patch:  0 => 1


Comment:

 Pull request https://github.com/django/django/pull/6436/files

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

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

Re: [Django] #26145: Made the debug context processor return queries for all databases

[Django]

#26145: Made the debug context processor return queries for all databases
-+-
 Reporter:  inoks|Owner:
 Type:   |  MounirMesselmeni
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sql_queries  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MounirMesselmeni):

 * has_patch:  0 => 1


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

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

Re: [Django] #26464: Add a link to the OWASP Top 10 in "Security in Django" doc

[Django]

#26464: Add a link to the OWASP Top 10 in "Security in Django" doc
-+-
 Reporter:  CrazyPython  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  1.9
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"bdbfa1b1f81536642cb4518877bdb4ecd18e83b7" bdbfa1b1]:
 {{{
 #!CommitTicketReference repository=""
 revision="bdbfa1b1f81536642cb4518877bdb4ecd18e83b7"
 [1.9.x] Refs #26464 -- Added a link to OWASP Top 10 in security topic
 guide.

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

Re: [Django] #26464: Add a link to the OWASP Top 10 in "Security in Django" doc

[Django]

#26464: Add a link to the OWASP Top 10 in "Security in Django" doc
-+-
 Reporter:  CrazyPython  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  1.9
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"f6ca63a9f8b3d030097135e096c1041e09c29fd9" f6ca63a9]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6ca63a9f8b3d030097135e096c1041e09c29fd9"
 Refs #26464 -- Added a link to OWASP Top 10 in security topic guide.
 }}}

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

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

Re: [Django] #26145: Made the debug context processor return queries for all databases

[Django]

#26145: Made the debug context processor return queries for all databases
-+-
 Reporter:  inoks|Owner:
 Type:   |  MounirMesselmeni
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sql_queries  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MounirMesselmeni):

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


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

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

Re: [Django] #26451: extend Paginator to support infinite pagination and postgres estimated count

[Django]

#26451: extend Paginator to support infinite pagination and postgres estimated
count
--+
 Reporter:  syphar|Owner:  syphar
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  1.9
 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 syphar):

 thanks claudep for the mysql link, codingjoe and me had the same idea
 about adding this to the db-backends and queryset, and then (optionally)
 using it for the paginator

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

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

Re: [Django] #26451: extend Paginator to support infinite pagination and postgres estimated count

[Django]

#26451: extend Paginator to support infinite pagination and postgres estimated
count
--+
 Reporter:  syphar|Owner:  syphar
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  1.9
 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 claudep):

 For MySQL, see also http://django-
 mysql.readthedocs.org/en/latest/queryset_extensions.html#approximate-
 counting
 We might create a separate ticket to add the approximate count to the
 queryset API.

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

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

Re: [Django] #26403: "Invalid block tag" message is English except for one word

[Django]

#26403: "Invalid block tag" message is English except for one word
--+
 Reporter:  interDist |Owner:  amureki
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Template system   |  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:  1 |UI/UX:  1
--+
Changes (by claudep):

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


Comment:

 The `Ready for checkin` flag is not supposed to be set by the patch
 author, but by a reviewer.

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

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

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField

[Django]

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField
--+
 Reporter:  MarysiaLowas  |Owner:  yakky
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 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 yakky):

 The behavior described in this ticket is due to this deprecation
 https://github.com/django/django/blob/stable/1.8.x/django/forms/fields.py#L507
 , thus it's an intended behavior
 The only possible fix here is to document better how to use
 `formfield_overrides` for `AdminSplitDateTime`
 `AdminSplitDateTime` per se it's not documented as is considered part of
 the private API
 We can document `SplitDateTimeWidget` but this won't solve this ticket
 anyway

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

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