[Django] #12849: django's development server raises an encoding exception when trying to colorize non-ascii text

#12849: django's development server raises an encoding exception when trying to colorize non-ascii text ---+ Reporter: jype | Owner: nobody Status: new|

Re: [Django] #12846: [PATCH] Support for compiled pyc files

#12846: [PATCH] Support for compiled pyc files -+-- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core framework |

Re: [Django] #12848: language names should be kept native

#12848: language names should be kept native ---+ Reporter: daonb | Owner: nobody Status: closed| Milestone: 1.2 Component:

Re: [Django] #12848: language names should be kept native

#12848: language names should be kept native ---+ Reporter: daonb | Owner: nobody Status: new | Milestone: 1.2 Component:

Re: [Django] #12848: language names should be kept native

#12848: language names should be kept native ---+ Reporter: daonb | Owner: nobody Status: new | Milestone: 1.2 Component:

[Django] #12848: language names should be kept native

#12848: language names should be kept native --+- Reporter: daonb | Owner: nobody Status: new | Milestone: 1.2 Component: Internationalization | Version:

Re: [Django] #12846: [PATCH] Support for compiled pyc files

#12846: [PATCH] Support for compiled pyc files -+-- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core framework |

Re: [Django] #12847: Allow simple_tags to specify a function name

#12847: Allow simple_tags to specify a function name --+- Reporter: dcramer | Owner: nobody Status: new | Milestone: Component: Template system |

[Django] #12847: Allow simple_tags to specify a function name

#12847: Allow simple_tags to specify a function name -+-- Reporter: dcramer | Owner: nobody Status: new | Milestone: Component: Template system | Version: 1.1

Re: [Django] #12846: [PATCH] Support for compiled pyc files

#12846: [PATCH] Support for compiled pyc files -+-- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core framework |

Re: [Django] #12846: [PATCH] Support for compiled pyc files

#12846: [PATCH] Support for compiled pyc files -+-- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core

Re: [Django] #12845: JSON serialization of empty query set raises "cannot serialize" error.

#12845: JSON serialization of empty query set raises "cannot serialize" error. +--- Reporter: orokusaki | Owner: nobody Status: new| Milestone: 1.2 Component:

Re: [Django] #4656: Allow In-depth serialization by specifying depth to follow relationship

#4656: Allow In-depth serialization by specifying depth to follow relationship -+-- Reporter: jay.m.mar...@gmail.com | Owner: nobody Status: new | Milestone:

Re: [Django] #12846: [PATCH] Support for compiled pyc files

#12846: [PATCH] Support for compiled pyc files -+-- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core framework |

[Django] #12846: Support for compiled pyc files (includes patch)

#12846: Support for compiled pyc files (includes patch) +--- Reporter: dap | Owner: nobody Status: new | Milestone: Component: Core framework | Version: SVN

Re: [Django] #10813: Database errors in the shell should roll back the transaction

#10813: Database errors in the shell should roll back the transaction ---+ Reporter: Glenn | Owner: nobody Status: new | Milestone:

Re: [Django] #10813: Database errors in the shell should roll back the transaction

#10813: Database errors in the shell should roll back the transaction ---+ Reporter: Glenn | Owner: nobody Status: new | Milestone:

Re: [Django] #2723: yes/no option for BooleanField

#2723: yes/no option for BooleanField --+- Reporter: Gary Wilson | Owner: shanx Status: assigned |

[Django] #12845: JSON serialization of empty query set raises "cannot serialize" error.

#12845: JSON serialization of empty query set raises "cannot serialize" error. ---+ Reporter: orokusaki | Owner: nobody Status: new| Milestone: Component: Serialization |

