42 rows where "changetime" is on date 2013-02-23

View and edit SQL

Suggested facets: stage, status, component, type, owner, easy, has_patch, needs_better_patch, needs_tests, needs_docs, ui_ux, created (date), last_pulled_from_trac (date)

changetime (date)

  • 2013-02-23 · 42
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
218 2005-07-28 10:47:14 2013-02-23 14:40:51 2019-06-24 00:17:35.216015 Ready for checkin closed contrib.admin defect normal   fixed changing column sort order in admin interface doesn't change sort order The admin interface pages for selecting which object to change (e.g. '''/admin/polls/polls/''' from the tutorial) allow choosing the column to sort by, and allow changing the sort order of that column (ascending or descending). However, while changing the sort order of a column changes the direction arrow correctly, the sort order doesn't change: '''/admin/polls/polls/?ot=desc&o=1''' and '''/admin/polls/polls/?ot=asc&o=1''' produce identical output. adrian fidothe list_display 0 0 0 0 0 0
1035 2005-12-09 19:23:54 2013-02-23 12:29:37 2019-06-24 00:26:16.762440 Ready for checkin closed contrib.admin defect normal master fixed Link to popup for adding related objects should respect user's permissions The little link for adding additional related objects (e.g. related by foreign key) should only show if the user has sufficient permissions to add these objects. {{{ Index: django/contrib/admin/templatetags/admin_modify.py =================================================================== --- django/contrib/admin/templatetags/admin_modify.py (revision 1587) +++ django/contrib/admin/templatetags/admin_modify.py (working copy) @@ -246,6 +246,7 @@ return { 'add': context['add'], + 'app_permission': context['app_permission'], 'change': context['change'], 'bound_fields': bound_fields, 'class_names': " ".join(class_names), @@ -257,3 +258,11 @@ return bound_manip.get_ordered_object_pk(ordered_obj) object_pk = register.simple_tag(object_pk) + +#@register.filter +def has_perm(perm_obj, perm): + if perm_obj: + return perm_obj[perm] + return False + +has_perm = register.filter(has_perm) Index: django/contrib/admin/views/main.py =================================================================== --- django/contrib/admin/views/main.py (revision 1587) +++ django/contrib/admin/views/main.py (working copy) @@ -286,6 +286,7 @@ self.is_date_time = isinstance(field, meta.DateTimeField) self.is_file_field = isinstance(field, meta.FileField) self.needs_add_label = field.rel and isinstance(field.rel, meta.ManyToOne) or isinstance(field.rel, meta.ManyToMany) and field.rel.to.admin + self.add_permission = self.needs_add_label and "can_add_%s" % (field.rel.to.verbose_name) self.hidden = isinstance(self.field, meta.AutoField) self.first = False @@ -375,11 +376,13 @@ return "" def render_change_form(opts, manipulator, app_label, context, add=False, change=False, show_delete=False, form_url=''): + app_permission = context['perms'][app_label] extra_context = { 'add': add, 'change': change, 'bound_manipulator': AdminBoundMa… SmileyChris Esaj <jason at jasondavies.com> sprint200912 0 1 0 0 0 0
6271 2007-12-23 22:42:03 2013-02-23 15:48:30 2019-06-24 01:22:23.748874 Accepted closed Template system New feature Normal master fixed filter arguments with spaces break several template tags After [6956], something like this now breaks: {{{ {% regroup object_list by created|date:"F Y" as grouped %} }}} I believe it now splits the quoted bits and the arg count is more than 6 in this case, so the templatetag errors out. aaugustin Rob Hudson <treborhudson@gmail.com> tplrf-fixed 0 1 1 0 0 0
7700 2008-07-10 06:33:34 2013-02-23 19:33:12 2019-06-24 01:37:53.848133 Accepted closed Core (Other) Bug Normal master fixed Query parent for child I'm not sure if this is a feature request or a bug fix :) This seemed to work a few weeks ago, and it no longer does. Whether or not the feature was intentional, it was quite useful--being able to query parent models for child instances. Given the following model: {{{ from django.contrib.auth.models import Group class Team(Group): pass }}} I want to query the Groups to find out which are Teams. This used to work {{{ >>> g = Group.objects.create(name='group1') >>> t = Team.objects.create(name='team1') >>> Group.objects.filter(team__pk__isnull=False) [<Group: team1>] }}} But instead now I get the following: {{{ >>> Group.objects.filter(team__pk__isnull=False) [<Group: group1>, <Group: team1>] }}} Ideally, it would be nice to simplify this to: {{{ >>> Group.objects.filter(team__isnull=False) [<Group: team1>] }}} But just getting it to work again would be nice. nobody casey@deccio.net   0 0 0 0 0 0
11136 2009-05-17 23:30:07 2013-02-23 12:28:30 2019-06-24 02:16:03.922213 Accepted closed contrib.admin Cleanup/optimization Normal 1.0 duplicate add button to related field in admin to be put only if user is authorized to add Here is the example situation: {{{ - my model is composed of two classes A and B - class A has a field being a foreign key to a B class field - I have permission to add A elements, but not to add B elements - in the admin, when I add an A element, I see the '+' button on the foreign key field to B even though I do not have the rights to create a B element - therefore, I think I can add the element, but when I click on +, I get a pop-up with permission denied }}} it would be nicer not to show at all the "+"; better user experience have a look at the second part of this thread: http://groups.google.com/group/django-users/browse_thread/thread/ceef2d6fd5f5a528 anonymous sergio add button 0 0 0 0 0 1
12280 2009-11-29 16:45:39 2013-02-23 14:52:15 2019-06-24 02:28:24.671685 Accepted closed Documentation Cleanup/optimization Normal 1.1 worksforme working with forms example should include editing an existing instance http://docs.djangoproject.com/en/dev/topics/forms/#using-a-form-in-a-view The page is titled 'Working with forms' yet there is no example of editing and existing instance of a model. This example refers to 'the standard pattern' it should also cover the case {{{ form = ContactForm(request.POST,instance=anInstance) }}} ecabuk johnsmith   0 0 0 0 0 0
15198 2011-01-31 15:16:57 2013-02-23 23:34:06 2019-06-24 03:00:07.828423 Ready for checkin closed contrib.auth Cleanup/optimization Normal master fixed AuthenticationForm.clean call does not have request set I'm working on per site login system currently. It is required to get the site of the request in prior to calling ``authenticate()`` so the calls to my auth backend should be either in form of: {{{ authenticate(site_id, username, password) }}} or more general: {{{ authenticate(request, username, password) }}} If I try to create own `django.contrib.auth.forms.AuthenticationForm` e.g. by subclassing, then the login view never sets the `request` attribute of auth form. So currently I have to recreate whole login view and authentication form in order to make per site login. With this simple patch I could just subclass AuthenticationForm and override the `clean()` functions call to authentication. More about my per site endeavours in [http://groups.google.com/group/django-developers/browse_thread/thread/7052c23321079295/fbf16f06fa17988c django-devs thread], and in [http://ciantic.github.com/multisited/README.html my proposal for changes to django]. nobody Ciantic   1 1 0 0 0 0
15877 2011-04-21 04:57:11 2013-02-23 17:32:47 2019-06-24 03:07:30.420298 Ready for checkin closed Forms Bug Normal 1.3 fixed Exception:ModelForm has no model class specified case: subj exception does not throws when in user class model is '''not''' specified in constructor instance is specified result: silently falls in validation returns > empty cleaned dict > nothing rendered expected: exception throws here: http://code.djangoproject.com/browser/django/trunk/django/forms/models.py#L229 nobody theaspect@gmail.com   0 1 1 0 0 0
16858 2011-09-15 20:58:46 2013-02-23 11:47:11 2019-06-24 03:18:16.200050 Accepted closed Core (Cache system) Bug Normal 1.5-rc-1 duplicate incr() on locmem cache resets the expiry time On the locmem cache backend, calling incr() causes the key's timeout value to be reset to the default for the cache. To reproduce: - setup the default cache to be locmem and with a timeout of 1 second {{{ >> cache.set('key', 10, 300) >> time.sleep(1) >> cache.get('key') 10 >> cache.incr('key') >> time.sleep(1) >> cache.get('key') None }}} The cache should still contain the key at the last line. The problem comes from the implementation of incr() in base.py which uses get() and set() to implement incr(). Since set() is called without a timeout, the cache default time is used. berkerpeksag boxm   1 1 0 0 0 0
17094 2011-10-23 23:45:26 2013-02-23 13:55:47 2019-06-24 03:20:49.515972 Design decision needed closed Documentation Bug Normal 1.3 fixed DeletionMixin get_success_url parameter In https://docs.djangoproject.com/en/1.3/ref/class-based-views/#django.views.generic.edit.DeletionMixin.get_success_url says that get_success_url get a parameter(obj) but this doesn't happen on the source code. nobody alej0   0 0 0 0 0 0
17663 2012-02-08 17:46:54 2013-02-23 12:12:21 2019-06-24 03:26:54.598897 Accepted closed Forms Bug Normal master fixed Method "save" in BaseModelFormSet is not marked as alters_data   vanschelven aiv formset 1 1 0 1 0 0
17751 2012-02-22 22:50:13 2013-02-23 17:44:11 2019-06-24 03:27:52.473621 Ready for checkin closed Forms Bug Normal master fixed GenericIPAddressField allows an ipv6 address to start with a space GenericIPAddressField allows an ipv6 address to start with a space, it should raise a ValidationError instead. At least the IPAddressField (ipv4) does it. erikr federico.capoano@teletu.it GenericIPAddressField, ipv6 0 1 0 0 0 0
17866 2012-03-10 15:17:29 2013-02-23 20:32:39 2019-06-24 03:29:07.858534 Accepted closed HTTP handling Uncategorized Normal 1.4-beta-1 fixed locale middleware adds Vary Accept-Language when language prefix used When i18n_patterns are in use, locale middleware does pretty nice job and redirects to proper url. But after redirection to localized site, "Vary: Accept-Language" forces (squid/varnish) to cache a lot of versions of this prefixed url, which isn't necessary in my opinion. ambv sero   0 1 0 0 0 0
17905 2012-03-15 13:20:41 2013-02-23 23:11:27 2019-06-24 03:29:33.140202 Accepted assigned contrib.admindocs New feature Normal 1.4-alpha-1   Admin documentation lists all models, even for users without access to certain applications By default, the admin docs lists documentation for all models. Some users may not have access to models that are still listed in their entirety. The easiest way to fix this was to check each model in the model index, and only add the model to the listing if a user has the correct permissions. I'm not sure if this is the correct way to go about this, but I'm submitting the patch for review. gszczepanczyk chriscohoat   0 1 0 1 0 0
18152 2012-04-17 11:08:01 2013-02-23 18:36:49 2019-06-24 03:32:11.473065 Accepted closed Template system Bug Normal 1.4 wontfix urlize filter does not work correctly in combination with linebreaksbr filter Use this text with these filter in exactly THIS order in a template: text = """ Lorem ipsum http://some.com/web-page Lorem ipsum """ {{ text|linebreaksbr|urlize }} The output will include an additional, escaped &gt; linebreaksbr appends a <br /><br /> directly to the url, which then appears to get wrongly escaped in the subsequent urlize filter. Vladimir.Filonov Nasmon   0 0 0 0 0 0
18208 2012-04-25 16:42:41 2013-02-23 15:11:58 2019-06-24 03:32:48.531180 Design decision needed closed Internationalization Uncategorized Normal 1.4 wontfix Escape translations by default '''Proposal''': 1. By default treat translations (`trans` and `blocktrans` templatetags, `ugettext` and `ungettext` functions) as '''unsafe''' strings. 2. Add '''`safe`''' flag to `trans` and `blocktrans` templatetags that would mark their output as safe. 3. When using `ugettext` and `ungettext` functions -- explicitly use `|safe` filter to skip escaping. Safety must be turned on by default. Noone knows how its app would be translated. Always escape it manually is not a solution for the same reasons as escaping every string used on the page. '''Use-case''' Translators may easily use special chars in the translations trying to make them better. See this example: {{{ <p>{% blocktrans %}Check Terms and Conditions or 5 is more than 4</p> <p>Even worse: <input type="button" value="{% trans 'Do not save' %}" /> }}} It looks fine until they translated string using special chars: {{{ Check Terms & Conditions or 5 > 4 Don't save "{{ item }}" }}} By default `blocktrans` and `trans` are "safe" strings that would lead to showing translations as-is. This would break the page completely and may lead to XSS and other unpleasant stuff. '''Current woraround''' To escape special chars in translations you have to always apply `force_escape` filter manually on each translation: {{{ <p>{% filter force_escape %}{% blocktrans %}Check Terms and Conditions or 5 is more than 4{% endfilter %}</p> <p>Even worse: <input type="button" value="{% filter force_escape %}{% trans 'Do not save {{ item }}}' %}{% endfilter %}" /> }}} nobody tonnzor   0 0 0 0 0 0
18260 2012-05-03 08:54:17 2013-02-23 15:48:30 2019-06-24 03:33:22.078246 Accepted closed Template system Bug Normal master fixed Cache tag doesn't handle filter expresssions I found the cache tag didn't well handle when I passed, for instance: {% cache ..... request.GET.foo %} As it would raise an exception if GET['foo'] wasn't set... so I tried passing a default: {% cache ..... request.GET.foo|default:"bar" %} Only to see it not only didn't fix the issue, but didn't appear to be parsing filter expressions, either. I've updated the cache tag to use parser.compile_filter for all its arguments. regebro FunkyBob cache 1 1 0 0 1 0
18376 2012-05-24 15:05:43 2013-02-23 14:28:27 2019-06-24 03:34:36.536392 Accepted closed Forms Bug Normal 1.4 invalid Model formsets apply unique checks to blank, null fields This is similar to #13811 but applies to fields declared with ``unique=True`` rather than ``unique_together``: a model formset will incorrectly raise a ValidationError during ``validate_unique`` if more than one of the objects have a null value. I noticed this on a site using admin list_editable with a blank, null field but the problem appears to affect any model formset. joeri acdha formset admin list_editable unique sprint2013 0 1 0 1 0 0
18583 2012-07-06 12:59:30 2013-02-23 21:45:16 2019-06-24 03:36:52.228319 Accepted closed Database layer (models, ORM) Bug Normal 1.4 fixed exclude generates wrong SQL query exclude generates a wrong SQL query in a certain setup. Given the following models: {{{#!python class A(models.Model): pass class AGroups(models.Model): a = models.ForeignKey(A, related_name='groups') group = models.ForeignKey(Group) class B(models.Model): a = models.ForeignKey(A) class C(models.Model): b = models.ForeignKey(B) }}} Then the following: {{{#!python g = Group.objects.create(name='foo') C.objects.exclude(b__a__groups__group__in=[g]) }}} generates the following query: {{{ SELECT "books_c"."id", "books_c"."name", "books_c"."b_id" FROM "books_c" INNER JOIN "books_b" ON ("books_c"."b_id" = "books_b"."id") INNER JOIN "books_a" ON ("books_b"."a_id" = "books_a"."id") WHERE NOT (("books_b"."a_id" IN ( SELECT U1."id" FROM "books_b" U1 INNER JOIN "books_a" U2 ON (U1."a_id" = U2."id") INNER JOIN "books_agroups" U3 ON (U2."id" = U3."a_id") WHERE (U3."group_id" IN (3) AND U1."id" IS NOT NULL) ) AND "books_a"."id" IS NOT NULL)) LIMIT 21 }}} Line 4 should be {{{ WHERE NOT (("books_b"."id" IN ( }}} instead. The same issue happens with {{{#!python agroups = AGroups.objects.filter(group__in=[g]) C.objects.exclude(b__a__groups__in=agroups) }}} This one works: {{{#!python b_excludes = B.objects.filter(a__groups__group__in=[g]) C.objects.exclude(b__in=b_excludes) }}} (Using Django 1.4, Python 2.7.3rc2, sqlite) See attachment for more testing code. nobody rbreu query exclude sql sprints-django-ar 0 0 0 0 0 0
18829 2012-08-22 02:26:32 2013-02-23 21:27:24 2019-06-24 03:39:29.601165 Accepted closed Forms Bug Normal 1.4 fixed ModelChoiceIterator doesn't adjust its length to account for an empty item. In forms/models.py, the ModelChoiceIterator defines an {{{ __iter__ }}} method which yields an empty entry {{{ if empty_label is not None}}}, but the {{{ __len__ }}} method always returns the length of the queryset, no matter if the empty choice is present. {{{ def __iter__(self): if self.field.empty_label is not None: yield (u"", self.field.empty_label) if self.field.cache_choices: if self.field.choice_cache is None: self.field.choice_cache = [ self.choice(obj) for obj in self.queryset.all() ] for choice in self.field.choice_cache: yield choice else: for obj in self.queryset.all(): yield self.choice(obj) def __len__(self): return len(self.queryset) }}} This can lead to erratic behavior when iterating. For example, the following template code wont hold the expected output, because the forloop.last will be True before for the second to last item, causing the semicolon to render on the last line and not in the previous one. {{{ {% for choice_id, choice_name in my_form.my_field.field.choices %} {{ choice_id }} - {{ choice_name }} {% if not forloop.last %};{% endif %} {% endfor %} }}} This would produce an output like: {{{ - -----; 1 - One; 2 - Two 3 - Three; }}} vanschelven facundo.olano@gmail.com ModelChoiceIterator ModelForm 1 1 0 0 0 0
19282 2012-11-13 04:31:41 2013-02-23 20:48:40 2019-06-24 03:44:22.369745 Ready for checkin closed contrib.humanize Cleanup/optimization Normal 1.4 fixed intcomma for decimal no longer works as expected intcomma used to work for decimals, but this has been broken somewhere between django 1.2.3 and django 1.4... e.g. {{{ >>> from decimal import Decimal >>> i = Decimal("1233566.22") >>> intcomma(i) u'1,233,566' }}} I guess technically the name is intcomma, so maybe it was officially only supposed to work for integers; however it appears that intcomma specifically supports floats: {{{ >>> i = 12356333.44 >>> intcomma(i) u'12,356,333.44' }}} for reference --- Old humanize.py: {{{ def intcomma(value): """ Converts an integer to a string containing commas every three digits. For example, 3000 becomes '3,000' and 45000 becomes '45,000'. """ orig = force_unicode(value) new = re.sub("^(-?\d+)(\d{3})", '\g<1>,\g<2>', orig) if orig == new: return new else: return intcomma(new) }}} New humanize.py (note that it specifically mentions float.. perhaps we could specifically mention decimal as well??): {{{ def intcomma(value, use_l10n=True): """ Converts an integer to a string containing commas every three digits. For example, 3000 becomes '3,000' and 45000 becomes '45,000'. """ if settings.USE_L10N and use_l10n: try: if not isinstance(value, float): value = int(value) except (TypeError, ValueError): return intcomma(value, False) else: return number_format(value, force_grouping=True) orig = force_unicode(value) new = re.sub("^(-?\d+)(\d{3})", '\g<1>,\g<2>', orig) if orig == new: return new else: return intcomma(new, use_l10n) }}} hernantz judy intcomma, humanize, decimal, sprints-django-ar 0 1 0 0 0 0
19365 2012-11-26 21:16:13 2013-02-23 17:34:18 2019-06-24 03:45:16.007672 Accepted closed Database layer (models, ORM) Bug Normal 1.4 wontfix Create a `NonNegativeIntegerField` alias for `PositiveIntegerField` The current name is totally bogus, we should at least have an alias that's correct. nobody Alex   1 1 0 0 0 0
19402 2012-11-30 23:30:04 2013-02-23 20:44:13 2019-06-24 03:45:41.189868 Accepted closed Documentation Cleanup/optimization Normal master fixed django.contrib.auth.models.CustomUser.REQUIRED_FIELDS needs better docs https://docs.djangoproject.com/en/dev/topics/auth/#django.contrib.auth.models.CustomUser.User.REQUIRED_FIELDS should be enhanced with more explanation and a clearer example. nobody pydanny   0 1 0 0 0 0
19526 2012-12-27 12:18:40 2013-02-23 22:16:49 2019-06-24 03:47:01.030352 Ready for checkin closed contrib.staticfiles Bug Normal 1.4 fixed CachedFilesMixin.patterns should be case-insensitive According to [1], ''all CSS syntax is case-insensitive within the ASCII range (i.e., [a-z] and [A-Z] are equivalent), except for parts that are not under the control of CSS.'' So, it seems like `re.compile(pattern, re.IGNORECASE)` is a valid and not so restricting way to go. [1] http://www.w3.org/TR/CSS2/syndata.html#characters ethlinn mike@openbunker.org CachedFilesMixin staticfiles 0 1 0 0 0 0
19572 2013-01-07 10:30:40 2013-02-23 13:47:30 2019-06-24 03:47:32.645220 Accepted closed contrib.staticfiles Cleanup/optimization Normal master fixed Unused argument in staticfiles.views.serve The view 'django.contrib.staticfiles.views.serve' has the optional argument 'document_root'. I guest that this argument can be used to serve files from another path. But the argument is not used in this function, so it does not serve other files in Django 1.4 or the development version. You could either delete the argument, or merge this pull request: https://github.com/django/django/pull/621 fakotb ostcar   0 0 0 0 0 0
19579 2013-01-08 15:13:27 2013-02-23 20:34:11 2019-06-24 03:47:36.992860 Accepted closed Documentation Uncategorized Normal 1.4 fixed Docs aren't clear on purpose of signals' "providing_args" I would like to suggest to the developers that the purpose of "providing_args" be clarified in the docs: https://docs.djangoproject.com/en/dev/topics/signals/#defining-signals This was a point of confusion for me. According to [https://groups.google.com/d/msg/django-developers/tThj2QjbLiw/wmN-a93tZkgJ this post], at the moment, "providing_args" is "purely documentation(al)". nobody anonymous   0 1 0 0 0 0
19609 2013-01-14 17:04:46 2013-02-23 22:35:07 2019-06-24 03:47:56.081143 Ready for checkin closed contrib.admin Bug Normal master fixed admin Inlines doesn't display help_text for readonly fields Admin inlines doesn't display help_text for readonly fields viciu glic3rinu admin inline help_text readonly 1 1 0 0 0 1
19675 2013-01-27 22:55:07 2013-02-23 16:10:13 2019-06-24 03:48:38.201334 Ready for checkin closed Documentation Cleanup/optimization Normal 1.4 fixed "At A Glance" does not say where to put "sitelogo.gif" This is non-trivial, and needs to be briefly mentioned -- MEDIA_ROOT? STATIC_ROOT? A STATICFILES_DIRS entry? Does it have to be listed in "urls.py"? anonymous anonymous   0 0 0 0 0 0
19686 2013-01-28 21:24:34 2013-02-23 09:18:30 2019-06-24 03:48:45.175515 Ready for checkin closed Forms New feature Normal master fixed Support HTML5 number input type In #16630, we added support for `type="email"` and `type="url"` HTML5 input types. This ticket is about `type="number"` input type. It has been separated so as we can discuss specific issues, in particular localization issues. nobody claudep   0 1 0 0 0 0
19752 2013-02-06 08:58:26 2013-02-23 15:43:20 2019-06-24 03:49:27.399779 Accepted closed Documentation Cleanup/optimization Normal 1.5-beta-1 fixed Latest version of Postgresql is 9.2 on EnterpriseDB On the documentation : https://docs.djangoproject.com/en/1.5/ref/contrib/gis/install/#postgresql It says: First, download the latest PostgreSQL 9.0 installer from the EnterpriseDB Web site. It should be 9.2 ecabuk anonymous   1 1 0 0 0 0
19775 2013-02-08 01:17:27 2013-02-23 21:03:20 2019-06-24 03:49:42.141819 Accepted closed Documentation Bug Normal 1.4 fixed database configuration without "default" not supported For version 1.4 and dev documentation on multiple databases the text seems to imply that you can choose not to define a "default" db https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-databases '' ... Django uses the database with the alias of default when no other database has been selected. If you don’t have a default database, you need to be careful to always specify the database that you want to use. '' However, when you actually remove, or do not include a "default" and attempt to syncdb with Postgresql, you get the following error that explicitly tells you, that you *must* define a "default" database: {{{ >python manage.py syncdb Traceback (most recent call last): File "manage.py", line 16, in <module> execute_manager(settings) File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line 459, in execute_manager utility.execute() File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line 261, in fetch_command klass = load_command_class(app_name, subcommand) File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line 69, in load_command_class module = import_module('%s.management.commands.%s' % (app_name, name)) File "C:\Python27\lib\site-packages\django\utils\importlib.py", line 35, in import_module __import__(name) File "C:\Python27\lib\site-packages\django\core\management\commands\syncdb.py", line 8, in <module> from django.core.management.sql import custom_sql_for_model, emit_post_sync_signal File "C:\Python27\lib\site-packages\django\core\management\sql.py", line 6, in <module> from django.db import models File "C:\Python27\lib\site-packages\django\db\__init__.py", line 12, in <module> raise ImproperlyConfigured("You must define a '%s' database" % DEFAULT_DB_ALIAS) django.core.exceptions.Improper… wsmith323 monkut multipledbs 0 1 0 0 0 0
19827 2013-02-14 16:44:35 2013-02-23 16:43:37 2019-06-24 03:50:15.339163 Ready for checkin closed Template system Bug Normal 1.4 fixed Exception reraise in defaulttags shoud keep stacktrace I've stumbled upon a problem where a reraised exception doesn't keep the original stacktrace. I'm attaching a patch to fix this regebro Kronuz sprint2013 1 1 1 0 0 0
19832 2013-02-15 13:40:18 2013-02-23 10:57:34 2019-06-24 03:50:18.500274 Accepted closed Forms Bug Normal 1.4 duplicate DecimalField validation shoud use plural forms The django.forms.fields.DecimalField line 260 - shlud use plural forms for decimal places and digis errors. Thank you. nobody clay.evil@gmail.com DecimalField validation 0 0 0 0 0 0
19850 2013-02-19 13:23:06 2013-02-23 13:42:56 2019-06-24 03:50:30.078033 Accepted closed contrib.admin Bug Release blocker 1.5-rc-1 fixed admin_static templatetag is not using the staticfiles' storage backend url The admin_static templatetag checks for statifiles app and then imports the appropriate static templatetag. The issue is that even when staticfiles contrib app is "installed", the templatetag imported is "static" while the one that uses the storage backend is "do_static". In Django 1.4, there was no "do_static" function, only "static", [https://github.com/django/django/commit/0a68a2994be17ed2669accead331881cb0be41dd This is the commit] that seems to have broken it. jezdez duduklein@gmail.com staticfiles storage backend templatetag 0 0 0 0 0 0
19872 2013-02-21 11:53:07 2013-02-23 22:32:46 2019-06-24 03:50:44.183957 Ready for checkin closed Core (Other) Cleanup/optimization Normal master fixed cached_property doesn't behave properly when accessed through the class cached_property raises an exception when used through the class, instead of returning self like property does. This makes introspection hard, and makes its use together with ABC's impossible. nobody simonpercivall   0 1 0 0 0 0
19880 2013-02-22 09:33:37 2013-02-23 20:28:17 2019-06-24 03:50:49.389137 Accepted closed Documentation Bug Normal master fixed form-wizard initial data example is wrong In this [https://docs.djangoproject.com/en/1.4/ref/contrib/formtools/form-wizard/#providing-initial-data-for-the-forms example] there is a small error, basically it is calling as_view and then call methods on the returned function. {{{ >>> wiz = ContactWizard.as_view([ContactForm1, ContactForm2], initial_dict=initial) >>> form1 = wiz.get_form('0') }}} should be: {{{ >>> wiz = ContactWizard([ContactForm1, ContactForm2], initial_dict=initial) >>> form1 = wiz.get_form('0') }}} (assuming {{{ __init__ }}} takes same arguments as as_view) nobody almalki form-wizard formwizard wizard 1 1 0 0 0 0
19886 2013-02-22 20:55:02 2013-02-23 01:10:49 2019-06-24 03:50:53.205339 Unreviewed closed Documentation Bug Normal master duplicate documentation: FormWizard.as_view() does not have the attribute get_form() The [https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/#providing-initial-data-for-the-forms documentation] for form wizards has this example: {{{ >>> from myapp.forms import ContactForm1, ContactForm2 >>> from myapp.views import ContactWizard >>> initial = { ... '0': {'subject': 'Hello', 'sender': 'user@example.com'}, ... '1': {'message': 'Hi there!'} ... } >>> wiz = ContactWizard.as_view([ContactForm1, ContactForm2], initial_dict=initial) >>> form1 = wiz.get_form('0') >>> form2 = wiz.get_form('1') >>> form1.initial {'sender': 'user@example.com', 'subject': 'Hello'} >>> form2.initial {'message': 'Hi there!'} }}} The above example (with the definitions of `ContactForm1`, `ContactForm2`, and `ContactWizard` from earlier) fails: {{{ AttributeError: 'function' object has no attribute 'get_form' }}} It seems like the example assumes that `as_view()` should return an instance of `ContactWizard`, whereas it actually returns a function. nobody gandalf013@gmail.com   0 0 0 0 0 0
19887 2013-02-23 00:35:57 2013-02-23 16:36:53 2019-06-24 03:50:53.851950 Accepted closed Documentation Cleanup/optimization Normal master fixed ModelAdmin.fields and ModelAdmin.fieldset not very detailed documented ModelAdmin.fields and ModelAdmin.fieldset are not very detailed documented compared to ModelAdmin.display_list. It is not clear if only fields or callables too can be used, and how to do so. In fact, callables need to be in readonly_fields, which is quite logical after you found out, but no hint is given in the documentation. This could be presented in comparison to the "list" display properties, where you have to state so if you want to make fields editable. Maybe noteworth is some hint about callables that you want to make writable. I guess in that case a custom Field would be the Right Thing (?). zsiciarz Patrick Strasser <patrick@wirklich.priv.at>   0 1 0 0 0 0
19892 2013-02-23 15:04:10 2013-02-23 15:39:04 2019-06-24 03:50:57.124465 Unreviewed closed Documentation Cleanup/optimization Normal master fixed mysite/mytemplates/ directory introduced in tutorial02, should it be mysite/templates/ ? Working on the staticfiles documentation. Jannis said that it would be better to have STATICFILES_DIRS introduced the same way as TEMPLATE_DIRS. But TEMPLATE_DIRS is `mysite/mytemplates/` in [https://docs.djangoproject.com/en/dev/intro/tutorial02/#customizing-your-project-s-templates tutorial02: Customizing your project's templates]. Does this mean that we have to document the example STATICFILES_DIRS as `STATICFILES_DIRS=[os.path.join(BASE_DIR, 'mystatic')]` just like `TEMPLATE_DIRS=[os.path.join(BASE_DIR, 'mytemplates')]` ? Or should `TEMPLATE_DIRS` be changed to `TEMPLATE_DIRS=[os.path.join(BASE_DIR, 'templates')]` so that we could use `STATICFILES_DIRS=[os.path.join(BASE_DIR, 'static')]` ? nobody jpic   1 0 0 0 0 0
19893 2013-02-23 15:36:43 2013-02-23 19:13:29 2019-06-24 03:50:57.782585 Unreviewed closed Core (Management commands) Uncategorized Normal 1.4 duplicate manage.py dbshell requires password for PostgreSQL databases SQLite and MySQL databases can be accessed using manage.py dbshell without entering any passwords. This isn't the case with PostgreSQL, which requires copying the password from settings.py and pasting it again after psql's prompt. We can use ~/.pgpass files but they have to be set up in advance, which is still annoying. To the best of my knowledge, passing the password via the environment is not a security risk. https://github.com/django/django/pull/772 nobody gnosek   0 1 0 0 0 0
19894 2013-02-23 16:50:24 2013-02-23 18:37:11 2019-06-24 03:50:58.426398 Unreviewed closed Documentation Bug Normal master worksforme default STATIC_URL is '/static/' in stead of None? https://docs.djangoproject.com/en/dev/ref/settings/#static-url mentions the default STATIC_URL to be None. But when we create a new project using startproject, it is actually '/static/'. nobody wim@go2people.nl   0 0 0 0 0 0
19899 2013-02-23 18:58:19 2013-02-23 22:58:00 2019-06-24 03:51:01.564074 Unreviewed closed contrib.auth New feature Normal master wontfix Add attr request in user_login_failed signal Add attr request in user_login_failed signal. This will allow to see the IP of the person who brute force passwords. nobody anonymous   0 0 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