Re: [Django] #18247: filter and Decimal equality doesn't work

[Django]

#18247: filter and Decimal equality doesn't work
-+-
 Reporter:  elmopl@… |Owner:  NEOatNHNG
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  decimal filter   | Triage Stage:  Accepted
  annotate having|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by NEOatNHNG):

 * has_patch:  0 => 1


Comment:

 On sqlite the SUM() of a decimal column doesn't have a NUMERIC type so
 when comparing it to a string literal (which a Decimal gets converted to
 in django) it is not compared as NUMERIC as may be expected but as
 something else (maybe string?).

 I added a CAST to NUMERIC type when using a SQL function that is expected
 to return a Decimal.

 All tests pass under SQLite.

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

Re: [Django] #24915: Stricter validation on session key

[Django]

#24915: Stricter validation on session key
-+-
 Reporter:  erikr|Owner:  sp1ky
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.sessions |  Version:  1.8
 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:"f4416b1a8b92e492707a6261b7a1132f8550457f" f4416b1]:
 {{{
 #!CommitTicketReference repository=""
 revision="f4416b1a8b92e492707a6261b7a1132f8550457f"
 Fixed #24915 -- Added stricter session key validation

 Changed _session_key attribute to a property and implemented basic
 validation in the setter. The session key must be 'truthy' and
 at least 8 characters long. Otherwise, the value is set to None.
 }}}

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

Re: [Django] #24859: UUIDField does not validate query value

[Django]

#24859: UUIDField does not validate query value
-+-
 Reporter:  cancan101|Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"20ff296cb15a53b8b9517a834688e57749b43e21" 20ff296]:
 {{{
 #!CommitTicketReference repository=""
 revision="20ff296cb15a53b8b9517a834688e57749b43e21"
 Fixed #24859 -- Made QuerySet.get() with UUIDField raise TypeError on bad
 value.

 For consistency with AutoField.
 }}}

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

Re: [Django] #24922: Templates: conflicting settings should emit a system check error

[Django]

#24922: Templates: conflicting settings should emit a system check error
-+-
 Reporter:  sergei-maertens  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  templates, system| Triage Stage:  Accepted
  check  |
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:"eaf4d8c0d85056c3481986fe092d5a8786bc4f26" eaf4d8c]:
 {{{
 #!CommitTicketReference repository=""
 revision="eaf4d8c0d85056c3481986fe092d5a8786bc4f26"
 Fixed #24922 -- Added system check for templates setting

 If `'loaders'` is present in the `TEMPLATES` options together with
 `APP_DIRS` set to `True`, the template engine raises an exception. This
 conflict is now detected by the system check templates.E001.
 }}}

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

Re: [Django] #12437: error_css_class should not override existing classes in html

[Django]

#12437: error_css_class should not override existing classes in html
-+-
 Reporter:  anonymous|Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  forms, errors| 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:"1884bf8e8e9fb3f9f44a9ec216aca96f63974268" 1884bf8e]:
 {{{
 #!CommitTicketReference repository=""
 revision="1884bf8e8e9fb3f9f44a9ec216aca96f63974268"
 Fixed #12437 -- Added css_classes to Form._html_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.e5a75581ff562f025df2a46ff3c70f75%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #56: Primary key columns should be UNSIGNED

[Django]

#56: Primary key columns should be UNSIGNED
-+-
 Reporter:  Manuzhai |Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by giuliettamasina):

 * owner:  christopherdcunha => giuliettamasina
 * cc: markus.magnuson@… (added)


Comment:

 I've rewritten pzinovkin's patch based on the
 [https://github.com/django/django/pull/1156 previous pull request] from
 gcc:

 https://github.com/alimony/django/compare/master...alimony:unsigned-
 primary-keys

 Did not open a pull request yet as it's not ready, most importantly the
 tests are failing:

 As far as I can see, the new `test_can_use_large_primary_keys` test can
 never have passed on postgres. There is no concept of unsigned in
 postgres, meaning a primary key bigger than 2147483648 only fits in a
 bigint/bigserial. The latter is used for the `AutoField` itself in this
 patch, but as someone pointed out, having a foreign key reference such
 large primary key fails.

 The updated `AutoField` in the patch
 [https://github.com/alimony/django/compare/master...alimony:unsigned-
 primary-keys#diff-bf776a3b8e5dbfac2432015825ef8afeR953 determines the
 field type] of a foreign key that references itself like this:

 {{{
 #!python
 def rel_db_type(self, connection):
 db_type = 'PositiveIntegerField' if self.unsigned else 'IntegerField'
 return self._internal_to_db_type(db_type, connection)
 }}}

 But both `PositiveIntegerField` and `IntegerField` resolve to `integer` in
 the case of postgres.

 Some ways it can ever do anything else, that I can think of now, are:

 1. Set `related_fields_match_type` to `True` for postgres.
 2. Make `PositiveIntegerField` mean a `bigint` for postgres.
 3. Make the `rel_db_type` method of the new `AutoField` do some special
 treatment to return e.g. `BigIntegerField` for postgres if `self.unsigned`
 is true.

 (The first two are of course out of the question.)

 I want to write proper tests for this patch to make sure everything
 behaves on every database, but I guess there needs to be some sort of
 consensus first on how to solve the above. And people with far more
 knowledge on Django than me will have to reach that consensus :)

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

Re: [Django] #24921: No Database objects can be created with set_autocommit(False)

[Django]

#24921: No Database objects can be created with set_autocommit(False)
-+-
 Reporter:  shabda   |Owner:  shabda
 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
-+-
Changes (by shaib):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


Comment:

 Accepting because the original analysis is correct and @carljm's comments
 are spot on.

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

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

Re: [Django] #22463: Inconsistent code style in HTML, JavaScript, and CSS files

[Django]

#22463: Inconsistent code style in HTML, JavaScript, and CSS files
-+-
 Reporter:  treyhunner   |Owner:
 Type:   |  treyhunner
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 oinopion):

 Looks like there is new PR for this:
 https://github.com/django/django/pull/4577

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

Re: [Django] #20436: Cleanup/Optimization of javascript code with JSLint in admin

[Django]

#20436: Cleanup/Optimization of javascript code with JSLint in admin
-+-
 Reporter:  galuszkak|Owner:  galuszkak
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by oinopion):

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


Comment:

 Closing as duplicate of #22463.

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

Re: [Django] #24890: Add warning to collectstatic when static files have clashing names

[Django]

#24890: Add warning to collectstatic when static files have clashing names
-+-
 Reporter:  giuliettamasina  |Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by giuliettamasina):

 I've updated the pull request according to code review. Should I squash
 all of the commits into a single one?

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

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

Re: [Django] #24946: Implement register_lookups

[Django]

#24946: Implement register_lookups
-+-
 Reporter:  coldmind |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by coldmind):

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


Comment:

 If it is good to go, I will implement this

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

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

[Django] #24946: Implement register_lookups

[Django]

#24946: Implement register_lookups
--+
 Reporter:  coldmind  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I think it will be good to implement `register_lookups` method to more DRY
 and prevent something like
 {{{
 SomeModel.register_lookup(L1)
 SomeModel.register_lookup(L2)
 SomeModel.register_lookup(L2)
 }}}

 So we will have
 {{{
 SomeModel.register_lookups([L1, L2, L3])
 }}}

 I think django code will become somewhat clearer.

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

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

Re: [Django] #24890: Add warning to collectstatic when static files have clashing names

[Django]

#24890: Add warning to collectstatic when static files have clashing names
-+-
 Reporter:  giuliettamasina  |Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  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 timgraham):

 * needs_better_patch:  0 => 1


Comment:

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

Re: [Django] #23190: Make paginator.page_range an iterator.

[Django]

#23190: Make paginator.page_range an iterator.
--+
 Reporter:  CollinAnderson|Owner:  zedr
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  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 zedr):

 * has_patch:  0 => 1


Comment:

 Pull request for this change: https://github.com/django/django/pull/4826

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

Re: [Django] #14196: Objects that come from something_set, should have their parent object filled in

[Django]

#14196: Objects that come from something_set, should have their parent object
filled in
-+-
 Reporter:  mark0978 |Owner:
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 mark0978):

 I'm betting over the course of the last 5 years this got fixed.  Might be
 a good idea to add the test code to prevent regression though.

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

Re: [Django] #22274: better tutorial for geodjango

[Django]

#22274: better tutorial for geodjango
-+
 Reporter:  digi_c@… |Owner:  sephii
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  1.6
 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 sephii):

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

[Django] #24945: Add support for fuzzystrmatch to contrib.postgres

[Django]

#24945: Add support for fuzzystrmatch to contrib.postgres
--+
 Reporter:  dracos|  Owner:
 Type:  New feature   | Status:  new
Component:  contrib.postgres  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 http://www.postgresql.org/docs/9.1/static/fuzzystrmatch.html has details
 of the extension, providing Levenshtein distance and soundex/metaphone
 functions.

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

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

