Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  GitHub
 Type:   |  
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  first install| Triage Stage:  Ready for
  documentation  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"8fe63dc4cd637c1422a9bf3e3421d64388e14afd" 8fe63dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="8fe63dc4cd637c1422a9bf3e3421d64388e14afd"
 [2.1.x] Fixed #30187 -- Moved "install Django" command to a console box.

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

Re: [Django] #30141: Fix parse_duration() for some negative durations

[Django]

#30141: Fix parse_duration() for some negative durations
---+
 Reporter:  heikkimattila  |Owner:  Seunghun Lee
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  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 Seunghun Lee):

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

Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  GitHub
 Type:   |  
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  first install| Triage Stage:  Ready for
  documentation  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9278acfd1277090257fdb27ce24ab8cf0674bd62" 9278acf]:
 {{{
 #!CommitTicketReference repository=""
 revision="9278acfd1277090257fdb27ce24ab8cf0674bd62"
 [2.2.x] Fixed #30187 -- Moved "install Django" command to a console box.

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

Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  GitHub
 Type:   |  
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  first install| Triage Stage:  Ready for
  documentation  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"edec11ce86a1a0d9e4c5a2a0df6acaf655041c24" edec11ce]:
 {{{
 #!CommitTicketReference repository=""
 revision="edec11ce86a1a0d9e4c5a2a0df6acaf655041c24"
 Fixed #30187 -- Moved "install Django" command to a console box.
 }}}

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

Re: [Django] #19544: IntegrityError during Many To Many add()

[Django]

#19544: IntegrityError during Many To Many add()
-+-
 Reporter:  German M. Bravo  |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * status:  new => assigned
 * owner:  nobody => Simon Charette


Comment:

 The patch should be ready for review. It also implements a fast-add
 analogous to the the fast-delete algorithm when the relation and the
 backend allows it (e.g. when no `m2m_changed` receivers are connected).

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

Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  first install| Triage Stage:  Ready for
  documentation  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Seunghun Lee):

 * status:  assigned => new
 * owner:  Seunghun Lee => (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/070.af7ee804c5260a49f4f657c0151f3b4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30138: Allow QuerySet.bulk_create() to set pk of created objects when ignore_conflicts=True

[Django]

#30138: Allow QuerySet.bulk_create() to set pk of created objects when
ignore_conflicts=True
-+-
 Reporter:  saber solooki|Owner:  Seunghun
 Type:   |  Lee
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (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 Seunghun Lee):

 * status:  new => assigned
 * owner:  nobody => Seunghun Lee


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

Re: [Django] #30124: QuerySet.only() on reverse many-to-one relationship causes extra database queries

[Django]

#30124: QuerySet.only() on reverse many-to-one relationship causes extra 
database
queries
-+-
 Reporter:  Beda Kosata  |Owner:  Dan Davis
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (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 Dan Davis):

 New idea - in the case of a select_related(), then the natural expectation
 is that only will also apply to fields in the related model.  To finish
 this, I will need to understand better how the select tuple in
 `django.db.models.sql.query.Query` is populated, and when.  I know it is
 deferred to the end.   I will check.

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

Re: [Django] #29098: Add SimpleTestCase.assertRedirectsRegex()

[Django]

#29098: Add SimpleTestCase.assertRedirectsRegex()
---+
 Reporter:  Dan J Strohl   |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  2.1
 Severity:  Normal |   Resolution:
 Keywords:  unittest redirect  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Dan Davis):

 * cc: Dan Davis (added)
 * owner:  Dan Davis => (none)
 * status:  assigned => new


Comment:

 Someone else can work on this issue if they have time.

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

Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  Seunghun
 Type:   |  Lee
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  first install| Triage Stage:  Ready for
  documentation  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

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

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

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

Re: [Django] #30187: Move "install Django" command into console box.

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  Marcel Epp   |Owner:  Seunghun
 Type:   |  Lee
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  first install| Triage Stage:  Accepted
  documentation  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Seunghun Lee):

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

Re: [Django] #30186: Show applied datetime in showmigrations

[Django]

#30186: Show applied datetime in showmigrations
-+-
 Reporter:  Timothy Schilling|Owner:  Timothy
 |  Schilling
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
  showmigrations |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Timothy Schilling):

 * status:  new => assigned
 * owner:  nobody => Timothy Schilling
 * has_patch:  0 => 1


Old description:

