home / django_tickets

tickets

3 rows where "created" is on date 2011-06-09 and easy = 1 sorted by changetime

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: resolution, needs_better_patch, needs_tests, last_pulled_from_trac (date)

easy 1 ✖

  • 1 · 3 ✖

created (date) 1 ✖

  • 2011-06-09 · 3 ✖
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
16209 2011-06-09 20:27:56 2011-06-26 16:52:14 2022-03-06 04:02:34.164293 Ready for checkin closed Documentation New feature Normal 1.3 fixed Add alternative repositories to 'Installing the development version' in the docs. https://docs.djangoproject.com/en/dev/topics/install/#installing-development-version The current page only refers to the subversion repo, but there are official github and bitbucket repos which some users will find more convenient. ShawnMilo ShawnMilo   1 1 0 0 0 0
16208 2011-06-09 19:50:36 2012-06-28 11:08:52 2022-03-06 04:02:34.031454 Accepted closed Core (Serialization) Bug Normal 1.2 invalid natural key YAML deserialization using non-list natural keys broken (with fixing patch) I'm using Django 1.2.5. I had trouble loading data from a fixture using the natural keys feature. I tracked this down to what seems to be a bug in the deserialization code for YAML data. If the field used as a natural key is a tuple, (has an __iter__ method in the yaml reader) the get_by_natural_key() method is called, but if it's a singleton, the same code is called that would be if no get_by_natural_key() method were defined. I made a patch that I believe fixes this bug (attached). It fixes the issue for me. I don't have a full working copy of Django set up, so I just generated this with POSIX diff; sorry if that's inconvenient. kenth jeff.k@benetech.org yaml 1 1 1 1 0 0
16188 2011-06-09 13:29:44 2012-10-12 21:19:18 2022-03-06 04:02:30.921564 Ready for checkin closed Internationalization Cleanup/optimization Normal dev fixed Added locale formats for swiss german language The swiss german number formats are slightly different than the german ones: {{{ DECIMAL_SEPARATOR = '.' THOUSAND_SEPARATOR = "'" }}} [http://lh.2xlibre.net/locale/de_CH/] ojii sspross locale, formats 1 1 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
    );
Powered by Datasette · Queries took 937.481ms