February 2013 - Zope-Dev

zope-tests - FAILED: 12, OK: 20
by Zope tests summarizer 25 Feb '13

25 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-23 00:00:00 UTC and 2013-02-24 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] Repository policy check found errors in 341 projects [2] Still Failing - zopetoolkit_trunk - Build # 183 [3] Still Failing - zopetoolkit_trunk_app - Build # 165 Total languishing bugs for zope2: 0 [4] Total languishing bugs for zope: 69 [5] Total languishing bugs for zopeapp: 1 [6] Total languishing bugs for zopetoolkit: 205 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.jsonrpc_py_265_32 [9] winbot / z3c.jsontree_py_265_32 [10] winbot / zope.app.authentication_py_265_32 [11] winbot / zope.app.pagetemplate_py_265_32 [12] winbot / zope.viewlet_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Repository policy check found errors in 341 projects https://mail.zope.org/pipermail/zope-tests/2013-February/072776.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 183 https://mail.zope.org/pipermail/zope-tests/2013-February/072774.html [3] FAILED Still Failing - zopetoolkit_trunk_app - Build # 165 https://mail.zope.org/pipermail/zope-tests/2013-February/072775.html [4] FAILED Total languishing bugs for zope: 69 https://mail.zope.org/pipermail/zope-tests/2013-February/072772.html [5] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2013-February/072770.html [6] FAILED Total languishing bugs for zopetoolkit: 205 https://mail.zope.org/pipermail/zope-tests/2013-February/072771.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072767.html [8] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072766.html [9] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072768.html [10] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072765.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072769.html [12] FAILED winbot / zope.viewlet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072796.html

2 1

zope-tests - FAILED: 19, OK: 17, UNKNOWN: 2
by Zope tests summarizer 24 Feb '13

24 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-22 00:00:00 UTC and 2013-02-23 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux [3] Still Failing - zopetoolkit_trunk - Build # 182 [4] Still Failing - zopetoolkit_trunk_app - Build # 164 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / z3c.authenticator_py_265_32 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.jsonrpc_py_265_32 [9] winbot / z3c.jsontree_py_265_32 [10] winbot / z3c.layer.ready2go_py_265_32 [11] winbot / z3c.tabular_py_265_32 [12] winbot / zc.sourcefactory_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.pagetemplate_py_265_32 [16] winbot / zope.app.wsgi_py_265_32 [17] winbot / zope.applicationcontrol_py_265_32 [18] winbot / zope.browserpage_py_265_32 [19] winbot / zope.contentprovider_py_265_32 [20] winbot / zope.login_py_265_32 [21] winbot / zope.pagetemplate_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072745.html [2] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072746.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 182 https://mail.zope.org/pipermail/zope-tests/2013-February/072738.html [4] FAILED Still Failing - zopetoolkit_trunk_app - Build # 164 https://mail.zope.org/pipermail/zope-tests/2013-February/072739.html [5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072762.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072760.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072731.html [8] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072732.html [9] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072737.html [10] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072764.html [11] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072759.html [12] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072736.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072727.html [14] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072729.html [15] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072735.html [16] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072761.html [17] FAILED winbot / zope.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072730.html [18] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072763.html [19] FAILED winbot / zope.contentprovider_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072733.html [20] FAILED winbot / zope.login_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072728.html [21] FAILED winbot / zope.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072734.html

2 1

zope-tests - FAILED: 14, OK: 17, UNKNOWN: 2
by Zope tests summarizer 23 Feb '13

23 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-21 00:00:00 UTC and 2013-02-22 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux [3] Still Failing - zopetoolkit_trunk - Build # 181 [4] Still Failing - zopetoolkit_trunk_app - Build # 163 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / z3c.authenticator_py_265_32 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.jsonrpc_py_265_32 [8] winbot / z3c.jsontree_py_265_32 [9] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.tabular_py_265_32 [11] winbot / zope.app.appsetup_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.generations_py_265_32 [14] winbot / zope.app.wsgi_py_265_32 [15] winbot / zope.browsermenu_py_265_32 [16] winbot / zope.browserpage_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072705.html [2] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072706.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 181 https://mail.zope.org/pipermail/zope-tests/2013-February/072698.html [4] FAILED Still Failing - zopetoolkit_trunk_app - Build # 163 https://mail.zope.org/pipermail/zope-tests/2013-February/072699.html [5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072722.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072720.html [7] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072696.html [8] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072697.html [9] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072726.html [10] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072719.html [11] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072723.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072694.html [13] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072695.html [14] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072724.html [15] FAILED winbot / zope.browsermenu_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072725.html [16] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072721.html

