Re: [Django] #24879: In the docs, models.QuerySet is used instead of models.query.QuerySet

#24879: In the docs, models.QuerySet is used instead of models.query.QuerySet ---+-- Reporter: devtester44|Owner: nobody Type: Bug| Status: new Component:

[Django] #24879: In the docs, models.QuerySet is used instead of models.query.QuerySet

#24879: In the docs, models.QuerySet is used instead of models.query.QuerySet ---+ Reporter: devtester44| Owner: nobody Type: Bug| Status: new Component: Documentation |Version: 1.8 Severity:

Re: [Django] #24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()`

#24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()` ---+ Reporter: Kronuz |Owner: nobody Type: New feature| Status: new

Re: [Django] #24878: response.content TypeError: Type str doesn't support the buffer API

#24878: response.content TypeError: Type str doesn't support the buffer API -+-- Reporter: LegoStormtroopr |Owner: nobody Type: Uncategorized| Status: closed

[Django] #24878: response.content TypeError: Type str doesn't support the buffer API

#24878: response.content TypeError: Type str doesn't support the buffer API -+ Reporter: LegoStormtroopr | Owner: nobody Type: Uncategorized| Status: new Component: Uncategorized|Version: 1.8

Re: [Django] #24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()`

#24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()` ---+-- Reporter: Kronuz |Owner: nobody Type: Uncategorized | Status:

[Django] #24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()`

#24877: Exceptions in renderizable responses are not handled by Middleware's `process_exception()` ---+ Reporter: Kronuz | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #23422: Cannot add Permission to Group in data migration

#23422: Cannot add Permission to Group in data migration +-- Reporter: tjwalch |Owner: nobody Type: Bug | Status: closed Component: Migrations |

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: Gagaro Type: Bug | Status: assigned Component:

Re: [Django] #24875: inotify broken with vim, dev server does not restart

#24875: inotify broken with vim, dev server does not restart -+- Reporter: chrisbainbridge |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24182: Document or improve limitations for doing queries in field defaults

#24182: Document or improve limitations for doing queries in field defaults -+ Reporter: arveitch |Owner: nobody Type: New feature | Status: new Component: Migrations

Re: [Django] #23643: Have debug page show "During handling of this exception, another exception occurred.."

#23643: Have debug page show "During handling of this exception, another exception occurred.." -+-- Reporter: cool-RR |Owner: tricoder42 Type: New feature |

Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob |Owner: | adamchainz Type: New feature |

Re: [Django] #24876: Skipping migrations checking in sql* commands

#24876: Skipping migrations checking in sql* commands ---+-- Reporter: marcinn|Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #24876: Skipping migrations checking in sql* commands

#24876: Skipping migrations checking in sql* commands ---+ Reporter: marcinn| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.8 Severity: Normal |

[Django] #24876: Skipping migrations checking in sql* commands

#24876: Skipping migrations checking in sql* commands ---+ Reporter: marcinn| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.8 Severity: Normal |

Re: [Django] #23643: Have debug page show "During handling of this exception, another exception occurred.."

#23643: Have debug page show "During handling of this exception, another exception occurred.." -+-- Reporter: cool-RR |Owner: tricoder42 Type: New feature |

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: Gagaro Type: Bug | Status: assigned Component:

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24875: inotify broken with vim, dev server does not restart

#24875: inotify broken with vim, dev server does not restart + Reporter: chrisbainbridge | Owner: nobody Type: Bug | Status: new Component: Core (Management commands)

[Django] #24875: inotify broken with vim, dev server does not restart

#24875: inotify broken with vim, dev server does not restart + Reporter: chrisbainbridge | Owner: nobody Type: Bug | Status: new Component: Core (Management commands)

Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob |Owner: | adamchainz Type: New feature |

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob |Owner: | adamchainz Type: New feature |

Re: [Django] #24874: Why does "AbstractBaseUser" contain "password" and "last_login" fields?

#24874: Why does "AbstractBaseUser" contain "password" and "last_login" fields? -+- Reporter: christopherdcunha|Owner: nobody Type: | Status:

[Django] #24874: Why does "AbstractBaseUser" contain "password" and "last_login" fields?

#24874: Why does "AbstractBaseUser" contain "password" and "last_login" fields? --+ Reporter: christopherdcunha | Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.auth |

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

Re: [Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

Re: [Django] #24831: Pickling querysets with prefetch_related breaks

#24831: Pickling querysets with prefetch_related breaks -+- Reporter: lsemel |Owner: coldmind Type: Bug | Status: assigned Component:

Re: [Django] #24704: Development server does not restart on SynaxError in models.py (was: Development server does not restart on SynaxError)

#24704: Development server does not restart on SynaxError in models.py -+- Reporter: artemrizhov |Owner: nobody Type: Bug | Status: new

Re: [Django] #24860: Migrations leak stale RelatedManager related_model definitions

#24860: Migrations leak stale RelatedManager related_model definitions -+- Reporter: ecederstrand |Owner: nobody Type: Bug | Status: closed

Re: [Django] #24869: Model unicode and Foreign key

#24869: Model unicode and Foreign key ---+-- Reporter: lefedor|Owner: nobody Type: Bug| Status: closed Component: Uncategorized |

Re: [Django] #24867: admin.E202 seems to include superclass references?

#24867: admin.E202 seems to include superclass references? -+-- Reporter: TorstenRottmann |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #24872: dbshell don't read parameters correctly with sql_server.pyodbc (django-pyodbc-azure)

#24872: dbshell don't read parameters correctly with sql_server.pyodbc (django- pyodbc-azure) -+- Reporter: netamego |Owner: nobody Type: Uncategorized|

Re: [Django] #24867: admin.E202 seems to include superclass references?

#24867: admin.E202 seems to include superclass references? -+-- Reporter: TorstenRottmann |Owner: nobody Type: Bug | Status: new Component: contrib.admin

Re: [Django] #24867: admin.E202 seems to include superclass references?

#24867: admin.E202 seems to include superclass references? -+-- Reporter: TorstenRottmann |Owner: nobody Type: Bug | Status: closed Component:

[Django] #24873: Error while using Prefech on more than two levels

#24873: Error while using Prefech on more than two levels -+- Reporter: Gagaro | Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

Re: [Django] #24871: Textarea widget has redundant \r\n

#24871: Textarea widget has redundant \r\n --+-- Reporter: tompecina |Owner: nobody Type: Bug | Status: new Component: Forms |

[Django] #24872: dbshell don't read parameters correctly with sql_server.pyodbc (django-pyodbc-azure)

#24872: dbshell don't read parameters correctly with sql_server.pyodbc (django- pyodbc-azure) -+- Reporter: netamego | Owner: nobody Type: Uncategorized| Status: new