Re: [Django] #29531: Chat live with other Django users fails to open

[Django]

#29531: Chat live with other Django users fails to open
-+--
 Reporter:  luisvee3 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  2.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tim Graham):

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


Comment:

 You need to open the URL with an IRC client.

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

[Django] #29531: Chat live with other Django users fails to open

[Django]

#29531: Chat live with other Django users fails to open
---+
   Reporter:  luisvee3 |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (URLs)  |Version:  2.0
   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|
---+
 In the community section of the Django site, (
 https://www.djangoproject.com/community/), the link to chat live with
 other users leads to a page unable to load on safari and is practically
 dead on chrome.

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

Re: [Django] #29527: Multi-column comparisons

[Django]

#29527: Multi-column comparisons
+--
 Reporter:  Ryan Hiebert|Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  2.0
 Severity:  Normal  |   Resolution:
 Keywords:  QuerySet.extra  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Ryan Hiebert):

 With the help of a patient colleague (thanks Tim!) I've been able to
 accomplish what I needed to natively, without using {{{.extra()}}}. With
 one caveat, I needed to add the LHS as a calculated column using annotate,
 which is a bit of a kludge, which ends up returning annotated data that I
 didn't really need. For my case, that's not too big of a deal, but perhaps
 less than ideal.

 It might be deserving of a way to remove annotations that don't need to be
 selected, or to allow filter expressions that allow a dynamic expression
 on both sides. I'm not sure if that deserves its own ticket, if it should
 be on this one, or if perhaps there's already a ticket open for that.

 Here's what we came up with:

 {{{#!python
 from django.db.models import Func, F, Subquery

 def after(queryset, value):
 fields = ['a', 'b', 'c', 'id']
 return (
 queryset
 .annotate(rank=Func(*(F(field) for field in fields),
 function='ROW'))
 .filter(rank=Subquery(queryset.filter(id=value).values(*fields)))
 .order_by(*fields)
 )
 }}}

 One other thing to note is that this opts to use the explicit {{{ROW}}}
 function, rather than relying on that being the result of just using
 parenthesis, because parenthesis alone with a single value doesn't
 necessarily make a {{{ROW}}}.

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

[Django] #29530: Chaining .annotate() on models generates wrong SQL aliases.

[Django]

#29530: Chaining .annotate() on models generates wrong SQL aliases.
-+-
   Reporter:  Volodymyr  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|   Keywords:  annotate, INNER
   Severity:  Normal |  JOIN, model,
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I simplified my models code as I could, keeping necessary fields.
 So with these models given:
 {{{
 class Station(models.Model):
 pass

 class Route(models.Model):
 """ just ties route nodes together """
 pass

 class RouteNode(models.Model):
 """
 Class that handles many-to-many relationship between stations and
 routes.
 """
 route = models.ForeignKey(Route, on_delete=models.CASCADE)
 station = models.ForeignKey(Station, on_delete=models.CASCADE)
 duration = models.DurationField()

 class Trip(models.Model):
 route = models.ForeignKey(Route, on_delete=models.DO_NOTHING)
 }}}

 I try to query them like:
 {{{
 Trip.objects.filter(
 route__routenode__station=1
 ).annotate(
 board_station_duration=F('route__routenode__duration'),
 ).filter(
 route__routenode__station=2,
 ).annotate(
 dest_station_duration=F('route__routenode__duration'),
 )
 }}}
 The code above being run on environment with
 ''Django 2.0, Python 3.6.2, DB engine : psycopg2''
 generates the following SQL, so "board_station_duration" and
 "dest_station_duration" referencing same field of same routenode record.
 {{{
 SELECT
   -- not-relevant to this ticket fields --
   "routenode"."duration"  AS "board_station_duration",
   "routenode"."duration"  AS "dest_station_duration"
 FROM "trip"
   INNER JOIN "route" ON ("trip"."route_id" = "route"."id")
   INNER JOIN "routenode" ON ("route"."id" = "routenode"."route_id")
   INNER JOIN "routenode" T5 ON ("route"."id" = T5."route_id")
 WHERE ("routenode"."station_id" = 1 AND T5."station_id" = 2);
 }}}
 And the same python code being run on env
 ''Django 1.10, Python 2.7.14, DB engine : psycopg2''
 generates the following SQL **(as expected)**, so "board_station_duration"
 and "dest_station_duration" referencing fields of different routenode
 record.
 {{{
 SELECT
   -- not-relevant to this ticket fields --
   "routenode"."duration"  AS "board_station_duration",
   T5."duration"  AS "dest_station_duration"
 FROM "trip"
   INNER JOIN "route" ON ("trip"."route_id" = "route"."id")
   INNER JOIN "routenode" ON ("route"."id" = "routenode"."route_id")
   INNER JOIN "routenode" T5 ON ("route"."id" = T5."route_id")
 WHERE ("routenode"."station_id" = 1 AND T5."station_id" = 2);
 }}}

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

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