> My idea is to add the applied datetime value to the showmigrations
> command.
>
> I've run into the case where I'm working on a branch that involves a
> number of migrations across various apps, but then have to switch to a
> different branch which has different migrations. It can be troublesome to
> determine which migrations are new and need to be rolled back. I've
> recently started looking at the django_migrations table sorted on the
> applied column to determine which I've run recently. This would make
> switching between branches involving conflicting migrations easier.
>
> There was some brief discussion [https://groups.google.com/forum/#!topic
> /django-developers/yWuVFvOUhy4 here].
>
> I've initially implemented this so that it would only apply to the
> `--list` option with a `--verbosity` of 2 and above. [https://github.com
> /tim-schilling/django/pull/1 Here's what I have so far.] I wasn't sure
> how to handle backporting.

New description:

 My idea is to add the applied datetime value to the showmigrations
 command.

 I've run into the case where I'm working on a branch that involves a
 number of migrations across various apps, but then have to switch to a
 different branch which has different migrations. It can be troublesome to
 determine which migrations are new and need to be rolled back. I've
 recently started looking at the django_migrations table sorted on the
 applied column to determine which I've run recently. This would make
 switching between branches involving conflicting migrations easier.

 There was some brief discussion [https://groups.google.com/forum/#!topic
 /django-developers/yWuVFvOUhy4 here].

 I've initially implemented this so that it would only apply to the
 `--list` option with a `--verbosity` of 2 and above. ~~[https://github.com
 /tim-schilling/django/pull/1 Here's what I have so far.] I wasn't sure how
 to handle backporting.~~

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

 Edited to strikeout old PR and reference the one to origin.

--

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

Re: [Django] #30183: SQLite instrospection.get_constraints() for unique constraints return wrong count of constraints and doesn't have columns for all items (was: Sqlite instrospection.get_constraints

[Django]

#30183: SQLite instrospection.get_constraints() for unique constraints return 
wrong
count of constraints and doesn't have columns for all items
-+-
 Reporter:  Pavel Tyslacki   |Owner:  nobody
 Type:  Bug  |   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 Tim Graham):

 * component:  Migrations => Database layer (models, ORM)
 * 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/063.509fd66549428f9d503826ec09a4c4ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30187: Move "install Django" command into console box. (was: Django installation unclear)

[Django]

#30187: Move "install Django" command into console box.
-+-
 Reporter:  congomonster |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  first install| Triage Stage:  Accepted
  documentation  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  2.1 => master
 * stage:  Unreviewed => Accepted


Comment:

 Sounds reasonable, and it will be consistent with
 https://docs.djangoproject.com/en/2.1/topics/install/#installing-the-
 development-version.

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

Re: [Django] #11593: Incomplete support for app-level testing

[Django]

#11593: Incomplete support for app-level testing
-+-
 Reporter:  Masklinn |Owner:  Raphael
 |  Kimmig
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  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 Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Patch looks good. Comments on PR (Summary: Just some rewording to the
 "Advanced testing topics" section linked from the new examples needed.)

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

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

Re: [Django] #12952: Models history doesn't use verbose names

[Django]

#12952: Models history doesn't use verbose names
-+-
 Reporter:  Antonio Cangiano |Owner:  Sanyam
 Type:   |  Khurana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 PR looks not far off after several reviews. Once comments are addressed it
 would be good if previous reviewers could give one more look to make sure
 we don't miss anything.

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

Re: [Django] #30183: Sqlite instrospection.get_constraints() for unique constraints return wrong count of constraints and doesn't have columns for all items

[Django]

#30183: Sqlite instrospection.get_constraints() for unique constraints return 
wrong
count of constraints and doesn't have columns for all items
+--
 Reporter:  Pavel Tyslacki  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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
+--

Comment (by Pavel Tyslacki):

 Yep, I'm a bit investigating it. For now look like for inline constraints
 (CHECK and UNIQUE) detection you should use table definition parsing,
 indexes created via `CREATE INDEX` can use current logic.

 Just describe why only table definition parsing should be used for inline
 UNIQUE constraint:
 - both named and unnamed (UNIQUE in field definition) has different name
 within `index_list` and you can match this indexes only (as I see) with
 fields comparison
 - two inline UNIQUE constraints with same fields will be represented as
 one index in `index_list`
 - there are lack for ASC/DESC ordering detecting
 - you cannot delete indexes created as inline constraints via `DROP INDEX`

 I have prototype of table definition parsing so hope I'll can finish fix
 soon.

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

Re: [Django] #30187: Django installation unclear

[Django]

#30187: Django installation unclear
-+-
 Reporter:  congomonster |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  first install| Triage Stage:
  documentation  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by congomonster):

 * type:  Uncategorized => Cleanup/optimization


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

[Django] #30187: Django installation unclear

[Django]

#30187: Django installation unclear
-+-
   Reporter: |  Owner:  nobody
  congomonster   |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.1
  Documentation  |   Keywords:  first install
   Severity:  Normal |  documentation
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 When you install django you only have this little text line "pip install
 Django" in the documentation.
 There should also be a codebox. It should look like the documentation for
 the development version.
 When you visit the site for the first time, it is confusing. Please give
 the stable version a better look.
 A highlight for the stable version would be good. So that a new user can
 faster find the stable version.

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