tickets

22 rows where "changetime" is on date 2011-09-28 and "created" is on date 2008-08-29 sorted by component

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: version, resolution, owner, reporter, has_patch, last_pulled_from_trac (date)

created (date) 1 ✖

  • 2008-08-29 · 22 ✖

changetime (date) 1 ✖

  • 2011-09-28 · 22 ✖
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
8664 2008-08-29 01:16:48 2011-09-28 16:12:17 2022-03-06 03:42:50.990600 Accepted closed Database layer (models, ORM)     dev fixed PhoneNumberField should be moved to django.contrib.localflavor.us Like ''russelm'' [http://code.djangoproject.com/ticket/8210#comment:4 has mentioned] in #8210 - `PhoneNumberField` should be moved to `django.contrib.localflavor.us`. After closing this ticket and #8210 there would be no references to `django.contrib.localflavor` from Django code (excluding `django/contrib/localflavor` directory itself). jacob Piotr Lewandowski <django@icomputing.pl> us localflavor 0 1 0 0 0 0
8668 2008-08-29 06:52:18 2011-09-28 16:12:17 2022-03-06 03:42:51.572172 Unreviewed closed Database layer (models, ORM)     dev fixed Serializer regressions tests broken with MySQL Looks like [8676] had some side-effects. The serializer regressions tests (`serializers_regress`) are broken on MySQL and worked before it. I haven't looked any further than just bisecting down to the problem commit (I thought it was something else I'd done tonight). But if I don't file this now, there'll be a ticket opened in the morning by the Florida Testing Society. Just saving some time by doing it now. nobody mtredinnick   0 0 0 0 0 0
8669 2008-08-29 08:15:02 2011-09-28 16:12:17 2022-03-06 03:42:51.725361 Accepted closed Database layer (models, ORM)     dev fixed All remaining create() methods also force an insert (continuation of r8670) #8419 / [8670] forced an SQL insert in the main create() and get_or_create() methods, preventing data loss from overwriting existing data - thanks Malcolm! All other get_or_create() methods end up calling back to the main get_or_create(). However, there are a few extra create() methods which don't call back to the main create() - this patch ensures that those also force an insert, so cannot overwrite existing data. Extra methods found via "find django -name '*.py' | xargs grep -F 'def create('" and "find django -name '*.py' | xargs grep -F 'def get_or_create('" nobody Richard Davies <richard.davies@elastichosts.com>   0 1 0 0 0 0
8683 2008-08-29 12:45:21 2011-09-28 16:12:17 2022-03-06 03:42:54.127760 Accepted closed Database layer (models, ORM)     dev fixed NameError caused by typo in DateQuerySet._setup_query In `!DateQuerySet._setup_query` there is an `assert` whose second expression refers to a non-existent name ("`field_name`"). I modified it to be "`field.name`" mtredinnick vung   0 0 0 0 0 0
8662 2008-08-29 00:16:02 2011-09-28 16:12:17 2022-03-06 03:42:50.720441 Unreviewed closed Documentation     dev fixed Overriding save() raises error when using Model.objects.create() It seems that when over writing .save() (and maybe other default methods) you should be accepting *args, **kwargs and passing it along. I get an exception when using Model.objects.create(): Traceback: File "/usr/local/lib/python2.5/site-packages/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/home/pjs/site/netlandish/../netlandish/ccproc/views.py" in order_process 41. form_data.get('custom', '') File "/home/pjs/site/netlandish/../netlandish/billing/helpers.py" in build_sale 48. ip=ip File "/usr/local/lib/python2.5/site-packages/django/db/models/manager.py" in create 87. return self.get_query_set().create(**kwargs) File "/usr/local/lib/python2.5/site-packages/django/db/models/query.py" in create 311. obj.save(force_insert=True) Exception Type: TypeError at /order/1027/ Exception Value: save() got an unexpected keyword argument 'force_insert' My custom .save() didn't have anything catching force_insert.. The docs don't show this is required. nobody pjs   0 0 0 0 0 0
8667 2008-08-29 06:20:52 2011-09-28 16:12:17 2022-03-06 03:42:51.426809 Unreviewed closed Documentation     dev duplicate Revive model inheritance documentation So I don't forget: the model inheritance documentation seems to have been dropped during the docs merge. So we have to extract that out of the old models-api.txt. There was quite a bit of it, mostly all in one block towards the end of the file. Plus a couple of references earlier (e.g. in the related name section). nobody mtredinnick   0 0 0 0 0 0
8679 2008-08-29 11:42:11 2011-09-28 16:12:17 2022-03-06 03:42:53.287009 Accepted closed Documentation     dev fixed Custom save() method signature needs to be fixed in some tests and docs after changeset 8670 Changeset r8670 change the way create() and get_or_create() methods work. Examples in documentation does not reflect this change yet. nobody Uninen documentation, save, create, get_or_create 0 1 0 0 0 0
8693 2008-08-29 18:25:21 2011-09-28 16:12:17 2022-03-06 03:42:55.782313 Accepted closed Documentation     dev fixed docs: missing blank line causes uneven rendering The `null` model field option is rendered in bold fonts here http://docs.djangoproject.com/en/dev/topics/db/models/#field-options, fiving it a different appearance from the rest of the options. nobody ramiro   0 0 0 0 0 0
8696 2008-08-29 19:33:15 2011-09-28 16:12:17 2022-03-06 03:42:56.253769 Accepted closed Documentation     1.0-beta fixed Online docs using incorrect apostrophe character The online docs at http://docs.djangoproject.com/en/dev/intro/tutorial02/#intro-tutorial02 are using incorrect characters for apostrophes. The example url patterns {{{ urlpatterns = patterns(‘’, # Example: # (r’^{{ project_name }}/’, include(‘{{ project_name }}.foo.urls’)), # Uncomment the next line to enable admin documentation: # (r’^admin/doc/’, include(‘django.contrib.admindocs.urls’)), # Uncomment the next line to enable the admin: (r’^admin/(.*)’, admin.site.root), ) }}} cannot be cut and pasted because they are using ’ instead of ' to delimit their strings. You'll notice that the code color-coding is incorrect. A search for ".. parsed-literal::" in the source turned up five hits; these four files show this problem with delimiters: {{{ docs/intro/tutorial02.txt docs/howto/deployment/modpython.txt docs/howto/custom-template-tags.txt docs/howto/apache-auth.txt }}} It looks like parsed-literal is the wrong tag to use here. jacob jjackson   0 1 0 0 0 0
8698 2008-08-29 21:54:11 2011-09-28 16:12:17 2022-03-06 03:42:56.607366 Unreviewed closed Documentation     dev fixed Middleware Documentation still refers to CacheMiddleware On the Cache documentation page, it says you have to use UpdateCacheMiddleware and FetchFromCacheMiddleware instead of the older CacheMiddleware. However the Middleware documentation only mentions CacheMiddleware and does not discuss the two new middlewares. nobody anonymous middleware, cache 0 1 0 0 0 0
8700 2008-08-29 23:43:38 2011-09-28 16:12:17 2022-03-06 03:42:56.915977 Ready for checkin closed Documentation     dev fixed Localflavor example code broken The doc fix in [7961] was reverted by [7967]. nobody mattmcc   0 1 0 0 0 0
8673 2008-08-29 09:17:31 2011-09-28 16:12:17 2022-03-06 03:42:52.325970 Accepted closed File uploads/storage     dev fixed Missing import in django.core.files.move In [8493] the copied `copystat` in django.core.files.move uses `stat.S_IMODE`, but `stat` is not imported. nobody vung   0 1 0 0 0 0
8663 2008-08-29 01:07:00 2011-09-28 16:12:17 2022-03-06 03:42:50.857469 Design decision needed closed Forms     dev wontfix Inconsistencies/Bug in ModelForm When a ModelForm is used to display a form for a Model, the fields defined with a choices option insert a "-------" value for the first option when the form is rendered. If you override a field and manually specify the choices for a Select widget, this "-------" does not appear as the first choice. {{{ # models.py from django.db import models MY_CHOICES = ( (0, 'Zero'), (1, 'One'), ) class MyModel(models.Model): my_field = models.IntegerField(choices=MY_CHOICES) }}} {{{ # forms.py from django import forms from myapp.models import MyModel, MY_CHOICES class MyModelForm(forms.ModelForm): #my_field = forms.IntegerField(widget=forms.Select(choices=MY_CHOICES)) class Meta: model = MyModel }}} View the HTML for the form with my_field commented out: {{{ >>> from myapp.forms import MyModelForm >>> f = MyModelForm() >>> print f <tr><th><label for="id_my_field">My field:</label></th><td><select name="my_field" id="id_my_field"> <option value="" selected="selected">---------</option> <option value="0">Zero</option> <option value="1">One</option> </select></td></tr> }}} Now uncomment my_field in MyModelForm: {{{ >>> from myapp.forms import MyModelForm >>> f = MyModelForm() >>> print f <tr><th><label for="id_my_field">My field:</label></th><td><select name="my_field" id="id_my_field"> <option value="0">Zero</option> <option value="1">One</option> </select></td></tr> }}} This value doesn't appear in the 2nd case: <option value="" selected="selected">---------</option> SVN-8643 nobody lingrlongr ModelForm forms 0 0 0 0 0 0
8680 2008-08-29 12:32:57 2011-09-28 16:12:17 2022-03-06 03:42:53.414224 Unreviewed closed GIS     dev fixed gis may break Python help() modules command As reported here: http://groups.google.com/group/django-users/browse_thread/thread/47529751d7a82fee?hl=en# This is similar to #5743 and perhaps could use a similar approach to fix? nobody kmtracey   0 0 0 0 0 0
8687 2008-08-29 15:25:18 2011-09-28 16:12:17 2022-03-06 03:42:54.820034 Unreviewed closed Metasystem     dev fixed NameError when validating m2m models Found this while monkeying around with pyflakes: `'django/core/management/validation.py:134: undefined name 'rel_from'` nobody vung   0 1 0 0 0 0
8665 2008-08-29 01:59:02 2011-09-28 16:12:17 2022-03-06 03:42:51.134763 Accepted closed Translations     dev fixed Update Polish translations Changelog: * Translate strings from [8679]. * Remove obsolete strings after `oldforms` removal. * Remove some fuzziness. zgoda Piotr Lewandowski <django@icomputing.pl> pl polish 0 1 0 0 0 0
8689 2008-08-29 16:32:44 2011-09-28 16:12:17 2022-03-06 03:42:55.159257 Accepted closed Translations     dev fixed Update russian translation Update Russian translation django.po and djangojs.po. nobody greg russian translation 0 0 0 0 0 0
8697 2008-08-29 21:03:34 2011-09-28 16:12:17 2022-03-06 03:42:56.414327 Unreviewed closed Translations     dev fixed Norwegian translation ready for 1.0 The Norwegian translation should now be ready for 1.0! All the localflavours are now translated (where applicable) + the new comments framework. nobody jonklo norwegian 0 1 0 0 0 0
8692 2008-08-29 17:34:53 2011-09-28 16:12:17 2022-03-06 03:42:55.644970 Unreviewed closed Uncategorized     dev fixed Add myself to AUTHORS Add myself to authors brosner bastih   0 0 0 0 0 0
8674 2008-08-29 09:38:51 2011-09-28 16:12:17 2022-03-06 03:42:52.508199 Unreviewed closed contrib.admin     dev duplicate OneToOne Fields display problem in admin gui This bug is for SVN 8696. I created the following simple !OneToOneField model: {{{ class Man(models.Model): name = models.CharField(max_length=10) def __unicode__(self): return self.name class Woman(models.Model): name = models.CharField(max_length=10) man = models.OneToOneField(Man) def __unicode__(self): return self.name }}} e.g., a woman is married to one man. If I register both models with admin.site.register and start editing them via administration I can add woman to man 1:1 relations, however if I start editing my womens objects again I get "--------" instead of my related man object shown in the select box. Within the database the OneToOneField data looks ok. nobody nekron OneToOne 0 0 0 0 0 0
8694 2008-08-29 18:39:15 2011-09-28 16:12:17 2022-03-06 03:42:55.931624 Accepted closed contrib.admin     dev fixed Change page for model with a OneToOne field doesn't display related field value This ticket is an attempt to state one simple re-creatable problem so as to simplify the tangled issues raised in #8241 and #8562. Given these models: {{{ from django.db import models # Create your models here. class Parent(models.Model): name = models.CharField(max_length=50) def __unicode__(self): return self.name class Child(models.Model): name = models.CharField(max_length=50) parent = models.OneToOneField(Parent, primary_key=True) def __unicode__(self): return '%s, child of %s' % (self.name, unicode(self.parent)) }}} and this admin.py: {{{ from django.contrib import admin from inlinet1.models import Parent, Child class ParentAdmin(admin.ModelAdmin): list_display = ('name',) class ChildAdmin(admin.ModelAdmin): list_display = ('name', 'parent',) admin.site.register(Parent, ParentAdmin) admin.site.register(Child, ChildAdmin) }}} From the admin: 1 - Select Add on Parents, fill in name, save 2 - Select Add on Childs, fill in name, select parent from 1, select "Save and continue editing" On re-display of the change page, the select box widget for 'Parent' will be set to '-----'. This was introduced by the fix for #7888 and may be fixed by one of the patches on #8241, Brian understands that better than I. brosner kmtracey   0 0 0 0 0 0
8695 2008-08-29 18:47:42 2011-09-28 16:12:17 2022-03-06 03:42:56.077369 Accepted closed contrib.admin     dev fixed KeyError on save of model with inline-edited OneToOne sharing primary key This ticket is an attempt to state one simple re-creatable problem so as to simplify the tangled issues raised in #8241 and #8562. Given these models: {{{ from django.db import models # Create your models here. class Parent(models.Model): name = models.CharField(max_length=50) def __unicode__(self): return self.name class Child(models.Model): name = models.CharField(max_length=50) parent = models.OneToOneField(Parent, primary_key=True) def __unicode__(self): return '%s, child of %s' % (self.name, unicode(self.parent)) }}} and this admin.py: {{{ from django.contrib import admin from inlinet1.models import Parent, Child class ChildInline(admin.StackedInline): model = Child max_num = 1 class ParentAdmin(admin.ModelAdmin): inlines = [ChildInline] list_display = ('name',) class ChildAdmin(admin.ModelAdmin): list_display = ('name', 'parent',) admin.site.register(Parent, ParentAdmin) admin.site.register(Child, ChildAdmin) }}} From the admin: 1 - Select Add on Parents, fill in parent name & inline-edited child name, select "Save and continue editing" 2 - Select "Save and continue editing" again and you'll get an exception: {{{ Environment: Request Method: POST Request URL: http://localhost:8888/admin/inlinet1/parent/3/ Django Version: 1.0-beta_2-SVN-8712 Python Version: 2.5.1 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.admin', 'django.contrib.redirects', 'playground.inlinet1'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.middleware.doc.XViewMiddleware', 'django.middleware.transaction.TransactionMiddleware') Traceback: File "/home/kmt/tmp/django/trunk/django/core/handlers/base.py" in get_response 86. … brosner kmtracey   0 0 0 0 0 0

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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
    );