Re: [Django] #29520: test client crashes when posting bytes

[Django]

#29520: test client crashes when posting bytes
-+-
 Reporter:  Mathias Ertl |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  2.1
 Severity:  Release blocker  |   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:"01b7fdfd67a87e8c881e34d7ed97767c506b189c" 01b7fdfd]:
 {{{
 #!CommitTicketReference repository=""
 revision="01b7fdfd67a87e8c881e34d7ed97767c506b189c"
 [2.1.x] Fixed #29520 -- Fixed test client crash when posting bytes.

 Regression in b8a41a2872624a6d9e61308932dd81d001e31eb9.

 Backport of 9294110a57ce0a6d14506969c950090045c622c8 from master
 }}}

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

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

Re: [Django] #29520: test client crashes when posting bytes

[Django]

#29520: test client crashes when posting bytes
-+-
 Reporter:  Mathias Ertl |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  2.1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9294110a57ce0a6d14506969c950090045c622c8" 9294110a]:
 {{{
 #!CommitTicketReference repository=""
 revision="9294110a57ce0a6d14506969c950090045c622c8"
 Fixed #29520 -- Fixed test client crash when posting bytes.

 Regression in b8a41a2872624a6d9e61308932dd81d001e31eb9.
 }}}

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Greg Allensworth):

 Pull Request is up:https://github.com/django/django/pull/10102

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

Re: [Django] #29520: test client crashes when posting bytes

[Django]

#29520: test client crashes when posting bytes
-+-
 Reporter:  Mathias Ertl |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  2.1
 Severity:  Release blocker  |   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 Claude Paroz):

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Greg Allensworth):

 Thanks, Andrii. Do you want to go ahead and close PR 8491
 https://github.com/django/django/pull/8491  ?

 I will open a new one later today, or 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/065.a4b70d5f888deb62af19ec16aafad088%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrii Soldatenko):

 You need to adopt your patch to django style and create docs and 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/065.f4043108ffad93d3934bf4c13d6ac8f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  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 Greg Allensworth):

 * owner:  Andrii Soldatenko => Greg Allensworth


Comment:

 My own internal note:I have a copy of the patched version here.
 https://github.com/GreenInfo-Network/Django-PostgreSQL-SearchVector

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Andrii
 |  Soldatenko
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrii Soldatenko):

 Sorry I don't have a free time for a long time, yes sure you can reuse my
 PR or create you own, if you need any help please let me know.

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Andrii
 |  Soldatenko
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Greg Allensworth):

 Hello. I wanted to check in on the status of this patch, to support
 `phraseto_tsquery()`

 I ask because this one has been idle for about 14 months, in a "needs
 improvement" state.

 I have come up with a much simpler approach to allowing phrase searching,
 and would be glad to generate a pull request.

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

Re: [Django] #29520: test client crashes when posting bytes (was: Posting bytes broken in 2.1 TestClient)

[Django]

#29520: test client crashes when posting bytes
---+
 Reporter:  Mathias Ertl   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  2.1
 Severity:  Release blocker|   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/10101 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/069.5fe22ed1c4b5a8e5fb1280537fefd480%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12663: Formalize, refactor, and document Model._meta

[Django]

#12663: Formalize, refactor, and document Model._meta
-+-
 Reporter:  Massimiliano |Owner:  pirosb3
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  1.8-alpha| 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 GitHub ):

 In [changeset:"dd367e0daefbeb8541bfdd0278a9ce338404f827" dd367e0d]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd367e0daefbeb8541bfdd0278a9ce338404f827"
 Refs #12663 -- Removed Meta API upgrade guide.
 }}}

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

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

