275 rows where "changetime" is on date 2007-07-03

View and edit SQL

Suggested facets: stage, component, type, severity, version, resolution, owner, has_patch, created (date), last_pulled_from_trac (date)

changetime (date)

  • 2007-07-03 · 275
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
2 2005-07-13 19:04:45 2007-07-03 23:04:18 2019-06-24 00:15:17.570436 Accepted closed contrib.admin defect normal   fixed Calendar popup - next/previous month links close the popup in Safari In Safari 2.0 on Tiger, the next/previous month links close the popup. There's no way to get to a different month. jacob anonymous   0 0 0 0 0 0
3 2005-07-13 19:06:09 2007-07-03 23:04:08 2019-06-24 00:15:18.232390 Design decision needed closed Metasystem enhancement normal   fixed Convert OneToOne to be like ForeignKey and ManyToManyField Remove the boilerplate from {{{OneToOne}}}. adrian adrian   0 0 0 0 0 0
7 2005-07-13 19:14:41 2007-07-03 23:04:26 2019-06-24 00:15:20.734813 Design decision needed closed contrib.admin defect minor   fixed Patch: Changelist date range filters don't maintain state as expected The changelist filter by a date doesn't behave as expected. '''What happens:''' When I click "This month", it correctly displays the objects for this month and drills down the date nav to the appropriate context, but the filter on the right does not indicate which range is currently applied. The "Any date" link does not reset the date drill down. '''What should happen:''' The date filter on the sidebar should update to show which range is currently applied. The "Any date" option should reset the date context. Alternatively, the filter "by date" options could be removed entirely to avoid conflict with the date drilldown. adrian wilson   0 0 0 0 0 0
8 2005-07-13 19:15:25 2007-07-03 23:03:55 2019-06-24 00:15:21.365914 Unreviewed closed contrib.admin defect minor   fixed Date and time fields should accept multiple formats Date and time fields should be able to adapt to multiple formats of user input (a la Simon's [http://simon.incutio.com/archive/2003/10/06/betterDateInput date parser]). As a basic example, a user should be able to enter "Today" or "Wednesday" for the date and have it converted to the correct format for today's date or this Wednesday's. For time fields, a user should be able to enter 6pm instead of 18:00. jacob adrian   0 0 0 0 0 0
11 2005-07-13 19:17:13 2007-07-03 23:03:30 2019-06-24 00:15:23.320721 Ready for checkin closed Metasystem defect minor   wontfix replaces_module should handle "admin" more intelligently Currently if you add or remove fields via the {{{replaces_module}}} framework, you have to redefine {{{admin}}} for the object. Ideally {{{admin}}} would be handled automatically. adrian adrian   0 0 0 0 0 0
12 2005-07-13 19:19:38 2007-07-03 23:03:44 2019-06-24 00:15:23.985673 Unreviewed closed Metasystem   normal   fixed Add metasystem database-check functionality We should automate the checking of whether everything is properly installed in the database for a particular app. For instance, a command such as {{{django-admin.py dbcheck news}}} would: * Check that the package exists in the DB. * Check that all the permissions exist in the DB. * Check that there aren't any *extra* permissions in the DB that the model doesn't know about. * Check that all the content types exist in the DB. * Check that there aren't any *extra* content types in the DB for this app. * Check that there aren't any missing fields. * Check that the fields are in the correct data type. adrian adrian   0 0 0 0 0 0
18 2005-07-13 19:26:27 2007-07-03 23:03:51 2019-06-24 00:15:27.878950 Unreviewed closed Database layer (models, ORM) enhancement normal   wontfix Metasystem optimization: Don't select duplicate fields In the following query, "poll_choices.poll_id" and "polls.id" are the same value. Only one of them needs to be selected: {{{ SELECT poll_choices.id,poll_choices.poll_id,poll_choices.choice, poll_choices.votes, polls.id,polls.slug,polls.question,polls.pub_date, polls.expire_date FROM poll_choices, polls WHERE poll_choices.poll_id = polls.id }}} adrian adrian   0 0 0 0 0 0
20 2005-07-13 19:32:17 2007-07-03 23:03:44 2019-06-24 00:15:29.178930 Ready for checkin closed contrib.admin enhancement normal   duplicate "Add another" for many-to-many relationships Django already creates an "Add another..." link in one-to-many select boxes. (Example: The "place" select box on the "Add event" admin page has an "Add another..." link at the bottom of it.) Many-to-many fields -- represented in the admin as multi-select boxes -- also need "Add another..." capability. It could probably appear as the last entry in the select box, as in the one-to-many add-anothers. adrian adrian   0 0 0 0 0 0
30 2005-07-13 22:12:36 2007-07-03 23:04:02 2019-06-24 00:15:35.824876 Design decision needed closed Tools defect normal 1.0 fixed django-admin shouldn't copy "." directories from the template. It's creating spurious ".svn" directories when used from svn; that's not so hot. adrian jacob   0 0 0 0 0 0
32 2005-07-15 14:35:30 2007-07-03 23:03:51 2019-06-24 00:15:37.031284 Unreviewed closed *.djangoproject.com defect normal   fixed Really dead link at http://www.djangoproject.com/documentation/faq/ http://www.djangoproject.com/documentation/admin_css/ at the bottom of http://www.djangoproject.com/documentation/faq/ dies with: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@djangoproject.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. jacob Martin   0 0 0 0 0 0
33 2005-07-16 02:37:35 2007-07-03 23:03:44 2019-06-24 00:15:37.668652 Design decision needed closed *.djangoproject.com defect normal   fixed frontpage typo Minor nitpick: there's a typo in the title attribute of the DIY acronym on the frontpage of http://www.djangoproject.com/ jacob anonymous typo 0 0 0 0 0 0
35 2005-07-16 12:15:35 2007-07-03 23:03:50 2019-06-24 00:15:38.979648 Unreviewed closed Database layer (models, ORM) defect blocker 1.0 invalid django-admin.py init problem for postgresql 8.0.3/win32 I try to pas step by step from http://www.djangoproject.com/documentation/tutorial1/ using PostgreSQL 8.0.3 (Winddows XP Pro SP2, Python 2.4.1, Apache 2.0.54, SVN version of django). I cannot initialize default django tables: C:\opt\Python24\Lib\site-packages\myproject>django-admin.py init Traceback (most recent call last): File "C:\opt\Python24\Scripts\django-admin.py", line 4, in ? pkg_resources.run_script('django==1.0.0', 'django-admin.py') File "C:\opt\Python24\Lib\site-packages\setuptools-0.5a12-py2.4.egg\pkg_resources.py", line 111, in run_script require(dist_spec)[0].metadata.run_script(script_name, ns) File "C:\opt\Python24\Lib\site-packages\setuptools-0.5a12-py2.4.egg\pkg_resources.py", line 634, in run_script execfile(script_filename, namespace, namespace) File "C:\opt\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\EGG-INFO\scripts\django-admin.py", line 399, in ? init() File "C:\opt\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\EGG-INFO\scripts\django-admin.py", line 275, in init from django.core import db, meta File "C:\opt\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\db\__init__.py", line 18, in ? dbmod = __import__('django.core.db.backends.%s' % DATABASE_ENGINE, '', '', ['']) File "C:\opt\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\db\backends\postgresql.py", line 65, in ? Database.register_type(Database.new_type((1082,), "DATE", typecasts.typecast_date)) !AttributeError: 'module' object has no attribute 'register_type' adrian JZ   0 0 0 0 0 0
37 2005-07-16 12:45:48 2007-07-03 23:03:23 2019-06-24 00:15:40.296975 Design decision needed closed Documentation defect normal   fixed Homepage link 'tutorial' is broken. The referred page is missing. Might be that it should refer to tutorial1 which exists. jacob sirpete@iki.fi   0 0 0 0 0 0
38 2005-07-16 18:15:54 2007-07-03 23:03:57 2019-06-24 00:15:40.948943 Unreviewed closed Database layer (models, ORM) enhancement normal   fixed Create sqlite backend An sqlite backend option would be useful for rapid-start development (ie. shortening the "unpack and try it" path. For an extreme case, look at roundup, and how you can download it, run one script from the source dir, and point a browser at it... django probably can't go *quite* that minimal, but with so many frameworks, having a quick way to "kick the tires" is very handy.) jacob eichin@thok.org   0 0 0 0 0 0
39 2005-07-16 21:08:21 2007-07-03 23:03:26 2019-06-24 00:15:41.644975 Design decision needed closed Database layer (models, ORM) defect major   fixed Get obj.save() working in all MySQL versions Some versions of MySQL tables (InnoDB?), with certain versions of MySQLdb, require that commit() be manually called. Others assume autocommit is turned on. We need to fix this. adrian adrian   0 0 0 0 0 0
41 2005-07-17 03:46:55 2007-07-03 23:03:22 2019-06-24 00:15:42.914849 Unreviewed closed Core (Other) enhancement normal   wontfix allow for multiple user identities with access rights to the database The current design assumes that only one user identity will be used for all database operations - from creating the database through inits and on to access from mod_python. This makes it very difficult to use ident auth (suitable for small, single host setups) and may be an issue even whent hat's not an issue. It's probably not too hard to remove this limitation. requires * a setup option to list other user ids to be allowed access * generate SQL GRANT statement(s) whenever a table is created (sequences too?!) And I think that's about it, at least for postgres. adrian maney@two14.net   0 0 0 0 0 0
43 2005-07-17 07:01:40 2007-07-03 23:03:29 2019-06-24 00:15:44.237358 Ready for checkin closed contrib.admin defect minor 1.0 fixed link to icon_searchbox.png is broken Now the icon is added, it's still got an extra "/admin" in it. adrian django@sabi.net   0 0 0 0 0 0
44 2005-07-17 13:01:43 2007-07-03 23:03:28 2019-06-24 00:15:44.866842 Ready for checkin closed Documentation defect normal   fixed Missing view templates for djangoproject.com in Subersion repos. I think it would be useful for documentation purposes to have templates files in SVN for the blog app which runs djangoproject.com, the folder /django_website/apps/blog/views is empty, while models and other stuff are curretly stored in the corresponding folders. jacob deelan   0 0 0 0 0 0
45 2005-07-17 15:41:33 2007-07-03 23:03:54 2019-06-24 00:15:45.528991 Design decision needed closed *.djangoproject.com defect normal   fixed Website should emphasize that MySQL support isn't thoroughly tested There seem to be lots of questions on the IRC channel about problems with MySQL - almost certainly bugs that exist because Django hasn't been comprehensively tested with that database. The website should emphasize the lack of stability in the MySQL bindings and encourage people to file bugs whenever they run in to a problem. jacob Simon Willison   0 0 0 0 0 0
47 2005-07-17 15:53:38 2007-07-03 23:03:42 2019-06-24 00:15:46.823438 Ready for checkin closed *.djangoproject.com defect normal   fixed Get rid of the Roadmap link in Trac It doesn't do anything, and unless it's going to be used it would be good to drop it from the template. (A Trac component for this kind of bug might be handy as well). jacob Simon Willison   0 0 0 0 0 0
49 2005-07-17 17:45:42 2007-07-03 23:03:32 2019-06-24 00:15:48.093157 Accepted closed contrib.admin defect normal   fixed Remove references to http://media.ljworld.com from the code Apparently http://media.ljworld.com is scattered through the code: {{{ simon:~/src/trunk$ grep -R "media.ljworld.com" * | grep -v ".svn" media/js/admin/add_calendars.js: quickElement('img', cal_link, '', 'src', 'http://media.ljworld.com/img/admin/icon_calendar.gif', 'alt', 'Calendar'); media/js/admin/DateTimeShortcuts.js: quickElement('img', clock_link, '', 'src', 'http://media.ljworld.com/img/admin/icon_clock.gif', 'alt', 'Clock'); media/js/admin/DateTimeShortcuts.js: quickElement('img', cal_link, '', 'src', 'http://media.ljworld.com/img/admin/icon_calendar.gif', 'alt', 'Calendar'); media/js/SelectFilter2.js: quickElement('img', filter_p, '', 'src', 'http://media.ljworld.com/img/admin/selector-search.gif'); media/js/SelectFilter2.js: quickElement('img', selector_filter, '', 'src', 'http://media.ljworld.com/img/admin/selector-add.gif', 'alt', 'Add'); }}} adrian Simon Willison   0 0 0 0 0 0
50 2005-07-17 21:05:22 2007-07-03 22:52:28 2019-06-24 00:15:48.733255 Ready for checkin closed Documentation defect minor   fixed Tutorial#1 section Initial Setup directory listing is missing settings/urls folder After django_admin.py startproject myproject is called new project now has a 'settings/urls' folder. Tutorial#1 section 'Initial Setup' has a directory listing of the new project. The listing is missing settings/urls folder. jacob sirpete@iki.fi django_admin startproject 0 0 0 0 0 0
51 2005-07-17 23:39:39 2007-07-03 22:54:15 2019-06-24 00:15:49.383683 Ready for checkin closed Metasystem enhancement normal 1.0 wontfix Create add_* methods for objects with a many-to many-relationship Objects with a many-to-one relationship have an add_object method for adding the type of object on the "many" end of the relationship to the list of values within the type of object on the "one" end of the relationship. Objects with a many-to-many relationship, however, are lacking these methods. For example: two objects, Set and Tag, have a many-to-many relationship. The Set object should have an add_tag method and the Tag method should have an add_set method. adrian jcernelli@gmail.com   0 0 0 0 0 0
53 2005-07-18 02:22:50 2007-07-03 22:57:14 2019-06-24 00:15:50.619800 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 0 0 0 0 0
54 2005-07-18 03:06:17 2007-07-03 23:01:12 2019-06-24 00:15:51.251649 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 0 0 0 0 0
55 2005-07-18 05:42:08 2007-07-03 23:03:50 2019-06-24 00:15:51.875254 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 0 0 0 0 0
58 2005-07-18 09:26:59 2007-07-03 23:03:52 2019-06-24 00:15:53.780835 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 0 0 0 0 0
59 2005-07-18 09:45:00 2007-07-03 23:03:34 2019-06-24 00:15:54.447213 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 0 0 0 0 0
63 2005-07-18 16:36:21 2007-07-03 23:03:59 2019-06-24 00:15:57.052468 Ready for checkin closed Core (Other) enhancement normal   fixed Factor django.core.handlers into subclasses to remove duplicate code   adrian adrian   0 0 0 0 0 0
64 2005-07-18 16:37:56 2007-07-03 23:03:39 2019-06-24 00:15:57.681476 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 0 0 0 0 0
66 2005-07-18 16:57:22 2007-07-03 23:03:50 2019-06-24 00:15:59.043327 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   0 1 0 0 0 0
67 2005-07-18 17:28:38 2007-07-03 23:04:03 2019-06-24 00:15:59.686798 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 0 0 0 0 0
68 2005-07-18 17:32:08 2007-07-03 23:03:24 2019-06-24 00:16:00.412347 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 0 0 0 0 0
69 2005-07-18 18:12:19 2007-07-03 23:03:53 2019-06-24 00:16:01.054426 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 0 0 0 0 0
70 2005-07-18 19:48:49 2007-07-03 23:04:04 2019-06-24 00:16:01.701086 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 0 0 0 0 0
71 2005-07-18 20:26:25 2007-07-03 23:04:07 2019-06-24 00:16:02.374234 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 0 0 0 0 0
73 2005-07-18 21:05:45 2007-07-03 23:03:38 2019-06-24 00:16:03.658483 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 0 0 0 0 0
75 2005-07-18 21:17:26 2007-07-03 23:04:01 2019-06-24 00:16:04.923669 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 0 0 0 0 0
76 2005-07-18 21:21:48 2007-07-03 23:04:02 2019-06-24 00:16:05.555560 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 0 0 0 0 0
77 2005-07-18 23:55:33 2007-07-03 23:03:24 2019-06-24 00:16:06.172799 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 0 0 0 0 0
79 2005-07-19 02:27:56 2007-07-03 23:03:51 2019-06-24 00:16:07.420167 Accepted closed contrib.admin defect normal   invalid Unable to run admin interface via stand-alone server Under revision 191. Running: > django-admin.py runserver 8888 When accessing admin URL receive below. ===== There's been an error: Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/django/core/handlers/wsgi.py", line 184, in get_response callback, param_dict = resolver.resolve(path) File "/usr/lib/python2.3/site-packages/django/core/urlresolvers.py", line 85, in resolve raise Http404, app_path Http404: admin/ adrian jyap@raywoodcommunications.com   0 0 0 0 0 0
82 2005-07-19 06:59:18 2007-07-03 23:03:59 2019-06-24 00:16:09.274703 Ready for checkin closed Core (Other) defect trivial   fixed Config snippet for mod_python users doing tutorial 3 Would be nice, if we could still continue the mod_python path... I don't think the httpd.conf for this site is in SVN either, right? adrian Manuzhai <mail@manuzhai.nl>   0 0 0 0 0 0
88 2005-07-19 16:57:51 2007-07-03 23:03:29 2019-06-24 00:16:13.069853 Accepted closed Core (Other) defect trivial   fixed Configuration should be more forgiving to users who forget the trailing comma. It is really easy for users to forget the trailing comma in configuration settings that should be a tuple, resulting in weird errors. In order to help keep (new) users from getting frustrated, a string should be converted into a tuple for these settings. Here is a patch to implement this: {{{ Index: django/conf/settings.py =================================================================== --- django/conf/settings.py (revision 211) +++ django/conf/settings.py (working copy) @@ -29,9 +29,16 @@ except ImportError, e: raise EnvironmentError, "Could not import DJANGO_SETTINGS_MODULE '%s' (is it on sys.path?): %s" % (me.SETTINGS_MODULE, e) + +# a list of settings that should be converted into tuples if they are strings: +tuple_settings = ["INSTALLED_APPS","TEMPLATE_DIRS"] + for setting in dir(mod): if setting == setting.upper(): - setattr(me, setting, getattr(mod, setting)) + setting_value = getattr(mod, setting) + if setting in tuple_settings and type(setting_value) == str: + setting_value = (setting_value,) #In case the user forgot the comma. + setattr(me, setting, setting_value) # save DJANGO_SETTINGS_MODULE in case anyone in the future cares me.SETTINGS_MODULE = os.environ.get('DJANGO_SETTINGS_MODULE', '') }}} Note that I only put two entries in the tuple_settings list, as they are the only ones I know of. If there are more, they should be added. adrian mmarshall   0 0 0 0 0 0
90 2005-07-19 20:12:48 2007-07-03 23:03:41 2019-06-24 00:16:14.398024 Unreviewed closed Tools enhancement normal   fixed Add "django-admin.py inspectdb" option {{{django-admin.py inspectdb}}} would take an argument -- the database name -- and would introspect the existing database-table structures and print a Django model to standard output. adrian adrian   0 0 0 0 0 0
91 2005-07-19 21:45:54 2007-07-03 23:05:24 2019-06-24 00:16:15.030115 Accepted closed Core (Other) enhancement normal   duplicate A (possible) cleaner ORM fields description Here is a cleaner approach to the ORM fields. Using this patch, the example in the tutorial can be changed to this: {{{ from django.core.meta import Model # Create your models here. class Poll(Model): def fields(Field): Field.Char('question', maxlength=200) Field.DateTime('pub_date', 'date published') class Choice(Model): def fields(Field): Field.ForeignKey(Poll) Field.Char('choice', 'choice', maxlength=200, core=True) Field.Integer('votes', 'votes', core=True) }}} I have done an implementation, which is fully backwards compatible, and quite simple. {{{ Index: django/core/meta.py =================================================================== --- django/core/meta.py (revision 227) +++ django/core/meta.py (working copy) @@ -377,12 +377,53 @@ new_v.func_globals[k] = func new_functions[k] = func + +class FieldGenerator(object): + """FieldGenerator is used for... uh... Generating fields. It has attributes, + such as "Char" and "DateTime", that can be used to create class instances such as + "CharField" or "DateTimeField". These instances are then added to the list "fields", + which can be retrieved to be used as the "fields" attribute in a Model class.""" + def __init__(self): + self.fields = [] + self.last_class = None #This is the class obj that corrisponds to the last __getattr__ call. + + def __getattr__(self,name): + self.last_class = None + try: + obj = eval(name+"Field") + if issubclass(obj,Field): self.last_class = obj + except NameError: pass + if not self.last_class: # If name+"Field" didn't work, just try name. + try: + obj = eval(name) + if issubclass(obj,Field): self.last_class = obj + except NameError: pass + if not self.last_class: + raise AttributeError("Could not find either %s or %sField (or they are not decendants… adrian mmarshall   0 0 0 0 0 0
92 2005-07-19 22:08:06 2007-07-03 23:04:10 2019-06-24 00:16:15.649048 Design decision needed closed Metasystem defect normal   fixed Make meta.Admin.fields optional If {{{meta.Admin.fields}}} isn't defined, it should default to all the fields in the model. adrian adrian   0 0 0 0 0 0
94 2005-07-19 23:26:58 2007-07-03 23:03:40 2019-06-24 00:16:16.906090 Ready for checkin closed contrib.admin defect normal   fixed Mysterious error I am trying to create a module for news, but with the code below, it reports a mysterious error. When trying to add a news item, it says "Please correct the errors below.", but it doesn't show any like it normally does. :/ I'm thinking it's just a stupid mistake on my part as I'm new to this (oh, I guess pretty much every one is right now ;) ) and rather new to python programming (and I've done little with object oriented coding). So if someone could help me out, that would be great! {{{ # 'news' module code: from django.core import meta from django.models import auth, core # Create your models here. class News(meta.Model): fields = ( meta.ForeignKey(auth.User, raw_id_admin=True), meta.CharField('title', maxlength=200), meta.DateTimeField('pub_date', 'date published'), meta.TextField('body',), meta.ManyToManyField(auth.Group, blank=True, help_text="Select which user groups will see this news article."), ) admin = meta.Admin( fields = ( (None, {'fields': ('title','body')}), ('Date information', {'fields': ('pub_date',)}), ('Groups', {'fields': ('groups',)}), ), list_display = ('title', 'pub_date', 'groups', 'was_published_today'), list_filter = ('pub_date', ), search_fields = ('title', ), date_hierarchy = 'pub_date', ) def __repr__(self): return self.title def was_published_today(self): if self.pub_date.date() == datetime.date.today(): return "Yes" else: return "No" was_published_today.short_description = 'Was published today' }}} adrian Joey Marshall   0 0 0 0 0 0
95 2005-07-20 00:05:06 2007-07-03 23:03:41 2019-06-24 00:16:17.527133 Design decision needed closed Core (Other) defect normal   fixed Encourage people to change the TAMPER_SECRET TAMPER_SECRET in source:django/trunk/django/middleware/admin.py#3 should be unique (and secret) for every deployed Django application. This needs to be mentioned in the documentation. The constant should probably be moved to settings.py rather than living in the middleware module. adrian Simon Willison   0 0 0 0 0 0
96 2005-07-20 00:12:31 2007-07-03 23:03:54 2019-06-24 00:16:18.152421 Design decision needed closed *.djangoproject.com   normal   fixed Coment counts on the djangoproject.com weblog It would be useful to see the number of comments on each entry attached to both the front page of the weblog and the front page of the site. jacob Simon Willison   0 0 0 0 0 0
98 2005-07-20 00:28:49 2007-07-03 23:04:10 2019-06-24 00:16:19.368099 Ready for checkin closed Documentation enhancement normal   fixed Pretty CSS for PHILOSOPHY sections in docs Every now and then in the tutorials there's a section starting with PHILOSOPHY which outlines some of the thinking behind Django's design. It would be nice if these were set apart from the rest of the content a bit, by being in a box with a different background colour and a picture of a lightbulb or thinking greek guy or something. See here for an example: http://www.djangoproject.com/documentation/tutorial1/#creating-models wilson Simon Willison   0 0 0 0 0 0
99 2005-07-20 00:48:15 2007-07-03 23:03:32 2019-06-24 00:16:20.030053 Design decision needed closed Core (Other) enhancement normal   fixed enhance model "ordering" to reduce redundancy for multiple same-order fields currently: ordering = ( ('last_name','ASC'), ('first_name','ASC'), ('middle_name','ASC'), ('name_suffix','ASC'), ) suggested: ordering = ((('last_name','first_name','middle_name','name_suffix'),'ASC'),) Looks like the same "string or sequence of strings" trick, but going the other way this time! Should be backwards compatible, too. adrian maney@two14.net   0 0 0 0 0 0
100 2005-07-20 01:21:07 2007-07-03 23:04:10 2019-06-24 00:16:20.631079 Ready for checkin closed Documentation defect normal   fixed document ForeignKey('self') hack, please assuming I got it right this time :-) jacob maney@two14.net   0 0 0 0 0 0
102 2005-07-20 02:21:13 2007-07-03 23:04:15 2019-06-24 00:16:21.871301 Ready for checkin closed Core (Other) defect normal   fixed Exceptions aren't html-quoted Exceptions that contain <> (like <Foo.bar at 0x139413>) aren't HTML quoted, and the text disapears. adrian ianb@colorstudy.com   0 0 0 0 0 0
103 2005-07-20 03:37:24 2007-07-03 23:06:11 2019-06-24 00:16:22.510345 Design decision needed closed *.djangoproject.com defect normal   fixed "Get current version: 1.0" is misleading The front page link to the download page says "Get current version: 1.0". This is misleading - there is no version 1.0 yet. The text should read "Get development version" or something similar which reinforces the fact that Django has not yet made it to a marked version. I would also argue that going straight to 1.0 isn't necessarily a good idea. If you look at Rails, they spent months and months rolling through the 0.9 etc releases before everything was considered stable enough for a 1.0. This seems like a smart model to follow. jacob Simon Willison   0 0 0 0 0 0
104 2005-07-20 06:12:21 2007-07-03 23:04:05 2019-06-24 00:16:23.173999 Design decision needed closed Core (Other) defect normal 1.0 duplicate i18n for internal strings Maybe it would be a good idea to start using gettext for internal string resources, so people could start translating stuff? I think especially about internal strings like those in the validators. adrian hugo i18n 0 0 0 0 0 0
108 2005-07-20 11:52:18 2007-07-03 23:03:57 2019-06-24 00:16:25.663763 Unreviewed closed *.djangoproject.com defect normal   fixed WikiFormatting page is not there When I am entering a new ticket, just above the main textarea the link to the WikiFormatting points to an empty page. I think it needs to be restored from the default Trac installation. jacob verbosus   0 0 0 0 0 0
109 2005-07-20 13:17:49 2007-07-03 23:03:46 2019-06-24 00:16:26.276816 Accepted closed contrib.admin defect blocker   fixed Patch: Customizing Date(Time)Field displays In the admin interface, dates are displayed as July 11, 2005, 8:39 p.m., while I'd at the least prefer to have a 24-hour format for the time. I think there should be options DATE_FORMAT, TIME_FORMAT and DATETIME_FORMAT which take care of the default formatting for these fields. anonymous Manuzhai   0 0 0 0 0 0
117 2005-07-20 18:25:32 2007-07-03 23:04:07 2019-06-24 00:16:31.286013 Unreviewed closed *.djangoproject.com enhancement normal   wontfix Site search and/or Trac search for djangoproject.com According to TracSearch, Trac has a neat feature where you can enter bug numbers, changeset codes etc in to the search box to jump directly to that item within Trac. It would be useful if the Trac search box was added to the templates for code.djangoproject.com in the same place on every page (it might work in the top right in the light green bar, below the Home / Download / etc links). Even better - how about adding search to the whole of the djangoproject.com website? It would be very handy for searching through the growing piles of documentation, not to mention the comments. jacob Simon Willison   0 0 0 0 0 0
120 2005-07-20 19:49:48 2007-07-03 23:05:27 2019-06-24 00:16:33.174445 Accepted closed Tools defect normal   fixed djang-admin.py called without argument Calling django-admin.py with no argument gives the following traceback: {{{ Traceback (most recent call last): File "./django-admin.py", line 102, in ? main() File "./django-admin.py", line 63, in main print_error("An 'action' is required.") TypeError: print_error() takes exactly 2 arguments (1 given) }}} And print_error function (defined line 43), effectively wants 2 arguments ;) I'm using rev 249 of Django's trunk. Attached is a trivial proposed patch. adrian anonymous   0 0 0 0 0 0
121 2005-07-20 20:20:29 2007-07-03 23:04:25 2019-06-24 00:16:33.801943 Accepted closed Metasystem enhancement normal   fixed [patch] Names in SQL should be quoted Some valid Python-identifiers are reserved words in SQL-databases, for instance "when" in PostgreSQL. It would be very nice, if Django would quote all names (e.g. schema, table, row) in SQL statements, so these database-reserved words would not pose problems. adrian sune.kirkeby@gmail.com sql 0 1 0 0 0 0
124 2005-07-20 21:39:32 2007-07-03 23:04:49 2019-06-24 00:16:35.707785 Ready for checkin closed Core (Other) defect normal   duplicate Better handling of raw POST data I'll come up with a patch for this, if slashzero doesn't. adrian Manuzhai   0 0 0 0 0 0
125 2005-07-20 22:13:00 2007-07-03 23:03:55 2019-06-24 00:16:36.327262 Ready for checkin closed contrib.admin defect normal   wontfix View-Controller separation violation For example, django.views.admin.main: {{{ if lookup_opts.admin.search_fields: raw_template.append('<div id="toolbar">\n<form id="changelist-search" action="" method="get">\n') raw_template.append('<label><img src="%simg/admin/icon_searchbox.png" /></label> ' % ADMIN_MEDIA_PREFIX) raw_template.append('<input type="text" size="40" name="%s" value="%s" id="searchbar" /> ' % \ (SEARCH_VAR, escape(query))) }}} Shouldn't it be done only with templates? adrian maurycy   0 0 0 0 0 0
128 2005-07-20 23:39:49 2007-07-03 23:03:54 2019-06-24 00:16:38.175802 Accepted closed Template system defect normal   worksforme IndexError when using invalid {% extends %} in template should be replaced with better error message. First of all the error {{{ There's been an error: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 190, in get_response return callback(request, **param_dict) File "/home/espen/django/blog/apps/blog/views/blog.py", line 20, in details return HttpResponse(t.render(c)) File "/usr/lib/python2.4/site-packages/django/core/template.py", line 116, in render return self.nodelist.render(context) File "/usr/lib/python2.4/site-packages/django/core/template.py", line 437, in render bits.append(node.render(context)) File "/usr/lib/python2.4/site-packages/django/core/template_loader.py", line 80, in render parent_is_child = isinstance(compiled_parent.nodelist[0], ExtendsNode) IndexError: list index out of range }}} The template file that trys to extend base.html: {{{ {% extends "base" %} {% block title %} Espen Grindhaug - Blog - {{ obj.headline }} {% endblock %} {% block content %} <h1>{{ obj.headline }}</h1> <p class="summary">{{ obj.summary }}</p> <p class="body">{{ obj.body }}</p> <p class="by">By {{ obj.author }} ({{ obj.pub_date }})</p> {% endblock %} }}} The weird thing here is that I get exactly the same error with completly different child template. base.html (the same as in [http://www.djangoproject.com/documentation/templates/#template-inheritance URL]): {{{ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <link rel="stylesheet" href="style.css" /> <title>{% block title %}Espen Grindhaug{% endblock %}</title> </head> <body> <div id="sidebar"> {% block sidebar %} <ul> <li><a href="/">Home</a></li> <li><a href="/blog/">Blog</a></li> </ul> {% endblock %} </div> <div id="content"> {% block content %}{%… adrian espen@grindhaug.org   0 0 0 0 0 0
129 2005-07-21 00:02:52 2007-07-03 23:04:03 2019-06-24 00:16:38.808651 Accepted closed Metasystem defect normal   fixed Multiple ManyToManyField fields with same "to" reference tries to create duplicate tables Revsion 257 added support for adding multiple !ManyToManyField fields with the same "to" class on the same class. I've tried adding two fields where one has an explicit rel_name option but running "django-admin.py sql myapp" is showing two CREATE TABLE statements with the same table name. I think I've tracked the problem down to the get_m2m_db_table method in the !ManyToManyField class in core/meta.py but I don't understand the code base enough yet to try to fix it. It looks like the code is returning the name as myapp_fromname_toname but I'd expect the name of the many-to-many table to be myapp_relname when the rel_name option is specified. I'm using the MySQL database engine but I don't think that has any bearing on this problem. adrian jason@diamond.name   0 0 0 0 0 0
130 2005-07-21 02:30:54 2007-07-03 23:04:15 2019-06-24 00:16:39.440293 Ready for checkin closed *.djangoproject.com enhancement normal   wontfix Display comments in Trac timeline Jacob figured out how to do this on our internal Trac installation. Let's do it here, too. jacob adrian   0 0 0 0 0 0
133 2005-07-21 09:24:39 2007-07-03 23:04:16 2019-06-24 00:16:41.333085 Unreviewed closed Core (Other) defect trivial   fixed Patch to improve DATABASE_ENGINE error message I could not load the postgresql back end because psycopg was nog installed properly. However, that was not clear from the error message. Patch attached. It changes "Your DATABASE_ENGINE setting, %r, is invalid. Is it spelled correctly? Available options are: %s" into "Could not load database backend: %s. Is DATABASE_ENGINE (currently, %r) spelled correctly? Available options are: %s" displaying the error message from import. adrian Joeri van Ruth <jvr+djangotrac@dory.blub.net>   0 0 0 0 0 0
134 2005-07-21 09:56:07 2007-07-03 23:05:23 2019-06-24 00:16:41.966013 Unreviewed closed contrib.admin defect normal   fixed Template for password change not included in source dist It seems that there are probably templates for this, just not in the current dist? {{{ TemplateDoesNotExist: Tried ['/home/manuzhai/dev/django/django/conf/admin_templates/registration/password_change_form.html'] }}} adrian Manuzhai   0 0 0 0 0 0
136 2005-07-21 12:15:51 2007-07-03 23:04:35 2019-06-24 00:16:43.178183 Design decision needed closed Documentation enhancement normal   fixed Provide a path to read documentation files in docs/ (enhancement/trivial) Yeah, it is really valuable to have a docs/ directory always rigorously up to date. The exposition is good also. However for people that approach Django for the first time it would be a great help to know if there is a *suggested* order to read documentation files. (Yes, I'm paranoid versus quality of documentation, it is too important!) It would be possible to specify that order in README file and add a prefix (00_, 01_, 02_ etc) in front of each file in docs/ This ticket is about a small but important!) change, anyway in my opinion it would be another great "welcome here" to newcomers :-) jacob paolo   0 0 0 0 0 0
138 2005-07-21 14:57:54 2007-07-03 23:04:26 2019-06-24 00:16:44.389563 Accepted closed Documentation defect normal   fixed Error naming the "docs" directory in README Inside README each occurrence of doc/ should be replaced with docs/. adrian paolo   0 0 0 0 0 0
141 2005-07-21 18:59:14 2007-07-03 23:04:25 2019-06-24 00:16:46.340156 Ready for checkin closed Core (Other) defect normal   fixed --settings option doesn't work as shown in the tutorial When running '''django-admin.py init --settings='myproject.settings.main'''' (as specified in tutorial 1) I received: {{{ C:\www\webroot\myproject>django-admin.py init --settings='myproject.settings.main' Traceback (most recent call last): File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\bin\django-admin.py", line 103, in ? main() File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\bin\django-admin.py", line 68, in main ACTION_MAPPING[action]() File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\management.py", line 278, in init from django.core import db, meta File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\db\__init__.py", line 16, in ? from django.conf.settings import DATABASE_ENGINE File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\conf\settings.py", line 34, in ? raise EnvironmentError, "Could not import %s '%s' (is it on sys.path?): %s"% (ENVIRONMENT_VARIABLE, me.SETTINGS_MODULE, e) EnvironmentError: Could not import DJANGO_SETTINGS_MODULE ''myproject.settings.main'' (is it on sys.path?): No module named 'myproject.settings.main' }}} The problem is with the quotes around the module name (--settings='myproject.settings.main'). Running '''django-admin.py init --settings=myproject.settings.main''' (no quotes) works correctly. adrian sdelatorre@gmail.com   0 0 0 0 0 0
142 2005-07-21 19:14:25 2007-07-03 23:03:55 2019-06-24 00:16:46.955511 Unreviewed closed Documentation defect normal   duplicate tutorial 1 bug in init --settings In tutorial1, rev 253, line 77: django-admin.py init --settings='myproject.settings.main' should be: django-admin.py init --settings=myproject.settings.main With Windows XP, Python 2.4.1, Django rev 282, I get this error when the quotes are present: {{{ C:\MyStuff\projects\django>c:\Python24\python.exe C:\Python24\Lib\site-packages\ django-1.0.0-py2.4.egg\django\bin\django-admin.py init --settings='myapp.setting s.admin' Traceback (most recent call last): File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\bin\django-a dmin.py", line 103, in ? main() File "C:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\bin\django-a dmin.py", line 68, in main ACTION_MAPPING[action]() File "c:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\managem ent.py", line 278, in init from django.core import db, meta File "c:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\db\__in it__.py", line 16, in ? from django.conf.settings import DATABASE_ENGINE File "c:\Python24\Lib\site-packages\django-1.0.0-py2.4.egg\django\conf\setting s.py", line 34, in ? raise EnvironmentError, "Could not import %s '%s' (is it on sys.path?): %s" % (ENVIRONMENT_VARIABLE, me.SETTINGS_MODULE, e) EnvironmentError: Could not import DJANGO_SETTINGS_MODULE ''myapp.settings.admin '' (is it on sys.path?): No module named 'myapp.settings.admin' }}} When I remove the quotes, I don't get an error, and my database is initialized correctly. {{{ C:\MyStuff\projects\django>c:\Python24\python.exe C:\Python24\Lib\site-packages\ django-1.0.0-py2.4.egg\django\bin\django-admin.py init --settings=myapp.settings .admin C:\MyStuff\projects\django> }}} jacob Jason Huggins tutorial django-admin init settings 0 0 0 0 0 0
143 2005-07-21 19:42:36 2007-07-03 23:04:38 2019-06-24 00:16:47.565693 Accepted closed Core (Other) defect normal   fixed Problem running the command line examples in Tut 1 when using --settings option In tutorial 1, under "Playing with the API", none of the examples will work if you've been using the --settings option with django-admin.py (the DJANGO_SETTINGS_MODULE env variable was never set). To work, you have to do the following before importing the project objects: {{{ >>> import os >>> os.environ['DJANGO_SETTINGS_MODULE']='myproject.settings.main' >>> from django.models.polls import polls, choices }}} Is there a more user friendly way to do this? Maybe add a global variable to django.conf that is used to do the import? {{{ >>> django.conf.DJANGO_SETTINGS_MODULE='myproject.settings.main' }}} or possibly {{{ >>> django.settings_module='myproject.settings.main' }}} adrian sdelatorre@gmail.com   0 0 0 0 0 0
144 2005-07-21 23:29:46 2007-07-03 23:04:25 2019-06-24 00:16:48.176067 Accepted closed contrib.admin defect normal   duplicate Some admin media files are not viewable When viewing the Polls site in tutorial 2 under "Click the 'What's up?' poll to edit it:" paragraph, I noticed that a few of the icons were missing (the save button, the checkbox icon when saving an item, the right side of the history button, etc.). The CSS and JS seem to load correctly, and the icons you have sourced at http://media.ljworld.com/ also load correctly. The problem lies with the CSS file which doesn't correctly go to http://media.ljworld.com/. Just to test, I changed the url to the tool-right.gif file in the css to http://media.ljworld.com/img/admin/tool-right.gif and it worked. adrian sdelatorre@gmail.com   0 0 0 0 0 0
146 2005-07-22 03:37:46 2007-07-03 23:04:40 2019-06-24 00:16:49.396912 Accepted closed Database layer (models, ORM) defect normal   fixed Change order_by and ordering parameters to be less verbose Instead of the following: {{{ ordering = (('pub_date', 'ASC'), ('name', 'DESC'), (None, 'RANDOM')) }}} ...we should use the following: {{{ ordering = ('pub_date', '-name', '?') }}} See http://groups-beta.google.com/group/django-developers/browse_thread/thread/f4945bd967defde1/f5f3cb3312f77fe5 adrian adrian   0 0 0 0 0 0
147 2005-07-22 03:55:27 2007-07-03 23:04:17 2019-06-24 00:16:50.031639 Design decision needed closed contrib.admin defect normal   fixed "sqlite" should be "sqlite3" in conf/project_template/settings/main.py Problem: new users are just going to copy the suggested "sqlite" in settings/main.py and find that it doesn't work. Solution: Use "sqlite3" throughout. Apply the following patch. {{{ Index: django/conf/project_template/settings/main.py =================================================================== --- django/conf/project_template/settings/main.py (revision 288) +++ django/conf/project_template/settings/main.py (working copy) @@ -10,11 +10,11 @@ LANGUAGE_CODE = 'en-us' -DATABASE_ENGINE = 'postgresql' # 'postgresql', 'mysql', or 'sqlite' -DATABASE_NAME = '' # or path to database file if using sqlite -DATABASE_USER = '' # not used with sqlite -DATABASE_PASSWORD = '' # not used with sqlite -DATABASE_HOST = '' # Set to empty string for localhost; not used with sqlite +DATABASE_ENGINE = 'postgresql' # 'postgresql', 'mysql', or 'sqlite3' +DATABASE_NAME = '' # or path to database file if using sqlite3 +DATABASE_USER = '' # not used with sqlite3 +DATABASE_PASSWORD = '' # not used with sqlite3 +DATABASE_HOST = '' # Set to empty string for localhost; not used with sqlite3 SITE_ID = 1 }}} adrian rmunn@pobox.com   0 0 0 0 0 0
153 2005-07-22 13:06:28 2007-07-03 23:04:14 2019-06-24 00:16:53.763612 Accepted closed Documentation defect normal   fixed Change docs to use new ordering syntax See #146 and [292]. jacob adrian   0 0 0 0 0 0
155 2005-07-22 13:12:55 2007-07-03 23:04:05 2019-06-24 00:16:55.069832 Design decision needed closed contrib.admin defect normal   invalid django-admin initializes mysite.com in meta table without way to change that The django-admin script initializes the meta table to contain a mysite.com record that is used for example with the flatfiles and redirects apps. There you can select for what site you want to add stuff - but there is no way to change this record to your own address and site name. And there is no way to add another site to the database - so one asks himself why there are multiple section possibilities in the flatfiles and redirects apps in the first place ... adrian gb@bofh.ms   0 0 0 0 0 0
157 2005-07-22 14:01:21 2007-07-03 23:04:35 2019-06-24 00:16:56.358870 Accepted closed contrib.admin defect normal   fixed view/admin/main.py change_list assumes orderlist is tuple In the function change_list in views/admin/main.py, an assumption is made that the "ordering" variable will be a tuple. The orderlist can be a single string, according to the behaviour built in meta.handle_legacy_orderlist. As a result of this, the code around line 106 seems incorrect, as it assumes an indexable array. Since a string actually is an indexable array, no error is thrown immediately. The following patch restores my admin pages to working order, but it may not be the best way to handle this. {{{ Index: django/views/admin/main.py =================================================================== --- django/views/admin/main.py (revision 293) +++ django/views/admin/main.py (working copy) @@ -98,6 +98,9 @@ # Normalize it to new-style ordering. ordering = meta.handle_legacy_orderlist(ordering) + if isinstance(ordering, basestring): + # tupelize it + ordering = (ordering,) if ordering[0].startswith('-'): order_field, order_type = ordering[0][1:], 'DESC' }}} adrian mfenniak@pobox.com   0 0 0 0 0 0
158 2005-07-22 16:34:51 2007-07-03 23:04:07 2019-06-24 00:16:57.019894 Design decision needed closed contrib.admin defect normal   fixed Base admin template changes * Now that the templates are in, re-enable the password change option. * Point "Home" to /admin/ by default; this makes sense since password_change and logout also point to /admin/. adrian Manuzhai   0 0 0 0 0 0
160 2005-07-22 17:03:40 2007-07-03 23:04:44 2019-06-24 00:16:58.337037 Ready for checkin closed contrib.admin defect normal   fixed Never get to the final logout page When trying to logout of the admin interface (code from [295]), I never get to the final logout page saying "Thanks for spending time with the website.". I do get redirected to /admin/logout/, but then I get a login form again (which, when I log in, logs me out again, see #159), instead of the final logged-out page. This leads me to think I'm not completely logged out. adrian Manuzhai   0 0 0 0 0 0
161 2005-07-22 17:42:12 2007-07-03 23:04:32 2019-06-24 00:16:58.976434 Design decision needed closed Tools   normal   fixed Log output for &#34;django-admin runserver&#34; shouldn't display admin media The admin media access logs just get in the way. We should figure out how to stop them from being displayed, so that the logs only feature Django-powered pages. adrian adrian   0 0 0 0 0 0
163 2005-07-22 17:58:19 2007-07-03 23:04:16 2019-06-24 00:17:00.310826 Unreviewed closed Template system enhancement major magic-removal fixed Option to leave off __exact Doing {{{sites.get_object(id__exact = 1)}}} seems kind of verbose if {{{sites.get_object(id = 1)}}} would convey the same meaning and be a little easier to read. adrian Manuzhai   0 0 0 0 0 0
166 2005-07-22 20:10:11 2007-07-03 23:04:18 2019-06-24 00:17:02.256922 Design decision needed closed Core (Other) enhancement normal   fixed [patch] Add "in" to the lookup types in the DB API This patch allows one to do {{{field__in=[1,4,7,10]}}} to select a non-contiguous set of values in a single SELECT statement, which will look like this in SQL: {{{SELECT * FROM table WHERE field IN (1,4,7,10)}}} {{{ Index: django/core/meta.py =================================================================== --- django/core/meta.py (revision 299) +++ django/core/meta.py (working copy) -1018,7 +1020,10 @@ return '%s%s %s %%s' % (table_prefix, field_name, db.OPERATOR_MAPPING[lookup_type]) except KeyError: pass - if lookup_type in ('range', 'year'): + if lookup_type == 'in': + in_clause = ','.join(['%s']*len(value)) + return '%s%s IN (%s)' % (table_prefix, field_name, in_clause) + elif lookup_type in ('range', 'year'): return '%s%s BETWEEN %%s AND %%s' % (table_prefix, field_name) elif lookup_type in ('month', 'day'): return "%s = %%s" % db.get_date_extract_sql(lookup_type, table_prefix + field_name) -1630,7 +1635,7 @@ "Returns field's value prepared for database lookup." if lookup_type in ('exact', 'gt', 'gte', 'lt', 'lte', 'ne', 'month', 'day'): return [value] - elif lookup_type == 'range': + elif lookup_type in ('range', 'in'): return value elif lookup_type == 'year': return ['%s-01-01' % value, '%s-12-31' % value] }}} adrian rmunn@pobox.com   0 1 0 0 0 0
168 2005-07-23 02:57:40 2007-07-03 23:04:31 2019-06-24 00:17:03.530214 Accepted closed contrib.admin defect major   fixed history() in django/views/admin/main.py makes assumptions about the object's key name Normally the ID of an object is "id", except in cases like mine where I'd redefined the key to be something like list: {{{ "meta.AutoField('item_id','Item ID',primary_key=True,unique=True)," }}} When pulling up the history of a record in the administrative interface, the function history() in django/views/admin/main.py is called and an assumption is made on line 1080: {{{ "obj = mod.get_object(id__exact=object_id)" }}} In my case, I believe that it should be (it cannot be hardcoded like this, obviously this needs to be dynamic): {{{ "obj = mod.get_object(item_id__exact=object_id)" }}} Here's the exact text of the traceback I get: {{{ There's been an error: Traceback (most recent call last): File "/usr/local/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 190, in get_response return callback(request, **param_dict) File "/usr/local/lib/python2.4/site-packages/django/views/admin/main.py", line 1080, in history obj = mod.get_object(id__exact=object_id) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 87, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 1035, in function_get_object obj_list = function_get_list(opts, klass, **kwargs) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 1057, in function_get_list select, sql, params = function_get_sql_clause(opts, **kwargs) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 1235, in function_get_sql_clause tables2, join_where2, where2, params2, _ = _parse_lookup(kwargs.items(), opts) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 1224, in _parse_lookup _throw_bad_kwarg_error(kwarg) File "/usr/local/lib/python2.4/site-packages/django/core/meta.py", line 1126, in _throw_bad_kwarg_error raise TypeError, "got unexpected keyword argument '%s'" % kwarg … adrian clintecker@gmail.com history 0 0 0 0 0 0
169 2005-07-23 11:28:21 2007-07-03 23:04:14 2019-06-24 00:17:04.169478 Design decision needed closed Documentation defect trivial   fixed \\dt instead of \dt in Tutorial 1 In [http://www.djangoproject.com/documentation/tutorial1/ Tutorial 1] we are told: ''If you're interested, run the command-line client for your database and type \\dt (PostgreSQL), SHOW TABLES; (MySQL), or .schema (SQLite) to display the tables.'' However, the right command in PostgreSQL is {{{\dt}}}, not {{{\\dt}}} jacob django@gimbo.org.uk   0 0 0 0 0 0
173 2005-07-24 03:00:41 2007-07-03 23:04:42 2019-06-24 00:17:06.684751 Ready for checkin closed Documentation defect normal   invalid How do I start Django's in built webserver? I don't want to spend however long setting up apache! It says in your docs that you have been super clever and thought of me by including a webserver out of the box. Maybe I am being very silly and missing it but I can't seem to find how to start said webserver? Does it really exist ;-) ? Thanks guys, you need a forum for this sort of stuff btw. jacob andrew.phillipo@yourstay.com Apache Web Server built-in 0 0 0 0 0 0
177 2005-07-24 19:22:36 2007-07-03 23:04:25 2019-06-24 00:17:09.182816 Ready for checkin closed contrib.admin defect minor   duplicate Logout from Admin leaves you in /admin/logout If you logout from the admin interface, your browser (konq & moz) is left in /admin/logout/ and you can't log back in until you manually go to /admin adrian EABinGA   0 0 0 0 0 0
178 2005-07-24 20:38:38 2007-07-03 23:04:14 2019-06-24 00:17:09.826621 Design decision needed closed Core (Other) defect normal   invalid Wrong time zone usage Django doesn't pick up time zone when running under Ubuntu. Setting TZ in environment fixes it. Ubuntu (and Debian Sarge) doesn't have TZ in environment by default though. adrian edgars@way.lv time zone 0 0 0 0 0 0
183 2005-07-25 00:36:48 2007-07-03 23:04:46 2019-06-24 00:17:12.962963 Accepted closed Template system defect normal   fixed TypeError: can't compare datetime.datetime to datetime.date Error: {{{ There's been an error: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line 63, in get_response return callback(request, **param_dict) File "/usr/lib/python2.4/site-packages/django/views/generic/date_based.py", line 108, in archive_month if date >= now: TypeError: can't compare datetime.datetime to datetime.date }}} adrian espen@grindhaug.org   0 0 0 0 0 0
185 2005-07-25 00:59:00 2007-07-03 23:04:51 2019-06-24 00:17:14.244306 Design decision needed closed Core (Other) defect normal   invalid Chaining views Currently, it's possible to assign only one view to specified URL pattern. It would be great to allow to create more complicated chains of views. There are two questions. First, how to extend urlpatterns to support more than one view. Second, how to pass HttpResponse between without breaking existing modules. adrian maurycy   0 0 0 0 0 0
186 2005-07-25 01:24:26 2007-07-03 23:04:43 2019-06-24 00:17:14.874160 Accepted closed Metasystem enhancement normal   fixed [patch] Refactor django/core/meta.py to eliminate duplicate code The {{{function_get_list}}} and {{{function_get_iterator}}} functions in {{{django/core/meta.py}}} are identical except for their return type. I propose refactoring them by making {{{function_get_list}}} into a simple wrapper around {{{function_get_iterator}}}. adrian rmunn@pobox.com   0 1 0 0 0 0
187 2005-07-25 01:27:13 2007-07-03 23:04:17 2019-06-24 00:17:15.501657 Ready for checkin closed contrib.admin defect normal 1.0 fixed Uknown error with ordering in the admin interface I've defined the following model: {{{ #!python class Blog(meta.Model): fields = ( meta.OneToOneField(Site), #One blog per site meta.CharField('name', maxlength=100, help_text="Blog Title, as shown on the page"), meta.CharField('subtitle', maxlength=500), meta.CharField('titlebarname', "Title Bar Name", maxlength=50, blank=True, help_text="Short name for putting in <title> elements") ) admin = meta.Admin() def __repr__(self): return self.name }}} When I try to list my blogs by going to http://localhost:8000/admin/blog/blogs/ I always end up with the following error: {{{ There's been an error: Traceback (most recent call last): File "D:\My Documents\Python Sources\Django\django\core\handlers\base.py", line 63, in get_response return callback(request, **param_dict) File "D:\My Documents\Python Sources\Django\django\views\admin\main.py", line 97, in change_list ordering = lookup_opts.admin.ordering or lookup_opts.ordering or ['-' + lookup_opts.pk.name] AttributeError: 'NoneType' object has no attribute 'ordering' }}} A quick play with the object in the interpreter shows it's working correctly: {{{ #!python >>> from django.models.blog import * >>> b = blogs.get_list() >>> b [My Blog] >>> from django.models.blog import * >>> bs = blogs.get_list() >>> bs [My Blog] >>> b = bs[0] >>> b My Blog >>> b.name 'My Blog' >>> b.id 1 >>> b.subtitle 'Where you find all the news' >>> b.titlebarname ' ' >>> s = b.get_site() >>> s mysite.com >>> s.domain 'mysite.com' >>> s.name 'My Django site' >>> }}} adrian Moof <moof@metamoof.net>   0 0 0 0 0 0
196 2005-07-25 19:15:04 2007-07-03 23:04:49 2019-06-24 00:17:21.185710 Design decision needed closed Core (Other) defect normal   fixed Patch: Allow integer months in views.generic.date_based While the three-letter months are nice and pretty, they are not international-safe. Given that most web hosting servers don't allow you to set the locale, and even if it did you might be hosting more than one language on the box. So a poor Spaniard will be wondering why he's looking at "jan" rather than "ene" if hosted on an English server. The following patch keeps the three-letter months as an option in the various views that use months, but also allows for one- or two-digit month numbers. adrian Moof <moof@metamoof.net>   0 0 0 0 0 0
197 2005-07-25 21:01:23 2007-07-03 23:04:42 2019-06-24 00:17:21.826108 Unreviewed closed contrib.admin defect normal   fixed Adding a flatfile causes a traceback in sqlite3.py Here is the taceback: {{{ There's been an error: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line 63, in get_response return callback(request, **param_dict) File "/usr/lib/python2.4/site-packages/django/views/admin/main.py", line 765, in add_stage new_object = manipulator.save(new_data) File "/usr/lib/python2.4/site-packages/django/core/meta.py", line 87, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/lib/python2.4/site-packages/django/core/meta.py", line 1464, in manipulator_save was_changed = getattr(new_object, 'set_%s' % f.name)(new_data.getlist(f.name)) File "/usr/lib/python2.4/site-packages/django/core/meta.py", line 87, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/lib/python2.4/site-packages/django/core/meta.py", line 922, in method_set_many_to_many cursor.executemany(sql, [(this_id, i) for i in ids_to_add]) File "/usr/lib/python2.4/site-packages/django/core/db/base.py", line 20, in executemany result = self.cursor.executemany(sql, param_list) File "/usr/lib/python2.4/site-packages/django/core/db/backends/sqlite3.py", line 59, in executemany query = self.convert_query(query, len(params)) File "/usr/lib/python2.4/site-packages/django/core/db/backends/sqlite3.py", line 64, in convert_query return query % tuple("?" * num_params) TypeError: not enough arguments for format string }}} jacob mmarshall   0 0 0 0 0 0
198 2005-07-25 21:26:45 2007-07-03 23:04:24 2019-06-24 00:17:22.454141 Ready for checkin closed Contrib apps enhancement critical magic-removal fixed istartswith doesn't work istartswith is not working. adrian brantley (deadwisdom@gmail.com) database lookup 0 0 0 0 0 0
203 2005-07-26 08:49:12 2007-07-03 23:04:41 2019-06-24 00:17:25.570810 Unreviewed closed Documentation defect normal   fixed Tutorial 2 list_filter example needs another comma I did not get list_filter example in tutorial 2 working without adding another comma after the line. Here is how I got it to work: "list_filter = ('pub_date', )," adrian sirpete@iki.fi list_filter tutorial 0 0 0 0 0 0
204 2005-07-26 08:57:17 2007-07-03 23:04:23 2019-06-24 00:17:26.255082 Accepted closed Tools defect normal   fixed Inconsistent treatment of blank passwords for superusers django-admin.py allows one to create a superuser with a blank password, but that password can't then be changed (eg to something non-blank) using the admin interface, because /admin/password_change/ demands that "Old password" be non-blank. Suggested action: fix django-admin.py so blank superuser passwords aren't allowed. adrian django@gimbo.org.uk password blank superuser createsuperuser django-admin.py 0 0 0 0 0 0
205 2005-07-26 09:24:34 2007-07-03 23:05:07 2019-06-24 00:17:26.901466 Design decision needed closed contrib.admin defect normal   fixed Can't log in from /admin/logout/ I don't seem to be able to log in to the admin interface from the /admin/logout/ page, despite the presence of a login form there. How to reproduce (using admin system of a fresh Django install): 1. Log in as a superuser at /admin/ 1. Click "Log out", takes us to /admin/logout/, which has a login form. 1. Attempt to log in using that form... Just stays on /admin/logout/ adrian django@gimbo.org.uk login logout 0 0 0 0 0 0
212 2005-07-27 16:28:02 2007-07-03 23:04:42 2019-06-24 00:17:31.401703 Unreviewed closed contrib.admin defect normal   fixed help_text is not displayed for ManyToManyField in the admin interface   adrian jkocherhans@mac.com   0 0 0 0 0 0
215 2005-07-27 20:26:28 2007-07-03 23:04:58 2019-06-24 00:17:33.309691 Accepted closed Database layer (models, ORM) defect normal 1.1 wontfix Need to generate postgresql tables WITHOUT OIDS by default When generating tables in Postgresql, django doesn't specify WITHOUT OIDS, which in Postgresql 7.4 or older (don't know about 8) results in tables that consumes the installation-wide OIDS. Most of the time this is unnecessary and undesirable. It would be good if the user is given a choice to specify WITH OIDS if they really know what they are doing. adrian wgunadi@nextcoder.net OIDS 0 0 0 0 0 0

Next page

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE "tickets_full" (
        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
    );