tickets

9 rows where "created" is on date 2008-09-02 and stage = "Accepted" sorted by id

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: resolution, owner, has_patch, needs_better_patch, ui_ux, changetime (date)

stage 1 ✖

  • Accepted · 9 ✖

created (date) 1 ✖

  • 2008-09-02 · 9 ✖
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
8787 2008-09-02 00:58:46 2011-09-28 16:12:17 2022-03-06 03:43:10.149129 Accepted closed contrib.admin     dev fixed Tests are currently failing on django trunk It's the admin_widget tests. nobody Alex 1.0-blocker 0 1 0 0 0 0
8794 2008-09-02 11:54:58 2011-10-09 13:42:11 2022-03-06 03:43:11.277140 Accepted closed contrib.comments     dev fixed Profanity filter suffers from the Scunthorpe problem The implementation of the profanity filter suffers from the [http://en.wikipedia.org/wiki/Scunthorpe_Problem Scunthorpe Problem]; ie. that it considers the town of Scunthorpe, amongst other innocuous words, to be profane. Profanity filtering is A Hard Problem, and naïve solutions like this one cause frustrating problems to end-users. Checking the current profanities list for false positives in a couple of word lists I had to hand also yields: {{{ gobbledegook snigger Brushite Cushite Niggerhead Peshito Peshitto Shittah Shittah tree Shittim Shittim wood Shittle Shittlecock Shittleness }}} Obviously proper names are not in my dictionary, but they cause frequent and often more annoying problems. I suggest to disable the filter by default so that scope of the problem is limited, and at the very least the filter must be restricted to {{{re.match(r'\b' + word + '\b')}}}. Users who need stricter profanity filters should have the responsibility for doing so, and potentially annoying their users themselves. Django should not be doing it for them. nobody Daniel Pope <dan@mauveinternet.co.uk>   0 0 0 0 0 0
8795 2008-09-02 12:00:55 2011-09-28 16:12:17 2022-03-06 03:43:11.436606 Accepted closed Forms     dev fixed unique_together validation fails on model forms that exclude unique fields i found this bug when you have model like this: {{{ #!python class FunkcjeProdukt(models.Model): funkcja = models.ForeignKey(FunkcjeRodzina) produkt = models.ForeignKey(Produkty) wartosc = models.CharField(max_length=255) class Meta: unique_together = ("produkt", "funkcja") }}} and form from model: {{{ #!python class FunkcjeProduktForm(ModelForm): wartosc = forms.CharField(widget=forms.TextInput(attrs={'size':'40','class':'formularz'})) class Meta: model = FunkcjeProdukt exclude=('produkt','funkcja') }}} end if you want only edit "wartosc" from existing instance: {{{ #!python form_fp = FunkcjeProduktForm(data=request.POST,instance=finst) if form_fp.is_valid(): form_fp.save() }}} error is throw: {{{ #!python KeyError at /cms/r_produkt/8/'produkt' Request Method: POST Request URL: http://posiflex.com.pl/cms/r_produkt/8/ Exception Type: KeyError Exception Value: 'produkt' Exception Location: /home/posiflex/django/forms/models.py in validate_unique, line 238 }}} because: in validate_unique() from django/forms/models.py line unique_checks = list(self.instance._meta.unique_together[:]) add 'produkt' and 'funkcja' even when this fields in on exclude list jacob anihrat@gmail.com   0 0 0 0 0 0
8798 2008-09-02 15:44:42 2012-10-15 21:16:47 2022-03-06 03:43:11.884053 Accepted closed contrib.localflavor New feature Normal dev invalid Add DEPhoneNumberField to German localflavor module This ticket tries to add a {{{DEPhoneNumberField}}} class to the German localflavor module. There are several valid standards in Germany: DIN 5008, E.123 and an informal format which have national and international notations. More information: http://de.wikipedia.org/wiki/Rufnummer#Schreibweisen jezdez jezdez locale, localflavor, german, phone, number, localflavorsplit 0 1 0 0 0 1
8802 2008-09-02 17:16:22 2011-09-28 16:12:17 2022-03-06 03:43:12.490927 Accepted closed Documentation     dev fixed Document database-dependent behavior of BooleanField. As noted in http://code.djangoproject.com/ticket/7190, BooleanField can be either an int or a bool depending on the database used. This bit of non-deterministic behavior should be documented very clearly. -Dave jacob stengleind   0 1 0 0 0 0
8804 2008-09-02 17:38:57 2011-09-28 16:12:17 2022-03-06 03:43:12.787520 Accepted closed Documentation     dev fixed Documentation example gives wrong result {{{ (r'^sitemap-(?P<section>.+).xml$', 'django.contrib.sitemaps.views.sitemap', {'sitemaps': sitemaps}) }}} This won't work. and results in sitemap-mysectionnamexxml instead of sitemap-mysectionname.xml This will work: {{{ (r'^sitemap-(?P<section>.+)\.xml$', 'django.contrib.sitemaps.views.sitemap', {'sitemaps': sitemaps}) }}} nobody toke   0 1 0 0 0 0
8809 2008-09-02 19:58:37 2015-01-30 17:09:54 2022-03-06 03:43:13.545045 Accepted closed Core (URLs) New feature Normal dev wontfix Better error message when can't import url callback in django.core.urlresolvers _get_callback it would be helpful to display not just the module name that couldn't be imported, but the entire urls.py line that was the problem. Without more information it's incredibly hard to track down WHICH urls.py file has the problem and which line in that file is problematic. nobody TP error message 0 1 1 0 0 0
8812 2008-09-02 20:44:39 2011-09-28 16:12:17 2022-03-06 03:43:14.019887 Accepted closed contrib.admin     dev fixed Delete link should be right-aligned when admin interface is RTL The class of the P tag that contains the 'deletelink' should be float-right rather than float-left for it to be displayed correctly. Currently it is: {{{<p class="float-left"><a href="delete/" class="deletelink">delete</a></p>}}} and should be {{{<p class="float-right"><a href="delete/" class="deletelink">delete</a></p>}}} nobody okhayat   0 1 0 0 0 0
8813 2008-09-02 20:48:20 2011-09-28 16:12:21 2022-03-06 03:43:14.196738 Accepted closed Forms     dev fixed BaseInlineFormSet unable to save existing objects The Error: {{{ Environment: Request Method: POST Request URL: http://localhost:8000/caktus-books/ledger/exchange/215/edit/invoice/ Django Version: 1.0-beta_2-SVN-8874 Python Version: 2.5.2 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.admin', 'django.contrib.humanize', 'django.contrib.markup', 'crm', 'ledger'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.middleware.doc.XViewMiddleware') Traceback: File "/home/tobias/caktus/eclipse-workspace/caktus_books/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/home/tobias/caktus/eclipse-workspace/caktus_books/django/contrib/auth/decorators.py" in __call__ 67. return self.view_func(request, *args, **kwargs) File "/home/tobias/caktus/eclipse-workspace/caktus_books/django/db/transaction.py" in _commit_on_success 238. res = func(*args, **kw) File "/home/tobias/caktus/eclipse-workspace/caktus_books/ledger/views.py" in create_edit_exchange 88. transactions = transaction_formset.save(commit=False) File "/home/tobias/caktus/eclipse-workspace/caktus_books/django/forms/models.py" in save 372. return self.save_existing_objects(commit) + self.save_new_objects(commit) File "/home/tobias/caktus/eclipse-workspace/caktus_books/django/forms/models.py" in save_existing_objects 386. obj = existing_objects[form.cleaned_data[self._pk_field.name]] Exception Type: KeyError at /caktus-books/ledger/exchange/215/edit/invoice/ Exception Value: None }}} From the debugger I found that: {{{ self._pk_field.name = 'id' self._pk_field.name in form.cleaned_data is True form.cleaned_data[self._pk_field.name] is None }}} The Formset: {{{ class BaseTr… jkocherhans tobias   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
    );