django_tickets

This data as json, CSV

id	created	changetime	last_pulled_from_trac	stage	status	component	type	severity	version	resolution	summary	description	owner	reporter	keywords	has_patch
57	2005-07-18 08:54:22	2006-08-29 10:24:58	2022-03-06 03:19:35.722229	Unreviewed	closed	Documentation	defect	normal		fixed	Add to Apache configuration for tutorial (part 2)	Possibly include PythonDebug On in the sample config, gives at least an error message you can work with instead of the rather non-descript 500 Internal Server Error. Also, at least in my case the PYTHONPATH I exported on the commandline didn't carry over to the one mod_python was using. In this case, PythonPath "['/var/www/django/http'] + sys.path" solved my problem.	jacob	Manuzhai <mail@manuzhai.nl>		0
60	2005-07-18 16:14:09	2006-10-08 00:18:02	2022-03-06 03:19:36.271218	Unreviewed	closed	Core (Other)	defect	normal		invalid	Built in webserver	Are you aware that they CherryPy team has implemented a python standalone wsgi server that they use for development? Perhaps that could be adapted, instead of having to reinvint the wheel? I apologize for putting this in a bug report, I couldn't find another way of contact on the website.	adrian	anonymous		0
62	2005-07-18 16:34:40	2006-10-22 15:54:23	2022-03-06 03:19:36.628513	Unreviewed	closed	Documentation	enhancement	normal		fixed	Change tutorial to use easy development server, not mod_python		adrian	adrian		0
52	2005-07-18 00:39:10	2006-10-22 16:22:27	2022-03-06 03:19:35.028090	Unreviewed	closed	Documentation	defect	normal		fixed	A couple of minor errors in the documentation on the site	On this page: http://www.djangoproject.com/documentation/model_api/ there are a couple of small errors. 1. It doesn't specify that maxlength must be set for a CommaSeparatedIntegerField. 2. That the FloatField requires max_digits=14 and decimal_places=4, it currently says those are optional. Thanks For all the hard work!	jacob	Dobbes		0
74	2005-07-18 21:05:56	2006-10-22 16:23:53	2022-03-06 03:19:38.590324	Unreviewed	closed	*.djangoproject.com	defect	normal		duplicate	add djangoproject.com templates into SVN	For transparency and instruction-by-example, it would be nice to have the templates for djangoproject.com in SVN. Then people can see how brilliant minds like mine hack the template system to do terrible things.	adrian	wilson		0
61	2005-07-18 16:17:34	2007-01-17 22:12:17	2022-03-06 03:19:36.456283	Unreviewed	closed	contrib.admin	enhancement	normal	dev	fixed	[patch] auth.User admin form shouldn't require people to edit hashes	People shouldn't have to enter MD5 hashes in the password field. World Online never used the user form to create users or edit passwords, but now there's a demand for a better form. We can solve it with JavaScript.	adrian	adrian		1
65	2005-07-18 16:53:09	2007-01-17 22:12:34	2022-03-06 03:19:37.141424	Unreviewed	closed	contrib.admin	enhancement	normal		fixed	[i18n] Internationalization and localisation	Ability to translate at least Admin UI into another language (using gettext?) and format date / time / numbers according to locale. I am willing to do Dutch, Russian and maybe Hebrew translation :)	hugo	ksenia@ksenia.nl		0
53	2005-07-18 02:22:50	2007-07-03 22:57:14	2022-03-06 03:19:35.179425	Ready for checkin	closed	Tools	defect	normal		fixed	djonga-admin.py sqlclear fails with entries in auth_permissions tables	Running the sql output from djonga-admin.py sqlclear blog BEGIN; DELETE from content_types WHERE package = 'blog'; DELETE FROM packages WHERE label = 'blog'; DROP TABLE blog_entries; COMMIT; Returns the following error: ERROR: update or delete on "packages" violates foreign key constraint "auth_permissions_package_fkey" on "auth_permissions" DETAIL: Key (label)=(blog) is still referenced from table "auth_permissions". This is pretty much what it says that there are still fields in the auth_permissions table that reference the blog package, so it can't be deleted. I created the simple patch for it and will attach.	adrian	Dobbes		0
54	2005-07-18 03:06:17	2007-07-03 23:01:12	2022-03-06 03:19:35.324390	Unreviewed	closed	Documentation	defect	normal		fixed	pattern in url_dispatch.txt maybe wrong	{{{ >>> import re >>> a = r'^/articles/(?P\d{4})/$' >>> re.compile( a ) Traceback (most recent call last): File "<input>", line 1, in ? File "C:\Python24\Lib\sre.py", line 180, in compile return _compile(pattern, flags) File "C:\Python24\Lib\sre.py", line 227, in _compile raise error, v # invalid expression error: unknown specifier: ?P\d >>> a = r'^/articles/(?P<year>\d{4})/$' >>> re.compile( a ) <_sre.SRE_Pattern object at 0x01093350> }}} Should we add the group name in patterns?	jacob	james		0
68	2005-07-18 17:32:08	2007-07-03 23:03:24	2022-03-06 03:19:37.636827	Ready for checkin	closed	Documentation	defect	minor		fixed	Tutorial 02 shows deprecated mod_python config	Per changeset:169, the mod_python config should specify django.core.handlers.modpython as handler. {{{ --- docs/tutorial02.txt Mon Jul 18 11:10:22 2005 +++ docs/tutorial02_update.txt Mon Jul 18 13:24:01 2005 @@ -65,7 +65,7 @@ <Location "/admin/"> SetHandler python-program - PythonHandler django.core.handler + PythonHandler django.core.handlers.modpython SetEnv DJANGO_SETTINGS_MODULE myproject.settings.admin PythonDebug On </Location> }}}	jacob	pb@e-scribe.com		0
77	2005-07-18 23:55:33	2007-07-03 23:03:24	2022-03-06 03:19:39.048107	Ready for checkin	closed	Database layer (models, ORM)	enhancement	minor		wontfix	The PostgreSQL code should use schemas instead of prefixes for namespaces.	Rather than append App_ before every table in PostgreSQL, you should use Schemas http://www.postgresql.org/docs/8.0/static/ddl-schemas.html. That's what they're there for, and it makes the database much more readable.	adrian	RahmCoff@Radio1190.org		0
59	2005-07-18 09:45:00	2007-07-03 23:03:34	2022-03-06 03:19:36.121419	Design decision needed	closed	contrib.admin	defect	normal		fixed	Hard-coded references to password_change and logout	Sorry for another ticket, but I really like what I've seen so far. :D If you'd rather I comment on the tutorial page itself, that's alright too, I'm just used to working with Trac myself. They don't actually point to the admin, just to the root of the web server. It would seem to me this is a problem with the template stuff, but it could be just a documentation problem that I have to change something else.	adrian	Manuzhai <mail@manuzhai.nl>		0
73	2005-07-18 21:05:45	2007-07-03 23:03:38	2022-03-06 03:19:38.438789	Accepted	closed	*.djangoproject.com	enhancement	normal		fixed	Sample templates in the repository?	I wonder if it would be possible to have the templates for this site also in the repository. This would be a useful starting point for beginning users, but maybe it's impossible due to copyright issues or some such. Also, the need for these things may disappear when the next tutorial appears - but still...	jacob	Manuzhai <mail@manuzhai.nl>		0
64	2005-07-18 16:37:56	2007-07-03 23:03:39	2022-03-06 03:19:36.990398	Accepted	closed	Core (Cache system)	enhancement	normal		fixed	Add cache middleware	It should be possible to say "Cache every page on this site." We'd use middleware for this.	adrian	adrian		0
55	2005-07-18 05:42:08	2007-07-03 23:03:50	2022-03-06 03:19:35.483780	Accepted	closed	Tools	defect	normal		wontfix	add a logger to django	insert the block into django.conf.settings file at line 32. {{{ #python a = me.SETTINGS_MODULE.split( '.' ) if 'settings' in a: idx = a.index( 'settings' ) if idx > 0: projname = a[idx-1] projmod = __import__( projname , '', '', ['']) else: projname = 'django' import django as projmod logdir = os.path.split( projmod.__file__ )[0] + os.sep + 'logs' if not os.access( logdir , os.W_OK ): raise 'Cannot write log file in dir: ' + logdir import logging logger = logging.getLogger( projname ) hdlr = logging.FileHandler( logdir + os.sep + projname + '.log' ) formatter = logging.Formatter('%(asctime)s %(levelname)s %(message)s') hdlr.setFormatter(formatter) logger.addHandler( hdlr ) logger.setLevel( logging.DEBUG ) __builtins__['log'] = logger log.info( 'project logger start' ) }}} make sure you have created 'logs' folder at your project or django src. then you can use log object anywhere. ATTENTION: NOT fully tested.	adrian	james	log	0
66	2005-07-18 16:57:22	2007-07-03 23:03:50	2022-03-06 03:19:37.305226	Design decision needed	closed	Core (Other)	defect	normal		wontfix	[patch] Give views access to application root from urlconf	When using include with urlpatterns, there should be a variable available to the views that will give us the root of the application. For instance, for: {{{ (r'^polls/', include('myproject.apps.polls.urls.polls')), }}} ...it would be "/polls/".	adrian	slashzero		1
58	2005-07-18 09:26:59	2007-07-03 23:03:52	2022-03-06 03:19:35.920339	Design decision needed	closed	Database layer (models, ORM)	defect	normal		invalid	Creating user from interactive interpreter doesn't work with MySQL	from django.models.auth import users doesn't seem to work with MySQL. I get the following error: {{{ Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/models/__init__.py", line 1, in ? from django.core import meta File "/usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/core/meta.py", line 2, in ? from django.core import db File "/usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/core/db/__init__.py", line 22, in ? raise ImproperlyConfigured, "Your DATABASE_ENGINE setting, %r, is invalid. Is it spelled correctly?" % DATABASE_ENGINE django.core.exceptions.ImproperlyConfigured: Your DATABASE_ENGINE setting, 'mysql', is invalid. Is it spelled correctly? }}} I tried checking out the source code to see what caused the error, but this is a little hard, as there is a circular import from db.__init__ and db.backends.mysql, so it seems I can't really see where the problem is coming from.	adrian	Manuzhai <mail@manuzhai.nl>		0
69	2005-07-18 18:12:19	2007-07-03 23:03:53	2022-03-06 03:19:37.795012	Unreviewed	closed	Database layer (models, ORM)	enhancement	normal		fixed	Enhancing the MySQL backend	I've implemented the dictfetch*() functions. May not be extremely fast, but at least the functionality is there. I'm not sure about the edge cases, though; we probably want the mysql and postgres backends to do the same thing when, for example, fetchmany() is called going over the result set bounds. Document this in the docstrings?	adrian	Manuzhai <mail@manuzhai.nl>		0
63	2005-07-18 16:36:21	2007-07-03 23:03:59	2022-03-06 03:19:36.810796	Ready for checkin	closed	Core (Other)	enhancement	normal		fixed	Factor django.core.handlers into subclasses to remove duplicate code		adrian	adrian		0
75	2005-07-18 21:17:26	2007-07-03 23:04:01	2022-03-06 03:19:38.754661	Accepted	closed	Metasystem	defect	normal		fixed	Add support for recursive ManyToManyFields	{{{ManyToManyField}}}s should be able to be related to {{{"self"}}}, as {{{ForeignKey}}}s can.	adrian	slashzero		0
76	2005-07-18 21:21:48	2007-07-03 23:04:02	2022-03-06 03:19:38.911572	Accepted	closed	Tools	defect	normal		fixed	Development server should serve admin images, too	The simple server started by {{{django-admin.py runserver}}} should serve admin images. It's a pain to have to set up Apache just to serve those.	adrian	adrian		0
67	2005-07-18 17:28:38	2007-07-03 23:04:03	2022-03-06 03:19:37.481269	Accepted	closed	Core (Other)	enhancement	normal		fixed	Make specifying 'human-readable' name optional.	I noticed that in the fields for the models in tutorial 1, three out of the four 'human-readable' names were identical to the 'machine-friendly' names. Following the DRY principle, I think that the specifying the 'human-readable' name should be optional, defaulting to the machine-friendly name. Here is a svn diff for a (trivial) implementation: {{{ Index: django/core/meta.py =================================================================== --- django/core/meta.py (revision 174) +++ django/core/meta.py (working copy) @@ -1564,13 +1564,13 @@ # database level. empty_strings_allowed = True - def __init__(self, name, verbose_name, primary_key=False, + def __init__(self, name, verbose_name=None, primary_key=False, maxlength=None, unique=False, blank=False, null=False, db_index=None, core=False, rel=None, default=NOT_PROVIDED, editable=True, prepopulate_from=None, unique_for_date=None, unique_for_month=None, unique_for_year=None, validator_list=None, choices=None, radio_admin=None, help_text=''): - self.name, self.verbose_name = name, verbose_name + self.name, self.verbose_name = name, verbose_name or name self.primary_key = primary_key self.maxlength, self.unique = maxlength, unique self.blank, self.null = blank, null }}}	adrian	mmarshall at myrealbox dot com		0
70	2005-07-18 19:48:49	2007-07-03 23:04:04	2022-03-06 03:19:37.946907	Ready for checkin	closed	*.djangoproject.com	defect	normal		fixed	Community link not there from within Code.	Probably should add it to the Trac templates. ;) How come, by the way, the addition of Community is not visible in the Timeline? The djangoproject.com website is also in SVN, right?	jacob	Manuzhai <mail@manuzhai.nl>		0
71	2005-07-18 20:26:25	2007-07-03 23:04:07	2022-03-06 03:19:38.102279	Ready for checkin	closed	Documentation	defect	minor		fixed	Consider using "example.com" instead of "mysite.com"	Kind of a [http://www.rfc-editor.org/rfc/rfc2606.txt fussy detail], but in the example files it might be better to use example.(com\|org\|net) instead of mysite.com, especially since the URL shows up as a live link at the top of the admin. Locations as of [181]: {{{ > grep -rn "mysite.com" * \| grep -v ".svn" django/bin/django-admin.py:283: cursor.execute("INSERT INTO %s (domain, name) VALUES ('mysite.com', 'My Django site')" % core.Site._meta.db_table) django/conf/admin_templates/base_site.html:7:<h2 id="site-url"><a href="http://www.mysite.com/">mysite.com</a></h2> docs/faq.txt:223: example, if you're going to "http://www.mysite.com/admin/" in your browser, docs/faq.txt:224: set ``REGISTRATION_COOKIE_DOMAIN = 'www.mysite.com'``. docs/tutorial02.txt:446:Clearly having "Django administration" and "mysite.com" at the top of each }}}	jacob	pb@e-scribe.com		0
72	2005-07-18 20:54:10	2012-11-23 02:29:52	2022-03-06 03:19:38.257291	Accepted	closed	Core (Other)	defect	normal		fixed	Django should add charset info to output HTTP headers	It seems Django doesn't add the "charset=utf8" field to "Content-type: text/html" header while sending headers to the browser. This cause pages encoded as UTF-8 look wrong in the browser (Firefox assumes page is encoded using iso-8859-1, which is the default HTTP encoding). Sample headers sent by Django: {{{ Date: Mon, 18 Jul 2005 20:51:43 GMT Server: Apache/2.0.54 (Win32) mod_python/3.1.4 Python/2.4.1 Connection: close Transfer-Encoding: chunked Content-Type: text/html 200 OK }}} Patching Content-type header to look like "Content-Type: text/html; charset=utf-8" would make clear which encoding is used by the server. [http://www.w3.org/International/O-HTTP-charset More info about charset param here.]	adrian	anonymous		0
56	2005-07-18 08:23:54	2021-04-07 08:10:50	2022-03-06 03:19:35.610334	Unreviewed	closed	Database layer (models, ORM)	New feature	Normal	dev	wontfix	Primary key columns should be UNSIGNED	This gets you twice the integer space, and seems to me to be a nice sanity check. Don't know if the same would go for Postgres. Not enough into the code right know to produce a patch myself.	caioariede	Manuzhai <mail@manuzhai.nl>	mysql	1

django_tickets

Custom SQL query returning 26 rows (show)

Query parameters