tickets
17 rows where "created" is on date 2008-08-26 and has_patch = 1 sorted by severity
This data as json, CSV (advanced)
Suggested facets: changetime, stage, component, version, resolution, reporter, needs_better_patch, needs_tests, changetime (date)
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity ▼ | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8551 | 2008-08-26 04:15:55 | 2009-02-21 07:29:21 | 2022-03-06 03:42:33.581527 | Ready for checkin | closed | Testing framework | dev | fixed | Add REMOTE_ADDR: '127.0.0.1' to TestClient environment by default | The fake environment django.test.client.Client sets up is missing REMOTE_ADDR. It could be very safely and accurately defaulted to localhost (127.0.0.1). Luckily this issue is very easy to work around when instantiating the test Client: {{{ c = Client(REMOTE_ADDR='127.0.0.1') }}} | ericholscher | schmichael | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8552 | 2008-08-26 07:49:41 | 2011-09-28 16:12:17 | 2022-03-06 03:42:33.727914 | Unreviewed | closed | contrib.auth | dev | fixed | Use the LOGIN_REDIRECT_URL in auth test views | Use the LOGIN_REDIRECT_URL setting in the login method instead of the hard coded '/accounts/profile/' to respect user settings. | nobody | aeby | auth test views LOGIN_REDIRECT_URL | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8556 | 2008-08-26 12:20:07 | 2011-09-28 16:12:17 | 2022-03-06 03:42:34.277215 | Accepted | closed | Forms | dev | fixed | models.CommaSeperatedIntegerField doesn't return a forms field of any use | CommaSeperatedIntegerField just returns a normal charfield, which obviously preforms no validation that it matches the purpose of the field. | nobody | Alex | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8557 | 2008-08-26 12:59:52 | 2009-02-25 19:51:44 | 2022-03-06 03:42:34.413732 | Design decision needed | closed | Template system | dev | duplicate | intpoint filter for contrib.humanize | for european users would be really useful an intpoint filter in contrib.humanize, here is the necessary code (similar to intcomma) def intpoint(value): """ Converts an integer to a string containing point every three digits. For example, 3000 becomes '3.000' and 45000 becomes '45.000'. """ orig = force_unicode(value) new = re.sub("^(-?\d+)(\d{3})", '\g<1>.\g<2>', orig) if orig == new: return new else: return intpoint(new) intpoint.is_safe = True register.filter(intpoint) hope this would be in 1.0, thanks drakkan | nobody | drakkan | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8560 | 2008-08-26 17:03:57 | 2011-09-28 16:12:17 | 2022-03-06 03:42:34.822350 | Accepted | closed | Documentation | dev | fixed | Small typo in tutorial 2 | A followup to #8392 and [8432], sorry for not noticing it was also present in part 2 of the tutorial. | nobody | ramiro | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8562 | 2008-08-26 18:09:13 | 2011-09-28 16:12:17 | 2022-03-06 03:42:35.101521 | Accepted | closed | contrib.admin | dev | duplicate | OneToOnes + primary_key = True ... fails in Admin | This goes back to the primary keys and missing in the Admin forms as hidden fields, but it also effect 2 things . I've brought this up before #7938 for instance, where a slightly different bug was mended. 1) Addition of an element 2) editing a OneToOne directly {{{ #create a simple model from django.db import models class BaseMoo(models.Model): name = models.CharField(max_length = 50) is_moo = models.BooleanField(default = True) class MooOne(models.Model): basemoo = models.OneToOneField(BaseMoo, primary_key = True) is_moo_one = models.BooleanField(default = True) }}} {{{ #create the ADmin from testmod.models import BaseMoo, MooOne from django.contrib import admin class MooOne_Inline(admin.StackedInline): model = MooOne extra = 1 max_num = 1 raw_id_fields = ('basemoo',) class BaseMooOptions(admin.ModelAdmin): inlines = [MooOne_Inline] list_display = ('name', 'is_moo',) class MooOneOptions(admin.ModelAdmin): raw_id_fields = ('basemoo',) list_display = ('basemoo', 'is_moo_one',) admin.site.register(BaseMoo, BaseMooOptions) admin.site.register(MooOne, MooOneOptions) }}} 1) In Admin, try to 'add' a BaseMoo Object. It will give you the option for the Inlined MooOne, but on save the MooOne object is _not_ saved 2) ok a work around (but assumes that MooOne is registered as not an inline like above), so try to add the MooOne directly buy adding one attached to BaseMoo .. 3) Go back to the BaseMoo object, try to edit and save .. boom {{{ Traceback: File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/django/contrib/admin/sites.py" in root 173. return self.model_page(request, *url.split('/', 2)) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/django/views/decorators/cache.py" in _… | brosner | magneto | admin onetoone | 0 | 1 | 1 | 1 | 0 | 0 | ||
| 8567 | 2008-08-26 19:47:08 | 2010-08-07 07:58:58 | 2022-03-06 03:42:35.838662 | Ready for checkin | closed | Documentation | dev | fixed | Formwizard documentation does not clearly describe how to specify forms | When I read the Form Wizard doc, it took me a lots of searching before the “glue” between Form and FormWizard showed up in the urls.py example a long way down in the document. Why don't put the urls.py much earlier in the document and/or describe the connection. | ElliottM | ClaesBas | Form wizard | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8568 | 2008-08-26 20:17:31 | 2011-09-28 16:12:17 | 2022-03-06 03:42:35.987603 | Accepted | closed | Documentation | dev | fixed | Remove note about missing signals documentation in models doc. | I've attached a patch | nobody | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8570 | 2008-08-26 20:26:12 | 2008-09-14 07:04:40 | 2022-03-06 03:42:36.286147 | Ready for checkin | closed | contrib.formtools | dev | fixed | Wrong indentation style in django/contrib/formtools/utils.py | This file has 8 space padding. This should be 4, as [http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style contributing docs] said | nobody | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8572 | 2008-08-26 21:04:18 | 2008-08-26 22:39:45 | 2022-03-06 03:42:36.604616 | Unreviewed | closed | contrib.admin | dev | duplicate | Improve flexibility of admin.autodiscover for custom admin sites | {{{admin.autodiscover}}} is great, but you cannot customize admin sites. It would be wonderful that you can call autodiscover with a optional {{{site}}} parameter, like this: {{{ #!python # urls.py from django.contrib import admin from yourproject.admin import custom_admin_site admin.autodiscover(site=custom_admin_site) urlpatterns = patterns('', ... ('^admin/(.*)', custom_admin_site.root), }}} I will attach a patch that implement that feature, without backwards incompatibility | msaelices | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8573 | 2008-08-26 21:24:34 | 2008-09-17 05:15:02 | 2022-03-06 03:42:36.735178 | Unreviewed | closed | django-admin.py inspectdb | dev | fixed | inspectdb doesn't make use of FK and uniqueness information when the column name has upper case characters | This was reported as an [http://code.google.com/p/django-pyodbc/issues/detail?id=12 issue] in the [http://code.google.com/p/django-pyodbc/ django-pyodbc] project but after some debugging turned to be a bug in `inspectdb`. Problem is it doesn't use the real database column name but rather a derived `att_name` value (used to represent the final Django model field name) when looking up the meta information about FK and indexes the DB backend provides via the `DatabaseIntrospection.get_relations()` method. This fails for database engines that are case sensitive (i.e. all but Oracle). Also, because of a related problem, it can attempt to use that same innaccurate `att_name` instead of the real table column when trying to introspect the `db_column` field option. Example: This `models.py` file: {{{ #!python class Magazine(models.Model): ident = models.AutoField(primary_key=True, db_column='Ident') class ReaderComment(models.Model): text = models.TextField(max_length=30, primary_key=True, db_column='reader_comment') }}} when `syncdb`ed to the database (sqlite3) and the introspected back gives: {{{ #!python class IntrosBugMagazine(models.Model): ident = models.IntegerField() class Meta: db_table = u'intros_bug_magazine' class IntrosBugReadercomment(models.Model): reader_comment = models.TextField(primary_key=True) class Meta: db_table = u'intros_bug_readercomment' }}} Note the `ident` field of the `Magazine` model is missing: a. The `'primary_key=True'`option(that's because the `syncdb` command didn't make use of the `'primary_key': True` info the database backend introspection support code correctly returned for it.) b. The `db_column='Ident'` option | nobody | ramiro | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8577 | 2008-08-26 22:43:31 | 2011-09-28 16:12:17 | 2022-03-06 03:42:37.379426 | Unreviewed | closed | contrib.admin | dev | fixed | Admin raises UnboundLocalError | {{{ Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/django/core/handlers/base.py", line 86, in get_response response = callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.3/site-packages/django/contrib/admin/sites.py", line 175, in root return self.app_index(request, url) File "/usr/lib/python2.3/site-packages/django/contrib/admin/sites.py", line 392, in app_index app_dict = { UnboundLocalError: local variable 'model_dict' referenced before assignment }}} Code added in [8474] for #1390 produced this error. The untested patch should fix this. | nobody | evenrik | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8578 | 2008-08-26 22:55:41 | 2008-08-28 12:22:33 | 2022-03-06 03:42:37.557976 | Ready for checkin | closed | Documentation | dev | fixed | Typo in testing docs, that also makes bad highlight | The incorrect typo was in this URL: http://docs.djangoproject.com/en/dev/topics/testing/#id1 | nobody | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8580 | 2008-08-26 23:10:29 | 2008-09-07 23:08:02 | 2022-03-06 03:42:37.865574 | Ready for checkin | closed | Documentation | dev | fixed | Missing links to django source files in settings doc. | nobody | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | ||||
| 8581 | 2008-08-26 23:28:44 | 2011-09-28 16:12:17 | 2022-03-06 03:42:38.012703 | Ready for checkin | closed | Documentation | dev | fixed | Obsolete command in whatsnext docs | Now, source docs are in several directories. In whatnext.txt doc there are a {{{grep}}} command now obsolete. Please see the patch. | jacob | msaelices | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8548 | 2008-08-26 00:09:34 | 2016-01-07 01:58:34 | 2022-03-06 03:42:33.166125 | Accepted | closed | Core (Management commands) | Bug | Normal | 1.4 | fixed | Lengthy verbose_name results in fatal mysql 'warning' error during syncdb. | {{{ #!python class Thingie(models.Model) #fields go here class Meta: verbose_name = 'A String Greater Than 50 Characters Long, Probably For The Admin' }}} Running 'python manage.py syncdb' results in MySQLdb trying to run the following: {{{ #!sql INSERT INTO `auth_permission` (`name`, `content_type_id`, `codename`) VALUES (%s, %s, %s)(u'A String Greater Than 50 Characters Long, Probably For The Admin', 11, u'add_thingie') }}} The field `name` has a length restriction of 50 characters. This results in a warning 'error' being generated (_mysql_exceptions.Warning: Data truncated for column 'name' at row 1) but no further useful information. This also halts syncdb, which is also called during the test suite. Suggestions (since I'm nowhere near qualified to contribute, yet): - Maybe just catch the warning and ignore it? This seems to be a display-only field, so it probably won't hurt. - Or maybe catch the warning and explain the cause? - Model validator could complain about verbose_name being too long? - Increase the size of the field? - Maybe just let google index this ticket so that the next person to google the error sees why it happened? {{{ Traceback (most recent call last): File "manage.py", line 11, in <module> execute_manager(settings) File "/usr/local/python-x/lib/python2.5/site-packages/django/core/management/__init__.py", line 334, in execute_manager utility.execute() File "/usr/local/python-x/lib/python2.5/site-packages/django/core/management/__init__.py", line 295, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/python-x/lib/python2.5/site-packages/django/core/management/base.py", line 77, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/local/python-x/lib/python2.5/site-packages/django/core/management/base.py", line 96, in execute output = self.handle(*args, **options) File "/usr/local/python-x/lib/python2.5/site-packages/django/core/management/base.py", line 178, in… | marcelor | samt@darkhorse.com | 0 | 1 | 1 | 0 | 0 | 0 | |
| 8561 | 2008-08-26 18:05:32 | 2014-03-05 23:15:40 | 2022-03-06 03:42:34.953106 | Accepted | closed | contrib.admin | New feature | Normal | dev | fixed | Patсh for Lithuanian support to Javascript slug creation | Path for Lithuanian support to Javascript slug creation in django/contrib/admin/media/js/urlify.js When slug is auto-generated some Lithuanian's letters are missing. So there is a patch for quick fix. Actualy I am not very happy with current auto-generated slug creation, but for quick result it will do the trick. | nobody | petraszd | LITHUANIAN_MAP | 0 | 1 | 1 | 0 | 0 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE tickets (
id int primary key,
created datetime,
changetime datetime,
last_pulled_from_trac datetime,
stage text,
status text,
component text,
type text,
severity text,
version text,
resolution text,
summary text,
description text,
owner text,
reporter text,
keywords text,
easy boolean,
has_patch boolean,
needs_better_patch boolean,
needs_tests boolean,
needs_docs boolean,
ui_ux boolean
);