Re: [Django] #30515: Document django.shortcuts.resolve_url.

[Django]

#30515: Document django.shortcuts.resolve_url.
-+-
 Reporter:  sage |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Adam (Chainz) Johnson):

 Okay fair enough, I don't care that much about making it documented and
 public. I can imagine other use cases like creating a custom redirect()
 that sends a 307 or 308 but I guess they're quite niche.

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

Re: [Django] #30551: urlize on URL with incomplete query string adds equal sign. (was: urlize on URL with incomplete query string adds equal sign)

[Django]

#30551: urlize on URL with incomplete query string adds equal sign.
---+--
 Reporter:  jochengcd  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by felixxm):

 * version:  1.11 => master
 * component:  Uncategorized => Utilities


Comment:

 Thanks for the report.
 
[https://github.com/django/django/blob/c498f088c584ec3aff97409fdc11b39b28240de9/django/utils/html.py#L220-L223
 smart_urlquote()] adds a trailing equal sign. I noticed that `parse_qsl()`
 raises:
 {{{
   File "/usr/lib/python3.6/urllib/parse.py", line 693, in parse_qsl
 raise ValueError("bad query field: %r" % (name_value,))
 ValueError: bad query field: '284309'
 }}}
 when we add `strict_parsing=True` flag, hence I believe that query string
 used by this site is incorrect. I'm not sure that we should handle this
 case in Django.

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

Re: [Django] #30551: urlize on URL with incomplete query string adds equal sign.

[Django]

#30551: urlize on URL with incomplete query string adds equal sign.
---+--
 Reporter:  jochengcd  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 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 felixxm):

 * status:  new => closed
 * type:  Uncategorized => Bug
 * resolution:   => wontfix


Comment:

 It seems that a patch is not feasible with the current implementation that
 uses `parse_qsl()`, because
 {{{
 >>> parse_qsl('a', keep_blank_values=True)
 [('a', '')]
 >>> parse_qsl('a=', keep_blank_values=True)
 [('a', '')]
 }}}
 so would have to add a special workaround for this single case, what is
 not worth it.

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

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

[Django] #30552: SRID data on GEOSGeometry is lost after calling `reverse()` method

[Django]

#30552: SRID data on GEOSGeometry is lost after calling `reverse()` method
-+-
   Reporter: |  Owner:  nobody
  ssrebelious|
   Type:  Bug| Status:  new
  Component:  GIS|Version:  2.1
   Severity:  Normal |   Keywords:  SRID, geometry, GIS
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Following code reproduces the bug. Haven't tested if it persists on Django
 2.2.

 {{{
 from django.contrib.gis.geos import GEOSGeometry

 linestring = GEOSGeometry('LINESTRING(0 1, 1 2)', srid=4326)
 assert linestring.srid == 4326
 linestring.reverse()
 assert linestring.srid == 4326, 'SRID data is lost!'
 }}}

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

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

[Django]

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
-+
 Reporter:  Chris Woytowitz  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Sardorbek Imomaliev):

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

Re: [Django] #28805: Add a database function for RegexpReplace

[Django]

#28805: Add a database function for RegexpReplace
-+-
 Reporter:  Joey Wilhelm |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Oskar Persson):

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

Re: [Django] #30552: GEOSGeometry.reverse() loses SRID.

[Django]

#30552: GEOSGeometry.reverse() loses SRID.
-+
 Reporter:  ssrebelious  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SRID, geometry, GIS  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

 * Attachment "30552.diff" added.

 Simple test.

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

Re: [Django] #30552: GEOSGeometry.reverse() loses SRID. (was: SRID data on GEOSGeometry is lost after calling `reverse()` method)

[Django]

#30552: GEOSGeometry.reverse() loses SRID.
-+
 Reporter:  ssrebelious  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SRID, geometry, GIS  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

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


Comment:

 Thanks for this report.


 Reproduced at c498f088c584ec3aff97409fdc11b39b28240de9.

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

Re: [Django] #29444: Allow fields to be part of the RETURNING clause during INSERT

[Django]

#29444: Allow fields to be part of the RETURNING clause during INSERT
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 Type:   |  Hoppe
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  django, db,  | Triage Stage:  Accepted
  returning, default, model, field   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_tests:  0 => 1


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

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

Re: [Django] #29379: Add autocomplete attribute to contrib.auth fields

[Django]

#29379: Add autocomplete attribute to contrib.auth fields
-+-
 Reporter:  CHI Cheng|Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  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
-+-
Changes (by Carlton Gibson ):

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