Re: [Django] #24887: Remove one-arg limitation from django.db.models.aggregate

[Django]

#24887: Remove one-arg limitation from django.db.models.aggregate
-+-
 Reporter:  akaariai |Owner:  gchp
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by 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.64b509d5eee3aab51e030d86a00cb780%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24829: TemplateView raises unhandled ContentNotRenderedError error when used as error handler

[Django]

#24829: TemplateView raises unhandled ContentNotRenderedError error when used as
error handler
---+--
 Reporter:  nonZero|Owner:  ana-balica
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  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 timgraham):

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


Comment:

 Now has tests, but needs some other improvements.

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

Re: [Django] #12437: error_css_class should not override existing classes in html

[Django]

#12437: error_css_class should not override existing classes in html
-+-
 Reporter:  anonymous|Owner:
 |  giuliettamasina
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  forms, errors| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

[Django] #24944: Have password_reset pass extra_context to the email template rendering as well

[Django]

#24944: Have password_reset pass extra_context to the email template rendering 
as
well
---+
 Reporter:  twelveeighty   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 The password_reset function in auth.views currently allows for extra
 context parameters to be passed to the rendered reset password form, but
 it does not pass through those extra context parameters to the 'opt'
 dictionary used for the email template. This should be an easy feature to
 add: just before the form.save(), add the extra_context to the opts
 dictionary:

 {{{
 # inside the request.method == 'POST' and form.isValid() block:
 opts = {  ...  }
 if extra_context is not None:
opts.update(extra_context)
 form.save(**opts)
 }}}

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

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

Re: [Django] #21927: URL namespacing improvements

[Django]

#21927: URL namespacing improvements
--+
 Reporter:  aaugustin |Owner:  knbk
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (URLs)   |  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 timgraham):

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

Re: [Django] #24922: Templates: conflicting settings should emit a system check error

[Django]

#24922: Templates: conflicting settings should emit a system check error
-+-
 Reporter:  sergei-maertens  |Owner:  sergei-
 |  maertens
 Type:  Bug  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  templates, system| Triage Stage:  Accepted
  check  |
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:

 Reviewed the [https://github.com/django/django/pull/4773 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/073.adc3b3f80844c482740b5c1628183108%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17375: 'makemessages' ignores plural from 'blocktrans'

[Django]

#17375: 'makemessages' ignores plural from 'blocktrans'
-+-
 Reporter:  ahagenbruch  |Owner:
 |  sergeykolosov
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 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 sergeykolosov):

 * cc: m17.admin@… (added)
 * owner:  pigletto => sergeykolosov


Comment:

 Working on it.

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

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

Re: [Django] #24915: Stricter validation on session key

[Django]

#24915: Stricter validation on session key
-+-
 Reporter:  erikr|Owner:  sp1ky
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.sessions |  Version:  1.8
 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 carljm):

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

Re: [Django] #24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()`

[Django]

#24877: Exceptions in renderizable responses are not handled by Middleware's
`process_exception()`
---+
 Reporter:  Kronuz |Owner:  sephii
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 timgraham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #24935: refactor conditional GET handling

[Django]

#24935: refactor conditional GET handling
--+
 Reporter:  syphar|Owner:  syphar
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  HTTP handling |  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 timgraham):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #24931: 404 error for "Views by namespace admin" at Admin Docs

[Django]

#24931: 404 error for "Views by namespace admin" at Admin Docs
---+
 Reporter:  girishkumarkh  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Admin, AdminDocs   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.b6ac2346358d099dce2d3d92d14dffd0%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:  peterfarrell   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 [https://groups.google.com/d/topic/django-
 developers/WrnhmTyLHuY/discussion thread on django-developers].

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

Re: [Django] #24906: ResolverMatch.app_name doesn't contain full application namespace for nested namespaces

[Django]

#24906: ResolverMatch.app_name doesn't contain full application namespace for
nested namespaces
-+
 Reporter:  knbk |Owner:  knbk
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"bc77eb6d0858652e197c08c299efaeb06c51efee" bc77eb6]:
 {{{
 #!CommitTicketReference repository=""
 revision="bc77eb6d0858652e197c08c299efaeb06c51efee"
 Fixed #24906 -- Fixed ResolverMatch.app_name for nested namespaces.

 Set ResolverMatch.app_name to the full path of nested application
 namespaces.
 }}}

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

Re: [Django] #24690: Warn about mutable defaults with ArrayField

