tickets
26 rows where "created" is on date 2008-09-04 sorted by resolution
This data as json, CSV (advanced)
Suggested facets: owner, reporter, has_patch, needs_better_patch
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8873 | 2008-09-04 08:49:37 | 2008-09-04 10:21:28 | 2022-03-06 03:43:23.371586 | Unreviewed | closed | *.djangoproject.com | 1.0 | duplicate | FAQ link broken | The bottom of page link to the FAQ (http://docs.djangoproject.com/faq/ is where it points) at the Third Party Distributions page (http://docs.djangoproject.com/en/dev/misc/distributions/#misc-distributions) leads to a "Page not found" page at http://docs.djangoproject.com/faq/dev/. | nobody | DailyWTF | 0 | 0 | 0 | 0 | 0 | 0 | |||
8878 | 2008-09-04 17:01:30 | 2008-09-06 07:37:34 | 2022-03-06 03:43:24.131635 | Unreviewed | closed | contrib.admin | dev | duplicate | Authentication in the admin should not make any assumptions on valid user names | When the user authentication with all configured authentication backend fails, the admin application adds some additional checks when the user name contains the character @.[[BR]] This does't make sense: the admin application can't know what is a valid user name for the backends. For some backends a @ in the user name may well be valid. | nobody | jdetaeye | authentication | 0 | 1 | 0 | 0 | 0 | 0 | ||
8884 | 2008-09-04 21:16:28 | 2008-09-04 21:30:05 | 2022-03-06 03:43:25.169640 | Unreviewed | closed | Documentation | 1.0 | duplicate | Typo in http://docs.djangoproject.com/en/dev/topics/db/models/#automatic-primary-key-fields | Multiple inheritance¶ Just as with Python's subclassing, it's possible for a Django model to inherit from multiple parent models. Keep in mind that normal Python name resolution rules apply. The first base class that a particular name appears in (e.g. Meta) will be the one that is used; for example, '''his''' means that if multiple parents contain a Meta class, only the first one is going to be used, and all others will be ignored. | nobody | schnuffle | Typo | 0 | 0 | 0 | 0 | 0 | 0 | ||
8861 | 2008-09-04 02:28:04 | 2011-09-28 16:12:21 | 2022-03-06 03:43:21.477645 | Accepted | closed | Documentation | 1.0 | fixed | Validation of Forms doesn't mention self.instance | on http://docs.djangoproject.com/en/dev/ref/forms/validation/#ref-forms-validation or on http://docs.djangoproject.com/en/dev/ref/contrib/admin/#adding-custom-validation-to-the-admin does it mention the self.instance variable which is integral in implementing a unique Validator. | jacob | lakin@structuredabstraction.com | 0 | 1 | 0 | 0 | 0 | 0 | |||
8862 | 2008-09-04 02:42:31 | 2008-09-04 11:29:20 | 2022-03-06 03:43:21.655907 | Ready for checkin | closed | *.djangoproject.com | 1.0 | fixed | bad link to faq | Link to http://docs.djangoproject.com/faq/ on the bottom of each FAQ page is invalid. | nobody | anonymous | 0 | 1 | 0 | 0 | 0 | 0 | |||
8863 | 2008-09-04 04:03:41 | 2008-09-06 02:18:02 | 2022-03-06 03:43:21.822194 | Unreviewed | closed | Documentation | 1.0 | fixed | Accidental duplication of word in 'porting guide'. | Found an accidental duplication of a word in the '1.0 porting guide' """ The oldforms module was also removed removed. """ Should likely say: """ The oldforms module was also removed. """ url of occurance: http://docs.djangoproject.com/en/dev/releases/1.0-porting-guide/ | nobody | cactus | 0 | 0 | 0 | 0 | 0 | 0 | |||
8865 | 2008-09-04 06:02:26 | 2008-09-17 09:32:37 | 2022-03-06 03:43:22.137402 | Unreviewed | closed | Testing framework | 1.0 | fixed | fields.py regression test fails | I'm getting a failure with tests/regressiontests/forms/fields.py {{{ ====================================================================== FAIL: Doctest: regressiontests.forms.tests.__test__.fields_tests ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/test/_doctest.py", line 2180, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for regressiontests.forms.tests.__test__.fields_tests File "/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/tests/regressiontests/forms/tests.py", line unknown line number, in fields_tests ---------------------------------------------------------------------- File "/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/tests/regressiontests/forms/tests.py", line ?, in regressiontests.forms.tests.__test__.fields_tests Failed example: fix_os_paths(f.choices) Expected: [('.../django/forms/__init__.py', '__init__.py'), ('.../django/forms/__init__.pyc', '__init__.pyc'), ('.../django/forms/fields.py', 'fields.py'), ('.../django/forms/fields.pyc', 'fields.pyc'), ('.../django/forms/forms.py', 'forms.py'), ('.../django/forms/forms.pyc', 'forms.pyc'), ('.../django/forms/models.py', 'models.py'), ('.../django/forms/models.pyc', 'models.pyc'), ('.../django/forms/util.py', 'util.py'), ('.../django/forms/util.pyc', 'util.pyc'), ('.../django/forms/widgets.py', 'widgets.py'), ('.../django/forms/widgets.pyc', 'widgets.pyc')] Got: [('/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/forms/__init__.py', '__init__.py'), ('/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/forms/fields.py', 'fields.py'), ('/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/forms/forms.py', 'forms.py'), ('/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/django/forms/formsets.py', 'formsets.py'), ('/var/tmp/portage/dev-python/django-1.0/work/Django-1.0/dj… | nobody | pythonhead@gentoo.org | 0 | 1 | 0 | 0 | 0 | 0 | |||
8867 | 2008-09-04 07:19:03 | 2008-09-04 07:29:27 | 2022-03-06 03:43:22.445901 | Unreviewed | closed | Documentation | 1.0 | fixed | Typo in signals docs | In [http://docs.djangoproject.com/en/dev/ref/signals/#pre-delete] "The actual instance being saved." Should be: "The actual instance being deleted." | nobody | igors | 0 | 0 | 0 | 0 | 0 | 0 | |||
8868 | 2008-09-04 07:25:28 | 2009-02-25 19:51:44 | 2022-03-06 03:43:22.606236 | Unreviewed | closed | contrib.comments | dev | fixed | Templates in comments framework are not marked for translation | Strings in new comments framework templates are not marked for translation. Attached patch fixes this issue by marking user-visible strings in templates for translation. | nobody | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8869 | 2008-09-04 07:35:06 | 2009-02-25 19:51:44 | 2022-03-06 03:43:22.767806 | Unreviewed | closed | contrib.comments | dev | fixed | Templates in comments framework are not XHTML-compliant | The HTML markup used in new comment framework templates is not XHTML-compliant in many places. Attached patch fixes this issue. | nobody | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8870 | 2008-09-04 07:41:22 | 2009-02-25 19:51:44 | 2022-03-06 03:43:22.916644 | Unreviewed | closed | contrib.comments | dev | fixed | Templates in comments framework are not compliant with Django style | In all templates in comment framework all froms have HTTP method uppercased. This is not compliant with style of other Django components. Attached patch fixes this issue. | nobody | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8872 | 2008-09-04 08:08:39 | 2009-02-25 19:51:44 | 2022-03-06 03:43:23.225870 | Ready for checkin | closed | Documentation | 1.0 | fixed | Small typo in commiters.txt | There's a very very very small typo in commiters.txt: {{{ diff --git a/docs/internals/committers.txt b/docs/internals/committers.txt index a623d99..42924b3 100644 --- a/docs/internals/committers.txt +++ b/docs/internals/committers.txt @@ -115,7 +115,7 @@ Joseph Kocherhans .. _charango: http://en.wikipedia.org/wiki/Charango `Luke Plant`_ - Like has contributed many excellent improvements, including database-level + Luke has contributed many excellent improvements, including database-level improvements, the CSRF middleware and many unit tests. .. _luke plant: http://lukeplant.me.uk/ }}} | nobody | telenieko | 0 | 1 | 0 | 0 | 0 | 0 | |||
8875 | 2008-09-04 14:25:51 | 2008-09-06 02:16:36 | 2022-03-06 03:43:23.669631 | Unreviewed | closed | Documentation | 1.0 | fixed | Typos in 1.0-porting-guide | Duplicate removal: "The oldforms module was also removed removed." Erroneous "contribg": "django.contrib.localflavor.usa has been renamed django.contribg.localflavor.us." | nobody | Charlie DeTar | 0 | 0 | 0 | 0 | 0 | 0 | |||
8876 | 2008-09-04 14:26:37 | 2008-09-06 00:07:15 | 2022-03-06 03:43:23.823477 | Accepted | closed | Documentation | 1.0 | fixed | Path to install.txt wrong in INSTALL file | Last line of INSTALL reads: "For more detailed instructions, see docs/install.txt." Should probably read: "For more detailed instructions, see docs/intro/install.txt." (docs/install.txt does not exist in the 1.0 distro) | nobody | Tom Radcliffe | 0 | 0 | 0 | 0 | 0 | 0 | |||
8879 | 2008-09-04 19:44:29 | 2008-10-05 05:16:39 | 2022-03-06 03:43:24.288358 | Accepted | closed | contrib.comments | dev | fixed | ngettext is used in comments framework | There is one place where `ngettext()` is used to translate strings in comment framework code. Since Django is all-unicode inside, `ungettext()` should be used. Attached patch fixes this issue. | nobody | zgoda | 0 | 1 | 0 | 0 | 0 | 0 | |||
8881 | 2008-09-04 20:34:46 | 2009-02-25 19:51:44 | 2022-03-06 03:43:24.595990 | Unreviewed | closed | GIS | 1.0-beta | fixed | LayerMapping Error with more than two fields geometry | If my models have two or more geometry fields: {{{ class Lugares(models.Model) : nombre = models.CharField(max_length=80) punto = models.MultiPointField(null=True, blank=True, srid=4326) poligono = models.MultiPolygonField(null=True, blank=True, srid=4326) objects =models.GeoManager() lm=LayerMapping(Lugares,'/home/woakas/nuevo.shp', mapping,unique={'poligono':'POLYGON','tipolugar':'Ciudad'}) }}} {{{ LayerMapError Traceback (most recent call last) /home/woakas/mig/Migtrace/trunk/src/<ipython console> in <module>() /usr/lib/python2.5/site-packages/django/contrib/gis/utils/layermapping.py in __init__(self, model, data, mapping, layer, source_srs, encoding, transaction_mode, transform, unique) 186 # geometry column). 187 self.model = model --> 188 self.geo_col = self.geometry_column() 189 190 # Checking the source spatial reference system, and getting /usr/lib/python2.5/site-packages/django/contrib/gis/utils/layermapping.py in geometry_column(self) 516 return GeometryColumns.objects.get(**gc_kwargs) 517 except Exception, msg: --> 518 raise LayerMapError('Geometry column does not exist for model. (did you run syncdb?):\n %s' % msg) 519 520 def make_multi(self, geom_type, model_field): LayerMapError: Geometry column does not exist for model. (did you run syncdb?): get() returned more than one GeometryColumns -- it returned 2! Lookup parameters were {'f_table_name': 'migtrace_lugares'} }}} | jbronn | woakas@gmail.com | gis layermapping | 0 | 0 | 0 | 0 | 0 | 0 | ||
8882 | 2008-09-04 21:08:16 | 2008-11-01 19:17:41 | 2022-03-06 03:43:24.808361 | Accepted | closed | Forms | 1.0 | fixed | Inline model formsets break validation for unique and unique_together with foreign keys | The admin site fails when trying to create two registers (not unique) on a model with unique or unique together fields. It doesn't check for the unique statement and database backend raises an IntegrityError exception like this: IntegrityError at /admin/myapp/mymodel/add/ (1062, "Duplicate entry '2-1' for key 2") I haven't checked if the problem exists in "handmade" forms, but in admin site it fails. | brosner | central@evosistemas.com | model-validation | 0 | 0 | 0 | 0 | 0 | 0 | ||
8883 | 2008-09-04 21:11:05 | 2008-09-06 16:52:01 | 2022-03-06 03:43:24.987982 | Unreviewed | closed | Documentation | 1.0 | fixed | doc glitches in model reference intro (writing models) | There are a couple of typos and some ReST errors in `docs/topics/db/models.txt`. In fixing those, I made some minor changes to the text that you may (or may not) want to include. See patch. | nobody | arien | 0 | 1 | 0 | 0 | 0 | 0 | |||
8885 | 2008-09-04 22:45:09 | 2009-10-03 14:03:53 | 2022-03-06 03:43:25.351018 | Accepted | closed | *.djangoproject.com | 1.0 | fixed | HTML markup appearing in title of doc page | The page at [http://docs.djangoproject.com/en/dev/ref/models/options/] has HTML markup appearing in the title for the page. I haven't seen this with other pages, but it's possible this isn't the only affected URL. | nobody | gkelly | 0 | 1 | 1 | 0 | 0 | 0 | |||
8860 | 2008-09-04 02:03:56 | 2009-02-25 19:51:44 | 2022-03-06 03:43:21.337135 | Unreviewed | closed | Documentation | dev | invalid | Where should form classes and formset classes be defined? | The current documentation doesn't say '''where''' form classes and formset classes and so on should be defined. Should they be defined in module models.py or in a separate module forms.py or somewhere else altogether? I think the situation is analogous to admin information which eventually was moved from models.py to admin.py. | nobody | r.topor@griffith.edu.au | forms | 0 | 0 | 0 | 0 | 0 | 0 | ||
8864 | 2008-09-04 04:12:07 | 2008-09-06 02:39:52 | 2022-03-06 03:43:21.974409 | Unreviewed | closed | Documentation | 1.0 | invalid | url example regex typo in '1.0-porting guide' | The following text appears: {{{ Previously, those patterns would have been redirected to have a trailing slash. If you always want a slash on such URLs, rewrite the pattern as: r'/some_prefix/(.*/)$' }}} Seems like the regex for the url-example should be (for clarity): {{{ r'/some_prefix/(.*)/$' }}} url of occurance: http://docs.djangoproject.com/en/dev/releases/1.0-porting-guide/ | nobody | cactus <eliott@cactuswax.net> | 0 | 0 | 0 | 0 | 0 | 0 | |||
8866 | 2008-09-04 06:22:07 | 2009-02-25 19:51:44 | 2022-03-06 03:43:22.289519 | Unreviewed | closed | Documentation | 1.0 | invalid | Built-in Javascript search results' links is missing FILE_SUFFIX | The docs generated by running 'make html' in the docs directory has a built-in javascript search facility (`docs/_build/html/search.html`). The search results' links/URLs are incorrect because they're missing the ".html" suffix in the file name. If I edit `search.html` and set FILE_SUFFIX to '.html' in the top javascript section then the search results links work. | nobody | ronny | search | 0 | 0 | 0 | 0 | 0 | 0 | ||
8874 | 2008-09-04 12:30:05 | 2012-01-27 22:12:24 | 2022-03-06 03:43:23.518986 | Accepted | closed | Core (Other) | Uncategorized | Normal | dev | invalid | problem with URLs on FastCGI after update to 1.0 | all URI resolve to root(/) after updating django from beta to 1.0-release. here is part of urls.py: {{{ urlpatterns = patterns('', (r'^$', 'src.views.main_index'), (r'^feedback/$', 'src.views.feedback'), (r'^admin/(.*)', admin.site.root) ) }}} trying to access /feedback/ but always get result of 'src.views.main_index'. | kyprizel | kyprizel | 0 | 1 | 0 | 0 | 0 | 0 | |
8877 | 2008-09-04 16:14:39 | 2008-09-04 16:49:51 | 2022-03-06 03:43:23.966476 | Unreviewed | closed | Core (Other) | 1.0 | invalid | Very strange bug in MySQL backend for exact query. | I have a User object whose username is 'jumann'. When I do this: {{{ >>> User.objects.get(username__exact='Jumann') }}} I got a user object <User: jumann>. This is bug? The SQL generated is: {{{ >>> connection.queries[-1]['sql'] u'SELECT `auth_user`.`id`, `auth_user`.`username`, `auth_user`.`first_name`, `auth_user`.`last_name`, `auth_user`.`email`, `auth_user`.`password`, `auth_user`.`is_staff`, `auth_user`.`is_active`, `auth_user`.`is_superuser`, `auth_user`.`last_login`, `auth_user`.`date_joined` FROM `auth_user` WHERE `auth_user`.`username` = Jumann ' }}} This is a invalid SQL statement, because the string Jumann is not quoted. But I don't know why it will pass and give me a wrong result. This problem is very serious... | nobody | bear330 | get exact SQL ORM MySQL | 0 | 0 | 0 | 0 | 0 | 0 | ||
8871 | 2008-09-04 07:59:26 | 2008-09-04 09:07:26 | 2022-03-06 03:43:23.071723 | Unreviewed | closed | Uncategorized | 1.0 | wontfix | django.get_version: 1.0-final-SVN-unknown | `django.get_version()` returns u'1.0-final-SVN-unknown' instead of u'1.0' or u'1.0-final'. | nobody | pythy | 0 | 0 | 0 | 0 | 0 | 0 | |||
8880 | 2008-09-04 20:13:19 | 2008-10-15 03:55:19 | 2022-03-06 03:43:24.432129 | Unreviewed | closed | Template system | 1.0 | wontfix | bit of django.template source doc | Just added a sample code for the Lexer | nobody | hvendelbo | 0 | 1 | 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 );