2 1

Current state of Python 3 migration
by Sebastien Douche 22 Feb '13

22 Feb '13

Hi all, Does anyone (Tres?) can list ZTK packages w/o Python 3 support? -- Sebastien Douche <sdouche(a)gmail.com> Twitter: @sdouche / G+: +sdouche

4 21

zope-tests - FAILED: 13, OK: 16, UNKNOWN: 2
by Zope tests summarizer 22 Feb '13

22 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-20 00:00:00 UTC and 2013-02-21 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux [3] Still Failing - zopetoolkit_trunk - Build # 180 [4] Still Failing - zopetoolkit_trunk_app - Build # 162 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / z3c.authenticator_py_265_32 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.layer.ready2go_py_265_32 [8] winbot / z3c.recipe.paster_py_265_32 [9] winbot / z3c.tabular_py_265_32 [10] winbot / zope.app.dependable_py_265_32 [11] winbot / zope.app.wsgi_py_265_32 [12] winbot / zope.contenttype_py_265_32 [13] winbot / zope.datetime_py_265_32 [14] winbot / zope.site_py_265_32 [15] winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072672.html [2] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072673.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 180 https://mail.zope.org/pipermail/zope-tests/2013-February/072665.html [4] FAILED Still Failing - zopetoolkit_trunk_app - Build # 162 https://mail.zope.org/pipermail/zope-tests/2013-February/072666.html [5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072689.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072687.html [7] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072693.html [8] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072688.html [9] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072686.html [10] FAILED winbot / zope.app.dependable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072691.html [11] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072692.html [12] FAILED winbot / zope.contenttype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072664.html [13] FAILED winbot / zope.datetime_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072690.html [14] FAILED winbot / zope.site_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072663.html [15] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072674.html

3 3

Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5
by Wichert Akkerman 21 Feb '13

21 Feb '13

On Feb 21, 2013, at 09:38 , Hans-Peter Locher <hans-peter.locher(a)inquant.de> wrote: > In a distributed application, > you cannot always ensure that you have each component > "under control". > The url is the most basic interface to a web application. > > In Plone the id (and therefore the url) is generated from user's title input. > For a title unicode is perfectly fine and needed (especially in unicode countries like germany). > > If Plone/Zope would generate utf-8 ids by default you'll get utf-8 urls from > the users generating the content immediately. > > This will lead to unpredictably errors (as most urls will still work as they don't contain utf-8 but some do) > in the distributed applications. What kind of errors are you thinking of? > Another issue might be that some developer tools might stop working / or only work in latest versions > > E.g. > > Python's urllib and xmlrpclib > Selenium IDE > windmill > jmeter > … All of these will still work fine. One thing to realise is that an UTF-8 URL itself is still an ASCII thing: it uses %-quoting for non-ASCII (and some other) characters. For example my local test site has a URL which looks like http://localhost:8080/Pløne/ in my browser but it really is http://localhost:8080/Pl%C3%B8ne/ . To get there Zope uses urllib.quote() internally, for example in the implementation of the absolute_url() method. > In my opinion having utf-8 urls should be possible in Zope/Plone. > But not by default. I have no problem with making that configurable. Wichert.

1 0

zope-tests - FAILED: 15, OK: 15, UNKNOWN: 4
by Zope tests summarizer 21 Feb '13

21 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-19 00:00:00 UTC and 2013-02-20 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] FAILED (failures=2) : Zope-2.13 Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-2.13 Python-2.7.3 : Linux [3] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [4] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux [5] Still Failing - zopetoolkit_trunk - Build # 179 [6] Still Failing - zopetoolkit_trunk_app - Build # 161 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.layer.ready2go_py_265_32 [9] winbot / z3c.recipe.paster_py_265_32 [10] winbot / z3c.tabular_py_265_32 [11] winbot / zope.copy_py_265_32 [12] winbot / zope.exceptions_py_265_32 [13] winbot / zope.hookable_py_265_32 [14] winbot / zope.i18n_py_265_32 [15] winbot / zope.lifecycleevent_py_265_32 [16] winbot / zope.location_py_265_32 [17] winbot / zope.proxy_py_265_32 [18] winbot / zope.testing_py_265_32 [19] winbot / zope.traversing_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN FAILED (failures=2) : Zope-2.13 Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072642.html [2] UNKNOWN FAILED (failures=2) : Zope-2.13 Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072643.html [3] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072644.html [4] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072645.html [5] FAILED Still Failing - zopetoolkit_trunk - Build # 179 https://mail.zope.org/pipermail/zope-tests/2013-February/072637.html [6] FAILED Still Failing - zopetoolkit_trunk_app - Build # 161 https://mail.zope.org/pipermail/zope-tests/2013-February/072638.html [7] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072659.html [8] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072661.html [9] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072660.html [10] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072658.html [11] FAILED winbot / zope.copy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072633.html [12] FAILED winbot / zope.exceptions_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072630.html [13] FAILED winbot / zope.hookable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072634.html [14] FAILED winbot / zope.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072629.html [15] FAILED winbot / zope.lifecycleevent_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072635.html [16] FAILED winbot / zope.location_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072631.html [17] FAILED winbot / zope.proxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072632.html [18] FAILED winbot / zope.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072636.html [19] FAILED winbot / zope.traversing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072662.html

