Re: [Django] #26464: Addition to the "Security in Django": Incremental URLs/Identifiers

#26464: Addition to the "Security in Django": Incremental URLs/Identifiers ---+-- Reporter: CrazyPython|Owner: nobody Type: New feature| Status: new Component:

Re: [Django] #26429: Name clash of merge migrations after squashing

#26429: Name clash of merge migrations after squashing -+- Reporter: xgenadam |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding -+- Reporter: yasondinalt |Owner: nobody Type: Bug | Status: new Component: Database layer |

[Django] #26464: Addition to the "Security in Django": Incremental URLs/Identifiers

#26464: Addition to the "Security in Django": Incremental URLs/Identifiers ---+ Reporter: CrazyPython| Owner: nobody Type: New feature| Status: new Component: Documentation |Version: 1.9 Severity:

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField --+ Reporter: MarysiaLowas |Owner: yakky Type: Cleanup/optimization | Status: assigned

Re: [Django] #26002: Improve ModelAdmin.get_search_results() example

#26002: Improve ModelAdmin.get_search_results() example --+ Reporter: timgraham |Owner: bbenko Type: Cleanup/optimization | Status: assigned Component:

Re: [Django] #26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration

#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration -+- Reporter: oneTimePad |Owner: | oneTimePad Type: New feature

Re: [Django] #26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources

#26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources -+- Reporter: charettes|Owner: nobody Type: |

Re: [Django] #26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration

#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration -+- Reporter: oneTimePad |Owner: | oneTimePad Type: New feature

Re: [Django] #26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration

#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration -+- Reporter: oneTimePad |Owner: | oneTimePad Type: New feature

Re: [Django] #14370: Adding support for Autocomplete in contrib.admin

#14370: Adding support for Autocomplete in contrib.admin -+- Reporter: tyrion |Owner: codingjoe Type: New feature | Status: assigned Component:

Re: [Django] #26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration

#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration -+- Reporter: oneTimePad |Owner: | oneTimePad Type: New feature

[Django] #26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration

#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration --+ Reporter: oneTimePad| Owner: oneTimePad Type: New feature | Status: new Component: Core (Other) |Version: master

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField --+ Reporter: MarysiaLowas |Owner: yakky Type: Cleanup/optimization | Status: assigned

Re: [Django] #26462: UnicodeEncodeError when warning about too long caching keys on Python 2

#26462: UnicodeEncodeError when warning about too long caching keys on Python 2 -+ Reporter: suligap |Owner: nobody Type: Bug | Status: new

Re: [Django] #25530: Deferred SQL operations fail when a referenced table or column is renamed during the same migration (was: Deferred foreign keys operations fail when the column is changed during t

#25530: Deferred SQL operations fail when a referenced table or column is renamed during the same migration --+ Reporter: simonphilips |Owner: nobody Type: Bug |

Re: [Django] #26462: UnicodeEncodeError when warning about too long caching keys on Python 2

#26462: UnicodeEncodeError when warning about too long caching keys on Python 2 -+- Reporter: suligap |Owner: nobody Type: Uncategorized| Status: new

Re: [Django] #26461: django.db.utils.ProgrammingError: relation "..." does not exist

#26461: django.db.utils.ProgrammingError: relation "..." does not exist -+- Reporter: prokaktus|Owner: nobody Type: Bug | Status: closed

[Django] #26462: UnicodeEncodeError when warning about too long caching keys on Python 2

#26462: UnicodeEncodeError when warning about too long caching keys on Python 2 ---+ Reporter: suligap| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9

Re: [Django] #26460: Don't call ``warnings.warn`` for each invalid character in a caching key

#26460: Don't call ``warnings.warn`` for each invalid character in a caching key -+- Reporter: suligap |Owner: nobody Type: | Status:

[Django] #26461: django.db.utils.ProgrammingError: relation "..." does not exist

#26461: django.db.utils.ProgrammingError: relation "..." does not exist + Reporter: prokaktus | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.9 Severity:

Re: [Django] #26460: Don't call ``warnings.warn`` for each invalid character in a caching key

#26460: Don't call ``warnings.warn`` for each invalid character in a caching key -+- Reporter: suligap |Owner: nobody Type: | Status:

Re: [Django] #26460: Don't call ``warnings.warn`` for each invalid character in a caching key

#26460: Don't call ``warnings.warn`` for each invalid character in a caching key ---+-- Reporter: suligap|Owner: nobody Type: Uncategorized | Status: new Component:

[Django] #26460: Don't call ``warnings.warn`` for each invalid character in a caching key

#26460: Don't call ``warnings.warn`` for each invalid character in a caching key ---+ Reporter: suligap| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9

Re: [Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding -+- Reporter: yasondinalt |Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding -+- Reporter: yasondinalt |Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding --+ Reporter: yasondinalt | Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |

Re: [Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding --+ Reporter: yasondinalt | Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |

[Django] #26459: DecimalField float rounding

#26459: DecimalField float rounding --+ Reporter: yasondinalt | Owner: nobody Type: Bug | Status: new Component: Database layer (models, ORM) |Version:

Re: [Django] #26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation

#26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation -+- Reporter: kamandol |Owner: nobody Type: Bug

Re: [Django] #26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources

#26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources -+- Reporter: charettes|Owner: nobody Type: |

Re: [Django] #26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation

#26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation -+- Reporter: kamandol |Owner: nobody Type: Bug

[Django] #26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources

#26458: The Avg aggregate should only automatically resolves its output field to FloatField on numeric sources -+- Reporter: charettes | Owner: nobody Type: |

Re: [Django] #25847: Make User.is_authenticated() and User.is_anonymous() "callable properties"

#25847: Make User.is_authenticated() and User.is_anonymous() "callable properties" ---+ Reporter: skorokithakis |Owner: jlaine Type: New feature| Status: assigned

Re: [Django] #26442: Get rid of geodjango.org

#26442: Get rid of geodjango.org -+- Reporter: sephii |Owner: nobody Type: | Status: closed Cleanup/optimization |

Re: [Django] #26290: Pagination module should warn about unordered query set

#26290: Pagination module should warn about unordered query set -+- Reporter: kartikanand |Owner: Type: | EmadMokhtar Cleanup/optimization |

Re: [Django] #26052: Consider removing conditional_content_removal

#26052: Consider removing conditional_content_removal --+ Reporter: aaugustin |Owner: susan Type: Cleanup/optimization | Status: assigned Component:

Re: [Django] #26419: Description of ALLOWED_HOSTS confusing

#26419: Description of ALLOWED_HOSTS confusing --+ Reporter: jtpereyda |Owner: nobody Type: Cleanup/optimization | Status: closed Component:

Re: [Django] #26419: Description of ALLOWED_HOSTS confusing

#26419: Description of ALLOWED_HOSTS confusing --+ Reporter: jtpereyda |Owner: nobody Type: Cleanup/optimization | Status: closed Component:

Re: [Django] #25856: JS strftime shim could (sometimes) support %B

#25856: JS strftime shim could (sometimes) support %B --+ Reporter: kezabelle |Owner: akoskaaa Type: New feature | Status: assigned Component:

Re: [Django] #26447: Remove USE_ETAGS setting

#26447: Remove USE_ETAGS setting --+ Reporter: syphar|Owner: syphar Type: Cleanup/optimization | Status: new Component: Uncategorized |

Re: [Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

#26455: Add lookups and database functions to check for valid geometries and repairing them. -+- Reporter: yellowcap|Owner: yellowcap Type: New feature |

Re: [Django] #26452: Load middleware on server start rather than on first request

#26452: Load middleware on server start rather than on first request --+ Reporter: evansd|Owner: nobody Type: Cleanup/optimization | Status: closed

Re: [Django] #26457: Recolor admin boolean field icons from green and red (was: Boolean fields assume True is good and False is bad)

#26457: Recolor admin boolean field icons from green and red -+- Reporter: newz2000 |Owner: nobody Type: | Status: closed

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField --+ Reporter: MarysiaLowas |Owner: yakky Type: Cleanup/optimization | Status: assigned

Re: [Django] #9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie

#9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie ---+ Reporter: pixelcort |Owner: ambv Type: New feature| Status:

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField --+ Reporter: MarysiaLowas |Owner: yakky Type: Cleanup/optimization | Status: assigned

[Django] #26457: Boolean fields assume True is good and False is bad

#26457: Boolean fields assume True is good and False is bad ---+ Reporter: newz2000 | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9 Severity: Normal |

Re: [Django] #26449: Document that SplitDateTimeWidget requires SplitDateTimeField (was: formfield_overrides doesn't work for models.DateTimeField with SplitDateTimeWidget)

#26449: Document that SplitDateTimeWidget requires SplitDateTimeField --+ Reporter: MarysiaLowas |Owner: yakky Type: Cleanup/optimization | Status: assigned

Re: [Django] #12915: formfield_callback is lost in an inherited ModelForm

#12915: formfield_callback is lost in an inherited ModelForm -+ Reporter: semenov |Owner: nobody Type: Bug | Status: new Component: Forms| Version:

Re: [Django] #26424: Allow URLValidator to skip schemes validation

#26424: Allow URLValidator to skip schemes validation --+ Reporter: timgraham |Owner: burhan Type: New feature | Status: assigned Component: Core (Other) |

Re: [Django] #26456: Document formfield_callback attribute in ModelForm

#26456: Document formfield_callback attribute in ModelForm ---+-- Reporter: vzima |Owner: nobody Type: New feature| Status: closed Component: Documentation |

Re: [Django] #26448: Improve docs for running tests using a different database

#26448: Improve docs for running tests using a different database --+ Reporter: aschn |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #26456: Document formfield_callback attribute in ModelForm

#26456: Document formfield_callback attribute in ModelForm ---+-- Reporter: vzima |Owner: nobody Type: Uncategorized | Status: new Component: Documentation |

Re: [Django] #26453: SITE_ID should start from 1, not 0

#26453: SITE_ID should start from 1, not 0 -+- Reporter: ynikitenko |Owner: nobody Type: | Status: closed Cleanup/optimization

[Django] #26456: Document formfield_callback attribute in ModelForm

#26456: Document formfield_callback attribute in ModelForm ---+ Reporter: vzima | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.9 Severity: Normal |

Re: [Django] #26452: Load middleware on server start rather than on first request (was: Remove lazy initialization of middleware)

#26452: Load middleware on server start rather than on first request --+ Reporter: evansd|Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #26450: Docs says label is "Save as" for the button that actually has the label "Save as new"

#26450: Docs says label is "Save as" for the button that actually has the label "Save as new" -+- Reporter: giuliettamasina |Owner: | giuliettamasina

Re: [Django] #26450: Docs says label is "Save as" for the button that actually has the label "Save as new"

#26450: Docs says label is "Save as" for the button that actually has the label "Save as new" -+- Reporter: giuliettamasina |Owner: | giuliettamasina

Re: [Django] #25699: Allow using test client session handling with custom session apps

#25699: Allow using test client session handling with custom session apps -+- Reporter: sergeykolosov|Owner: | sergeykolosov Type: New feature

Re: [Django] #21608: Logged out sessions are resurrected by concurrent requests

#21608: Logged out sessions are resurrected by concurrent requests -+- Reporter: jonasborgstrom |Owner: tltx Type: Bug | Status: closed

Re: [Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

#26455: Add lookups and database functions to check for valid geometries and repairing them. -+- Reporter: yellowcap|Owner: yellowcap Type: New feature |

Re: [Django] #26454: Direct Link to supported Version Table

#26454: Direct Link to supported Version Table -+- Reporter: guettli |Owner: nobody Type: | Status: closed Cleanup/optimization

[Django] #26455: Add lookups and database functions to check for valid geometries and repairing them.

#26455: Add lookups and database functions to check for valid geometries and repairing them. -+- Reporter: | Owner: yellowcap yellowcap | Type: New | Status: new

Re: [Django] #26201: Document the consequences of rotating the CSRF token on login

#26201: Document the consequences of rotating the CSRF token on login --+ Reporter: wimfeijen |Owner: vehrlich Type: Cleanup/optimization | Status: assigned

Re: [Django] #26403: "Invalid block tag" message is English except for one word

#26403: "Invalid block tag" message is English except for one word --+ Reporter: interDist |Owner: amureki Type: Cleanup/optimization | Status: assigned

Re: [Django] #26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation

#26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation -+- Reporter: kamandol |Owner: nobody Type: Bug

Re: [Django] #26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation

#26434: Inconsistent results of QuerySet count() method using PostgreSQL backend prior and post the QuerySet evaluation -+- Reporter: kamandol |Owner: nobody Type: Bug

Re: [Django] #17741: QuerySet.query.__str__() does not generate valid MySQL query with dates

#17741: QuerySet.query.__str__() does not generate valid MySQL query with dates -+- Reporter: anonymous|Owner: nobody Type: Bug | Status:

Re: [Django] #26403: "Invalid block tag" message is English except for one word

#26403: "Invalid block tag" message is English except for one word -+- Reporter: interDist|Owner: amureki Type: | Status: assigned