tickets
15 rows where "created" is on date 2008-09-02 and has_patch = 0 sorted by description
This data as json, CSV (advanced)
Suggested facets: version, resolution, owner, reporter
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8810 | 2008-09-02 20:30:23 | 2011-09-28 16:12:17 | 2022-03-06 03:43:13.707296 | Unreviewed | closed | Documentation | fixed | Link from docs.djangoproject.com to Django Software foundation doesn't work | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||||
8789 | 2008-09-02 06:56:24 | 2008-11-04 10:12:42 | 2022-03-06 03:43:10.471253 | Unreviewed | closed | contrib.admin | dev | fixed | .submit-row class doesnt have clearfix on password change page | "Change password" form in admin (when you go to change users passwords) has only 1 submit button and it's floated right so it's container (which has class .submit-row) doesn't wrap around it properly. It's probably missing .clearfix class or something like overflow:auto. Bug appears in latest Firefox and Opera (and probably most of other browsers, but i haven't had time to test it). | nobody | rebus | css | 0 | 0 | 0 | 0 | 0 | 0 | ||
8792 | 2008-09-02 09:56:47 | 2009-03-01 12:13:57 | 2022-03-06 03:43:10.945404 | Unreviewed | closed | Testing framework | dev | wontfix | Django's unit test system wipes out "custom sql" data before performing tests | Django's unit test system issues "flush" command (resulting in a truncate for all tables) just before performing tests. This causes problems when having custom sql scripts (<appname>/sql/<modelname>.sql) because all this data is wiped out by the truncate and might be required for the tests. Django's test execution path: - tables creation - custom sql execution (potential data insertion) - flush (truncate all tables) - perform tests (without potential custom sql data!) I think it might be good to execute custom sql after the truncate has occurred ... | nobody | deltoide | 0 | 0 | 0 | 0 | 0 | 0 | |||
8799 | 2008-09-02 15:45:19 | 2008-09-02 16:59:57 | 2022-03-06 03:43:12.046010 | Unreviewed | closed | Database layer (models, ORM) | invalid | .save() and .objects.create() does not set the primary key when the model has an explicit primary key field | Here is what I observed on django1.0-beta2 and 0.96 releases with MySQL or Sqlite3.[[BR]] I have the following table:[[BR]] Sqlite: {{{ CREATE TABLE "Person" ( "id" integer NOT NULL PRIMARY KEY, "name" text NOT NULL ) MySQL: CREATE TABLE `Person` ( `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, `name` longtext NOT NULL ) }}} In the models.py I have {{{ class Person(models.Model): id = models.IntegerField(primary_key=True) name = models.TextField() class Meta: db_table = u'Person' }}} When I issue: {{{ p = Person.objects.create(name='Bob') p.id }}} I get nothing. The record however is persisted. Same happens with {{{ p = Person('name'=Bob) p.save() p.id }}} If however the model is missing the id field and django auto generates it: {{{ class Person(models.Model): name = models.TextField() class Meta: db_table = u'Person' }}} Than everything is OK. The id is set correctly. | nobody | vmihaylov@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | ||||
8816 | 2008-09-02 22:46:16 | 2008-09-02 23:21:31 | 2022-03-06 03:43:14.663898 | Unreviewed | closed | *.djangoproject.com | dev | fixed | Links to security fixes (might be) incorrect | One of the links to the security fixes at http://www.djangoproject.com/weblog/2008/sep/02/security/ doesn't match the description: * Django 0.96.3: http://www.djangoproject.com/download/0.91.3/tarball/ --> 0.91.3 * Django 0.95.4: http://www.djangoproject.com/download/0.95.4/tarball/ --> 0.95.4 * Django 0.91.3: http://www.djangoproject.com/download/0.96.3/tarball/ --> 0.96.2 Is this what was intended? Both the link (0.96.3) and the result (0.96.3) look off, and why is 0.96.3 pointing to 0.91.3? Also, the main download page (http://www.djangoproject.com/download/) is pointing to 0.96.2: First, download Django-0.96.3.tar.gz. Then: which links to Django-0.96.2.tar.gz | nobody | jjackson | 0 | 0 | 0 | 0 | 0 | 0 | |||
8790 | 2008-09-02 08:36:49 | 2011-09-28 16:12:17 | 2022-03-06 03:43:10.642351 | Unreviewed | closed | Database layer (models, ORM) | dev | fixed | Q objects problem with disjunction | Thank you for fixing my bug in #8439, but I'm still having issues with these complex queries. Below is the exact system I'm trying to implement, although I've simplified it as much as I could for this report. Basically, there are "users" and "groups" (which contain users), and "resources" that they have privileges to access with respect to particular "abilities". Here are my models: {{{ from django.db import models class XResource(models.Model): pass class XUser(models.Model): pass class XGroup(models.Model): pass class XMembership(models.Model): user = models.ForeignKey(XUser) group = models.ForeignKey(XGroup) class XRole(models.Model): pass class XAbility(models.Model): role = models.ForeignKey(XRole) name = models.CharField(max_length=100) allowed = models.BooleanField() class XUserPriv(models.Model): user = models.ForeignKey(XUser) resource = models.ForeignKey(XResource) role = models.ForeignKey(XRole) class XGroupPriv(models.Model): group = models.ForeignKey(XGroup) resource = models.ForeignKey(XResource) role = models.ForeignKey(XRole) }}} So I create a user, who is in a group, and the group has privileges to use the "display" ability on a resource. {{{ user = XUser.objects.create() group = XGroup.objects.create() membership = XMembership.objects.create(user=user, group=group) resource = XResource.objects.create() role = XRole.objects.create() ability = XAbility.objects.create(role=role, name="display", allowed=True) group_priv = XGroupPriv.objects.create(group=group, resource=resource, role=role) }}} I do the following query (I want to get a list of all resources that the user is directly allowed to display, along with those that the user is allowed to display via his group, given that he is not explicitly denied the privilege himself), and I get no results (but I should get back [resource]): {{{ direct_yes_q = Q(xuserpriv__user=user, xuserp… | mtredinnick | mikemintz | 1.0-blocker | 0 | 0 | 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 | |||
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 | |||
8814 | 2008-09-02 21:11:25 | 2008-09-02 21:17:51 | 2022-03-06 03:43:14.352682 | Unreviewed | closed | Documentation | 0.96 | invalid | Link for 0.96 Admin module Broken | The page located at http://www.djangoproject.com/documentation/0.96/admin/ is missing. When reading the documentation for the admin module and you click on the 0.96 version link and there is no page at that location. | nobody | Caelin | 0 | 0 | 0 | 0 | 0 | 0 | |||
8786 | 2008-09-02 00:12:20 | 2011-09-28 16:12:17 | 2022-03-06 03:43:09.984065 | Unreviewed | closed | Documentation | dev | fixed | PhoneNumberField still listed in model docs | [8819] moved USStateField to localflavor docs, but not PhoneNumberField. | nobody | mattmcc | 0 | 0 | 0 | 0 | 0 | 0 | |||
8801 | 2008-09-02 17:08:36 | 2008-09-04 00:01:01 | 2022-03-06 03:43:12.360908 | Unreviewed | closed | Documentation | 0.96 | wontfix | .96 docs say svn | http://www.djangoproject.com/documentation/release_notes_0.96/#backwards-incompatible-changes says "This document is for Django's SVN release" which is incorrect. | nobody | CarlFK | 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 | |||
8797 | 2008-09-02 14:56:07 | 2011-11-22 07:43:42 | 2022-03-06 03:43:11.729761 | Design decision needed | closed | contrib.auth | Bug | Normal | dev | worksforme | django password reset tests assume hardcoded urls | in `django/contrib/auth/tests/views.py` there are lines like e.g.: {{{ response = self.client.post('/password_reset/', {'email': 'not_a_real_email@email.com'}) }}} When one associates the password views with different urls in urls.py these tests will fail because of the hardcoded `'/password_reset/'`. | SmileyChris | teh | 0 | 0 | 0 | 0 | 0 | 0 | |
8793 | 2008-09-02 11:10:42 | 2011-09-28 16:12:17 | 2022-03-06 03:43:11.108225 | Unreviewed | closed | File uploads/storage | dev | duplicate | using the file.url can not download the uploaded file | when I digg into the source code,I found that in line 47 of django.db.models.fields.files,the call to self.storage.path(self.name) returns a os.path.normpath processed file path, it changes the file's full path to all lower case, but the url is not following this change, so this error happens! sorry, I can not submit a good patch for it,but I think it will resolved by you gurus. thank you | nobody | etng | normcase path | 0 | 0 | 0 | 0 | 0 | 0 | ||
8805 | 2008-09-02 18:22:57 | 2011-09-28 16:12:17 | 2022-03-06 03:43:12.939766 | Unreviewed | closed | contrib.admin | dev | fixed | TypeError: sequence expected, int found | {{{ class Brand(models.Model): ... geo = models.ForeignKey(Geo, related_name='brand_set', blank=True, null=True, limit_choices_to={'level__exact' : 0}, ) ... }}} Caught an exception while rendering: sequence expected, int found Original Traceback (most recent call last): File "/opt/elec-devel/python/django/template/debug.py", line 71, in render_node result = node.render(context) File "/opt/elec-devel/python/django/template/debug.py", line 87, in render output = force_unicode(self.filter_expression.resolve(context)) File "/opt/elec-devel/python/django/utils/encoding.py", line 49, in force_unicode s = unicode(s) File "/opt/elec-devel/python/django/forms/forms.py", line 326, in __unicode__ return self.as_widget() File "/opt/elec-devel/python/django/forms/forms.py", line 358, in as_widget return widget.render(name, data, attrs=attrs) File "/opt/elec-devel/python/django/contrib/admin/widgets.py", line 109, in render params = self.url_parameters() File "/opt/elec-devel/python/django/contrib/admin/widgets.py", line 134, in url_parameters params = self.base_url_parameters() File "/opt/elec-devel/python/django/contrib/admin/widgets.py", line 129, in base_url_parameters params.update(dict([(k, ','.join(v)) for k, v in self.rel.limit_choices_to.items()])) TypeError: sequence expected, int found | nobody | anonymous | 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 );