tickets
85 rows where version = "1.1-beta" sorted by resolution
This data as json, CSV (advanced)
Suggested facets: status, component, type, severity, resolution, owner, has_patch, needs_better_patch, needs_tests, changetime (date), last_pulled_from_trac (date)
created (date) >30 ✖
- 2009-04-22 3
- 2009-05-03 3
- 2009-05-27 3
- 2009-06-12 3
- 2009-03-25 2
- 2009-03-26 2
- 2009-03-31 2
- 2009-04-09 2
- 2009-04-15 2
- 2009-04-20 2
- 2009-05-06 2
- 2009-05-13 2
- 2009-05-24 2
- 2009-07-10 2
- 2009-07-27 2
- 2009-07-31 2
- 2005-09-04 1
- 2008-06-19 1
- 2008-06-21 1
- 2008-08-08 1
- 2008-08-19 1
- 2008-09-06 1
- 2008-11-24 1
- 2009-03-24 1
- 2009-03-27 1
- 2009-04-02 1
- 2009-04-05 1
- 2009-04-06 1
- 2009-04-07 1
- 2009-04-13 1
- …
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
11541 | 2009-07-24 13:35:44 | 2020-04-12 12:22:25 | 2022-03-06 03:50:10.239619 | Accepted | new | Database layer (models, ORM) | Bug | Normal | 1.1-beta | F() expressions don't allow assignment of Foreign Key values on instances | Lines 93-102 of the expressions model test define the following test case: {{{ # F expressions cannot be used to update attributes which are foreign keys, or # attributes which involve joins. >>> test_gmbh.point_of_contact = None >>> test_gmbh.save() >>> test_gmbh.point_of_contact is None True >>> test_gmbh.point_of_contact = F('ceo') Traceback (most recent call last): ... ValueError: Cannot assign "<django.db.models.expressions.F object at ...>": "Company.point_of_contact" must be a "Employee" instance. }}} There's no reason this sort of assignment shouldn't be possible - it just requires the appropriate handling on the related field. | nobody | russellm | 0 | 0 | 0 | 0 | 0 | 0 | ||
10626 | 2009-03-25 21:08:14 | 2013-02-28 10:15:36 | 2022-03-06 03:47:48.660190 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | duplicate | Default model ordering affects annotation query | Example models without default orderings: {{{ class Author(models.Model): id = models.IntegerField(primary_key=True, help_text='Uniquely identifies an author.') name= models.CharField(max_length=200, help_text="Author's first name.") class Book(models.Model): id = models.IntegerField(primary_key=True, help_text='Uniquely identifies a book.') title = models.CharField(max_length=200, help_text='The title of this book.') author = models.ForeignKey(Author, db_column='author_id', help_text='The author of this book.') price = models.FloatField( help_text='Price of the book.') inventory = models.IntegerField( help_text='Copies of book in the store.') }}} Use values() and annotate() to determine the number of books at each price. This works as I expected: {{{ >>> q = Book.objects.values('price').annotate(Count('price')) >>> list(q) [{'price': 7.9900000000000002, 'price__count': 2}, {'price': 9.9900000000000002, 'price__count': 1}] }}} Now add default orderings to the models: {{{ class Author(models.Model): id = models.IntegerField(primary_key=True, help_text='Uniquely identifies an author.') name= models.CharField(max_length=200, help_text="Author's first name.") class Meta: ordering = ['id'] class Book(models.Model): id = models.IntegerField(primary_key=True, help_text='Uniquely identifies a book.') title = models.CharField(max_length=200, help_text='The title of this book.') author = models.ForeignKey(Author, db_column='author_id', help_text='The author of this book.') price = models.FloatField( help_text='Price of the book.') inventory = models.IntegerField( help_text='Copies of book in the store.') class Meta: ordering = ['id'] }}} And repeat the query: {{{ >>> q = Book.objects.values('price').annotate(Count('price')) >>> list(q) [{'price': 9.990000000… | kmassey | values annotate ordering | 0 | 0 | 0 | 0 | 0 | 0 | |||
10763 | 2009-04-07 21:33:21 | 2011-09-28 16:12:23 | 2022-03-06 03:48:08.811170 | Unreviewed | closed | contrib.auth | 1.1-beta | duplicate | Allow custom AuthenticationForm in django.contrib.auth login view. | The idea is: allow develop to set a custom authentication form in login view without change much code. Support of custom forms is usefull if developer use a custom form class, if plan to make more things in authentication that default form does (if for some motive he not want to write your own view) and, after all, form is better place to validate trought e-mail instead username (a common request I think). This patch allow develop to send own authentication form to login view in urls.py and do what he wants in form. I attach patch, a urls.py snippet and a form that I used to show example. My form use <a href="https://launchpad.net/django-form-utils">django-form-utils</a> in case to allow more customizable forms. | nobody | chronos | login, forms, authentication, customization, custom | 0 | 1 | 0 | 0 | 0 | 0 | ||
10769 | 2009-04-09 15:16:13 | 2011-09-28 16:12:21 | 2022-03-06 03:48:09.741985 | Unreviewed | closed | contrib.admin | 1.1-beta | duplicate | IntegrityError with generic relations, unique_together, and inline admin forms | Using the models and admin below, create a new !GenericAttachment object using the inline form on the Parent change page. Then create another one with the same slug. The result is an IntegrityError where "columns content_type_id, object_id, slug are not unique". This works fine for Attachment objects. Models: {{{ class Parent(models.Model): name = models.CharField(max_length=200) class Attachment(models.Model): name = models.CharField(max_length=200) parent = models.ForeignKey(Parent) slug = models.SlugField() class Meta: unique_together = ['parent', 'slug'] class GenericAttachment(models.Model): name = models.CharField(max_length=200) content_type = models.ForeignKey(ContentType) object_id = models.PositiveIntegerField() parent = generic.GenericForeignKey() slug = models.SlugField() class Meta: unique_together = ['content_type', 'object_id', 'slug'] }}} Admin: {{{ class GenericAttachmentInline(generic.GenericTabularInline): model = GenericAttachment class ParentAdmin(admin.ModelAdmin): inlines = [AttachmentInline, GenericAttachmentInline] admin.site.register(Attachment, admin.ModelAdmin) admin.site.register(GenericAttachment, admin.ModelAdmin) admin.site.register(Parent, ParentAdmin) }}} | nobody | rutt | 0 | 0 | 0 | 0 | 0 | 0 | |||
10770 | 2009-04-09 15:28:24 | 2011-09-28 16:12:21 | 2022-03-06 03:48:09.911664 | Unreviewed | closed | contrib.admin | 1.1-beta | duplicate | IntegrityError when creating multiple inline objects with ForeignKey and unique_together | Using the models below, enter two Attachment objects with the same slug on the Parent change page, and then save. The result is an IntegrityError where "columns parent_id, slug are not unique". If the two Attachment objects are created and saved individually, the admin shows the expected form error: "Attachment with this Parent and Slug already exists." Models: {{{ class Parent(models.Model): name = models.CharField(max_length=200) class Attachment(models.Model): name = models.CharField(max_length=200) parent = models.ForeignKey(Parent) slug = models.SlugField() class Meta: unique_together = ['parent', 'slug'] }}} Admin: {{{ class ParentAdmin(admin.ModelAdmin): inlines = [AttachmentInline] admin.site.register(Attachment, admin.ModelAdmin) admin.site.register(Parent, ParentAdmin) }}} | nobody | rutt | 0 | 0 | 0 | 0 | 0 | 0 | |||
10820 | 2009-04-15 10:26:18 | 2011-09-28 16:12:21 | 2022-03-06 03:48:17.716217 | Unreviewed | closed | contrib.auth | 1.1-beta | duplicate | Can't logout from admin interface | Hi guys, I'm using newer trunk version (15-04-2009) and found one problem. When I'm logged in AdminUI and click 'Logo out' link, it return 404 error django generate admin/admin/logout/ url instead of admin/logout/ ;) | nobody | strelnikovdmitrij | 0 | 0 | 0 | 0 | 0 | 0 | |||
10829 | 2009-04-15 22:05:15 | 2010-11-09 16:22:33 | 2022-03-06 03:48:19.295419 | Design decision needed | closed | Database layer (models, ORM) | 1.1-beta | duplicate | QuerySet.delete() attempts to delete unmanaged models. | When there is an unmanaged model which has a ForeignKey to an object that you're attempting to delete, the ORM attempts to delete it. In my case, this is a database view which doesn't support deletion. I'll update this with a bit more information and a method for reproducing the error later today, just want to get it on the radar. I'm also assigning this to the 1.1 milestone as not being able to delete an object associated with a managed model is kind of a big deal. Feel free to override me on it though. | nobody | justinlilly | unmanaged | 0 | 0 | 0 | 0 | 0 | 0 | ||
10986 | 2009-05-03 13:38:49 | 2009-05-03 13:48:22 | 2022-03-06 03:48:48.802264 | Unreviewed | closed | Generic views | 1.1-beta | duplicate | [patch] generic object_detail support for custom 404 page | It's handy to have custom 404 page for generic object_detail view. Such as "Sorry man, post not found". Here is a simple patch which adds handler404 keyword arg which should point to django template file. | nobody | redbaron | 0 | 1 | 0 | 0 | 0 | 0 | |||
11089 | 2009-05-13 00:13:57 | 2009-05-13 00:52:05 | 2022-03-06 03:49:04.080265 | Unreviewed | closed | Contrib apps | 1.1-beta | duplicate | contrib.auth.views.login should take an optional 'form' argument | I've been using http://www.djangosnippets.org/snippets/74/ to allow users to log in with their email address, and it has been working really nicely except that users with an email address over 30 characters can't log in. The fix is simply to increase the max_length attribute on the login form's username field, however to effect this change I needed to write a custom view, which was a duplicate of contrib.auth.views.login except that it used my custom form. My proposal is to add an optional 'form' argument to contrib.auth.views.login - that way I could just put {{{ (r'^accounts/login/$', auth_views.login, {'form': MyAuthenticationForm}), }}} in my url conf. | nobody | gregplaysguitar | 0 | 0 | 0 | 0 | 0 | 0 | |||
11105 | 2009-05-13 19:56:47 | 2009-05-13 20:16:38 | 2022-03-06 03:49:06.472572 | Unreviewed | closed | Internationalization | 1.1-beta | duplicate | Permission names should be translated on syncdb | The basic permissions created during ''syncdb'' (add, change, delete) should be localized according to the LANGUAGE_CODE. Permission names are the only human-readable representation available to apps using contrib.auth, and are also used on contrib.admin, so it's kind of disappointing that all the admin is translated, but still unusable for managing permissions by non-english speakers because permissions aren't translated. The relevant code is at {{{django/contrib/auth/management/__init__.py:12}}} {{{ def _get_all_permissions(opts): "Returns (codename, name) for all permissions in the given opts." perms = [] for action in ('add', 'change', 'delete'): perms.append((_get_permission_codename(action, opts), u'Can %s %s' % (action, opts.verbose_name_raw))) return perms + list(opts.permissions) }}} I tried a patch (see attachment), and created translations to my locale (pt_BR), but ''syncdb'' doesn't seem to consider translations. Looking for an insight on this, fixing this should be trivial, and would help a lot those using contrib.auth (today I need to edit all my permission's names by hand to about 60 models, it sucks). | nobody | hcarvalhoalves | 0 | 1 | 0 | 0 | 0 | 0 | |||
11125 | 2009-05-15 21:54:24 | 2011-09-28 16:12:21 | 2022-03-06 03:49:09.635072 | Unreviewed | closed | contrib.comments | 1.1-beta | duplicate | comment redirect does not work with preview | I'm using rev. 10790, the latest version as of the time this ticket was submitted. The django docs [http://docs.djangoproject.com/en/dev/ref/contrib/comments/#redirecting-after-the-comment-post say] that you can redirect after a comment is posted by including a field like this in your comment form: {{{ <input type="hidden" name="next" value="{% url my_comment_was_posted %}" /> }}} However, this is incorrect. The post_comment view in django.contrib.comments.views.comments does not preserve this field for the comment preview form. Thus in the preview form template, the next variable is always None. The reason why is clear: {{{ def post_comment(request, next=None): }}} There is never a "next" keyword argument passed to this view, so next is always None. | nobody | james_stevenson | next redirect | 0 | 1 | 0 | 0 | 0 | 0 | ||
11219 | 2009-05-27 17:45:37 | 2009-05-27 17:52:44 | 2022-03-06 03:49:24.611953 | Unreviewed | closed | Core (Other) | 1.1-beta | duplicate | build_rpm problems | (Same issue as reported in ticket 3338.) RPMs don't like dashes in the version name. Running "python setup.py bdist_rpm" blows up because of this. The very same hack reported in 3338 can be used to fix this. It looks like this is a regression. Please see 3338 for the details. Thank you. | nobody | guitarmanvt | build_rpm | 0 | 0 | 0 | 0 | 0 | 0 | ||
11239 | 2009-05-31 11:33:27 | 2011-09-28 16:12:21 | 2022-03-06 03:49:27.415668 | Unreviewed | closed | contrib.admin | 1.1-beta | duplicate | logging out of the admin site from the changelist page or the changeform gives a ValueError | the logout link in the admin changelist or changeform pages references /admin/app_name/model_name/admin/logout/ and when you click on it, will give a ValueError invalid literal for int() with base 10: 'admin/logout while the logout link from the admin home page also points to /admin/admin/logout/ To log out of the admin you have to enter the /admin/logout/ url in the address bar manually. | nobody | boyombo | admin logout | 0 | 0 | 0 | 0 | 0 | 0 | ||
11334 | 2009-06-17 17:12:57 | 2012-03-06 21:01:47 | 2022-03-06 03:49:40.995788 | Accepted | closed | Core (Other) | Bug | Normal | 1.1-beta | duplicate | Django fails to show non-latin exception messages from PostgreSQL running on FastCGI | Run django via FastCGI (used nginx 0.6.x to deploy) with PosgreSQL. Try to execute some query, that will produce an error. If the error returned by PosgreSQL is not latin (Russian in my case), django tries to render an error page, but fails. nginx return a page with "Unhandled exception" If you turn on debug in flup, you will see the traceback, that shows that django tries to force_unicode the error message and fails with UnicodeDecodeError, so the user cannot determine the problem. I'll attach a flup error page with stack trace. | nobody | Loststylus | 0 | 0 | 0 | 0 | 0 | 0 | |
11386 | 2009-06-26 10:50:47 | 2009-07-10 14:55:04 | 2022-03-06 03:49:48.408760 | Unreviewed | closed | Core (Management commands) | 1.1-beta | duplicate | manage.py sqlall error msg says it did not find an app when it found it | run $python manage.py sqlall appname when django FINDS the app but there is an exception in the app's models file, manage.py still says: "Error: App with label comps_clists_draft could not be found. Are you sure your INSTALLED_APPS setting is correct?" although it did find the app. maybe that specific exception should give a "apps found, models file has a problem" message catching this exception occurs at django/db/models/loading.py line 74 | nobody | aviahl | sqlall manage.py | 0 | 0 | 0 | 0 | 0 | 0 | ||
11397 | 2009-06-29 03:35:24 | 2011-04-02 02:51:32 | 2022-03-06 03:49:49.972586 | Accepted | closed | contrib.admin | New feature | Normal | 1.1-beta | duplicate | [New Feature In Admin] Added Edit-Icon in selection widget of ForeignKey and ManyToMany Fields(Relationship fields). | Added a Edit-Icon to edit selected items in selection widget of ForeignKey and ManyToMany fields(Relationship fields) in admin interface. | Dharmesh [Patel | dharmesh | Edit Icon, edit selected item in selection widget | 0 | 1 | 0 | 0 | 0 | 0 |
11452 | 2009-07-10 11:15:57 | 2009-07-12 19:36:10 | 2022-03-06 03:49:57.616367 | Unreviewed | closed | Core (Management commands) | 1.1-beta | duplicate | Using filter_horizontal on a field in admin stops its help_text appearing | As soon as the filter_horizontal is removed, the help_text reappears. | nobody | EvilDMP | 0 | 0 | 0 | 0 | 0 | 0 | |||
11456 | 2009-07-10 18:37:45 | 2010-02-04 19:32:40 | 2022-03-06 03:49:58.152781 | Accepted | closed | Contrib apps | 1.1-beta | duplicate | flatpages append slash not working with unicode urls | The append slash is currently: {{{ if not url.endswith('/') and settings.APPEND_SLASH: return HttpResponseRedirect("%s/" % request.path) }}} It works fine for non-unicode urls. However, when using another regex for the url field which allows unicode chars in it, request.path needs to be quoted for the redirection to work: {{{ if not url.endswith('/') and settings.APPEND_SLASH: return HttpResponseRedirect("%s/" % iri_to_uri(urlquote(request.path))) }}} | nobody | hadaraz | flatpages | 0 | 0 | 0 | 0 | 0 | 0 | ||
11466 | 2009-07-12 19:16:28 | 2009-07-12 19:32:57 | 2022-03-06 03:49:59.472173 | Unreviewed | closed | contrib.admin | 1.1-beta | duplicate | Problem with 'logout', 'change password' links in contrib.admin interface | '''Currently in ''"django/contrib/admin/templates/admin/base.html" '' there is a line:''' <div id="user-tools">{% trans 'Welcome,' %} <strong>{% firstof user.first_name user.username %}</strong>. {% block userlinks %}{% url django-admindocs-docroot as docsroot %}{% if docsroot %}<a href="{{ docsroot }}">{% trans 'Documentation' %}</a> / {% endif %}<a href="{{ root_path }}password_change/">{% trans 'Change password' %}</a> / <a href="{{ root_path }}logout/">{% trans 'Log out' %}</a>{% endblock %}</div>--> '''It should be replaced with:''' <div id="user-tools">{% trans 'Welcome,' %} <strong>{% firstof user.first_name user.username %}</strong>. {% block userlinks %}{% url django-admindocs-docroot as docsroot %}{% if docsroot %}<a href="{{ docsroot }}">{% trans 'Documentation' %}</a> / {% endif %}<a href="/{{ root_path }}password_change/">{% trans 'Change password' %}</a> / <a href="/{{ root_path }}logout/">{% trans 'Log out' %}</a>{% endblock %}</div> '''Reason:''' {{root_path}} variable does not contain a trailing slash. As a result, logout and change password links are relative, not absolute. It leads to 404 error when using the links from the pages other then home one. The solution is to add a trailing slash in front of {{root_path}} variable. | nobody | gurunars | 0 | 0 | 0 | 0 | 0 | 0 | |||
11475 | 2009-07-14 07:34:03 | 2013-05-23 09:22:08 | 2022-03-06 03:50:00.763568 | Accepted | closed | Testing framework | Bug | Normal | 1.1-beta | duplicate | test.Client.session.save() raises error for anonymous users | I am trying to save data into the session object for an anonymous user. While I can do this for "real" using `request.session[key] = value` I am not able to simulate this during testing (by calling `test.Client.session.save()`). A quick round of debugging revealed that the test client uses a regular dictionary object for storing session data in the case of anonymous users (as opposed to a SessionStore object for known/authenticated users). This causes an error when I try to call `self.client.session.save()` from the `setUp()` method of my test class before running a test case. {{{ from django.test import Client, TestCase class MyTestCase(TestCase): def setUp(self): self.client = Client() self.client.session['key'] = 'value' self.client.session.save() # AttributeError: 'dict' object has no attribute 'save' def test_foo(self): self.assertEqual(1, 1) }}} I have included `django.contrib.sessions` in my `INSTALLED_APPS`. | nobody | egmanoj@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | |
11571 | 2009-07-27 23:26:32 | 2009-07-28 11:47:02 | 2022-03-06 03:50:14.839734 | Unreviewed | closed | Documentation | 1.1-beta | duplicate | latex documentation generation error | building latex documentation fails with the following error: Markup is unsupported in LaTeX: ref/contrib/admin/actions:: too many nesting section levels for LaTeX, at heading: Writing action functions make: *** [latex] Error 1 | nobody | nsmgr8 | latex, pdf | 0 | 0 | 0 | 0 | 0 | 0 | ||
7506 | 2008-06-19 18:15:07 | 2011-09-28 16:12:21 | 2022-03-06 03:39:49.126719 | Accepted | closed | Database layer (models, ORM) | 1.1-beta | fixed | Unable to pickle certain QuerySet objects due to use of curry function in RelatedField | QuerySet objects containing Model objects that have a RelatedField attribute are not pickle-able due to the use of the curry function in RelatedField. The Python pickle/cPickle modules can only serialize objects that are defined at the top level of a module. Since the curry function returns a nested function, pickling fails. In this case, the use of curry to create a partial function seems unnecessary. Equivalent functionality can be achieved by storing the curry parameters in an instance variable. This appears to be the simplest fix to this problem, so it's probably the right one. I've attached a diff for related.py that implements this fix. Alternatively, re-implementing the curry function as a callable class may work, but not without some trickery in getstate to get the callable to pickle. | jacob | mmalone | QuerySet pickle curry | 0 | 0 | 0 | 0 | 0 | 0 | ||
7521 | 2008-06-21 18:21:55 | 2011-09-28 16:12:17 | 2022-03-06 03:39:51.692667 | Accepted | closed | Testing framework | 1.1-beta | fixed | auth/tests fail on custom project with "manage.py test" | The auth/tests.py, which evidently was added yesterday, produces some failed assertions when enacted by 'python manage.py test': {{{ ====================================================================== FAIL: test_email_found (django.contrib.auth.tests.PasswordResetTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/auth/tests.py", line 71, in test_email_found self.assertEquals(response.status_code, 302) AssertionError: 404 != 302 ====================================================================== FAIL: test_email_not_found (django.contrib.auth.tests.PasswordResetTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/auth/tests.py", line 64, in test_email_not_found self.assertEquals(response.status_code, 200) AssertionError: 404 != 200 ---------------------------------------------------------------------- }}} | telenieko | anonymous | test failure | 0 | 1 | 0 | 0 | 0 | 0 | ||
8160 | 2008-08-08 11:42:41 | 2011-10-09 13:42:11 | 2022-03-06 03:41:30.955845 | Accepted | closed | Forms | Bug | Normal | 1.1-beta | fixed | ModelFormset ignores form properties | The implementation of modelformset_factory and inlineformset_factory ignore 'fields' and 'excludes' attributes of the supplied form (in fact all of Meta), and only use the values passed to the factory function. Also the ModelFormset and InlineFormset 'save' method ignores the 'save' method of the supplied form. {{{ #!python class MyModelForm (django.forms.models.ModelForm): class Meta: model = models.MyModel fields = ('field1', 'field2') def save(self): m = super(MyModelForm, self).save() do_something_with(m) return m MyFormSet = modelformset_factory(models.MyModel, MyModelForm) fset = MyFormSet() }}} The forms that are part of fset have all fields of models.MyModel and not just 'field1' and 'field2' as expected. Also fset.save() will not call 'do_something_with' on the models saved. Much of the functionality of the ModelForm is ignored when used as part of a formset. This may be intended behavior, but it is not mentioned in the manual as far as I can see, and is not what one might expect. | jkocherhans | andrew.mcmurry@ifi.uio.no | formset | 0 | 1 | 0 | 0 | 0 | 0 |
10617 | 2009-03-24 20:44:57 | 2011-09-28 16:12:21 | 2022-03-06 03:47:47.042173 | Ready for checkin | closed | Documentation | 1.1-beta | fixed | Typo in docs/ref/contrib/admin/index.txt | Line 680: "actions_on_top, actions_on_buttom" should read "actions_on_top, actions_on_bottom" | nobody | UloPe | typo docs | 0 | 1 | 0 | 0 | 0 | 0 | ||
10620 | 2009-03-25 06:35:17 | 2011-09-28 16:12:21 | 2022-03-06 03:47:47.525717 | Accepted | closed | GIS | 1.1-beta | fixed | All .py files have LF line endings except test_mutable_list.py | Source file http://code.djangoproject.com/svn/django/trunk/django/contrib/gis/geos/tests/test_mutable_list.py (as of revision 10170 and version 1.1-beta-1) has CRLF line endings, whereas all other .py files under http://code.djangoproject.com/svn/django/trunk/django/ have LF line endings. This interfered with a Python 2to3 conversion that I was experimenting with, although I am very aware that Python 3 is not supported yet. Minimal solution: Replace the CRLF line endings in file test_mutable_list.py with LF line endings. Full solution: Replace the CRLF line endings in file test_mutable_list.py with LF line endings, then set the "svn:mime-type" property of all .py files to "text/x-python", and set the "svn:eol-style" property of all .py files to "native". | nobody | ruiyen | 0 | 0 | 0 | 0 | 0 | 0 | |||
10635 | 2009-03-26 14:44:21 | 2011-09-28 16:12:21 | 2022-03-06 03:47:50.040319 | Accepted | closed | Documentation | 1.1-beta | fixed | list_editable: mention Meta class in ordering exception | {{{ >>> l = (opts.ordering or cls.ordering) >>> l [ '-id' ] >>> not l False >>> }}} Following patch fixes this bug. {{{ To apply: $ cd <django-src-root> $ patch -p0 < contrib.admin.validate.patch0 For example, $ cd /usr/lib/python2.5/site-packages/django/ $ sudo patch -p0 < $OLDPWD/contrib.admin.validate.patch0 $ cd - --- /dev/null +++ ./contrib/admin/validation.py 2009-03-26 10:37:36.000000000 -0400 @@ -67,7 +67,7 @@ # list_editable if hasattr(cls, 'list_editable') and cls.list_editable: check_isseq(cls, 'list_editable', cls.list_editable) - if not (opts.ordering or cls.ordering): + if not len(opts.ordering or cls.ordering): raise ImproperlyConfigured("'%s.list_editable' cannot be used " "without a default ordering. Please define ordering on either %s or %s." % (cls.__name__, cls.__name__, model.__name__)) }}} | jacob | mkbucc@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | |||
10646 | 2009-03-27 23:03:57 | 2011-09-28 16:12:23 | 2022-03-06 03:47:51.850650 | Ready for checkin | closed | Core (Cache system) | 1.1-beta | fixed | memcached's incr and decr should throw ValueError if keys don't exist | The "incr" and "decr" methods of the "django.core.cache.backends.memcached.CacheClass" should throw a ValueError if the "key" to increase/decrease does not exist. Right now, two things can happen trying to increase/decrease an invalid key, depending on the python memcached backend you're using: Using "cmemcache", you simply a `None` as return value. Using "memcache", you'll get some weird ValueErrors telling you that you cannot convert "NOT_FOUND" to an int ("memcache" tries to return the memcache server's return value as int). See the attached patch for a fix. | anonymous | dauerbaustelle | memcached, cache, incr, decr, sprint200912 | 0 | 1 | 0 | 0 | 0 | 0 | ||
10672 | 2009-03-31 03:51:10 | 2011-09-28 16:12:21 | 2022-03-06 03:47:55.500776 | Accepted | closed | Database layer (models, ORM) | 1.1-beta | fixed | Proxy Model does not send save signal | {{{ from django.test import TestCase from django.db import models class Test1Model(models.Model): field1 = models.CharField(max_length=10) class TestProxyModel(Test1Model): class Meta: proxy = True class ProxySignalTest(TestCase): def test_proxy_signal(self): from django.db.models import signals def save_signal(): raise Exception() signals.post_save.connect(save_signal, sender=TestProxyModel) tp = TestProxyModel(field1="test1") self.assertRaises(Exception, tp.save) }}} This test case fails as the save signal never gets called. | Nobody | zbyte64 | 0 | 1 | 0 | 0 | 0 | 0 | |||
10677 | 2009-03-31 14:53:27 | 2011-09-28 16:12:21 | 2022-03-06 03:47:56.080668 | Accepted | closed | contrib.comments | 1.1-beta | fixed | post_save_moderation breaks confirmation view | I tried out the new moderation tools and I found that when a comment is deleted in the post_save signal handler post_save_moderation(), it breaks the comment confirmation view because the comment instance is gone and _get_pk_val() returns None. This causes the following traceback for the redirected request. {{{ File "/var/lib/python-support/python2.5/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/var/lib/python-support/python2.5/django/contrib/comments/views/utils.py" in confirmed 41. comment = comments.get_model().objects.get(pk=request.GET['c']) File "/var/lib/python-support/python2.5/django/db/models/manager.py" in get 93. return self.get_query_set().get(*args, **kwargs) File "/var/lib/python-support/python2.5/django/db/models/query.py" in get 303. clone = self.filter(*args, **kwargs) File "/var/lib/python-support/python2.5/django/db/models/query.py" in filter 489. return self._filter_or_exclude(False, *args, **kwargs) File "/var/lib/python-support/python2.5/django/db/models/query.py" in _filter_or_exclude 507. clone.query.add_q(Q(*args, **kwargs)) File "/var/lib/python-support/python2.5/django/db/models/sql/query.py" in add_q 1258. can_reuse=used_aliases) File "/var/lib/python-support/python2.5/django/db/models/sql/query.py" in add_filter 1201. self.where.add((alias, col, field, lookup_type, value), connector) File "/var/lib/python-support/python2.5/django/db/models/sql/where.py" in add 48. params = field.get_db_prep_lookup(lookup_type, value) File "/var/lib/python-support/python2.5/django/db/models/fields/__init__.py" in get_db_prep_lookup 202. return [self.get_db_prep_value(value)] File "/var/lib/python-support/python2.5/django/db/models/fields/__init__.py" in get_db_prep_value 353. return int(value) Exception Type: ValueError at /comments/posted/… | nobody | nate-django@refried.org | django comments moderation | 0 | 1 | 0 | 0 | 0 | 0 | ||
10738 | 2009-04-05 09:47:20 | 2011-09-28 16:12:21 | 2022-03-06 03:48:04.823990 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | fixed | ContentType and model instances with deferred fields | Suppose we have model like this: {{{ class Entry(models.Model): title = models.CharField(max_length=128) body = models.TextField() }}} {{{ >>> from blog.models import Entry >>> # creating new entry object >>> Entry.objects.create(title="test entry", body="some body content") >>> entry_1 = Entry.objects.get(title="test entry") >>> entry_2 = Entry.objects.defer('body').get(title="test entry") >>> from django.contrib.contenttypes.models import ContentType >>> ContentType.objects.get_for_model(e1) <ContentType: entry> >>> ContentType.objects.get_for_model(e2) <ContentType: entry_ deferred_body> }}} `ContentTypes` for the same model instances with and without deferred fields are not the same (I suppose that's because they're not instances of the same class and have different `_meta.object.name` value). I'm not sure if that's the correct behavior. I mean - does the instance with deferred field(s) should have different `ContentType`? I found this issue when i tried use django-tagging and it's template tag `tags_for_object` with 'deferred `QuerySet`'. But maybe described behavior is correct and that's django-tagging bug? | nobody | tomasz.elendt | 0 | 1 | 0 | 0 | 0 | 0 | |||
10747 | 2009-04-06 04:38:56 | 2011-09-28 16:12:21 | 2022-03-06 03:48:06.222822 | Unreviewed | closed | contrib.auth | 1.1-beta | fixed | django.contrib.auth logout test fails after [10332] | The test_logout_default fails for me when I run my projects test suite. I have django.contrib.auth in my INSTALLED_APPS. The traceback is (note this is a red-herring): {{{ ====================================================================== ERROR: Logout without next_page option renders the default template ---------------------------------------------------------------------- Traceback (most recent call last): File "/xxx/django/django/contrib/auth/tests/views.py", line 208, in test_logout_default response = self.client.get('/logout_test/') File "/xxx/django/django/test/client.py", line 280, in get response = self.request(**r) File "/xxx/vendor/django/django/test/client.py", line 224, in request response = self.handler(environ) File "/xxx/vendor/django/django/test/client.py", line 68, in __call__ response = self.get_response(request) File "/xxx/vendor/django/django/core/handlers/base.py", line 122, in get_response return self.handle_uncaught_exception(request, resolver, sys.exc_info()) File "/xxx/nong/vendor/django/django/core/handlers/base.py", line 165, in handle_uncaught_exception callback, param_dict = resolver.resolve500() File "/xxx/vendor/django/django/core/urlresolvers.py", line 229, in resolve500 return self._resolve_special('500') File "/xxx/vendor/django/django/core/urlresolvers.py", line 218, in _resolve_special callback = getattr(self.urlconf_module, 'handler%s' % view_type) AttributeError: 'module' object has no attribute 'handler500' ---------------------------------------------------------------------- }}} Which template the logout view uses depends on your INSTALLED_APPS list order and whether or not you have your own {{{registration/logged_out.html}}}, which I do. The traceback above is a red-herring because what is happening is that the logout view is finding my project's {{{registration/logged_out.html}}} template which has a few {{{{% url ... %}}}}'s in it but the test runner is unable to resolve all those oth… | nobody | Matthew Flanagan <mattimustang@gmail.com> | 0 | 1 | 0 | 0 | 0 | 0 | |||
10807 | 2009-04-13 20:24:35 | 2011-09-28 16:12:21 | 2022-03-06 03:48:15.642947 | Accepted | closed | GIS | 1.1-beta | fixed | 'Constraint' object has no attribute 'relabel_aliases' when using | with GeoQueryset | {{{ from django.contrib.auth.models import User from django.contrib.gis.db import models class Place(models.Model): name = models.CharField(max_length=100) location = models.PointField() objects = models.GeoManager() def __unicode__(self): return self.name }}} {{{ from django.contrib.gis.geos import Point from django.contrib.gis.measure import D from djtest.models import Place point = Point(x=0, y=0) place1 = Place.objects.create(name='A', location=point) place2 = Place.objects.create(name='B', location=point) qs1 = Place.objects.filter(name='A', location__distance_lte=(point, D(mi=5))) qs2 = Place.objects.filter(name='B', location__distance_lte=(point, D(mi=5))) qs1 | qs2 }}} {{{ Traceback (most recent call last): File "test.py", line 13, in <module> qs1 | qs2 File "/a/djtest/lib/python2.6/site-packages/django/db/models/query.py", line 163, in __or__ combined.query.combine(other.query, sql.OR) File "/a/djtest/lib/python2.6/site-packages/django/db/models/sql/query.py", line 500, in combine w.relabel_aliases(change_map) File "/a/djtest/lib/python2.6/site-packages/django/db/models/sql/where.py", line 226, in relabel_aliases child[0].relabel_aliases(change_map) AttributeError: 'Constraint' object has no attribute 'relabel_aliases' }}} | bretthoerner | 0 | 0 | 0 | 0 | 0 | 0 | ||||
10878 | 2009-04-20 20:50:50 | 2011-09-28 16:12:23 | 2022-03-06 03:48:29.163205 | Ready for checkin | closed | contrib.comments | 1.1-beta | fixed | Comments moderation.py docstring error | It seems that "Moderator" should be used in place of "CommentModerator" at line 310 in django.contrib.comments.moderation.py docstring. | ubernostrum | lucalenardi | 0 | 1 | 0 | 0 | 0 | 0 | |||
10889 | 2009-04-22 14:58:03 | 2011-09-28 16:12:21 | 2022-03-06 03:48:31.023343 | Ready for checkin | closed | contrib.admin | 1.1-beta | fixed | ModelAdmin calls .log_deletion after deletion, causing invalid object_id | When an object is deleted, its PK value is set to None. Unfortunately, ModelAdmin calls log_deletion (which results in a LogEntry) after object.delete, so that LogEntry's with DELETION action_flag have u'None' as their PK. This is less than useful, since I sometimes what to trace the full history of an object through LogEvent, and object_repr isn't really enough to do that. | nobody | jdunck | 0 | 1 | 0 | 0 | 0 | 0 | |||
10897 | 2009-04-22 21:07:58 | 2011-09-28 16:12:21 | 2022-03-06 03:48:32.272767 | Ready for checkin | closed | contrib.admin | 1.1-beta | fixed | ngettext is used in confirmation of bulk-edits in admin | Confirmation of bulk-edits in admin is translated with ngettext(). This breaks badly with UnicodeDecodeError when language of the admin interface is other than English (I can confirm this issue with Polish at least). Attached patch fixes this problem. | nobody | zuber | 0 | 1 | 0 | 0 | 0 | 0 | |||
10898 | 2009-04-22 21:23:57 | 2011-09-28 16:12:21 | 2022-03-06 03:48:32.403438 | Accepted | closed | Documentation | 1.1-beta | fixed | Bugs in 'conditional view processing' doc | First of all there's bug in code sample in `latest_entry` function, which should returns `datetime` object instead of `dict`. There's also one typo (`last_modified` instead of `last_modified_func`). | nobody | tomasz.elendt | 0 | 1 | 0 | 0 | 0 | 0 | |||
10927 | 2009-04-25 15:52:31 | 2009-12-19 15:31:29 | 2022-03-06 03:48:36.876238 | Ready for checkin | closed | Contrib apps | 1.1-beta | fixed | Content Types shortcut view throws 500s easily | BaseHandler.handle_uncaught_exception calls mail_admins any time an uncaught exception occurs. In my general usage, this is very rare. The contenttypes.views.shortcut view, many arbitrary URLs will throw a 500. Since crawlers probe URL spaces, this leads to a lot of noise in error emails. | nobody | jdunck | 0 | 1 | 0 | 0 | 0 | 0 | |||
10989 | 2009-05-03 21:44:15 | 2011-09-28 16:12:23 | 2022-03-06 03:48:49.419548 | Ready for checkin | closed | Documentation | 1.1-beta | fixed | Typos in formset and widget media docs | /docs/topics/forms/formsets.txt line 141: now: BaseModelFormSet patch: BaseFormSet (here are only non "model forms" components described yet, although its true too) ---- /docs/topics/forms/media.txt line 179: now: model property patch: media property (or term "instance" or so??, nothing about models here) ---- (sorrry, tortoise-svn diff returned whole files replace, so here rather patches in text) | nobody | falken@mixworx.net | formset media | 0 | 1 | 0 | 0 | 0 | 0 | ||
11054 | 2009-05-08 20:48:54 | 2009-05-17 17:01:05 | 2022-03-06 03:48:59.147569 | Ready for checkin | closed | Documentation | 1.1-beta | fixed | Small typo in docs/howto/auth-remote-user.txt | I found a small typo in said file. Path attached. | nobody | Jan Hülsbergen | typo | 0 | 1 | 0 | 0 | 0 | 0 | ||
11194 | 2009-05-24 18:18:57 | 2011-09-28 16:12:21 | 2022-03-06 03:49:20.914221 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | fixed | Saving proxy model with raw=True gives UnboundLocalError 'record_exists' | When importing data I am running into this error: {{{ Problem installing fixture '../tpm/contacts/fixtures/sampladata.json': Traceback (most recent call last): File "/usr/local/lib/python2.5/site-packages/django/core/management/commands/loaddata.py", line 153, in handle obj.save() File "/usr/local/lib/python2.5/site-packages/django/core/serializers/base.py", line 163, in save models.Model.save_base(self.object, raw=True) File "/usr/local/lib/python2.5/site-packages/django/db/models/base.py", line 495, in save_base created=(not record_exists), raw=raw) UnboundLocalError: local variable 'record_exists' referenced before assignment }}} | nobody | wardi | proxy model serialization | 0 | 1 | 1 | 1 | 0 | 0 | ||
11218 | 2009-05-27 14:30:31 | 2011-09-28 16:12:21 | 2022-03-06 03:49:24.471461 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | fixed | typo: forgot to rename an occurrence (2) | No variable "results" in the function, seems there's no test to check this, but my PyDev Extensions nailed it down Please check the flow correctness, as I don't know what is going on there. {{{ diff --git a/django/db/models/sql/query.py b/django/db/models/sql/query.py index 394e30b..cc8c264 100644 --- a/django/db/models/sql/query.py +++ b/django/db/models/sql/query.py @@ -2362,7 +2362,7 @@ class BaseQuery(object): return cursor if result_type == SINGLE: if self.ordering_aliases: - return cursor.fetchone()[:-len(results.ordering_aliases)] + return cursor.fetchone()[:-len(self.ordering_aliases)] return cursor.fetchone() # The MULTI case. }}} | nobody | buriy | 0 | 1 | 0 | 0 | 0 | 0 | |||
11243 | 2009-06-01 09:39:00 | 2009-11-19 04:35:32 | 2022-03-06 03:49:27.945226 | Unreviewed | closed | contrib.admin | 1.1-beta | fixed | Not possible to add Model with URLField with the Admin Interface | --- models.py from django.db import models # Create your models here. class Weblink(models.Model): url = models.URLField(unique=True) def __unicode__(self): return self.url class Weblink2(models.Model): url = models.CharField(max_length=200, unique=True) def __unicode__(self): return self.url --- Activated Admin Interface. Can add Weblink Objects via the Postgres Database Interface (pgadmin). But not with the Django Admin interface. If the object save button is clicked at the http://localhost:8002/admin/references/weblink/add/ nothing is happening. Only Waiting for Localhost in Firefox and page loading activity in Firefox. Objects without URLField can be added via the Admin Interface without problems (Weblink2 is working). Worked in the release 1.0 but need the Development version (need the development version because of proxy classes in the model). Django version 1.1 beta 1, using settings 'testproject.settings' Development server is running at http://127.0.0.1:8002/ Quit the server with CONTROL-C. [01/Jun/2009 04:36:05] "GET / HTTP/1.1" 404 1915 [01/Jun/2009 04:36:09] "GET /admin HTTP/1.1" 301 0 [01/Jun/2009 04:36:09] "GET /admin/ HTTP/1.1" 200 3986 [01/Jun/2009 04:36:12] "GET /admin/references/weblink2/add/ HTTP/1.1" 200 2688 [01/Jun/2009 04:36:12] "GET /admin/jsi18n/ HTTP/1.1" 200 803 [01/Jun/2009 04:36:17] "POST /admin/references/weblink2/add/ HTTP/1.1" 302 0 [01/Jun/2009 04:36:17] "GET /admin/references/weblink2/ HTTP/1.1" 200 3032 [01/Jun/2009 04:36:21] "GET /admin/references/ HTTP/1.1" 200 2297 [01/Jun/2009 04:36:23] "GET /admin/references/weblink/add/ HTTP/1.1" 200 2681 [01/Jun/2009 04:36:23] "GET /admin/jsi18n/ HTTP/1.1" 200 803 | nobody | engrams | 0 | 0 | 0 | 0 | 0 | 0 | |||
11313 | 2009-06-12 20:05:30 | 2016-02-01 21:04:05 | 2022-03-06 03:49:38.022023 | Ready for checkin | closed | contrib.admin | Bug | Normal | 1.1-beta | fixed | list_editable fields don't support 'save' in multiuser environment | I don't think that the list_editable fields concept in the admin, as implmemented in 1.1, works. Imagine this: 1. User 1 brings up a changelist for an object and orders it by a 'deadline' field, most recent first, resulting in object 'foo' being shown as the most recent object 2. User 2 edits object 'foo' and changes its deadline field so that it is no longer the most recent object 3. User 1 still has the changelist form on his screen, and modifies the 'name' field of object foo. Then he hits 'save'. When the 'save' request from user 1 is processed, a queryset for the objects is created that is ordered by deadline. However, the ordering of the queryset in the POST request is different than the ordering of the queryset in the GET request made by user 1, due to the edit made by user 2. In the example I describe above, object foo is no longer the object that has the most recent deadline when the code processes user 1's POST request. Instead, object 'bar' is. In effect, it's as if the code thinks the user wants to change the name of object 'bar' instead of object 'foo'. However, the id sent with the post data is for object 'foo'. Eventually we get into _perform_unique_checks() and this sort of identifies that there is a problem. There is the following code: {{{ # Exclude the current object from the query if we are editing an # instance (as opposed to creating a new one) if self.instance.pk is not None: qs = qs.exclude(pk=self.instance.pk) }}} In a non-multiuser case I think this would exclude the instance being edited, but in this case it doesn't. The result is that we drop into the next lines of code which generate an error, but the error looks like this: "Task with this None already exists." It contains the word "None" because the id field does not have a laberl attribute (ie self.fields['id'].label is None). I see this error when I print the form but it actually doesn't even show up in the admin ui. I just see the message "… | nobody | margieroginski | model formsets | 0 | 1 | 0 | 0 | 0 | 0 |
11381 | 2009-06-25 22:12:04 | 2011-09-28 16:12:21 | 2022-03-06 03:49:47.721048 | Accepted | closed | GIS | 1.1-beta | fixed | select_related over nullable ForeignKey using GeoQuerySet and GeoManager gives blank object rather than None | Sorry for the bad title... I can only explain this with an example, {{{ from django.contrib.gis.db import models class Author(models.Model): name = models.CharField(max_length=100) class BookManager(models.GeoManager): def get_query_set(self): return super(BookManager, self).get_query_set().select_related('author') class Book(models.Model): name = models.CharField(max_length=100) author = models.ForeignKey(Author, related_name="books", null=True, blank=True) objects = BookManager() }}} {{{ >>> Book.objects.create(name='Without Author') <Book: Book object> >>> b = Book.objects.get(name='Without Author') >>> b.author <Author: Author object> >>> b.author.name }}} As you can see, rather than b.author being None, is it an "empty" Author object. This isn't the case when using non-GeoDjango. What's even weirder is that this only happens when using the GeoManager. If you remove the manager and run the select_related yourself, the following happens, {{{ >>> Book.objects.select_related('author').get(name='Without Author').author }}} It's None, rather than the "empty" Author from above. | nobody | bretthoerner | geodjango geo select_related geomanager | 0 | 1 | 0 | 1 | 0 | 0 | ||
11405 | 2009-06-30 06:00:59 | 2009-07-01 03:06:19 | 2022-03-06 03:49:51.000127 | Unreviewed | closed | Contrib apps | 1.1-beta | fixed | The select all checkbox for action in admin does not work with IE web browser. | I have test in IE 6/8, the select all checkbox does not work. But it can work with Safari or Firefox. | nobody | khsing | 0 | 0 | 0 | 0 | 0 | 0 | |||
11498 | 2009-07-17 19:22:28 | 2011-09-28 16:12:21 | 2022-03-06 03:50:04.203057 | Unreviewed | closed | Translations | 1.1-beta | fixed | Little mistake in Polish translation | There is a little mistake in Polish translation in admin actions. In context of admin actions "Go" should be translated as "Wykonaj" or something similar. Actual value - "Szukaj" means "Search". | zgoda | sayane | 0 | 1 | 0 | 0 | 0 | 0 | |||
11518 | 2009-07-21 17:13:06 | 2012-06-07 14:18:42 | 2022-03-06 03:50:07.042847 | Ready for checkin | closed | Core (Other) | Bug | Normal | 1.1-beta | fixed | Custom commands cannot be run from cron (or other directory) if project is not on Python Path | If I wanted to create a custom command say in myproj.weather application a custom command to get_latest_weather and wanted to run that in a cron job it would fail if myproj is not on the PYTHON PATH. I am using Python 2.6 and the imp.find_module is not finding the project path. I can see the project module does indeed exist in sys.modules | nobody | mark.ellul@gmail.com | custom commands | 0 | 1 | 0 | 0 | 0 | 0 |
11558 | 2009-07-26 14:53:58 | 2011-09-28 16:12:21 | 2022-03-06 03:50:12.790049 | Fixed on a branch | closed | Translations | 1.1-beta | fixed | Updated Italian localization | Just updated the references. makemessages didn't find any new string | nobody | gogna | 0 | 1 | 0 | 0 | 0 | 0 | |||
11567 | 2009-07-27 20:18:13 | 2011-09-28 16:12:21 | 2022-03-06 03:50:14.277048 | Unreviewed | closed | Translations | 1.1-beta | fixed | Translation update for Danish | Please update the translation for Danish (da) according to the attached diff file. This update is for Django 1.1. | nobody | finngruwier | 0 | 0 | 0 | 0 | 0 | 0 | |||
11594 | 2009-07-29 19:34:05 | 2011-09-28 16:12:27 | 2022-03-06 03:50:18.984141 | Ready for checkin | closed | Documentation | 1.1-beta | fixed | Inaccurate docstring for WhereNode.add() | r9700 changed the interface for {{{WhereNode.add()}}}, but it did not update the function's docstring to reflect the change. The docstring currently says: {{{ """ Add a node to the where-tree. If the data is a list or tuple, it is expected to be of the form (alias, col_name, field_obj, lookup_type, value), which is then slightly munged before being stored (to avoid storing any reference to field objects). Otherwise, the 'data' is stored unchanged and can be anything with an 'as_sql()' method. """ }}} As of r9700, if {{{data}}} is a list or tuple, it is actually expected to be of the form {{{(obj, lookup_type, value)}}}, where {{{obj}}} is a {{{Constraint}}} object. | dwillis | garrison | 0 | 1 | 0 | 0 | 0 | 0 | |||
11608 | 2009-07-31 11:45:47 | 2009-08-08 03:07:31 | 2022-03-06 03:50:21.023789 | Accepted | closed | Documentation | 1.1-beta | fixed | Django version in documentation should be 1.1 | In django 1.1 release docs still shows the version number 1.0. It should be 1.1. | nobody | nsmgr8 | 0 | 0 | 0 | 0 | 0 | 0 | |||
11609 | 2009-07-31 12:31:38 | 2011-09-28 16:12:23 | 2022-03-06 03:50:21.169835 | Accepted | closed | GIS | 1.1-beta | fixed | Allow for long pointer format in django.contrib.gis.gdal.base | My apache webserver is outputting long pointer types for the ESRI Driver. Adding a check for the long format and then converting it to int allows for the webserver to work correctly. | nobody | rmkemker | gdal.base | 0 | 0 | 1 | 1 | 0 | 0 | ||
13259 | 2010-04-01 07:26:48 | 2011-09-28 16:12:23 | 2022-03-06 03:54:41.990187 | Accepted | closed | Core (Mail) | 1.1-beta | fixed | multiple calls to message() breaks the mail content | The message() function from django/core/mail/message.py pop's out From header from extra_headers, so as a side effect, multiple calls to message() generates an email which has the from_email in the From header, instead of the one set in the headers. As a quick fix, one can reset "From" in extra headers just after calling the message(). | nobody | canburak | 0 | 1 | 0 | 1 | 0 | 0 | |||
8916 | 2008-09-06 18:39:30 | 2009-06-19 18:07:33 | 2022-03-06 03:43:30.713000 | Unreviewed | closed | contrib.admin | 1.1-beta | invalid | admin auth change password not working | Trying to access the change password form in auth admin will cause a "ValueError" Trace is below {{{ Environment: Request Method: GET Request URL: http://localhost:8000/admin/auth/user/1/password/ Django Version: 1.0-final-SVN-unknown Python Version: 2.5.0 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.admin', 'django.contrib.databrowse', 'pressDB.press', 'pressDB.ext'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.middleware.doc.XViewMiddleware') Traceback: File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/admin/sites.py" in root 158. return self.model_page(request, *url.split('/', 2)) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/views/decorators/cache.py" in _wrapped_view_func 44. response = view_func(request, *args, **kwargs) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/admin/sites.py" in model_page 177. return admin_obj(request, rest_of_url) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/admin/options.py" in __call__ 197. return self.change_view(request, unquote(url)) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/db/transaction.py" in _commit_on_success 238. res = func(*args, **kw) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/contrib/admin/options.py" in change_view 557. … | nobody | ask@jillion.dk | 0 | 0 | 0 | 0 | 0 | 0 | |||
9678 | 2008-11-24 15:11:47 | 2009-07-06 14:22:00 | 2022-03-06 03:45:26.006237 | Unreviewed | closed | Uncategorized | 1.1-beta | invalid | Flatpage with URL of "/" ends up in a redirect loop. | Picture a site with a flatpage at the root. This root flatpage in the admin tool has a "/" for the URL. The root flatpage gets into a redirect loop. All other flatpages except the root flatpage work fine. If Append_Slash is set to false, this perplexing behavior no longer occurs and the root flatpage works just fine. | nobody | watusee | flatpage | 0 | 0 | 0 | 0 | 0 | 0 | ||
10628 | 2009-03-26 07:05:59 | 2009-03-26 07:46:49 | 2022-03-06 03:47:48.951345 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | invalid | RelatedManager and NULL | My Model: {{{ class Active(models.Model): post = models.ForeignKey(Post, related_name='activeposts') rubrica = models.ForeignKey(Rubrica, related_name='activeposts', null=True, blank=True) type = models.ForeignKey(Type, related_name='activeposts', null=True, blank=True) }}} Code: {{{ >>> p = Post.objects.get(pk=1206535731) >>> p.activeposts.filter(type__pk=2, rubrica__isnull=True) }}} return empty result. but a have data in database. {{{ >>> p.activeposts.filter(type__exact=2, rubrica__isnull=True).query.as_sql() ('SELECT `doska_active`.`id`, `doska_active`.`post_id`, `doska_active`.`rubrica_id`, `doska_active`.`type_id` FROM `doska_active` LEFT OUTER JOIN `doska_rubrica` ON (`doska_active`.`rubrica_id` = `doska_rubrica`.`id`) WHERE (`doska_active`.`post_id` = %s AND `doska_active`.`type_id` = %s AND `doska_rubrica`.`id` IS NULL)', (1206535731, 2)) }}} Problem in '''AND `doska_rubrica`.`id` IS NULL''' | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
10873 | 2009-04-20 09:44:43 | 2009-04-21 10:53:44 | 2022-03-06 03:48:28.299771 | Unreviewed | closed | Template system | 1.1-beta | invalid | urlize | Adverted in the django docs is that a string http://www.example.com go's to <a href="http://www.example.com">www.example.com</a> http://docs.djangoproject.com/en/dev/ref/templates/builtins/#urlize However this is not the case when you use teh model.URLField that requires http:// and ads a "/" to the end. Resulting in <a href="http://www.example.com">http://www.example.com/</a> This is ugly and should be fixed! | nobody | onno | urlize | 0 | 0 | 0 | 0 | 0 | 0 | ||
10930 | 2009-04-26 15:08:44 | 2011-09-28 16:12:21 | 2022-03-06 03:48:37.411191 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | invalid | int_alias UnboundLocalError exception in query.py (reported by Wingware IDE defaults) | using latest wingware IDE which always reports UnboundLocalError exceptions by its default preferences, immediatelly during first application access to started devserver I discovered this small waste annoyance in code - I had ignored this error location according to this thread: http://groups.google.com/group/django-developers/browse_thread/thread/a5432ea21c40b667#, but today it occured again during debugging deeper in this code, so I decided to report it with quick patch. IMHO its better to have this ugly annoyance solved. | nobody | falken@mixworx.net | 0 | 1 | 0 | 0 | 0 | 0 | |||
10943 | 2009-04-28 01:52:54 | 2011-09-28 16:12:21 | 2022-03-06 03:48:39.736311 | Unreviewed | closed | Uncategorized | 1.1-beta | invalid | ordinal not in range(128) | Before Apri 24, it is worked fine that adding file whith chinese characters, but after Apri 27, error comes. I don't understand why. I hadn't upgraded anything. Help. {{{ UnicodeEncodeError at /admin/articles/article/18248/ ('ascii', u'/home/httpd/html/media/doc/2009/04/28/\u90b3\u5dde\u516c\u53f8\u8df5\u884c\u79d1\u5b66\u53d1\u5c55\u89c2\u670d\u52a1\u53d1\u5c55\u5f53\u5148\u950b.jpg', 38, 56, 'ordinal not in range(128)') Request Method: POST Request URL: http://172.30.113.203/admin/articles/article/18248/ Exception Type: UnicodeEncodeError Exception Value: ('ascii', u'/home/httpd/html/media/doc/2009/04/28/\u90b3\u5dde\u516c\u53f8\u8df5\u884c\u79d1\u5b66\u53d1\u5c55\u89c2\u670d\u52a1\u53d1\u5c55\u5f53\u5148\u950b.jpg', 38, 56, 'ordinal not in range(128)') Exception Location: /usr/lib/python2.6/genericpath.py in exists, line 18 Python Executable: /usr/bin/python Python Version: 2.6.0 Python Path: ['/home/lio/mydjango', '/usr/lib/python26.zip', '/usr/lib/python2.6', '/usr/lib/python2.5/site-packages', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/lib/python2.6/site-packages', '/usr/lib/python2.6/site-packages/PIL'] Server time: 星期二, 28 四月 2009 08:54:20 +0800 }}} {{{ Unicode error hint The string that could not be encoded/decoded was: 4/28/邳州公司践行科学发展观服务发展当先锋.jpg }}} {{{ Environment: Request Method: POST Request URL: http://172.30.113.203/admin/articles/article/18248/ Django Version: 1.1 beta 1 SVN-10638 Python Version: 2.6.0 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.admin', 'ncdqh.articles'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware') Traceback: File "/usr/lib/python2.6/site-packages/django/core/ha… | nobody | gulliver | 0 | 0 | 0 | 0 | 0 | 0 | |||
10987 | 2009-05-03 13:38:56 | 2009-05-03 16:16:38 | 2022-03-06 03:48:49.052170 | Unreviewed | closed | Generic views | 1.1-beta | invalid | [patch] generic object_detail support for custom 404 page | It's handy to have custom 404 page for generic object_detail view. Such as "Sorry man, post not found". Here is a simple patch which adds handler404 keyword arg which should point to django template file. | nobody | redbaron | 0 | 1 | 0 | 1 | 0 | 0 | |||
10998 | 2009-05-04 09:02:40 | 2011-07-16 07:02:02 | 2022-03-06 03:48:51.206516 | Unreviewed | closed | Uncategorized | Uncategorized | Normal | 1.1-beta | invalid | Django does not work with Python 3 | Django is not compatible with Python 3. | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |
11013 | 2009-05-05 15:20:54 | 2009-08-24 01:23:48 | 2022-03-06 03:48:53.200512 | Design decision needed | closed | Core (Other) | 1.1-beta | invalid | Named imports in urls | Every time there is an exception during testing (inside the tested code, not the tests), the only thing I get is: Traceback (most recent call last): File "/home/gruszczy/Programy/bozorth/../bozorth/issues/tests.py", line 194, in test_edit_sent_ticket_post_staff_only response = client.post(address, dictionary) File "/var/lib/python-support/python2.6/django/test/client.py", line 292, in post return self.request(**r) File "/var/lib/python-support/python2.6/django/test/client.py", line 217, in request response = self.handler(environ) File "/var/lib/python-support/python2.6/django/test/client.py", line 64, in __call__ response = self.get_response(request) File "/var/lib/python-support/python2.6/django/core/handlers/base.py", line 128, in get_response return self.handle_uncaught_exception(request, resolver, exc_info) File "/var/lib/python-support/python2.6/django/core/handlers/base.py", line 159, in handle_uncaught_exception callback, param_dict = resolver.resolve500() File "/var/lib/python-support/python2.6/django/core/urlresolvers.py", line 218, in resolve500 return self._resolve_special('500') File "/var/lib/python-support/python2.6/django/core/urlresolvers.py", line 207, in _resolve_special callback = getattr(self.urlconf_module, 'handler%s' % view_type) AttributeError: 'module' object has no attribute 'handler500' This gives me very little information about what happened inside. Is there any chance to pass more information, when such an exception occurs? | nobody | gruszczy | 0 | 1 | 0 | 1 | 0 | 0 | |||
11088 | 2009-05-12 22:59:14 | 2013-02-28 10:15:36 | 2022-03-06 03:49:03.947668 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | invalid | Aggregation problem, table JOINed twice | I don't know if I'm doing something wrong but I've tried to compile all the information needed to track this one. === Models === video/models.py {{{ class Video(models.Model): name = models.TextField() dir = models.TextField() videoclass = models.ForeignKey('Videoclass') status = models.CharField(max_length=24) date = models.DateTimeField() duration = models.FloatField() width = models.IntegerField() height = models.IntegerField() displayname = models.TextField() published = models.IntegerField() views = models.IntegerField() ratesum = models.IntegerField() ratenum = models.IntegerField() }}} statistics/models.py {{{ class VisitorAction(models.Model): name = models.CharField(max_length = 200) def __unicode__(self): return self.name class VisitorLog(models.Model): visitor = models.ForeignKey("Visitor") video = models.ForeignKey(Video) action = models.ForeignKey(VisitorAction) seek_video = models.FloatField() event_time = models.DateTimeField(default = datetime.datetime.now) domain = models.CharField(max_length = 128) }}} === Datas === statistics_visitorlog contains 100k+ entries video_video contains 400 entries statistics_visitoraction contains 6 entries ('play', 'seek' ... etc) === The QS === {{{ >>> from video.models import * >>> from django.db.models import Count >>> Video.objects.annotate(play_log = Count('visitorlog')).filter(visitorlog__action__name = 'play').order_by('-play_log')[0:10] }}} [Kill the mysqld because it takes forever and have a nice backtrace] {{{ >>> from django.db import connection >>> connection.queries[-1] {'time': '7.180', 'sql': u'SELECT `video_video`.`id`, `video_video`.`name`, `video_video`.`dir`, `video_video`.`videoclass_id`, `video_video`.`status`, `video_video`.`date`, `video_video`.`duration`, `video_video`.`width`, `video_video`.`height`, `video_video`.`displayname`, `video_video`.`published`, `video_video`.`views`, `… | loic@vflow.tv | aggregation, join | 0 | 0 | 0 | 0 | 0 | 0 | |||
11189 | 2009-05-24 02:54:54 | 2009-05-24 17:05:25 | 2022-03-06 03:49:20.083111 | Unreviewed | closed | contrib.admin | 1.1-beta | invalid | Admin add page rendering blank fieldset | Just installed the 1.1 Beta. Using sqlite3. Started a new project and app, created some models with some simple varchar fields. Registered them in admin. Logged in, attempted to add a new record. Get the add page, but no form. Actually I get a form but with a blank form fieldset. This is happening with each of my models. trace: http://dpaste.com/47091/ | nobody | epottercg@gmail.com | blank form add | 0 | 0 | 0 | 0 | 0 | 0 | ||
11214 | 2009-05-27 08:58:42 | 2009-05-28 07:46:56 | 2022-03-06 03:49:23.853576 | Unreviewed | closed | Forms | 1.1-beta | invalid | inline in django | I am having inlines in my model.I want that all the inlines should come as a readonly while updation | nobody | ankit | 0 | 0 | 0 | 0 | 0 | 0 | |||
11224 | 2009-05-28 07:46:40 | 2011-09-28 16:12:21 | 2022-03-06 03:49:25.317795 | Unreviewed | closed | Core (Management commands) | 1.1-beta | invalid | how to make forignkey readonly | I am having a model which has foriegnkey.I can make fields readonly using readonlyadmin.But if i set foreignkeyfield in readonly it gives error 'Can't adapt'.And if remove forignkey from the readonly list it doesnot gives. | nobody | ankit | 0 | 0 | 0 | 0 | 0 | 0 | |||
11255 | 2009-06-03 19:43:30 | 2011-09-28 16:12:21 | 2022-03-06 03:49:29.645755 | Unreviewed | closed | Uncategorized | 1.1-beta | invalid | Missing parameter in cursor method (BaseDatabaseWrapper) | In db/backends/__init__.py the cursor method of BaseDatabaseWrapper class, has a missed parameter (line 81). Original code (django 1.1 beta1 - trunk) {{{ def cursor(self): from django.conf import settings cursor = self._cursor() #<--here if settings.DEBUG: return self.make_debug_cursor(cursor) return cursor }}} In line 81: cursor = self._cursor() Should be: cursor = self._cursor(setting) When I run syncdb, a missing parameter error is raised. | nobody | maxi | 0 | 0 | 0 | 0 | 0 | 0 | |||
11307 | 2009-06-12 04:52:59 | 2009-06-12 05:00:49 | 2022-03-06 03:49:37.217267 | Unreviewed | closed | Template system | 1.1-beta | invalid | template | '''''Inline template''''' In my template can i used <a href> tag.i want that if there is a field named 'id' it should give a href link over there.I have tried following options 1){% ifequal field.field.label "Id" %} <a href =../../{{field.field}}>click here </a> 2){% ifequal field.field.label "Id" %} <a href ="../../{{field.field}}">click here </a> 3){% ifequal field.field.label "Id" %} <a href =../../{{field.field.value}}>click here </a> 4){% ifequal field.field.label "Id" %} <a href ="../../"{{field.field}}>click here </a> 5){% ifequal field.field.label "Id" %} <a href ={{field.field}}>click here </a> in this case it is showing the addres of the current page.Means not showing the value of field.field All the options does not work .It is not showing the value of field.field in href.field.field.label shows Id in href when I displays the value field.field {{field.field}} it is showing correct value. | nobody | ankit | 0 | 0 | 0 | 0 | 0 | 0 | |||
11309 | 2009-06-12 06:50:21 | 2009-06-12 06:56:03 | 2022-03-06 03:49:37.480238 | Unreviewed | closed | Template system | 1.1-beta | invalid | template | ''inline template '' I want to use <a href > tag in the template where i found the field named as 'Id'. {% for fieldset in inline_admin_form %} {% for line in fieldset %} {% for field in line %} <td class="original {{ field.field.name }}"> {{ field.field.errors.as_ul }} <div name="foobar_a" {% ifequal field.field.label "Id" %} {% endifequal %} > {{ field.field }} </span> </td> {% endfor %} {% endfor %} {% endfor %} in if condition i want a href tag to be placed. I have tried several option but are not working 1)<a href =../../{{fieild.field}}>click here </a> 2)<a href = '../../'{{field.field}}>click here </a> 3)<a href ='../../{{field.field}}'>click here</a> {{field.field.label}} is giving 'Id' when i write {{field.field}} it is giving the correct value but when i write it inside <a href tag it does not show any value | nobody | ankit | inline -template | 0 | 0 | 0 | 0 | 0 | 0 | ||
11552 | 2009-07-25 09:07:20 | 2011-09-28 16:12:21 | 2022-03-06 03:50:11.927223 | Unreviewed | closed | Translations | 1.1-beta | invalid | Action menu in Django Admin is not translated (nl-nl) | The new action menu in Django Admin is not (properly) translated. For example: The button says 'search' (that isn't correct) and the confirmation screen after you choose an action is still in English. I'm a Django/Python newbe, so I apology that I didn't include a patch. | nobody | anonymous | Admin, action menu | 0 | 0 | 0 | 0 | 0 | 0 | ||
11602 | 2009-07-30 13:33:51 | 2009-07-30 20:00:26 | 2022-03-06 03:50:20.219656 | Unreviewed | closed | *.djangoproject.com | 1.1-beta | invalid | Django versions (fork the docs for 1.1 and trunk) | Since Django 1.1 is out, the 1.1 docs should be in a directory 1.1 and the search on the right side should have a selection 1.1. Also, the This document is for Django's SVN release, which can be significantly different from previous releases. Get old docs here: Django 1.0 warning should be changed accordingly | nobody | pihentagy | website version | 0 | 0 | 0 | 0 | 0 | 0 | ||
11846 | 2009-09-07 13:04:05 | 2009-09-08 13:58:11 | 2022-03-06 03:50:53.843237 | Unreviewed | closed | Forms | 1.1-beta | invalid | field check does not wok | I am having a class which is defined as {{{ #!python class ABC(models.Model): id = models.CharField(max_length=100, primary_key=True) pub = models.ForeignKey(WapUser, null=True) brief_description = models.TextField(null=True,blank=True) status = models.CharField(max_length=12, null=True, help_text='Select the appropriate status and click on save', choices=SITE_STATUS_CHOICES ) created_on = models.DateTimeField(null=True) pub_share = models.DecimalField('site_rev_share',max_digits=4,decimal_places=2,null=True) require_full_size_banner = models.IntegerField("Full Size Banner Ads", choices=BOOLEAN_CHOICES, default = 0,null=True) modified_on = models.DateTimeField(auto_now=True,auto_now_add=True,verbose_name ='Last_modified_on') critical_nfr = models.DecimalField(max_digits=5,decimal_places=3,default='60',help_text='Plesae Enter in the range of (0-100)') class Meta: db_table = u'wap_abc' verbose_name_plural= "ABC" managed = False def __unicode__(self): return self.status def get_absolute_url(self): return "/abc/%i/" % self.id }}} And form.py looks like {{{ #!python class SiteForm(ModelForm): class Meta: model = ABC reason_for_reject = CharField(widget=forms.Textarea,max_length=500,help_text='Please enter if the reason is not in the list',required=False) def clean(self): cleaned_data = self.cleaned_data newStatus = self.cleaned_data.get('status') id_a = self.cleaned_data.get('id') critical_nfr = self.cleaned_data.get('critical_nfr') if new_pub_share == 0 or new_pub_share >=100: raise forms.ValidationError('You cannot set pub_share either equal to 0% or greater than equal to 100% !') if critical_nfr <0 and critical_nfr is not None: raise forms.ValidationError('You cannot set critical_nfr less than Zero !') if self.instance and self.instance.status=='pending': if newStatus =='activated' or newStatus == 'rejected': if newStatus == 'rejected': if rejection_code is None and new_reject… | nobody | ankit | 0 | 0 | 0 | 0 | 0 | 0 | |||
12316 | 2009-12-05 01:30:57 | 2009-12-09 19:15:11 | 2022-03-06 03:52:11.506168 | Unreviewed | closed | Uncategorized | 1.1-beta | invalid | GenericForeignKey produces an error when submitting from a form | I apologize for not making a better report, but I cannot afford the time right now to write the minimum amount of code to reproduce this. Snippet from my models.py: {{{ class Subscription(models.Model): user = models.OneToOneField(User, primary_key=True) promotion = models.ForeignKey(Promotion) start_date = models.DateTimeField(auto_now_add=True) # Foreign key to AuthorizeNetSubscription u other model payment_gateway_subscription = generic.GenericForeignKey() is_active = models.BooleanField(default=True) class AuthorizeNetSubscription(models.Model): subscription_id = models.CharField('subscriptionId in the ARB API call return', max_length=16, primary_key=True) }}} Snippet from my forms.py: {{{ authorize_net_subscription = AuthorizeNetSubscription( subscription_id=result_dict.subscription_id.text_) user = User.objects.create_user( username = form_list[1].cleaned_data['display_name'], email=email, password=password, ) subscription = Subscription( user=user, promotion=promotion, start_date=start_date, payment_gateway_subscription=authorize_net_subscription ) }}} It fails in the line that creates the Subscription instance with a TypeError exception "'object_id' is an invalid keyword argument for this function" coming from line 320 in django/db/models/base.py | nobody | djansoft | 0 | 0 | 0 | 0 | 0 | 0 | |||
12549 | 2010-01-08 16:11:35 | 2010-01-08 17:04:31 | 2022-03-06 03:52:51.697527 | Unreviewed | closed | Core (Other) | 1.1-beta | invalid | Native list method sort() does not work on ValuesListQuerySet instance returned from value_list() QuerySet | '''The following code causes an exception:''' {{{ members = Member.objects.all().values_list('name',flat=True) members.sort(key=len,reverse=True) # Sorts members so that longer strings are first }}} '''The exception is:''' {{{ Traceback (most recent call last): File "members_update.py", line 1179, in <module> uploadMembers(trace,mems.members,configuration=conf) File "/usr/lib/python2.5/site-packages/django/db/transaction.py", line 265, in _commit_manually return func(*args, **kw) File "members_update.py", line 186, in uploadProducts members.sort(key=len,reverse=True) # Sorts members so that longer strings are first AttributeError: 'ValuesListQuerySet' object has no attribute 'sort' }}} As far as the documentation goes, value_list() QuerySet was supposed to return a List object, not a ValuesListQuerySet. The documentation specifically states that value_list does is one of the functions not returning a QuerySet. Even if there's some kind of need to to return a List object, at least you would expect it to behave like a List object and support its methods - such as sort() | nobody | jonathan_livni | 0 | 0 | 0 | 0 | 0 | 0 | |||
12615 | 2010-01-15 00:13:00 | 2010-01-15 20:16:22 | 2022-03-06 03:53:01.389626 | Unreviewed | closed | Uncategorized | 1.1-beta | invalid | Broken queryset indexing with postgresql_psycopg2 with custom through model | If you start a new project and setup a database using postgresl_psycopg2 (I know sqlite3 works. I dunno about others), and create a model that uses a custom through model, queryset indexing will be broken when accessed through that relationship. I've attached a simplified models.py and tests.py to explain and demonstrate it. | nobody | yxven | 0 | 0 | 0 | 0 | 0 | 0 | |||
11029 | 2009-05-07 12:36:58 | 2014-02-08 20:48:22 | 2022-03-06 03:48:55.411776 | Someday/Maybe | closed | Testing framework | New feature | Normal | 1.1-beta | needsinfo | Model mocking support | Writing unit tests is hard mainly because of how tight are Models coupled to database. Being able to mock Models in a way that one could run tests entirely in memory (giving far better performance then even in-memory sqlite as one must not handle rollbacks and stuff) would be really helpful. Main problem to solve are foreign keys and contenttype framework handling. Solution could probably be some kind of mocking backend that do not support any database operations except for creation (and providing ID from in-memory generator) and primary-key retrieval (from stored dictionary). | nobody | Almad | 0 | 0 | 0 | 0 | 0 | 0 | |
458 | 2005-09-04 07:20:40 | 2011-09-28 16:12:21 | 2022-03-06 03:20:46.231336 | Unreviewed | closed | contrib.admin | defect | normal | 1.1-beta | wontfix | "View on site" doesn't link to model's get_absoulte_url() method | "View on site" button doesn't link to model's get_absolute_url() method, but shows something like '/r/12/1/'. It could be observed on the generic Users model. | adrian | igor@jahber.org | 0 | 0 | 0 | 0 | 0 | 0 | |
10703 | 2009-04-02 18:33:24 | 2011-09-28 16:12:21 | 2022-03-06 03:47:59.343189 | Unreviewed | closed | Core (Other) | 1.1-beta | wontfix | Helper for importing modules from installed apps | It would be really convenient to create extensible and reusable apps, if there was a simple way to import dynamically from an installed app (without defining the full path). For example, there could be the following function defined somewhere in django.utils or django.db.models: {{{ from django.db import models from django.utils import importlib def import_installed(path): """ Imports a module from an installed app >>> import_installed("myapp.forms") <module 'myproject.apps.myapp.forms'> """ app_name, module = path.split(".", 1) app = models.get_app(app_name) return importlib.import_module(app.__name__[:-6] + module) }}} | nobody | Archatas | reusable utility extensible import dynamic | 0 | 0 | 0 | 0 | 0 | 0 | ||
11016 | 2009-05-06 06:21:18 | 2011-09-28 16:12:21 | 2022-03-06 03:48:53.667169 | Unreviewed | closed | Core (Management commands) | 1.1-beta | wontfix | manage.py not finding custom commands when run from different directory (or through a symlink in a different directory) | [http://code.djangoproject.com/ticket/5825] Similar to the above case, but manage.py will not find custom commands if called through a symlink from a different directory or from a different directory other than the project directory. | nobody | icyhandofcrap | 0 | 1 | 0 | 1 | 0 | 0 | |||
11018 | 2009-05-06 06:35:47 | 2015-10-02 21:53:01 | 2022-03-06 03:48:53.935985 | Accepted | closed | contrib.contenttypes | New feature | Normal | 1.1-beta | wontfix | Generic foreign keys in custom m2m relationship model | In version 1.0.2 and older we can use custom table for ManyToManyField with parameter through = MyRelationModel. MyRelationModel should include foreign keys. I want to use generic foreign key as one foreign keys: {{{ class SomeModel(models.Model): marks = models.ManyToManyField(to=Mark, through=MarkedItem) class MarkedItem(models.Model): mark = models.ForeignKey(Mark) content_type = models.ForeignKey(ContentType) object_id = models.PositiveIntegerField() content_object = generic.GenericForeignKey('content_type', 'object_id') }}} Example: content object as one of foreign keys. But this code is't work. | nobody | Alexandr | 0 | 0 | 0 | 0 | 0 | 0 | |
11449 | 2009-07-09 20:33:33 | 2012-06-28 20:55:03 | 2022-03-06 03:49:57.174692 | Accepted | closed | Core (Serialization) | Cleanup/optimization | Normal | 1.1-beta | wontfix | Performance regression loading from fixtures in 1.1 & trunk | I have created a test that does nothing but read in a fixture. It goes significantly slower on Django 1.1-beta and trunk than it does in Django 1.0. 1.0: Ran 1 test in 4.940s 1.1: Ran 1 test in 21.541s trunk: Ran 1 test in 21.228s My rejected patch in #11181 reduces cuts each of these times in half -- but does not fix the regression. | nobody | novalis | perf | 0 | 0 | 0 | 0 | 0 | 0 |
13817 | 2010-06-23 10:25:30 | 2010-12-29 02:16:01 | 2022-03-06 03:56:13.146220 | Unreviewed | closed | Database layer (models, ORM) | 1.1-beta | wontfix | Error message when cache.set has trouble. | I am using low-level cache in my app, there were some cases when the `cache.set` method reported the `TransactionManagementError: This code isn't under transaction management` error, because (I guessed) that there is some underlying DB execution error. I managed to find out what that original error was (with PDB) (and solve the problem): `OperationalError: (1153, "Got a packet bigger than 'max_allowed_packet' bytes")` Now, is there a way to retrieve the original error from code? Is there a way to tell Django not to try to rollback that unsuccessful query? Is it a bug (i.e. Django shouldn't try to rollback code that is not under transaction management)? Is it a version specific problem? django.VERSION is: `(1, 1, 1, 'final', 0)` django.get_version() says: 1.1.1 SVN-865 Thank you for your time. | nobody | ezimir | 0 | 0 | 0 | 0 | 0 | 0 | |||
8412 | 2008-08-19 10:12:19 | 2009-07-28 08:07:04 | 2022-03-06 03:42:11.780251 | Accepted | closed | Core (Serialization) | 1.1-beta | worksforme | When there is a DateTimeField in, data saved with dumpdata cannot be reloaded using loaddata (on German Systems) | To recreate: 1. Setup Django on a Windows XP system with the Time Format set to German (19/8/2008) 2. Save the data using manage.py dumpdata > initial_data.json<br> 3. Reload the data using manage.py loaddata initial_data.json<br> The message appears: {{{ Problem installing fixture 'initial_data.json': Traceback (most recent call last ): File "C:\Program Files\Python\Lib\site-packages\django\core\management\command s\loaddata.py", line 108, in handle for obj in objects: File "C:\Program Files\Python\Lib\site-packages\django\core\serializers\json.p y", line 42, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File "C:\Program Files\Python\Lib\site-packages\django\core\serializers\python .py", line 93, in Deserializer data[field.name] = field.to_python(field_value) File "C:\Program Files\Python\Lib\site-packages\django\db\models\fields\__init __.py", line 631, in to_python raise validators.ValidationError, _('Enter a valid date/time in YYYY-MM-DD H H:MM format.') ValidationError: [u'Enter a valid date/time in YYYY-MM-DD HH:MM format.'] }}} | nobody | Mark Essien <markessien@gmail.com> | loaddata dumpdata DateTimeField | 0 | 0 | 0 | 0 | 0 | 0 | ||
11620 | 2009-08-01 22:27:29 | 2009-08-01 23:37:50 | 2022-03-06 03:50:22.705767 | Unreviewed | closed | Documentation | 1.1-beta | worksforme | Tutorial part II, page 1, gives error message when followed. | Admin screen will not run when tutorial is followed. I hacked around and found that making a change in '''settings.py''' will correct the error. I uncommented the line '''django.template.loaders.eggs.load_template_source''' and that found the correct template and admin ran. EGGS? must be inside joke. | nobody | thegreygeek | tutorial part II, admin | 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 );