tickets
45 rows where "created" is on date 2008-09-08
This data as json, CSV (advanced)
Suggested facets: stage, status, component, type, owner, reporter, keywords, has_patch, needs_better_patch, needs_docs, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8936 | 2008-09-08 01:10:41 | 2018-08-17 15:37:27 | 2022-03-06 03:43:33.780505 | Ready for checkin | closed | contrib.admin | New feature | Normal | dev | fixed | Add view (read-only) permission to admin | Adrian and Jacob on stage at DjangoCon. | olivierdalang | simon | 0 | 1 | 0 | 0 | 0 | 0 | |
8937 | 2008-09-08 01:10:59 | 2008-09-08 16:01:30 | 2022-03-06 03:43:33.907195 | Accepted | closed | contrib.admin | 1.0 | duplicate | Multi-delete in the admin changelist | Adrian and Jacob on stage at DjangoCon. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8938 | 2008-09-08 01:11:14 | 2009-02-25 22:39:44 | 2022-03-06 03:43:34.063237 | Unreviewed | closed | Database layer (models, ORM) | 1.0 | invalid | A nice API for multi-db support | Adrian and Jacob on stage at DjangoCon. | nobody | simon | 0 | 0 | 0 | 0 | 0 | 0 | |||
8939 | 2008-09-08 01:11:28 | 2011-09-28 16:12:20 | 2022-03-06 03:43:34.214308 | Accepted | closed | Uncategorized | 1.0 | fixed | Editable fields on the changelist view in the admin | Adrian and Jacob on stage at DjangoCon. | nobody | simon | 0 | 0 | 0 | 0 | 0 | 0 | |||
8940 | 2008-09-08 01:13:41 | 2013-02-11 00:01:53 | 2022-03-06 03:43:34.372000 | Accepted | closed | Documentation | New feature | Normal | duplicate | A mechanism for managing official translations of the documentation | Adrian and Jacob on stage at DjangoCon. | jacob | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | |
8941 | 2008-09-08 01:14:51 | 2009-02-25 22:41:48 | 2022-03-06 03:43:34.542887 | Unreviewed | closed | Uncategorized | 1.0 | invalid | Shared identity across all of the different Django community sites | Adrian and Jacob on stage at DjangoCon. | ericholscher | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8942 | 2008-09-08 01:29:04 | 2008-10-06 03:44:10 | 2022-03-06 03:43:34.687607 | Unreviewed | closed | Uncategorized | 1.0 | invalid | Django should have the best debugging and profiling tools of any web framework | Adrian and Jacob on stage at DjangoCon. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8943 | 2008-09-08 01:30:16 | 2009-02-25 22:42:11 | 2022-03-06 03:43:34.840631 | Unreviewed | closed | Uncategorized | 1.0 | fixed | Discuss starting to phase out support for Python 2.3 | Adrian and Jacob on stage at DjangoCon. Jacob: "If there's some distro being used by millions of people maybe we won't do this just yet, but we need to start getting ready for Python 2.6 and the eventual migration to Python 3. Guido says we have 5 years". | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8944 | 2008-09-08 01:34:07 | 2009-02-25 22:44:19 | 2022-03-06 03:43:34.973347 | Unreviewed | closed | Documentation | 1.0 | invalid | Documentation should go further than just your first application | Adrian and Jacob on stage at DjangoCon. Adrian: "maybe we should link to a video of James' DjangoCon talk at the end of the tutorial" | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8945 | 2008-09-08 01:36:36 | 2009-02-25 22:48:53 | 2022-03-06 03:43:35.132222 | Unreviewed | closed | Uncategorized | 1.0 | invalid | Better links from the Django docs to community tutorials | Adrian and Jacob on stage at DjangoCon. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8946 | 2008-09-08 01:38:27 | 2013-01-18 05:31:56 | 2022-03-06 03:43:35.309540 | Someday/Maybe | closed | Database layer (models, ORM) | New feature | Normal | 1.0 | wontfix | Denormalisation built in to the ORM | Adrian and Jacob on stage at DjangoCon. See also Cal's talk. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 |
8947 | 2008-09-08 01:40:49 | 2013-02-11 21:29:41 | 2022-03-06 03:43:35.488891 | Unreviewed | closed | Uncategorized | Uncategorized | Normal | 1.0 | duplicate | A way to have non-editable fields in the admin | Adrian and Jacob on stage at DjangoCon. | nobody | simon | DjangoCon | 0 | 0 | 0 | 0 | 0 | 0 |
8948 | 2008-09-08 01:41:23 | 2008-09-08 13:20:16 | 2022-03-06 03:43:35.652572 | Unreviewed | closed | Uncategorized | 1.0 | duplicate | Namespaces for template tags | Adrian and Jacob on stage at DjangoCon. Jacob: "it's going to be really hard to do without breaking backwards compatibility" | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8949 | 2008-09-08 01:41:51 | 2012-12-16 13:31:02 | 2022-03-06 03:43:35.806075 | Someday/Maybe | closed | Uncategorized | New feature | Normal | 1.0 | fixed | A django-stones benchmark | Adrian and Jacob on stage at DjangoCon. A holistic benchmark so we know if changes are speeding things up or slowing it down. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 1 | 0 |
8950 | 2008-09-08 01:42:48 | 2012-01-02 19:51:48 | 2022-03-06 03:43:35.965778 | Someday/Maybe | closed | Core (Other) | New feature | Normal | 1.0 | fixed | django.shortcuts should be better, less boilerplate in views.py please | Adrian and Jacob on stage at DjangoCon. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 |
8951 | 2008-09-08 01:43:21 | 2009-02-25 22:51:02 | 2022-03-06 03:43:36.125596 | Unreviewed | closed | Template system | 1.0 | invalid | Better support for writing more complex template tags | Adrian and Jacob on stage at DjangoCon. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8952 | 2008-09-08 01:49:43 | 2015-08-28 21:02:35 | 2022-03-06 03:43:36.289797 | Someday/Maybe | closed | contrib.sites | New feature | Normal | dev | wontfix | Refactor a Django "site" to be just another view function | At the moment middleware applies globally (unless you use the decorator_from_middleware hack). A Django powered site is essentially a thing that takes an HTTP request and returns an HTTP response. We should refactor things a bit so the highlest level of a Django site is just another view, which can compose bits of middleware and a URL dispatcher. This way Django applications end up composed of nested view functions, URL dispatchers and middleware which is really elegant. It won't be easy to do this due to lots of existing code expecting things to be how they are at the moment, but it's worth investigating. | Y3K | simon | 0 | 0 | 0 | 0 | 0 | 0 | |
8953 | 2008-09-08 01:58:47 | 2009-02-25 22:52:04 | 2022-03-06 03:43:36.458408 | Unreviewed | closed | Uncategorized | 1.0 | duplicate | Timezone support at the model level | This should probably rely on dateutil and/or pytz - so you wouldn't be able to use !DateTimeTzField without having those installed. | nobody | simon | djangocon | 0 | 0 | 0 | 0 | 0 | 0 | ||
8954 | 2008-09-08 02:07:12 | 2008-09-08 02:23:52 | 2022-03-06 03:43:36.643880 | Unreviewed | closed | Template system | queryset-refactor | invalid | [SPAM] | [SPAM] | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
8955 | 2008-09-08 04:52:51 | 2008-09-18 15:46:20 | 2022-03-06 03:43:36.808882 | Unreviewed | closed | Documentation | 1.0 | fixed | Latex Document Empty | The sphinx generated latex document is empty. If the conf.py file is changed to reference 'contents' as opposed to 'index' for latex_documents, as below, then at least the generated file has some content: latex_documents = [ ('contents', 'django.tex', 'Django Documentation', 'Django Software Foundation', 'manual'), ] | nobody | simonb | latex | 0 | 0 | 0 | 0 | 0 | 0 | ||
8956 | 2008-09-08 05:29:00 | 2008-10-06 03:42:53 | 2022-03-06 03:43:36.967626 | Unreviewed | closed | Uncategorized | 1.0 | invalid | doctests should not be used in regular documentation outside the orm | The forms docs for example really shouldn't be using doctest style. | nobody | simon | 0 | 0 | 0 | 0 | 0 | 0 | |||
8957 | 2008-09-08 06:14:29 | 2008-09-15 11:12:02 | 2022-03-06 03:43:37.129534 | Unreviewed | closed | contrib.admin | dev | fixed | Typo in Admin validation exception message | If a prepopulated_fields value refers to a nonexistant field, the error message is in correct. So for: {{{ prepopulated_fields = {'slug': ['field_which_doesnt_exist']} }}} The error raised is: {{{ 'SomeAdmin.prepopulated_fields['field_which_doesnt_exist'][0]' refers to field 'field_which_doesnt_exist' that is missing from model 'Release'. }}} The expected error should finger 'slug' as the key with the offending source field: {{{ 'SomeAdmin.prepopulated_fields['slug'][0]' refers to field 'field_which_doesnt_exist' that is missing from model 'Release'. }}} This is a simple typo. Fix attached. | nobody | charmless | 0 | 1 | 0 | 0 | 0 | 0 | |||
8958 | 2008-09-08 06:56:00 | 2008-09-09 19:53:57 | 2022-03-06 03:43:37.294371 | Unreviewed | closed | Documentation | 1.0 | fixed | Typo in [8980] | In the cache documentation, the rewording got changed to ..that doesn't support the them.. I've removed 'the' | nobody | benwalton@gmail.com | 0 | 1 | 0 | 0 | 0 | 0 | |||
8959 | 2008-09-08 07:06:45 | 2009-02-25 19:51:44 | 2022-03-06 03:43:37.452292 | Accepted | closed | contrib.comments | dev | fixed | Remove calls to escape in new comments framework templates | As autoescaping is in place with current Django, escaping values in templates is not necessary. Attached patch fixes this. | adrian | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8960 | 2008-09-08 07:33:52 | 2011-09-28 16:12:27 | 2022-03-06 03:43:37.639961 | Accepted | closed | Contrib apps | 1.1 | fixed | "View on site" does not work if contrib.sites is not installed | Code in django.conf.urls.defaults.shortcut expect that contrib.sites is installed and throws error "no such table: django_sites" otherwise. | adrian | bmihelac | 0 | 1 | 0 | 1 | 0 | 0 | |||
8961 | 2008-09-08 07:36:15 | 2018-08-16 10:15:44 | 2022-03-06 03:43:37.822479 | Unreviewed | closed | Core (Mail) | Uncategorized | Normal | 1.0 | wontfix | Add support for sending emails directly through MTA | What I'm volunteering to do is to add support for sending email directly through the MTA (i.e.: {{{/usr/bin/sendmail}}} or whatever). | kratorius | kratorius | mail, email | 0 | 0 | 0 | 0 | 0 | 0 |
8962 | 2008-09-08 08:40:25 | 2012-01-09 09:29:07 | 2022-03-06 03:43:37.994120 | Accepted | closed | Forms | Uncategorized | Normal | dev | fixed | Make `input_formats` and `format` work consistently across `date`, `datetime`, and `time` fields and widgets. | Currently, there are some inconsistencies in what form fields and widgets we have available for `date`, `datetime`, and `time` data. There are also inconsistencies in how the `format` argument applies to the widgets, and the `input_formats` applies to the fields. 1. `DateTimeInput` and `TimeInput` exist, `DateInput` doesn't. 2. `DateTimeInput` accepts `format`, but `TimeInput` doesn't. 3. `SplitDateTimeField` doesn't use `SplitDateTimeWidget` by default. 4. `SplitDateTimeField` doesn't allow the user to specify `input_formats`. 5. `SplitDateTimeWidget` uses two `TextInput` widgets, instead of `TimeInput` and the missing `DateInput` (and thus doesn't allow the user to specify `formats`). 6. `django.contrib.localflavor.generic.forms` is missing `SplitDateTimeField`. 7. The documentation is sparse on detail for `SplitDateTimeField`, `DateTimeInput` and `TimeInput`. This patch: 1. Adds `DateInput`, which accepts `format`, and is used for `DateField` by default. 2. Adds `format` as an argument to `TimeInput`. 3. Uses `SplitDateTimeWidget` for `SplitDateTimeField` by default. 4. Adds `input_date_formats` and `input_time_formats` as arguments to `SplitDateTimeField`. 5. Uses `DateInput` and `TimeInput` for `SplitDateTimeWidget`, and passes through `date_format` and `time_format` through to `DateInput` and `TimeInput` as `format`, respectively. 6. Adds `SplitDateTimeField` to `django.contrib.localflavor.generic.forms`. 7. Adds documentation for all of these changes. 8. Adds tests for all of these changes. | kmtracey | mrmachine | datetime format widget i18n-rf | 0 | 1 | 0 | 0 | 0 | 0 |
8963 | 2008-09-08 09:06:13 | 2009-02-25 19:51:44 | 2022-03-06 03:43:38.159995 | Accepted | closed | contrib.comments | dev | fixed | Comments framework should use standard decorators where possible | Comments framework uses custom method for assuring proper HTTP method is used in view breaking DRY principle. Attached patch fixes this issuel | nobody | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8964 | 2008-09-08 09:31:10 | 2008-10-05 06:56:15 | 2022-03-06 03:43:38.332198 | Unreviewed | closed | Documentation | 1.0 | fixed | InnoDB is default with Windows Essentials installer for MySQL 5.0 (Community server) | The "Storage engines" section in "Notes about supported databases" (http://docs.djangoproject.com/en/dev/ref/databases/#storage-engines) says unconditionally that MyISAM is the default storage engine for MySQL 5.0. This is not so, at least for MySQL 5.0 installed with the Windows Essentials installer (see http://dev.mysql.com/doc/refman/5.0/en/innodb-overview.html); my experience confirms the MySQL doc's statement for the Community Server install. | nobody | Jerzy.Ludwichowski@uni.torun.pl | 0 | 0 | 0 | 0 | 0 | 0 | |||
8965 | 2008-09-08 10:46:11 | 2008-10-06 06:39:09 | 2022-03-06 03:43:38.499702 | Unreviewed | closed | Uncategorized | 1.0 | fixed | UnicodeEncodeError in template path after migration from Django 0.96 to 1.0 | My templates are in a dir with a non-ascii char. Something like: u"/foo/bar/para'''í'''so/templates". With Django-0.96 works fine. With Django-1.0 internal testing server (./manage.py runserver) works fine too. But with apache and mod_python throws an UnicodeEncodeError ('ascii' codec can't encode character u'\xed' in position 13: ordinal not in range(128)) in /var/lib/python-support/python2.5/django/template/loaders/filesystem.py, in load_template_source: {{{ return (open(filepath).read().decode(settings.FILE_CHARSET), filepath) }}} settings.FILE_CHARSET is "utf-8". filepath is something like u"/foo/bar/paraíso/templates/foobar.html". It comes from TEMPLATE_DIRS in settings.py, that it looks like: {{{ TEMPLATE_DIRS = (unicode(os.path.join(os.path.dirname(__file__), 'templates').replace('\\','/'), "utf-8"), ) }}} If I put template dir without unicode conversion both runserver and mod_python+apache gives a "cannot extend foobar.html because template doesn't exist" error. | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
8966 | 2008-09-08 13:15:32 | 2008-10-28 19:05:00 | 2022-03-06 03:43:38.657645 | Ready for checkin | closed | Template system | dev | fixed | {% if "x"|length_is:n %} always evaluates True | {% if "x"|capfirst|length_is:n %} is always true. Example: {{{ In [1]: from django.template import Template, Context In [2]: Template('{% if "x"|capfirst|length_is:0 %}This is wrong{% endif %}').render(Context({})) Out[2]: u'This is wrong' }}} Using latest Django SVN. | carljm | Thomas Steinacher <tom@eggdrop.ch> | 0 | 1 | 0 | 0 | 0 | 0 | |||
8967 | 2008-09-08 15:54:50 | 2009-02-25 19:51:44 | 2022-03-06 03:43:38.840708 | Unreviewed | closed | Documentation | 1.0 | fixed | Model documentation omits through option in ManyToManyField | The [http://docs.djangoproject.com/en/dev/ref/models/fields/#manytomanyfield Model Field Reference] does not mention the new kwarg "through" for ManyToMany field. Before the refactoring, the omission of that option was not so serious because the next section of the same page was [http://www.djangoproject.com/documentation/model-api/#extra-fields-on-many-to-many-relationships Extra fields on many-to-many relationships], but now that section was moved to a different page ([http://docs.djangoproject.com/en/dev/topics/db/models/ Writing Models]), so "through" must be mentioned in the Model Field Reference. | nobody | ramalho | 0 | 0 | 0 | 0 | 0 | 0 | |||
8968 | 2008-09-08 15:57:01 | 2013-03-24 13:37:42 | 2022-03-06 03:43:39.010131 | Accepted | closed | contrib.comments | New feature | Normal | 1.0 | wontfix | No way to utilize `next` parameter to redirect after comment deletion | How is default «delete comment» view from new comments system meant to get `next` argument (see `contrib/comments/views/moderation.py`)? I think good way to do it is to support `next` GET request parameter, so that one could use `/delete/123/?next=/blog/entry/bla-blah` as a link to comment deletion page in order to redirect to page other than default «deleted» view after actually removing the comment. This works with «post comment» because `next_redirect` in `post_comment` function can see the `next` POST parameter in `data`. This does not work with «delete comment» because confirmation page is rendered first with `next="None"` in confirmation form. | kkubasik | Dzhus | comments | 0 | 1 | 1 | 1 | 1 | 0 |
8969 | 2008-09-08 16:25:24 | 2008-09-11 00:28:18 | 2022-03-06 03:43:39.174947 | Unreviewed | closed | Documentation | 1.0 | fixed | Missing ref tag on QuerySet API reference page | The first attempt to reference the database query guide on http://docs.djangoproject.com/en/dev/ref/models/querysets/ is missing the leading `:ref:`. Patch attached. | nobody | kmtracey | 0 | 0 | 0 | 0 | 0 | 0 | |||
8970 | 2008-09-08 16:33:21 | 2008-09-08 22:44:45 | 2022-03-06 03:43:39.344883 | Unreviewed | closed | contrib.admin | dev | duplicate | Explicit argument should be added to admin 'autodiscover()' | Just an idea, but it would be nice to be able to give an argument to autodiscover() that would target an admin.py. Many people use a collective admin.py in their project to call their app admin.py's. This would avoid having to manually import the project admin.py in settings. example: {{{ admin.autodiscover(admin) }}} | nobody | joshuajonah | 0 | 0 | 0 | 0 | 0 | 0 | |||
8971 | 2008-09-08 16:34:53 | 2011-09-28 16:12:21 | 2022-03-06 03:43:39.505914 | Ready for checkin | closed | contrib.admin | dev | fixed | URL resolution for admindocs reST roles incorrect | The parse_rst method in admindocs/utils.py has a link_base argument set to "../.." — that works fine if the the link being created is in either the model_detail or view_detail view. But if the view is being created in the tag_index or detail_index the url does not resolve correctly. The attached patch is a solid solution, but possibly temporary. It simply has the tag_index and model_index views pass parse_rst a link_base kwarg set to the correct relative URL. I think a better solution would be to have the roles’ URLs use reverse() rather than be hard-coded. I tried to do that, but it is difficult as reverse() needs views.py to resolve the URL and views.py relies on utils.py. I am sure it can be done, but I couldn’t figure out how. | mitsuhiko | benspaulding | admindocs urls | 0 | 1 | 0 | 0 | 0 | 0 | ||
8972 | 2008-09-08 17:35:43 | 2011-04-22 06:13:28 | 2022-03-06 03:43:39.683720 | Accepted | assigned | GIS | New feature | Normal | 1.0 | Add ability to delete selected vector features within the Geodjango/OpenLayers Admin map interface | This feature has been needed for some time, and was recently requested. See: http://groups.google.com/group/django-users/browse_thread/thread/36242edfd0d0281c?hl=en I've started a basic patch that adds a javascript function to allow multiple features to be selected in the map interface, deleted from view, and removed from the save method. I've tested this so far when editing multipolygon data in the admin. A known issue I'm hoping others may have a solution to: Currently, an OL javascript error occurs on line 948 of OpenLayer.js after successfully deleting a feature. This do not seem to cause any problems in saving the correct geometry or in continuing to use the select control. This is the firebug output: {{{ object is undefined selectFeature()(undefined)OpenLayers.js (line 948) clearSelectedFeatures()()277 (line 327) javascript:geodjango_geometry.clearSelectedFeatures()()()javascri...eatures() (line 1) [Break on this error] this.feature=null;this.dragControl.deact...ply(this.selectControl,[this.feature]);} }}} | jbronn | springmeyer | OpenLayers, admin, vector editing | 0 | 1 | 0 | 1 | 0 | 0 | |
8973 | 2008-09-08 18:02:41 | 2008-09-09 16:07:14 | 2022-03-06 03:43:39.841466 | Accepted | closed | Translations | dev | fixed | Update the telugu translations. | Update the telugu translations as much as possible. Locale for telugu is te. | nobody | thejaswi_puthraya | 0 | 1 | 0 | 0 | 0 | 0 | |||
8974 | 2008-09-08 21:14:40 | 2009-01-01 16:48:22 | 2022-03-06 03:43:40.015462 | Unreviewed | closed | Uncategorized | 1.0 | duplicate | ModelChoiceField raises "ValueError: invalid literal for int() with base 10: 'abc'" when non-numerical value is supplied | When I have a Form with a ModelChoiceField, and supply this field with a non-numerical value the specified error occurs on form.is_valid() as it tries to convert 'abc' with int(). The whole thing is reproducible with this code: http://dpaste.com/76808/ | nobody | burp_ | 0 | 0 | 0 | 0 | 0 | 0 | |||
8975 | 2008-09-08 21:23:51 | 2011-09-28 16:12:27 | 2022-03-06 03:43:40.174507 | Accepted | closed | Documentation | dev | fixed | related order functions are not documented | The functions detailed in this blog post: http://james.wheare.org/notes/2007/11/ordering-related-objects-in-django.php aren't documented at all in the main Django documentation, for example: http://docs.djangoproject.com/en/dev/search/?cx=009763561546736975936%3Ae88ek0eurf4&cof=FORID%3A11&ie=UTF-8&hl=&q=get_previous_in_order&sa=Search&as_q=more%3Adev_docs#242 These are super useful functions and it would be great to have them be described in the docs. If they're meant to be private then should they be renamed to begin with an '_'? | dwillis | Leo | 0 | 1 | 0 | 0 | 0 | 0 | |||
8976 | 2008-09-08 22:27:42 | 2008-09-08 22:31:22 | 2022-03-06 03:43:40.347129 | Unreviewed | closed | Template system | 1.0 | invalid | {% for x, y in dictionary %} not working as documented | When unpacking key: value pairs in a dict, in a foor loop, as documented in http://docs.djangoproject.com/en/dev/ref/templates/builtins/#ttag-for , x gets the first character of key, y gets the second character of key. Template Code: {{{ {{django_version}} Image Sizes: {{ insert_image_sizes|pprint }} {% for compartment,inserts in insert_image_sizes %} compartment: {{ compartment|pprint }} inserts: {{inserts}} {% endfor %} insert_image_sizes.101.aaaa.1:{{ insert_image_sizes.101.aaaa.1}} insert_image_sizes.1.1.1:{{ insert_image_sizes.1.1.1}} }}} Output: {{{ 1.0-final-SVN-8985 Image Sizes: {u'-': {}, u'101': {u'aaaa': (92, 169), u'bbb': (91, 169)}, u'102': {u'cccc': (53, 98), u'dddd': (53, 98)}, u'103': {}, u'104': {}, u'105': {}} compartment: u'-' inserts: compartment: u'1' inserts: 0 compartment: u'1' inserts: 0 compartment: u'1' inserts: 0 compartment: u'1' inserts: 0 compartment: u'1' inserts: 0 insert_image_sizes.101.aaaa.1:169 insert_image_sizes.1.1.1: }}} | nobody | hlecuanda | for loop dictionary | 0 | 0 | 0 | 0 | 0 | 0 | ||
8977 | 2008-09-08 22:27:58 | 2008-09-08 22:49:43 | 2022-03-06 03:43:40.590047 | Unreviewed | closed | Documentation | 1.0 | duplicate | no admin.py | from: http://docs.djangoproject.com/en/dev/intro/tutorial02/#intro-tutorial02 "Just one thing to do: We need to tell the admin that Poll objects have an admin interface. Edit the mysite/polls/admin.py file and add the following to the bottom of the file:" Following the tutorial through two times, I do not have that file (admin.py). I added what it suggested to a file i created in that location, named admin.py, but that did not expose the poll to the admin piece. | nobody | kyralak | 0 | 0 | 0 | 0 | 0 | 0 | |||
8978 | 2008-09-08 22:48:43 | 2008-09-09 02:18:31 | 2022-03-06 03:43:40.760078 | Accepted | closed | Core (Management commands) | 1.0 | fixed | python manage.py dbshell unhelpful error when postgresql-client not installed | If you try to start a dbshell and don't have the postgresql client installed, you get an unhelpful error message: {{{ aaron@hoth:~/code/sfd$ ./manage.py dbshell Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/usr/lib/python2.5/site-packages/django/core/management/__init__.py", line 340, in execute_manager utility.execute() File "/usr/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/lib/python2.5/site-packages/django/core/management/base.py", line 77, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 96, in execute output = self.handle(*args, **options) File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 178, in handle return self.handle_noargs(**options) File "/usr/lib/python2.5/site-packages/django/core/management/commands/dbshell.py", line 10, in handle_noargs connection.client.runshell() File "/usr/lib/python2.5/site-packages/django/db/backends/postgresql/client.py", line 17, in runshell os.execvp('psql', args) File "/usr/lib/python2.5/os.py", line 353, in execvp _execvpe(file, args) File "/usr/lib/python2.5/os.py", line 389, in _execvpe func(fullname, *argrest) OSError: [Errno 2] No such file or directory }}} | adrian | darkpixel | 0 | 0 | 0 | 0 | 0 | 0 | |||
8979 | 2008-09-08 23:57:09 | 2008-09-10 03:59:49 | 2022-03-06 03:43:40.996602 | Unreviewed | closed | Documentation | 1.0 | fixed | Documentation fixes | A few issues thata haven't already been reported in other Component:Documentation tickets: reST fixes, addition of Pygmentation to some files, typos. | nobody | ramiro | 0 | 1 | 0 | 0 | 0 | 0 | |||
8980 | 2008-09-08 23:57:35 | 2011-09-28 16:12:21 | 2022-03-06 03:43:41.182691 | Accepted | closed | Documentation | 1.0 | fixed | missing documentation for password_reset_confirm, password_reset_complete views | there's no docs! help! | nobody | aaronkrill | pycamp2009 kkmegapatch | 0 | 1 | 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 );