tickets
9 rows where "created" is on date 2007-12-01 and owner = "nobody" sorted by resolution
This data as json, CSV (advanced)
Suggested facets: stage, component, version, resolution, has_patch, needs_better_patch, needs_docs, last_pulled_from_trac (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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6070 | 2007-12-01 04:06:55 | 2007-12-02 15:33:08 | 2022-03-06 03:36:09.924966 | Ready for checkin | closed | Documentation | dev | fixed | Document that SITE_ID is no longer required to run all tests | I just ran all tests successfully with the following settings.py file: {{{ #!python URL_CONF = "urls" DATABASE_ENGINE = "sqlite3" }}} so the mention about "and a SITE_ID setting (any non-zero integer value will do) in order for all the tests to pass." in the [http://www.djangoproject.com/documentation/contributing/ Contributing to Django] page is wrong. Btw, why not put the above settings.py file in the tests directory to make it even easier for people to get going and start running tests? Just name it {{{sample_test_settings.py}}}. | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
6079 | 2007-12-01 17:21:37 | 2007-12-01 17:27:45 | 2022-03-06 03:36:11.448073 | Unreviewed | closed | Documentation | dev | fixed | AUTHENTICATION_BACKENDS is not documented in settings.txt | Hi there, AUTHENTICATION_BACKENDS is documented in authentication.txt, but not in settings.txt Maybe it's intentional as django.contrib.auth is "contrib", but SITE_ID is documented! ;) Anyway I'll try to post a patch later. | nobody | telenieko | 0 | 0 | 0 | 0 | 0 | 0 | |||
6085 | 2007-12-01 20:08:22 | 2008-01-13 13:15:02 | 2022-03-06 03:36:12.335200 | Unreviewed | closed | Uncategorized | newforms-admin | fixed | separated contrib.auth and contrib.admin views | it would make more sense to move stuff from contrib/admin/views/auth.py to contrib.auth.models into the UserAdmin | nobody | Honza_Kral | auth admin views | 0 | 1 | 1 | 0 | 0 | 0 | ||
6086 | 2007-12-01 20:32:09 | 2008-07-18 23:46:11 | 2022-03-06 03:36:12.492494 | Ready for checkin | closed | Core (Cache system) | dev | fixed | Refactor django.core.cache to deprecate "simple" backend | As detailed in [http://groups.google.com/group/django-developers/browse_thread/thread/16866b74a2390a26 this django-dev thread], the "simple" cache backend doesn't have much reason to live any more. The attached patch refactors the cache backends to eliminate simple.py, and issues a DeprecationWarning per Jacob's recommendation. Thanks to Brian Johnson and David Schein for a great afternoon of cafe coding! | nobody | pbx | sprintdec01 | 0 | 1 | 1 | 0 | 0 | 0 | ||
6088 | 2007-12-01 21:09:36 | 2008-04-27 02:50:16 | 2022-03-06 03:36:12.761416 | Accepted | closed | Database layer (models, ORM) | dev | fixed | get_previous_in_order broken | There's a bug in the SQL generated when calling get_previous_in_order. Luckily looks like a quick fix from where I'm sitting. Just need to change the ordering to DESC from ASC. | nobody | James Wheare <django@sparemint.com> | qs-rf-fixed | 0 | 1 | 0 | 0 | 0 | 0 | ||
6084 | 2007-12-01 18:41:39 | 2007-12-03 14:25:52 | 2022-03-06 03:36:12.217534 | Accepted | closed | Documentation | dev | invalid | Add warning about python-memcached client < 1.40 not being thread safe | Since older versions of [http://www.tummy.com/Community/software/python-memcached/ python-memcached] often cause connections to stay open indefinitely, add a warning about versions before 1.40. | nobody | mcroydon | 0 | 1 | 0 | 0 | 1 | 0 | |||
6076 | 2007-12-01 12:46:14 | 2007-12-04 10:07:13 | 2022-03-06 03:36:10.855676 | Unreviewed | closed | Documentation | dev | wontfix | deprecated code example in dodumentation | In the page http://www.djangoproject.com/documentation/i18n/ There is an example that use the deprecate/not working document.write function. {{{ document.write(gettext('this is to be translated')); }}} please replace with the current dom standard {{{ tnode = document.createTextNode(gettext('this is to be translated')); [code to insert the tnode using dom...] }}} | nobody | dan | 0 | 0 | 0 | 0 | 0 | 0 | |||
6090 | 2007-12-01 23:11:02 | 2007-12-08 12:41:03 | 2022-03-06 03:36:13.037711 | Design decision needed | closed | Database layer (models, ORM) | dev | wontfix | Add whitespace between fields in queries | The attached patch adds whitespace between fields in queries, as to better display the queries for debugging. All occurrences of {{{ ",".join(...) }}} in django.db is replaced by {{{ ", ".join(...) }}}. | nobody | jodal | 0 | 1 | 0 | 0 | 0 | 0 | |||
6067 | 2007-12-01 00:13:32 | 2008-03-07 14:38:13 | 2022-03-06 03:36:09.474552 | Unreviewed | closed | Forms | dev | worksforme | Small addition to newForms documentation regarding required fields in templates | In the documentation: http://www.djangoproject.com/documentation/newforms/#highlighting-required-fields-in-templates It might be useful to give an example of how to check if a field is required when accessing a form field directly. This would be in addition to the existing example which is demonstrating use when iterating over a form. I'd suggest an example such as {% if form.fieldName.field.required %}*{% endif %} Thanks | nobody | stp2007 <stp2007@solvingtheproblem.ca> | documentation | 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 );