Re: [Django] #28579: Clarify 2.0 is just a new version numbering scheme

[Django]

#28579: Clarify 2.0 is just a new version numbering scheme
-+-
 Reporter:  Collin Anderson  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  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 Collin Anderson):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #28583: test_timezone.py test failure on Django 1.9 with Python 3.6 (was: test_timezone.py)

[Django]

#28583: test_timezone.py test failure on Django 1.9 with Python 3.6
-+-
 Reporter:  Matthew Brown|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Utilities|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  timezone.py  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * component:  Uncategorized => Utilities
 * resolution:   => invalid


Comment:

 The Django 1.9 branch isn't compatible with Python 3.6 (see #27025). Also,
 it's [https://www.djangoproject.com/download/#supported-versions end of
 life as of April 2017].

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

[Django] #28583: test_timezone.py

[Django]

#28583: test_timezone.py
-+-
   Reporter:  Matthew|  Owner:  nobody
  Brown  |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  1.9
  Uncategorized  |
   Severity:  Normal |   Keywords:  timezone.py
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 FAIL: test_make_aware_pytz (utils_tests.test_timezone.TimezoneTests)

 Traceback (most recent call last):
 File "/Users/matthewbrown/django/tests/utils_tests/test_timezone.py", line
 162, in test_make_aware_pytz
 timezone.make_naive(datetime.datetime(2011, 9, 1, 12, 20, 30), CET)
 AssertionError: ValueError not raised

 received the error message above and once i removed the #with
 self.assertRaisesMessage(ValueError, 'make_naive() cannot be applied to a
 naive datetime'): I did not receive the error message or failure from
 ./runtests.py

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

Re: [Django] #27846: refresh_from_db() doesn't clear reverse OneToOneFields

[Django]

#27846: refresh_from_db() doesn't clear reverse OneToOneFields
-+-
 Reporter:  Keith Hostetler  |Owner:  Paulo
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  refresh_from_db  | Triage Stage:  Accepted
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Berker Peksag):

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

Re: [Django] #28567: Set Language Redirect View -> 404 if prefix_default_language=False

[Django]

#28567: Set Language Redirect View -> 404 if prefix_default_language=False
-+-
 Reporter:  George Tantiras  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.11
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by George Tantiras):

 I have created a relevant [https://github.com/django/django/pull/9058 pull
 request] which includes the above tests.

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

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

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
+--
 Reporter:  karyon  |Owner:  Tim Martin
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.11
 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 karyon):

 sorry for the confusion!

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

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
+--
 Reporter:  karyon  |Owner:  Tim Martin
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Martin):

 * owner:  nobody => Tim Martin
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 You're right, I assumed that the code you gave was the reproduction case
 and I didn't see that the `unique=True` is commented out. I can confirm
 that I can reproduce the problem now, with the master branch and with
 stable branches back to 1.8. I'll investigate further.

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

Re: [Django] #28570: setting SRID in GEOSGeometry.clone() could be avoided for better performance on GEOS 3.3.1+

[Django]

#28570: setting SRID in GEOSGeometry.clone() could be avoided for better
performance on GEOS 3.3.1+
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  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 Sergey Fedoseev):

 [https://github.com/django/django/pull/9056 PR]

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

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

Re: [Django] #28560: distinct() on ordered queryset with restricted list of columns returns incorrect result

[Django]

#28560: distinct() on ordered queryset with restricted list of columns returns
incorrect result
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  distinct values  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
+--
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by karyon):

 the sqlite failure is described here:
 https://code.djangoproject.com/ticket/28541

 have you added unique=True to the migration? without that the error does
 not appear.

 i'll experiment with psycop versions and will provide a pip freeze
 tomorrow.

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

Re: [Django] #28392: GIS's WKT regex doesn't match large scientific notation

[Django]

#28392: GIS's WKT regex doesn't match large scientific notation
--+
 Reporter:  Greg Larmore  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  GIS   |  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 Sergey Fedoseev):

 * cc: Sergey Fedoseev (added)
 * needs_tests:  1 => 0