[Django]

#24690: Warn about mutable defaults with ArrayField
-+-
 Reporter:  redbeard0x0a |Owner:
 Type:   |  marissazhou
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField postgres  | 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


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

Re: [Django] #24929: permission_required decorator should take any iterable of permissions

[Django]

#24929: permission_required decorator should take any iterable of permissions
-+-
 Reporter:  raphaelm |Owner:  raphaelm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #24935: refactor conditional GET handling

[Django]

#24935: refactor conditional GET handling
-+-
 Reporter:  syphar   |Owner:  syphar
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  HTTP handling|  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 syphar):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => syphar
 * needs_docs:   => 0
 * 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/064.259dd817ffee243a54c90f05e17b0133%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24126: Consider deprecating the current_app argument of auth views

[Django]

#24126: Consider deprecating the current_app argument of auth views
--+
 Reporter:  aaugustin |Owner:  lukawoj
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  current_app   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #24943: Update contributing tutorial to use virtualenv

[Django]

#24943: Update contributing tutorial to use virtualenv
-+-
 Reporter:  timgraham|Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 giuliettamasina):

 * status:  new => assigned
 * owner:  nobody => giuliettamasina
 * cc: markus.magnuson@… (added)


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

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

Re: [Django] #24767: Add GREATEST and LEAST Query Expressions

[Django]

#24767: Add GREATEST and LEAST Query Expressions
-+-
 Reporter:  Ian-Foote|Owner:  Ian-Foote
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 The new tests are not passing on older versions of MySQL which don't
 support microseconds (see [http://djangoci.com/job/django-master/
 Jenkins]).

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

Re: [Django] #22274: better tutorial for geodjango

[Django]

#22274: better tutorial for geodjango
-+
 Reporter:  digi_c@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.6
 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):

 You are of course welcome to work on this, and your summary looks
 promising. Feel free to assign the ticket to you as soon as you start
 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/073.674d58ac7366a6a399b86952a8bcf73a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24910: createsuperuser in interactive mode assumes USERNAME_FIELD is unique

[Django]

#24910: createsuperuser in interactive mode assumes USERNAME_FIELD is unique
-+-
 Reporter:  carljm   |Owner:
 |  alasdairnicol
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.8
 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:"1ea87c8c7974acb5fa795362253c61b38f3cb137" 1ea87c8]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ea87c8c7974acb5fa795362253c61b38f3cb137"
 Fixed #24910 -- Added createsuperuser support for non-unique
 USERNAME_FIELDs

 Clarified docs to say that a non-unique USERNAME_FIELD is permissable
 as long as the custom auth backend can support it.
 }}}

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

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

Re: [Django] #23516: ifchanged no longer works within an included template

[Django]

#23516: ifchanged no longer works within an included template
-+-
 Reporter:  dracos   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.7
 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:"a391b17ad24bc5f255a3928c23c158c79004c656" a391b17]:
 {{{
 #!CommitTicketReference repository=""
 revision="a391b17ad24bc5f255a3928c23c158c79004c656"
 Fixed #23516 -- Added caching of include tag Template objects

 This also speeds up for loops that render the same template
 multiple times.
 }}}

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

Re: [Django] #24744: Missing relabeled_clone methods are causing fails in subqueries

[Django]

#24744: Missing relabeled_clone methods are causing fails in subqueries
-+-
 Reporter:  mrAdm|Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  hstore   | 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:"b4b13759f82e9e09951bb72875b1c6e384dca6a9" b4b1375]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4b13759f82e9e09951bb72875b1c6e384dca6a9"
 [1.8.x] Fixed #24744 - Fixed relabeled_clone for the Transform

 Backport of 08232ef84d4959826ad5136f183c9fc5bedf0599 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/063.addeb36a7c113568b7399f2c172fd7ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24744: Missing relabeled_clone methods are causing fails in subqueries

[Django]

#24744: Missing relabeled_clone methods are causing fails in subqueries
-+-
 Reporter:  mrAdm|Owner:  coldmind
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  hstore   | 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:"08232ef84d4959826ad5136f183c9fc5bedf0599" 08232ef]:
 {{{
 #!CommitTicketReference repository=""
 revision="08232ef84d4959826ad5136f183c9fc5bedf0599"
 Fixed #24744 - Fixed relabeled_clone for the Transform
 }}}

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

