Re: [Django] #31235: assertQuerysetEqual cannot compare querysets directly.

[Django]

#31235: assertQuerysetEqual cannot compare querysets directly.
-+-
 Reporter:  Peter Inglesby   |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  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 Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.88839ff946a6fa75ca9d9947da35d3ee%40djangoproject.com.

Re: [Django] #32175: FORCE_SCRIPT_NAME documentation doesn't explain how the prefix is prepended with regard to relative vs. absolute paths.

[Django]

#32175: FORCE_SCRIPT_NAME documentation doesn't explain how the prefix is 
prepended
with regard to relative vs. absolute paths.
---+
 Reporter:  Mason Egger|Owner:  Nayan sharma
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  3.1
 Severity:  Normal |   Resolution:  invalid
 Keywords:  documentation  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Mariusz Felisiak):

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


Comment:

 This behavior is already documented in
 [https://docs.djangoproject.com/en/3.1/ref/settings/#media-url MEDIA_URL]
 and [https://docs.djangoproject.com/en/3.1/ref/settings/#static-url
 STATIC_URL] docs and it's not related with `FORCE_SCRIPT_NAME`, which is
 only a way to override the server-provided value of `SCRIPT_NAME`.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.da02210f0309cdaf31bf612da914f2ea%40djangoproject.com.

Re: [Django] #32114: Workaround for subtest issue with parallel test runner

[Django]

#32114: Workaround for subtest issue with parallel test runner
-+-
 Reporter:  Jordan Ephron|Owner:  Jordan
 Type:   |  Ephron
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Test subtest | Triage Stage:  Accepted
  parallel   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * type:  Uncategorized => Cleanup/optimization


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

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

Re: [Django] #31235: assertQuerysetEqual cannot compare querysets directly.

[Django]

#31235: assertQuerysetEqual cannot compare querysets directly.
-+-
 Reporter:  Peter Inglesby   |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"3f7b3275627385f8f7531fca01cdda50d4ec6b6e" 3f7b327]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f7b3275627385f8f7531fca01cdda50d4ec6b6e"
 Fixed #31235 -- Made assertQuerysetEqual() compare querysets directly.

 This also replaces assertQuerysetEqual() to
 assertSequenceEqual()/assertCountEqual() where appropriate.

 Co-authored-by: Peter Inglesby 
 Co-authored-by: Mariusz Felisiak 
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1f12739fe779e2a82c6edb2e08cd2165%40djangoproject.com.

Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.01d753710d1a97027bd1be17045b7f23%40djangoproject.com.

Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.1
 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:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d67f965c799f15d45723027d2b42aec01a1d3ca2" d67f965]:
 {{{
 #!CommitTicketReference repository=""
 revision="d67f965c799f15d45723027d2b42aec01a1d3ca2"
 [3.1.x] Fixed #32045 -- Doc'd GenericRelatedObjectManager methods.

 This also documents that .remove() and clear() methods delete related
 objects.

 Backport of 354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.015d0a9df0acdd38364e076934d2b88d%40djangoproject.com.

Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.1
 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:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3" 354c1524]:
 {{{
 #!CommitTicketReference repository=""
 revision="354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3"
 Fixed #32045 -- Doc'd GenericRelatedObjectManager methods.

 This also documents that .remove() and clear() methods delete related
 objects.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.2fe797d51b4fdb7390d1d02a965840ba%40djangoproject.com.

Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"6fa3d02f7f4aa06e18b19ca1f2771b9af9f52294" 6fa3d02f]:
 {{{
 #!CommitTicketReference repository=""
 revision="6fa3d02f7f4aa06e18b19ca1f2771b9af9f52294"
 Refs #32045 -- Added tests for
 GenericRelatedObjectManager.clear()/remove().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.95a5743394acc67366f626dbb18254a3%40djangoproject.com.

Re: [Django] #21183: Filter block on the right covers information in admin

[Django]

#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Vlada Macek  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Accepted
  collapse   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * owner:  Wiktor => (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.4202965010f2d9d392b6a45fc258ee2d%40djangoproject.com.

Re: [Django] #32165: Add pre-commit Hooks

[Django]

#32165: Add pre-commit Hooks
---+--
 Reporter:  David Smith|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 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 Adam (Chainz) Johnson):

 * cc: Adam (Chainz) Johnson (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.85a69f6ebe14a50a51939e43cdfc23ce%40djangoproject.com.

[Django] #32176: Filesystem caching documentation incorrect

[Django]

#32176: Filesystem caching documentation incorrect
-+-
   Reporter:  Carles |  Owner:  Carles Pina Estany
  Pina Estany|
   Type:  Bug| Status:  assigned
  Component: |Version:  master
  Documentation  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 In: https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching

 It says that {{{LOCATION}}} needs to exist. But the code creates it if it
 doesn't exist:
 
https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/cache/backends/filebased.py#L116
 called from
 
https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L23

 Current documentation:
 {{{Make sure the directory pointed-to by this setting exists and is
 readable and writable by the system user under which your Web server runs.
 Continuing the above example, if your server runs as the user apache, make
 sure the directory /var/tmp/django_cache exists and is readable and
 writable by the user apache.}}}

 PR coming soon.

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

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

Re: [Django] #32176: Filesystem caching documentation incorrect

[Django]

#32176: Filesystem caching documentation incorrect
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 |  Pina Estany
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Carles Pina Estany):

 See PR: https://github.com/django/django/pull/13649

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.521a8cdb5285af7c1a6a96a8842f96db%40djangoproject.com.

Re: [Django] #32176: Filesystem caching documentation incorrect

[Django]

#32176: Filesystem caching documentation incorrect
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 |  Pina Estany
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carles Pina Estany):

 * cc: Carles Pina Estany (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.9002622fcfae27f32ad670e3f44f6922%40djangoproject.com.

Re: [Django] #32176: Filesystem caching documentation incorrect

[Django]

#32176: Filesystem caching documentation incorrect
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 |  Pina Estany
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by Carles Pina Estany:

Old description:

> In: https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-
> caching
>
> It says that {{{LOCATION}}} needs to exist. But the code creates it if it
> doesn't exist:
> https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/cache/backends/filebased.py#L116
> called from
> https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L23
>
> Current documentation:
> {{{Make sure the directory pointed-to by this setting exists and is
> readable and writable by the system user under which your Web server
> runs. Continuing the above example, if your server runs as the user
> apache, make sure the directory /var/tmp/django_cache exists and is
> readable and writable by the user apache.}}}
>
> PR coming soon.

New description:

 In: https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching

 It says that {{{LOCATION}}} needs to exist. But the code creates it if it
 doesn't exist:
 
https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/cache/backends/filebased.py#L116
 called from
 
https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L23

 Current documentation:
 {{{Make sure the directory pointed-to by this setting exists and is
 readable and writable by the system user under which your Web server runs.
 Continuing the above example, if your server runs as the user apache, make
 sure the directory /var/tmp/django_cache exists and is readable and
 writable by the user apache.}}}

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

--

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.2a6172f10f36b27849f724d8c06a35d8%40djangoproject.com.

Re: [Django] #32158: loaddata crashes on SQLite when table names are SQL keywords.

[Django]

#32158: loaddata crashes on SQLite when table names are SQL keywords.
-+-
 Reporter:  Scott Herriman   |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  loaddata SqlLite3| Triage Stage:  Accepted
  check_constraints  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Simon Charette):

 > shall i wrap "table_name" in "quote_name" as in
 "quote_name(table_name)"?

 yes, `self.ops.quote_name(table_name)`

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.528b810c0b5948a047fd585fc01fabb3%40djangoproject.com.

Re: [Django] #32176: Outdated LOCATION requirement in Filesystem caching docs. (was: Filesystem caching documentation incorrect)

[Django]

#32176: Outdated LOCATION requirement in Filesystem caching docs.
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 Type:   |  Pina Estany
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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

[Django] #32177: ManagementUtility instantiates CommandParser without passing already-computed prog argument

[Django]

#32177: ManagementUtility instantiates CommandParser without passing already-
computed prog argument
-+-
   Reporter:  William|  Owner:  nobody
  Schwartz   |
   Type:  Bug| Status:  new
  Component:  Core   |Version:  master
  (Management commands)  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 `ManagementUtility`
 
[https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/management/__init__.py#L188-L192
 goes to the trouble] to parse the program name from the `argv` it's passed
 rather than from `sys.argv`:


 {{{
 #!python
 def __init__(self, argv=None):
 self.argv = argv or sys.argv[:]
 self.prog_name = os.path.basename(self.argv[0])
 if self.prog_name == '__main__.py':
 self.prog_name = 'python -m django'
 }}}


 But then when it needs to parse `--pythonpath` and `--settings`, it
 
[https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/management/__init__.py#L347
 uses] the program name from `sys.argv`:


 {{{
 #!python
 parser = CommandParser(usage='%(prog)s subcommand [options]
 [args]', add_help=False, allow_abbrev=False)
 }}}

 Above `"%(prog)s"` [https://docs.python.org/3/library/argparse.html#prog
 refers] to `sys.argv[0]`. Instead, it should refer to `self.prog_name`.
 This can fixed as follows:


 {{{
 #!python
 parser = CommandParser(
 prog=self.prog_name,
 usage='%(prog)s subcommand [options] [args]',
 add_help=False,
 allow_abbrev=False)
 }}}

 I'm aware that `execute_from_command_line` is a private API, but it'd be
 really convenient for me if it worked properly in my weird embedded
 environment where `sys.argv[0]` is
 [https://github.com/indygreg/PyOxidizer/issues/307 incorrectly] `None`. If
 passing my own `argv` to `execute_from_command_line` avoided all the
 ensuing exceptions, I wouldn't have to modify `sys.argv[0]` globally as
 I'm doing in the meantime.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.0dfa25fd8fbee44e0b7ac9ccf8245766%40djangoproject.com.

Re: [Django] #32158: loaddata crashes on SQLite when table names are SQL keywords.

[Django]

#32158: loaddata crashes on SQLite when table names are SQL keywords.
-+-
 Reporter:  Scott Herriman   |Owner:  George
 |  Bezerra
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  loaddata SqlLite3| Triage Stage:  Accepted
  check_constraints  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by George Bezerra):

 * owner:  (none) => George Bezerra
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.99b33c2e9b39d4355d233f7314a3dcbd%40djangoproject.com.

Re: [Django] #32158: loaddata crashes on SQLite when table names are SQL keywords.

[Django]

#32158: loaddata crashes on SQLite when table names are SQL keywords.
-+-
 Reporter:  Scott Herriman   |Owner:  George
 |  Bezerra
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  loaddata SqlLite3| Triage Stage:  Accepted
  check_constraints  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by George Bezerra):

 First contribution, currently trying to understand the code to figure out
 how to write a regression test for this.

 Any help in how to unit test this is appreciated.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cff3305d82dd8551c36849d5c234e87c%40djangoproject.com.