[Django] #30550: TestClient's response.json() should decode content using the response charset

2019-06-06 Thread Django
#30550: TestClient's response.json() should decode content using the response charset -+ Reporter: Jon Dufresne | Owner: nobody Type: Bug| Status: new

Re: [Django] #30550: TestClient's response.json() should decode content using the response charset

2019-06-06 Thread Django
#30550: TestClient's response.json() should decode content using the response charset ---+-- Reporter: Jon Dufresne |Owner: nobody Type: Bug| Status:

Re: [Django] #27804: Use unittest.subTest() in Django's test suite

2019-06-06 Thread Django
#27804: Use unittest.subTest() in Django's test suite --+ Reporter: Tim Graham|Owner: (none) Type: Cleanup/optimization | Status: closed Component: Core

Re: [Django] #30550: TestClient's response.json() should decode content using the response charset.

2019-06-06 Thread Django
#30550: TestClient's response.json() should decode content using the response charset. -+- Reporter: Jon Dufresne |Owner: Jon | Dufresne Type:

Re: [Django] #30550: TestClient's response.json() should decode content using the response charset. (was: TestClient's response.json() should decode content using the response charset)

2019-06-06 Thread Django
#30550: TestClient's response.json() should decode content using the response charset. -+- Reporter: Jon Dufresne |Owner: Jon | Dufresne Type:

Re: [Django] #30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace.

2019-06-06 Thread Django
#30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace. -+-- Reporter: Erik Stein |Owner: nobody Type: Bug | Status:

Re: [Django] #30397: Allow app_label and class to be specified in the name argument for indexes and constraints.

2019-06-06 Thread Django
#30397: Allow app_label and class to be specified in the name argument for indexes and constraints. -+- Reporter: felixxm |Owner: Can | Sarıgöl

Re: [Django] #29706: RenameContentType._rename() doesn't save the content type on the correct database

2019-06-06 Thread Django
#29706: RenameContentType._rename() doesn't save the content type on the correct database -+- Reporter: Tyler Morgan |Owner: Hasan | Ramezani

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

2019-06-06 Thread Django
#30515: Document django.shortcuts.resolve_url. -+- Reporter: sage |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #30543: admin.E108 is raised on fields accessible only via instance.

2019-06-06 Thread Django
#30543: admin.E108 is raised on fields accessible only via instance. -+- Reporter: ajcsimons|Owner: ajcsimons Type: Bug | Status: assigned

Re: [Django] #26813: ModelForm RadioSelect widget for foreign keys should not present a blank option if blank=False on the model

2019-06-06 Thread Django
#26813: ModelForm RadioSelect widget for foreign keys should not present a blank option if blank=False on the model -+- Reporter: Alex Heyden |Owner: Ludwig

Re: [Django] #30547: Document what happens during model validation with Meta.constraints. (was: Specify what happens during model validation with Meta.constraints)

2019-06-06 Thread Django
#30547: Document what happens during model validation with Meta.constraints. -+- Reporter: Dirk Groten |Owner: nobody Type: | Status: new

Re: [Django] #26813: ModelForm RadioSelect widget for foreign keys should not present a blank option if blank=False on the model

2019-06-06 Thread Django
#26813: ModelForm RadioSelect widget for foreign keys should not present a blank option if blank=False on the model -+- Reporter: Alex Heyden |Owner: Ludwig

[Django] #30548: Improve exception message when BaseExpression raises "'Expression contains mixed types. You must set output_field.'"

2019-06-06 Thread Django
#30548: Improve exception message when BaseExpression raises "'Expression contains mixed types. You must set output_field.'" -+- Reporter: Keryn | Owner: nobody Knight

Re: [Django] #30548: Improve exceptions about mixed types in Expressions. (was: Improve exception message when BaseExpression raises "'Expression contains mixed types. You must set output_field.'")

2019-06-06 Thread Django
#30548: Improve exceptions about mixed types in Expressions. -+- Reporter: Keryn Knight |Owner: nobody Type: | Status: new

Re: [Django] #30512: Update mail backend to use modern standard library parsing approach.

2019-06-06 Thread Django
#30512: Update mail backend to use modern standard library parsing approach. -+- Reporter: Joachim Jablon |Owner: Joachim Type: | Jablon Cleanup/optimization

Re: [Django] #30512: Update mail backend to use modern standard library parsing approach.

2019-06-06 Thread Django
#30512: Update mail backend to use modern standard library parsing approach. -+- Reporter: Joachim Jablon |Owner: Joachim Type: | Jablon Cleanup/optimization

[Django] #30547: Specify what happens during model validation with Meta.constraints

2019-06-06 Thread Django
#30547: Specify what happens during model validation with Meta.constraints -+- Reporter: Dirk | Owner: nobody Groten | Type: |

Re: [Django] #30397: Allow app_label and class to be specified in the name argument for indexes and constraints.

2019-06-06 Thread Django
#30397: Allow app_label and class to be specified in the name argument for indexes and constraints. -+- Reporter: felixxm |Owner: Can | Sarıgöl

Re: [Django] #30546: isinstance() call on SimpleLazyObject doesn't swallow evaluation exceptions on Python3. (was: SimpleLazyObject not so lazy on Python3)

2019-06-06 Thread Django
#30546: isinstance() call on SimpleLazyObject doesn't swallow evaluation exceptions on Python3. -+- Reporter: Sławek Ehlert|Owner: nobody Type: Bug |

Re: [Django] #28567: Incompatibility between the set_language() view, LocaleMiddleware, and i18n_patterns() when prefix_default_language=False.

2019-06-06 Thread Django
#28567: Incompatibility between the set_language() view, LocaleMiddleware, and i18n_patterns() when prefix_default_language=False. -+- Reporter: George Tantiras |Owner: George

[Django] #30549: Error while saving the user.

2019-06-06 Thread Django
#30549: Error while saving the user. -+- Reporter: Shritesh | Owner: (none) Jamulkar | Type: Bug| Status: new

Re: [Django] #28567: Unclear documentation for 'next' parameter of set_language view

2019-06-06 Thread Django
#28567: Unclear documentation for 'next' parameter of set_language view -+- Reporter: George Tantiras |Owner: George | Tantiras Type: Bug

Re: [Django] #28567: Incompatibility between the set_language() view, LocaleMiddleware, and i18n_patterns() when prefix_default_language=False. (was: Unclear documentation for 'next' parameter of set_

2019-06-06 Thread Django
#28567: Incompatibility between the set_language() view, LocaleMiddleware, and i18n_patterns() when prefix_default_language=False. -+- Reporter: George Tantiras |Owner: George

Re: [Django] #30549: Error while saving the user.

2019-06-06 Thread Django
#30549: Error while saving the user. -+- Reporter: Shritesh Jamulkar|Owner: (none) Type: Bug | Status: closed Component: Error reporting |

Re: [Django] #30549: Error while saving the user.

2019-06-06 Thread Django
#30549: Error while saving the user. -+- Reporter: Shritesh Jamulkar|Owner: (none) Type: Bug | Status: closed Component: Error reporting |