tickets
32 rows where "created" is on date 2008-09-02 sorted by status
This data as json, CSV (advanced)
Suggested facets: resolution, owner, reporter, keywords, has_patch, needs_better_patch, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 | |||
| 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 | ||
| 8788 | 2008-09-02 03:55:18 | 2011-09-28 16:12:17 | 2022-03-06 03:43:10.312116 | Ready for checkin | closed | Documentation | dev | fixed | correction for some typos in #8805 | {{{ Index: django/forms/models.py =================================================================== --- django/forms/models.py (revision 8831) +++ django/forms/models.py (working copy) @@ -244,7 +244,7 @@ if self.instance.pk is not None: qs = qs.exclude(pk=self.instance.pk) - # This cute trick with extra/values is the most efficiant way to + # This cute trick with extra/values is the most efficient way to # tell if a particular query returns any results. if qs.extra(select={'a': 1}).values('a').order_by(): model_name = capfirst(self.instance._meta.verbose_name) Index: docs/topics/forms/modelforms.txt =================================================================== --- docs/topics/forms/modelforms.txt (revision 8831) +++ docs/topics/forms/modelforms.txt (working copy) @@ -337,10 +337,10 @@ Overriding the clean() method ----------------------------- -You can overide the ``clean()`` method on a model form to provide additional +You can override the ``clean()`` method on a model form to provide additional validation in the same way you can on a normal form. However, by default the ``clean()`` method validates the uniqueness of fields that are marked as unique -on the model, and those marked as unque_together, if you would like to overide +on the model, and those marked as unique_together, if you would like to override the ``clean()`` method and maintain the default validation you must call the parent class's ``clean()`` method. }}} | nobody | Matthew Flanagan <mattimustang@gmail.com> | 0 | 1 | 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 | ||
| 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 | ||
| 8791 | 2008-09-02 08:48:24 | 2008-09-02 10:19:07 | 2022-03-06 03:43:10.786973 | Unreviewed | closed | Translations | dev | fixed | Turkish translation updates | Here's another (and hopefully last) update for Turkish tanslations. Many additions and corrections. | nobody | amiroff | turkish tr | 0 | 1 | 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 | |||
| 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 | ||
| 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 | |||
| 8796 | 2008-09-02 14:22:12 | 2011-09-28 16:12:17 | 2022-03-06 03:43:11.579563 | Unreviewed | closed | Translations | dev | fixed | Last update of Brazilian Portuguese (pt_BR) localization for Django 1.0 final | Some translations improved and added new translations. Please, if possible, apply this patch latest as possible, because is probably that we are going to have new changes later today. Thanks! :-) | nobody | Guilherme M. Gondim <semente@taurinus.org> | pt_BR | 0 | 1 | 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 | |
| 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 |
| 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 | ||||
| 8800 | 2008-09-02 15:59:36 | 2008-12-08 02:35:31 | 2022-03-06 03:43:12.198834 | Unreviewed | closed | *.djangoproject.com | dev | fixed | New docs search producing invalid HTML | Very minor, but I noticed that my patch from #8723 that was committed in [8844] contains errors which causes the new docs site to produce invalid HTML. The script tag in `search_form.html` has an unescaped ampersand (this was actually copied and pasted from Google's example code). Also, it looks like the `lang` variable is never populated. The attached (untested) patch should hopefully fix both of these. | jacob | frasern | 0 | 1 | 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 | |||
| 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 | |||
| 8803 | 2008-09-02 17:36:53 | 2008-10-05 05:18:25 | 2022-03-06 03:43:12.638756 | Unreviewed | closed | contrib.comments | dev | fixed | Possibility to use username if full name is missing in the comments framework | The ticket summary mentions it all. After a discussion with Jacob on IRC, it was decided to have this though having the full name is always recommended. | nobody | thejaswi_puthraya | fullname, username, comments | 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 | |||
| 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 | |||
| 8806 | 2008-09-02 18:38:01 | 2009-02-25 19:51:44 | 2022-03-06 03:43:13.075868 | Unreviewed | closed | contrib.admin | dev | duplicate | ModelAdmin should allow not default manager | My use case is this: I have a model with two Managers - one named objects (the default), and another one. I want the admin to use the non-default one (in my case I can't even give it the default one since it doesn't return instances of the model, but of another model it inherits from). So my solution (It doesn't even merit a patch - its just 3 lines changed in django/contrib/admin/options.py): # my code from django.contrib import admin class MyAdmin(admin.ModelAdmin): model = MyModel manager = MyModel.othermanager # unified diff against django/contrib/admin/options.py svn 8851 --- a/django/contrib/admin/options.py +++ b/django/contrib/admin/options.py @@ -166,6 +166,8 @@ class ModelAdmin(BaseModelAdmin): ordering = None inlines = [] + manager = None + # Custom templates (designed to be over-ridden in subclasses) change_form_template = None change_list_template = None @@ -239,7 +241,10 @@ class ModelAdmin(BaseModelAdmin): Returns a QuerySet of all model instances that can be edited by the admin site. This is used by changelist_view. """ - qs = self.model._default_manager.get_query_set() + if self.manager is None: + qs = self.model._default_manager.get_query_set() + else: + qs = self.manager.get_query_set() # TODO: this should be handled by some parameter to the ChangeList. ordering = self.ordering or () # otherwise we might try to *None, which is bad ;) if ordering: | nobody | alon | ModelAdmin,Manager | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8807 | 2008-09-02 18:54:10 | 2011-09-28 16:12:17 | 2022-03-06 03:43:13.233283 | Unreviewed | closed | Forms | dev | duplicate | django.forms.utils.ValidationError should be a subclass of django.core.exceptions.ValidationError | Seems that this should be true as they are kinda the same thing, but in a different context (i.e. sometimes hard to figure out which ValidationError is thrown in a try except) | nobody | magneto | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8808 | 2008-09-02 19:04:04 | 2011-06-01 15:37:55 | 2022-03-06 03:43:13.384797 | Design decision needed | closed | contrib.formtools | New feature | Normal | dev | fixed | Form Wizard keeps state on subsequent requests and provides no way to cut short inside parse_params | Since this issue is subtle I'll describe my concrete usecase first and than describe the issue and possible solutions to this. '''Usecase:''' I have a form that contains a ChoiceField which depends on the currently logged in user and some request parameters. Since I need a special behaviour I subclassed the FormWizard and did overwrite the methods {{{parse_params}}}, {{{done}}}, {{{process_step}}}, {{{get_form}}} and {{{get_template}}}. Inside {{{parse_params}}} I set some attributes of self. For some reason I assumed that returning anything but None would cause the Wizard to abort. However the return value is ignored and the wizard code continues by calling {{{get_form}}} and {{{process_step}}}. Since {{{get_form}}} is the only way of putting the stuff which was set earlier in {{{parse_params}}} I have a hook that calls some helper methods on the form to set up the options of the ChoiceField depending on the stuff set by {{{parse_params}}} earlier. Since the only way of injecting custom data there is {{{self}}} one has no chance of telling wether the value comes from the current request or something earlier which might just have failed. Thus no AttributeError is raised as the attribute is set. The data just does not come from the current request. Even worse: In my case - since I was assuming that returning from {{{parse_params}}} with an {{{HttpResponse}}} would stop the wizard and return the HttpResponse immediately - caused invalid requests to be rendered with the state from a previous requests. A horrid leak of sensible data, as the wizard is part of a checkout process and the {{{ChoiceField}}} is used to pick an address. I'm just glad our QA noticed that glitch before putting this stuff live. It would not be hard to exploit and I don't like the idea of leaking sensible data. '''Solutions:''' 1. By overwriting the {{{__call__}}} method one can inject any attribute into self and return any HttpResponse object if something is wrong. I consider this rather ugly as the FormWizard explicitly state… | nobody | Michael P. Jung | FormWizard, state, parse_params, shortcut, HttpResponse | 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 |
| 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 | |||||
| 8811 | 2008-09-02 20:41:02 | 2011-09-28 16:12:17 | 2022-03-06 03:43:13.872029 | Unreviewed | closed | Documentation | dev | fixed | urls.py example of tutorial part 2 has Django template-style vars | `"mysite"` should appear instead of `{{ project_name }}` | nobody | ramiro | 0 | 1 | 0 | 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 | |||
| 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 | |||
| 8815 | 2008-09-02 21:18:55 | 2011-09-28 16:12:17 | 2022-03-06 03:43:14.520226 | Unreviewed | closed | Translations | dev | fixed | Final Arabic translation update and QA | Final QA and changed after testing the translation. | nobody | okhayat | arabic | 0 | 1 | 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 | |||
| 8817 | 2008-09-02 22:48:31 | 2011-09-28 16:12:21 | 2022-03-06 03:43:14.814460 | Ready for checkin | closed | File uploads/storage | dev | fixed | Accessing ImageField's dimensions doesn't close file | If you access an ImageField's width or height property, the corresponding image file doesn't seem to be closed after retrieving its dimensions: After retrieving a lot of image dimensions (of different images), Django produces strange errors ("cannot open template file ..." etc.) which seem to result from too many files being open by the process. Manually calling the close() method of the ImageFieldFile object (after accessing the width and height properties) resolves these errors, so it seems it isn't not called automatically... | mitsuhiko | tripediac | 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
);