[Django] #26571: Documentation about usage of fromtimestamp (wrt timezones) is confusing

#26571: Documentation about usage of fromtimestamp (wrt timezones) is confusing --+ Reporter: bronger | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |

[Django] #26570: Test runner imports module package with Python 3.5+

#26570: Test runner imports module package with Python 3.5+ ---+ Reporter: bronger| Owner: nobody Type: Bug| Status: new Component: Testing framework |Version: 1.9 Severity:

Re: [Django] #26570: Test runner imports models package with Python 3.5+ (was: Test runner imports module package with Python 3.5+)

#26570: Test runner imports models package with Python 3.5+ ---+-- Reporter: bronger|Owner: nobody Type: Bug| Status: new Component: Testing

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

#26341: Weird comments in PO files (.html.py filenames) -+- Reporter: sylvain-garancher|Owner: veranika- | sab Type: Bug |

Re: [Django] #26341: Weird comments in PO files (.html.py filenames)

#26341: Weird comments in PO files (.html.py filenames) -+- Reporter: sylvain-garancher|Owner: veranika- | sab Type: Bug |

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

#26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25986: Django crashes on unicode characters in the local part of an e-mail address

#25986: Django crashes on unicode characters in the local part of an e-mail address -+- Reporter: sergei-maertens |Owner: sergei- | maertens Type:

Re: [Django] #26565: Allow Prefetch query to use .values()

#26565: Allow Prefetch query to use .values() -+- Reporter: mlorant |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #26565: Allow Prefetch query to use .values()

#26565: Allow Prefetch query to use .values() -+- Reporter: mlorant |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #11964: Add the ability to use database-level CHECK CONSTRAINTS

#11964: Add the ability to use database-level CHECK CONSTRAINTS -+- Reporter: schinckel|Owner: nobody Type: New feature | Status: new Component:

Re: [Django] #26569: OSM.Mapnik is an obsolete constructor

#26569: OSM.Mapnik is an obsolete constructor -+- Reporter: claudep |Owner: claudep Type: | Status: closed Cleanup/optimization

Re: [Django] #26569: OSM.Mapnik is an obsolete constructor

#26569: OSM.Mapnik is an obsolete constructor -+- Reporter: claudep |Owner: claudep Type: | Status: assigned Cleanup/optimization

Re: [Django] #26569: OSM.Mapnik is an obsolete constructor

#26569: OSM.Mapnik is an obsolete constructor -+- Reporter: claudep |Owner: claudep Type: Bug | Status: assigned Component: GIS | Version:

[Django] #26569: OSM.Mapnik is an obsolete constructor

#26569: OSM.Mapnik is an obsolete constructor -+ Reporter: claudep| Owner: nobody Type: Bug| Status: new Component: GIS

Re: [Django] #26565: Allow Prefetch query to use .values()

#26565: Allow Prefetch query to use .values() -+- Reporter: mlorant |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #26565: Allow Prefetch query to use .values()

#26565: Allow Prefetch query to use .values() -+- Reporter: mlorant |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #26565: Allow Prefetch query to use .values() (was: Allow Prefetch query to returns aggregations)

#26565: Allow Prefetch query to use .values() -+- Reporter: mlorant |Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #26567: Update references to the HTTP spec

#26567: Update references to the HTTP spec --+ Reporter: vfaronov |Owner: vfaronov Type: Cleanup/optimization | Status: assigned Component:

Re: [Django] #26568: in_bulk when run on a query set should not need a list of IDs

#26568: in_bulk when run on a query set should not need a list of IDs -+- Reporter: brillgen |Owner: nobody Type: | Status: closed

[Django] #26568: in_bulk when run on a query set should not need a list of IDs

#26568: in_bulk when run on a query set should not need a list of IDs ---+ Reporter: brillgen | Owner: nobody Type: Bug| Status: new Component: Uncategorized |Version: 1.8 Severity: Normal

Re: [Django] #22936: Get rid of field.get_db_prep_lookup()

#22936: Get rid of field.get_db_prep_lookup() -+- Reporter: akaariai |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #26567: Update references to the HTTP spec

#26567: Update references to the HTTP spec -+- Reporter: vfaronov |Owner: vfaronov Type: | Status: assigned Cleanup/optimization

Re: [Django] #26567: Update references to the HTTP spec (was: Update references to the HTTP spec in the docs)

#26567: Update references to the HTTP spec -+- Reporter: vfaronov |Owner: nobody Type: | Status: new Cleanup/optimization

[Django] #26567: Update references to the HTTP spec in the docs

#26567: Update references to the HTTP spec in the docs --+ Reporter: vfaronov | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |Version: master

Re: [Django] #26566: Wrong example of Cache-Control in the docs

#26566: Wrong example of Cache-Control in the docs ---+-- Reporter: vfaronov |Owner: nobody Type: Bug| Status: new Component: Documentation |

[Django] #26566: Wrong example of Cache-Control in the docs

#26566: Wrong example of Cache-Control in the docs ---+ Reporter: vfaronov | Owner: nobody Type: Bug| Status: new Component: Documentation |Version: master Severity: Normal |

Re: [Django] #26564: Migration for renaming M2M field intermediate model causes exception

#26564: Migration for renaming M2M field intermediate model causes exception +-- Reporter: MJafarMashhadi |Owner: nobody Type: Bug | Status: new Component:

[Django] #26565: Allow Prefetch query to returns aggregations

#26565: Allow Prefetch query to returns aggregations --+ Reporter: mlorant | Owner: nobody Type: Bug | Status: new Component: Database layer