Comment:

 In [changeset:"dcb8f00d06eec99072b78d54215c9a3dc04acb99" dcb8f00]:
 {{{
 #!CommitTicketReference repository=""
 revision="dcb8f00d06eec99072b78d54215c9a3dc04acb99"
 Fixed #29379 -- Added autocomplete attribute to contrib.auth.forms fields.

 Thank you to Nick Pope for review.

 Co-authored-by: CHI Cheng 
 }}}

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

[Django] #30553: Misleading logging documentation about disable_existing_loggers default value

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value
-+-
   Reporter: |  Owner:  nobody
  darthdragon|
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.2
  Documentation  |   Keywords:
   Severity:  Normal |  disable_existing_loggers logging
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 In the documentation it's stated that:

  "If the disable_existing_loggers key in the LOGGING dictConfig is set to
 True (which is the default) ..."

 But we can see in
 [https://github.com/django/django/blob/master/django/utils/log.py]
 (master branch commit 10b44e4 at the time of writting) that it is set to
 False instead:

 {{{
 ...
 DEFAULT_LOGGING = {
 'version': 1,
 'disable_existing_loggers': False,
 'filters': {
 ...
 }}}

 Moving "(which is the default)" in the paragraph should be enough:

  "If the disable_existing_loggers key in the LOGGING dictConfig is set to
 True then all loggers from the default configuration will be disabled.
 Disabled loggers are not the same as removed; the logger will still exist,
 but will silently discard anything logged to it, not even propagating
 entries to a parent logger. Thus you should be very careful using
 'disable_existing_loggers': True; it’s probably not what you want.
 Instead, you can set disable_existing_loggers to False (which is the
 default) and redefine some or all of the default loggers; or you can set
 LOGGING_CONFIG to None and handle logging config yourself."

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

Re: [Django] #30553: Misleading logging documentation about disable_existing_loggers default value. (was: Misleading logging documentation about disable_existing_loggers default value)

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value.
-+-
 Reporter:  darthdragon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  disable_existing_loggers logging   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  2.2 => master
 * type:  Uncategorized => Cleanup/optimization
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report, it seems that this note is incorrect since its
 introduction in 095643e69145d6899313c518fdd39919c9a89908 because we
 changed that in 72c65fea41a6a01f24e134e7627417d94746291a.

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

Re: [Django] #30553: Misleading logging documentation about disable_existing_loggers default value.

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value.
-+-
 Reporter:  darthdragon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  disable_existing_loggers logging   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 I think what's meant here is the default for **dictConfig** if
 `disable_existing_loggers` isn't provided.

 > If absent, this parameter defaults to `True`.

 https://docs.python.org/3.7/library/logging.config.html#dictionary-schema-
 details

 I guess the point is that it's important to provide
 `disable_existing_loggers: False` because often the default behaviour is
 not what you want. (''Why aren't my loggers working?'' comes up a lot
 because of this.)

 For me, it'd be worth a rephrase to clarify this. (We see a lot of
 confusions.)

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

Re: [Django] #30553: Misleading logging documentation about disable_existing_loggers default value.

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value.
-+-
 Reporter:  darthdragon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  disable_existing_loggers logging   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Yeah, it seems this kind of thought was exactly what led to #20981 in the
 first place.

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

Re: [Django] #30553: Misleading logging documentation about disable_existing_loggers default value.

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value.
-+-
 Reporter:  darthdragon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  disable_existing_loggers logging   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by felixxm):

 You're right I missed that in
 [https://docs.python.org/3/library/logging.config.html#dictionary-schema-
 details dictionary-schema-details].

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

Re: [Django] #30553: Misleading logging documentation about disable_existing_loggers default value.

[Django]

#30553: Misleading logging documentation about disable_existing_loggers default
value.
-+-
 Reporter:  darthdragon  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  disable_existing_loggers logging   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by darthdragon):

 I think these two sentences are what may start the headache:

  "By default, the LOGGING setting is merged with Django’s default logging
 configuration using the following scheme.

  If the disable_existing_loggers key in the LOGGING dictConfig is set to
 True (which is the default) then all loggers from the default
 configuration will be disabled. ...

 Because even after reading it 10 times, if you have never looked to python
 logging.config (and I didn't until today, shame on me),  you may not
 understand that also any loggers that may have been defined before are
 also disabled.

 And maybe clarifying in "Django’s default logging configuration", that the
 default django loggers are added with disable_existing_loggers=False.

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

Re: [Django] #29087: Impossible to delete pending new inline in admin when invalid (delete button missing)

[Django]

#29087: Impossible to delete pending new inline in admin when invalid (delete
button missing)
---+
 Reporter:  Owen Heisler   |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.0
 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:  1
