tickets
23 rows where "created" is on date 2007-09-10 sorted by resolution
This data as json, CSV (advanced)
Suggested facets: stage, component, version, summary, description, has_patch, needs_tests, changetime (date), last_pulled_from_trac (date)
reporter 12 ✖
- Petr Marhoun <petr.marhoun@gmail.com> 8
- anonymous 5
- Boo <boobsd@gmail.com> 1
- Danilo 1
- Ludovico Magnocavallo <ludo@qix.it> 1
- Matthew Flanagan <mattimustang@gmail.com> 1
- Nathaniel Whiteinge <whiteinge@eseth.com> 1
- czajnik@czajsoft.pl 1
- jkocherhans 1
- mikkel@hoegh.org 1
- toddobryan 1
- zhaoz@u.washington.edu 1
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
5391 | 2007-09-10 16:56:06 | 2007-09-16 22:07:42 | 2022-03-06 03:34:15.843608 | Unreviewed | closed | contrib.admin | dev | duplicate | date_hierarchy breaks for date objects of January 1st | Verified with the following test model. Add a few entries of January 1st for differing years. DateTimeField fields do not have this problem. Appears to affect at least SQLite and MySQL. {{{ class Test(models.Model): test = models.DateField() class Admin: date_hierarchy = 'test' def __unicode__(self): return str(self.test) }}} | nobody | Nathaniel Whiteinge <whiteinge@eseth.com> | date_hierarchy qs-rf | 0 | 0 | 0 | 0 | 0 | 0 | ||
5374 | 2007-09-10 00:48:03 | 2011-09-28 16:12:16 | 2022-03-06 03:34:13.034398 | Accepted | closed | Core (Other) | newforms-admin | fixed | We need a validator for ModelAdmin classes | {{{get_validation_errors}}} needs to be updated to deal with {{{ModelAdmin}}} classes instead of the old inline {{{Admin}}} classes. It may be desirable for {{{ModelAdmin}}} to know how to validate itself (and by 'validate' I basically mean catching invalid attribute names). | brosner | jkocherhans | nfa-blocker | 0 | 1 | 1 | 1 | 1 | 0 | ||
5375 | 2007-09-10 02:03:31 | 2007-09-10 02:07:58 | 2022-03-06 03:34:13.183854 | Unreviewed | closed | Core (Management commands) | dev | fixed | django-admin.py dumpdata fails because it doesn't inherit options_list from BaseCommand | Running {{{django-admin.py dumpdata}} fails with the following traceback: {{{ Traceback (most recent call last): File "./manage.py", line 11, in ? execute_manager(settings) File "/xxx/django/django/core/management/__init__.py", line 163, in execute_manager utility.execute(argv) File "/xxx/django/django/core/management/__init__.py", line 107, in execute self.fetch_command(command_name, argv[0]).run(argv[1:]) File "/xxx/django/django/core/management/base.py", line 59, in run if options.settings: AttributeError: Values instance has no attribute 'settings' }}} because it doesn't append its own options to the BaseCommand options_list. Simple patch is {{{ Index: django/core/management/commands/dumpdata.py =================================================================== --- django/core/management/commands/dumpdata.py (revision 6080) +++ django/core/management/commands/dumpdata.py (working copy) @@ -3,7 +3,7 @@ from optparse import make_option class Command(BaseCommand): - option_list = ( + option_list = BaseCommand.option_list + ( make_option('--format', default='json', dest='format', help='Specifies the output serialization format for fixtures'), make_option('--indent', default=None, dest='indent', type='int', }}} | nobody | Matthew Flanagan <mattimustang@gmail.com> | 0 | 1 | 0 | 0 | 0 | 0 | |||
5376 | 2007-09-10 02:40:21 | 2007-09-16 16:01:25 | 2022-03-06 03:34:13.329400 | Ready for checkin | closed | Core (Management commands) | dev | fixed | Add --addrport option to testserver command | Because the `testserver` command takes fixtures as arguments, you can't currently set the IP address or port that it should use when it runs the server. This ticket adds the option `--addrport` to `testserver` and just passes it to the `runserver` command. | toddobryan | toddobryan | 0 | 1 | 0 | 0 | 0 | 0 | |||
5383 | 2007-09-10 13:52:01 | 2007-09-12 01:34:26 | 2022-03-06 03:34:14.465569 | Accepted | closed | contrib.admin | newforms-admin | fixed | [newforms-admin] - InlineModelAdmin.formset_class is used but not set. | I think there is a little bug in [6080]. In InlineModelAdmin._fieldsets ([http://code.djangoproject.org/browser/django/branches/newforms-admin/django/contrib/admin/options.py#L684 row 684]) attribute formset_class is used. But it was removed from init in [6080]. Attached patch gives it back. I am not sure if it is the right solution - maybe only fields should be saved. See also #5372 - I think that it isn't a good idea to use one formset_class for all requests. | jkocherhans | Petr Marhoun <petr.marhoun@gmail.com> | newforms, admin, inlines | 0 | 1 | 0 | 0 | 0 | 0 | ||
5384 | 2007-09-10 14:39:08 | 2007-09-12 01:30:50 | 2022-03-06 03:34:14.664802 | Ready for checkin | closed | contrib.admin | newforms-admin | fixed | [newforms-admin] - html bug in edit_inline_tabular.html | There is an unclosed td tag in template admin/edit_inline_tabular.html. Attached patch solves it. | nobody | Petr Marhoun <petr.marhoun@gmail.com> | newforms, admin, inlines | 0 | 1 | 0 | 0 | 0 | 0 | ||
5385 | 2007-09-10 14:49:56 | 2011-09-28 16:12:17 | 2022-03-06 03:34:14.854754 | Ready for checkin | closed | contrib.admin | newforms-admin | fixed | [newforms-admin] - inconsistency in admin date fields from javascript | Usual format for dates in admin is 2007-09-02. But javascript code uses format 2007-9-2. I thing it is inconsistent and it should be fixed. Attached patch solves it. | xian | Petr Marhoun <petr.marhoun@gmail.com> | nfa-someday admin, javascript | 0 | 1 | 0 | 0 | 0 | 0 | ||
5386 | 2007-09-10 15:54:36 | 2008-07-09 16:41:30 | 2022-03-06 03:34:15.051074 | Accepted | closed | Forms | dev | fixed | content type for newforms.UploadedFile | I think that it would be nice if django.newforms.UploadedFile has attribute content_type - see the attached patch. | nobody | Petr Marhoun <petr.marhoun@gmail.com> | newforms, file uploads | 0 | 1 | 0 | 0 | 0 | 0 | ||
5387 | 2007-09-10 16:07:06 | 2007-09-15 10:12:06 | 2022-03-06 03:34:15.214245 | Accepted | closed | Forms | dev | fixed | method Form.is_multipart | I would like to write this in a general template: {{{ #!html {% if form.is_multipart %} <form action="." method="post" enctype="multipart/form-data"> {% else %} <form action="." method="post"> {% endif %} }}} I can do it with the attached patch. | murkt | Petr Marhoun <petr.marhoun@gmail.com> | newforms, is_multipart, sprintsept14 | 0 | 1 | 0 | 0 | 0 | 0 | ||
5388 | 2007-09-10 16:29:11 | 2007-09-12 01:37:40 | 2022-03-06 03:34:15.404869 | Ready for checkin | closed | Forms | newforms-admin | fixed | [newforms-admin] - validation is broken for sites with more than one inline formsets | Validation of inline formsets is done with this code: {{{ #!python def all_valid(formsets): """Returns true if every formset in formsets is valid.""" valid = True for formset in formsets: if not formset.is_valid(): return False }}} But method formset.is_valid has side-effect - it calls formset.clean_all and method clean_all resets all unused inline formset. But if first formset is invalid, forms in the second formset aren't reset. This code works (attached patch changes it): {{{ #!python def all_valid(formsets): """Returns true if every formset in formsets is valid.""" valid = True for formset in formsets: if not formset.is_valid(): valid = False return valid }}} | jkocherhans | Petr Marhoun <petr.marhoun@gmail.com> | newforms, admin, inlines | 0 | 1 | 0 | 0 | 0 | 0 | ||
5390 | 2007-09-10 16:43:39 | 2012-01-09 08:44:50 | 2022-03-06 03:34:15.704844 | Design decision needed | closed | Database layer (models, ORM) | Uncategorized | Normal | dev | fixed | Add signals to ManyRelatedManager | There's currently no way to run some custom code when the ManyRelatedManager adds, removes, or clears objects. Extending the ManyRelatedManager is very hard, since it's dynamically created each time, and the ManyRelatedObjectsDescriptor prevents any access to it from its container class. A simple solution is to add three signals, and hook them into the dispatching mechanism when adding, removing, or deleting a related object. A typical use case for attaching custom code to a MayRelatedManager is blog categories: having a num_posts field in the Category models, and updating it each time a category is added/removed to/from a post, speeds up considerably a simple category list that excludes empty categories, and counts only published posts. The difference in resource usage is huge -- one query with two simple filters against one query for the list, plus one for each category (yes, you can cache the output, but think eg of a multi-blog app where posts are frequently updated, and a cache miss is very expensive), and the resulting code is much simpler. A simple patch is attached to this ticket, I have tested it briefly against some of my models and it appears to work ok. | rvdrijst | Ludovico Magnocavallo <ludo@qix.it> | manytomanyfield feature signals | 0 | 1 | 0 | 0 | 0 | 0 |
5392 | 2007-09-10 17:11:15 | 2010-09-11 22:49:08 | 2022-03-06 03:34:15.978819 | Design decision needed | closed | contrib.admin | newforms-admin | fixed | [newforms-admin] - hooks for template names | I think it is possible to have more admin sites in one project. And it would be nice to have different default templates for these two sites - these templates should be independent on application. So I would like to have some hooks as changelist_templates, add_templates and so on. For example this code could be changed: {{{ #!python class ModelAdmin(BaseModelAdmin): def changelist_view(self, request): ### ... return render_to_response(['admin/%s/%s/change_list.html' % (app_label, opts.object_name.lower()), 'admin/%s/change_list.html' % app_label, 'admin/change_list.html'], context_instance=c) }}} New variant: {{{ #!python class ModelAdmin(BaseModelAdmin): def changelist_view(self, request): ### ... return render_to_response(self.changelist_templates(app_label, opts.object_name.lower()), context_instance=c) def changelist_templates(self, app_label, object_label): return ['admin/%s/%s/change_list.html' % (app_label, opts.object_name.lower()), 'admin/%s/change_list.html' % app_label, 'admin/change_list.html'] }}} I haven't need it yet so I have no patch. But it is no problem for me to create it - if you think it is a good idea. | nobody | Petr Marhoun <petr.marhoun@gmail.com> | nfa-someday | 0 | 0 | 1 | 0 | 0 | 0 | ||
5394 | 2007-09-10 18:06:55 | 2007-09-14 19:25:38 | 2022-03-06 03:34:16.300341 | Accepted | closed | Contrib apps | dev | fixed | REDIRECT_FIELD_NAME should be configurable | I think that it should be possible to set REDIRECT_FIELD_NAME in settings.py. For example it can be useful if I want to have url in another language than English. It is changed by the attached patch. | DavidReynolds | Petr Marhoun <petr.marhoun@gmail.com> | authorization, redirection, sprintsept14 | 0 | 1 | 0 | 0 | 0 | 0 | ||
5395 | 2007-09-10 19:35:28 | 2007-09-13 14:37:23 | 2022-03-06 03:34:16.468088 | Unreviewed | closed | Uncategorized | dev | fixed | Error in settings.py, line 26-28 | settings.py (in a newly started project) states this: {{{ # Language code for this installation. All choices can be found here: # http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes LANGUAGE_CODE = 'en-us' }}} That is, however, not true. The document at that URI does in fact not have a list of applicable choices. It describes the syntax for them, however. Either the text should be changed or we should find a location where ''all choices can be found'' (which I think would be more helpful). | nobody | mikkel@hoegh.org | 0 | 0 | 0 | 0 | 0 | 0 | |||
5397 | 2007-09-10 22:48:01 | 2007-09-13 14:38:25 | 2022-03-06 03:34:16.805848 | Unreviewed | closed | Documentation | dev | fixed | Typo in example for newforms -- overriding the default field types | http://www.djangoproject.com/documentation/newforms/#overriding-the-default-field-types Seems to have a bad example, (missing the model to create the ArticleForm from): {{{ ArticleForm = form_for_model(formfield_callback=my_callback) }}} Should be more like: {{{ ArticleForm = form_for_model(Article, formfield_callback=my_callback) }}} | nobody | zhaoz@u.washington.edu | 0 | 0 | 0 | 0 | 0 | 0 | |||
5377 | 2007-09-10 07:06:15 | 2007-09-10 07:15:19 | 2022-03-06 03:34:13.467970 | Unreviewed | closed | Uncategorized | dev | invalid | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 北京百润慧通电子技术有限公司是集LED显示屏、LED外延应用产品科研开发、生产、销售、安装及培训服务于一体的高新科技产业公司。公司的产品已形成完整的系列,应用于室内、室外、半室外各种场所的单色显示屏、伪彩色显示屏、全彩色显示屏等达二十多个品种。产品应用范围涉及机场、火车站、汽车站、大型体育及会展场馆、智能交通、高速公路、银行、广告、电力、商业、电信、医院、税务、银行、交易市场、市民广场等几乎所有的相关系统及行业。公司建立了具有现代化管理、设备先进的显示屏生产加工基地。公司视产品品质为企业的生命,对每一项产品都进行严谨的工艺设计、严密生产监督和质量检测,从而确保了产品的高可靠性。 公司特别重视产品的售后服务,建立了完善的售后服务体系,向用户提供免费培训、定期巡检、反应迅捷、终身维护的服务承诺。本公司将秉承“执着进取、追求完美”的理念以孜孜不倦的勤奋精神向用户提供优质的服务。 公司产品全面贯彻信息产业部<<LED显示屏通用规范>>的要求,秉承“以质量、服务、诚信为发展根本”的企业精神,从产品开发、试制、生产、检测、安装、服务建立健全了完善的产品质量保证体系。公司与规模庞大的支持屏体生产的管芯厂、封装厂、LED数码管,发光管、点阵模块、电源、PCB、加工生产厂等数家专业配套厂有良好的商业合作关系,我们将共同完成LED产业纵向一体化宏伟目标。 我们相信:我们以优良的整体设计、完美的细节表现及完善的服务体系,终将成为您真诚永远的合作伙伴。 企业宗旨:发展光电科技 企业目标:打造知名品牌 企业精神:追求卓越品质 企业价值观:开拓创新,诚实守信,以客户为本 百润慧通具有从LED显示屏的开发、设计到制造、组装等一条龙生产设备。有国际先进水平的全自动贴片机、波峰焊、回流焊机、超声波清洗机;专用生产、调试车间和成套测试仪器等。经过多年的发展,自身的管理机制、技术开发、品质体系、服务导向等已日趋成熟,在国内LED业界始终保持着领先地位。 北京百润慧通电子技术有限责任公司 销售部: 联系电话:010-52566097 52566451 24小时售前产品咨询热线:13911588988 技术部: 联系电话: 010-52566452 24小时售后产品技术支持:13911205351 生产工程部: 联系电话:010-52566453 24小时售后产品维修电话:13811164442 地址:北京市昌平区定福皇庄钢材木材市场7号院(102208) 电子邮件:panelway@126.com 网址:http://www.panelway.com | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
5378 | 2007-09-10 07:06:33 | 2007-09-10 07:15:03 | 2022-03-06 03:34:13.631248 | Unreviewed | closed | Uncategorized | dev | invalid | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 北京百润慧通电子技术有限公司是集LED显示屏、LED外延应用产品科研开发、生产、销售、安装及培训服务于一体的高新科技产业公司。公司的产品已形成完整的系列,应用于室内、室外、半室外各种场所的单色显示屏、伪彩色显示屏、全彩色显示屏等达二十多个品种。产品应用范围涉及机场、火车站、汽车站、大型体育及会展场馆、智能交通、高速公路、银行、广告、电力、商业、电信、医院、税务、银行、交易市场、市民广场等几乎所有的相关系统及行业。公司建立了具有现代化管理、设备先进的显示屏生产加工基地。公司视产品品质为企业的生命,对每一项产品都进行严谨的工艺设计、严密生产监督和质量检测,从而确保了产品的高可靠性。 公司特别重视产品的售后服务,建立了完善的售后服务体系,向用户提供免费培训、定期巡检、反应迅捷、终身维护的服务承诺。本公司将秉承“执着进取、追求完美”的理念以孜孜不倦的勤奋精神向用户提供优质的服务。 公司产品全面贯彻信息产业部<<LED显示屏通用规范>>的要求,秉承“以质量、服务、诚信为发展根本”的企业精神,从产品开发、试制、生产、检测、安装、服务建立健全了完善的产品质量保证体系。公司与规模庞大的支持屏体生产的管芯厂、封装厂、LED数码管,发光管、点阵模块、电源、PCB、加工生产厂等数家专业配套厂有良好的商业合作关系,我们将共同完成LED产业纵向一体化宏伟目标。 我们相信:我们以优良的整体设计、完美的细节表现及完善的服务体系,终将成为您真诚永远的合作伙伴。 企业宗旨:发展光电科技 企业目标:打造知名品牌 企业精神:追求卓越品质 企业价值观:开拓创新,诚实守信,以客户为本 百润慧通具有从LED显示屏的开发、设计到制造、组装等一条龙生产设备。有国际先进水平的全自动贴片机、波峰焊、回流焊机、超声波清洗机;专用生产、调试车间和成套测试仪器等。经过多年的发展,自身的管理机制、技术开发、品质体系、服务导向等已日趋成熟,在国内LED业界始终保持着领先地位。 北京百润慧通电子技术有限责任公司 销售部: 联系电话:010-52566097 52566451 24小时售前产品咨询热线:13911588988 技术部: 联系电话: 010-52566452 24小时售后产品技术支持:13911205351 生产工程部: 联系电话:010-52566453 24小时售后产品维修电话:13811164442 地址:北京市昌平区定福皇庄钢材木材市场7号院(102208) 电子邮件:panelway@126.com 网址:http://www.panelway.com | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
5379 | 2007-09-10 07:07:09 | 2007-09-10 07:14:52 | 2022-03-06 03:34:13.774902 | Unreviewed | closed | Uncategorized | dev | invalid | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 北京百润慧通电子技术有限公司是集LED显示屏、LED外延应用产品科研开发、生产、销售、安装及培训服务于一体的高新科技产业公司。公司的产品已形成完整的系列,应用于室内、室外、半室外各种场所的单色显示屏、伪彩色显示屏、全彩色显示屏等达二十多个品种。产品应用范围涉及机场、火车站、汽车站、大型体育及会展场馆、智能交通、高速公路、银行、广告、电力、商业、电信、医院、税务、银行、交易市场、市民广场等几乎所有的相关系统及行业。公司建立了具有现代化管理、设备先进的显示屏生产加工基地。公司视产品品质为企业的生命,对每一项产品都进行严谨的工艺设计、严密生产监督和质量检测,从而确保了产品的高可靠性。 公司特别重视产品的售后服务,建立了完善的售后服务体系,向用户提供免费培训、定期巡检、反应迅捷、终身维护的服务承诺。本公司将秉承“执着进取、追求完美”的理念以孜孜不倦的勤奋精神向用户提供优质的服务。 公司产品全面贯彻信息产业部<<LED显示屏通用规范>>的要求,秉承“以质量、服务、诚信为发展根本”的企业精神,从产品开发、试制、生产、检测、安装、服务建立健全了完善的产品质量保证体系。公司与规模庞大的支持屏体生产的管芯厂、封装厂、LED数码管,发光管、点阵模块、电源、PCB、加工生产厂等数家专业配套厂有良好的商业合作关系,我们将共同完成LED产业纵向一体化宏伟目标。 我们相信:我们以优良的整体设计、完美的细节表现及完善的服务体系,终将成为您真诚永远的合作伙伴。 企业宗旨:发展光电科技 企业目标:打造知名品牌 企业精神:追求卓越品质 企业价值观:开拓创新,诚实守信,以客户为本 百润慧通具有从LED显示屏的开发、设计到制造、组装等一条龙生产设备。有国际先进水平的全自动贴片机、波峰焊、回流焊机、超声波清洗机;专用生产、调试车间和成套测试仪器等。经过多年的发展,自身的管理机制、技术开发、品质体系、服务导向等已日趋成熟,在国内LED业界始终保持着领先地位。 北京百润慧通电子技术有限责任公司 销售部: 联系电话:010-52566097 52566451 24小时售前产品咨询热线:13911588988 技术部: 联系电话: 010-52566452 24小时售后产品技术支持:13911205351 生产工程部: 联系电话:010-52566453 24小时售后产品维修电话:13811164442 地址:北京市昌平区定福皇庄钢材木材市场7号院(102208) 电子邮件:panelway@126.com 网址:http://www.panelway.com | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
5380 | 2007-09-10 07:07:20 | 2007-09-10 07:14:43 | 2022-03-06 03:34:13.921144 | Unreviewed | closed | Uncategorized | dev | invalid | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 北京百润慧通电子技术有限公司是集LED显示屏、LED外延应用产品科研开发、生产、销售、安装及培训服务于一体的高新科技产业公司。公司的产品已形成完整的系列,应用于室内、室外、半室外各种场所的单色显示屏、伪彩色显示屏、全彩色显示屏等达二十多个品种。产品应用范围涉及机场、火车站、汽车站、大型体育及会展场馆、智能交通、高速公路、银行、广告、电力、商业、电信、医院、税务、银行、交易市场、市民广场等几乎所有的相关系统及行业。公司建立了具有现代化管理、设备先进的显示屏生产加工基地。公司视产品品质为企业的生命,对每一项产品都进行严谨的工艺设计、严密生产监督和质量检测,从而确保了产品的高可靠性。 公司特别重视产品的售后服务,建立了完善的售后服务体系,向用户提供免费培训、定期巡检、反应迅捷、终身维护的服务承诺。本公司将秉承“执着进取、追求完美”的理念以孜孜不倦的勤奋精神向用户提供优质的服务。 公司产品全面贯彻信息产业部<<LED显示屏通用规范>>的要求,秉承“以质量、服务、诚信为发展根本”的企业精神,从产品开发、试制、生产、检测、安装、服务建立健全了完善的产品质量保证体系。公司与规模庞大的支持屏体生产的管芯厂、封装厂、LED数码管,发光管、点阵模块、电源、PCB、加工生产厂等数家专业配套厂有良好的商业合作关系,我们将共同完成LED产业纵向一体化宏伟目标。 我们相信:我们以优良的整体设计、完美的细节表现及完善的服务体系,终将成为您真诚永远的合作伙伴。 企业宗旨:发展光电科技 企业目标:打造知名品牌 企业精神:追求卓越品质 企业价值观:开拓创新,诚实守信,以客户为本 百润慧通具有从LED显示屏的开发、设计到制造、组装等一条龙生产设备。有国际先进水平的全自动贴片机、波峰焊、回流焊机、超声波清洗机;专用生产、调试车间和成套测试仪器等。经过多年的发展,自身的管理机制、技术开发、品质体系、服务导向等已日趋成熟,在国内LED业界始终保持着领先地位。 北京百润慧通电子技术有限责任公司 销售部: 联系电话:010-52566097 52566451 24小时售前产品咨询热线:13911588988 技术部: 联系电话: 010-52566452 24小时售后产品技术支持:13911205351 生产工程部: 联系电话:010-52566453 24小时售后产品维修电话:13811164442 地址:北京市昌平区定福皇庄钢材木材市场7号院(102208) 电子邮件:panelway@126.com 网址:http://www.panelway.com | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
5381 | 2007-09-10 07:07:36 | 2007-09-10 07:12:57 | 2022-03-06 03:34:14.081299 | Unreviewed | closed | Uncategorized | dev | invalid | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 | LED显示屏、全彩色LED电子显示屏专业制造商 百润慧通 13911588988 北京百润慧通电子技术有限公司是集LED显示屏、LED外延应用产品科研开发、生产、销售、安装及培训服务于一体的高新科技产业公司。公司的产品已形成完整的系列,应用于室内、室外、半室外各种场所的单色显示屏、伪彩色显示屏、全彩色显示屏等达二十多个品种。产品应用范围涉及机场、火车站、汽车站、大型体育及会展场馆、智能交通、高速公路、银行、广告、电力、商业、电信、医院、税务、银行、交易市场、市民广场等几乎所有的相关系统及行业。公司建立了具有现代化管理、设备先进的显示屏生产加工基地。公司视产品品质为企业的生命,对每一项产品都进行严谨的工艺设计、严密生产监督和质量检测,从而确保了产品的高可靠性。 公司特别重视产品的售后服务,建立了完善的售后服务体系,向用户提供免费培训、定期巡检、反应迅捷、终身维护的服务承诺。本公司将秉承“执着进取、追求完美”的理念以孜孜不倦的勤奋精神向用户提供优质的服务。 公司产品全面贯彻信息产业部<<LED显示屏通用规范>>的要求,秉承“以质量、服务、诚信为发展根本”的企业精神,从产品开发、试制、生产、检测、安装、服务建立健全了完善的产品质量保证体系。公司与规模庞大的支持屏体生产的管芯厂、封装厂、LED数码管,发光管、点阵模块、电源、PCB、加工生产厂等数家专业配套厂有良好的商业合作关系,我们将共同完成LED产业纵向一体化宏伟目标。 我们相信:我们以优良的整体设计、完美的细节表现及完善的服务体系,终将成为您真诚永远的合作伙伴。 企业宗旨:发展光电科技 企业目标:打造知名品牌 企业精神:追求卓越品质 企业价值观:开拓创新,诚实守信,以客户为本 百润慧通具有从LED显示屏的开发、设计到制造、组装等一条龙生产设备。有国际先进水平的全自动贴片机、波峰焊、回流焊机、超声波清洗机;专用生产、调试车间和成套测试仪器等。经过多年的发展,自身的管理机制、技术开发、品质体系、服务导向等已日趋成熟,在国内LED业界始终保持着领先地位。 北京百润慧通电子技术有限责任公司 销售部: 联系电话:010-52566097 52566451 24小时售前产品咨询热线:13911588988 技术部: 联系电话: 010-52566452 24小时售后产品技术支持:13911205351 生产工程部: 联系电话:010-52566453 24小时售后产品维修电话:13811164442 地址:北京市昌平区定福皇庄钢材木材市场7号院(102208) 电子邮件:panelway@126.com 网址:http://www.panelway.com | nobody | anonymous | 0 | 0 | 0 | 0 | 0 | 0 | |||
5389 | 2007-09-10 16:35:22 | 2007-09-15 08:43:12 | 2022-03-06 03:34:15.561171 | Accepted | closed | Database layer (models, ORM) | dev | invalid | ImportError in daily_cleanup.py after [6087] changeset | '''Settings:''' {{{ INSTALLED_APPS = ( ... 'corpsite.feedagregator', ) }}} '''Traceback:''' {{{ Traceback (most recent call last): File "daily_cleanup.py", line 20, in ? clean_up() File "daily_cleanup.py", line 16, in clean_up Session.objects.filter(expire_date__lt=datetime.datetime.now()).delete() File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 342, in delete for object in del_query[0:GET_ITERATOR_CHUNK_SIZE]: File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 114, in __iter__ return iter(self._get_data()) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 482, in _get_data self._result_cache = list(self.iterator()) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 180, in iterator select, sql, params = self._get_sql_clause() File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 497, in _get_sql_clause joins2, where2, params2 = self._filters.get_sql(opts) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 719, in get_sql joins2, where2, params2 = val.get_sql(opts) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 770, in get_sql return parse_lookup(self.kwargs.items(), opts) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 922, in parse_lookup joins2, where2, params2 = lookup_inner(path, lookup_type, value, opts, opts.db_table, None) File "/usr/local/lib/python2.4/site-packages/django/db/models/query.py", line 987, in lookup_inner field = find_field(name, current_opts.get_all_related_many_to_many_objects(), True) File "/usr/local/lib/python2.4/site-packages/django/db/models/options.py", line 177, in get_all_related_many_to_many_objects for klass in get_models(): File "/usr/local/lib/python2.4/site-packages/django/db/models/loading.py", line 134, in get_models self._populate() … | adrian | Boo <boobsd@gmail.com> | 0 | 0 | 0 | 0 | 0 | 0 | |||
5382 | 2007-09-10 13:07:26 | 2007-09-10 14:39:21 | 2022-03-06 03:34:14.262130 | Unreviewed | closed | Generic views | dev | wontfix | create_update.delete_object always needs a confirmation page | I've found one thing annoying about delete_object() view. In my application I prefer to use HREFs (as opposed to forms) for object deletion, together with JavaScript-based confirmation dialogs. This makes delete_object() useless for me, as I want it to delete the object upon GET request, without aby further confirmation page. Could it be possible to add additional param like no_confirmation (with False as default for backward compatibility) ? Changing {{{ if request.method == 'POST': }}} to {{{ if no_confirmation or request.method == 'POST': }}} would do the trick then. | nobody | czajnik@czajsoft.pl | delete_object | 0 | 0 | 0 | 0 | 0 | 0 | ||
5396 | 2007-09-10 21:58:57 | 2007-09-14 06:15:06 | 2022-03-06 03:34:16.630618 | Design decision needed | closed | Template system | dev | wontfix | Filter "urlizetrunc" does not truncize email adresses | Filter shortens urls, but not email addresses. | nobody | Danilo | 0 | 1 | 0 | 1 | 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 );