2 2

Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5
by Wichert Akkerman 21 Feb '13

21 Feb '13

On Feb 21, 2013, at 09:26 , Christian Ledermann <christian.ledermann(a)gmail.com> wrote: > I agree with Hans Peter, > > > > On Thu, Feb 21, 2013 at 11:09 AM, Wichert Akkerman <wichert(a)wiggy.net> wrote: >> >> On Feb 21, 2013, at 09:08 , Hans-Peter Locher <hans-peter.locher(a)inquant.de> wrote: >> >>> In my opinion utf-8 urls are >>> >>> the same kind of evil as having >>> >>> tabs and whitespaces in filenames. > > have you ever tried to type german umlauts or russian characters on an > english keyboard? Yes, frequently. Wichert.

1 0

Relaxing Zope id rules for Zope 4 / Plone 5
by Wichert Akkerman 21 Feb '13

21 Feb '13

Currently Zope has two rules for object ids: 1) they must be str instances, and 2) they must only consist of alphanumerics and a few extra characters. I have been playing around recently with trying to relax those rules to allow more flexible object ids, specifically allowing UTF-8 object ids. That seems to be entirely doable, and I made a simple package which monkey-patches Zope to do this: https://github.com/wichert/experimental.utf8id . Since all current browsers will interpret URLs as UTF-8 strings this will create beautiful URLs and gets us out of the ASCII-jail. Based on the result so far I want to suggest that we officially allow more flexible object ids for Zope 4. Dieter Mauer tried something similar five (!!) years ago: https://github.com/zopefoundation/Zope/commit/40f1a4af3605204de7d803afe11f6… . His approach differs a bit from mine: I added checks to make sure ids are valid UTF-8 and still disallow some characters, while he allows everything except a slash (/). That has the advantage of easily supporting things like binary user ids (for example GUIDs from Active Directory users). I want to propose that we do the following: Allow arbitrary str object ids in Zope 4 based on Dieter's work. Configure standard name choosers, normalizers, etc. used to generate ids for content to create UTF-8 object ids. Wichert.

2 2

Re: [Zope-dev] [Plone-developers] Relaxing Zope id rules for Zope 4 / Plone 5
by Wichert Akkerman 21 Feb '13

21 Feb '13

On Feb 21, 2013, at 09:08 , Hans-Peter Locher <hans-peter.locher(a)inquant.de> wrote: > In my opinion utf-8 urls are > > the same kind of evil as having > > tabs and whitespaces in filenames. Can you explain your reasoning? Wichert.

1 0