April 2013 - Zope-Dev

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

13 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-11 00:00:00 UTC and 2013-04-12 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 # 231 [2] Still Failing - zopetoolkit_trunk - Build # 235 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 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 # 231 https://mail.zope.org/pipermail/zope-tests/2013-April/073814.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 235 https://mail.zope.org/pipermail/zope-tests/2013-April/073816.html [3] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073815.html [4] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073813.html

1 0

Biggest Fake Conference in Computer Science
by georgepeter＠hushmail.com 12 Apr '13

12 Apr '13

We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without any reviews) and we were invited to submit the final paper and a payment of $500+ fee to present the paper. We decided to use the fee for better purposes than making Prof. Hamid Arabnia (Chairman of WORLDCOMP) rich. After that, we received few reminders from WORLDCOMP to pay the fee but we never responded. We MUST say that you should look at the above website if you have any thoughts to submit a paper to WORLDCOMP. DBLP and other indexing agencies have stopped indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the conferences of WORLDCOMP and notice that there is no listing after 2010. See http://sites.google.com/site/dumpconf for comments from well-known researchers about WORLDCOMP. If WORLDCOMP is not fake then why did DBLP suddenly stopped listing the proceedings after? The status of your WORLDCOMP papers can be changed from “scientific” to “other” (i.e., junk or non-technical) at any time. See the comments http://www.mail-archive.com/tccc@lists.cs.columbia.edu/msg05168.html of a respected researcher on this. Better not to have a paper than having it in WORLDCOMP and spoil the resume and peace of mind forever! Our study revealed that WORLDCOMP is a money making business, using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing out a small chunk of that money (around 20 dollars per paper published in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) who publicizes WORLDCOMP and also defends it at various forums, using fake/anonymous names. The puppet uses fake names and defames other conferences to divert traffic to WORLDCOMP. He also makes anonymous phone calls and threatens the critiques of WORLDCOMP (see Item 7 in Section 5 of http://sites.google.com/site/dumpconf ).That is, the puppet does all his best to get a maximum number of papers published at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. Monte Carlo Resort (the venue of WORLDCOMP until 2012) has refused to provide the venue for WORLDCOMP’13 because of the fears of their image being tarnished due to WORLDCOMP’s fraudulent activities. WORLDCOMP’13 will be held at a different resort. WORLDCOMP will not be held after 2013. The paper submission deadline for WORLDCOMP’13 was March 18 and it was extended to April 6 and now it is extended to April 20 (it may be extended again) but still there are no committee members, no reviewers, and there is no conference Chairman. The only contact details available on WORLDCOMP’s website is just an email address! Prof. Hamid Arabnia expends the deadline to get more papers (means, more registration fee into his pocket!). Let us make a direct request to Prof. Hamid arabnia: publish all reviews for all the papers (after blocking identifiable details) since 2000 conference. Reveal the names and affiliations of all the reviewers (for each year) and how many papers each reviewer had reviewed on average. We also request him to look at the Open Challenge at https://sites.google.com/site/moneycomp1 Sorry for posting to multiple lists. Spreading the word is the only way to stop this bogus conference. Please forward this message to other mailing lists and people. We are shocked with Prof. Hamid Arabnia and his puppet’s activities http://worldcomp-fake-bogus.blogspot.com Search Google using the keyword worldcomp fake for additional links.

1 0

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

12 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-10 00:00:00 UTC and 2013-04-11 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] Failure - zopetoolkit_trunk - Build # 231 [2] Failure - zopetoolkit_trunk_app - Build # 169 [3] Still Failing - zopetoolkit_trunk - Build # 230 [4] Still Failing - zopetoolkit_trunk - Build # 232 [5] Still Failing - zopetoolkit_trunk - Build # 233 [6] Still Failing - zopetoolkit_trunk - Build # 234 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.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 Failure - zopetoolkit_trunk - Build # 231 https://mail.zope.org/pipermail/zope-tests/2013-April/073796.html [2] FAILED Failure - zopetoolkit_trunk_app - Build # 169 https://mail.zope.org/pipermail/zope-tests/2013-April/073800.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 230 https://mail.zope.org/pipermail/zope-tests/2013-April/073794.html [4] FAILED Still Failing - zopetoolkit_trunk - Build # 232 https://mail.zope.org/pipermail/zope-tests/2013-April/073797.html [5] FAILED Still Failing - zopetoolkit_trunk - Build # 233 https://mail.zope.org/pipermail/zope-tests/2013-April/073798.html [6] FAILED Still Failing - zopetoolkit_trunk - Build # 234 https://mail.zope.org/pipermail/zope-tests/2013-April/073799.html [7] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073795.html [8] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073793.html

2 1

five.grok -> svn
by Leonardo Rochael Almeida 12 Apr '13

12 Apr '13

Hi repository "specialists", Can anyone please migrate five.grok to GitHub? Some people have fixes for it, but don't want to touch SVN ever again, like its some sort of plague... Thanks in advance! Cheers, Leo

2 2

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

11 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-09 00:00:00 UTC and 2013-04-10 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 # 229 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 # 229 https://mail.zope.org/pipermail/zope-tests/2013-April/073779.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073780.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073778.html

1 0

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

10 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-08 00:00:00 UTC and 2013-04-09 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 # 228 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 # 228 https://mail.zope.org/pipermail/zope-tests/2013-April/073764.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073765.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073763.html

1 0

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

09 Apr '13

This is the summary for test reports received on the zope-tests list between 2013-04-07 00:00:00 UTC and 2013-04-08 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 # 227 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 / 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 # 227 https://mail.zope.org/pipermail/zope-tests/2013-April/073749.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073750.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073748.html

1 0

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