Comment:

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

Re: [Django] #28582: Tutorial 01 and 02 cleanup suggestions

[Django]

#28582: Tutorial 01 and 02 cleanup suggestions
--+
 Reporter:  ImmaSix   |Owner:  ImmaSix
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.11
 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 Claude Paroz):

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

Re: [Django] #28581: Pagination topic docs need a little restructuring

[Django]

#28581: Pagination topic docs need a little restructuring
--+
 Reporter:  luto  |Owner:  luto
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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 Claude Paroz):

 * type:  Bug => Cleanup/optimization
 * 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/062.0d22892b008e75b144b6924fdf09709e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25650: `GEOSGeomerty.__eq__` should use `equals` not `equals_exact`

[Django]

#25650: `GEOSGeomerty.__eq__` should use `equals` not `equals_exact`
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Sergey Fedoseev):

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


Comment:

 After a while I think the current implementation is OK because if we want
 to compare "spatially" we need to transform both geometries to the SRID
 which will inevitably lead to computational error.

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

Re: [Django] #28497: QuerySet.filter() with a sliced QuerySet crashes

[Django]

#28497: QuerySet.filter() with a sliced QuerySet crashes
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   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 Sergey Fedoseev):

 Replying to [comment:5 Tim Graham]:
 > It's not clear to me why this shouldn't be allowed.

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

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

[Django]

#28542: migration that introduces uuid field is not reversible with unique=True
+--
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 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 Tim Martin):

 * cc: Tim Martin (added)


Comment:

 I can't reproduce this using django branch `stable/1.11.x` or `master`.
 With sqlite, the migration fails to apply forwards, with the error:

 {{{
 django.db.utils.OperationalError: duplicate column name: id
 }}}

 AFAICT, this is hitting after it has deleted the `id` field. I think this
 is happening because in sqlite you can't actually remove the `id` field
 from a table?

 With Postgres 9.6.5 and Django `stable/1.11.x` I can apply the migration
 forwards and backwards without a problem.

 Can you provide more details about the environment where this is failing?
 Perhaps the output of `pip freeze` so I can get the same versions of
 psycopg2 etc.

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

Re: [Django] #28582: Tutorial 01 and 02 cleanup suggestions

[Django]

#28582: Tutorial 01 and 02 cleanup suggestions
-+-
 Reporter:  ImmaSix  |Owner:  ImmaSix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 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 Daniele Procida):

 * cc: Daniele Procida (added)


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

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

Re: [Django] #28582: Tutorial 01 and 02 cleanup suggestions (was: Tutorial contains unnecessary explanation)

[Django]

#28582: Tutorial 01 and 02 cleanup suggestions
-+-
 Reporter:  ImmaSix  |Owner:  ImmaSix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

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

Re: [Django] #28582: Tutorial contains unnecessary explanation

[Django]

#28582: Tutorial contains unnecessary explanation
-+-
 Reporter:  ImmaSix  |Owner:  ImmaSix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 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
-+-
Description changed by ImmaSix:

Old description:

> working at write the docs conference with Daniele Procida. Work in
> progress, will add more notes here.
>
> * tutorial 01: "changing the port" block explanation not necessary -
> beginning users can skip this,
> * tutorial 01: "Projects vs. apps" block explanation not necessary.
> * tutorial 01: mysite/urls.py code snippets: the two code snippets are
> different from each other. The second adds not only the `include` as
> described in the tutorials, but also adds more lines that are not
> explained.
> * tutorial 01: explanation for `include()` a bit too detailed. A part of
> it can move to the `include()` reference if it isn't already there.
> * tutorial 01: a bit of explanation about the 'url()'  arguments is well-
> suited. Some remarks:
>
>   1. explanation about performance of regular expressions is not
> necessary.
>   2. kwargs and name are not used in the example and are optional: can
> probably be removed.
>
> * tutorial 02: for a tutorial, it is ok to stick to the SQLite database.
> Any information about settings for other databases can be moved away. If
> it is important to set the database correctly this early in the project,
> I'd suggest to make a how-to and create a link to it.
> * tutorial 02: The content of the **philosophy** block might be moved to
> the main text, so that the main text is not interrupted by the block.
> Explaining why we create a model is important enough. If the explanation
> can be a bit shorter, that would be great.
> * tutorial 02: block bypassing manage.py is not necessary.
> * tutorial 02: the line {{{@python_2_unicode_compatible  # only if you
> need to support Python 2}}} comes a bit out of the blue. How important is
> this line?