Re: [Django] #29253: method_decorator() with list argument doesn't copy over attributes of the decorator function

[Django]

#29253: method_decorator() with list argument doesn't copy over attributes of 
the
decorator function
+--
 Reporter:  Chris Jerdonek  |Owner:  Chris Jerdonek
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  decorators  | 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:"da46599143408be58c1845b8c82cacbae0bb56c0" da46599]:
 {{{
 #!CommitTicketReference repository=""
 revision="da46599143408be58c1845b8c82cacbae0bb56c0"
 [2.1.x] Refs #29253 -- Fixed method_decorator() crash if decorator sets a
 new attribute.

 Regression in fdc936c9130cf4fb5d59869674b9a31cc79a7999.

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

Re: [Django] #29253: method_decorator() with list argument doesn't copy over attributes of the decorator function

[Django]

#29253: method_decorator() with list argument doesn't copy over attributes of 
the
decorator function
+--
 Reporter:  Chris Jerdonek  |Owner:  Chris Jerdonek
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  decorators  | 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:"f434f5b84f7fcea9a76a551621ecce70786e2899" f434f5b]:
 {{{
 #!CommitTicketReference repository=""
 revision="f434f5b84f7fcea9a76a551621ecce70786e2899"
 Refs #29253 -- Fixed method_decorator() crash if decorator sets a new
 attribute.

 Regression in fdc936c9130cf4fb5d59869674b9a31cc79a7999.
 }}}

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

Re: [Django] #29253: method_decorator() with list argument doesn't copy over attributes of the decorator function

[Django]

#29253: method_decorator() with list argument doesn't copy over attributes of 
the
decorator function
+--
 Reporter:  Chris Jerdonek  |Owner:  Chris Jerdonek
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  2.0
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  decorators  | 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):

 [https://github.com/django/django/pull/10091 PR 10091] fixes a regression
 where `@method_decorator(transaction.non_atomic_requests)` crashes.

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

Re: [Django] #28457: A new 'Congrats' page for first time Django installs

[Django]

#28457: A new 'Congrats' page for first time Django installs
--+
 Reporter:  Timothy Allen |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"f52b026168292803693cecbca061630227df1b29" f52b026]:
 {{{
 #!CommitTicketReference repository=""
 revision="f52b026168292803693cecbca061630227df1b29"
 Refs #28457 -- Tweaked colors/layout of the congrats page for readability.
 }}}

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

Re: [Django] #28478: Make DiscoverRunner skip creating a test database if not needed

[Django]

#28478: Make DiscoverRunner skip creating a test database if not needed
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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 Adam (Chainz) Johnson):

 The PR looks like a good start... do you have time to continue working on
 it? I'll happily help with review, since I was bitten by multi_db in
 #29513.

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

Re: [Django] #28541: migration introducing a UUID primary key fails on sqlite3

[Django]

#28541: migration introducing a UUID primary key fails on sqlite3
+
 Reporter:  karyon  |Owner:  nobody
 Type:  Bug |   Status:  new
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):

 In case anyone else is affected: We found a workaround, that is instead of
 removing the old id column straight away, first rename it and then delete
 it at the end of the migration. See https://github.com/fsr-
 itse/EvaP/pull/1216/files

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

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

[Django] #29529: FilePathField path attribute gets resolved when running makemigrations.

[Django]

#29529: FilePathField path attribute gets resolved when running makemigrations.
-+-
   Reporter: |  Owner:  nobody
  Sebastiaan Arendsen|
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.0
  Migrations |   Keywords:  migration,
   Severity:  Normal |  filepathfield, makemigrations
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have a special case where I want to create a model containing the path
 to some local files on the server/dev machine. Seeing as the place where
 these files are stored is different on different machines I have the
 following:

 {{{
 #!python
 import os

 from django.conf import settings
 from django.db import models

 class LocalFiles(models.Model):
 name = models.CharField(max_length=255)
 file = models.FilePathField(path=os.path.join(settings.LOCAL_FILE_DIR,
 'example_dir'))
 }}}

 Now when running manage.py makemigrations it will resolve the path based
 on the machine it is being run on.  Eg:
 /home//server_files/example_dir

 I had to manually change the migration to include the os.path.join() part
 to not break this when running the migration on production/other machine.

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

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