tickets
23 rows where "created" is on date 2008-08-29 and stage = "Unreviewed" sorted by description
This data as json, CSV (advanced)
Suggested facets: changetime, component, resolution, owner, reporter, has_patch
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 | |||
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 | |||
8666 | 2008-08-29 04:35:37 | 2008-08-29 05:01:56 | 2022-03-06 03:42:51.289362 | Unreviewed | closed | Core (Management commands) | dev | duplicate | no startproject in django-admin.py | I just updated the checkout and now when I try to django-admin.py startproject, it says that this is an unknown command. If I use help to list the available commands, startproject is not on the list. | nobody | labtjd | startproject | 0 | 0 | 0 | 0 | 0 | 0 | ||
8688 | 2008-08-29 16:22:46 | 2008-10-06 08:44:41 | 2022-03-06 03:42:54.994220 | Unreviewed | closed | Documentation | dev | fixed | Small change on documentation for static media serving | I'd like to suggest a small change to the documentation on http://docs.djangoproject.com/en/dev/howto/static-files/#limiting-use-to-debug-true which would be adding a variable like settings.MEDIA_DEVELOPMENT_ROOT instead of using an hardcoded path on the urls.py for development purposes. This is a much better way for different developers to work on the same project with only different settings.py files. | nobody | trodrigues | static media files | 0 | 1 | 0 | 0 | 0 | 0 | ||
8682 | 2008-08-29 12:39:15 | 2008-08-29 15:50:16 | 2022-03-06 03:42:53.961792 | Unreviewed | closed | contrib.admin | dev | invalid | Admin ordering works incorrectly if ModelAdmin.ordering has several fields, and one of them is an another Model field | If I create two dependent models, and ask the admin interface to order instances of the dependent Model based on the field of the base Model AND on its own field, the secondary ordering is lost. See minimalistic example: {{{ #!python class Foo(models.Model): is_active = models.BooleanField(default=True) class Bar(models.Model): foo = models.OneToOneField(Foo, primary_key=True) name = models.CharField(max_length=100) def __unicode__(self): return "%s, %s" % (self.name, "active" if self.foo.is_active else "inactive") # ... class BarAdmin(admin.ModelAdmin): list_display = ('name',) ordering = ('-foo__is_active', 'name') admin.site.register(Bar, BarAdmin) }}} {{{ insert into app_foo set is_active=1; insert into app_foo set is_active=1; insert into app_foo set is_active=1; insert into app_bar values (1,'aaaa'); insert into app_bar values (1,'ccc'); insert into app_bar values (1,'bbb'); }}} If we run a manual query, it works as expected: {{{ >>> Bar.objects.order_by('-foo__is_active', 'name') [<Bar: aaaa, active>, <Bar: bbb, active>, <Bar: ccc, active>] }}} However, the admin page at http://my.site/admin/app/bar/ would display: {{{ aaa ccc bbb }}} which means the ordering was lost. If both fields are in the same model, everything works fine. Django version is [8696]. | nobody | semenov | newforms-admin admin ordering | 0 | 0 | 0 | 0 | 0 | 0 | ||
8681 | 2008-08-29 12:34:35 | 2009-02-25 20:58:46 | 2022-03-06 03:42:53.790898 | Unreviewed | closed | Core (Other) | dev | invalid | Uncaught exception in django/db/models/base.py: UnboundLocalError | In source:django/trunk/django/db/models/base.py as of [8696], lines 197-203: {{{ #!python for field in fields_iter: rel_obj = None if kwargs: if isinstance(field.rel, ManyToOneRel): try: # Assume object instance was passed in. rel_obj = kwargs.pop(field.name) }}} If kwargs[field.name] is None, rel_obj is set to None, val is not set at all, and we get an UnboundLocalError at line 226. Context: the model in question had a OneToOneField whose primary_key was not yet set/was set to None and a save() was attempted. See stacktrace at dpaste: http://dpaste.com/74655/ Either we need to have a better error-message here, for instance mentioning what field is the problem and how it can be fixed, or the code needs to do something sensible. | nobody | HM <hanne.moa@gmail.com> | models, onetoonefield | 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 | |||
8686 | 2008-08-29 15:01:49 | 2009-02-25 20:59:13 | 2022-03-06 03:42:54.661969 | Unreviewed | closed | Documentation | dev | invalid | Example of permissions to edit/delete a particular object | It would be nice to give an example of permissions to edit/delete/etc. a particular object, since this is a common scenario. | nobody | anonymous | 0 | 0 | 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 | |||
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 | ||
8699 | 2008-08-29 23:19:37 | 2008-08-30 03:50:26 | 2022-03-06 03:42:56.757397 | Unreviewed | closed | Translations | dev | fixed | Translated post-string freeze strings for Hungarian | See the attached diff. Sorry for the cruft, but a large number of comment lines were messed up during the POT generation, and others are just KBabel's stupidity. | nobody | szilveszter | 0 | 1 | 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 | |||
8676 | 2008-08-29 10:24:03 | 2008-08-29 10:33:05 | 2022-03-06 03:42:52.830715 | Unreviewed | closed | Uncategorized | dev | wontfix | BooleanField says value required if False | The BooleanField should accept False values and not raise the required error. Here is a diff from the http://code.djangoproject.com/svn/django/tags/notable_moments/1.0-beta-1 branch. The problem is in trunk too. {{{ Index: django/forms/fields.py =================================================================== --- django/forms/fields.py (revision 8696) +++ django/forms/fields.py (working copy) @@ -569,9 +569,9 @@ if value == 'False': value = False else: - value = bool(value) + value = value and True or None super(BooleanField, self).clean(value) - if not value and self.required: + if value is None and self.required: raise ValidationError(self.error_messages['required']) return value }}} | nobody | dobee | forms | 0 | 1 | 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 | ||
8675 | 2008-08-29 09:44:21 | 2008-08-29 09:52:49 | 2022-03-06 03:42:52.683218 | Unreviewed | closed | Documentation | dev | duplicate | File storage - Storage objects example does not work | The example at the beginning of http://www.djangoproject.com/documentation/files/#storage-objects does not work. {{{ >>> from django.core.files.storage import default_storage >>> path = default_storage.save('/path/to/file', 'new content') }}} will give you an error: {{{ <type 'exceptions.AttributeError'>: 'str' object has no attribute 'chunks' }}} The way to fix is to pass ContentFile('new content') from django.core.files.base. In fact, other examples should be double checked if they expect a string or a ContentFile-like object. See http://groups.google.com/group/django-users/browse_thread/thread/230a8601a4839bd9 for more information. | nobody | whiskybar | 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 | ||
8685 | 2008-08-29 13:46:42 | 2008-08-29 17:49:11 | 2022-03-06 03:42:54.473038 | Unreviewed | closed | Translations | dev | fixed | Portuguese translation patch | This is a Portuguese translation update. I'm sending the patch and the .po files, just in case. | nobody | nmariz | 0 | 1 | 0 | 0 | 0 | 0 | |||
8671 | 2008-08-29 08:44:10 | 2008-08-29 16:57:23 | 2022-03-06 03:42:52.025743 | Unreviewed | closed | Core (Other) | dev | worksforme | django.views.static.serve shoud have APPEND_SLASH=True | When running debug server with some .js .css file using django.views.static.serve while 'show_indexes': True, example, navigate to http://127.0.0.1:8000/images when click a 1.jpg listed bellow, I was navigate to http://127.0.0.1:8000/1.jpg But what I desired URL is http://127.0.0.1:8000/images/1.jpg The problem is we should set APPEND_SLASH=True as default here in django.views.static.serve | nobody | est | static | 0 | 0 | 0 | 0 | 0 | 0 | ||
8677 | 2008-08-29 10:28:54 | 2008-08-29 10:55:01 | 2022-03-06 03:42:52.968880 | Unreviewed | closed | contrib.admin | dev | duplicate | admin redirect when "save" doesn't account for previous querystring (e.g: search) | When saving a model edited coming from a list page where a search was performed, (i.e. with ?q=<search_text>), admin redirects to the list page without the querystring. If the user is editing a series of common objects within a big list, it is forced to perform the same search again and again with every 'save'. | nobody | gogna | 0 | 0 | 0 | 0 | 0 | 0 | |||
8684 | 2008-08-29 13:41:05 | 2008-08-31 23:22:45 | 2022-03-06 03:42:54.301351 | Unreviewed | closed | contrib.admin | invalid | Adding custom (succes/failure) messages to the admin site | When you for example save a new object in the admin site this small yellow bar on top will appear telling you "everything's saved correctly". It would be very useful if you were able to create your own custom messages here. | nobody | metzeltiger | message, notification | 0 | 0 | 0 | 0 | 0 | 0 | |||
8691 | 2008-08-29 17:17:39 | 2008-08-29 17:23:27 | 2022-03-06 03:42:55.508704 | Unreviewed | closed | Uncategorized | dev | wontfix | link to beta/dev doc in main documentation page | hi, you might want to add a link to beta documentation (http://docs.djangoproject.com/en/dev/) in the main documentation page (http://www.djangoproject.com/documentation/) at the bottom of the page with the other versions. lookin quite nice otherwise! thx much ;) | nobody | mamat | 0 | 0 | 0 | 0 | 0 | 0 | |||
8678 | 2008-08-29 11:04:50 | 2009-02-25 19:51:44 | 2022-03-06 03:42:53.128356 | Unreviewed | closed | contrib.auth | dev | invalid | errors with custom profile | if profile model is placed somewhere else than in root dir django has 'ValueError at /users/profil/ too many values to unpack' in /home/grono3/python/django/contrib/auth/models.py in get_profile, line 292 | nobody | slowik | 0 | 0 | 0 | 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 );