Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
2013/3/27 Zope tests summarizer nore...@zope.org This is the summary for test reports received on the zope-tests list between 2013-03-25 00:00:00 UTC and 2013-03-26 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 # 214 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 # 214 https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html I can reproduce the problems. I do not understand at all, why buildout does not add persistent into the path for zope.traverser. Through dependency chains it depends on BTrees and BTrees depends on persistent, still, persistent is not in the paths for my script. Marius, can you show me your buildout script and your test script for zope traverser? Mine is: do3cc@BRICK cat bin/buildout | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /eggs/distribute-0.6.35-py2.7.egg', /eggs/zc.buildout-2.0.1-py2.7.egg', ] import zc.buildout.buildout if __name__ == '__main__': sys.exit(zc.buildout.buildout.main()) do3cc@BRICK cat bin/test-ztk-zope.traversing | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /zope.traversing/src', /zope.testrunner/src', /zope.interface/src', /zope.exceptions/src', /eggs/six-1.2.0-py2.7.egg', /eggs/distribute-0.6.35-py2.7.egg', /zope.testing/src', /zope.tales/src', /zope.security/src', /zope.configuration/src', /zope.component/src', /zope.browserresource/src', /zope.annotation/src', /zope.publisher/src', /zope.proxy/src', /zope.location/src', /zope.i18nmessageid/src', /zope.i18n/src', /src/transaction', /src/BTrees', /zope.schema/src', /zope.event/src', /zope.contenttype/src', /zope.browser/src', /eggs/pytz-2012j-py2.7.egg', ] import os sys.argv[0] = os.path.abspath(sys.argv[0]) /parts/test-ztk-zope.traversing') import zope.testrunner if __name__ == '__main__': sys.exit(zope.testrunner.run([ /zope.traversing/src', ])) I am using python 2.7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Wed, Mar 27, 2013 at 12:00:17PM +0100, Patrick Gerken wrote:
2013/3/27 Zope tests summarizer nore...@zope.org
[1]FAILED Still Failing - zopetoolkit_trunk - Build # 214
https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html
I can reproduce the problems.
Hehe, there's a U+200B ZERO WIDTH SPACE in front of that sentence.
I do not understand at all, why buildout does not add persistent into the
path for zope.traverser. Through dependency chains it depends on BTrees and
BTrees depends on persistent, still, persistent is not in the paths for my
script. Marius, can you show me your buildout script and your test script
for zope traverser? Mine is:
do3cc@BRICK cat bin/buildout | sed -e 's/\(
*\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/'
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/buildout | sed -e 's/\(
*\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/'
sed: -e expression #1, char 4: unterminated `s' command
I'm not sure what that sed expression was supposed to do, so there's the entire
thing:
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/buildout
#!/home/mg/src/zopetoolkit/python/bin/python
import sys
sys.path[0:0] = [
'/home/mg/.buildout/eggs/distribute-0.6.35-py2.7.egg',
'/home/mg/.buildout/eggs/zc.buildout-2.0.1-py2.7.egg',
]
import zc.buildout.buildout
if __name__ == '__main__':
sys.exit(zc.buildout.buildout.main())
/home/mg/src/zopetoolkit/python is a virtualenv for Python 2.7, to avoid
/usr/lib/python2.7/dist-packages/zope.interface (which is 3.6.1).
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/test-ztk-zope.traversing
#!/home/mg/src/zopetoolkit/python/bin/python
import sys
sys.path[0:0] = [
'/home/mg/.buildout/eggs/zope.traversing-4.0.0a2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.testrunner-4.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.interface-4.0.4-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.exceptions-4.0.6-py2.7.egg',
'/home/mg/.buildout/eggs/six-1.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/distribute-0.6.35-py2.7.egg',
'/home/mg/.buildout/eggs/zope.testing-4.1.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.tales-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.security-4.0.0b1-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.configuration-4.0.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.component-4.1.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.browserresource-4.0.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.annotation-4.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.publisher-4.0.0a2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.proxy-4.1.1-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.location-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.i18nmessageid-4.0.2-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.i18n-4.0.0a4-py2.7.egg',
'/home/mg/.buildout/eggs/transaction-1.4.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.schema-4.3.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.event-4.0.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.contenttype-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/BTrees-4.0.5-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.browser-2.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/pytz-2012j-py2.7.egg',
'/home/mg/.buildout/eggs/persistent-4.0.6-py2.7-linux-x86_64.egg',
]
import os
sys.argv[0] = os.path.abspath(sys.argv[0])
os.chdir('/home/mg/src/zopetoolkit/parts/test-ztk-zope.traversing')
import zope.testrunner
if __name__ == '__main__':
sys.exit(zope.testrunner.run([
'--test-path',
'/home/mg/.buildout/eggs/zope.traversing-4.0.0a2-py2.7.egg',
]))
What I did was
svn co svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk zopetoolkit
cd zopetoolkit
virtualenv -p python2.7 python
python/bin/python bootstrap.py
bin/buildout prefer-final=false
bin/test-ztk-zope.traversing
because I didn't realize I needed to use a different buildout config!
Trying now to
bin/buildout -c development-python2.cfg buildout:prefer-final=false
bin/test-ztk-zope.traversing
I can reproduce the problem, and my bin/test-ztk-zope.traversing does
*not* include persistent in sys.path.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Wed, Mar 27, 2013 at 09:53:56PM +0200, Marius Gedminas wrote: On Wed, Mar 27, 2013 at 12:00:17PM +0100, Patrick Gerken wrote: 2013/3/27 Zope tests summarizer nore...@zope.org [1]FAILED Still Failing - zopetoolkit_trunk - Build # 214 https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html ... svn co svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk zopetoolkit cd zopetoolkit virtualenv -p python2.7 python python/bin/python bootstrap.py bin/buildout -c development-python2.cfg buildout:prefer-final=false bin/test-ztk-zope.traversing I can reproduce the problem, and my bin/test-ztk-zope.traversing does *not* include persistent in sys.path. I think we've been bit by https://bugs.launchpad.net/zc.buildout/+bug/257555 $ ls -d src/*/*.egg src/BTrees/persistent-4.0.6-py2.7-linux-x86_64.egg src/BTrees/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/ZODB/persistent-4.0.6-py2.7-linux-x86_64.egg src/ZODB/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/zope.security/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/zope.security/zope.proxy-4.1.3-py2.7-linux-x86_64.egg $ grep setup_requires src/*/setup.py src/BTrees/setup.py: setup_requires=['persistent'], src/ZODB/setup.py: setup_requires=['persistent'], src/zope.security/setup.py:setup_requires = [] src/zope.security/setup.py:setup_requires = ['zope.proxy = 4.1.0'] src/zope.security/setup.py: setup_requires=setup_requires, Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-26 00:00:00 UTC and 2013-03-27 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 # 215 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 # 215 https://mail.zope.org/pipermail/zope-tests/2013-March/073564.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073563.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073562.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope] Product CalendarTag on zope2.13.19
Hello!
I'm running a zope2.13.19 instance on my mac. I intstalled the product Calendar
version 1.0.19
I adjusted the file __init__.py
Change the line:
from ImageFile import ImageFile
with:
from App.ImageFile import ImageFile
so far so good.
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file
/Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no
encoding declared;
Is pointing to lines containing non ASCII character such as this one:
'pl':
('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ')
What is the best way to take care of this issue?
Of course, the fastest is to get rid of some languages... not good.
It could be nice to release a complete working version of the product.
Please give me some hints.
Thank You,
Giampiero
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Product CalendarTag on zope2.13.19
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2013 11:44 AM, Giampiero Benvenuti wrote:
Hello!
I'm running a zope2.13.19 instance on my mac. I intstalled the product
Calendar version 1.0.19
I adjusted the file __init__.py
Change the line:
from ImageFile import ImageFile
with:
from App.ImageFile import ImageFile
so far so good.
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file
/Applications/zope21319/Products/Calendar/CalendarTag.py on line 139,
but no encoding declared;
Is pointing to lines containing non ASCII character such as this one:
'pl':
('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ')
What is the best way to take care of this issue? Of course, the
fastest is to get rid of some languages... not good.
It could be nice to release a complete working version of the
product.
Please give me some hints.
You could add the encoding at the top of the Python module. See PEP 263:
http://www.python.org/dev/peps/pep-0263/
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJMwACgkQ+gerLs4ltQ6sugCeNDKMadJOIa1IlmdoIvIImO+4
+FcAnAzX7dZrorjmoJCmSvBYV4U+a7mH
=hmSL
-END PGP SIGNATURE-
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Product CalendarTag on zope2.13.19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote: Still, one problem is this type of error: SyntaxError: Non-ASCII character '\xf1' in file /Applications/zope21319/Products/Calendar/CalendarTag.py on line 139, but no encoding declared; just place this line on top of the file: # -*- coding: utf-8 -*- with this, you declare the encoding of the file to be utf-8, which is probably the encoding you need. http://www.python.org/dev/peps/pep-0263/ what you describe sounds as if the Calendar product is not actively maintained. what usecase do you want to solve? where did you get the Calendar product from? best, johannes raggam - -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: off...@programmatic.pro web: http://programmatic.pro http://bluedynamics.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N MNIAn1corxQzogbnr5MHe38SlSSI2xCo =zNPb -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Product CalendarTag on zope2.13.19
Thanks so much for your tips!
I'm running out right now.
I'll be testing and reporting tomorrow.
Giampiero
On Mar 27, 2013, at 17:56 44, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/27/2013 11:44 AM, Giampiero Benvenuti wrote:
Hello!
I'm running a zope2.13.19 instance on my mac. I intstalled the product
Calendar version 1.0.19
I adjusted the file __init__.py
Change the line:
from ImageFile import ImageFile
with:
from App.ImageFile import ImageFile
so far so good.
Still, one problem is this type of error:
SyntaxError: Non-ASCII character '\xf1' in file
/Applications/zope21319/Products/Calendar/CalendarTag.py on line 139,
but no encoding declared;
Is pointing to lines containing non ASCII character such as this one:
'pl':
('StyczeÒ','Luty','Marzec','KwiecieÒ','Maj','Czerwiec','Lipiec','SierpieÒ','WrzesieÒ','Paºdziernik','Listopad','GrudzieÒ')
What is the best way to take care of this issue? Of course, the
fastest is to get rid of some languages... not good.
It could be nice to release a complete working version of the
product.
Please give me some hints.
You could add the encoding at the top of the Python module. See PEP 263:
http://www.python.org/dev/peps/pep-0263/
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFTJMwACgkQ+gerLs4ltQ6sugCeNDKMadJOIa1IlmdoIvIImO+4
+FcAnAzX7dZrorjmoJCmSvBYV4U+a7mH
=hmSL
-END PGP SIGNATURE-
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-CMF] cmf-tests -
This is the summary for test reports received on the cmf-tests list between 2013-03-26 00:00:00 UTC and 2013-03-27 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 Non-OK results -- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