New description:

 working at write the docs conference with Daniele Procida. Work in
 progress, will add more notes here.

 * tutorial 01: "changing the port" block explanation not necessary -
 beginning users can skip this,
 * tutorial 01: "Projects vs. apps" block explanation not necessary.
 * tutorial 01: mysite/urls.py code snippets: the two code snippets are
 different from each other. The second adds not only the `include` as
 described in the tutorials, but also adds more lines that are not
 explained.
 * tutorial 01: explanation for `include()` a bit too detailed. A part of
 it can move to the `include()` reference if it isn't already there.
 * tutorial 01: a bit of explanation about the 'url()'  arguments is well-
 suited. Some remarks:

   1. explanation about performance of regular expressions is not
 necessary.
   2. kwargs and name are not used in the example and are optional: can
 probably be removed.

 * tutorial 02: for a tutorial, it is ok to stick to the SQLite database.
 Any information about settings for other databases can be moved away. If
 it is important to set the database correctly this early in the project,
 I'd suggest to make a how-to and create a link to it.
 * tutorial 02: The content of the **philosophy** block might be moved to
 the main text, so that the main text is not interrupted by the block.
 Explaining why we create a model is important enough. If the explanation
 can be a bit shorter, that would be great.
 * tutorial 02: block bypassing manage.py is not necessary.
 * tutorial 02: the line {{{@python_2_unicode_compatible  # only if you
 need to support Python 2}}} comes a bit out of the blue. How important is
 this line?
 * tutorial 02: second time running `python manage.py shell` block is quite
 long. Maybe split it into multiple blocks and add explanation in between.

--

-- 
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 

Re: [Django] #28574: Add a QuerySet.explain() method

[Django]

#28574: Add a QuerySet.explain() method
-+-
 Reporter:  Tom  |Owner:  Tom
 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 Tom):

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

 On any select queryset you can do `print(qs.explain())` and it will print
 the databases EXPLAIN output. There is a `verbose` and a `format` flag for
 backends that support it, e.g on Mysql/Postgres
 `print(qs.explain(verbose=True, format='json'))`

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

Re: [Django] #28582: Tutorial contains unnecessary explanation

[Django]

#28582: Tutorial contains unnecessary explanation
-+-
 Reporter:  ImmaSix  |Owner:  ImmaSix
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 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
-+-
Description changed by ImmaSix:

Old description:

> working at write the docs conference with Daniele Procida. Work in
> progress, will add more notes here.
>
> * tutorial 01: changing the port block explanation not necessary -
> beginning users can skip this,
> *

New description:

 working at write the docs conference with Daniele Procida. Work in
 progress, will add more notes here.

 * tutorial 01: "changing the port" block explanation not necessary -
 beginning users can skip this,
 * tutorial 01: "Projects vs. apps" block explanation not necessary.
 * tutorial 01: mysite/urls.py code snippets: the two code snippets are
 different from each other. The second adds not only the `include` as
 described in the tutorials, but also adds more lines that are not
 explained.
 * tutorial 01: explanation for `include()` a bit too detailed. A part of
 it can move to the `include()` reference if it isn't already there.
 * tutorial 01: a bit of explanation about the 'url()'  arguments is well-
 suited. Some remarks:

   1. explanation about performance of regular expressions is not
 necessary.
   2. kwargs and name are not used in the example and are optional: can
 probably be removed.

 * tutorial 02: for a tutorial, it is ok to stick to the SQLite database.
 Any information about settings for other databases can be moved away. If
 it is important to set the database correctly this early in the project,
 I'd suggest to make a how-to and create a link to it.
 * tutorial 02: The content of the **philosophy** block might be moved to
 the main text, so that the main text is not interrupted by the block.
 Explaining why we create a model is important enough. If the explanation
 can be a bit shorter, that would be great.
 * tutorial 02: block bypassing manage.py is not necessary.
 * tutorial 02: the line {{{@python_2_unicode_compatible  # only if you
 need to support Python 2}}} comes a bit out of the blue. How important is
 this line?