Re: [Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

[Django]

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and 
not
just methods
-+-
 Reporter:  coolRR   |Owner:  m_sha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 mjtamlyn):

 Stylistically, I'd say a property is wrong for that use case, I don't like
 properties which do round trips to the database as when reading the code
 it looks like an attribute. That said...

 The implementation is straightforwards, we can use
 https://docs.python.org/3/library/inspect.html#inspect.isdatadescriptor

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 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 Tim Graham ):

 In [changeset:"f4c09d3e4273ac8946d6da1f4ee785ddb378ca19" f4c09d3]:
 {{{
 #!CommitTicketReference repository=""
 revision="f4c09d3e4273ac8946d6da1f4ee785ddb378ca19"
 [1.8.x] Fixed #24882 -- Documented Migration.run_before

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

Re: [Django] #24882: Add documentation for Migration.run_before

[Django]

#24882: Add documentation for Migration.run_before
-+-
 Reporter:  coolRR   |Owner:
 Type:   |  mcbhenwood
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 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:"dee1bcd08a013ba5ffd8d1ec9b6628702f755066" dee1bcd0]:
 {{{
 #!CommitTicketReference repository=""
 revision="dee1bcd08a013ba5ffd8d1ec9b6628702f755066"
 Fixed #24882 -- Documented Migration.run_before
 }}}

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

Re: [Django] #24937: DateTimeRangeField.value_to_string raises TypeError

[Django]

#24937: DateTimeRangeField.value_to_string raises TypeError
--+
 Reporter:  unklphil  |Owner:  dracos
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Matthew Somerville ):

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


Comment:

 In [changeset:"2926559cce34e48efb4b073721926d737e372dd3" 2926559c]:
 {{{
 #!CommitTicketReference repository=""
 revision="2926559cce34e48efb4b073721926d737e372dd3"
 Fixed #24937 -- fix serialization of Date(Time)RangeField.

 Use the DjangoJSONEncoder so that datetime and date are encoded
 appropriately.
 }}}

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

Re: [Django] #24937: DateTimeRangeField.value_to_string raises TypeError

[Django]

#24937: DateTimeRangeField.value_to_string raises TypeError
--+
 Reporter:  unklphil  |Owner:  dracos
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Marc Tamlyn ):

 In [changeset:"d58816bd6bf93a878085d35d3ed4609efeb0acfa" d58816b]:
 {{{
 #!CommitTicketReference repository=""
 revision="d58816bd6bf93a878085d35d3ed4609efeb0acfa"
 Merge pull request #4818 from dracos/24937-ranging-to-victory

 Fixed #24937 -- fix serialization of Date(Time)RangeField.
 }}}

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

[Django] #24943: Update contributing tutorial to use virtualenv

[Django]

#24943: Update contributing tutorial to use virtualenv
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 We should assume Python 3 which (usually) includes virtualenv. There are
 some caveats, but many can be adapted from the
 [http://tutorial.djangogirls.org/en/django_installation/index.html Django
 Girls tutorial].

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

Re: [Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

[Django]

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and 
not
just methods
-+-
 Reporter:  coolRR   |Owner:  m_sha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 coolRR):

 I'm not really understanding what the implementation problem is. If you're
 going over all the members of the `QuerySet` class, you can see which are
 properties and then copy them. So what's the problem?

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

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

Re: [Django] #24907: Update the contributing tutorial to use a more recent patch

[Django]

#24907: Update the contributing tutorial to use a more recent patch
-+-
 Reporter:  giuliettamasina  |Owner:
 Type:   |  giuliettamasina
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  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:"3fd754f12df42d173b6e9a93e7c32f8f5be55e7f" 3fd754f1]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fd754f12df42d173b6e9a93e7c32f8f5be55e7f"
 Fixed #24907 -- Updated contributing tutorial with a more recent example
 ticket.
 }}}

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

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

Re: [Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

[Django]

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and 
not
just methods
-+-
 Reporter:  coolRR   |Owner:  m_sha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 MarkusH):

 I have no idea how we'd be able to only take those properties and no
 attributes or other properties, except for requiring an attribute on the
 property. But I think just using a function without any arguments is just
 fine.

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

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

Re: [Django] #24942: Update installation instructions of spatial libraries

[Django]

#24942: Update installation instructions of spatial libraries
-+-
 Reporter:  sephii   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 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 sephii):

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


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

Re: [Django] #24942: Update installation instructions of spatial libraries

[Django]

#24942: Update installation instructions of spatial libraries
-+-
 Reporter:  sephii   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by sephii):

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


