November 2013 - Zope-Dev

zope-tests - FAILED: 3, OK: 17
by Zope tests summarizer 06 Nov '13

06 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-11-04 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 449 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.recipe.paster_py_265_32 [2] winbot / z3c.recipe.paster_py_265_32 [3] winbot / zope.testrunner_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 winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079556.html [2] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079541.html [3] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079542.html

1 0

zope-tests - FAILED: 2, OK: 12
by Zope tests summarizer 05 Nov '13

05 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-10-31 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 445 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / zope.mimetype_py_265_32 [2] 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 winbot / zope.mimetype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079484.html [2] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-November/079486.html

3 3

zope-tests - FAILED: 2, OK: 9
by Zope tests summarizer 05 Nov '13

05 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-11-03 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 448 [1] winbot / z3c.recipe.paster_py_265_32 [2] winbot / zope.testrunner_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 winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079526.html [2] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079527.html

1 0

Review request: repozo --verify
by Marius Gedminas 04 Nov '13

04 Nov '13

https://github.com/zopefoundation/ZODB/pull/14 adds 'repozo --verify' that lets one compare file sizes and checksums against the manifest (the *.dat file). It has tests and everything. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development

2 1

zope-tests - FAILED: 2, OK: 13
by Zope tests summarizer 04 Nov '13

04 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-11-02 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 447 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.recipe.paster_py_265_32 [2] winbot / zope.testrunner_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 winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079511.html [2] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079512.html

2 1

unicode+make_query - New Pull request
by Michael McFadden 03 Nov '13

03 Nov '13

Tres: I hope I got everything you wanted. Thanks for taking the time to give feedback! I learned a lot doing this. https://github.com/zopefoundation/Zope/pull/5 In an effort to increase confidence that existing functionality is not affected, I did not modify any existing tests. I only created new tests. Notes: ----- I abandoned the idea to add the 'enc' parameter Since make_query takes **kwargs - which are designed to be 'key'='value' pairs, no matter what variable name I choose, I have a chance of breaking someone's install. I could break our install, for example, by picking kwargs['encoding'], because we use 'encoding' as a key in a query string. It becomes ambiguous if the argument 'encoding' is supposed to be used as a key in the query string or to control make_query() behavior. It's way to risky to implement this way. Thoughts? ----- I'm still thinking about the current 'make_query' in the field. If you provide Unicode types to make_query, and they are being successfully encoded with ASCII, all is well - but the output will change. Example: value=u'Hello' make_query(key=value) #returns 'key=Hello' New functionality would return: 'key:utf8:ustring=Hello' This might not be wanted. What do you think about preserving backward-compatibility with something like: if isInstance(value, unicode): try: string = str(value) except UnicodeDecodeError: string = value.encode(utf8) Which would preserve existing behavior. Thoughts? ----- I went slightly overboard and re-factored complex_marshal to use a recursive solution for nested structures. I didn't want to type check for unicode and v.decode() every time simple_marshal() was called. that's all it was. My OCD took over. It looks cleaner to my eyes! All existing tests pass, plus support for lists in lists, records in lists, lists in records, records in records. It might be a good idea to limit depth to, say, 3. Right now depth is limited to python recursion depth. Thoughts? -Flip

1 0

zope-tests - OK: 13
by Zope tests summarizer 03 Nov '13

03 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-11-01 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 446 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 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 0

zope-tests - OK: 9
by Zope tests summarizer 01 Nov '13

01 Nov '13

This is the summary for test reports received on the zope-tests list between 2013-10-30 00:00:00 UTC and 2013-10-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 ---------------- Successful - zopetoolkit_trunk - Build # 444 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 0