django_tickets: tickets: 24 rows where "created" is on date 2011-09-09 sorted by changetime

24 rows where "created" is on date 2011-09-09 sorted by changetime

descending

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_docs
16775	2011-09-09 01:39:17	2011-09-09 01:49:14	2022-03-06 04:04:06.312959	Unreviewed	closed	Database layer (models, ORM)	New feature	Normal	1.3	duplicate	Support for simple arithmetic in ORM annotations	I would like to use the Django ORM to run a query such as the following: SELECT SUM(amount * quantity) FROM orders; Right now, I'm not sure this is possible. As for a potential API, I might suggest something like this: Order.objects.annotate(sum=Sum(F("amount") * F("quantity"))) Thoughts? Suggestions?	nobody	dloewenherz		0	0	0	0
16771	2011-09-09 00:44:17	2011-09-09 07:23:13	2022-03-06 04:04:05.691531	Unreviewed	closed	*.djangoproject.com	Bug	Normal	1.3	fixed	https://code.djangoproject.com old link to subversion	https://code.djangoproject.com links to subversion.tigris.org. Subversion moved to apache and is now at http://subversion.apache.org.	nobody	poirier		0	0	0	0
16772	2011-09-09 00:46:33	2011-09-09 17:16:45	2022-03-06 04:04:05.848174	Unreviewed	closed	*.djangoproject.com	Bug	Normal	1.3	fixed	https://code.djangoproject.com Getting Involved points to 1.3 goals	On https://code.djangoproject.com the Getting Involved section's first bullet is "Help with 1.3 goals" and links to https://code.djangoproject.com/wiki/Version1.3Roadmap. 1.3 has been released so this is out of date.	nobody	poirier		0	0	0	0
16780	2011-09-09 17:48:55	2011-09-09 17:54:04	2022-03-06 04:04:07.126649	Accepted	closed	Template system	Cleanup/optimization	Normal	1.3	fixed	Timing sensitivity in templates regression tests	The templates regression tests uses a TestObj that has a sleep embedded in it; the tests for template loading and rendering then perform a timing check to ensure that the "bad" code doesn't run. However, this is fragile; system conditions on the test box can cause the test to fail. E.g., if the disk is thrashing, a template will take longer to load.	nobody	russellm		0	0	0	0
16783	2011-09-09 18:48:35	2011-09-09 19:02:52	2022-03-06 04:04:07.581714	Unreviewed	closed	Core (Management commands)	New feature	Normal	1.3	wontfix	Don't validate models on runfcgi	runfcgi now requires model validation. However in production validation does more harm than it helps. It prevents site from starting up at all and showing any useful information (a pretty 500.html or partially working site). Besides, production is not the best place to debug validation errors anyway. I think simply dropping model validation on runfcgi is a good solution.	isagalaev	isagalaev		0	0	0	0
16784	2011-09-09 19:16:15	2011-09-09 19:51:19	2022-03-06 04:04:07.737805	Unreviewed	closed	Forms	Bug	Normal	dev	invalid	FormWizardWithNullBooleanField regression test failing	While running the regression tests with the default sqlite test, I get this error which is not on the ci server (http://ci.django-cms.org/job/Django/223/#showFailuresLink): {{{ ====================================================================== ERROR: testWizard (regressiontests.formwizard.tests.FormWizardWithNullBooleanField) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/adam/Development/yipit-env/src/django/tests/regressiontests/formwizard/tests.py", line 57, in testWizard File "/Users/adam/Development/yipit-env/src/django/django/test/client.py", line 439, in get response = super(Client, self).get(path, data=data, extra) File "/Users/adam/Development/yipit-env/src/django/django/test/client.py", line 241, in get return self.request(r) File "/Users/adam/Development/yipit-env/src/django/django/core/handlers/base.py", line 111, in get_response response = callback(request, callback_args, callback_kwargs) File "/Users/adam/Development/yipit-env/src/django/django/utils/decorators.py", line 25, in _wrapper return bound_func(args, *kwargs) File "/Users/adam/Development/yipit-env/src/django/django/utils/decorators.py", line 91, in _wrapped_view response = view_func(request, args, *kwargs) File "/Users/adam/Development/yipit-env/src/django/django/utils/decorators.py", line 21, in bound_func return func(self, args2, **kwargs2) File "/Users/adam/Development/yipit-env/src/django/django/contrib/formtools/wizard/legacy.py", line 127, in __call__ return self.render(form, request, current_step) File "/Users/adam/Development/yipit-env/src/django/django/contrib/formtools/wizard/legacy.py", line 141, in render return self.render_template(request, form, ''.join(prev_fields), step, context) File "/Users/adam/Development/yipit-env/src/django/django/contrib/formtools/wizard/legacy.py", line 243, in render_template ), context_instance=RequestContext(request)) File "/…	nobody	adamnelson		0	0	0	0
16791	2011-09-09 21:23:42	2011-09-09 21:43:12	2022-03-06 04:04:08.800330	Unreviewed	closed	Documentation	Uncategorized	Normal	1.3	fixed	URL reference to docs on how to run tests in README is out of date	This is similar to bug #16343 which fixed the reference to the text file in the source tree, but I also noticed the URL also needed updating.	nobody	paulcwatts		0	1	0	0
16794	2011-09-09 23:07:08	2011-09-10 17:52:02	2022-03-06 04:04:09.266785	Unreviewed	closed	Uncategorized	Uncategorized	Normal	1.3	worksforme	Attachment Upload Test	Testing attachment uploads for https://github.com/tswicegood/detracify Feel free to close ticket whenever	nobody	pizzapanther		0	0	0	0
16788	2011-09-09 20:31:07	2011-09-13 18:57:56	2022-03-06 04:04:08.361101	Accepted	closed	Core (Other)	Cleanup/optimization	Normal	1.3	duplicate	remove import * from urls.py	Let's face it: import * is ugly and breaks guidelines on what is good practice in Python code. (And pylint complains about it. :) ) Let's send them into oblivion! import patterns or import patterns, urls will do in most cases :) contrib/admindocs/urls.py:from django.conf.urls.defaults import * contrib/auth/urls.py:from django.conf.urls.defaults import * contrib/comments/urls.py:from django.conf.urls.defaults import * contrib/databrowse/urls.py:from django.conf.urls.defaults import * contrib/flatpages/urls.py:from django.conf.urls.defaults import * contrib/staticfiles/urls.py:from django.conf import settings contrib/staticfiles/urls.py:from django.conf.urls.static import static contrib/auth/tests/urls.py:from django.conf.urls.defaults import patterns, url contrib/flatpages/tests/urls.py:from django.conf.urls.defaults import * contrib/formtools/tests/urls.py:from django.conf.urls.defaults import * contrib/messages/tests/urls.py:from django.conf.urls.defaults import * contrib/sitemaps/tests/urls.py:from django.conf.urls.defaults import *	draix	wim@go2people.nl		1	1	0	0
16773	2011-09-09 00:48:35	2011-09-14 04:57:22	2022-03-06 04:04:06.016579	Design decision needed	closed	Database layer (models, ORM)	Bug	Normal	1.3	wontfix	QuerySet.count does no caching until the result cache is filled	Before a queryset is evaluated, each QuerySet.count call for a given QuerySet hits the database with a `COUNT()` query, and doesn't cache the result in any way. {{{ In [1]: from django.contrib.auth.models import User In [2]: from django.db import connections In [3]: qs = User.objects.all() In [4]: qs.count() Out[4]: 3 In [5]: qs.count() Out[5]: 3 In [6]: list(qs); In [7]: qs.count() Out[7]: 3 In [8]: connections['default'].queries Out[8]: [{'sql': 'SELECT COUNT() FROM "auth_user"', 'time': '0.005'}, {'sql': 'SELECT COUNT(*) FROM "auth_user"', 'time': '0.001'}, {'sql': 'SELECT "auth_user"."id", "auth_user"."username", "auth_user"."first_name", "auth_user"."last_name", "auth_user"."email", "auth_user"."password", "auth_user"."is_staff", "auth_user"."is_active", "auth_user"."is_superuser", "auth_user"."last_login", "auth_user"."date_joined" FROM "auth_user"', 'time': '0.001'}] }}}	nobody	eternicode		0	0	0	0
16792	2011-09-09 21:38:23	2011-09-25 06:29:15	2022-03-06 04:04:08.951570	Unreviewed	closed	Uncategorized	Cleanup/optimization	Normal	1.3	invalid	DO NOT TRIAGE: This is a test ticket for Detracify	Please do not triage, this ticket is for testing github pull request -> trac processing.	nobody	robopony		0	0	0	0
16782	2011-09-09 18:44:39	2011-10-09 13:42:11	2022-03-06 04:04:07.430285	Unreviewed	closed	Documentation	Bug	Normal	1.3	fixed	Link to other database backends in the tutorial is no longer functional (as of 1.3)	In the "Database setup" section of the docs, there's a link to other database backends. Since this configuration changed in Django 1.3, the location that this should point to in the docs changed as well. https://docs.djangoproject.com/en/dev/intro/tutorial01/#database-setup	cmheisel	mjumbewu@gmail.com		0	1	0	0
16786	2011-09-09 20:17:21	2011-10-09 13:42:11	2022-03-06 04:04:08.033244	Unreviewed	closed	Documentation	Uncategorized	Normal	1.3	fixed	Document cleanup in `topics/cache`	The section on Memcached in topics/cache has an inconsistent reference to their website. Also, there's a typo ("moderns browsers"). Patch attached!	nobody	jamesp		0	1	0	0
16789	2011-09-09 20:35:15	2011-10-09 13:42:11	2022-03-06 04:04:08.503753	Ready for checkin	closed	contrib.auth	Cleanup/optimization	Normal	1.3	fixed	use named urls in django.contrib.auth.urls	Use named urls in django.contrib.auth: eat own dogfood and make it possible to use reverse auth urls for everyone! Freedom to the people!	fcurella	wim@go2people.nl		1	1	0	0
16790	2011-09-09 21:08:27	2011-10-09 13:42:11	2022-03-06 04:04:08.644821	Accepted	closed	GIS	Bug	Normal	dev	fixed	GeoDjango tutorial error (selecting WorldBorders via admin crashes)	First time django contributor; I may be doing something wrong, but here it goes... Note that the crash does not occur with the 1.3.0 release (I'm running trunk, 1.4.0 alpha). Got to the following point in the tutorial: "Finally, browse to http://localhost:8000/admin/, and log in with the admin user created after running syncdb. Browse to any of the WorldBorders entries" Clicking on "WorldBorders" causes the crash: "'super' object has no attribute '_media'" The following seems to be the problem: the first thing that django.contrib.gis.admin.options.GeoModelAdmin._media() does is to invoke... {{{ media = super(GeoModelAdmin, self)._media() }}} The problem is that there was a recent changeset (16594) in the parent class (ModelAdmin). In that changeset the following changed: old: {{{ def _media(self): }}} new: {{{ @property def media(self): }}} I tested a patch (which I'll submit shortly) where GeoModelAdmin gets "media" from its parent as a property, instead of getting it via a method call. This seems to fix the problem. {{{ media = super(GeoModelAdmin, self).media }}} Note that I ran the GeoDjangoTestSuiteRunner tests and although there were some errors, none of them seem to correspond to this case; however, I'm not positive about this.	jdiego	jdiego	GIS GeoDjango tutorial	0	0	0	0
16793	2011-09-09 23:07:06	2011-10-09 13:42:11	2022-03-06 04:04:09.111712	Accepted	closed	Documentation	Cleanup/optimization	Normal	1.3	fixed	consolidate and/or cross reference documentation on {% load %} template tag	The {{{ {% load %} }}} template tag is documented in at least 3 places, and 2 of them do not mention the {{{ {% load foo from bar %} }}} syntax that was introduced in 1.3. This documentation can probably be consolidated (and/or spruced up with cross links) to make the {{{from}}} syntax easier to find. The 3 locations are: https://docs.djangoproject.com/en/dev/topics/templates/#custom-tag-and-filter-libraries https://docs.djangoproject.com/en/dev/howto/custom-template-tags/#code-layout https://docs.djangoproject.com/en/dev/ref/templates/builtins/#load	bluejeansummer	tobias		1	1	0	0
16776	2011-09-09 09:04:17	2011-10-13 09:20:11	2022-03-06 04:04:06.467798	Accepted	closed	contrib.admin	Bug	Normal	dev	fixed	jQuery.noConflict(false) in jquery.init.js leaks the admin jQuery into the global namespace	{{{jQuery.noConflict(true)}}} should be used instead. Now that django's jQuery object is namespaced to django.jQuery (#12882), it doesn't need to appear anywhere else in the global namespace. Most jQuery plugins overload the jQuery object (documented here: http://docs.jquery.com/Plugins/Authoring ), and putting the admin's object here makes it harder to use a newer version. django apps like django-selectable, which requires a recent jQuery and jQuery UI, are affected. [16415] should be reverted.	julien	anonymous	jQuery admin	0	1	0	0
16787	2011-09-09 20:30:35	2011-11-21 10:28:12	2022-03-06 04:04:08.193769	Ready for checkin	closed	Template system	Bug	Release blocker	1.3	fixed	{% load %} doesn't work with libraries in package heierarcy	In other words {% load package.lib %} doesn't work. The docstring of load tag suggests it should work and it used to work before changeset r12944. We should allow this behavior again and document it properly in docs.	isagalaev	isagalaev		0	1	0	0
16777	2011-09-09 10:09:25	2012-06-06 09:14:45	2022-03-06 04:04:06.642945	Accepted	closed	Documentation	Cleanup/optimization	Normal	dev	invalid	Contributing guide: github and bitbucket pull requests are acceptable	See Russell's comment here: https://code.djangoproject.com/ticket/16774#comment:2 I'm pretty sure this isn't written in the current documentation.	justinlilly	aaugustin		1	1	1	0
16779	2011-09-09 17:28:10	2012-11-17 19:12:36	2022-03-06 04:04:06.975121	Accepted	closed	Documentation	New feature	Normal		fixed	Add a tutorial for first time Django contributors	There's been some discussion about adding a tutorial for first time Django contributors who may not be familiar with the processes and tools involved in submitting patches to Django. I've written a rough draft of a tutorial for this. You can view a rendered copy of the RST at http://www.taijala.com/tutorial.html Some of the links may not work though, since I only uploaded the tutorial document.	taavi223	taavi223		0	1	0	0
16778	2011-09-09 11:49:25	2013-01-11 09:07:07	2022-03-06 04:04:06.814897	Ready for checkin	closed	GIS	Bug	Normal	1.3	fixed	Bad geometry escape in postgis	Geometries for postgis are adapted using an escaping style only working with postgresql setting for standard_conforming_string = off. On is the default for PostgreSQL 9.1 The attached patch fixes the problem and works for any PG version and any SCS setting. Also see http://psycopg.lighthouseapp.com/projects/62710/tickets/69	nobody	piro		1	1	0	0
16781	2011-09-09 18:36:24	2013-11-02 20:58:56	2022-03-06 04:04:07.269143	Accepted	closed	Database layer (models, ORM)	Bug	Normal	1.3	fixed	Wrong SQL for a query-set	I'm using Django 1.3 and the postgres (postgresql_psycopg2) backend. A query set is producing the wrong (invalid) SQL. Query that breaks the SQL: `Address.objects.exclude(user__relationships_from__from_user__id=100)` Resulting in: {{{ #!div style="font-size: 80%" Code highlighting: {{{#!sql SELECT "bug3_address"."id", "bug3_address"."user_id", "bug3_address"."address" FROM "bug3_address" WHERE NOT ("bug3_address"."user_id" IN (SELECT U2."from_user_id" FROM "entities_user" U1 WHERE (U0."user_id" = 100 AND U2."from_user_id" IS NOT NULL))) }}} }}} However, this works fine: `Address.objects.exclude(user__relationships_to__from_user__id=100)` Resulting in: {{{ #!div style="font-size: 80%" Code highlighting: {{{#!sql SELECT "bug3_address"."id", "bug3_address"."user_id", "bug3_address"."address" FROM "bug3_address" WHERE NOT (("bug3_address"."user_id" IN (SELECT U2."to_user_id" FROM "bug3_relationship" U2 WHERE (U2."from_user_id" = 100 AND U2."to_user_id" IS NOT NULL)) AND "bug3_address"."user_id" IS NOT NULL)) }}} }}} Also accessing other attributes works fine: `Address.objects.exclude(user__relationships_from__status='A')` Resulting in: {{{ #!div style="font-size: 80%" Code highlighting: {{{#!sql SELECT "bug3_address"."id", "bug3_address"."user_id", "bug3_address"."address" FROM "bug3_address" WHERE NOT (("bug3_address"."user_id" IN (SELECT U2."from_user_id" FROM "bug3_relationship" U2 WHERE (U2."status" = A AND U2."from_user_id" IS NOT NULL)) AND "bug3_address"."user_id" IS NOT NULL)) }}} }}} These are the models: {{{ #!div style="font-size: 80%" Code highlighting: {{{#!python from django.db import models from django.contrib.auth.models import User class Address(models.Model): user = models.ForeignKey(User) address = models.CharField(max_length=100) class Relationship(models.Model): status = models.CharField(max_length=1) from_user = models.ForeignKey(User, related_name='relationships_from') to_user = models.ForeignKey(…	nobody	Kronuz		0	0	0	0
16785	2011-09-09 20:14:03	2014-01-17 02:14:44	2022-03-06 04:04:07.883821	Accepted	closed	Documentation	New feature	Normal	1.3	fixed	Document cache design in `misc/design-philosophies`	I initially found the design of the cache backend classes confusing, especially with respect to references to Memcached in {{{django.core.cache.backends.base.BaseCache.validate_key()}}} . I found that this was added a year ago in ticket #6447, so I figured there was a good reason but it was not explained anywhere I could find. I discussed this with a couple core developers and hopefully the attached patch will be suitable.	timo	jamesp		0	1	1	0
16774	2011-09-09 01:05:25	2021-05-07 17:47:43	2022-03-06 04:04:06.159441	Accepted	new	Core (URLs)	New feature	Normal	dev		Backtracking URL resolver	Right now the URL resolver only resolves to the first matched URL, and the view that is resolved to is unable to inspect the requested URL to see if it truly should be the view to be handling this URL. You can only have one "catch all" url pattern, however, occasionally it would make sense to allow distinct applications to receive a URL and upon inspection claim it, or allow the URL resolver to continue to find a match (i.e. CMS, legacy database driven system to handle legacy urls, etc.) https://github.com/django/django/pull/37 Thoughts? If this is a desired feature, then I would be happy to write the docs or further this concept. Thanks! Nowell Strite		nbstrite		0	1	1	1

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
    );