42 rows where "changetime" is on date 2006-10-16

View and edit SQL

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

changetime (date)

  • 2006-10-16 · 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
84 2005-07-19 13:06:51 2006-10-16 15:33:56 2019-06-24 00:16:10.574593 Unreviewed closed Database layer (models, ORM) defect major   fixed Foreign keys don't work in MySQL Django generates: post_id mediumint(9) unsigned auto_increment NOT NULL REFERENCES posts_posts (slug) This doesn't work. In MySQL, only one column can have auto_increment, and that same column has to be the PRIMARY KEY. I think there should be a separate DATATYPE for ForeignKeys (it seems to just reuse the AutoField). adrian Manuzhai   0 0 0 0 0 0
132 2005-07-21 07:33:38 2006-10-16 15:32:45 2019-06-24 00:16:40.721826 Unreviewed closed Core (Other) defect normal   fixed REMOTE_ADDR not in WSGI-environ The WSGI-spec does not promise the presence of 'REMOTE_ADDR' in environ, but DjangoContext reads it unconditionally when checking if it is in INTERNAL_IPS. Here is a short patch to fix this, by using .get instead of []. {{{ Index: django/core/extensions.py =================================================================== --- django/core/extensions.py (revision 247) +++ django/core/extensions.py (working copy) @@ -13,7 +13,7 @@ self['user'] = request.user self['messages'] = request.user.get_and_delete_messages() self['perms'] = PermWrapper(request.user) - if DEBUG and request.META['REMOTE_ADDR'] in INTERNAL_IPS: + if DEBUG and request.META.get('REMOTE_ADDR') in INTERNAL_IPS: self['debug'] = True from django.core import db self['sql_queries'] = db.db.queries }}} adrian anonymous wsgi 0 0 0 0 0 0
210 2005-07-27 10:50:02 2006-10-16 15:33:12 2019-06-24 00:17:30.125409 Unreviewed closed *.djangoproject.com defect normal   fixed Some tables are unreadable due to white text on white background At least for me :). The {{{body { color: white; }}}} CSS declaration gets inherited by unclassed table cells and makes text unreadable in certain cases (eg, the argument list tables). {{{table { color: #000;}}}} fixes it. wilson anonymous css 0 0 0 0 0 0
233 2005-07-30 11:58:09 2006-10-16 14:53:52 2019-06-24 00:17:44.756459 Unreviewed closed Core (Other)   normal   invalid Using ImageField without PIL Using PIL to extract width and height of the image is not necessary. For that I'm using handy function that I got from draco [http://draco.boskant.nl/]: Works for GIF, PNG and JPEG formats. Also, maybe is useful to cache results of function to avoid accessing to file system frequently. Another good idea from draco is the IMG tag rewriter which automatically adds image width and height to img tags. Can this be added to template system? {{{ def _imageInfo(fhandle): """ Determine the image type of fhandle and return its size. from draco """ head = fhandle.read(24) if len(head) != 24: return if head[:4] == '\x89PNG': # PNG check = struct.unpack('>i', head[4:8])[0] if check != 0x0d0a1a0a: return width, height = struct.unpack('>ii', head[16:24]) img_type = 'PNG' elif head[:6] in ('GIF87a', 'GIF89a'): # GIF width, height = struct.unpack('<HH', head[6:10]) img_type = 'GIF' elif head[:4] == '\xff\xd8\xff\xe0' and head[6:10] == 'JFIF': # JPEG img_type = 'JPEG' try: fhandle.seek(0) # Read 0xff next size = 2 ftype = 0 while not 0xc0 <= ftype <= 0xcf: fhandle.seek(size, 1) byte = fhandle.read(1) while ord(byte) == 0xff: byte = fhandle.read(1) ftype = ord(byte) size = struct.unpack('>H', fhandle.read(2))[0] - 2 # We are at a SOFn block fhandle.seek(1, 1) # Skip `precision' byte. height, width = struct.unpack('>HH', fhandle.read(4)) except Exception: #IGNORE:W0703 return else: return return img_type, width, height # imageSize }}} adrian nesh <nesh [at] studioquattro [dot] co [dot] yu>   0 0 0 0 0 0
303 2005-08-10 22:53:39 2006-10-16 14:53:34 2019-06-24 00:18:29.799924 Unreviewed closed contrib.admin defect normal   invalid Error: got unexpected keyword argument when deleting object in admin interface Traceback: {{{ There's been an error: Traceback (most recent call last): File "/usr/local/lib/python2.4/site-packages/django/core/handlers/base.py", line 62, in get_response return callback(request, **param_dict) File "/usr/local/lib/python2.4/site-packages/django/views/admin/main.py", line 1061, in delete_stage _get_deleted_objects(deleted_objects, perms_needed, request.user, obj, opts, 1) File "/usr/local/lib/python2.4/site-packages/django/views/admin/main.py", line 1006, in _get_deleted_objects for sub_obj in getattr(obj, 'get_%s_list' % rel_opts_name)(): File "/usr/local/lib/python2.4/site-packages/django/utils/functional.py", line 3, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 876, in method_get_related return getattr(rel_mod, method_name)(**kwargs) File "/usr/local/lib/python2.4/site-packages/django/utils/functional.py", line 3, in _curried return args[0](*(args[1:]+moreargs), **dict(kwargs.items() + morekwargs.items())) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 1066, in function_get_list return list(function_get_iterator(opts, klass, **kwargs)) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 1048, in function_get_iterator select, sql, params = function_get_sql_clause(opts, **kwargs) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 1235, in function_get_sql_clause tables2, join_where2, where2, params2, _ = _parse_lookup(kwargs.items(), opts) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 1171, in _parse_lookup _throw_bad_kwarg_error(kwarg) File "/usr/local/lib/python2.4/site-packages/django/core/meta/__init__.py", line 1124, in _throw_bad_kwarg_error raise TypeError, "got unexpected keyword argument '%s'" % kwarg TypeError: got… adrian Boffbowsh delete object admin 0 0 0 0 0 0
304 2005-08-11 01:25:40 2006-10-16 14:55:25 2019-06-24 00:18:30.535523 Unreviewed closed Database layer (models, ORM) defect major   duplicate Changes to auth.LogEntry in changeset [469] breaks Oracle backend. Changeset [469] added an additional "TextField" objects to the LogEntry model. In the Oracle backend (#87), I mapped TextField types in Django to the "Long" datatype in the db, because the Model documentaton suggests TextFields should be used to store (potentially large) html content. If I used any other string datatype (like varchar2), the max length of the field would be 4000 characters/bytes. That isn't good. Yet, again, Oracle stinks compared to PostgreSQL, because Oracle only allows '''one''' "Long" field type per table. If LogEntry's "object_id" needs to only hold small strings, and it is going to be less than 4000 characters, I'd suggest you change it to CharField. After changeset #469, I get this error in django-admin.py init: """ Error: The database couldn't be initialized. Here's the full exception: ORA-01754: a table may contain only one column of type LONG """ I've confirmed that changing LogEntry's object_id field to "CharField" fixes the problem for Oracle. adrian Jason Huggins oracle TextField CharField Long 0 0 0 0 0 0
379 2005-08-21 01:28:02 2006-10-16 15:08:10 2019-06-24 00:19:18.550160 Unreviewed closed *.djangoproject.com defect trivial   wontfix Add OS, Python version, database version fields to ticket tracker There should be fields for OS, Python Version, Database and Version in the bug tracking system and it should be kept cookily so it is automatically entered on subsequent tickets. jacob ssteiner ticket, environment 0 0 0 0 0 0
728 2005-11-04 13:50:10 2006-10-16 15:50:24 2019-06-24 00:23:01.771896 Unreviewed closed Translations enhancement normal   fixed Norwegian .po file Norwegian .po file hugo espen ÆT grindhaug PRIKK org   0 0 0 0 0 0
774 2005-11-12 06:23:04 2006-10-16 15:29:52 2019-06-24 00:23:30.889708 Unreviewed closed *.djangoproject.com defect normal   fixed Typo in 'User authentication in Django' documentation article? Second example from the bottom at http://www.djangoproject.com/documentation/authentication/ 'return render_to_response("playlists/create", context_instance=DjangoContext)' this only works for me if i the instantiate DjangoContext first, eg: 'return render_to_response("playlists/create", context_instance=DjangoContext(request))' This is my first ticket, hope it helps and that I'm not wasting your time, Cheers, foot jacob footless@gmail.com   0 0 0 0 0 0
894 2005-11-24 08:35:53 2006-10-16 15:22:21 2019-06-24 00:24:47.893588 Unreviewed closed Core (Other) defect normal   fixed [patch] Catch exceptions in response middleware Exceptions thrown in response middlewares are not caught by the normal exception handlers, because the response-middlewares are applied outside {{{get_response}}}. It would be nice if the exceptions were caught, and nicely formatted like normal exceptions :) adrian sune.kirkeby@gmail.com   0 1 0 0 0 0
1059 2005-12-14 04:58:13 2006-10-16 15:44:01 2019-06-24 00:26:31.818860 Unreviewed closed contrib.admin defect trivial   fixed [patch] debug output off by one line Debug output is indexed to zero instead of 1. Line numbers are output incorrectly, one less than they should be. adrian oggie rob   0 1 0 0 0 0
1097 2005-12-21 11:09:04 2006-10-16 15:09:24 2019-06-24 00:26:55.862701 Unreviewed closed Documentation enhancement normal   duplicate Add deployable example configs for mod_python/FastCGI/SCGI/Lighttpd etc There's enough real-world experience of deploying Django out there now that we should be able to gather together example configuration files for all kinds of different setups. Let's add a directory to the Django distribution (maybe docs/deployment or something) which contains a collection of almost-ready-to-go configuration files for Apache 1.3/2, Lighttpd and so on covering the various ways in which Django can be deployed using them. Ideally people should be able to install the web server of their choice, drop in a config file we've provided, change one or two settings in it (the location of their code base, the domains hosted by the server) and start it up. This would make deploying Django faster and easier, and would emphasize the production-ready nature of the framework. For bonus points, comment the example configs heavily with tips on tweaking or improving performance once you're up and running. jacob Simon Willison   0 0 0 0 0 0
1203 2006-01-12 01:59:40 2006-10-16 15:36:50 2019-06-24 00:28:03.127538 Unreviewed closed Core (Cache system) defect trivial   fixed [patch] Typos in cache.py The following patch fixes two typos: 1. In comments. 2. {{{raise}}} is used instead of {{{pass}}}. The latter can blow up a web site, if there is a problem with {{{/tmp}}}. jacob eugene@lazutkin.com   0 1 0 0 0 0
1206 2006-01-12 18:26:21 2006-10-16 15:29:52 2019-06-24 00:28:05.027394 Unreviewed closed Documentation defect normal   fixed Typo in generic views docs There's a minor typo in the generic views docs, here's a patch: {{{ Index: /Users/mcroydon/django/django_src.trunk/docs/generic_views.txt =================================================================== --- /Users/mcroydon/django/django_src.trunk/docs/generic_views.txt (revision 1928) +++ /Users/mcroydon/django/django_src.trunk/docs/generic_views.txt (working copy) @@ -329,7 +329,7 @@ Uses the template ``app_label/module_name_form`` by default. This is the same template as the ``update_object`` view below. Your template can tell - the different by the presence or absence of ``{{ object }}`` in the + the difference by the presence or absence of ``{{ object }}`` in the context. Has the following template context: }}} jacob matt   0 0 0 0 0 0
1212 2006-01-13 08:25:06 2006-10-16 14:20:50 2019-06-24 00:28:08.908438 Unreviewed closed Core (Other) defect normal   fixed django.conf.settings is hard to override if you want to do anything with settings, the settings module is (unnecessarily) hard to work with. Configuration shouldn't be a module, but instead an object in a module. And configuration setup shouldn't happen implicitly on import, but instead when specifically invoked (passing in the module name for the settings). Then the standard server setup can invoke this settings setup using the normal environmental variable. Or other people can do other things. Also, there should be a way to swap in new settings dynamically, using threadlocal storage. But at least if the object is there you can monkeypatch something that does swapping. Hacking in swappable modules is harder. AFAICT, everyone does "from django.conf import settings", so pottentially settings can be an object in the django.conf module, without much impact to existing code. Or a new module with an object can be created, and django.conf.settings is a shell fake module around that. hugo ianb@colorstudy.com   0 0 0 0 0 0
1224 2006-01-14 13:11:50 2006-10-16 14:21:26 2019-06-24 00:28:16.411060 Unreviewed closed Database layer (models, ORM) enhancement normal magic-removal wontfix Use inner class for custom Manager in magic removal branch The current (implemented) proposal for adding custom table-level methods in RemovingTheMagic is a little clumsy: {{{ class PersonManager(models.Manager): def get_list(self, **kwargs): # Changes get_list() to hard-code a limit=10. kwargs['limit'] = 10 return models.Manager.get_list(self, **kwargs) # Call the "real" get_list() method. class Person(models.Model): first_name = models.CharField(maxlength=30) last_name = models.CharField(maxlength=30) objects = PersonManager() }}} How about doing this using an inner class instead? {{{ class Person(models.Model): first_name = models.CharField(maxlength=30) last_name = models.CharField(maxlength=30) class Manager(models.Manager): def get_list(self, **kwargs): # Changes get_list() to hard-code a limit=10. kwargs['limit'] = 10 return self.get_list(self, **kwargs) # Call the "real" get_list() method. }}} Are there any reasons this couldn't work? adrian Simon Willison   0 0 0 0 0 0
1367 2006-02-17 14:44:29 2006-10-16 15:31:59 2019-06-24 00:29:47.788188 Unreviewed closed Metasystem defect normal magic-removal fixed [magic-removal] Patch to fix unique_together validator ... which still uses the magical `get_model_module()` stuff. I'll attach a patch, however it should be noted that: * The `manipulators.py` module contains other references to the “old API”, such as `get_object()`, which I haven't looked into. * I've not added any unit tests, or even run the existing suite, since I couldn't yet figure out how they should be run (why do they need a `DJANGO_SETTINGS_MODULE`? Why can't `runtests.py` set that up for me? And why can't I just run `setup.py test`, seeing that Django is already using setuptools?) adrian Christopher Lenz <cmlenz@gmx.de>   0 0 0 0 0 0
1413 2006-02-28 09:00:46 2006-10-16 15:42:36 2019-06-24 00:30:17.177531 Unreviewed closed Core (Other) defect normal magic-removal fixed [magic-removal] [patch] ImportError raised for Models not in INSTALLED_APPS has invalid module path The code checks for the model's module by removing '.models' from the end of the string, but the error message still uses full model path. adrian akaihola   0 1 0 0 0 0
1444 2006-03-02 09:44:47 2006-10-16 15:02:49 2019-06-24 00:30:36.961943 Unreviewed closed Template system defect normal   fixed Template debug not working here is an exception I got when running with template_debug and debug set to true. no debug info, no idea what's wrong, etc. {{{ Traceback (most recent call last): File "/home/wojtek/django/core/servers/basehttp.py", line 272, in run self.result = application(self.environ, self.start_response) File "/home/wojtek/django/core/servers/basehttp.py", line 615, in __call__ return self.application(environ, start_response) File "/home/wojtek/django/core/handlers/wsgi.py", line 159, in __call__ response = self.get_response(request.path, request) File "/home/wojtek/django/core/handlers/base.py", line 109, in get_response return self.get_technical_error_response(request) File "/home/wojtek/django/core/handlers/base.py", line 139, in get_technical_error_response return debug.technical_500_response(request, *sys.exc_info()) File "/home/wojtek/django/views/debug.py", line 126, in technical_500_response return HttpResponseServerError(t.render(c), mimetype='text/html') File "/home/wojtek/django/core/template/__init__.py", line 146, in render return self.nodelist.render(context) File "/home/wojtek/django/core/template/__init__.py", line 714, in render bits.append(self.render_node(node, context)) File "/home/wojtek/django/core/template/__init__.py", line 732, in render_node result = node.render(context) File "/home/wojtek/django/core/template/defaulttags.py", line 112, in render nodelist.append(node.render(context)) File "/home/wojtek/django/core/template/defaulttags.py", line 179, in render return self.nodelist_true.render(context) File "/home/wojtek/django/core/template/__init__.py", line 714, in render bits.append(self.render_node(node, context)) File "/home/wojtek/django/core/template/__init__.py", line 742, in render_node raise wrapped TemplateSyntaxError: Caught an exception while rendering. }}} adrian wsobczuk@gmail.com   0 0 0 0 0 0
1590 2006-04-05 19:52:43 2006-10-16 15:18:42 2019-06-24 00:32:09.367160 Unreviewed closed Core (Other) enhancement minor magic-removal fixed mysql and postgresql backends get_last_insert_id() do extra queries PEP-249 specifies: {{{ Cursor Attribute .lastrowid This read-only attribute provides the rowid of the last modified row (most databases return a rowid only when a single INSERT operation is performed). If the operation does not set a rowid or if the database does not support rowids, this attribute should be set to None. The semantics of .lastrowid are undefined in case the last executed statement modified more than one row, e.g. when using INSERT with .executemany(). Warning Message: "DB-API extension cursor.lastrowid used" }}} While this is an extension, it is supported by both MySQLdb and psycopg (including version 1). Therefore, it is only necessary in base.py to do this: {{{ def get_last_insert_id(cursor, table_name, pk_name): return cursor.lastrowid }}} The sqlite3 backend already does this, in fact. I've been testing the above change with MySQLdb for awhile and it works fine. I have not tried it with pyscopg1, but judging from the source code, it should work: http://initd.org/tracker/psycopg/browser/psycopg1/trunk/cursor.c (look for lastrowid defined on the cursor object). adrian anonymous   0 0 0 0 0 0
1599 2006-04-07 22:51:28 2006-10-16 15:11:12 2019-06-24 00:32:15.033385 Unreviewed closed Documentation defect critical   fixed [magic-removal] tutorial01.txt: bugs in example of using the shell Line 508 and following: >>> p.choice_set.add(choice='Not much', votes=0) Gives: Traceback (most recent call last): File "<console>", line 1, in ? TypeError: add() got an unexpected keyword argument 'choice' is wrong. Should probably be >>> p.choice_set.add(Choice(choice='Not much', votes=0)) >>> c = p.choice_set.add(choice='Just hacking again', votes=0) >>> c.poll Gives the error: Traceback (most recent call last): File "<console>", line 1, in ? AttributeError: 'QuerySet' object has no attribute 'poll' Even if changed to >> c = p.choice_set.add(Choice(choice='Just hacking again', votes=0))[0] >>> c.poll The error is Traceback (most recent call last): File "<console>", line 1, in ? AttributeError: 'NoneType' object has no attribute 'poll' Maybe add does not return a value?? jacob anonymous   0 0 0 0 0 0
1706 2006-04-27 20:00:58 2006-10-16 15:02:53 2019-06-24 00:33:22.647318 Unreviewed closed contrib.admin defect normal   duplicate Admin interface munging overquoted data Creating a new django object, etc on top of MySQL and adding a row with the following column: Rejecting file due to 'Unable to retrieve XML-RPC Data for loan: '<Fault 103: 'unknown loan'>'.' Django puts it into the database correctly, and a select shows the correct data. However running the admin interface seems to munge that data... The actual HTML output is: {{{ <td>Rejecting file 00001781.txt due to 'Unable to retrieve XML-RPC Data for loan 302486992: '<Fault 103: 'unknown loan'>'.' </td> }}} One can assume that it's trying to safely drop what it sees as an 'invalid html tag'... But it seems that dropping valid display data may be undesired behavior. Escaping HTML characters or something similar might be a better output. adrian brendan.mcadams@thewintergrp.com   0 0 0 0 0 0
1745 2006-05-02 19:23:21 2006-10-16 15:06:11 2019-06-24 00:33:47.571909 Unreviewed closed Metasystem defect normal master fixed [patch] Accessing many-to-many relationships without a PK value should throw exceptions For background, see: http://groups.google.com/group/django-users/browse_frm/thread/9ab2c6f7115a1c1b/6f859e5f1941f3c1#6f859e5f1941f3c1 Basically, if you access m2m fields before the object has a primary key value, you get incorrect results. The attached patch fixes this and throws a helpful exception. It also includes a fix for a nonsense test that was discovered by the patch. adrian lukeplant   0 1 0 0 0 0
1785 2006-05-06 20:43:01 2006-10-16 14:21:33 2019-06-24 00:34:13.768215 Unreviewed closed Core (Other)   major   fixed debug.py assumes _get_lines_from_file() doesn't return None if an error occurs during view processing, debug.py has a bug such that, on occasion, debug traceback printing fails and you cannot see what your error was. Here's the debug.py traceback. Also see the attached patch for a fix that works in my development environment. Development server is running at Quit the server with CONTROL-C. [06/May/2006 13:39:57] "GET /rate/1/3?dojo.transport=xmlhttp& HTTP/1.1" 301 0 Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/servers/basehttp.py", line 272, in run self.result = application(self.environ, self.start_response) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/servers/basehttp.py", line 615, in __call__ return self.application(environ, start_response) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 145, in __call__ response = self.get_response(request.path, request) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/handlers/base.py", line 100, in get_response return self.get_technical_error_response(request) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/core/handlers/base.py", line 133, in get_technical_error_response return debug.technical_500_response(request, *sys.exc_info()) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/django/views/debug.py", line 100, in technical_500_response frames.append({ TypeError: unsupported operand type(s) for +: 'NoneType' and 'int' [06/May/2006 13:39:57] "GET /rate/1/3/?dojo.transport=xmlhttp HTTP/1.1" 500 1349 adrian django@binaryfeed.org   0 0 0 0 0 0
2012 2006-05-26 16:22:21 2006-10-16 15:41:49 2019-06-24 00:36:38.815087 Unreviewed closed Documentation defect normal   fixed We need a central place to list things that are being developed Currently, finding out whether something is being worked on, or is currently non-functional, is somewhat difficult; this can involve a lot of digging through Trac and hunting for wiki pages (and sometimes the wiki pages aren't linked off the index, let alone listed with the "under discussion" links). It'd be nice to have some place, possibly a prominent link on the wiki, which documents these things. At the current moment, I'm thinking of something like mentioning clearly that model subclassing for post-m-r trunk is still being worked on, and pointing out that schema evolution is also being worked on, since those seem to be the top two most-often-asked questions right now. jacob ubernostrum   0 0 0 0 0 0
2034 2006-05-30 10:48:42 2006-10-16 14:53:17 2019-06-24 00:36:52.376921 Unreviewed closed Core (Other) defect normal master fixed [patch] sqlinitialdata broken in mysql I think [2985] broke sqlinitialdata in mysql. It seems to strip trailing semicolons, and hence errors out on hitting the next sql statement. adrian Joeboy   0 1 0 0 0 0
2054 2006-05-31 20:11:05 2006-10-16 15:36:51 2019-06-24 00:37:05.061264 Unreviewed closed Documentation enhancement minor   fixed [PATCH] Update core description in the model API to clarify behaviour The description of the core argument is not complete. Right now if you use the admin and you marked a field as blank = True, putting a core = True will effectively cause it to non-optional. If you leave such a field blank and you save it, the object will not be saved. jacob asmodai@in-nomine.org   0 0 0 0 0 0
2069 2006-06-02 12:10:01 2006-10-16 15:11:19 2019-06-24 00:37:14.481777 Unreviewed closed contrib.admin defect normal   invalid try to run the admin first I am just starting the 2nd tutorial: when i run the command, python manager.py syncdb, i get this result: Error: None couldn't be installed, because there were errors in your model: admin.logentry: 'user' has relation with uninstalled model User admin.logentry: 'content_type' has relation with uninstalled model ContentType Any idea? thanks adrian matt   0 0 0 0 0 0
2100 2006-06-06 20:47:29 2006-10-16 15:31:40 2019-06-24 00:37:34.609366 Unreviewed closed Internationalization enhancement normal   fixed [patch] admin change list i18n patchlets This patch makes translatable the following items of the change list page: * The search results counter and total item count, in the search form * The "View all" text that appears at the right of the paginator when activated * The "Filter" text at the top of the list_filer sidebar Hope this those are the last pieces of hard coded text in this app templates. There are a couple of things left in the javascript stuff, I will try to submit a patch for that too. Regards, hugo ramiro   0 1 0 0 0 0
2128 2006-06-10 08:51:42 2006-10-16 15:06:11 2019-06-24 00:37:53.140713 Unreviewed closed Internationalization enhancement normal   fixed Updated BiDi support (styles, templates, JS) This follows #2089 and [http://groups.google.com/group/Django-I18N/browse_thread/thread/b3ec690839a1fc38/e8d0909ac9fe7217#e8d0909ac9fe7217 this discussion at django-i18n]. As decided, all overided styles should be in a single rtl stylesheet. Please remove : * django/contrib/admin/media/css/base_rtl.css * django/contrib/admin/media/css/dashboard_rtl.css * django/contrib/admin/media/css/login_rtl.css They'll be replaced by rtl.css which is fed from base.html. See also attached screenshot for a sample of the bidi admin interface. hugo meir@mksoft.co.il   0 0 0 0 0 0
2147 2006-06-13 20:58:28 2006-10-16 14:21:19 2019-06-24 00:38:05.126560 Unreviewed closed Generic views defect normal   fixed [patch] Fixes FileField/UploadField in update_object As it stands, file uploads don't work if you use the update_object generic view. This patch corrects that. jacob anonymous   0 1 0 0 0 0
2158 2006-06-14 16:14:46 2006-10-16 14:21:25 2019-06-24 00:38:12.134613 Unreviewed closed Contrib apps enhancement normal master fixed [patch] Syndication framework doesn't allow custom template paths. Let me illustrate this with an example. I have two sorts of feeds in my app: /authors/feed/ # simple feed of all authors[[BR]] /authors/authorname/feed/ # complex per-author feed Defined by the following URLconf {{{ feeds = { 'authors': AuthorsFeed, } author_feed = { 'authors': AuthorFeed, } (r'^(?P<url>authors/[-\w]+)/feed/$', 'feed', {'feed_dict': author_feed}), (r'^(?P<url>authors)/feed/$', 'feed', {'feed_dict': feeds}), }}} The problem is that both urls share the same slug "authors" which determines the feed model to use and—more critically—the template paths (authors_description, authors_title) I managed to work around the model issue by specifying two different feed_dicts but I can't see a way to specify different templates for each feed without patching django.contrib.syndication.views. adrian James Wheare syndication, feeds, templates, urls 0 1 0 0 0 0
2235 2006-06-26 02:10:05 2006-10-16 15:29:56 2019-06-24 00:39:01.445738 Unreviewed closed Documentation defect normal master fixed Typo in docs for inclusion_tag decorator In the templates-for-programmers section, the example suggests a 2.4 decorator: {{{ @inclusion_tag('results.html') def show_results(poll): ... }}} But I believe one needs to have it like so: {{{ @register.inclusion_tag('results.html') def show_results(poll): ... }}} jacob jvinet@zeroflux.org   0 0 0 0 0 0
2262 2006-06-29 02:44:18 2006-10-16 15:06:02 2019-06-24 00:39:18.625255 Unreviewed closed Database layer (models, ORM) defect normal master duplicate [patch] ManyToManyField with blank=True errors out when the field is blank I have a ManyToManyField with blank=True in a model that is in being edited inline, and whenever I add a new item with a blank entry in that field, I would receive an error about missing set_fieldname. So I threw together a quick patch and it is working for me currently. This is my first stab at working with Django, so the logic may be a bit off. adrian rayners@gmail.com   0 1 0 0 0 0
2312 2006-07-08 13:52:55 2006-10-16 14:21:24 2019-06-24 00:39:50.673603 Unreviewed closed contrib.admin defect minor master fixed E-mail validator should accept new TLDs such as ".museum" Id doesn't accept new TLDs like '''.museum''' adrian anonymous   0 0 0 0 0 0
2371 2006-07-18 11:41:17 2006-10-16 15:39:37 2019-06-24 00:40:27.820091 Unreviewed closed Translations enhancement normal   fixed Tamil .po file .po file with Tamil translations hugo rha@au-kbc.org   0 0 0 0 0 0
2387 2006-07-21 02:39:15 2006-10-16 15:32:58 2019-06-24 00:40:38.228099 Unreviewed closed Generic views defect normal master invalid "object_list" is empty in archive_year generic view Using a minimal test case (attached), I created two object (though this works with a wide range of number of objects) the "object_list" context of the archive_year generic view is empty, even though there are objects with dates within the year I am trying to view. jacob Tyson Tate <tyson@fallingbullets.com> genericview object_list 0 0 0 0 0 0
2617 2006-08-29 19:28:51 2006-10-16 15:31:42 2019-06-24 00:43:04.984576 Unreviewed closed Translations enhancement normal   fixed First stab at a Finnish translation I have made an incomplete but fairly usable Finnish Django translation. hugo akaihola   0 0 0 0 0 0
2623 2006-08-30 11:28:02 2006-10-16 14:18:50 2019-06-24 00:43:08.725737 Unreviewed closed Internationalization enhancement normal master fixed [patch] Minimal kk and tr language support   hugo ibr@radix50.net   0 1 0 0 0 0
2798 2006-09-23 08:06:25 2006-10-16 14:21:35 2019-06-24 00:45:00.281241 Unreviewed closed Contrib apps enhancement minor master wontfix [patch] make comments work on models with alphanummmeric PKs Comments don't work on Models using non-integer Primary Keys. The tiny patch below makes them work (with no observable preformance impact). http://c0re.23.nu/c0de/misc/django-r3797-comments_for_objects_with_non_integer_ids.diff {{{ --- django/contrib/comments/models.py (revision 3797) +++ django/contrib/comments/models.py (working copy) @@ -64,7 +64,7 @@ class Comment(models.Model): user = models.ForeignKey(User, raw_id_admin=True) content_type = models.ForeignKey(ContentType) - object_id = models.IntegerField(_('object ID')) + object_id = models.CharField(_('object ID'), maxlength=255) }}} adrian Maximillian dornseif <md@hudora.de>   0 1 0 0 0 0
2836 2006-09-27 23:39:07 2006-10-16 15:02:33 2019-06-24 00:45:23.952605 Unreviewed closed Template system enhancement normal 0.95 worksforme nested for it'd be cool if django had nested {% for %} for it's template system. for example if pass a dict like this to the template system: {'myvar': {'list': [<Object: Thing1>, <Object: Thing2>], 'list2': [<Object: OtherThing1>, <Object: OtherThing1>] }, 'myvar2': 'bla'} and then in the template sys: {% for lists in myvar %} {% for object in lists %} {{ object.attribut }} {% endfor %} {% endfor %} adrian anonymous   0 0 0 0 0 0
2911 2006-10-14 15:09:27 2006-10-16 16:23:28 2019-06-24 00:46:11.387973 Unreviewed closed Internationalization defect normal master fixed Add Polish language to the default LANGUAGES list http://www.djangoproject.com/documentation/settings/#languages - LANGUAGES doesn't have Polish by default and it should be added (as it's very annoying when you make a translation and it doesn't want to work for no special reason) PS. It would be nice if diango printed some notice if a not allowed language but existing in translations is called hugo riklaunim@gmail.com   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