- Zope-Dev - Zope lists

Success at porting ZTK to Python 3!
by Albertas Agejevas 08 Apr '13

08 Apr '13

Subject: Success at porting ZTK app to Python 3! Hi all, I'm glad to announce that we at CipherHealth have recently ported a full-fledged ZTK application to Python 3! What is cipher.uibuilder? ~~~~~~~~~~~~~~~~~~~~~~~~~ UI Builder is the infrastructural part of our major product. It is a library for building multi-tenant systems for business applications that involve import, processing and export of some data. UI Builder allows the admin to set up various user-facing views for the data, including tables, forms, charts, etc. Each tenant (site) has a separate configuration that is editable TTW and is stored using the ZODB and ConfigParser files on disk. The configuration files then can be loaded into a site. This allows us to version configurations and move them between environments. UI Builder also provides facilities for scheduled tasks and background execution of long-running jobs using celery. UI Builder uses z3c.form, z3c.table, as well as zope.publisher and friends. We have put together a simple demo application that exercises most UI Builder features. Status of the Python 3 port ~~~~~~~~~~~~~~~~~~~~~~~~~~~ We have the demo application successfully running on Python 3.3. In order to do that we have to rely on a number of alpha packages and several unreleased versions in py3 branches of dependencies. There still are several open issues, such as absence of xlwt-based Excel output and the issue of ZODB data backwards compatibility. In order to get zope.testbrowser-based tests to work on Python 3, we chose to migrate to WebTest as the back end instead of mechanize, as mechanize proved to be too hard to port to Python 3. The new version of zope.testbrowser is highly compatible with the previous one, verified on test suites of several major applications which used zope.testbrowser. Trying it out ~~~~~~~~~~~~~ If you're interested, you can check out the py3 branch of cipher.uibuilderdemo. Follow the instructions in the README.txt: https://github.com/CipherHealth/cipher.uibuilderdemo/tree/py3 Albertas

3 2

zope-tests - FAILED: 3, OK: 11
by Zope tests summarizer 08 Apr '13

08 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-06 00:00:00 UTC and 2013-04-07 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] Still Failing - zopetoolkit_trunk - Build # 226 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 226 https://mail.zope.org/pipermail/zope-tests/2013-April/073734.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073735.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073733.html

1 0

zope-tests - FAILED: 3, OK: 12
by Zope tests summarizer 07 Apr '13

07 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-05 00:00:00 UTC and 2013-04-06 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] Still Failing - zopetoolkit_trunk - Build # 225 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 225 https://mail.zope.org/pipermail/zope-tests/2013-April/073719.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073720.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073718.html

2 1

zope-tests - FAILED: 4, OK: 12
by Zope tests summarizer 06 Apr '13

06 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-04 00:00:00 UTC and 2013-04-05 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] Still Failing - zopetoolkit_trunk - Build # 224 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / ZODB_dev py_270_win64 [3] winbot / z3c.contents_py_265_32 [4] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 224 https://mail.zope.org/pipermail/zope-tests/2013-April/073704.html [2] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073702.html [3] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073705.html [4] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073703.html

1 0

zope-tests - FAILED: 6, OK: 8
by Zope tests summarizer 05 Apr '13

05 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-03 00:00:00 UTC and 2013-04-04 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] Still Failing - zopetoolkit_trunk - Build # 223 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 223 https://mail.zope.org/pipermail/zope-tests/2013-April/073689.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073699.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073700.html [4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073701.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073690.html [6] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073688.html

2 1

zope-tests - FAILED: 8, OK: 8
by Zope tests summarizer 04 Apr '13

04 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-02 00:00:00 UTC and 2013-04-03 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] Still Failing - zopetoolkit_trunk - Build # 222 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / ZODB_dev py_270_win64 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / zope.security_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 Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html [4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html [5] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073674.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073672.html [8] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html

3 2

zope-tests - FAILED: 8, OK: 8
by Zope tests summarizer 03 Apr '13

03 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-01 00:00:00 UTC and 2013-04-02 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] Still Failing - zopetoolkit_trunk - Build # 221 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / ZODB_dev py_270_win64 [6] winbot / ZODB_dev py_270_win64 [7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 221 https://mail.zope.org/pipermail/zope-tests/2013-April/073658.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073668.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073669.html [4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073670.html [5] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073671.html [6] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073656.html [7] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073659.html [8] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073657.html

1 0

zope.security and Python 3
by Albertas Agejevas 02 Apr '13

02 Apr '13

Hi, While porting one ZTK app to Python 3 I discovered the following problems with zope.security: 1) There was a package zope.app.security, which, along with zope.app baggage provided security declarations for BTrees and PersistentDict, PersistentList. They were in a separate file, _protections.zcml. What would be a good place for these from now on? zope.security? There is also a file globalmodules.zcml in zope.app.security, which declares public APIs of a lot of standard library modules. These declarations don't seem to enable open access on attributes of those classes, though. Is that a leftover of old untrusted TTW code attempts or does it do something useful? 2) PersistentDict on Py3 is based on collections.abc.Mapping, which uses classes such as collections.abc.View, KeysView, ValuesView for the results of the relevant methods. These classes currently have no security declarations. Perhaps all immutable/view classes in collections.abc should be added to the list of basic types in zope.security.checker? Or just declared together with persistent and BTrees classes? For Python 2 we can hedge out the declarations with zcml:condition="not-installed collections.abc". 3) BTrees have problems with security, too. Their items/keys/values methods return objects of classes like OOBTreeItems. On Python 2 zope.security used to pass them through, on Python 3 I'm getting ForbiddenAttribute errors. These classes don't seem importable, so it's not obvious how to declare their permissions. Thoughts? Advice? Albertas

1 0

zope-tests - FAILED: 6, OK: 8
by Zope tests summarizer 02 Apr '13

02 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-03-31 00:00:00 UTC and 2013-04-01 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] Still Failing - zopetoolkit_trunk - Build # 220 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 220 https://mail.zope.org/pipermail/zope-tests/2013-April/073643.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073653.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073654.html [4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073655.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073644.html [6] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073642.html

2 1

zope-tests - FAILED: 12, OK: 8
by Zope tests summarizer 01 Apr '13

01 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-03-30 00:00:00 UTC and 2013-03-31 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 499 projects [2] Still Failing - zopetoolkit_trunk - Build # 219 [3] Total languishing bugs for zope2: 1 [4] Total languishing bugs for zope: 69 [5] Total languishing bugs for zopeapp: 1 [6] Total languishing bugs for zopetoolkit: 195 [7] winbot / ZODB_dev py_265_win32 [8] winbot / ZODB_dev py_265_win64 [9] winbot / ZODB_dev py_270_win32 [10] winbot / ZODB_dev py_270_win64 [11] winbot / z3c.contents_py_265_32 [12] winbot / z3c.form_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 499 projects https://mail.zope.org/pipermail/zope-tests/2013-March/073629.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 219 https://mail.zope.org/pipermail/zope-tests/2013-March/073627.html [3] FAILED Total languishing bugs for zope2: 1 https://mail.zope.org/pipermail/zope-tests/2013-March/073623.html [4] FAILED Total languishing bugs for zope: 69 https://mail.zope.org/pipermail/zope-tests/2013-March/073625.html [5] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2013-March/073624.html [6] FAILED Total languishing bugs for zopetoolkit: 195 https://mail.zope.org/pipermail/zope-tests/2013-March/073626.html [7] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-March/073638.html [8] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-March/073639.html [9] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-March/073640.html [10] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-March/073641.html [11] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073628.html [12] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073622.html

1 0