---+
Changes (by Vitor Freitas):

 * owner:  Vitor Freitas => (none)
 * status:  assigned => new


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

[Django] #30554: Excessive logging by autoreload in v 2.2.1 and 2.2.2

[Django]

#30554: Excessive logging by autoreload in v 2.2.1 and 2.2.2
-+
   Reporter:  Phoebe Bright  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.2
   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  |
-+
 With these two versions I get over 3000 lines of logging by autoreload.py.
 It looks like this::


 {{{
 DEBUG 2019-06-07 09:47:15,927 autoreload Watching dir
 /Users/phoebe/venv/skorie3/lib/python3.6/site-
 packages/import_export/locale with glob **/*.mo.
 DEBUG 2019-06-07 09:47:15,939 autoreload Watching dir
 /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/imagekit/locale
 with glob **/*.mo.
 DEBUG 2019-06-07 09:47:15,945 autoreload Watching dir
 /Users/phoebe/venv/skorie3/lib/python3.6/site-
 packages/django_social_share/locale with glob **/*.mo.
 DEBUG 2019-06-07 09:47:15,953 autoreload Watching dir
 /Users/phoebe/Development/skorie/obstacles/locale with glob **/*.mo.
 System check identified no issues (0 silenced).
 June 07, 2019 - 09:47:18
 Django version 2.2.2, using settings 'config.settings'
 Starting development server at http://127.0.0.1:8000/
 Quit the server with CONTROL-C.
 DEBUG 2019-06-07 09:47:18,990 autoreload File
 /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-
 dynload/_decimal.cpython-36m-darwin.so first seen with mtime 1545635091.0
 DEBUG 2019-06-07 09:47:18,996 autoreload File
 /Users/phoebe/venv/skorie3/lib/python3.6/site-
 packages/tablib/packages/__init__.py first seen with mtime
 1559667881.475002
 DEBUG 2019-06-07 09:47:18,996 autoreload File
 /Users/phoebe/venv/skorie3/lib/python3.6/site-
 packages/reportlab/pdfbase/ttfonts.py first seen with mtime
 1559667875.595854
 DEBUG 2019-06-07 09:47:18,996 autoreload File
 /Users/phoebe/venv/skorie3/lib/python3.6/site-
 packages/stripe/api_resources/sku.py first seen with mtime
 1559667881.135201
 }}}

 3000 more lines like this follow.

 Downgrading back to 2.2 and the logging is not displayed. The change was
 made here to add logging:
 
https://github.com/django/django/commit/6754bffa2b2df15a741008aa611c1bb0e8dff22b

 Is there a way, or could a way be added, to turn this logging off?

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

Re: [Django] #29087: Impossible to delete pending new inline in admin when invalid (delete button missing)

[Django]

#29087: Impossible to delete pending new inline in admin when invalid (delete
button missing)
---+
 Reporter:  Owen Heisler   |Owner:  frnhr
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  2.0
 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:  1
---+
Changes (by frnhr):

 * status:  new => assigned
 * owner:  (none) => frnhr


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

Re: [Django] #30066: UserManager.create_superuser doesn't allow for omitting email or password, unlike create_user which does.

[Django]

#30066: UserManager.create_superuser doesn't allow for omitting email or 
password,
unlike create_user which does.
-+-
 Reporter:  Joshua Cannon|Owner:  Daniel
 Type:   |  Rios
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  create_superuser | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Daniel Rios):

 * owner:  (none) => Daniel Rios
 * 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/068.2cbc0182e1bf35805d17a6e8b01631f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29834: Union queryset with ordering breaks on ordering with derived querysets

[Django]

#29834: Union queryset with ordering breaks on ordering with derived querysets
-+-
 Reporter:  Sergei Maertens  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  orm, union,  | Triage Stage:  Accepted
  ordering   |
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:

 Alternate approach suggested on PR to be considered.

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

[Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
+
   Reporter:  algomaster99  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Migrations|Version:  2.2
   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 |
+
 Migration files, which are automatically created by Django on running
 `python manage.py makemigrations`, do not seem to follow PEP8 guidelines
 completely. The rule **E501 line too long** is not respected in the file.
 I have attached a file to support my arguments.

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

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

Re: [Django] #30555: Migration files generated do not follow PEP8 E501 rule

[Django]

#30555: Migration files generated do not follow PEP8 E501 rule
--+--
 Reporter:  algomaster99  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  2.2
 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 algomaster99):

 * Attachment "Screenshot from 2019-06-08 11-40-35.png" added.

 PEP8 throwing warnings when ran on `migrations` directory

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