Re: [Django] #30516: Autoreloader crashes on re-raising exceptions with custom signature.

#30516: Autoreloader crashes on re-raising exceptions with custom signature. -+ Reporter: Alan Trick |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #30516: Autoreloader crashes on re-raising exceptions with custom signature. (was: raise_last_exception doesn't work with exception types with different __init__ signatures)

#30516: Autoreloader crashes on re-raising exceptions with custom signature. -+ Reporter: Alan Trick |Owner: nobody Type: Bug | Status: new Component:

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

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

Re: [Django] #30517: refactor BaseMemcachedCache to be a base class for KV engines (was: Base class for Key Value engines for caching)

#30517: refactor BaseMemcachedCache to be a base class for KV engines -+- Reporter: dulmandakh |Owner: nobody Type: | Status: new

Re: [Django] #30517: Base class for Key Value engines for caching

#30517: Base class for Key Value engines for caching -+- Reporter: dulmandakh |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #30517: Base class for Key Value engines for caching

#30517: Base class for Key Value engines for caching -+- Reporter: dulmandakh |Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #30517: Base class for Key Value engines for caching

#30517: Base class for Key Value engines for caching + Reporter: dulmandakh| Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #30516: raise_last_exception doesn't work with exception types with different __init__ signatures

#30516: raise_last_exception doesn't work with exception types with different __init__ signatures ---+-- Reporter: alantrick |Owner: nobody Type: Uncategorized | Status:

[Django] #30516: raise_last_exception doesn't work with exception types with different __init__ signatures

#30516: raise_last_exception doesn't work with exception types with different __init__ signatures -+ Reporter: alantrick | Owner: nobody Type: Uncategorized | Status: new

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

#30515: Document django.shortcuts.resolve_url + Reporter: sage | Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #30485: Unexpected behavior for django.utils.http.urlencode

#30485: Unexpected behavior for django.utils.http.urlencode -+- Reporter: Johan Lübcke |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #30479: Autoreloader with StatReloader doesn't track changes in manage.py.

#30479: Autoreloader with StatReloader doesn't track changes in manage.py. -+-- Reporter: Keryn Knight |Owner: Tom Forbes Type: Bug | Status: assigned

Re: [Django] #30479: Autoreloader with StatReloader doesn't track changes in manage.py.

#30479: Autoreloader with StatReloader doesn't track changes in manage.py. -+-- Reporter: Keryn Knight |Owner: Tom Forbes Type: Bug | Status: assigned

Re: [Django] #30505: Ordering of Field.choices is significant for makemigrations

#30505: Ordering of Field.choices is significant for makemigrations --+--- Reporter: Marnanel Thurman |Owner: Caio Ariede Type: Bug | Status: assigned

Re: [Django] #30507: Update admin's jQuery to 3.4.X.

#30507: Update admin's jQuery to 3.4.X. -+- Reporter: felixxm |Owner: Type: | dulmandakh Cleanup/optimization | Status:

Re: [Django] #29548: Add official support for MariaDB.

#29548: Add official support for MariaDB. -+- Reporter: Tim Graham |Owner: felixxm Type: New feature | Status: closed Component: Database layer

Re: [Django] #29548: Add official support for MariaDB.

#29548: Add official support for MariaDB. -+- Reporter: Tim Graham |Owner: felixxm Type: New feature | Status: assigned Component: Database layer

Re: [Django] #30505: Ordering of Field.choices is significant for makemigrations

#30505: Ordering of Field.choices is significant for makemigrations --+--- Reporter: Marnanel Thurman |Owner: Caio Ariede Type: Bug | Status: assigned

Re: [Django] #30513: Impossible migration (with a change of model base) is not noticed.

#30513: Impossible migration (with a change of model base) is not noticed. ---+-- Reporter: Victor Porton |Owner: nobody Type: Bug| Status: closed Component:

Re: [Django] #30513: Impossible migration (with a change of model base) is not noticed.

#30513: Impossible migration (with a change of model base) is not noticed. ---+-- Reporter: Victor Porton |Owner: nobody Type: Bug| Status: closed Component:

Re: [Django] #23521: removal of concrete Model from bases doesn't remove it from ModelState bases

#23521: removal of concrete Model from bases doesn't remove it from ModelState bases -+- Reporter: Sergey Fedoseev |Owner: Ian Foote Type: Bug | Status:

Re: [Django] #30513: Impossible migration (with a change of model base) is not noticed. (was: Impossible migration (with a change of model base) is not noticed)

#30513: Impossible migration (with a change of model base) is not noticed. ---+-- Reporter: Victor Porton |Owner: nobody Type: Bug| Status: closed Component:

[Django] #30514: Occasional CSRF cookie not set Django 2.1

#30514: Occasional CSRF cookie not set Django 2.1 + Reporter: Yusuf Musleh | Owner: nobody Type: Bug | Status: new Component: CSRF |

Re: [Django] #30372: Django (moderately) High CPU usage at Idle

#30372: Django (moderately) High CPU usage at Idle -+- Reporter: Benjamin Schollnick |Owner: nobody Type: Bug | Status: closed Component: Core

Re: [Django] #30513: Impossible migration (with a change of model base) is not noticed

#30513: Impossible migration (with a change of model base) is not noticed ---+-- Reporter: Victor Porton |Owner: nobody Type: Bug| Status: new Component:

[Django] #30513: Impossible migration (with a change of model base) is not noticed

#30513: Impossible migration (with a change of model base) is not noticed -+ Reporter: Victor Porton | Owner: nobody Type: Bug| Status: new Component:

Re: [Django] #30355: Specifying custom manager doesn't work with prefetch

#30355: Specifying custom manager doesn't work with prefetch -+- Reporter: Kyle Mulka |Owner: robinh00d Type: Bug | Status: assigned

Re: [Django] #30511: AutoField with postgres10/11 as generated identity.

#30511: AutoField with postgres10/11 as generated identity. -+- Reporter: Michael Kany |Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #24944: Have password_reset pass extra_context to the email template rendering as well

#24944: Have password_reset pass extra_context to the email template rendering as well --+- Reporter: twelveeighty |Owner: Sujay S Kumar Type: New feature | Status:

Re: [Django] #30499: PasswordResetView should be allowed to set `domain_override`. (was: PasswordResetView should be allowed to set `domain_override`)

#30499: PasswordResetView should be allowed to set `domain_override`. -+- Reporter: Mattia Procopio |Owner: Mattia | Procopio Type: New feature

Re: [Django] #30490: migrations unique_index on (app, name).

#30490: migrations unique_index on (app, name). -+- Reporter: Richard |Owner: nobody Kojedzinszky | Type: Bug |

Re: [Django] #30315: StringAgg with ordering in subquery generates invalid string_agg() SQL function call

#30315: StringAgg with ordering in subquery generates invalid string_agg() SQL function call --+--- Reporter: Reupen Shah |Owner: Caio Ariede Type: Bug |

Re: [Django] #30490: migrations unique_index on (app, name).

#30490: migrations unique_index on (app, name). -+- Reporter: Richard |Owner: nobody Kojedzinszky | Type: Bug |

Re: [Django] #30490: migrations unique_index on (app, name).

#30490: migrations unique_index on (app, name). -+- Reporter: Richard |Owner: nobody Kojedzinszky | Type: Bug |

Re: [Django] #30511: AutoField with postgres10/11 as generated identity. (was: AutoField with postgres10/11 as generated identity)

#30511: AutoField with postgres10/11 as generated identity. -+- Reporter: Michael Kany |Owner: nobody Type: New feature | Status: new Component:

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

#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: