tickets
32,817 rows
This data as json, CSV (advanced)
Suggested facets: type, severity, resolution, easy, has_patch, needs_better_patch, needs_tests, needs_docs, created (date), changetime (date), last_pulled_from_trac (date)
| id ▼ | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2005-07-13 19:03:27 | 2012-05-20 15:12:37 | 2022-03-06 03:19:23.152286 | Unreviewed | closed | Core (Other) | enhancement | normal | fixed | Create architecture for anonymous sessions | We need an architecture for anonymous sessions. Right now we have django.models.auth.sessions, but that only handles registered users' sessions. We need a system that automatically creates and manages sessions for anonymous users. Here's one idea for this: * In the settings file, you define a {{{SESSION_MODULE}}} string, like the {{{AUTH_PROFILE_MODULE}}}, which points to the model to use for sessions. * Using this, httpwrappers automatically creates a request.session object which is persistant across requests based on cookies, etc. | jacob | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 2 | 2005-07-13 19:04:45 | 2007-07-03 23:04:18 | 2022-03-06 03:19:23.301840 | 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 | 2022-03-06 03:19:23.472795 | 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 | ||
| 4 | 2005-07-13 19:08:10 | 2005-09-16 17:01:24 | 2022-03-06 03:19:23.630870 | Design decision needed | closed | Core (Cache system) | enhancement | normal | duplicate | Add a db cache backend | We should have a db cache backend -- this will be very useful for people who can't/won't run memcached. | jacob | adrian | 0 | 0 | 0 | 0 | ||||
| 5 | 2005-07-13 19:08:56 | 2007-02-25 17:31:18 | 2022-03-06 03:19:23.798789 | Design decision needed | closed | Metasystem | enhancement | normal | wontfix | Add a cache=NUM_SECONDS argument to QuerySet | It'd be convenient for the lookup API to have caching baked in. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 6 | 2005-07-13 19:13:41 | 2006-10-07 21:25:13 | 2022-03-06 03:19:23.963614 | Unreviewed | closed | Metasystem | defect | minor | fixed | Remove has_related_links option from models | The current (undocumented) {{{has_related_links}}} code is too Ellington-specific and doesn't belong in Django. Let's remove it. We'll have to come up with a more generic way of associating content_type_id/object_id relationships, such as related links, to a model. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 7 | 2005-07-13 19:14:41 | 2007-07-03 23:04:26 | 2022-03-06 03:19:24.105352 | 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 | 2022-03-06 03:19:24.252139 | 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 | ||
| 10 | 2005-07-13 19:16:42 | 2007-01-19 17:00:10 | 2022-03-06 03:19:24.535662 | Unreviewed | closed | Validators | task | minor | invalid | Ordered objects should have API access to their order number | The specific problem is that photos within photo galleries need to know their place within the gallery (1st, 2nd, etc.). In order to solve this, we'll need ordered objects to give API access to their order number. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 11 | 2005-07-13 19:17:13 | 2007-07-03 23:03:30 | 2022-03-06 03:19:24.708876 | 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 | 2022-03-06 03:19:24.890200 | 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 | |||
| 13 | 2005-07-13 19:20:21 | 2011-09-08 05:35:18 | 2022-03-06 03:19:25.074830 | Accepted | closed | contrib.admin | New feature | Normal | dev | fixed | Related objects interface should be tighter (edit_inline) | The admin interface for related objects and the ordering interface need some tighter integration. Currently, anything that can be ordered goes in the right sidebar of the admin change form, with no relation to the actual input fields for those objects. The adding, removing, editing and ordering of related objects should be tied together in one part of the form. '''Specific areas for enhancement:''' * '''Adding related objects should be easier.''' Now you have to "save and continue" to get an extra set of fields to add a new related object. You should be able to click "add new object" to add another set of blank fields inline on the page. * '''Deleting related objects should be easier.''' Now you have to clear the "core fields" of a related object to delete it. You should be able to click "delete" to delete the object, or at least mark it for deletion when you click save on the main object. * '''Ordering of related objects should be clearly tied to editing those objects.''' Now the ordering interface is completely separate. You should be use the same list of objects to set the order (by dragging) or select that object for editing or deleting (by clicking). | barbuza | adrian | nfa-someday nfa-changelist | 0 | 1 | 1 | 0 | 0 | 0 |
| 14 | 2005-07-13 19:20:55 | 2008-01-14 18:07:24 | 2022-03-06 03:19:25.261243 | Accepted | closed | contrib.admin | defect | normal | wontfix | PIE-IN-THE-SKY: Add spell-check capability to admin textareas | It'd be nice if every textarea throughout our admin offered users the option to spell-check its contents. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 15 | 2005-07-13 19:22:11 | 2006-08-29 10:03:03 | 2022-03-06 03:19:25.461869 | Unreviewed | closed | Metasystem | defect | normal | duplicate | Metasystem unique_together doesn't work for an object that's related inline | See {{{unique_together}}} in {{{music.MusicianInBand}}}, which causes this when ManipulatorAdd is instantiated: {{{ Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/worldonline/cms/core/handler.py", line 123, in get_response return callback(request, **param_dict) File "/usr/lib/python2.3/site-packages/worldonline/cms/views/admin/main_new.py", line 608, in change_stage manipulator = mod.ChangeManipulator(object_id) File "/usr/lib/python2.3/site-packages/worldonline/cms/models/meta.py", line 77, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/lib/python2.3/site-packages/worldonline/cms/models/meta.py", line 1008, in manipulator_init self.fields.extend(f.get_manipulator_fields(rel_opts, self, name_prefix='%s.%d.' % (rel_opts.object_name.lower(), i), rel=True)) File "/usr/lib/python2.3/site-packages/worldonline/cms/models/meta.py", line 1279, in get_manipulator_fields params['validator_list'].append(getattr(manipulator, 'isUnique%sFor%s' % (i, j))) AttributeError: BandManipulatorChange instance has no attribute 'isUniquemusician_idForband_id' }}} | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 16 | 2005-07-13 19:24:03 | 2007-05-30 21:27:58 | 2022-03-06 03:19:25.856417 | Design decision needed | closed | contrib.admin | normal | invalid | Create some form of "edit many at once" feature for the admin | {{{ [5:54 pm] jacobkm: Hey, what do you think of making a general purpose CSV export/import for all admin pages? [5:54pm] jacobkm: A way for data entry folks to get lots of info in quickly? [5:56pm] django34: Sounds like a good idea...How would it handle many-to-one related objects? [5:56pm] jacobkm: I'm not sure, but probably just with IDs [5:56pm] jacobkm: Or maybe it wouldn't work if there are relations [5:57pm] django34: Do you have a use-case in mind? [5:57pm] jacobkm: Yeah -- Billy's been entering rosters/schedules/etc all day, and it's a PITA [5:58pm] jacobkm: I could write an excel importer for him, but it would take almost as long [5:58pm] django34: All of those things have related objects, don't they? [5:58pm] django34: I guess a roster doesn't, if it's just players [6:01pm] jacobkm: Well, it's got the team id [6:02pm] django34: But it doesn't have "many" of something else [6:02pm] jacobkm: I don't think any of them do... [6:03pm] django34: such as a team has many players [6:03pm] jacobkm: It could be an optional admin feature like the add as new thing [6:04pm] jacobkm: It's just that our admin isn't ideal when it comes to entering a *lot* of information. [6:04pm] django34: agreed [6:04pm] jacobkm: I think it would probably be dangerous, so we should be careful about who gets to use it [6:05pm] django34: There would be some usability issues, such as what to do if 5 records are submitted but one of them has an error in it [6:05pm] jacobkm: Yeah [6:05pm] jacobkm: I'd say all or nothing, probably. [6:06pm] django34: "There was an error in the 'player name' field in record #4" [6:06pm] django34: Not that bad [6:06pm] jacobkm: Right, exactly [6:06pm] jacobkm: (I did something like this for the CMS I build at IDSociety, except it had *no* error checking at all and was bascially a shortcut for me alone) [6:07pm] django34: I don't see a huge problem with adding this functionality to every admin item [6:07pm] jacobkm: How would it handle ManyToMany relations? [6:07pm] jacobkm: That's … | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 17 | 2005-07-13 19:25:18 | 2019-12-17 11:37:56 | 2022-03-06 03:19:26.110232 | Accepted | closed | Database layer (models, ORM) | New feature | Normal | dev | wontfix | Metasystem optimization: Share select_related in memory | When using {{{select_related}}}, each cache is stored separately in memory. For example, each Choice object here has its Poll cached, but each of those caches is a separate object in memory. It would require less memory if the caches were references to the same Poll object. {{{ >>> from djangomodels.polls import choices >>> choice_list = choices.get_list(poll__id__exact=90, select_related=True) >>> id(choice_list[0]._poll_cache) -156344020 >>> id(choice_list[1]._poll_cache) -156344084 }}} | PhiR | adrian | feature caching | 0 | 1 | 1 | 0 | 1 | 0 |
| 18 | 2005-07-13 19:26:27 | 2007-07-03 23:03:51 | 2022-03-06 03:19:27.157564 | 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 | ||
| 19 | 2005-07-13 19:31:17 | 2021-05-10 19:10:04 | 2022-03-06 03:19:27.337791 | Design decision needed | closed | Validators | enhancement | minor | new-admin | wontfix | Automatically generate JavaScript form validation | Django should generate JavaScript form validation for all admin pages, in addition to the server-side validation it already does. Each FormField object already gets an HTML class of the type of field it is (e.g. "vCheckboxField", "vEmailField", "vTextField"), so we can probably build off of that. OR, we could use {{{XMLHttpRequest}}} to send each field individually and validate everything *server-side*. ====================================================== I've given some more thought to this. We could set up a view that validates a given field via XMLHttpRequest, like this: admin.6newslawrence.com/validate_field/polls/polls/question/?value=blah (The "value=blah" would be POST data, not GET data.) But here's a problem: What do we do for validators that expect all_data, i.e. the ones that validate a field according to the value of another field? We could solve that by only using dynamic JavaScript? validation to check single fields and using server-side validation for the rest -- but it's a usability problem if some validation errors appear instantly and others appear after form submission. | adrian | adrian | validators | 0 | 0 | 0 | 0 | 0 | 0 |
| 20 | 2005-07-13 19:32:17 | 2007-07-03 23:03:44 | 2022-03-06 03:19:28.799681 | 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 | ||
| 21 | 2005-07-13 19:33:01 | 2007-05-30 21:29:52 | 2022-03-06 03:19:29.033864 | Design decision needed | closed | contrib.admin | enhancement | trivial | fixed | FileUploadField should allow for manual filename entry | FileUploadFields currently don't allow users to type in the name of an ''already-existing file'' -- the system forces them to upload a new file each time. There should be a way of designating a path/filename on the server. It'd be great if there was some sort of filesystem-browsing interface, like the one Urchin has for selecting log sources. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 22 | 2005-07-13 19:33:33 | 2008-10-06 03:46:01 | 2022-03-06 03:19:29.513777 | Unreviewed | closed | contrib.admin | defect | normal | duplicate | [patch] FileUploadField should allow for clearing the field | It's currently not possible to clear the value of a FileUploadField. | adrian | adrian | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 23 | 2005-07-13 19:34:33 | 2013-10-15 09:17:25 | 2022-03-06 03:19:30.445855 | Accepted | closed | Forms | New feature | Normal | wontfix | Add support for ValidationWarning | We've talked in the past about how useful it would be to let certain validators throw ValidationWarning instead of ValidationError. A ValidationWarning, when thrown, would still redisplay the admin form but display an additional checkbox above the field. If that checkbox is checked when the form is submitted, the error is ignored. The change would have to be made in django/core/formfields.py. | jgeskens | adrian | 0 | 1 | 1 | 0 | 1 | 1 | ||
| 24 | 2005-07-13 19:35:15 | 2008-08-21 16:09:48 | 2022-03-06 03:19:30.618279 | Design decision needed | closed | Metasystem | defect | normal | wontfix | edit_inline support for OneToOne relationships | An object should be able to edit a OneToOne related object inline on the original object's page. For example, users should be able to edit lawrence.com Restaurants on the Place admin screen. (Restaurants are a one-to-one extension of Places.) | nobody | adrian | subclassing | 0 | 0 | 0 | 0 | 0 | 0 | |
| 25 | 2005-07-13 19:35:54 | 2013-06-02 18:10:34 | 2022-03-06 03:19:30.770423 | Accepted | closed | contrib.admin | Bug | Normal | dev | fixed | Filtering interface on ForeignKey <select> boxes | Select boxes are a pain, and slow, to deal with when there are a lot of values to select from. (Example: datelines on news stories). There should be a generator option, use_filter_interface, available on select boxes. It would add an <input type="text"> next to the select box and allow users to filter the select box that way. This would make data entry quicker, because folks could just paste in the dateline they want, and it'd be selected for them (assuming it's been entered as a dateline in the system). | nobody | adrian | feature | 0 | 1 | 1 | 0 | 0 | 1 |
| 26 | 2005-07-13 19:36:46 | 2012-01-19 12:53:15 | 2022-03-06 03:19:30.935713 | Design decision needed | closed | contrib.admin | Uncategorized | minor | newforms-admin | wontfix | Admin validation errors cause FileUploadFields to be reset | Phil said: {{{ <pcauthon> if, say, the turnpike episode, event, etc admin kicks back with an error, you have to rebrowse to upload the pics. only really aggravating on turnpike episodes where there are 6 pics to browse for }}} JavaScript form validation could be a clean fix for this. | nobody | adrian | nfa-someday | 0 | 0 | 0 | 0 | 0 | 0 |
| 27 | 2005-07-13 19:40:29 | 2014-06-08 07:20:52 | 2022-03-06 03:19:31.121463 | Someday/Maybe | closed | Forms | New feature | Normal | worksforme | Single form field for multiple database fields | Some admin interfaces would benefit from being able to have multiple fields' worth of data entered in a single field. For example, a field for a sports stat could be entered into a single field as "XX-YY-ZZ", whereas the three values are actually three separate fields in the DB. Relevant conversation: {{{ <jacobkm> Well, I'm using those aggregate fields for stats where you type something like "3-17" and it gets split into multiple fields. I see there's a CommaSeperatedIntegerField in formfields which would work for this, but there needs to be a way in the datadescriptions to say "this group of fields should be presented as a single field" <django34> The DD will have to provide a format string of some sort <jacobkm> Easy enough <jacobkm> are you thinking of a % format string or a regex? <django34> Not sure... <django34> Probably just % <django34> fields_together = '%(last_name)s, %(first_name)s' }}} | nobody | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 28 | 2005-07-13 19:41:08 | 2007-07-17 21:49:58 | 2022-03-06 03:19:31.290643 | Accepted | closed | Metasystem | enhancement | normal | duplicate | Delete confirmation should have "replace relationships" shortcut | This is best explained with an example. Right now, when I click to delete a duplicate dateline, I get a list of all the news stories that feature that dateline. So I click on each story to change its dateline to the correct (non-duplicate) dateline, because if I didn't do that, deleting the dateline would delete all those stories. Then, once I've changed all the stories, I can delete the dateline safely, because it won't have any relationships. What I want is the delete-confirmation page for datelines -- and everything else -- to offer a "convert all of these stories' datelines to the following *different* dateline" select box. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 29 | 2005-07-13 19:43:02 | 2015-11-07 09:54:25 | 2022-03-06 03:19:31.418555 | Someday/Maybe | closed | contrib.admin | Bug | Normal | dev | wontfix | Fix usability issue with limit_choices_to and "Add another" in admin | {{{ django34: We have the ability to put a customized limit/filter on which related objects get displayed in select boxes. For instance, the "photographer" field on the "Add photo" form only displays the "Staff members" that have shoots_photos=True. django34: This results in some usability problems, though, because if a producer doesn't see a person's name in the list, he might click "Add another..." instead of checking to make sure the person isn't in "Staff members" and doesn't have "shoots_photos" checked. django34: Does this make sense? wilson: kind of wilson: what page would that case appear on django34: Here's an example... django34: The "Photographer" select box includes *only* the staff members that have shoots_photos=True. django34: So if a producer doesn't see a photographer in there, he might click "Add another...", which would create an entirely new staff member. But it might be the case that the staff member DOES exist, just doesn't have shoots_photos=True checked. wilson: if the staff member did exist, would it let them add them again? django34: Yes, as long as the slug was different. django34: The only way I can think of to fix this would be to have some sort of "Showing only photographers [Show all staff members]" link. Or to eliminate the filtering altogether. wilson: i was going to suggest a "show all staff" link wilson: yes, that is my suggestion wilson: "show all staff" link next to the select wilson: then "show photographers only" when the filter is off django34: All right. }}} | nobody | adrian | 0 | 0 | 0 | 0 | 0 | 1 | |
| 30 | 2005-07-13 22:12:36 | 2007-07-03 23:04:02 | 2022-03-06 03:19:31.569913 | 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 | |
| 31 | 2005-07-15 13:09:24 | 2007-10-03 00:37:21 | 2022-03-06 03:19:31.719348 | Ready for checkin | closed | Documentation | defect | trivial | fixed | Spelling corrections from Template Guide page. | There are a few spelling errors on http://www.djangoproject.com/documentation/templates/ : 1. Under "What's a Variable?" the last sentence in the first paragraph has "be replaces with" and should have "be replaced with". 2. Under "What's a Filter?" the second sentence in the first paragraph has "This display the" and should be "This displays the". | jacob | shalofin@gmail.com | nitpick | 0 | 0 | 0 | 0 | 0 | 0 | |
| 32 | 2005-07-15 14:35:30 | 2007-07-03 23:03:51 | 2022-03-06 03:19:31.860139 | 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 | 2022-03-06 03:19:32.011351 | 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 | |
| 34 | 2005-07-16 11:28:55 | 2005-07-16 12:05:30 | 2022-03-06 03:19:32.197738 | Unreviewed | closed | Core (Other) | defect | normal | fixed | Tutorial Import and Attribute errors while using MySQL. | I'm following the tutorial using Windows2k, MySQL 4.1 and Python 2.4.1. I've passed thru the installation phase, directory structure creation and database table creation withou problems, but i'm getting strange errors when i try to exec command described in "Playing with the API". a little note, i guess that the "export" command in the tutorial must be replaced with a "set" on windows: {{{ set DJANGO_SETTINGS_MODULE=myproject.settings.main }}} Here's the first traceback i have: {{{ >>> from django.models.polls import polls, choices Traceback (most recent call last): File "<stdin>", line 1, in ? File "C:\Data\Dev\myproject\apps\polls\models\polls.py", line 1, in ? from django.core import meta File "C:\Python\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\meta.py", line 2, in ? from django.core import db File "C:\Python\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:\Python\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\db\backen ds\postgresql.py", line 8, in ? import psycopg as Database ImportError: No module named psycopg >>> ^Z }}} the system seems to ignore the settings specified in the main.py (although they was correctly used in the table creation pahse). hacking the Django global_settings.py file and set DATABASE_ENGINE key to "mysql" makes me skipt that error, but i've got another one: {{{ >>> from django.models.polls import polls, choices Traceback (most recent call last): File "<stdin>", line 1, in ? File "C:\Python\Lib\site-packages\django-1.0.0-py2.4.egg\django\models\__in _.py", line 8, in ? for mod in meta.get_installed_models(): File "C:\Python\Lib\site-packages\django-1.0.0-py2.4.egg\django\core\meta.p line 76, in get_installed_models for a in settings.INSTALLED_APPS: AttributeError: 'module' object has no attribute 'INSTALLED_APPS' }}} Now i'm stuck. ;( | adrian | deelan | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 35 | 2005-07-16 12:15:35 | 2007-07-03 23:03:50 | 2022-03-06 03:19:32.361893 | 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 | |
| 36 | 2005-07-16 12:17:46 | 2007-07-17 21:19:58 | 2022-03-06 03:19:32.501188 | Design decision needed | closed | Core (Other) | defect | normal | 1.0 | invalid | how do I config the apache+mod_python? | hi, I have successfully created the project and app as the tutorial wrote. but i can not make it work under the apache+mod_python. I put the block {{{ <Directory "d:/myproject/django/trunk"> AddHandler mod_python .py PythonHandler django.core.handler PythonDebug On </Directory> }}} in httpd.conf, so i can use url:'http://localhost:8080/a.py' to call the handler. however , how can i use url:'http://localhost:8080/2005/12/35678' to read an article? wait the answer , thanks. | adrian | james | web server | 0 | 0 | 0 | 0 | 0 | 0 |
| 37 | 2005-07-16 12:45:48 | 2007-07-03 23:03:23 | 2022-03-06 03:19:32.645139 | 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 | 2022-03-06 03:19:32.801848 | 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 | 2022-03-06 03:19:32.951816 | 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 | ||
| 40 | 2005-07-17 01:32:23 | 2006-10-22 16:14:52 | 2022-03-06 03:19:33.109198 | Unreviewed | closed | Database layer (models, ORM) | defect | major | fixed | Attempt to set a many to many relation throws exception unless model specifies ordering. | I've got two basic models, with a ManyToManyField connecting them. An exception is thrown while trying to set the relation: {{{ class Foo(meta.Model) fields = ( meta.CharField('name', 'name', maxlength=100), ) class Bar(meta.Model) fields = ( meta.CharField('name', 'name', maxlength=100), meta.ManyToManyField(Foo), ) >>> f = foos.get_object(id__exact=1) >>> b = bars.get_object(id__exact=1) >>> f.set_bars((b.id,)) Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/meta.py", line 57, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/meta.py", line 897, in method_set_related_many_to_many if rel_field.rel.orderable: AttributeError: ManyToMany instance has no attribute 'orderable' }}} If I add an "ordering = (('name', 'ASC'),)" to Bar then it works as expected. The relation should work even without specifying an ordering, however orderable does not seem to be set at all unless I explicitly add ordering to the model. | adrian | jforeman@hark.org | ManyToMany | 0 | 0 | 0 | 0 | 0 | 0 | |
| 41 | 2005-07-17 03:46:55 | 2007-07-03 23:03:22 | 2022-03-06 03:19:33.293160 | 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 | ||
| 42 | 2005-07-17 05:47:13 | 2006-10-14 14:31:41 | 2022-03-06 03:19:33.463570 | Unreviewed | closed | Database layer (models, ORM) | defect | normal | fixed | OneToOneField missing from DATA_TYPES dict | revision 138 on trunk is missing entries for OneToOneField fields, and so sql generation fails if you have such a field in one of your models. below is a simple patch to add it to the backends. {{{ Index: django/core/db/backends/postgresql.py =================================================================== --- django/core/db/backends/postgresql.py (revision 134) +++ django/core/db/backends/postgresql.py (working copy) @@ -105,6 +105,7 @@ 'IPAddressField': 'inet', 'ManyToManyField': None, 'NullBooleanField': 'boolean', + 'OneToOneField': None, 'PhoneNumberField': 'varchar(20)', 'PositiveIntegerField': 'integer CHECK (%(name)s >= 0)', 'PositiveSmallIntegerField': 'smallint CHECK (%(name)s >= 0)', Index: django/core/db/backends/mysql.py =================================================================== --- django/core/db/backends/mysql.py (revision 134) +++ django/core/db/backends/mysql.py (working copy) @@ -95,6 +95,7 @@ 'IPAddressField': 'char(15)', 'ManyToManyField': None, 'NullBooleanField': 'bool', + 'OneToOneField': None, 'PhoneNumberField': 'varchar(20)', 'PositiveIntegerField': 'integer UNSIGNED', 'PositiveSmallIntegerField': 'smallint UNSIGNED', }}} the patch fixes sql generation for simple cases such as: {{{ class Piece(meta.Model): fields = ( meta.CharField('title', 'title', maxlength=256), meta.DateTimeField('publishDate', 'date published'), meta.ManyToManyField(Category), ) class ImagePiece(meta.Model): fields = ( meta.OneToOneField(Piece), meta.FileField('data', 'data', upload_to='pieces'), ) }}} but more complicated models haven't been tested. | adrian | nullstyle@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 43 | 2005-07-17 07:01:40 | 2007-07-03 23:03:29 | 2022-03-06 03:19:33.614661 | 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 | 2022-03-06 03:19:33.781615 | 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 | 2022-03-06 03:19:33.946561 | 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 | ||
| 46 | 2005-07-17 15:44:25 | 2006-10-07 22:22:38 | 2022-03-06 03:19:34.112500 | Unreviewed | closed | contrib.admin | defect | normal | fixed | Refactor DATE_TRUNC() and EXTRACT() database code for MySQL | It's a Windows XP SP 2, Apache 2.0.54, Python 2.41, Mod_python 3.14, MySQL 4 setup. You can reproduce the bug in several cases. One of them is to click the filters in the Users page. Also ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''month' FROM polls_polls.pub_date) = '7' AND polls_polls.pub_date BETWEEN '2005-' at line 1") Another example would be using date_hierarchy = 'pub_date', to get ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '('year', polls_polls.pub_date) FROM polls_polls GROUP BY 1 ORDER BY 1 ASC' at line 1") | adrian | Umair | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 47 | 2005-07-17 15:53:38 | 2007-07-03 23:03:42 | 2022-03-06 03:19:34.257492 | 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 | ||
| 48 | 2005-07-17 16:11:23 | 2007-07-21 14:43:57 | 2022-03-06 03:19:34.417240 | Accepted | closed | Database layer (models, ORM) | defect | normal | fixed | Unit tests for MySQL support | Since more people are going to be using MySQL than PostgreSQL, but the MySQL support is new and mostly untested, let's build up a comprehensive set of unit tests for the MySQL stuff. We might even be able to share them with other database backends. This would make it much easier to add sqlite support (for example) later on. | adrian | Simon Willison | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 49 | 2005-07-17 17:45:42 | 2007-07-03 23:03:32 | 2022-03-06 03:19:34.565641 | 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 | 2022-03-06 03:19:34.717632 | 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 | 2022-03-06 03:19:34.866064 | 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 | |
| 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 1 | 0 | 0 | 0 | 0 |
| 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 | 0 | 0 | 0 | 0 | 0 | ||
| 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 1 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 0 | ||
| 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 | 0 | 0 | 0 | 0 | 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 | 0 | 1 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 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 | 0 | 0 | 0 | 0 | 0 | ||
| 78 | 2005-07-19 00:51:50 | 2006-10-15 20:17:46 | 2022-03-06 03:19:39.189327 | Unreviewed | closed | Tools | enhancement | normal | fixed | Add a test suite for core functionality | Congratulations on the (slightly earlier than expected) launch of Django. It looks very cool, and the site is nicely put together. Just what Python needs. On initial evaluation I was surprised to find almost no test code. There are a few tests in one package, but no comprehensive unit test suite. Automated testing seems particularly important for the fiddly bits of code like your database caching system. It's also really valuable to have unit tests in an open source project; you're much less likely to get broken code if you require the tests pass. Adding unit tests after the fact feels like a lot of work, but the earlier you get a good test framework in place the easier it will be. And the sooner it pays off. Thanks for listening to my suggestion! Nelson | adrian | nelson@monkey.org | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 79 | 2005-07-19 02:27:56 | 2007-07-03 23:03:51 | 2022-03-06 03:19:39.339636 | 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 | ||
| 80 | 2005-07-19 05:32:08 | 2005-07-19 17:36:30 | 2022-03-06 03:19:39.487275 | Unreviewed | closed | contrib.admin | defect | critical | worksforme | Browsing to http://127.0.0.1:8000 fails when running django-admin.py runserver | Following the tutorial 2 instructions to run django-admin.py runserver causes the following to be shown in the browser: There's been an error: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 184, in get_response callback, param_dict = resolver.resolve(path) File "/usr/lib/python2.4/site-packages/django/core/urlresolvers.py", line 85, in resolve raise Http404, app_path Http404 This occurs on a Ubuntu 5.04 system running Python 2.4.1, Django SVN version 193. | adrian | pkropf@gmail.com | 0 | 0 | 0 | 0 | ||||
| 81 | 2005-07-19 06:38:29 | 2007-01-17 22:12:17 | 2022-03-06 03:19:39.671244 | Unreviewed | closed | contrib.admin | defect | major | fixed | Setting primary_key=True on an non-integer field isn't yet supported | The admin interface appears to want to keep the primary_key numerical, and so breaks if you have set a field as primary_key=True. Model: {{{ class Airfield(meta.Model): fields = ( meta.CharField('code', 'airfield code', maxlength=4, primary_key=True), meta.CharField('name', 'name', maxlength=50), ) admin = meta.Admin( fields = ( (None, {'fields': ('code', 'name')}), ), ) def __repr__(self): return self.name }}} Result from trying to add an item through the admin interface: {{{ There's been an error: Traceback (most recent call last): File "/sw/lib/python2.3/site-packages/django/core/handlers/wsgi.py", line 190, in get_response return callback(request, **param_dict) File "/sw/lib/python2.3/site-packages/django/views/admin/main.py", line 769, in add_stage log.log_action(request.user.id, opts.get_content_type_id(), getattr(new_object, opts.pk.name), repr(new_object), log.ADDITION) File "/sw/lib/python2.3/site-packages/django/models/auth.py", line 293, in _module_log_action e.save() File "/sw/lib/python2.3/site-packages/django/core/meta.py", line 57, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/sw/lib/python2.3/site-packages/django/core/meta.py", line 748, in method_save (opts.db_table, ','.join(field_names), ','.join(placeholders)), db_values) File "/sw/lib/python2.3/site-packages/django/core/db/base.py", line 10, in execute result = self.cursor.execute(sql, params) ProgrammingError: ERROR: invalid input syntax for integer: "EGKR" INSERT INTO auth_admin_log (action_time,user_id,content_type_id,object_id,object_repr,action_flag,change_message) VALUES ('2005-07-19 01:31:40',1,17,'EGKR','Redhill',1,'') }}} | adrian | jmb@atuin.co.uk | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 82 | 2005-07-19 06:59:18 | 2007-07-03 23:03:59 | 2022-03-06 03:19:39.839173 | 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 | ||
| 83 | 2005-07-19 11:02:41 | 2005-07-19 14:44:38 | 2022-03-06 03:19:40.255427 | Unreviewed | closed | Core (Other) | defect | trivial | fixed | Spelling error in Environment not found exception | {{{File "/usr/lib/python2.4/site-packages/django/conf/settings.py", line 25, in ? raise EnvironmentError, "Environemnt variable DJANGO_SETTINGS_MODULE is undefined."}}} --- Environenmt. | adrian | Manuzhai <mail@manuzhai.nl> | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 84 | 2005-07-19 13:06:51 | 2006-10-16 15:33:56 | 2022-03-06 03:19:40.498117 | Unreviewed | closed | Database layer (models, ORM) | defect | major | fixed | Foreign keys don't work in MySQL | Django generates: post_id mediumint(9) unsigned auto_increment NOT NULL REFERENCES posts_posts (slug) This doesn't work. In MySQL, only one column can have auto_increment, and that same column has to be the PRIMARY KEY. I think there should be a separate DATATYPE for ForeignKeys (it seems to just reuse the AutoField). | adrian | Manuzhai | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 85 | 2005-07-19 13:47:36 | 2007-01-17 22:12:17 | 2022-03-06 03:19:40.679016 | Unreviewed | closed | contrib.admin | defect | normal | worksforme | Admin login doesn't work with Konqueror | Logging into admin interface does not work for konqueror, but works for firefox. The console output of django-admin.py runserver: localhost.localdomain - - [19/Jul/2005 08:44:24] "POST /admin/ HTTP/1.1" 302 0 localhost.localdomain - - [19/Jul/2005 08:44:24] "GET /admin/ HTTP/1.1" 200 1638 The login time gets updated in database, but konqueror returns to login page. svn revision 201, Konqueror 3.4.1 | adrian | hruske@kiberpipa.org | konqueror admin | 0 | 0 | 0 | 0 | 0 | 0 | |
| 86 | 2005-07-19 15:37:19 | 2006-10-22 16:17:36 | 2022-03-06 03:19:40.838369 | Unreviewed | closed | Core (Other) | defect | normal | invalid | Custom External TemplateTag module | I know that you can add template tags to a project by placing them in an apps' TemplateTag module, but is it possible to add an external TemplateTag module to a project. I'm currently working on an Ajax middleware for Django and I'd like to create a templatetag to load the javascript libraries needed. I don't want to make the users put the custom template tag library into the django.templatetags module because that would be messing with the djangocore. Maybe allow the user to specify a tuple called EXTERNAL_TEMPLATETAG_MODULES in the settings module. Thanks | adrian | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 87 | 2005-07-19 16:39:52 | 2007-01-17 22:12:17 | 2022-03-06 03:19:41.019035 | Unreviewed | closed | Database layer (models, ORM) | enhancement | normal | duplicate | [patch] Oracle database support | Here's a patch for Oracle support. | adrian | jrhuggins@thoughtworks.com | oracle database db sequence | 1 | 0 | 0 | 0 | |||
| 88 | 2005-07-19 16:57:51 | 2007-07-03 23:03:29 | 2022-03-06 03:19:41.163208 | 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 | ||
| 89 | 2005-07-19 18:06:39 | 2006-04-23 22:52:28 | 2022-03-06 03:19:41.329410 | Unreviewed | closed | contrib.admin | defect | minor | 1.1 | fixed | DateTimeFields with auto_now_add = True in admin | Expose a DateTimeField with auto_now_add = True to the admin, try to add a new object. You can see the date field with empty values (no calendar, etc). Save the object, you'll get a validation error. Example model: {{{ class Article(meta.Model): fields = ( meta.CharField('title', 'title', maxlength=200, core=True), meta.TextField('data','data'), meta.DateTimeField('date','date',auto_now_add=True), ) admin = meta.Admin( fields = ( (None, {'fields': ('title', 'date','data',)}), ), ) }}} If i un-expose the 'date' field from admin, everything works fine. | adrian | philippe.normand@gmail.com | date | 0 | 0 | 0 | 0 | 0 | 0 |
| 90 | 2005-07-19 20:12:48 | 2007-07-03 23:03:41 | 2022-03-06 03:19:41.483591 | 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 | 2022-03-06 03:19:41.637006 | 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 | 2022-03-06 03:19:41.790772 | 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 | ||
| 93 | 2005-07-19 22:43:48 | 2007-03-26 21:39:52 | 2022-03-06 03:19:41.901224 | Design decision needed | closed | Tools | defect | major | fixed | django-admin startproject can create invalid settings/admin.py on windows | Following part 2 of the tutorial, I get the following error when trying to view /admin/: There's been an error: Traceback (most recent call last): File "C:\play\python\django\trunk\django\core\handlers\wsgi.py", line 187, in get_response response = middleware_method(request, callback, param_dict) File "C:\play\python\django\trunk\django\middleware\admin.py", line 46, in process_view return self.display_login_form(request, message) File "C:\play\python\django\trunk\django\middleware\admin.py", line 91, in display_login_form t = template_loader.get_template(self.get_login_template_name()) File "C:\play\python\django\trunk\django\core\template_loader.py", line 13, in get_template return get_template_from_string(load_template_source(template_name)) File "C:\play\python\django\trunk\django\core\template_file.py", line 22, in load_template_source raise TemplateDoesNotExist, error_msg TemplateDoesNotExist: Tried ['C:\\play\\python\\django\trunk\\django/conf/admin_templates\\login.html'] The \t in django\trunk is a tab character. This is coming from the settings/admin.py file created by django-admin startproject. At line 349 in django-admin.py, where it is populating the TEMPLATE_DIRS setting, the %r format specifier should be used to ensure that the path is rendered correctly into the file, and r needs to be put in the string before it to ensure that it is interpreted as a raw string. So line 349 should be: settings_contents = re.sub(r'(?s)\b(TEMPLATE_DIRS\s*=\s*\()(.*?)\)', "\\1\n r%r,\\2)" % ADMIN_TEMPLATE_DIR, settings_contents) | adrian | xtian@toysinabag.com | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 94 | 2005-07-19 23:26:58 | 2007-07-03 23:03:40 | 2022-03-06 03:19:42.023629 | 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 | 2022-03-06 03:19:42.133120 | 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 | 2022-03-06 03:19:42.268275 | 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 | |||
| 97 | 2005-07-20 00:13:39 | 2005-07-20 15:14:00 | 2022-03-06 03:19:42.450355 | Unreviewed | closed | Core (Other) | defect | normal | fixed | Refactor django-admin.py so it only contains command-line interface code | Move the bulk of django-admin.py into something like django/core/management.py, for code cleanliness and so other code can import from django.core.management. | adrian | adrian | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 98 | 2005-07-20 00:28:49 | 2007-07-03 23:04:10 | 2022-03-06 03:19:42.698394 | 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 | 2022-03-06 03:19:43.264801 | 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 | 2022-03-06 03:19:44.511817 | 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 | ||
| 101 | 2005-07-20 01:28:53 | 2006-08-29 10:50:06 | 2022-03-06 03:19:45.011425 | Unreviewed | closed | Core (Management commands) | enhancement | normal | wontfix | Add functionality to django-admin to create skeleton views | You should be able to do something like {{{django-admin.py createview APPNAME VIEWNAME method1 method2 ...}}} and having {{{apps/APPNAME/views/VIEWNAME.py}}} created and filled with some sensible template (eg., comments on how to create methods, etc.) With a bit of work, it could be possible even modifying {{{apps/APPNAME/urls/APPNAME.py}}} to point to the new methods. See the attached patch. | adrian | ricardo@conysis.com | 0 | 0 | 0 | 0 | 0 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE tickets (
id int primary key,
created datetime,
changetime datetime,
last_pulled_from_trac datetime,
stage text,
status text,
component text,
type text,
severity text,
version text,
resolution text,
summary text,
description text,
owner text,
reporter text,
keywords text,
easy boolean,
has_patch boolean,
needs_better_patch boolean,
needs_tests boolean,
needs_docs boolean,
ui_ux boolean
);