Comment:

 My bad, it looks like this is already documented. I still think it should
 be more emphasized though. Maybe the source installation should be moved
 to specific part in the docs to keep the basic installation instructions
 light. This could be fixed in #22274.

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

Re: [Django] #22274: better tutorial for geodjango

[Django]

#22274: better tutorial for geodjango
-+
 Reporter:  digi_c@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.6
 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 sephii):

 * cc: sephii (added)


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

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

Re: [Django] #24908: Overridden field in modelform used in modeladmin which name is returned by get_readonly_fields

[Django]

#24908: Overridden field in modelform used in modeladmin which name is returned 
by
get_readonly_fields
---+
 Reporter:  jpic   |Owner:
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.8
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by jpic):

 I got a bit confused by another problem and the PR above has become
 unrelated.

 The new PR which fixes the bug in ModelAdmin is:
 https://github.com/django/django/pull/4822 (I wish I had contributed
 something more elegant lol)

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

Re: [Django] #22274: better tutorial for geodjango

[Django]

#22274: better tutorial for geodjango
-+
 Reporter:  digi_c@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  1.6
 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 sephii):

 I would be happy to work on this.

 Here are the things I think could be improved:

 * Create an easier tutorial that doesn't require extensive comprehension
 of world borders, ogrinfo etc that are quite specific. We could go on
 creating an application that defines models with simple coordinates or
 shapes and calculates distances between objects. We could make a tutorial
 that looks like the Django tutorial (1. creating models, 2. the geo admin,
 3. using geo data in views/templates/forms).
 * Simplify GIS installation of GIS libraries (see #24942)
 * Make a better explanation of what GDAL and GEOS are (if the docs are
 aimed to lambda users, we can assume that the following could be explained
 better: "GEOS stands for Geometry Engine - Open Source, and is a C++
 library, ported from the Java Topology Suite. GEOS implements the OpenGIS
 Simple Features for SQL spatial predicate functions and spatial operators.
 GEOS, now an OSGeo project, was initially developed and maintained by
 Refractions Research of Victoria, Canada.")
 * Reorganize/simplify the TOC (GeoDjango installation is placed after the
 GeoDjango tutorial, although you first need to go through the installation
 process to proceed with the tutorial). Also this long list of topics is
 far from being as clear as Django's docs TOC
 * This one might be more of a detail but I would use native types (eg.
 Point) instead of the GEOSGeometry constructor, and try to be consistent
 along the tutorial

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

[Django] #24942: Update installation instructions of spatial libraries

[Django]

#24942: Update installation instructions of spatial libraries
--+
 Reporter:  sephii|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  GIS   |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The installation instructions in the GeoDjango docs
 (https://docs.djangoproject.com/en/1.8/ref/contrib/gis/install/geolibs/
 and https://docs.djangoproject.com/en/1.8/ref/contrib/gis/install/) could
 be vastly simplified since most of the libraries (geos, gdal, proj4,
 spatialite) are now packaged at least in Ubuntu and Debian and thus don't
 require an installation from source.

 I guess this would contribute to #22274.

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

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

Re: [Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

[Django]

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and 
not
just methods
-+-
 Reporter:  coolRR   |Owner:  m_sha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 coolRR):

 Carl: Yes, that's my intention.

 mjtamlyn: Okay, here's a concrete use case. I have a model `CreditCard`
 and a corresponding queryset `CreditCardQuerySet`. I want to have a
 property `expired` on `CreditCardQuerySet` so I could filter to expired
 credit cards like `CreditCard.objects.expired`. (Assuming there isn't a
 straightforward query to do that.) I could do it as a method but I always
 prefer using a `property` when there aren't any arguments.

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

Re: [Django] #24796: Middleware ordering hints don't mention SecurityMiddleware

[Django]

#24796: Middleware ordering hints don't mention SecurityMiddleware
-+-
 Reporter:  TaymonB  |Owner:
 Type:   |  marissazhou
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by marissazhou):

 Fixed the ticket
 https://github.com/django/django/pull/4814

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

Re: [Django] #24894: Add CURRENT_TIMESTAMP function to contrib.postgres

[Django]

#24894: Add CURRENT_TIMESTAMP function to contrib.postgres
--+--
 Reporter:  adamchainz|Owner:  adamchainz
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by adamchainz):

 Expressions as defaults don't work, they would need at least #24509 (Allow
 Expressions when saving new models) to be done. I've had a look at it and
 it's quite complicated.

 I'll add the document pointers to the patch now, it was originally there
 when this was part of the #24866 patch but I forgot to add it during
 rebase.

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