177 rows where "changetime" is on date 2006-10-22

View and edit SQL

Suggested facets: component, type, version, owner, keywords, has_patch, created (date), last_pulled_from_trac (date)

changetime (date)

  • 2006-10-22 · 177
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
40 2005-07-17 01:32:23 2006-10-22 16:14:52 2019-06-24 00:15:42.302555 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
52 2005-07-18 00:39:10 2006-10-22 16:22:27 2019-06-24 00:15:50.008694 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
62 2005-07-18 16:34:40 2006-10-22 15:54:23 2019-06-24 00:15:56.409972 Unreviewed closed Documentation enhancement normal   fixed Change tutorial to use easy development server, not mod_python   adrian adrian   0 0 0 0 0 0
74 2005-07-18 21:05:56 2006-10-22 16:23:53 2019-06-24 00:16:04.309683 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
86 2005-07-19 15:37:19 2006-10-22 16:17:36 2019-06-24 00:16:11.819791 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
119 2005-07-20 19:42:19 2006-10-22 16:18:52 2019-06-24 00:16:32.531116 Unreviewed closed Core (Other) enhancement normal   wontfix Serving media There is currently no way of serving media through Django, which might be alright for mod_python as it's counting on Apache, but the WSGI server doesn't have such benefits. adrian brantley (deadwisdom@gmail.com) media wsgi images 0 0 0 0 0 0
135 2005-07-21 11:19:17 2006-10-22 16:26:08 2019-06-24 00:16:42.563728 Unreviewed closed Documentation defect normal   fixed Document mod_python behavior with more than one SETTINGS in a vhost URL resolving will be unstable if more than one DJANGO_SETTINGS_MODULE is referenced within a vhost (for example, in different locations) due to mod_python caching. This should be documented in the mod_python doc. jacob Manuzhai   0 0 0 0 0 0
174 2005-07-24 04:25:02 2006-10-22 16:25:38 2019-06-24 00:17:07.302220 Unreviewed closed Documentation defect normal   fixed Tutorial01 translated to brazilian portuguese Tutorial01 translated to brazilian portuguese jacob eminetto@gmail.com   0 0 0 0 0 0
175 2005-07-24 15:48:38 2006-10-22 16:39:55 2019-06-24 00:17:07.899040 Unreviewed closed Database layer (models, ORM) defect normal   wontfix select_related does not work in both directions.. comparing the following two statements: {{{ >>> for p in polls.get_list(select_related=True): print p, p.get_choice_list() >>> for c in choices.get_list(select_related=True): print c.get_poll(), c }}} The first statement runs one query per poll, while the second runs one query no matter how many polls you have. This seems to be because the information about what models are related to each other does not get added to both ends of the relationship... now this is not 100% true because a poll obviously knows about what choices reference it... My guess is that there needs to be a OneToMany class that compliments the ManyToOne relationship, letting the Poll class know that select_related should pull in choices. adrian Justin select_related 0 0 0 0 0 0
179 2005-07-24 20:55:12 2006-10-22 16:31:13 2019-06-24 00:17:10.444214 Unreviewed closed Core (Management commands) defect normal   invalid Time zone doesn't work right under django_admin.py runserver No problems with mod_python though adrian edgars@way.lv   0 0 0 0 0 0
199 2005-07-25 21:31:55 2006-10-22 16:12:44 2019-06-24 00:17:23.047982 Unreviewed closed Metasystem defect trivial   fixed CharField should raise an exception when maxlength is not specified "maxlength" is a required keyword argument for a CharField, yet no error is raised if the argument is not provided. The error produces its effect much later when the SQL code containing "varchar(None)" fails. It would be better for CharField to raise an exception immediately, so as to simplify debugging. adrian Steadicat   0 0 0 0 0 0
201 2005-07-26 00:52:28 2006-10-22 16:33:19 2019-06-24 00:17:24.286493 Unreviewed closed contrib.admin defect major   invalid ImageField validation error Once an image has been uploaded in an ImageField (its path is shown labeled "currently"), any successive edit to the object raises a validation error: "Enter a valid filename.". This happens regardless of whether a new image is being uploaded or not. (OS: Windows, Browser: any) adrian Steadicat   0 0 0 0 0 0
221 2005-07-29 07:01:59 2006-10-22 16:09:18 2019-06-24 00:17:37.136658 Unreviewed closed Documentation defect normal   invalid Missing argument for ForeignKey in documentation ForeignKey fields provide an argument called 'name', which is not not mentioned in documentation. It is useful when you need to reference a ForeignKey field by name, i.e. when you want to order the fields list in admin via admin = meta.Admin(fields = ((None, {'fields': ('foo', 'forKey_name', 'bar')}),) jacob paolo   0 0 0 0 0 0
288 2005-08-08 05:55:46 2006-10-22 15:46:59 2019-06-24 00:18:20.144561 Unreviewed closed Documentation enhancement normal   invalid Document custom template tags systyem As far as I could see, there was no way to include userdefined taglibs into a django app except by extending django.templatetags. I might well have missed something, though. Be that as it may, I found it to be quickest to hack django.core.defaulttags to try and load taglibs from paths provided in TEMPLATETAG_DIRS in your config. I'll try to upload the patch here. jacob jens@unwesen.de taglibs 0 0 0 0 0 0
298 2005-08-10 12:32:57 2006-10-22 16:03:31 2019-06-24 00:18:26.509470 Unreviewed closed Core (Other) enhancement normal   wontfix Need impovement to POST.copy() When i need to change only few fields of model, for example only date_start field of Project, i need to pass a values of other fields like new_data variable into manipulator.* methods ('coz they are not present in POST) The only place of values of other fields is Project.__dict__ But manipulator.* methods expects new_data.values() like strings. And Project.__dict__ contains .values() like python-values. Also, new_data must be MultiValueDict So, i need to make new_data like this (it's a simple shortened example without checks): {{{ def start(req, p_id): """ Updates "start" information about project Such as start_date, start_people e.t.c. """ try: prj = projects.get_object(pk=rp_id) except projects.ProjectDoesNotExist: raise Http404 manipulator = projects.ChangeManipulator(prj.id) new_data = prj.__dict__ # all fields of Project errors = dict() if req.POST: #only tree fields changed, and values of them are in req.POST new_data = update_post(req.POST.copy(), new_data) errors = manipulator.get_validation_errors(new_data) mnp.do_html2python(new_data) mnp.save(new_data) }}} Where the update_post() is like this: {{{ def update_post(post, data): for key in data: if not key in post.keys(): if data[key]: post[key]=str(data[key]) else: post[key]='' return post }}} But it's easy to say: {{{ new_data = req.POST.copy(new_data) # default values like param #or new_data.update(req.POST) }}} or something like this... adrian mr_little   0 0 0 0 0 0
321 2005-08-15 00:31:40 2006-10-22 16:29:05 2019-06-24 00:18:41.532531 Unreviewed closed Database layer (models, ORM) defect blocker   fixed Revision 494 breaks MySQL Immediately after upgrading to [494], the MySQL backend has stopped functioning. Django reports the following error: {{{ ImproperlyConfigured: Could not load database backend: cannot import name CursorNW. Is your DATABASE_ENGINE setting (currently, 'mysql') spelled correctly? Available options are: 'mysql', 'postgresql', 'sqlite3' }}} adrian anonymous   0 0 0 0 0 0
346 2005-08-17 16:54:18 2006-10-22 16:26:27 2019-06-24 00:18:57.581092 Unreviewed closed Template system defect normal   wontfix Template tag for the media_root variable There should be a template tag for the media_root variable like there is one for the admin_media_root variable adrian slashzero   0 0 0 0 0 0
350 2005-08-17 21:02:26 2006-10-22 15:54:57 2019-06-24 00:19:00.078802 Unreviewed closed Database layer (models, ORM) defect major   fixed "offset" keyword does not work on MySQL 3.x When you use the Django API to query your data using the {{{get_items(offset=X)}}} style call, the SQL that is generated seems to be in Postgres style that is only recently supported in MySQL (4.x and later, as far as I can tell.) The SQL generated is something like the following: {{{ SELECT ... ORDER BY ... DESC LIMIT 5 OFFSET 4 }}} On MySQL 3.x this gives the following error: {{{ "You have an error in your SQL syntax near 'OFFSET 4 '" }}} It works fine on my 4.1. As far as I can tell from the MySQL manual, there is an alternate form of query that should work on all versions of MySQL. Here's the relevant snippet from the SELECT format: {{{ [LIMIT {[offset,] row_count | row_count OFFSET offset}] }}} Since 3.23 is the default MySQL version for Fedora Core etc, this could affect quite a few people. adrian ronan@cremin.com mysql database offset 0 0 0 0 0 0
417 2005-08-25 12:28:02 2006-10-22 16:05:02 2019-06-24 00:19:43.200564 Unreviewed closed Documentation defect normal   fixed Tutorial 2 doesn't make the settings module clear enough for the admin server. In Tutorial 2, the user is instructed to start the admin server using myproject.settings.admin. Unfortunately, this looks similarish to myproject.settings.main and can cause confusion when the admin URL doesn't work. I've attached a patch which adds a nice big note to help people out when they hit this. The wording could probably use a bit of work. jacob benno@jeamland.net   0 0 0 0 0 0
419 2005-08-26 04:23:46 2006-10-22 16:30:00 2019-06-24 00:19:44.584307 Unreviewed closed Metasystem enhancement enhancement   duplicate Create meta.AbstractModel {{{ #!python class BaseModel(meta.Model): foo = meta.CharField(maxlength=200) class FirstChild(BaseModel): bar = meta.CharField(maxlength=10) class SecondChild(BaseModel): bar = meta.CharField(maxlength=10) }}} In this example, {{{BaseModel}}} only exists as an "abstract class" -- its only purpose is to be extended. We don't want to install SQL for it, and we don't want it to be available via the API. So we could introduce a {{{meta.AbstractModel}}} for models that serve this purpose. adrian adrian   0 0 0 0 0 0
445 2005-08-31 22:00:04 2006-10-22 16:24:00 2019-06-24 00:20:01.265664 Unreviewed closed Metasystem defect normal   fixed allow partial object updates with manipulators currently the manipulators that are created from model modules (ChangeManipuator and AddManipulator) expects all fields of an object in the new_data dict. This is a bit cumbersome if somebody want's to put up a form that only should edit some fields of an object. The validation code will barf about every missing required field and the html2python conversion and data saving will require all data to be there. An idea that came up on IRC was to give the ChangeManipulator constructor an optional parameter "only_fields" that receives a list of fieldnames that should be worked on in the manipulator. The ChangeManipulator already reads in the original object (and stores it as Manipulator.original_object internally) and so could use the "only_fields" list as a guide to what fields of the original_object should be overwritten with data from new_data. Additionally the Manipulator would have to keep only the fields named in the "only_fields" list in it's internal fields dictionary so that the validation code and the html2python conversion only work with those fields. With this change it would be possible to build a form with the standard ChangeManipulator code for situations where only part of the object should be edited - an example would be a user profile page that will allow the user only to edit the first_name, last_name and email fields. adrian hugo <gb@bofh.ms> new-admin 0 0 0 0 0 0
464 2005-09-06 10:48:09 2006-10-22 16:18:38 2019-06-24 00:20:13.233404 Unreviewed closed Core (Other) defect minor   invalid [patch] Modification of django.core.mail: more fields, using dicts to pass arguments Currently, mail.py allows specifying only few email headers. This enhancement would allow to specify fields such as Reply-To, Content-Type and charset. It also adds methods (send_mail_dict, send_mass_mail_dict) allowing to pass these values as a dictionary. It could be done by modifying existing methods and dictionary unpacking, but that would break backwards compatibility (if someone uses fail_silently as a positional argument). So, here's the patch: {{{ Index: mail.py =================================================================== --- mail.py (revision 629) +++ mail.py (working copy) @@ -9,15 +9,28 @@ Easy wrapper for sending a single message to a recipient list. All members of the recipient list will see the other recipients in the 'To' field. """ - return send_mass_mail([[subject, message, from_email, recipient_list]], fail_silently) + return send_mass_mail([(subject, message, from_email, recipient_list)], fail_silently) +def send_mail_dict(message_dict, fail_silently=False): + return send_mass_mail_dict([message_dict], fail_silently) + def send_mass_mail(datatuple, fail_silently=False): """ Given a datatuple of (subject, message, from_email, recipient_list), sends each message to each recipient list. Returns the number of e-mails sent. + If from_email is None, the DEFAULT_FROM_EMAIL setting is used. + """ + keys = ("subject", "message", "from_email", "recipient_list") + return send_mass_mail_dict([dict(zip(keys, item)) for item in datatuple]) - If from_email is None, the DEFAULT_FROM_EMAIL setting is used. +def send_mass_mail_dict(message_dicts, fail_silently=False): """ + Given a list of dictionaries containing email parameters, sends each message + to each recipient list. Returns the number of e-mails sent. Available parameters: + 'from_email', 'recipient_list', 'message', 'subject', 'reply_email', 'content_type' + and 'charset'. Two first are mandatory. If from_email is None, the + DEFAULT_F… adrian anonymous   0 1 0 0 0 0
468 2005-09-07 10:48:41 2006-10-22 15:58:18 2019-06-24 00:20:15.680484 Unreviewed closed Metasystem enhancement normal   fixed [patch] Add accessor method to get human readable value for fields with a choice list. Sometimes it is useful to access the human readable value of a field with a choices list. Currently (AFAIK) this can only be done by a manipulator. This patch adds methods to the generated model classes to allow clients to access the human readable value. adrian robert@wittams.com   0 1 0 0 0 0
496 2005-09-12 21:21:37 2006-10-22 16:40:14 2019-06-24 00:20:33.451175 Unreviewed closed Core (Other) defect normal   fixed Better error messages when using generic views. I had problems, and it sounds like it's fairly common, figuring out how to pass information to the generic views. I propose the following patch which reports an improperly set app_label as: ImportError: Unable to import app_label "poll": No module named poll And if the module_name is bad, it reports: ImportError: Unable to import module_name "user": No module named user (available choices: ['Event', 'User', 'View', '_MODELS', '__builtins__', '__doc__', '__file__', '__name__', 'events', 'meta', 'users', 'views']) Sean adrian jafo@tummy.com   0 0 0 0 0 0
522 2005-09-16 16:24:54 2006-10-22 15:51:00 2019-06-24 00:20:50.143341 Unreviewed closed Metasystem defect normal   fixed Model methods should accept decorators Model methods don't accept decorators, and they should. Here's a snippet from imaurer on the django-developers mailing list: {{{ The one thing I don't like is that I cannot add decorators like classmethod. For instance, this method: @classmethod def clsmethod(cls): print "HERE in", cls Blows up like this for me: File "C:\www\django\core\meta\__init__.py", line 490, in __new__ assert callable(v), "%r is an invalid model parameter." % k AssertionError: 'clsmethod' is an invalid model parameter. I am also not able to create a 'memoize' decorator for caching method results in an instance. Instead, I either have to do the "if _cache_blah: return _cache_blah" pattern in each method I want cacheable or call out to a non-model function that can be memoized but using a global LRU dictionary. }}} adrian adrian   0 0 0 0 0 0
534 2005-09-21 22:58:56 2006-10-22 16:30:42 2019-06-24 00:20:58.001648 Unreviewed closed Tools enhancement minor   invalid Model validator should validate models/__init__.py The model validator should ensure the {{{__all__}}} in {{{models/__init__.py}}} matches the list of models within the {{{models/}}} directory. adrian adrian   0 0 0 0 0 0
539 2005-09-22 16:08:38 2006-10-22 15:56:44 2019-06-24 00:21:01.549727 Unreviewed closed Core (Other) defect normal   fixed Support for strides in the slice filter. This patch adds support for strides in the slice filter. For example: {{{ {% my_list|slice:"::2" %} }}} should include every other element of my_list. adrian Esaj slice strides 0 0 0 0 0 0
540 2005-09-22 17:34:15 2006-10-22 16:24:36 2019-06-24 00:21:02.269997 Unreviewed closed Core (Other) defect normal   fixed ManyToManyField gives error with blank, raw_id_admin and empty input If you define the following field: {{{ tags = meta.ManyToManyField(Tag, blank=True, raw_id_admin=True) }}} And provide no input for the 'tags' field in the HTML form for the addition of the given model. You get this error (although blank=True should cause it to work fine): {{{ There's been an error: Traceback (most recent call last): File "d:\django\django\core\handlers\base.py", line 64, in get_response response = callback(request, **param_dict) File "i:\projects\grono2\contrib\web\create_update.py", line 51, in create_object new_object = manipulator.save(new_data) File "d:\django\django\utils\functional.py", line 3, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "d:\django\django\core\meta\__init__.py", line 1483, in manipulator_save was_changed = getattr(new_object, 'set_%s' % f.name)(new_data.getlist(f.name)) File "d:\django\django\utils\functional.py", line 3, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "d:\django\django\core\meta\__init__.py", line 896, in method_set_many_to_many id_list = map(int, id_list) # normalize to integers ValueError: invalid literal for int(): }}} adrian wojtek3@brandlay.com   0 0 0 0 0 0
550 2005-09-23 18:39:49 2006-10-22 16:15:16 2019-06-24 00:21:09.210737 Unreviewed closed contrib.admin enhancement normal   fixed [patch] Modify admin site to remove apps, modules, actions that the user does not have permissions for. In the current Django admin site, if a user doesn't have permissions to certain apps or modules within Django, the user can still see the entire list of apps, modules, and actions (add and change). The user only finds out that they don't have permission to do something if they follow one of the "add" or "change" links for that module and get a "Permission Denied" page in response. This patch fixes the admin view so a user can only see modules and actions they have permissions for. adrian Jason Huggins admin UI permissions 0 1 0 0 0 0
574 2005-09-29 03:53:21 2006-10-22 16:27:21 2019-06-24 00:21:24.232486 Unreviewed closed contrib.admin defect trivial   fixed [patch] fix small CSS bug in admin interface A small CSS bug in the admin interface "squised" tables togther when using filtering, no more! jacob hp@syntomax.com   0 1 0 0 0 0
606 2005-10-10 21:57:01 2006-10-22 16:04:16 2019-06-24 00:21:44.288537 Unreviewed closed Documentation defect normal   invalid Admin documentation section URL not mentioned in docs The location of the live documentation in the admin ('''/admin/doc/''') is not mentioned at [http://www.djangoproject.com/documentation/templates/]. I saw it mentioned in a comment and also found it myself by looking at the URLconf. jacob cygnus@cprogrammer.org   0 0 0 0 0 0
608 2005-10-10 22:20:49 2006-10-22 15:55:25 2019-06-24 00:21:45.554836 Unreviewed closed Generic views enhancement normal   duplicate Allow objects with future dates to display in date based generic views The date based generic views are coded to only show objects whose given date field is <= now. However, for views of something like an events calendar, one needs to display objects whose date field is >= now. Proposed is to add an "upcoming_index", which sorts ascending, for showing future objects, and a "future_ok=False" keyword argument to the "archive_(year, month,day)" and "object_detail" views. jacob scaba   0 0 0 0 0 0
610 2005-10-11 13:26:23 2006-10-22 16:17:37 2019-06-24 00:21:46.842489 Unreviewed closed contrib.admin enhancement normal   wontfix XSLT as templating engine. It would be great to have XSLT as an optional template engine. It would require some sort of model -> XML conversion first. The reasons to use XSLT are: * it's XML (easy to verify that the templates are in workding condition using DTD or Schema) * it's a widely accepted standard (higher interoperability between different frameworks) * it is extremely versatile and extensible * it's very fast (using libxslt from xmlsoft.org or other fast implementations) adrian anonymous   0 0 0 0 0 0
622 2005-10-13 18:36:32 2006-10-22 15:53:40 2019-06-24 00:21:54.327634 Unreviewed closed Template system enhancement normal   fixed Added a isnull filter Added a isnull filter to be used instead of default for times when 0 in a numeric field has meaning adrian Eric Moritz   0 0 0 0 0 0
644 2005-10-18 18:12:54 2006-10-22 15:55:52 2019-06-24 00:22:08.259543 Unreviewed closed Database layer (models, ORM) defect normal   duplicate SQL Server DB backend: Rev 940 test results This is the output of tests/runtests.py against MS SQL 2000 SP 3 on Win2K SP4. adrian jdunck@gmail.com db ado sqlserver core test 0 0 0 0 0 0
660 2005-10-20 14:48:40 2006-10-22 16:33:58 2019-06-24 00:22:18.382102 Unreviewed closed contrib.admin defect normal   fixed admin executes template code that happens to be in strings in the list views When you have a field that stores template snippets and add that field to the list_display tuple to show up in admin list views, the template code in those snippets is evaluated. I suppose this is because of the dynamic creation of the admin template code. adrian hugo new-admin 0 0 0 0 0 0
664 2005-10-20 21:30:25 2006-10-22 16:28:42 2019-06-24 00:22:20.927867 Unreviewed closed Documentation enhancement minor   fixed Document 'singular' argument for ManyToMany fields Having two ManyToMany relationships between the same two models is actually fairly common (I came across it myself early on in creating my models and have seen a number of people asking about this situation). So it needs to be better documented how you do this and get the get_XXX methods you need, and below is a very small patch to the docs which I think is correct. (I haven't checked the formatting parses correctly as I don't know how to do that, but it should be right). jacob L.Plant.98@cantab.net   0 0 0 0 0 0
670 2005-10-20 23:17:25 2006-10-22 16:19:43 2019-06-24 00:22:24.703315 Unreviewed closed *.djangoproject.com defect minor   fixed djangoproject website should be updated to reflect recent admin changes the djangoproject.com website is a reference point for new django users, showing them a "complete" project after moving on from the tutorials. Therefore the code in subversion (not necessary the public site) should be updated to reflect the recent admin/settings changes jacob anonymous   0 0 0 0 0 0
686 2005-10-24 02:41:22 2006-10-22 16:10:04 2019-06-24 00:22:34.847774 Unreviewed closed Generic views enhancement major 0.90 fixed sqlreset references django_admin_log C:\ncauction>django-admin sqlreset auction 1>_builddb.sql C:\ncauction>sqlite3 c:\ncauction\db\auction.db3 0<_builddb.sql DELETE FROM django_admin_log WHERE content_type_id = 17; SQL error: no such table: django_admin_log ... sqlreset generates bad sql as above in the case where admin is not installed. Does not really hurt anything though. adrian davidschein@alumni.tufts.edu   0 0 0 0 0 0
698 2005-10-26 15:52:14 2006-10-22 16:41:26 2019-06-24 00:22:42.579810 Unreviewed closed Core (Management commands) defect normal   duplicate Exceptions thrown after CONTROL-C typed to stop test web server. I received the following exceptions after attempting to stop the built-in test server with CONTROL-C: {{{ shell> django-admin.py runserver Validating models... 0 errors found. Starting server on port 8000 with settings module 'myproject.settings'. Go to for Django. Quit the server with CONTROL-C (Unix) or CTRL-BREAK (Windows). [26/Oct/2005 09:43:53] "GET /admin/ HTTP/1.1" 200 1615 [26/Oct/2005 09:44:00] "POST /admin/ HTTP/1.1" 302 0 [26/Oct/2005 09:44:00] "GET /admin/ HTTP/1.1" 200 5899 Error in atexit._run_exitfuncs: Traceback (most recent call last): File "/usr/local/python-2.4.1/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/local/python-2.4.1/lib/python2.4/threading.py", line 636, in __exitfunc self._Thread__delete() File "/usr/local/python-2.4.1/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: 1076103392 Error in sys.exitfunc: Traceback (most recent call last): File "/usr/local/python-2.4.1/lib/python2.4/atexit.py", line 24, in _run_exitfuncs func(*targs, **kargs) File "/usr/local/python-2.4.1/lib/python2.4/threading.py", line 636, in __exitfunc self._Thread__delete() File "/usr/local/python-2.4.1/lib/python2.4/threading.py", line 522, in __delete del _active[_get_ident()] KeyError: 1076103392 }}} adrian Tekhne   0 0 0 0 0 0
699 2005-10-26 19:55:17 2006-10-22 16:08:45 2019-06-24 00:22:43.215674 Unreviewed closed contrib.admin defect normal   invalid unique_together - raise an error message unique_together should raise an error message, instead of show: {{{ There's been an error: Traceback (most recent call last): ... ... ... OperationalError: columns foo, bar are not unique }}} adrian Bless   0 0 0 0 0 0
701 2005-10-27 15:46:45 2006-10-22 15:51:49 2019-06-24 00:22:44.513337 Unreviewed closed contrib.admin defect normal   fixed admin doc tool doesn't work with custom fields {{{django.contrib.admin.views.doc.get_readable_field_data_type()}}} was still {{{using field.__class__.__name__}}} Change it to use field.get_internal_type() adrian jkocherhans@mac.com   0 0 0 0 0 0
703 2005-10-27 21:23:59 2006-10-22 16:15:23 2019-06-24 00:22:45.745872 Unreviewed closed Core (Other) enhancement normal   fixed Decorators to restrict views based on REQUEST_METHOD would be great. Sometimes it's great to restrict whether views run based on the REQUEST_METHOD of the request being processed. If code expects to read from request.POST, the request method should be enforceable. jacob cygnus@cprogrammer.org   0 0 0 0 0 0
707 2005-10-30 12:46:19 2006-10-22 16:19:57 2019-06-24 00:22:48.318860 Unreviewed closed Template system enhancement normal   fixed Add support for optional filter arguments Right now a filter can either have an argument or not have it. And there is no way to write a filter which would have a default value for an argument. It would be neat if one could write a filter with an argument which assumes a default value if the user does not specify the argument :) adrian wojtek@brandlay.com   0 0 0 0 0 0
724 2005-11-04 04:51:28 2006-10-22 16:30:50 2019-06-24 00:22:59.210354 Unreviewed closed Core (Other) defect minor   fixed get_next_by_pub_date/get_previous_by_pub_date model methods only see 1 item for each day. The model.get_next_by_pub_date() and model.get_previous_by_pub_date() methods appear to only see one item for each day. For example, I have a blog.posts model in which pub_date is a DateTimeField. If there are multiple posts in one day, the above methods will only see the first post for each day, and then skip to the next day. This is clearly wrong behaviour; the method should retrieve the next item by date whether it was created the same day or not. Example: {{{ item1.pub_date = 2005/01/01 12:00 item2.pub_date = 2005/01/02 8:00 item3.pub_date = 2005/01/02 9:00 item1.get_next… = item2 item2.get_next… = None item3.get_prev… = item1 }}} adrian mattycakes@gmail.com   0 0 0 0 0 0
733 2005-11-05 09:22:30 2006-10-22 16:19:47 2019-06-24 00:23:04.956349 Unreviewed closed Core (Other) defect normal   fixed small addition to i18n.txt with regard to caching The i18n.txt (reading much smoother than my version!) should point out that the LocaleMiddleware needs to be _after_ the CacheMiddleware (if used), because it modifies the Vary-header. Otherwise the accept-language header wouldn't be used correctly. And it is a case for #730: the LocaleMiddleware needs in process_request access to the session, so must come _after_ SessionMiddleware. But SessionMiddleware and LocaleMiddleware must come _after_ CacheMiddleware, so that the caching sees the Vary header in process_response (due to the reversed order of middleare). That's exactly the kind of "order deadlock" the user can't solve without giving explicit middleware order. I copied the above text to #730, too. adrian hugo   0 0 0 0 0 0
752 2005-11-07 19:04:43 2006-10-22 16:07:53 2019-06-24 00:23:16.966941 Unreviewed closed Metasystem enhancement normal   wontfix Base Classes for Trees Base classes, what could efficiently handle large tree-like structures. * Recursive handling (delete, move, rebuild, and so) * Querying for children in some ways, with filters * Nearest * By path * Level[s] slice * Parents * Node data types handling. Mapping to other classes. I think it would be 2 classes: one for handling tree structure and one base class for node items. adrian dp_wiz   0 0 0 0 0 0
755 2005-11-08 16:31:02 2006-10-22 15:50:33 2019-06-24 00:23:18.865688 Unreviewed closed Template system enhancement normal   invalid Add "appendable" blocks to the current "overrideable" ones It would be nice to have a block tag where you can append to the current contents of the block, instead of replacing them. This is useful if you need to add a JS file for your template, and the parent template block already has useful links in it (most likely because it overrided yet another parent template). Since you can have nested inheritance, this make preserving whatever the inmediate parent set possible. adrian GomoX <gomo AT datafull DOT com>   0 0 0 0 0 0
763 2005-11-10 08:42:25 2006-10-22 16:29:00 2019-06-24 00:23:24.050863 Unreviewed closed Core (Cache system) defect normal   fixed [patch] fix for 'file' cache {{{os.remove()}}} blows with {{{OSError}}}, which was not caught. jacob eugene@lazutkin.com   0 1 0 0 0 0
768 2005-11-10 18:59:23 2006-10-22 15:49:11 2019-06-24 00:23:27.143141 Unreviewed closed Core (Other) defect major   fixed tests errors on winxp tests errors on winxp (czech locale settings) - see errors.txt adrian radek   0 0 0 0 0 0
773 2005-11-12 06:18:55 2006-10-22 16:04:40 2019-06-24 00:23:30.287107 Unreviewed closed Documentation defect trivial   fixed CACHE_MIDDLEWARE_GZIP is documented but not used {{{CACHE_MIDDLEWARE_GZIP}}} is obsolete, but it's still documented as valid option in http://www.djangoproject.com/documentation/cache/#the-per-site-cache. jacob eugene@lazutkin.com   0 0 0 0 0 0
780 2005-11-13 15:17:22 2006-10-22 16:20:17 2019-06-24 00:23:34.722725 Unreviewed closed Documentation defect minor   fixed wrong closing tag in an example of the modpython documentation In the '''Serving media file''' section of the modpython documentation the following example has a wrong closing tag: {{{ <LocationMatch "\.(jpg|gif|png)$"> SetHandler None </Location> }}} The correct tag is </LocationMatch> jacob jhernandez   0 0 0 0 0 0
782 2005-11-13 20:49:03 2006-10-22 15:51:55 2019-06-24 00:23:36.009700 Unreviewed closed *.djangoproject.com defect normal   fixed "Django at a glance" has wrong download link The page http://www.djangoproject.com/documentation/overview/, titled "Django at a glance", has a link at the bottom that should link to the Django download page. Instead, it links to the Documentation page. It's in the following HTML snippet: {{{ <p>The next obvious steps are for you to <a class="reference" href="http://www.djangoproject.com/documentation/">download Django</a>, ... }}} jacob frederik@pandora.be   0 0 0 0 0 0
796 2005-11-14 23:55:39 2006-10-22 16:05:33 2019-06-24 00:23:44.827050 Unreviewed closed Core (Other) defect normal   fixed Return no permission rather than a traceback for anonymous users Quick and easy patch: {{{ Index: django/core/extensions.py =================================================================== --- django/core/extensions.py (revision 1234) +++ django/core/extensions.py (working copy) @@ -55,7 +55,8 @@ def __getitem__(self, perm_name): return self.user.has_perm("%s.%s" % (self.module_name, perm_name)) def __nonzero__(self): - return self.user.has_module_perms(self.module_name) + return hasattr(self.user, 'has_module_perms') \ + and self.user.has_module_perms(self.module_name) class PermWrapper: def __init__(self, user): }}} adrian garthk   0 0 0 0 0 0
800 2005-11-15 12:23:11 2006-10-22 15:49:32 2019-06-24 00:23:47.426683 Unreviewed closed Database layer (models, ORM) defect normal   fixed startswith lookup type does not work with underscore Quite strange. Using SQLite 3.2.7, django r1238. {{{ #!python >>> for i in attributes.get_iterator(key__startswith = 'threaded'): print i ... threaded_collector.count >>> for i in attributes.get_iterator(key__startswith = 'threaded_'): print i ... >>> }}} I also tested with {{{foo_}}} and {{{foo}}} and it exhibited the same behaviour. adrian django-form@swapoff.org   0 0 0 0 0 0
817 2005-11-16 15:44:24 2006-10-22 15:53:19 2019-06-24 00:23:58.481304 Unreviewed closed Metasystem defect normal   duplicate problem with column-quoting and "computed columns" When using the registered comments, an SQL is build that produces the following error: ProgrammingError at /forum/technik/waschmaschinen/miele-superfix/discussion/ ERROR: column "SELECT COUNT(*) FROM comments_karma WHERE comments_karma.commen" does not exist SELECT "comments"."id","comments"."user_id","comments"."content_type_id","comments"."object_id","comments"."headline","comments"."comment","comments"."rating1","comments"."rating2","comments"."rating3","comments"."rating4","comments"."rating5","comments"."rating6","comments"."rating7","comments"."rating8","comments"."valid_rating","comments"."submit_date","comments"."is_public","comments"."ip_address","comments"."is_removed","comments"."site_id","auth_users"."id","auth_users"."username","auth_users"."first_name","auth_users"."last_name","auth_users"."email","auth_users"."password_md5","auth_users"."is_staff","auth_users"."is_active","auth_users"."is_superuser","auth_users"."last_login","auth_users"."date_joined","content_types"."id","content_types"."name","content_types"."package","content_types"."python_module_name","packages"."label","packages"."name","sites"."id","sites"."domain","sites"."name",("SELECT COUNT(*) FROM comments_karma WHERE comments_karma.comment_id=comments.id AND score=1") AS "_karma_total_good",("SELECT COUNT(*) FROM comments_karma WHERE comments_karma.comment_id=comments.id AND score=-1") AS "_karma_total_bad" FROM "comments","content_types" "t1","content_types" "t5","auth_users","content_types","packages","sites" WHERE "comments"."content_type_id" = "t1"."id" AND "comments"."content_type_id" = "t5"."id" AND "t1"."package" = 'forum' AND "comments"."site_id" = 1 AND "comments"."object_id" = 3 AND "t5"."python_module_name" = 'groups' AND "comments"."user_id" = "auth_users"."id" AND "comments"."content_type_id" = "content_types"."id" AND "content_types"."package" = "packages"."label" AND "comments"."site_id" = "sites"."id" ORDER BY "comments"."submit_date" ASC This looks like there is column-quoting even done on computed columns like … adrian hugo   0 0 0 0 0 0
827 2005-11-17 13:51:23 2006-10-22 16:27:51 2019-06-24 00:24:04.816553 Unreviewed closed contrib.admin enhancement normal   fixed Admin page should automatically replace _s with ' 's to make a short_description   adrian aaronsw   0 0 0 0 0 0
829 2005-11-17 14:47:44 2006-10-22 16:25:14 2019-06-24 00:24:06.100512 Unreviewed closed contrib.admin defect normal   duplicate __repr__ overloaded for short_descriptions in admin interface The admin interface abuses __repr__ to get its short_descriptions for listing objects. Instead, it should have a new function (perhaps short_description or something like that) to generate these things. Then, perhaps by default, __repr__ can be '<'+classname+': '+short_description+'>' which is much more appropriate for the REPL situations in which __repr__ is traditionally used. If you have to use a special function, perhaps it could be __str__. adrian aaronsw   0 0 0 0 0 0
836 2005-11-18 18:20:15 2006-10-22 16:27:59 2019-06-24 00:24:10.518336 Unreviewed closed Translations enhancement normal   fixed Update slovak ( sk ) translation for new-admin Update slovak ( sk ) translation for new-admin hugo vlado@labath.org   0 0 0 0 0 0
843 2005-11-19 14:57:57 2006-10-22 15:49:02 2019-06-24 00:24:14.973166 Unreviewed closed Translations enhancement normal new-admin fixed Update slovak (sk) translation new-admin Update slovak (sk) translation new-admin hugo vlado@labath.org   0 0 0 0 0 0
844 2005-11-19 22:11:55 2006-10-22 16:03:45 2019-06-24 00:24:15.621054 Unreviewed closed contrib.admin defect normal new-admin fixed new_admin: add_stage_new not defined When using the save_as_new feature, I get the following error: {{{ NameError at /admin/snippets/templates/7/ global name 'add_stage_new' is not defined Request Method: POST Request URL: http://admin.rfc1437.de/admin/snippets/templates/7/ Exception Type: NameError Exception Value: global name 'add_stage_new' is not defined Exception Location: /home/rfc1437/project/django/contrib/admin/views/main.py in change_stage, line 488 }}} rjwittams hugo   0 0 0 0 0 0
847 2005-11-20 05:53:31 2006-10-22 15:47:47 2019-06-24 00:24:17.545427 Unreviewed closed Metasystem defect normal   invalid users.create_user fails if User is subclassed using replaces_module = 'auth.users' Given the following model: {{{ class User(auth.User): class META: admin = meta.Admin() replaces_module = 'auth.users' foo = meta.URLField(blank=True) }}} ¨django-admin.py sql auth¨ creates the correct output {{{ CREATE TABLE "auth_users" ( "id" integer NOT NULL PRIMARY KEY, "date_joined" datetime NOT NULL, "last_login" datetime NOT NULL, "is_superuser" bool NOT NULL, "is_active" bool NOT NULL, "is_staff" bool NOT NULL, "password_md5" varchar(32) NOT NULL, "email" varchar(75) NOT NULL, "last_name" varchar(30) NOT NULL, "first_name" varchar(30) NOT NULL, "username" varchar(30) NOT NULL UNIQUE, "foo" varchar(200) NOT NULL ); }}} But an attempt to create a superuser with django-admin fails. A debugging session yields the following: {{{ eric@home[bbs]|1> %pdb Automatic pdb calling has been turned ON eric@home[bbs]|2> from django.models.auth import users eric@home[bbs]|3> users.create_user("foo", "bar@baz.com", "secret") --------------------------------------------------------------------------- exceptions.AttributeError Traceback (most recent call last) /home/eric/django/bbs/<console> /usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/models/auth.py in _module_create_user(username, email, password) 181 now = datetime.datetime.now() 182 user = User(None, username, '', '', email.strip().lower(), password_md5, False, True, False, now, now) --> 183 user.save() 184 return user 185 /usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/utils/functional.py in _curried(*moreargs, **morekwargs) 2 def _curried(*moreargs, **morekwargs): ----> 3 return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) 4 return _curried 5 6 def lazy(func, *resultclasses): /usr/lib/python2.4/site-packages/django-1.0.0-py2.4.egg/django/core/meta/__i… adrian EABinGA   0 0 0 0 0 0
853 2005-11-20 12:32:07 2006-10-22 16:06:22 2019-06-24 00:24:21.419534 Unreviewed closed Metasystem defect normal   worksforme Django has high start costs, weight My biggest issue with Django right now is that it's so hard and heavy to get started. Here are all the administrative (non-code writing) things you have to do: 1. Install Django. 2. Run startproject, which creates six things. 3. Create a database. 4. Update several variables to use the database. 5. Update your PYTHONPATH variable. 6. Update your DJANGO_SETTINGS_MODULE variable. 7. Run init. 8. Run startapp, creating six more things. 9. Update INSTALLED_APPS. 10. Run install. 10 steps, 12 files. For comparison, here are the only two necessary steps: 1. Install Django. 2. Give Django the URL to an existing database (ala SQLObject) and a prefix so it doesn't reuse any tables. Imagine how much simpler that tutorial document would be. Imagine how many more people would just start using Django, instead of putting it off or giving up. Imagine how people would start using bits and pieces of Django everywhere, instead of just their website. I'll follow by posting tickets with more concrete suggestions, but I'd like to propose this sort of simplicity as a new design principle. You shouldn't have to fit your code into Django, Django should fit into your code. adrian aaronsw   0 0 0 0 0 0
862 2005-11-21 01:48:04 2006-10-22 16:16:57 2019-06-24 00:24:27.232861 Unreviewed closed Metasystem defect normal   wontfix Which field caused method_save to bomb out? If method_save fails whilst trying to call pre_save on a field, it can be tricky to figure out which field caused the problem without wading to exactly the right place in the stack frame or riddling meta\__init.py__ with debugging code. To save everyone the effort, I've got a patch that'll append a descriptive message to the exception's arguments so the errant field name is obvious and easy to find from the last line of the traceback. adrian garthk   0 0 0 0 0 0
873 2005-11-22 06:02:56 2006-10-22 16:19:48 2019-06-24 00:24:34.355194 Unreviewed closed Core (Other) defect minor   wontfix handler404 and handler500 don't get applied within a URLconf include() When a 404 error happens in a view that has been {{{include()}}}d from another URLconf, the {{{handler404}}} from the uppermost URLconf is called -- not the {{{handler404}}} from the lowermost URLconf. adrian adrian   0 0 0 0 0 0
878 2005-11-22 18:08:01 2006-10-22 16:08:58 2019-06-24 00:24:37.558748 Unreviewed closed Core (Other) defect normal   fixed URLconf regexp captures should be passed as *args Currently you have to write (?P<foo>) to get a capture out of a URL regular expression and into your function. Since this seems to be what you almost always want to do, why not just treat it like a normal regular expression and pass on every capture that doesn't start with ?: adrian aaronsw   0 0 0 0 0 0
898 2005-11-24 12:07:39 2006-10-22 16:17:02 2019-06-24 00:24:50.434529 Unreviewed closed Translations enhancement normal   fixed update slovak (sk) translation update slovak (sk) translation hugo vlado@labath.org   0 0 0 0 0 0
913 2005-11-25 22:34:29 2006-10-22 16:26:52 2019-06-24 00:24:59.940004 Unreviewed closed contrib.admin defect normal   fixed [patch] incorrect `list_filter` field error message a bit stranger than necessary See backtrace and model file. It breaks when I try to see a list of restaurants. adrian eugene@lazutkin.com   0 1 0 0 0 0
917 2005-11-26 04:28:43 2006-10-22 16:13:17 2019-06-24 00:25:02.448671 Unreviewed closed contrib.admin defect normal   fixed [patch]New admin change_list should be looked up in the app templates The change_list template should be customisable like the change_form template on a per-app basis. adrian django@kieranholland.com   0 1 0 0 0 0
925 2005-11-26 21:17:45 2006-10-22 16:04:23 2019-06-24 00:25:07.541373 Unreviewed closed Core (Other) enhancement normal   fixed [patch] Refactor functionality of DjangoContext into 'processors' which can be replaced or added to The attached patch is the result of this discussion on the dev list: http://groups.google.co.uk/group/django-developers/browse_frm/thread/4a61014b42a72177/e65f1aee2a58cb73?tvc=1&q=request_processors+django#e65f1aee2a58cb73 == Summary == The patch does the following things: 1. Refactors the functionality of DjangoContext into a bunch of 'request processors'. These are callables that take a request object and return a dictionary to be added to the context. 2. Allows you to override the request processors that are used by default by changing the REQUEST_PROCESSORS setting 3. Adds a 'processors' keyword argument to generic views and DjangoContext to allow additional processors to be defined on a per view basis. == Description == Request processors are to template tags what the view function is to templates -- both views and processors process the request object and create data to be added to the context. (Views are different from processors in that they are responsible for returning the HttpResponse object as well, giving them full control and the option to not use the templating system at all etc). Processors are needed to do the processing needed by custom template tags and included sub-templates. The addition of these processors makes it possible to have things like stateful template tags, or other tags that need data from the request object, and have them work in generic views. The patch is totally backwards compatible. == Advantages == * DjangoContext is no longer tied to built-in sub-systems. * With this patch Django's authentication system becomes more decoupled and replaceable. By simply adding your own version of "django.core.processors.auth" in the REQUEST_PROCESSORS setting, you can plug in your own system and have it available in the template context by default. (In fact, if you wrote an appropriate middleware could replace the built-in one altogether with this patch in place, AFAICT) * Part of ticket #667 would be made redundant by this patch (i.e. need for callables in… adrian L.Plant.98@cantab.net   0 1 0 0 0 0
935 2005-11-27 20:12:55 2006-10-22 16:25:58 2019-06-24 00:25:13.772026 Unreviewed closed contrib.admin defect normal   duplicate weird interaction between edit_inline and OneToOneField causes adding through admin to fail if I take a model like: {{{ class Account(meta.Model): user = meta.OneToOneField(auth.User, core=True) kid_name = meta.CharField(...) }}} which extends the User model, and then have: {{{ class Transaction(meta.Model): account = meta.ForeignKey(Account) value = meta.FloatField(max_digits=10,decimal_places=2, default=0) date = meta.DateField(default=datetime.datetime.today()) note = meta.CharField(maxlength=200, default='') }}} to associate many transactions w/ each account, everything works fine, including the admin pages. If I add "edit_inline=True, core=True" to the account ForeignKey description, then creating Accounts through the admin interface fails with an error: {{{ AttributeError at /admin/accounts/accounts/add/ 'Account' object has no attribute 'user' Request Method: POST Request URL: http://localhost:8000/admin/accounts/accounts/add/ Exception Type: AttributeError Exception Value: 'Account' object has no attribute 'user' Exception Location: /Users/davidascher/django/django/core/meta/__init__.py in manipulator_save, line 1754 }}} The request object looks like: <DjangoRequest GET:{}, POST:{'transaction.1.id': [''], 'transaction.1.date': ['2005-11-27'], 'transaction.2.value': ['0'], '_addanother': ['Save and add another'], 'transaction.0.date': ['2005-11-27'], 'transaction.2.note': [''], 'transaction.1.note': [''], 'balance_at_last_transaction': ['0'], 'last_transaction_date': ['2005-11-27'], 'transaction.0.value': ['0'], 'currency': ['CAD'], 'transaction.2.id': [''], 'user': ['1'], 'kid_name': ['asdas'], 'transaction.0.id': [''], 'transaction.2.date': ['2005-11-27'], 'pub_date': ['2005-11-27'], 'transaction.1.value': ['0'], 'transaction.0.note': ['']}, COOKIES:{'hotclub': 'a8625192d1938973fe717071e5202194'}, META:{'CONTENT_LENGTH': '420', 'CONTENT_TYPE': 'application/x-www-form-urlencoded', 'DJANGO_SETTINGS_MODULE': 'bankofdad.settings', 'GATEWAY_INTERFACE': 'CGI/1.1', 'GDK_USE_XFT': '1', 'HOME': '/Users/davidascher', 'HTTP_ACCEPT': 'text/xml,… adrian David Ascher <david.ascher@gmail.com>   0 0 0 0 0 0
944 2005-11-28 09:28:52 2006-10-22 15:54:06 2019-06-24 00:25:19.481131 Unreviewed closed Core (Other) enhancement normal   fixed allow app to specify a template for login/logout screens probably should make LOGIN_URL & REDIRECT_TO settings in the config. {{{ Index: login.py =================================================================== --- login.py (revision 1474) +++ login.py (working copy) @@ -8,7 +8,7 @@ REDIRECT_FIELD_NAME = 'next' LOGIN_URL = '/accounts/login/' -def login(request): +def login(request, template_name='/registration/login'): "Displays the login form and handles the login action." manipulator = AuthenticationForm(request) redirect_to = request.REQUEST.get(REDIRECT_FIELD_NAME, '') @@ -24,18 +24,18 @@ else: errors = {} request.session.set_test_cookie() - return render_to_response('registration/login', { + return render_to_response(template_name , { 'form': formfields.FormWrapper(manipulator, request.POST, errors), REDIRECT_FIELD_NAME: redirect_to, 'site_name': sites.get_current().name, }, context_instance=DjangoContext(request)) -def logout(request, next_page=None): +def logout(request, next_page=None, template_name ='registration/logged_out'): "Logs out the user and displays 'You are logged out' message." try: del request.session[users.SESSION_KEY] except KeyError: - return render_to_response('registration/logged_out', context_instance=DjangoContext(request)) + return render_to_response(template_name, context_instance=DjangoContext(request)) else: # Redirect to this page until the session has been cleared. return HttpResponseRedirect(next_page or request.path) }}} adrian Ian@holsman.net   0 0 0 0 0 0
962 2005-11-29 23:44:28 2006-10-22 16:16:58 2019-06-24 00:25:30.829119 Unreviewed closed Core (Other) defect normal   fixed [patch] Filter registration decorator is missing a return statement See attached patch against r1496. adrian django@kieranholland.com   0 1 0 0 0 0
979 2005-12-02 11:58:48 2006-10-22 16:07:41 2019-06-24 00:25:41.522396 Unreviewed closed Core (Other) enhancement normal   wontfix add support for the akismet spam scanner to free comments? There is a [http://www.kemayo.com/python/akismet/akismet.py python interface] available to the [http://akismet.com akismet spam] scanner. Maybe this could be integrated into the free comment system? This would allow to spam-scan new comments if the server admin adds a wordpress.com API key and so would allow blogs and other sites to do spam scanning on comments. adrian hugo   0 0 0 0 0 0
990 2005-12-04 14:10:11 2006-10-22 16:22:16 2019-06-24 00:25:48.491541 Unreviewed closed Translations defect normal   fixed Update Simplified Chinese Translation Update Simplified Chinese Translation hugo limodou@gmail.com   0 0 0 0 0 0
998 2005-12-05 20:12:35 2006-10-22 15:49:13 2019-06-24 00:25:53.518957 Unreviewed closed Core (Other) defect normal   fixed Exception in views/debug.py There's an error in the {{{get_template_exception_info}}} function that causes the interpreter to raise an {{{UnboundLocalError}}} in the marginal case that the template being debugged has only one line. This is caused by the {{{before}}}, {{{during}}} and {{{after}}} variables not being assigned. This can be fixed by inserting the line {{{before = during = after = ""}}} ...before the {{{for}}} loop (line 26, django/views/debug.py). This bug is present in revision 1550. adrian andy@jadedplanet.net   0 0 0 0 0 0
1012 2005-12-06 23:23:25 2006-10-22 15:59:01 2019-06-24 00:26:02.386421 Unreviewed closed Core (Other) defect normal master wontfix [patch] ManyToMany not working in Manipulators when the form control isn't of the same style as the control in the admin ManyToMany not working in Manipulators when the form control isn't of the same style as the control in the admin For instance, if raw_id_admin=True, the admin will show an editbox, but if you use a select-multiple in your app, manipulator.save() will only save the first selected item. A patch has been submitted. adrian Gustavo Picon <gpicon@aureal.com.pe>   0 1 0 0 0 0
1014 2005-12-07 01:21:15 2006-10-22 16:26:20 2019-06-24 00:26:03.632693 Unreviewed closed Metasystem enhancement normal   fixed Allow _pre_save and _pre_delete to stop save / delete It'd be useful in some situations if a _pre_save or _pre_delete hook could signal that the saving or deleting shouldn't go ahead. Throwing an exception isn't the best way to handle it if it's not actually exceptional behaviour. For instance, in a version control system, on _pre_delete you might wish to alter the status to 'deleted' but stop the actual object from being deleted. adrian django@illuminosity.net   0 0 0 0 0 0
1024 2005-12-08 01:15:13 2006-10-22 16:06:26 2019-06-24 00:26:09.861814 Unreviewed closed contrib.admin defect normal   worksforme Auto-reloading is not working in development server. I try the tutorial#2, the admin part. When I change the cose e.g. the polls field order, I refresh the browser, the change not reflect in browser, but when I stop and start the server again and refresh the browser, it shows the changed content adrian theepraphn@gmail.com   0 0 0 0 0 0
1025 2005-12-08 03:21:11 2006-10-22 15:48:13 2019-06-24 00:26:10.474838 Unreviewed closed Translations enhancement normal   fixed update slovak (sk) translation update slovak (sk) translation hugo vlado@labath.org   0 0 0 0 0 0
1034 2005-12-09 09:37:08 2006-10-22 16:24:00 2019-06-24 00:26:16.134520 Unreviewed closed Database layer (models, ORM) defect normal   fixed Object save fails for models with mixed-case names using postgresql Using a model named 'myApp.py', the 0.90 build fails the first time I try to save an object to the database (postgresql) with this message: {{{ ProgrammingError at /admin/myApp/units/add/ ERROR: relation "myapp_units_id_seq" does not exist SELECT CURRVAL('myApp_units_id_seq') }}} The faulty code seems to be in django\core\db\backends\postgresql.py around line 69: {{{ cursor.execute("SELECT CURRVAL('%s_%s_seq')" % (table_name, pk_name)) }}} The proper SQL statement to handle the mixed-case name should be (note the double quotes): {{{ SELECT CURRVAL('"myApp_units_id_seq"') }}} So this code would probably work (haven't tried): {{{ cursor.execute("SELECT CURRVAL('\"%s_%s_seq\"')" % (table_name, pk_name)) }}} Renaming myApp to myapp fixed the problem. This problem didn't occur with previous builds. Other lines of code might have the same missing double quotes. adrian rfugger at gmail dot com   0 0 0 0 0 0
1055 2005-12-13 20:28:36 2006-10-22 16:00:31 2019-06-24 00:26:29.272279 Unreviewed closed Database layer (models, ORM) defect normal   fixed Models should have better default __str__() and __repr__() methods Right now, the default !__repr!__() method as defined in the Model class (in django/core/meta/!__init!__.py) looks like: {{{ #!python def __repr__(self): return '<%s object>' % self.__class__.__name__ }}} I think we should have at least a !__str!__() definition and a better !__repr!__(), which includes at least the object id, so that when using the interactive interpreter, you can tell an object from another. Something like: {{{ #!python def __str__(self): return '%s %s' % (self.__class__.__name__, self.id) def __repr__(self): return '<%s object ID=%s>' % (self.__class__.__name__, self.id) }}} adrian GomoX <gomo@datafull.com>   0 0 0 0 0 0
1064 2005-12-15 06:01:38 2006-10-22 15:47:48 2019-06-24 00:26:34.915003 Unreviewed closed contrib.admin defect normal   fixed [patch] ManyToManyField pointing at a model that contains a OneToOneField is broken If you have a ManyToManyField pointing at a model that uses a OneToOneField, then the model with the OneToOneField has no attribute "id" which causes the code in method_set_many_to_many to fail due to it relying on the presence of an attribute "id". Luminosity helped figure out the correct fix and I will attach the patch that fixes the problem. mtredinnick bruce@cubik.org   0 1 0 0 0 0
1067 2005-12-15 17:54:32 2006-10-22 16:19:35 2019-06-24 00:26:36.788108 Unreviewed closed Template system enhancement normal   fixed "Spaceless" tag, removes spaces between html nodes This is a cool tag that I think should be added to the defaults, it removes spaces between HTML tags. This is a problem many designers has banged their heads against many walls over, where spaces between tags show up even though they are clearly not inteded to be there. So this: {{{ {% spaceless %} <a href='#'> <img src='something.jpg' border='0'/> </a> <a href='#'> <img src='something-else.jpg' border='0'/> </a> {% endspaceless %} }}} Renders as: {{{ <a href='#'><img src='something.jpg' border='0'/></a><a href='#'><img src='something-else.jpg' border='0'/></a> }}} {{{ import re re_spaceless = re.compile(">\s+<") def do_spaceless(parser, token): nodelist = parser.parse(('endspaceless',)) parser.delete_first_token() return SpacelessNode(nodelist) class SpacelessNode(template.Node): def __init__(self, nodelist): self.nodelist = nodelist def render(self, context): rendered = self.nodelist.render(context).strip() return re_spaceless.sub("><", rendered) }}} adrian brantley (deadwisdom@gmail.com)   0 0 0 0 0 0
1068 2005-12-15 18:43:26 2006-10-22 16:22:27 2019-06-24 00:26:37.413547 Unreviewed closed Database layer (models, ORM) defect minor   invalid Silly bug in ForiegnKey This works when it probably shouldn't {{{ from django.models import places ... class MyModel(meta.Model): place = meta.ForeignKey(places.Place) }}} If someone accidentally uses the app module's Place class in a foreign key, everything seems to work except the place object will not get the get_mymodel_... methods. It should throw an error if that occurs otherwise it's not obvious that something is wrong. adrian Eric Moritz   0 0 0 0 0 0
1072 2005-12-16 10:49:12 2006-10-22 16:11:54 2019-06-24 00:26:39.969622 Unreviewed closed Documentation enhancement trivial   invalid Does the server code.djangoproject.com have enscript instaled? Sorry to file a bug just for this, but I recently added a wiki page to Django's trac env, [wiki:SimpleBashScriptToSetupDevelopmentEnvironment Simple Bash Script To Setup Development Environment], that would be neater if trac had '''`sh`''' syntax highlight, and trac needs enscript installed on the server running it to correctly display it. Example: A code block usin' '''`sh`''' syntax coloring, wich you won't see because you don't have enscript {{{ #!sh #!/bin/bash VAR="This is a Bash Script" }}} And now a plain monospace block with the same bash script but not usin' the '''`sh(#!sh)`''' [wiki:WikiProcessors WikiProcessor]. So this ticket is actually to see if you could install enscript on your server, Thanks! {{{ #!/bin/bash VAR="This is a Bash Script" }}} jacob Pedro Algarvio <ufs@ufsoft.org>   0 0 0 0 0 0
1074 2005-12-16 23:12:15 2006-10-22 16:14:27 2019-06-24 00:26:41.236181 Unreviewed closed Core (Management commands) defect normal   fixed createsuperuser broken on magic-removal branch manage.py createsuperuser fails becuase {{{import datetime}}} is missing from the top of django.models.auth adrian Joseph Kocherhans <jkocherhans@mac.com>   0 0 0 0 0 0
1076 2005-12-17 22:01:29 2006-10-22 16:08:52 2019-06-24 00:26:42.532990 Unreviewed closed Internationalization defect normal   invalid [patch] Safari has a bug that prevents usage of JS i18n interpolate function Safari has a bug in handling string.replace with a function as the second parameter. That leads to weird output or no translation. This bug needs to be fixed on Safaris side of the things though - unless someone finds a solution in pure JavaScript that works on all browsers (and is fast enough). Yes, the bug is filed for Safari. So this is either to remind me that the problem exist or to find a workaround (if fixing Safari takes too long). hugo hugo   0 1 0 0 0 0
1078 2005-12-18 17:37:41 2006-10-22 15:45:39 2019-06-24 00:26:43.792468 Unreviewed closed Translations defect normal   fixed cs translation updated   hugo radek   0 0 0 0 0 0
1086 2005-12-19 14:18:11 2006-10-22 15:49:50 2019-06-24 00:26:48.835846 Unreviewed closed *.djangoproject.com defect normal   invalid [patch] UnicodeDecodeError: 'utf8' codec can't decode byte 0xa3 in position 28: unexpected code byte {{{UnicodeDecodeError: 'utf8' codec can't decode byte 0xa3 in position 28: unexpected code byte}}} I got this error today. I've attached a patch to make it ignore utf-8 decoding errors. {{{ Traceback (most recent call last): File "/home/j/jason/django_src/django/core/handlers/base.py", line 74, in get_response response = callback(request, *callback_args, **callback_kwargs) File "/home/j/jason/django_src/django/contrib/syndication/views.py", line 20, in feed feedgen = f(slug, request.path).get_feed(param) File "/home/j/jason/django_src/django/contrib/syndication/feeds.py", line 95, in get_feed feed.add_item( UnicodeDecodeError: 'utf8' codec can't decode byte 0xa3 in position 28: unexpected code byte }}} adrian Esaj   0 1 0 0 0 0
1090 2005-12-19 22:44:04 2006-10-22 15:56:59 2019-06-24 00:26:51.366068 Unreviewed closed contrib.admin enhancement normal   fixed [patch] allow templates that extend admin/base to override the H1 in #content   adrian Joseph Kocherhans <jkocherhans@mac.com>   0 1 0 0 0 0
1111 2005-12-24 07:23:41 2006-10-22 16:20:35 2019-06-24 00:27:04.822625 Unreviewed closed Documentation defect normal   fixed Documentation Error in custom validator example From the documentation as it is at the time of this bug report: {{{ from django.core import validators, formfields class ContactManipulator(formfields.Manipulator): def __init__(self): self.fields = ( # ... snip fields as above ... formfields.EmailField(field_name="to", validator_list=[self.isValidToAddress]) ) def isValidToAddress(self, field_data, all_data): if not field_data.endswith("@example.com"): raise ValidationError("You can only send messages to example.com e-mail addresses.") }}} Calls to ValidationError be written as such: {{{ raise validators.ValidationError(...) }}} ValidationError by itself is undefined. jacob afarnham@gmail.com   0 0 0 0 0 0
1126 2005-12-27 14:18:21 2006-10-22 15:47:19 2019-06-24 00:27:14.183399 Unreviewed closed Internationalization enhancement normal   fixed i18n: Japanese (ja) django.po   hugo makoto tsuyuki   0 0 0 0 0 0
1131 2005-12-28 19:33:43 2006-10-22 16:14:05 2019-06-24 00:27:17.416782 Unreviewed closed Core (Other) defect trivial   fixed Add a __repr__ to MultiValueDict At the moment, MultiValueDict inherits its __repr__ from Python's dictionary type. This is confusing, as it leads to the misunderstanding demonstrated in #1130. We should add a custom __repr__ something like this: {{{ def __repr__(self): return "<MultiValueDict: %s>" % dict.__repr__(self) }}} adrian Simon Willison   0 0 0 0 0 0
1132 2005-12-28 22:15:00 2006-10-22 16:03:54 2019-06-24 00:27:18.065308 Unreviewed closed Core (Other) enhancement normal   duplicate [patch] CurrentUserField and manipulator changes This isn't as high level as I would like, but it works. It's also still usable without access to a request object as well. It feels like a hack to me, but no more so than DateField's auto_now and auto_add_now. I played around with using events, and even with RuleDispatch, but this was the simplest change that worked. It doesn't work for inline objects yet though. I figured I'd get some feedback before I waste my time. Here's how to use it: {{{ class Article(meta.Model): title = meta.CharField(maxlength=100) body = meta.TextField() added_by = meta.CurrentUserField(update_on_edit=False) # only save the current user in add_stage edited_by = meta.CurrentUserField() # update_on_edit defaults to True }}} adrian jkocherhans <jkocherhans@mac.com>   0 1 0 0 0 0
1145 2005-12-30 23:32:43 2006-10-22 16:08:24 2019-06-24 00:27:26.177507 Unreviewed closed Template system defect normal   fixed [patch] added tests for filters and fixed two bugs with filters The patch adds tests for the defaultfilters module, and fixes two bugs discovered while doing the tests: * a bug in 'slice' with argument '0' (caused by use of the 'a and b or c' shortcut) * a rounding error in the timesince function (timesince(now - 1 day) came out as '23 hours, 59 minutes') There remains an issue with the 'timesince' function -- is the 'milliseconds' option meant to be there? It seems strange, since 'seconds' isn't, and it isn't i18nised. Also, some doc strings have also been updated. adrian L.Plant.98@cantab.net   0 1 0 0 0 0
1186 2006-01-08 02:37:51 2006-10-22 16:12:08 2019-06-24 00:27:52.204430 Unreviewed closed Database layer (models, ORM) defect major magic-removal fixed [patch] Problem resolving primary key in some kwarg database queries This patch is provided against magic_removal. The same logic should apply equally well on the trunk. Queries involving primary keys over a relation currently exhibit some problems. The existing logic in parse_lookup works out if the final query clause is 'pk', and if so, replaces 'pk' with '(primary key)!__exact'. This is fine, except that the primary key is determined from the Options object provided to parse_lookup, which is he Options object relating to the main table. Some additional context data is added if the field is a related field. However, if a custom primary key is in use, and/or the pk query is several levels deep, the primary key is incorrectly resolved, as a different options object is required. If a one-to-one relationship is being used, the extra context is not required. To overcome these problems, I've done a rework of parse_lookup. The following are the most notable features of the change: 1. The algorithm is now recursive, rather than iterative. This simplifies the internal logic, and contains less repetition of code (especially with isnull and exact queries). The algorithm is also documented much more extensively than previously. 2. Primary key lookup behaviour is now determined on the correct Options object 3. Joins now utilize a 'Sorted Map' data structure, to ensure that joins are applied to the final query in the order that they are constructed. 4. One-many queries (i.e., reverse lookup over Foreign Keys) are now possible. As well as an Article finding its (single) Reporter, a Reporter can query over all their (many) Articles. 5. Error messages produced are a little more explicit as to the source of the problem with a kwarg query. The fix comes as two patches; one to implement the parse_lookup changes, and one to update unit tests. The two patches are almost completely independent. If you apply the parse_lookup patch without the unit test patch, all existing unit tests will pass, with the exception of two: custom_columns, Line 17 and many_to_one, Line 64. These te… adrian freakboy@iinet.net.au magic-removal kwarg pk primary key query 0 1 0 0 0 0
1189 2006-01-08 16:41:20 2006-10-22 15:46:15 2019-06-24 00:27:54.277940 Unreviewed closed Documentation defect minor master fixed Extra Commas in Model Example In root/django/trunk/docs/forms.txt change Place class to: {{{ class Place(meta.Model): name = meta.CharField(maxlength=100) address = meta.CharField(maxlength=100, blank=True) city = meta.CharField(maxlength=50, blank=True) state = meta.USStateField() zip_code = meta.CharField(maxlength=5, blank=True) place_type = meta.IntegerField(choices=PLACE_TYPES) class META: admin = meta.Admin() def __repr__(self): return self.name }}} Note, remove extra commas. jacob Brian Ray <bray@sent.com> Place, Model, commas 0 0 0 0 0 0
1211 2006-01-13 07:34:03 2006-10-22 15:58:46 2019-06-24 00:28:08.278093 Unreviewed closed Documentation defect normal   fixed Typo in "Forms, fields, and manipulators" document There's a minor typo in "Forms, fields, and manipulators" document. {{{ Index: docs/forms.txt =================================================================== --- docs/forms.txt (revision 1940) +++ docs/forms.txt (working copy) @@ -98,7 +98,7 @@ because that field is required. Ugly. * Even if you *do* perform validation, there's still no way to give that - information to the user is any sort of useful way. + information to the user in any sort of useful way. * You'll have to separately create a form (and view) that submits to this page, which is a pain and is redundant. }}} adrian paolo <paolo@php3.it>   0 0 0 0 0 0
1217 2006-01-13 16:59:36 2006-10-22 16:32:31 2019-06-24 00:28:12.051202 Unreviewed closed Template system defect normal magic-removal fixed [patch] Additional unit tests for default template tags This patch, against rev 1941 of magic-removal, adds missing unit tests to {{{tests/othertests/templates.py}}} for tags {{{cycle}}}, {{{filter}}}, {{{firstof}}}, {{{ifchanged}}}, {{{regroup}}}, {{{templatetag}}} and {{{widthratio}}}. Tags {{{debug}}}, {{{now}}} and {{{ssi}}} still don't have tests, as I'm not too clear on how best to implement them. Any thoughts?... There is one issue relating to {{{cycle}}} that needs clarification. It seems that {{{{% cycle foo %}}}} is interpreted as a repeat occurrence of a cycle previously named {{{foo}}}. If there is no cycle named {{{foo}}} then I would expect this usage to yield a {{{TemplateSyntaxError}}}, but in fact we see {{{AttributeError: 'Parser' object has no attribute '_namedCycleNodes'}}}. Is this a bug, perhaps? adrian nick@efford.net   0 1 0 0 0 0

Next page

Advanced export

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

CSV options:

CREATE TABLE "tickets_full" (
        id int primary key,
        created datetime,
        changetime datetime,
        last_pulled_from_trac datetime,
        stage text,
        status text,
        component text,
        type text,
        severity text,
        version text,
        resolution text,
        summary text,
        description text,
        owner text,
        reporter text,
        keywords text,
        easy boolean,
        has_patch boolean,
        needs_better_patch boolean,
        needs_tests boolean,
        needs_docs boolean,
        ui_ux boolean