Re: [Django] #28978: Djano m2m_changed signal's "model" argument is acting wierd (was: Djano m2m changed signal model argument is acting wierd)

2018-01-01 Thread Django
#28978: Djano m2m_changed signal's "model" argument is acting wierd -+- Reporter: Dev Aggarwal |Owner: nobody Type: Uncategorized| Status: new Componen

[Django] #28978: Djano m2m changed signal model argument is acting wierd

2018-01-01 Thread Django
#28978: Djano m2m changed signal model argument is acting wierd -+- Reporter: Dev| Owner: nobody Aggarwal | Type: | Status: n

Re: [Django] #28918: Model.refresh_from_db() should use _base_manager instead of the default_manager

2018-01-01 Thread Django
#28918: Model.refresh_from_db() should use _base_manager instead of the default_manager -+- Reporter: Sjoerd Job Postmus |Owner: nobody Type: Bug | Statu

Re: [Django] #28970: Option to suppress signals on save to avoid loop

2018-01-01 Thread Django
#28970: Option to suppress signals on save to avoid loop -+- Reporter: Gustavo Henrique de |Owner: nobody Almeida Gonçalves | Type: New feature |

Re: [Django] #28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance

2018-01-01 Thread Django
#28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance -+- Reporter: Kal Sze |Owner: nobody Type: Bug |

Re: [Django] #28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance

2018-01-01 Thread Django
#28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance -+- Reporter: Kal Sze |Owner: nobody Type: Bug |

Re: [Django] #28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance

2018-01-01 Thread Django
#28972: `RelatedObjectDoesNotExist` during `loaddata` of models with multi-table inheritance -+- Reporter: Kal Sze |Owner: nobody Type: Bug |

[Django] #28977: Change Local Memory Cache to Use LRU

2018-01-01 Thread Django
#28977: Change Local Memory Cache to Use LRU ---+ Reporter: Grant Jenks | Owner: nobody Type: New feature | Status: new Component: Core (Cache

Re: [Django] #28976: not possible to customize template_name anymore in password reset views

2018-01-01 Thread Django
#28976: not possible to customize template_name anymore in password reset views --+-- Reporter: Jesse Haka|Owner: Jesse Haka Type: Bug | Status: closed Component

Re: [Django] #28859: Django hides NO_DATA_FOUND exception from database with Oracle backend.

2018-01-01 Thread Django
#28859: Django hides NO_DATA_FOUND exception from database with Oracle backend. -+- Reporter: Jani Tiainen |Owner: felixxm Type: Bug | Status: ass

Re: [Django] #28976: not possible to customize template_name anymore in password reset views

2018-01-01 Thread Django
#28976: not possible to customize template_name anymore in password reset views -+-- Reporter: Jesse Haka |Owner: Jesse Haka Type: Bug | Status: assigned

Re: [Django] #28976: not possible to customize template_name anymore in password reset views

2018-01-01 Thread Django
#28976: not possible to customize template_name anymore in password reset views -+-- Reporter: Jesse Haka |Owner: Jesse Haka Type: Bug | Status: assigned

Re: [Django] #28976: not possible to customize template_name anymore in password reset views

2018-01-01 Thread Django
#28976: not possible to customize template_name anymore in password reset views -+-- Reporter: Jesse Haka |Owner: Jesse Haka Type: Bug | Status: assigned

[Django] #28976: not possible to customize template_name anymore in password reset views

2018-01-01 Thread Django
#28976: not possible to customize template_name anymore in password reset views ---+ Reporter: Jesse Haka | Owner: nobody Type: Bug | Status: new C