Re: [Django] #28377: Retain order of form media assets during aggregation

[Django]

#28377: Retain order of form media assets during aggregation
--+
 Reporter:  Johannes Hoppe|Owner:  info@…
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  1.11
 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 Tim Graham ):

 In [changeset:"751f7a6d9b29871795aec1c909ac47ba0b5305a3" 751f7a6]:
 {{{
 #!CommitTicketReference repository=""
 revision="751f7a6d9b29871795aec1c909ac47ba0b5305a3"
 Added Media.__repr__().

 It makes it easier to debug MediaOrderConflictWarnings
 (refs #28377).
 }}}

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

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

[Django]

#28034: Update the contributing tutorial to use a more recent patch
-+-
 Reporter:  Mateusz Jankowski|Owner:  Joe
 Type:   |  Krzystan
  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:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 At this point, it would be idea to use a more recent patch that doesn't
 require an old version of Sphinx to build the documentation. I'm beginning
 to wonder if there might be a better approach to this tutorial so that we
 don't have to update it every so often.

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

Re: [Django] #28536: Replace old cross-browser compatibility JavaScript functions with HTML DOM equivalents (was: Removed old cross-browser compatibility JS functions)

[Django]

#28536: Replace old cross-browser compatibility JavaScript functions with HTML 
DOM
equivalents
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  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 Tim Graham):

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

Re: [Django] #28525: Document GDAL & GeoIP exceptions

[Django]

#28525: Document GDAL & GeoIP exceptions
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gdal geoip geoip2| Triage Stage:  Accepted
  exceptions documentation   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Martin):

 * needs_better_patch:  0 => 1


Comment:

 The patch looks good to me, but I had one query about the `OGRIndexError`
 description.

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

Re: [Django] #28536: Removed old cross-browser compatibility JS functions

[Django]

#28536: Removed old cross-browser compatibility JS functions
-+-
 Reporter:  Claude Paroz |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  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 Claude Paroz):

 * has_patch:  0 => 1


Comment:

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

[Django] #28536: Removed old cross-browser compatibility JS functions

[Django]

#28536: Removed old cross-browser compatibility JS functions
+
   Reporter:  Claude Paroz  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  contrib.admin |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 I think that `addEvent`, `removeEvent` and `cancelEventPropagation` can
 now be safely replaced by their pure Javascript implementations
 (`addEventListener`, `removeEventListener` and `stopPropagation`). They
 were added 12 years ago.

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

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

[Django] #28535: Message on conflicting migrations is misleading for rebase workflows

[Django]

#28535: Message on conflicting migrations is misleading for rebase workflows
+
   Reporter:  karyon|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Migrations|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 |
+
 When there are conflicting migrations, it says
 {{{
 Conflicting migrations detected; multiple leaf nodes in the migration
 graph: (%s). To fix them run 'python manage.py makemigrations --merge'
 }}}

 I lead a project where we have frequent newcomers. on a few occasions they
 encountered this message and the reason was always that they rebased their
 feature branch on a new master, and the master brought a new migration
 which conflicted with a new migration in the feature branch.

 we generally don't see why we would want the merge migrations and advise
 them to migrate to the common ancestor, rename their migration and change
 the dependency, and then run migrate again. that's easy enough and the end
 result is simpler.

 i think makemigrations --merge matches well to a git workflow with
 merging. in our project, we use rebasing instead, and there the merge
 migrations don't make much sense.

 I propose to change the message to {{{To fix them by creating a merge
 migration, run  'python manage.py makemigrations --merge'}}} to make it
 more clearer what will happen, and add {{{Alternatively, you can resolve
 the conflict manually}}}.

 an automatic solution could look like this: {{{mergemigrations --rebase
 }}}, which would ask for confirmation
 {{{this will rebase migration  onto migration
 }}}, or {{{this will set
  as new dependency of
 }}}.

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

Re: [Django] #28533: Add request.headers, track used headers and use that information to automatically populate Vary header.

[Django]

#28533: Add request.headers, track used headers and use that information to
automatically populate Vary header.
---+--
 Reporter:  Linus Lewandowski  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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 Tim Graham):

 `request.headers` is already proposed in #20147. Perhaps you should raise
 the other points on the DevelopersMailingList as it reaches a wider
 audience than this ticket tracker.

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

Re: [Django] #9475: add(), create(), etc. should be supported by intermediate ManyToMany model with extra attributes if extra fields can be calculated

[Django]

#9475: add(), create(), etc. should be supported by intermediate ManyToMany 
model
with extra attributes if extra fields can be calculated
-+-
 Reporter:  omat@…   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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
-+-
Changes (by Collin Anderson):

 * cc: Collin Anderson (added)


Comment:

 Pull Request: https://github.com/django/django/pull/8981

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

Re: [Django] #28487: runserver crashes with UncodeDecodeError as of Django 1.11.4

[Django]

#28487: runserver crashes with UncodeDecodeError as of Django 1.11.4
-+-
 Reporter:  newerBkl |Owner:  Mark
 |  Rogaski
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 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 Tim Graham):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #27869: Add fastupdate and gin_pending_list_limit parameters to GinIndex

[Django]

#27869: Add fastupdate and gin_pending_list_limit parameters to GinIndex
-+-
 Reporter:  Mads Jensen  |Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e016c4c65b4aa0521a74e1cba6f75a596ee9ee1c" e016c4c6]:
 {{{
 #!CommitTicketReference repository=""
 revision="e016c4c65b4aa0521a74e1cba6f75a596ee9ee1c"
 Refs #27869 -- Omitted field kwargs from GinIndex.deconstruct() if they're
 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/068.2a2264c198262a2fe0bda0d46520002d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

[Django]

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres
-+-
 Reporter:  Asif Saifuddin Auvi  |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres, index, | Triage Stage:  Ready for
  BRIN, db-indexes   |  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:"c685b8f838f7f9411a2a65fba7e3893f15439e18" c685b8f8]:
 {{{
 #!CommitTicketReference repository=""
 revision="c685b8f838f7f9411a2a65fba7e3893f15439e18"
 [1.11.x] Refs #25809 -- Omitted pages_per_range from
 BrinIndex.deconstruct() if it's None.

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

Re: [Django] #25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres

[Django]

#25809: PostgreSQL 9.5 BRIN Index support in contrib.postgres
-+-
 Reporter:  Asif Saifuddin Auvi  |Owner:  Mads
 |  Jensen
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres, index, | Triage Stage:  Ready for
  BRIN, db-indexes   |  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:"fb42d0247136249ea81962474e9a6a2faf1755f1" fb42d024]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb42d0247136249ea81962474e9a6a2faf1755f1"
 Refs #25809 -- Omitted pages_per_range from BrinIndex.deconstruct() if
 it's 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/064.a5923bff8c342d3aaa1ba66020bac18d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28531: MultipleChoiceField / CheckboxSelectMultiple values linked to a CharField not restored on bound model forms

[Django]

#28531: MultipleChoiceField / CheckboxSelectMultiple values linked to a 
CharField
not restored on bound model forms
--+--
 Reporter:  Benjamin  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  1.11
 Severity:  Normal|   Resolution:  duplicate
 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 Benjamin):

 Replying to [comment:2 Tim Graham]:
 > Looks like a duplicate of #27495. As far as I know, using those widgets
 with `CharField` isn't supported (and shouldn't be, in my opinion). It's
 better practice to store choices in a many to many table than in a
 `CharField`.

 It works fine with postgres array field: values are properly stored and
 restored.

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

Re: [Django] #21318: Clarify the ordering of the various Media classes

[Django]

#21318: Clarify the ordering of the various Media classes
-+-
 Reporter:  leandro.gz73@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  admin, js, jquery| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Collin Anderson):

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


Comment:

 I believe this is fixed by #28377

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

Re: [Django] #12265: Media (js/css) collection strategy in Forms has no order dependence concept

[Django]

#12265: Media (js/css) collection strategy in Forms has no order dependence 
concept
--+-
 Reporter:  tblanchard@…  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Forms |  Version:  1.1
 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 Collin Anderson):

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


Comment:

 I believe this is fixed by #28377

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

Re: [Django] #28534: Changing JSONField on inline in admin doesn't always trigger change

[Django]

#28534: Changing JSONField on inline in admin doesn't always trigger change
-+
 Reporter:  john-parton  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  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/069.d7b50a682ab8c652d75a86c4a5d241d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28532: Misspelled PostgreSQL data type in documentation

[Django]

#28532: Misspelled PostgreSQL data type in documentation
+--
 Reporter:  Andreas Poisel  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Documentation   |  Version:  1.11
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by Claude Paroz ):

 In [changeset:"503b9ab7ad8369ce1e1566de987872ccebc11f08" 503b9ab7]:
 {{{
 #!CommitTicketReference repository=""
 revision="503b9ab7ad8369ce1e1566de987872ccebc11f08"
 [1.11.x] Fixed #28532 -- Fixed typo in PostgreSQL field docs

 Thanks Andreas Poisel for the report.
 Backport of 3c0b2b80edbe744f45b59fa29219db4997d2a108 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/066.a3a4d69a6afd9f874428588fd71bd622%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28532: Misspelled PostgreSQL data type in documentation

[Django]

#28532: Misspelled PostgreSQL data type in documentation
+--
 Reporter:  Andreas Poisel  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Documentation   |  Version:  1.11
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"3c0b2b80edbe744f45b59fa29219db4997d2a108" 3c0b2b8]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c0b2b80edbe744f45b59fa29219db4997d2a108"
 Fixed #28532 -- Fixed typo in PostgreSQL field docs

 Thanks Andreas Poisel for the report.
 }}}

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