tickets
31 rows where "created" is on date 2008-08-19 sorted by resolution
This data as json, CSV (advanced)
Suggested facets: type, version, summary, description, owner, reporter, keywords, has_patch, needs_better_patch, needs_tests
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8408 | 2008-08-19 07:09:11 | 2021-11-03 09:40:45 | 2022-03-06 03:42:11.159268 | Accepted | new | contrib.admin | New feature | Normal | dev | Add a new meta option: don't do count(*) in admin | Hello, everytime when I use Admin to view a table, the Admin count the rows in the table. if the database is mysql+innodb, this step is very slow, how about add an option in Meta to prevent this, such as {{{ #!python class A(models.Model): class Meta: do_not_count = True }}} thanks | tchaumeny | lidaobing | 0 | 1 | 1 | 1 | 0 | 0 | ||
| 8405 | 2008-08-19 02:00:43 | 2008-08-22 16:59:00 | 2022-03-06 03:42:10.660771 | Unreviewed | closed | contrib.admin | dev | duplicate | Editing inline-image in admin results in KeyError | I have three models: {{{ class Image(models.Model): image = models.ImageField(upload_to='productimages/') class ExtraImage(Image): model = models.ForeignKey('ProductModel') class ProductModel(models.Model): modelnumber = models.CharField(primary_key=True, max_length=50, unique=True) }}} and admin interface for them, which has a inline for the extra images: {{{ class ExtraImageInline(admin.TabularInline): model = ExtraImage extra = 2 class ProductModelAdmin(admin.ModelAdmin): inlines = (ModelPropertyInline, ExtraImageInline) }}} Adding the image works OK, but anything after that (editing or deleting) results in KeyError: {{{ File "/home/customer/django/django/forms/models.py", line 292, in save_existing_objects obj = existing_objects[form.cleaned_data[self.model._meta.pk.attname]] KeyError: 'image_ptr_id' }}} Tested with dev server with Django r8435 and apache+mod_python running Django r8355. | nobody | Uninen | inheritance modelinheritance admin keyerror | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8413 | 2008-08-19 10:16:45 | 2013-08-01 12:18:48 | 2022-03-06 03:42:11.935886 | Accepted | closed | Core (Management commands) | Bug | Normal | dev | duplicate | Django runserver doesn't reload itself after updating files on disk that raised error on import. | When autoreload is on, 1. after any occasional error in any models.py file, reloading doesn't work for further updates of that file. 2. modules that had import errors and updated on disk, are never reloaded. Applied patch fixes the described problems and also allows to track various wrong usages of __import__ API. | buriy | buriy | autoreload reload import error fix runserver | 0 | 1 | 0 | 0 | 0 | 0 |
| 8416 | 2008-08-19 13:16:42 | 2011-09-28 16:12:17 | 2022-03-06 03:42:12.448480 | Accepted | closed | Core (Management commands) | dev | duplicate | Using Sqlite as database backend causes list_filter and date_hierarchy misbehave in Admin pages | list_filter and date_hierarchy in Admin do not work properly when using Sqlite as a db backend and filtering by DateField / DateTimeField field types. To see the bug in action: 1. Create a Django project and an app 2 Set sqlite as db backend 3. Create a test model with DateTimeField 4. Sync the database 5. Add some entries. 6. Observe how clicking "Today" or "This month" does not reveal the entries that were just created. 7. Also, date_hierarchy behaves wierd too, displaying Current month's name and returning no results when clicked. I came across this bug while following the official tutorial at http://www.djangoproject.com/documentation/tutorial01/ Switching to Mysql as a db backend solves the problem. Software: Using latest (1.0-beta_1-SVN-8437) SVN checkout Python 2.5.2 Sqlite bundled with Python 2.5.2 Windows XP Pro SP2 | nobody | amiroff | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8423 | 2008-08-19 18:14:36 | 2008-08-19 18:23:59 | 2022-03-06 03:42:13.633570 | Unreviewed | closed | Database layer (models, ORM) | dev | duplicate | Implement time filters | As of r8442, it is possible to filter a queryset by year, month or day using the usual syntax: {{{ Event.objects.filter(start_time__year=2008) Article.objects.filter(pub_date__month=11, pub_date__day=3) }}} However, filters for hours, minutes and seconds were missing. I have added those in a patch for your consideration along with unit tests and documentation. | nobody | gnuvince | datetime filter hour minute second | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8429 | 2008-08-19 21:22:30 | 2012-01-02 15:07:35 | 2022-03-06 03:42:14.627049 | Accepted | closed | Core (Management commands) | New feature | Normal | dev | duplicate | Option to restrict django-admin.py --dumpdata to a subset of records. | I'd like to suggest being able to limit the output of django-admin.py --dumpdata to a "slice" of records. For example ./manage.py --dumpdata app [10:100] This would be super handy for exporting test-data from large data-sets for unit testing.... | nobody | erikcw | django-admin.py, dumpdata | 0 | 0 | 0 | 0 | 0 | 0 |
| 8403 | 2008-08-19 00:21:53 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.349070 | Accepted | closed | File uploads/storage | dev | fixed | Current file locking does not work on NFS mounts | The code in `django.core.files.locks` assumes that `flock()` is safe to use on every POSIX system to lock files. This isn't the case when the filesystem in question is a relatively recent NFS system. In that case, `flock()` actively raises an error (rather than potentially silently failing to lock things, which was the older behaviour). For those situations `fnctl()` should be used to do file locking. From a bit of a search around and some source reading (plus some comments on the Mailman list, although I've avoided reading the relevant code there for the moment, since it's GPL and I might end up being the person who fixes this ticket), it looks like posixfile.lock() in the Python source is an appropriate way to do this. I realise the `locks.py` file isn't our source, but it is broken in this respect and we do include it. So we have to fix it, since, right now, you can't save files to an NFS-mounted filesystem. This effect in Django was initially noticed in [http://groups.google.com/group/django-users/browse_thread/thread/384c3ec44672cb02 this django-users thread]. | mtredinnick | mtredinnick | file lock | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8404 | 2008-08-19 00:29:36 | 2013-02-14 10:21:24 | 2022-03-06 03:42:10.492942 | Accepted | closed | contrib.auth | Bug | Normal | dev | fixed | Auth password reset tests are too restrictive about template requirements | The tests in `django.contrib.auth.tests.views.PasswordResetTest` check for a correct "failure to submit" with an invalid email address by looking for a particular error message string. The problem is that this string actually reveals that a particular email address isn't on the system. So if somebody writes a password reset template for their own sites that doesn't reveal the presence or absence of a user (an ITS requirement in some organisations, e.g. financial sites), there is no way to have that test pass. So we need to come up with a better way to test for "success" (i.e. failure to submit the form) when the email address doesn't exist in the system. Possibly just easing back and checking for the existence of form.errors in the template rendering will be enough (or the existence of that error message in the context used for rendering), rather than checking the actual string output so carefully is enough. But maybe somebody has another idea. | nobody | mtredinnick | 0 | 0 | 0 | 0 | 0 | 0 | |
| 8406 | 2008-08-19 02:12:13 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.829506 | Accepted | closed | Documentation | dev | fixed | docs: incorrect model repr in interactive sessions | There is a number of instances in the docs where the `repr` for model objects is incorrectly shown as `...` instead of `<SomeModel: ...>`. | nobody | arien | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8407 | 2008-08-19 02:31:43 | 2011-09-28 16:12:17 | 2022-03-06 03:42:10.995558 | Accepted | closed | Documentation | dev | fixed | docs: incorrect output shown for Paginator use in interactive session | The docs show an session at the Python prompt where a `Paginator`'s `page` method throws an `InvalidPage` exception for pages that don't have any objects; the actual exception thrown is an `EmptyPage`. While `EmptyPage` descends from `InvalidPage`, the display is incorrect and may well confuse people. | nobody | arien | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8409 | 2008-08-19 07:18:25 | 2008-09-17 05:42:12 | 2022-03-06 03:42:11.293814 | Accepted | closed | HTTP handling | dev | fixed | Django built-in server is very slow with Firefox browser when serving admin media | Firefox (v3.0.1) with default settings is taking a very conservative view on cacheability of admin media files served by the Django built-in server in django.core.servers.basehttp.py. This can be dramatically improved by arranging for AdminMediaHandler class to provide Last-Modified headers in its responses. Without this change, IE outperforms Firefox on admin pages by a big margin (apparently its heuristics for cache expiry in this case are far looser). | nobody | andylowry | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8410 | 2008-08-19 07:47:01 | 2011-09-28 16:12:17 | 2022-03-06 03:42:11.434908 | Ready for checkin | closed | Core (Cache system) | dev | fixed | memcache backend add method is inconsistent with it's other methods | Split of from #7460 [1] The add method of the memcached backend uses a different approach for it's key/value pair then the other methods. Seems to be 'left' over from past changes/fixes ? Patch attached here aims to make 'add' consistent in terms of handling the key/value pair as it's brother the 'set' method. [1] http://code.djangoproject.com/ticket/7460 | nobody | trbs | memcached, consistency, add | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8411 | 2008-08-19 08:58:02 | 2008-08-30 04:04:53 | 2022-03-06 03:42:11.599541 | Unreviewed | closed | Documentation | dev | fixed | Link to custom model fields documentation missing on SVN release documentation page | It might be helpful to have http://www.djangoproject.com/documentation/custom_model_fields/ explicitly listed on http://www.djangoproject.com/documentation/ | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8414 | 2008-08-19 10:46:36 | 2010-11-23 23:32:01 | 2022-03-06 03:42:12.112270 | Unreviewed | closed | Core (Cache system) | 1.2 | fixed | multiple sites on one memcached | For every site which use for example CacheMiddleware we need to run new memcached instance, its not efficient with few small sites. I think that adding a key_prefix to the CACHE_BACKEND params will solve this problem. I've attached patch aganist memcache backend. | nobody | urban | cache prefix session cached_db | 0 | 1 | 0 | 1 | 0 | 0 | ||
| 8415 | 2008-08-19 12:25:17 | 2011-09-28 16:12:17 | 2022-03-06 03:42:12.279443 | Ready for checkin | closed | contrib.localflavor | dev | fixed | Spelling error in Dutch localflavour nl_provinces.py | There is a spelling error in django/contrib/localflavor/nl/nl_provinces.py Allthough this is a minor patch, it *is* a string change so perhaps setting milestone to 1.0 in this point in time is wrong. But because this local name is best left untranslated i think it should go in anyway. Existing translations should be updated to reflect the correct spelling. | nobody | nlsp | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8419 | 2008-08-19 15:43:17 | 2011-09-28 16:12:17 | 2022-03-06 03:42:12.965336 | Design decision needed | closed | Database layer (models, ORM) | dev | fixed | Fix race in get_or_create() which can lead to update | There is a race condition in get_or_create - if the object is not present for the initial get(), but is swiftly created elsewhere, then the save() will update the object created elsewhere and return it with created=True. This patch uses save(force_insert=True) to stop this from happening, and to drop through into the existing code that re-attempts the get(). I also update some of the documentation to make the behavior completely clear. Note: Patch follows discussion with Malcolm at http://groups.google.com/group/django-developers/browse_thread/thread/179ed55b3bf44af0/067be6c02aba2bb3?hl=en#067be6c02aba2bb3 I am only submitting the patch to get_or_create(), which seemed uncontroversial. I personally believe that a similar force_insert=True should be used in create(), or if not then at least that force_insert and force_update flags should be available for create() as well as for save(). | nobody | Richard Davies <richard.davies@elastichosts.com> | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8422 | 2008-08-19 16:18:53 | 2011-09-28 16:12:21 | 2022-03-06 03:42:13.458263 | Accepted | closed | contrib.admin | dev | fixed | FilePathField gives no blank option in admin when blank=True is set | it seems that the issue in ticket #1756 is still occurring. | nobody | tosh | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8424 | 2008-08-19 18:16:55 | 2013-12-10 05:41:37 | 2022-03-06 03:42:13.793614 | Accepted | closed | Database layer (models, ORM) | New feature | Normal | fixed | Implement time filters | As of r8442, it is possible to filter a queryset by year, month or day using the usual syntax, However, filters for hours, minutes and seconds were missing. I have added those into a patch for your consideration along with unit tests and documentation. {{{ Meeting.objects.filter(meeting_time__hour=12) }}} | UloPe | gnuvince | datetime filter hour minute second | 0 | 1 | 1 | 1 | 0 | 0 | |
| 8425 | 2008-08-19 19:20:06 | 2011-09-28 16:12:17 | 2022-03-06 03:42:13.960248 | Design decision needed | closed | Database layer (models, ORM) | dev | fixed | Palau, Federated States of Micronesia and Marshall Islands are soverign nations and should not be included in the USStateField | http://travel.state.gov/travel/cis_pa_tw/cis/cis_993.html https://www.cia.gov/library/publications/the-world-factbook/geos/ps.html http://en.wikipedia.org/wiki/Palau Citizens of Palau are not US citizens. | anonymous | Jake Nelson <jake.nelson@gmail.com> | palau usstatefield | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8426 | 2008-08-19 19:27:19 | 2010-08-07 01:29:24 | 2022-03-06 03:42:14.122349 | Accepted | closed | Forms | dev | fixed | Wrap help_text in "<span class="helptext"></span>", like errors in "<ul class="errorlist"></ul>" in HTML output | form.as_p() and form.as_ul() should both either have a div (with class="help"), span, or br around the help_text. form.as_table() already has a br tag before the helptext. So this should be added to improve consistency. This will really aid in styling the form with CSS! | kmtracey | erikcw | help_text, as_p, as_ul, forms | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8427 | 2008-08-19 21:04:22 | 2011-09-28 16:12:17 | 2022-03-06 03:42:14.290242 | Unreviewed | closed | Translations | dev | fixed | Updated the Norwegian translation | Updated the Norwegian translation. Added the missing localflavour strings (mostly as blank msgstr). Thanks to Christian Mikalsen for helping out =) | nobody | jonklo | norwegian | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8433 | 2008-08-19 23:33:54 | 2011-09-28 16:12:17 | 2022-03-06 03:42:15.512847 | Accepted | closed | contrib.admin | dev | fixed | auth add_view popup | add_view should probably be: {{{ if "_addanother" in request.POST: request.user.message_set.create(message=msg) return HttpResponseRedirect(request.path) + elif '_popup' in request.REQUEST: + return self.response_add(request, new_user) else: request.user.message_set.create(message=msg + ' ' + ugettext("You may edit it again below.")) return HttpResponseRedirect('../%s/' % new_user.id) }}} | nobody | sorl | 0 | 1 | 0 | 0 | 0 | 0 | |||
| 8417 | 2008-08-19 13:59:12 | 2009-03-07 02:29:11 | 2022-03-06 03:42:12.636453 | Accepted | closed | Documentation | dev | invalid | Include the support of djangos within Archlinux | On the website, please add Archlinux (www.archlinux.org) as a distribution that supports django. A sample explanatory text is as follows: There are two options available for a repository-controlled installation of django. The first option is the availability of django in the 'extra' repository. The availability of this repository on the system allows for the package to be installed with the magic of 'pacman -S django'. The second option is to install an svnbuild of the package. This package can be found on the Archlinux AUR, and can be easily installed with the yaourt program. Using yaourt as a user with sudo access allows for a relative safe way to install user-made packages. There are multiple other django packages on the AUR. You have for example the django-utils package that can be installed in a similar fashion using yaourt. | jacob | voidzero | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8428 | 2008-08-19 21:20:11 | 2009-02-25 19:51:44 | 2022-03-06 03:42:14.446142 | Unreviewed | closed | Uncategorized | dev | invalid | hakrrz@hakrrz.com | hakrrz@hakrrz.com | nobody | hakrrz@hakrrz.com | hacker | 0 | 1 | 0 | 0 | 0 | 0 | ||
| 8430 | 2008-08-19 22:11:13 | 2008-08-23 01:10:47 | 2022-03-06 03:42:14.791133 | Unreviewed | closed | Uncategorized | dev | invalid | MFGdSfsNsCVyubEbzfC | JUkRfJ <a href="http://sjxqsgafowdo.com/">sjxqsgafowdo</a>, [url=http://pxqqeimoxrnq.com/]pxqqeimoxrnq[/url], [link=http://mskokfiuvqbw.com/]mskokfiuvqbw[/link], http://nqngjvxvhgcx.com/ | nobody | anonymous | spam | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8431 | 2008-08-19 22:12:02 | 2008-08-23 01:10:47 | 2022-03-06 03:42:14.975658 | Unreviewed | closed | Uncategorized | dev | invalid | MFGdSfsNsCVyubEbzfC | JUkRfJ <a href="http://sjxqsgafowdo.com/">sjxqsgafowdo</a>, [url=http://pxqqeimoxrnq.com/]pxqqeimoxrnq[/url], [link=http://mskokfiuvqbw.com/]mskokfiuvqbw[/link], http://nqngjvxvhgcx.com/ | nobody | anonymous | spam | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8432 | 2008-08-19 22:16:09 | 2008-08-23 01:10:47 | 2022-03-06 03:42:15.342499 | Unreviewed | closed | Uncategorized | dev | invalid | [spam] | [spam] | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8418 | 2008-08-19 15:13:26 | 2008-10-15 03:03:57 | 2022-03-06 03:42:12.811281 | Unreviewed | closed | Generic views | dev | wontfix | archive_year should pass a date year object to template context instead of four digit unicode | The date_based generic view to manage years should pass year as a date object to template context in order to be coherent with other date_based generic views. | nobody | esauro@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8420 | 2008-08-19 15:58:25 | 2011-09-28 16:12:17 | 2022-03-06 03:42:13.131119 | Unreviewed | closed | Generic views | dev | wontfix | Inconsistent use of template_name in generic views | Nearly all generic views use the parameter ''template_name'' to provide a custom template for rendering purposes. But, the generic view ''django.views.generic.simple.direct_to_template'' uses the parameter ''template'' instead of ''template_name'' for exactly the same. This is an inconsistency that probably should be fixed before releasing 1.0. | nobody | benjixx | 0 | 0 | 0 | 0 | 0 | 0 | |||
| 8412 | 2008-08-19 10:12:19 | 2009-07-28 08:07:04 | 2022-03-06 03:42:11.780251 | Accepted | closed | Core (Serialization) | 1.1-beta | worksforme | When there is a DateTimeField in, data saved with dumpdata cannot be reloaded using loaddata (on German Systems) | To recreate: 1. Setup Django on a Windows XP system with the Time Format set to German (19/8/2008) 2. Save the data using manage.py dumpdata > initial_data.json<br> 3. Reload the data using manage.py loaddata initial_data.json<br> The message appears: {{{ Problem installing fixture 'initial_data.json': Traceback (most recent call last ): File "C:\Program Files\Python\Lib\site-packages\django\core\management\command s\loaddata.py", line 108, in handle for obj in objects: File "C:\Program Files\Python\Lib\site-packages\django\core\serializers\json.p y", line 42, in Deserializer for obj in PythonDeserializer(simplejson.load(stream)): File "C:\Program Files\Python\Lib\site-packages\django\core\serializers\python .py", line 93, in Deserializer data[field.name] = field.to_python(field_value) File "C:\Program Files\Python\Lib\site-packages\django\db\models\fields\__init __.py", line 631, in to_python raise validators.ValidationError, _('Enter a valid date/time in YYYY-MM-DD H H:MM format.') ValidationError: [u'Enter a valid date/time in YYYY-MM-DD HH:MM format.'] }}} | nobody | Mark Essien <markessien@gmail.com> | loaddata dumpdata DateTimeField | 0 | 0 | 0 | 0 | 0 | 0 | ||
| 8421 | 2008-08-19 15:58:28 | 2011-09-28 16:12:17 | 2022-03-06 03:42:13.294445 | Unreviewed | closed | Forms | 1.0-beta | worksforme | FileField traps error when uploading non-ascii filename | Uploading non-ascii filename causes error by UnicodeEncodeError. If the form has two (or more) input fields for uploading files, and if you fill in either field by non-ascii filename and the other field empty, then an UnicodeEncodeError occurs when is_valid() is invoked. To the contrary, no error occurs when (1) the form has only one input field and fill it by non-ascii filename, (2) or the form has two (or more) input fields and fill them all by filenames. (3) or fill one or more input field(s) by ascii filename(s) I wonder why the error occurs only on condition that (4) the form has two (or more) input fields and one field is filled by non-ascii filename and the other field(s) is/are kept empty. [1] source code {{{ ---[ views.py ]--- class UploadForm(forms.Form): attach_1 = forms.FileField(required = False) attach_2 = forms.FileField(required = False) def test_upload(self,request): if request.method == 'POST': formup = UploadForm(request.POST,request.FILES) if formup.is_valid(): result = self.handle_uploaded_file(request.FILES) return HttpResponseRedirect('result.html') --- * the form page is encoded in UTF-8. [2] error message UnicodeEncodeError at /mysite1/debug/upload.html 'ascii' codec can't encode characters in position 37-39: ordinal not in range(128) Unicode error hint The string that could not be encoded/decoded was: NON-ASCII-UPLOAD-FILENAME [3] traceback message Traceback: File "/usr/lib/python25/Lib/site-packages/django/core/handlers/base.py" in get_response 86. response = callback(request, *callback_args, **callback_kwargs) File "/mysite1/debug/views.py" in upload 70. return MyDebug.toolbox.test_upload(request) File "/mysite1/debug/util_mysite_debug.py" in test_upload 177. if formup.is_valid(): File "/usr/lib/python25/Lib/site-packages/django/forms/forms.py" in is_valid 120. return self.is_bound and not bool(self.errors) File "/usr/lib/python25/Lib/site-packages/django/forms/forms.py" in _get_errors 111.… | nobody | mizutori | FileField upload files | 0 | 0 | 0 | 0 | 0 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE tickets (
id int primary key,
created datetime,
changetime datetime,
last_pulled_from_trac datetime,
stage text,
status text,
component text,
type text,
severity text,
version text,
resolution text,
summary text,
description text,
owner text,
reporter text,
keywords text,
easy boolean,
has_patch boolean,
needs_better_patch boolean,
needs_tests boolean,
needs_docs boolean,
ui_ux boolean
);