Re: [Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage -+-- Reporter: wkornewald | Owner: nobody Status: new | Milestone: Component:

Re: [Django] #4656: Allow In-depth serialization by specifying depth to follow relationship

#4656: Allow In-depth serialization by specifying depth to follow relationship -+-- Reporter: jay.m.mar...@gmail.com | Owner: nobody Status: new | Milestone:

Re: [Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage -+-- Reporter: wkornewald | Owner: nobody Status: new | Milestone: Component:

Re: [Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage -+-- Reporter: wkornewald | Owner: nobody Status: new | Milestone: Component:

Re: [Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage -+-- Reporter: wkornewald | Owner: nobody Status: new | Milestone: Component:

Re: [Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage +--- Reporter: wkornewald | Owner: nobody Status: new| Milestone: Component: Uncategorized |

[Django] #12844: improve lazy loading and resource usage

#12844: improve lazy loading and resource usage ---+ Reporter: wkornewald | Owner: nobody Status: new| Milestone: Component: Uncategorized | Version: SVN Keywords:

Re: [Django] #9995: Mention 'easy_install Django' as an alternative installation method.

#9995: Mention 'easy_install Django' as an alternative installation method. +--- Reporter: daveyjoe | Owner: nobody Status: new

Re: [Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded ---+ Reporter: m...@tranchant.co.uk | Owner: nobody Status: closed|

Re: [Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded ---+ Reporter: m...@tranchant.co.uk | Owner: nobody Status: closed|

Re: [Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded ---+ Reporter: m...@tranchant.co.uk | Owner: nobody Status: closed|

Re: [Django] #11244: serialization only works for iterable objects

#11244: serialization only works for iterable objects -+-- Reporter: epper | Owner: nobody Status: closed | Milestone: Component:

Re: [Django] #12689: admin model's exclude with single member tuple and no comma does not produce an error

#12689: admin model's exclude with single member tuple and no comma does not produce an error ---+ Reporter: bparker | Owner: nobody Status: new | Milestone:

Re: [Django] #2740: Specifying an order_with_respect_to for a self referential one to many relationship fails

#2740: Specifying an order_with_respect_to for a self referential one to many relationship fails -+-- Reporter: anonymous | Owner: Gulopine Status: assigned| Milestone:

[Changeset] r12416 - django/branches/releases/1.1.X/django/core/cache/backends

Author: russellm Date: 2010-02-11 07:23:11 -0600 (Thu, 11 Feb 2010) New Revision: 12416 Modified: django/branches/releases/1.1.X/django/core/cache/backends/db.py Log: [1.1.X] Corrected merge of r12411 to 1.1.X branch (see r12415). Modified:

Re: [Django] #11675: [patch] Support new memcached wrapper pylibmc

#11675: [patch] Support new memcached wrapper pylibmc -+-- Reporter: pipp...@yahoo.co.jp | Owner: otherjacob Status: assigned| Milestone: 1.2

[Changeset] r12415 - in django/branches/releases/1.1.X: django/core/cache/backends tests/regressiontests/cache

Author: russellm Date: 2010-02-11 07:12:38 -0600 (Thu, 11 Feb 2010) New Revision: 12415 Modified: django/branches/releases/1.1.X/django/core/cache/backends/db.py django/branches/releases/1.1.X/tests/regressiontests/cache/tests.py Log: [1.1.X] Fixed #11483 -- Modified db cache backend to use

[Changeset] r12414 - in django/branches/releases/1.1.X: django/core/cache/backends django/core/management/commands tests/regressiontests/cache

Author: russellm Date: 2010-02-11 07:11:47 -0600 (Thu, 11 Feb 2010) New Revision: 12414 Modified: django/branches/releases/1.1.X/django/core/cache/backends/db.py django/branches/releases/1.1.X/django/core/management/commands/createcachetable.py

[Changeset] r12413 - django/branches/releases/1.1.X/django/core/cache/backends

Author: russellm Date: 2010-02-11 07:10:52 -0600 (Thu, 11 Feb 2010) New Revision: 12413 Modified: django/branches/releases/1.1.X/django/core/cache/backends/db.py Log: [1.1.X] Fixed #12189 -- Corrected rollback behavior in database cache backend. Thanks to Lakin Wecker for the report.

Re: [Django] #11260: File based cache not very efficient with large amounts of cached files

#11260: File based cache not very efficient with large amounts of cached files -+-- Reporter: anteater_sa | Owner: josh Status: closed |

[Changeset] r12411 - django/trunk/django/core/cache/backends

Author: russellm Date: 2010-02-11 06:26:34 -0600 (Thu, 11 Feb 2010) New Revision: 12411 Modified: django/trunk/django/core/cache/backends/db.py Log: Fixed #11483 -- Modified db cache backend to use db backend functions for date conversion, avoiding problems under Jython. Thanks to Leo Soto

Re: [Django] #11483: DB Cache backend should use value_to_db_datetime() on datetime values

#11483: DB Cache backend should use value_to_db_datetime() on datetime values ---+ Reporter: leosoto | Owner: nobody Status: new | Milestone: 1.2 Component:

Re: [Django] #12604: Typo on /en/dev/releases/1.1

#12604: Typo on /en/dev/releases/1.1 +--- Reporter: mortense | Owner: dwillis Status: assigned | Milestone: 1.2 Component: Documentation |

[Changeset] r12410 - in django/trunk: django/core/cache/backends django/core/management/commands tests/regressiontests/cache

Author: russellm Date: 2010-02-11 06:21:46 -0600 (Thu, 11 Feb 2010) New Revision: 12410 Modified: django/trunk/django/core/cache/backends/db.py django/trunk/django/core/management/commands/createcachetable.py django/trunk/tests/regressiontests/cache/tests.py Log: Fixed #11623 --

[Changeset] r12409 - django/trunk/django/core/cache/backends

Author: russellm Date: 2010-02-11 06:10:11 -0600 (Thu, 11 Feb 2010) New Revision: 12409 Modified: django/trunk/django/core/cache/backends/db.py Log: Fixed #12189 -- Corrected rollback behavior in database cache backend. Thanks to Lakin Wecker for the report. Modified:

[Changeset] r12408 - in django/trunk: django/core/cache/backends tests/regressiontests/cache

Author: russellm Date: 2010-02-11 06:06:26 -0600 (Thu, 11 Feb 2010) New Revision: 12408 Modified: django/trunk/django/core/cache/backends/memcached.py django/trunk/tests/regressiontests/cache/tests.py Log: Fixed #12399 -- Added handling for memcache timeouts longer than 30 days. Thanks to

Re: [Django] #9310: 404 debug pages should show the name of the tried urlpattern if one exists.

#9310: 404 debug pages should show the name of the tried urlpattern if one exists. -+-- Reporter: floguy | Owner: tobias Status: assigned| Milestone: 1.2

Re: [Django] #12434: django.contrib.admin does not work with blank short_description

#12434: django.contrib.admin does not work with blank short_description ---+ Reporter: anonymous | Owner: nobody Status: new | Milestone: 1.2

Re: [Django] #12434: django.contrib.admin does not work with blank short_description

#12434: django.contrib.admin does not work with blank short_description ---+ Reporter: anonymous | Owner: nobody Status: new | Milestone: 1.2

Re: [Django] #12434: django.contrib.admin does not work with blank short_description

#12434: django.contrib.admin does not work with blank short_description ---+ Reporter: anonymous | Owner: nobody Status: new | Milestone: 1.2

Re: [Django] #12434: django.contrib.admin does not work with blank short_description

#12434: django.contrib.admin does not work with blank short_description ---+ Reporter: anonymous | Owner: nobody Status: new | Milestone: 1.2

Re: [Django] #12434: django.contrib.admin does not work with blank short_description

#12434: django.contrib.admin does not work with blank short_description ---+ Reporter: anonymous | Owner: nobody Status: new | Milestone: 1.2

Re: [Django] #12841: In admin options class, blank short_description causes "string index out of range" exception

#12841: In admin options class, blank short_description causes "string index out of range" exception ---+ Reporter: gregplaysguitar | Owner: nobody Status: closed|

Re: [Django] #12841: In admin options class, blank short_description causes "string index out of range" exception

#12841: In admin options class, blank short_description causes "string index out of range" exception ---+ Reporter: gregplaysguitar | Owner: nobody Status: new |

Re: [Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded ---+ Reporter: m...@tranchant.co.uk | Owner: nobody Status: new |

Re: [Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded ---+ Reporter: m...@tranchant.co.uk | Owner: nobody Status: new |

[Django] #12843: add user in admin causes template exception: maximum recursion depth exceeded

#12843: add user in admin causes template exception: maximum recursion depth exceeded --+- Reporter: m...@tranchant.co.uk | Owner: nobody Status: new | Milestone: Component: