61 rows where "changetime" is on date 2007-12-01

View and edit SQL

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

changetime (date)

  • 2007-12-01 · 61
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
921 2005-11-26 14:13:22 2007-12-01 18:53:00 2019-06-24 00:25:04.992520 Design decision needed closed contrib.admin enhancement trivial newforms-admin wontfix Add a "me" shortcut to UserFields In the admin, when I have a UserField, it would be nice to have a shortcut to "me", kind of like how dates have shortcuts to "now", that would automatically fill in the current user, wich means I don't have to go through the (sometimes) long list of users. hakejam ozamosi@blinkenlights.se   0 0 0 0 0 0
2858 2006-10-02 16:35:52 2007-12-01 13:51:11 2019-06-24 00:45:37.906548 Design decision needed closed Core (Other) enhancement normal master wontfix [patch] Better default value for SERVER_EMAIL Neither ''mail_managers()'' nor ''mail_admins()'' allow you to specify the address from which their email should be sent, but instead use the value of SERVER_EMAIL from the settings file. This is fine, but the default is 'root@localhost'. Some MTAs (such as Postfix) will automatically append a domain suffix to this, as it knows that 'localhost' won't resolve on the Internet and it tries to convert it into a fully qualified hostname (e.g. 'root@localhost' would become 'root@localhost.example.com'). As such a hostname will not usually exist, some email servers will reject messages from this sender as it assumes that it is a spoofed address. Obviously, an easy solution is just to define SERVER_EMAIL to something sensible in your settings file! However, should you neglect (or forget) do do this, it would be nice if Django had a default value that was more likely to be a real email address. The attached patch defines this variable using the machine's hostname. A similar issue exists with DEFAULT_FROM_EMAIL, which the patch also addresses. nobody Fraser Nevett <mail@nevett.org>   0 1 0 0 0 0
2859 2006-10-02 17:16:24 2007-12-01 13:52:21 2019-06-24 00:45:38.528967 Design decision needed closed Generic views enhancement normal master wontfix Extend generic update view to accept a optional query set It would be a nice addition to extend the update_opject view to accept a optional query_set parameter. If this parameter is present the object to update is selected from this query set. This can be useful if you want to change an object via a slug but the slug is not a unique identifier. In this case you can create a query_set with for pre-selecting the valid entries. nobody Indy   0 1 0 0 0 0
3116 2006-12-08 18:22:20 2007-12-01 17:04:08 2019-06-24 00:48:27.459139 Design decision needed closed django-admin.py inspectdb enhancement normal   wontfix [multi-db] inspectdb should inspect OTHER_DATABASES Currently to analyze all of my legacy databases, I have to modify the main database in settings.py to one database at a time ( python manage.py inspectdb > somefile.py ) ... then copy that somefile.py file to the correct directory that corresponds to the MODEL entry for that database under OTHER_DATABASES. For this branch, it seems to me that the behavior for inspectdb should be as follows: 1. Inspects main database and outputs code to models.py 2. For each item in OTHER_DATABASES, inspect that table, and create a models.py file in the directory that corresponds to the MODEL entry for that database. nobody carole.zieler@gmail.com   0 0 0 0 0 0
3356 2007-01-23 19:59:56 2007-12-01 14:15:48 2019-06-24 00:50:59.898660 Design decision needed closed Generic views     master wontfix Ability to turn off new message in the Message framework when using create/edit/delete generic view It would be great if Django provided a parameter to disable creating a new message when using create/update/delete generic view. It would be enabled by default. Something like: def delete_object(request, model, post_delete_redirect ...., create_info_message=True) ... if request.user.is_authenticated() and create_info_message: request.user.message_set.create(message=gettext("The %(verbose_name)s was deleted.") % {"verbose_name": model._meta.verbose_name}) return HttpResponseRedirect(post_delete_redirect) nobody anonymous generic views, message 0 0 0 0 0 0
3382 2007-01-28 23:17:07 2007-12-01 14:20:55 2019-06-24 00:51:16.202343 Design decision needed closed Database layer (models, ORM)     master wontfix FloatField values get rounded on save() Django uses the %s format code to insert FloatField values into SQL command strings to send to the database. However, the %s format code rounds floating point numbers to 12 significant digits, which may cause unexpected rounding when the FloatField is configured to store more than 12 digits. I would have expected Django to use the '%.xf' format code, where x = decimal_places specified for the FloatField in the model definition, which would prevent rounding when saving to the database. nobody rfugger at gmail dot com float rounding 0 0 0 0 0 0
3445 2007-02-06 21:52:31 2007-12-01 17:44:53 2019-06-24 00:51:56.044457 Design decision needed closed Core (Other)     master wontfix all caching-related code should be collected into its own cache application There are various modules related to caching spread throughout the django tree. They should be collected into a "cache" package/application. nobody Gary Wilson <gary.wilson@gmail.com>   0 1 0 0 0 0
3462 2007-02-08 20:44:56 2007-12-01 17:14:26 2019-06-24 00:52:06.718248 Design decision needed closed Generic views     master wontfix model objects can fail during save Currently django uses an existence test (at least on postgresql_psycopg2 backend, but I assume it does the same thing everywhere) before and INSERT or UPDATE to decide which to do. This can fail if another connection does an INSERT or a DELETE while the existence test is running, even in a transaction block (unless the transaction isolation level is serializable) as each statement can potentially see a different view of the database depending on which transactions have already completed before that statement executes. I'm not sure how to fix this (serializable transactions are probably not the right answer), and it is probably an edge case for most applications, but I'm entered a bug for it so that people know this issue exists. nobody Jack Moffitt <metajack@gmail.com>   0 0 0 0 0 0
3474 2007-02-11 06:47:05 2007-12-01 17:49:41 2019-06-24 00:52:14.309459 Design decision needed closed Core (Other)     master wontfix Allow regex flags to be specified in url dispatcher It would be nice if the URL dispatcher allowed REs with the re.VERBOSE flag set so that we can set out our REs using triple-quoted, commented strings containing formatting whitespace. It probably even makes sense to have it on by default, as with URLs it's pretty unlikely they'll include meaningful intentional whitespace anyway. I think it would make my RE debugging taks much easier. Thanks. nobody admackin@gmail.com url re verbose flags 0 1 0 0 0 0
3475 2007-02-11 14:29:41 2007-12-01 17:55:19 2019-06-24 00:52:14.952778 Design decision needed closed Core (Management commands)     master wontfix Creating apps with certain names causes manage.py to stop working manage.py should not allow creating an app with a certain name when that could break manage.py itself. after doing ''manage.py startapp site'' I got the following error when trying to do something with manage.py {{{ Traceback (most recent call last): File "path\manage.py", line 2, in ? from django.core.management import execute_manager ImportError: No module named django.core.management }}} nobody svant manage.py, startapp 0 1 0 0 0 0
3482 2007-02-12 12:40:19 2007-12-01 23:43:02 2019-06-24 00:52:19.375164 Ready for checkin closed Forms     master fixed MultipleChoiceField validation against a list with a single null element MultipleChoiceField fails validation when required=False against a list with a single null value (as opposed to when value itself is null) {{{ >>> f = MultipleChoiceField(required=False, choices=[('1', '1'), ('2', '2')]) >>> f.clean(['']) Traceback (most recent call last): File "<stdin>", line 1, in ? File "django/newforms/fields.py", line 386, in clean if val not in valid_values: django.newforms.util.ValidationError: [u'Select a valid choice. is not one of the available choices.'] >>> }}} nobody Jeff Bauer <jbauer@rubic.com> MultipleChoiceField 0 1 0 0 0 0
3483 2007-02-12 15:04:59 2007-12-01 20:45:05 2019-06-24 00:52:19.991108 Accepted closed Documentation     master fixed Document AUTH_PROFILE_MODULE The AUTH_PROFILE_MODULE isn't documented, the whole "Profile" support is undocumented except for a small reference to the 'get_profile' method in [source:django/trunk/docs/authentication.txt authentication docs] maybe it should be documented somewhere, the best source of information I could find about it is [http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model this b-list post], there is also [wiki:ExtendedUserModel this] wiki page which should be updated to reflect this new setting maybe with a note to the documentation if it gets added. On the code you can get a few more information: [source:django/trunk/django/contrib/auth/models.py here] nobody Marc Fargas <telenieko@telenieko.com>   0 1 0 0 0 0
3520 2007-02-18 13:18:44 2007-12-01 18:47:59 2019-06-24 00:52:43.453716 Design decision needed closed Database layer (models, ORM)     master wontfix [patch] New search_filter for default manager Simple convenience method to run filter() using field lookups and values from supplied dicts. {{{ mysearch = {'myfield': 'myfield', 'mytext': 'mytext__startswith', 'mydate': 'mydata__lte', } formdata = {'myfield': 'somevalue', 'mytext': 'h', 'mydate': '' } results = MyObject.objects.search_filter(lookups=mysearch, data=formdata) }}} Would be exactly the same as -- {{{ filter(myfield='somevalue', mytext__startswith='h') }}} Skips empty values. Useful for searching against form or request data. nobody Simon Litchfield <simon@slicmedia.com> search form filter request post get field lookup dict 0 0 0 0 0 0
3548 2007-02-22 01:55:03 2007-12-01 19:46:14 2019-06-24 00:53:00.822319 Design decision needed closed Database layer (models, ORM)     master wontfix add a direct mapping when using ForeignKey fields with unique=True in place of the deprecated OneToOneField OneToOneField sets up a direct mapping to the related object in the ORM, e.g. when relating Profile in your app to User in contrib.auth, you can access the profile with u.profile. as OneToOneField has a few issues and is likely going away soon, could we change ForeignKey to add a similar user friendly mapping when unique=True is specified, to save having to do something like u.profile_set.all()[0]. when only using one model to extend User, you can use the AUTH_PROFILE_MODULE setting and the User.get_profile() method, but this is specific to User, and indicates the extending model is a "profile", and can only be used with one extension of a model. for example, it may be possible to have multiple apps within a project, which all share common users, but each has specific extensions of User specific to their purpose. it's also possible to want to extend other models besides User with a OneToOne relation. in those cases, the direct mapping above would come in handy. e.g. u.blog_profile, u.intranet_profile, etc. nobody mrmachine <real dot human at mrmachine dot net> 121-rewrite 0 0 0 0 0 0
3559 2007-02-24 01:54:38 2007-12-01 19:25:48 2019-06-24 00:53:07.721317 Design decision needed closed Documentation     master wontfix Should have official simple AJAX documentation I've seen all the reasons why Django doesn't have a plug-n-play javascript framework, and agree. However, this appears to give Django some sort of anti-javascript/AJAX reputation and drives people away from Django (see e.g. [http://www.b-list.org/weblog/2007/02/23/pycon-2007-web-frameworks-panel "does Django have an AJAX plan?"]). Given that this sort of thing is a web2.0ey buzzword, I can see this being used as a deciding factor in Dilbert-esque management meetings. Whilst there are good reasons not to tie into a specific framework (e.g. [http://www.b-list.org/weblog/2006/07/02/django-and-ajax Ubernostrums infamous post]), there is [http://www.djangoproject.com/documentation/serialization/ plenty] that Django does to make it easy to do AJAX-y things. This should be documented fairly briefly, but *prominently* to correct these misconceptions, and can incorporate info from/link to the many wiki pages (e.g. [http://code.djangoproject.com/wiki/XML-RPC XML-RPC]) or blog posts (e.g. [http://www.b-list.org/weblog/2006/07/31/django-tips-simple-ajax-example-part-1 another b-list post]) where people can find more information. nobody Simon G. <dev@simon.net.nz>   0 0 0 0 0 0
3568 2007-02-24 21:47:01 2007-12-01 23:24:55 2019-06-24 00:53:13.317799 Design decision needed closed Forms     master wontfix Add support for serializing newforms to HTML Currently, newforms only serializes to suit W3C's often-criticized Guidelines for serving XHTML 1.0 as text/html to buggy user agents. Its markup is not conformant with the HTML 4.01 specification, because according to HTML's SGML definition <input /> means <input>&gt; not <input>. My patch leaves the status quo as the default, but facilitates producing conformant HTML by adding an optional argument to the serialization methods. as_p(forms.SERIALIZATION_HTML401) for example. If there's a better way to achieve the same thing, that would be good too. It would also be nice to be able to set SERIALIZATION_DEFAULT app-wide, but I'm not sure how that's done. It may be that an end_empty_element() function would be useful elsewhere in Django too. nobody Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> newforms html xhtml 0 1 1 0 0 0
3580 2007-02-26 15:18:22 2007-12-01 23:32:40 2019-06-24 00:53:20.863395 Design decision needed closed Generic views     master wontfix Contribution: generic view for serialized queryset As I posted on django-developers, something like this could be a useful addition to the distribution. nobody David Chandek-Stark <david.chandek.stark@duke.edu> serialization 0 1 0 1 1 0
3585 2007-02-26 20:39:23 2007-12-01 23:36:40 2019-06-24 00:53:23.977443 Design decision needed closed Generic views     master wontfix django.views.generic.date_based.archive_{month,day}: date of first object outside interval available in template context Ticket #2368 suggests that in {{{django.views.generic.date_based}}} generic views, {{{previous_month}}} and {{{previous_day}}} should reflect if there is objects in those months. When trying to port the patch attached to #2368 to the state after the changes introduced in fixing #2433 with changeset [3457], I realised it was not entirely sensible. The patch attached to this Ticket implements new variables in template context for {{{django.views.generic.date_based.archive_month}}} and {{{django.views.generic.date_based.archive_day}}}, {{{previous_object_date}}} and {{{next_object_date}}}, which gives the possibility to access the date of the first accessible object outside the interval in either direction. nobody Per Jonsson <poj@lysator.liu.se>   0 1 0 0 0 0
3701 2007-03-10 22:33:19 2007-12-01 17:23:16 2019-06-24 00:54:37.028948 Accepted closed Core (Cache system)     master duplicate Memcached backend is not thread-safe Django relies on the cache backend to be thread-safe, and a single instance of a memcache.Client is not thread-safe. The issue is with Django only creating a single instance that is shared between all threads (django.core.cache.cache). Also discussed here: http://groups.google.com/group/django-developers/browse_thread/thread/c7566757bae3f139 nobody samuel@descolada.com memcached 0 0 0 0 0 0
3817 2007-03-25 21:14:56 2007-12-01 19:30:23 2019-06-24 00:55:49.762175 Accepted closed contrib.admin     newforms-admin worksforme submit_row shows "Save and add another" button when user has not permission to add submit_row decide to show the "Save and add another" button when: {{{ 'show_save_and_add_another': not is_popup and (not opts.admin.save_as or context['add']) }}} and show "Save and continue editing" when: {{{ 'show_save_and_continue': not is_popup and context['has_change_permission'] }}} It's better to change first condition to this: {{{ 'show_save_and_add_another': not is_popup and (not opts.admin.save_as or context['add']) and context['has_add_permission'] }}} nobody reza@zeerak.ir   0 1 0 0 0 0
3959 2007-04-08 03:48:18 2007-12-01 20:19:43 2019-06-24 00:57:18.572674 Design decision needed closed Forms     master wontfix [patch] newforms: label as first argument It seems strange to me that model fields can have their `verbose_name` set as a single positional argument, but newforms labels require the `label=` prefix unless `required` and `widget` are also specified. This patch simply moves `label` to the front, so that forms may specify field labels as just a single positional argument, just like model field `verbose_name`s. nobody Marty Alchin <gulopine@gamemusic.org> newforms label,sprintdec01 0 1 0 0 0 0
3982 2007-04-10 03:06:32 2007-12-01 17:15:34 2019-06-24 00:57:33.116395 Unreviewed closed Database layer (models, ORM)     master fixed Allow Field subclasses to coerce arbitrary Python types In working with a recent !DurationField patch (#2443), I noticed that Django seems to rely on the backend database driver to coerce data into native Python types. However, when adding new fields with non-standard mappings (such as !FloatField for storage, but timedelta as a native type, as in !DurationField), `to_python` needs to be called explicitly when populating an object from the database in order to be usable. This simple patch does just that, using `to_python` to coerce native Python types, after whatever coercion might be done by the database. nobody Marty Alchin <gulopine@gamemusic.org> coerce coercion 0 1 1 1 1 0
4248 2007-05-09 14:53:24 2007-12-01 20:15:08 2019-06-24 01:00:21.374063 Design decision needed closed Forms     master wontfix Form fields should have the title attribute set The title attribute should be optionally set on most form fields. This could be pulled from a new field attribute or the existing help_text. http://www.w3.org/TR/html4/struct/global.html#title nobody nslater@gmail.com sprintdec01 0 0 0 0 0 0
4302 2007-05-15 17:48:34 2007-12-01 18:49:14 2019-06-24 01:00:55.953569 Accepted closed Documentation     master fixed Fix usage of "absolute URL" in the documentation Django's documentation is using the term "absolute URL" in a way that is inconsistent with existing standards. We should fix that; it leads to errors too easily. The relevant definition to apply is in section 3 (and also section 1.4) of RFC 2396: An absolute URI includes everything from the scheme ("http:", etc) onwards. All other URIs are relative. Documentation that needs to be updated * get_absolute_url() -- all our examples are relative and absolute URLs are in the sites documentation. Add a link between the two and some explanation. * The location field in sitemaps. * A few places in syndication_feeds.txt This are all purely documentation/explanation changes. We aren't doing anything fundamentally wrong in the code (outside of !HttpRedirect) that I know of. nobody mtredinnick   0 0 0 0 0 0
4573 2007-06-15 15:56:45 2007-12-01 23:46:02 2019-06-24 01:03:49.874237 Design decision needed closed Template system     master wontfix Minor rewrite of linebreaks and linebreaksbr This relatively small patch modifieslinebreaks and linebreaksbr. They now share the same backend (django.utils.html.linebreaks) which makes linebreaksbr accept additional types of newlines (\r\n etc). This patch also adds support for html (as addition to xhtml) output which are passed in as an argument to the filter: {{{ <h1>linebreaks/linebreaksbr both accepts "html" or 0 (False) as argument</h1> {{ blog.entry|linebreaks:"html" }} }}} Both filters and util defaults to xhtml output (the current behaviour). nobody Johan Bergström <bugs@bergstroem.nu> linebreaks html 0 1 0 0 0 0
4605 2007-06-17 21:15:45 2007-12-01 19:31:08 2019-06-24 01:04:10.832349 Accepted closed Documentation     master wontfix Raw SQL DB API docs should mention transaction.commit_unless_managed() The raw SQL DB API docs don't mention how to deal with transactions other than that cursor does not follow the python DB-API in its support. Transactions should probably be covered at least to the extent of mentioning transaction.commit_unless_managed(). nobody anonymous   0 0 0 0 0 0
4707 2007-06-27 15:08:38 2007-12-01 20:28:22 2019-06-24 01:05:15.993464 Ready for checkin closed Core (Mail)     master wontfix Allow attachements in mail_{admins,managers} The patch adds a parameter to send attachements with mail_admins() and mail_managers() methods. thejaswi_puthraya calvin@debian.org sprintdec01 0 0 0 0 0 0
4737 2007-07-01 17:31:29 2007-12-01 19:11:12 2019-06-24 01:05:35.065883 Design decision needed closed Documentation     master wontfix Split the model field options into those affecting the database and those affecting its appearance or validation. The attached documentation patch split the model field options into those affecting the model's representation in the database and those affecting its appearance or validation. A slight confusion with 'blank' and 'null' meant that I was associating 'blank' with 'required'. This is a fair assumption for the majority of the time (admin app and forms do the same) but using the models in other scripts could cause some confusion when CharFields get created with empty strings by default. nobody Lllama models docs validation 0 1 1 0 0 0
4819 2007-07-10 03:38:18 2007-12-01 19:52:53 2019-06-24 01:06:27.934963 Ready for checkin closed Documentation     master fixed django.contrib.auth.login doesn't just take any user, it needs one that's been modified by authenticate Looking at http://www.djangoproject.com/documentation/authentication/, you'd think you could just pass in a request and a User. But you can't. The code for login needs the side effect caused by calling authenticate, which is to add the backend to the user object. This is very frustrating when writing code where you'd like to log a user in automatically. At the very least, the documentation needs to be changed to reflect it. dakrauth django@catchall.getdown.org   0 1 0 0 0 0
5092 2007-08-05 19:59:24 2007-12-01 20:14:04 2019-06-24 01:09:24.982188 Unreviewed closed Documentation     master invalid FastCGI httpd.conf Example Path I believe the example socket path is missing myproject and should be: {{{ # Connect to FastCGI via a socket / named pipe. FastCGIExternalServer /home/user/public_html/mysite.fcgi -socket /home/user/myproject/mysite.sock }}} nobody jacob@gridface.com   0 0 0 0 0 0
5447 2007-09-14 09:07:25 2007-12-01 18:27:03 2019-06-24 01:13:28.698132 Accepted closed contrib.admin     newforms-admin fixed has_{add,change,delete}_permission not working correctly Using "def has_add_permission(*args):return False" in the model options only raises a permission denied when trying to add an object but it doesn't hide the "add object" button in change_list.html and index.html (and they seem to use different ways to check if the object has the add permission: change_list.html uses "{% if has_add_permission %}" while index.html uses {% if model.perms.add %}) This also applies to "has_change_permission" and "has_delete_permission". Moreover I think that when has_change_permission returns False, it should't allow to modify (save modified) objects, while currently it doesn't allow to see the list of objects. anonymous anonymous   0 0 0 0 0 0
5465 2007-09-14 18:06:35 2007-12-01 20:23:33 2019-06-24 01:13:41.388036 Design decision needed closed Core (Other)     master invalid Summer of Code 2007: Reusable Django applications As one result of my work during the Google summer of code 2007 I changed django.core.management a little and added a new django.utils.package with a metadata assistent and setuptools-based application creation. For more detail ping me on IRC (jezdez) or look at http://jannisleidel.com/ and http://groups.google.com/group/django-developers/browse_thread/thread/bc830d718957beb8 jezdez jezdez packaging, sprintsept14, feature 0 1 0 0 0 0
5469 2007-09-14 19:39:15 2007-12-01 19:39:34 2019-06-24 01:13:43.949848 Accepted closed Documentation     master worksforme Document difference in cleaning between initial and data parameter when using dynamic initial parameters I think is important to note that dynamic {{{initial}}} data created in a form is not cleaned, unlike {{{data}}} parameter. It could causes developer fails like caused by ticket #5145. This is an example what I refer: {{{ >>> class NewsForm(forms.Form): ... date = forms.DateField() ... title = forms.CharField() >>> f = NewsForm(initial={'date': 'not_a_date'}) >>> f.as_table() <tr><th><label for="id_date">Date:</label></th><td><input type="text" name="date" value="not_a_date" id="id_date" /></td></tr> <tr><th><label for="id_title">Title:</label></th><td><input type="text" name="title" id="id_title" /></td></tr> }}} msaelices msaelices newforms, sprintsept14 0 0 0 0 0 0
5514 2007-09-16 18:10:28 2007-12-01 20:28:56 2019-06-24 01:14:14.416241 Design decision needed closed Core (Other)     master wontfix Consistency issue when using ForeignKeys Consider the following models: {{{ class Operand(models.Model): value_1 = models.CharField(maxlength=200) value_2 = models.CharField(maxlength=200) class Operation(models.Model): arg = models.ForeignKey(Operand) }}} Now let's suppose we want to do some work on Operands: {{{ >>> common_arg = Operand(value_1="val1", value_2="val2") >>> common_arg.save() >>> op1 = Operation(arg = common_arg) >>> op2 = Operation(arg = common_arg) >>> op1.save() >>> op2.save() >>> operations = Operation.objects.all().select_related() >>> operations [<Operation: Operation object>, <Operation: Operation object>] >>> operations[0].arg.value_1 = "new_val1" >>> operations[0].arg.save() >>> operations[1].arg.value_2 = "new_val2" >>> operations[1].arg.save() >>> modified_arg = Operand.objects.get(id=1) # OOPS we lost one change here !! >>> modified_arg.value_1 u'val1' >>> modified_arg.value_2 u'new_val2' # restore the initial state >>> modified_arg.value_2 = "val2" >>> modified_arg.save() # this is not limited to select_related but pervasive with FKs >>> work_to_do = [(op, op.arg) for op in Operation.objects.all()] >>> work_to_do[0][1].value_1 = "new_val1" >>> work_to_do[0][1].value_1 'new_val1' # oops, operation 2 will use the outdated argument >>> work_to_do[1][1].value_1 u'val1' }}} #17 could provide a solution for this issue: caching instances in memory so get() and friends can return the instance we already have instead of creating a new, distinct one. The issue is especially easy to encounter with select_related because all related fields will be preloaded in distinct instances in memory. Walking Operation.objects.all() and modifying the Operands from there would load an new instance from the DB for each operation and work as expected in most cases. PhiR PhiR select_related 0 0 0 0 0 0
5550 2007-09-20 07:25:59 2007-12-01 20:11:55 2019-06-24 01:14:37.661568 Ready for checkin closed Documentation     master fixed write docs about the 404.html & 500.html files. Write docs about the 404.html & 500.html files. I found two pages about the files 404.html and 500.html: http://www.djangoproject.com/documentation/tutorial03/#write-a-404-page-not-found-view http://www.djangoproject.com/documentation/request_response/#the-404-page-not-found-view But i can't find a example of these files in the documentation. I find a example here: http://code.djangoproject.com/browser/djangoproject.com/django_website/templates/404.html and here: http://code.djangoproject.com/browser/djangoproject.com/django_website/templates/500.html A django user must known whats in the context of these templates files, to write a nice own error page. whiskybar anonymous   0 1 0 0 0 0
5551 2007-09-20 08:34:08 2007-12-01 22:17:53 2019-06-24 01:14:38.275607 Ready for checkin closed Documentation     master fixed Minor Image Error in Tutorial The image at http://media.djangoproject.com/img/doc/tutorial/admin13t.png shows underscores in the list display, which would probably be fine, except that a little below the image it states: "Also note that the column header for was_published_today is, by default, the name of the method '''(with underscores replaced with spaces)'''." I've edited the original image and am attaching a substitute. ubernostrum anonymous   0 1 0 0 0 0
5626 2007-09-27 17:41:08 2007-12-01 18:45:38 2019-06-24 01:15:26.812078 Design decision needed closed Documentation     master wontfix Mac OS X permissions command could be more succinct. In the ''Mac OSX Permissions'' box (at the top of [http://www.djangoproject.com/documentation/tutorial01/#creating-a-project Creating a Project]), there is some text suggesting a possible permissions solution: ||... To do this, open Terminal.app and navigate (using the `cd` command) to the directory where `django-admin.py` is installed, then run the command `chmod +x django-admin.py`.|| This line could be made quicker and easier by replacing "and navigate... ." with "and run the command {{{chmod +x `which django-admin.py`}}}." This removes the work involved in locating the installation directory, making it a little less painless, and makes the fix a one-step process. It will also guarantee that the correct `django-admin.py` is modified. Possible problem: Backticks can be difficult to recognize in some fonts, but monospace fonts usually show them correctly. The user will most likely copy and paste the command anyway, making this issue moot. mboersma blinks@acm.org terminal Mac OS X 0 1 0 0 0 0
5645 2007-09-30 22:58:48 2007-12-01 19:26:52 2019-06-24 01:15:39.008150 Unreviewed closed Documentation     master wontfix "First App" is Way Too Complex - Some Suggestions For a novice, or PHP convert, or even a Rails convert (I'm versed in PHP and Rails), the "Your First App" is way,way too complex. The important thing here is too remember the 80/20 rule - that users are going to use 20% of the features 80% of the time - so in the "First App" you just want to highlight the 20%. All the rest of the documentation should go into a Users Guide. I'm happy to modify/submit changes to "Your First App" documentation as we build our first Django App. What is really the best way to do this ? Should we download a section, send in our modifications ? Or just give a section by section change here (which means someone else does the actual page changes (feel free to email me). Also a testing section is really needed - testing should be both demonstrated as part of the initial stages as well as encouraged. I've written up a section on testing (but I used James Bennett's to do list example). I'll put that on a separate ticket. One big decision is whether or not a user wants to use the Admin or their own CRUD via NewForms. I think it's important to include a paragraph (see below) to let users decide which they want to use to add/edit/delete their data and then direct them to the appropriate section. We would rather use NewForms but not sure if we are majority, minority or even split. == '''Add, Edit, Delete Your Data''' == Once you have a model described, the next function is to provide for adding, editing, or deleting your data. Django offers 2 primary ways to do this: Admin and NewForms. [perhaps you just want to use "Forms" instead of "New Forms" since people reading this are new users and not used to the old forms]. '''Admin''' First, you can use the Admin library. This library automatically provides a built-in system for managing data, arranging data fields in a tabular form. [merge in all the admin stuff] New Forms You may wish to custom design your data forms like the way it's done with most other web development packages such as PHP and Rails. Django a… nobody john.staff2222@gmail.com   0 0 0 0 0 0
5646 2007-09-30 23:04:01 2007-12-01 17:00:06 2019-06-24 01:15:39.684160 Unreviewed closed Documentation     master wontfix Add Testing Section As part of the "Your First App" - right after creating a model, a short section should be included on how to set up and use a unit test. Here's an example writeup of what we did (though we used the example of James Bennett's to do list tutorial). == Testing Your Models == Now that you have created a few models, it is important to create unit tests to insure they work. This becomes more important later when you make changes to your application and want to insure the changes work before you upload them to the web. Django has built in unit testing that makes this easy. In your application directory, you need to create a "tests.py" file. In this file you can include the following code: import unittest from todo.models import List from todo.models import Item class ListTestCase(unittest.TestCase): def setUp(self): self.testlist = List.objects.create(name='TestList') def test_Name(self): self.assertEquals(self.testlist.name, 'TestList') class ItemTestCase(unittest.TestCase): def setUp(self): self.testlist = List.objects.create(name='TestList') self.testitem = Count.objects.create(name="TestItem", todo_list = self.testlist) def test_Name(self): self.assertEquals(self.testitem.name, 'TestItem') The "def setUp(self)" function can be used to create an instance of the model that can be used in the test functions that follow. So for the List model, we create an instance named "testlist" and have set the object name field with "TestList". Actual test functions begin with "test" (an underscore is not necessary but makes for easy code reading). In the test function, different "assert" functions can be used - in this case an "assertEquals" function is used to make a comparison of the name field in the created object (testlist) with the actual phrase "TestList". Now you run the tests at the command line by typing: python manage.py test If the object was created correctly, the names should match and you should get a te… nobody john.staff2222@gmail.com   0 0 0 0 0 0
5667 2007-10-02 21:41:59 2007-12-01 15:34:00 2019-06-24 01:15:53.379655 Unreviewed closed Uncategorized     master wontfix Session backend does not work for db backend Using the default database backend for the session, the session values are not stored, so it can't not be retrieved when requested. If you configure the session engine to be caché based and you configure the cache_backend as memcached or locmem for example. it works properly. I have tried to drop and syncdb the session table without succes. I you configure the cache backend as file you'll get an error trying to store the session. The django.contrib.sessions.backends.file does not work either. I'm on the 0.97-pre-SVN-6443 branch and using sqlite as the development database. nobody aaloy@apsl.net session cache backend 0 0 0 0 0 0
5760 2007-10-15 23:10:08 2007-12-01 18:21:38 2019-06-24 01:16:53.873455 Unreviewed closed contrib.sessions     0.96 wontfix Use keyed hashing for session data, remove duplicate code Use hmac instead of md5 to create a digest of session data. Using hmac is probably more secure than the home built md5 implementation. Also, the current implementation uses hexdigest() when digest() is just fine. While replacing the hash, extract the digest code to a new function to remove duplicate code. Issues: - Old session will be invalidated with this patch nobody Nir Soffer <nirs@freeshell.org>   0 1 0 0 0 0
5812 2007-10-24 21:03:27 2007-12-01 18:52:57 2019-06-24 01:17:27.395742 Unreviewed closed Documentation     master invalid Misleading sentence in the database api reference On http://www.djangoproject.com/documentation/db-api/ I'm reading: "The people who made Django prefer to put all the SQL-affecting methods first, followed (optionally) by any output-affecting methods (such as values()), but it doesn’t really matter." This leads to the impression that values() does not affect the SQL statement of the query set which it purportedly does! nobody Hans Faber <chmane@gmail.com>   0 0 0 0 0 0
5844 2007-10-31 05:03:11 2007-12-01 17:30:26 2019-06-24 01:17:48.031531 Unreviewed closed Documentation     master invalid Part 4 of the Tutorial is missing another step at the end In this section: {{{ The vote() view is still required. However, it must be modified to match the new templates and context variables. Change the template call from polls/detail.html to polls/poll_detail.html, and pass object in the context instead of poll. }}} You should also make a note that they need to update results.html. They need to change the reference in the template page from poll to object. nobody Harry Park tutorial 0 0 0 0 0 0
5859 2007-11-02 00:47:10 2007-12-01 16:46:27 2019-06-24 01:17:57.684757 Design decision needed closed Contrib apps     master duplicate Redirect middleware should use iexact to match old_path This, or drop unique_together=(('site', 'old_path'),) in Redirect model. The problem is that you can't add both '/About.html' and '/about.html' as two redirects for the same site. nobody E Miller <thnntn+djtrac@gmail.com> redirects 0 1 0 0 0 0
5860 2007-11-02 09:27:40 2007-12-01 20:08:45 2019-06-24 01:17:58.319571 Unreviewed closed Documentation     master fixed The mentioned order of checking item_link for feeds is wrong In the documentation for syndication feeds, it is stated that Django checks the items' get_absolute_url() first, but actually it is checked last, as it should be. http://www.djangoproject.com/documentation/syndication_feeds/#feed-class-reference {{{ # ITEM LINK -- One of these three is required. The framework looks for # them in this order. # First, the framework tries the get_absolute_url() method on each item # returned by items(). Failing that, it tries these two methods: }}} nobody omat@gezgin.com feeds syndication item_link 0 0 0 0 0 0
5870 2007-11-03 23:21:24 2007-12-01 17:20:19 2019-06-24 01:18:04.640770 Unreviewed closed Documentation     master fixed send-mail docs out of date >>> help( send_mail ) {{{ Help on function send_mail in module django.core.mail: NOTE: This method is deprecated. It exists for backwards compatibility. New code should use the EmailMessage class directly. }}} This should be stated in http://www.djangoproject.com/documentation/email/#send-mail nobody Carl Karsten <carl@personnelware.com> deprecated email 0 0 0 0 0 0
5882 2007-11-06 16:37:11 2007-12-01 17:12:55 2019-06-24 01:18:12.497667 Unreviewed closed Documentation     master invalid Cross-site scripting not mentioned in the tutorial Am I right that you don't mention the problem of cross-site scripting in the tutorial? Let's say I would add a poll like this: question: What does <script>alert("foo");</script> do? Would the application output a properly quoted question or would I get a JavaScript message box? nobody roland.illig@gmx.de xss cross-site-scripting 0 0 0 0 0 0
5907 2007-11-08 23:44:06 2007-12-01 16:45:53 2019-06-24 01:18:28.562827 Unreviewed closed Documentation     master wontfix development installation docs should mention .pth for path configuration on Windows Currently, the installation docs say that: "Alternatively, you can define your PYTHONPATH environment variable so that it includes the django subdirectory of django-trunk. This is perhaps the most convenient solution on Windows systems, which don't support symbolic links." IMHO using a django.pth file is more convenient, because the user doesn't have to set PYTHONPATH for Python or mod_python. nobody arien <regexbot@gmail.com> installation windows 0 1 0 0 0 0
5940 2007-11-14 21:24:47 2007-12-01 17:07:33 2019-06-24 01:18:50.089770 Unreviewed closed Documentation     master fixed documentation/add_ons is missing sessions and webdesign http://www.djangoproject.com/documentation/add_ons/ has form_tools out of alphabetic order. And it is missing sessions and webdesign. nobody Jonathan Fine <jfine@pytex.org>   0 0 0 0 0 0
5941 2007-11-14 21:29:20 2007-12-01 17:02:35 2019-06-24 01:18:50.737449 Unreviewed closed Documentation     master fixed documentation/shortcuts not linked to from documentation This was posted yesterday to django-users. Missing Documentation cross-reference to shortcuts ? A lookup on google shows that the page http://www.djangoproject.com/documentation/shortcuts/ isn't linked from anywhere on the documentation (and the site), and I had to search it to find it. nobody Jonathan Fine <jfine@pytex.org>   0 0 0 0 0 0
5946 2007-11-15 03:13:58 2007-12-01 16:47:19 2019-06-24 01:18:53.982887 Accepted closed Documentation     master invalid error in tutorial Error found in page http://www.djangoproject.com/documentation/tutorial03/ in the urlconf file listed in this tutorial, in this case, mysite/polls/url.py...the following should be commented out until built during the next tutorial stage. {{{ # (r'^(?P<poll_id>\d+)/results/$', 'results'), # (r'^(?P<poll_id>\d+)/vote/$', 'vote'), }}} If you don't, the admin page is broken. See http://code.djangoproject.com/ticket/5904 for details. I'm new to django and pieced together what i needed to do based on the terse description in that closed ticket. Having this mentioned in the tutorial would have saved me about an hour of grief. Other than that, cool! thanks. :) nobody sneakywombat   0 1 0 0 0 0
5976 2007-11-19 01:39:22 2007-12-01 14:22:45 2019-06-24 01:19:13.628583 Ready for checkin closed contrib.admin     master fixed Admin escapes non-breaking spaces for empty fields in change list The admin change list displays {{{&nbsp;}}} in all empty fields since autoescape has landed, since a non-breaking space is returned but not marked as safe. nobody nickl   0 1 0 0 0 0
5979 2007-11-19 04:57:16 2007-12-01 21:58:51 2019-06-24 01:19:15.474924 Ready for checkin closed Testing framework     master fixed Django tests fail if SITE_ID is not 1. The following tests fail if the SITE_ID is set to 2, for example. They work fine if it's 1. {{{ #!python ====================================================================== ERROR: Request a logout after logging in ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/tobryan1/workspace/django/tests/modeltests/test_client/models.py", line 315, in test_logout self.assertRedirects(response, 'http://testserver/accounts/login/?next=/test_client/login_protected_view/') File "/usr/lib/python2.5/site-packages/django/test/testcases.py", line 98, in assertRedirects redirect_response = response.client.get(path, QueryDict(query)) File "/usr/lib/python2.5/site-packages/django/test/client.py", line 219, in get return self.request(**r) File "/usr/lib/python2.5/site-packages/django/core/handlers/base.py", line 81, in get_response response = callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.5/site-packages/django/contrib/auth/views.py", line 32, in login current_site = Site.objects.get_current() File "/usr/lib/python2.5/site-packages/django/contrib/sites/models.py", line 22, in get_current current_site = self.get(pk=sid) File "/usr/lib/python2.5/site-packages/django/db/models/manager.py", line 69, in get return self.get_query_set().get(*args, **kwargs) File "/usr/lib/python2.5/site-packages/django/db/models/query.py", line 263, in get raise self.model.DoesNotExist, "%s matching query does not exist." % self.model._meta.object_name DoesNotExist: Site matching query does not exist. ====================================================================== ERROR: Request a page that is protected with @login_required ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/tobryan1/workspace/django/tests/modeltests/test_client/models.py", line 245, in test_view_with_login self.assertRedirects(response… nobody toddobryan   0 1 0 0 0 0
6007 2007-11-21 12:18:01 2007-12-01 19:23:49 2019-06-24 01:19:33.867876 Accepted closed Core (Management commands)     master fixed Oracle DB-Backend: db_tablespace setting for django standard tables It would be nice, if there could be a possibilty to define a default tablespace (maybe in setting.py) for the django internal tables and indexes (auth, contenttypes, session, sites,...) I tried to define a little project in my company with django and a oracle database. But 'syncdb' didn't work, because our database administrator forbid a CREATE TABLE, CREATE INDEX without a tablespace option. ikelly Bernd oracle tablespace 0 0 0 0 0 0
6034 2007-11-27 03:34:09 2007-12-01 16:42:53 2019-06-24 01:19:51.081371 Design decision needed closed Core (Management commands)     master wontfix Add boolean option 'load_fixtures' to the django command 'syncdb', default value is True. Add boolean option 'load_fixtures' to the django command 'syncdb', default value is True. We use this option in tests, so load_fixtures=False will not commit a transaction, and we can rollback easily. There are also other circumstances that we don't want the fixture to load automatically. nobody delimy@exoweb.net syncdb 0 1 0 0 0 0
6053 2007-11-29 16:26:09 2007-12-01 21:00:41 2019-06-24 01:20:03.611900 Unreviewed closed Testing framework     master invalid Allow django.contrib tests to be in tests/ subdirectory A "nice to have item": some of the django.contrib.* directories have a few files in them because of the tests. For example, tests.py, models.py, maybe a urls file as well. These aren't really related to the functionality of the contrib app. It would be nice if we could put those in a tests/ subdirectory. nobody mtredinnick   0 0 0 0 0 0
6068 2007-12-01 01:27:15 2007-12-01 21:18:46 2019-06-24 01:20:13.146715 Ready for checkin closed Uncategorized     master fixed typo error in modeltests docstring in tests/modeltests, fixture and user_commands are all signed with number 37, this is a typo error. 37.Fixtures. ./fixtures/models.py 37.User-registered management commands ./user_commands/models.py And all docstring of models.py after number 37 should be changed, they are: tests/modeltests/user_commands/models.py should be 38 tests/modeltests/test_client/models.py should be 39 tests/modeltests/empty/models.py should be 40 tests/modeltests/select_related/models.py should be 41 tests/modeltests/serializers/models.py should be 42 bartuer bartuer <bartuer@exoweb.net> tests fixtures user-registered management commands 0 1 0 0 0 0
6069 2007-12-01 03:57:52 2007-12-01 22:24:51 2019-06-24 01:20:13.753079 Accepted closed contrib.admin     master wontfix Fix auto-escaping Password-Change-Link in Admin Auto-escaping broke Password-Change link in Admin. anonymous anonymous admin, escaping, sprintdec01 0 1 0 0 0 0
6078 2007-12-01 14:12:39 2007-12-01 16:39:29 2019-06-24 01:20:19.509366 Unreviewed closed contrib.admin     newforms-admin fixed Admin escapes non-breaking spaces for empty fields in change list Same Bug as #5976 but in Newforms Admin. Same Patch will work. jkocherhans toke newforms, admin, escape, sprintdec01 0 1 0 0 0 0
6079 2007-12-01 17:21:37 2007-12-01 17:27:45 2019-06-24 01:20:20.181121 Unreviewed closed Documentation     master fixed AUTHENTICATION_BACKENDS is not documented in settings.txt Hi there, AUTHENTICATION_BACKENDS is documented in authentication.txt, but not in settings.txt Maybe it's intentional as django.contrib.auth is "contrib", but SITE_ID is documented! ;) Anyway I'll try to post a patch later. nobody telenieko   0 0 0 0 0 0
6081 2007-12-01 17:45:17 2007-12-01 18:10:15 2019-06-24 01:20:21.586349 Unreviewed closed contrib.sessions     master fixed contrib.sessions.models.Session has obsolete functions As of [6333], `get_new_session_key` and `get_new_session_object` on `Session` are no longer used, but are still present. Functionality was moved to `SessionBase` under `_get_new_session_key`. __hawkeye__ __hawkeye__   0 1 0 0 0 0

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