--

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

Re: [Django] #28560: distinct() on ordered queryset with restricted list of columns returns incorrect result

[Django]

#28560: distinct() on ordered queryset with restricted list of columns returns
incorrect result
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  distinct values  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by felixxm:

Old description:

> When `distinct()` is used with `values()` (or `values_list()`) on ordered
> queryset and a list of fields in `values()` doesn't contain all fields
> from `ORDER BY`, then it doesn't return correct result because columns
> from `ORDER BY` clause must be included in `SELECT`. As Simon suggested
> we should wrap a query in a subquery.

New description:

 When `distinct()` is used with `values()` (or `values_list()`) on ordered
 queryset and a list of fields in `values()` doesn't contain all fields
 from `ORDER BY`, then it doesn't return correct result because columns
 from `ORDER BY` clause must be included in `SELECT`. As Simon suggested we
 should wrap a query in a subquery (see related tickets #7070, #5321).

--

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

Re: [Django] #28560: distinct() on ordered queryset with restricted list of columns returns incorrect result

[Django]

#28560: distinct() on ordered queryset with restricted list of columns returns
incorrect result
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  distinct values  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by felixxm:

Old description:

> I think we should raise `NotSupportedError` when `distinct()` is used
> with `values()` (or `values_list()`) on ordered queryset and a list of
> fields in `values()` doesn't contain all fields from `ORDER BY`. It
> cannot return correct result because columns from `ORDER BY` clause must
> be included in `SELECT`.

New description:

 When `distinct()` is used with `values()` (or `values_list()`) on ordered
 queryset and a list of fields in `values()` doesn't contain all fields
 from `ORDER BY`, then it doesn't return correct result because columns
 from `ORDER BY` clause must be included in `SELECT`. As Simon suggested we
 should wrap a query in a subquery.

--

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

[Django] #28582: Tutorial contains unnecessary explanation

[Django]

#28582: Tutorial contains unnecessary explanation
+--
   Reporter:  ImmaSix   |  Owner:  ImmaSix
   Type:  Cleanup/optimization  | Status:  assigned
  Component:  Documentation |Version:  1.11
   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 |
+--
 working at write the docs conference with Daniele Procida. Work in
 progress, will add more notes here.

 * tutorial 01: changing the port block explanation not necessary -
 beginning users can skip 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/049.7a37e39cc13f1e951054ba9c8ec79894%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28581: Pagination topic docs need a little restructuring

[Django]

#28581: Pagination topic docs need a little restructuring
-+--
   Reporter:  luto   |  Owner:  luto
   Type:  Bug| Status:  assigned
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+--
 During the Write The Docs conference I came a cross a few issues with the
 [https://docs.djangoproject.com/en/dev/topics/pagination/ pagination topic
 documentation]. The content itself is great, but I think a little
 restructuring could make it even better. Together with Daniele, we came
 with the following changes:

 * the topic page contains a full class reference to the `Paginator` class
 as well as some helper classes. This should move to a new reference page.
 * most developers will use a views `paginate_by` instead of the
 `Paginator` class directly. This is documented in reference as part of
 [https://docs.djangoproject.com/en/dev/ref/class-based-views/mixins-
 multiple-object/ Multiple object mixins] as well as a very specific
 example in [https://docs.djangoproject.com/en/dev/topics/class-based-
 views/mixins/#using-singleobjectmixin-with-listview Class Based Views].
 But there is no straight-forward example anywhere. The new page should
 provide one and explain the behavior on a higher level.

 Please note that this is my very first issue and pull request to django.
 If any part of this does not comply with the way you usually do things,
 just let me know and I'll happily adapt :)

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

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