[Zope-Checkins] SVN: Zope/branches/2.12/src/ explicit is better than implicit

2011-11-14 Thread Yvo Schubbe 
Log message for revision 123341:
  explicit is better than implicit

Changed:
  U   Zope/branches/2.12/src/OFS/Image.py
  U   Zope/branches/2.12/src/webdav/LockItem.py

-=-
Modified: Zope/branches/2.12/src/OFS/Image.py
===
--- Zope/branches/2.12/src/OFS/Image.py 2011-11-14 16:41:37 UTC (rev 123340)
+++ Zope/branches/2.12/src/OFS/Image.py 2011-11-14 16:42:11 UTC (rev 123341)
@@ -36,7 +36,6 @@
 from webdav.Lockable import ResourceLockedError
 from ZPublisher import HTTPRangeSupport
 from ZPublisher.HTTPRequest import FileUpload
-from ZPublisher.Iterators import filestream_iterator
 from zExceptions import Redirect
 from zope.contenttype import guess_content_type
 from zope.interface import implementedBy
@@ -657,6 +656,9 @@
 
 return ''
 
+InitializeClass(File)
+
+
 manage_addImageForm=DTMLFile('dtml/imageAdd',globals(),
  Kind='Image',kind='image')
 def manage_addImage(self, id, file, title='', precondition='', content_type='',
@@ -898,7 +900,9 @@
 
 return '%s /' % result
 
+InitializeClass(Image)
 
+
 def cookId(id, title, file):
 if not id and hasattr(file,'filename'):
 filename=file.filename

Modified: Zope/branches/2.12/src/webdav/LockItem.py
===
--- Zope/branches/2.12/src/webdav/LockItem.py   2011-11-14 16:41:37 UTC (rev 
123340)
+++ Zope/branches/2.12/src/webdav/LockItem.py   2011-11-14 16:42:11 UTC (rev 
123341)
@@ -19,6 +19,7 @@
 
 from AccessControl.Owned import ownerInfo
 from AccessControl.SecurityInfo import ClassSecurityInfo
+from App.class_init import InitializeClass
 from Persistence import Persistent
 from zope.interface import implements
 
@@ -173,7 +174,6 @@
 return s
 
 def asXML(self):
-
 s = ?xml version=1.0 encoding=utf-8 ?
 d:prop xmlns:d=DAV:
  d:lockdiscovery
@@ -181,3 +181,5 @@
  /d:lockdiscovery
 /d:prop % self.asLockDiscoveryProperty(ns=d)
 return s
+
+InitializeClass(LockItem)

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/src/ explicit is better than implicit

2011-11-14 Thread Yvo Schubbe 
Log message for revision 123343:
  explicit is better than implicit

Changed:
  U   Zope/trunk/src/OFS/Image.py
  U   Zope/trunk/src/webdav/LockItem.py

-=-
Modified: Zope/trunk/src/OFS/Image.py
===
--- Zope/trunk/src/OFS/Image.py 2011-11-14 16:42:24 UTC (rev 123342)
+++ Zope/trunk/src/OFS/Image.py 2011-11-14 16:42:41 UTC (rev 123343)
@@ -34,7 +34,6 @@
 from webdav.Lockable import ResourceLockedError
 from ZPublisher import HTTPRangeSupport
 from ZPublisher.HTTPRequest import FileUpload
-from ZPublisher.Iterators import filestream_iterator
 from zExceptions import Redirect
 from zope.contenttype import guess_content_type
 from zope.interface import implementedBy
@@ -651,6 +650,9 @@
 
 return ''
 
+InitializeClass(File)
+
+
 manage_addImageForm=DTMLFile('dtml/imageAdd',globals(),
  Kind='Image',kind='image')
 def manage_addImage(self, id, file, title='', precondition='', content_type='',
@@ -890,7 +892,9 @@
 
 return '%s /' % result
 
+InitializeClass(Image)
 
+
 def cookId(id, title, file):
 if not id and hasattr(file,'filename'):
 filename=file.filename

Modified: Zope/trunk/src/webdav/LockItem.py
===
--- Zope/trunk/src/webdav/LockItem.py   2011-11-14 16:42:24 UTC (rev 123342)
+++ Zope/trunk/src/webdav/LockItem.py   2011-11-14 16:42:41 UTC (rev 123343)
@@ -15,6 +15,7 @@
 
 import time
 
+from AccessControl.class_init import InitializeClass
 from AccessControl.owner import ownerInfo
 from AccessControl.SecurityInfo import ClassSecurityInfo
 from Persistence import Persistent
@@ -171,7 +172,6 @@
 return s
 
 def asXML(self):
-
 s = ?xml version=1.0 encoding=utf-8 ?
 d:prop xmlns:d=DAV:
  d:lockdiscovery
@@ -179,3 +179,5 @@
  /d:lockdiscovery
 /d:prop % self.asLockDiscoveryProperty(ns=d)
 return s
+
+InitializeClass(LockItem)

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins

Re: [Zope-dev] zope-tests - FAILED: 8, OK: 39

2011-11-14 Thread Brian Sutherland 
On Sun, Nov 13, 2011 at 08:22:38AM -0500, Tres Seaver wrote:
  [8]FAILED  winbot / z3c.form_py_265_32 
  https://mail.zope.org/pipermail/zope-tests/2011-November/052551.html
 
 Stephan said yesterday he thought this was a chameleon bug.  I just
 tried to reproduce this on a Linux box with a fresh checkout, using
 Python 2.5.5.  The tests don't even run for me::
 
  Traceback (most recent call last):
File /tmp/zft/bin/test, line 26, in module
  '--test-path', '/tmp/zft/src',
File 
  /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
   line 30, in run
  failed = run_internal(defaults, args, script_parts=script_parts)
File 
  /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
   line 41, in run_internal
  from zope.testrunner.runner import Runner
File 
  /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/runner.py, 
  line 46, in module
  import zope.testrunner.tb_format
File 
  /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/tb_format.py,
   line 19, in module
  import zope.exceptions.exceptionformatter
File 
  /tmp/zft/eggs/zope.exceptions-3.6.1-py2.5.egg/zope/exceptions/__init__.py,
   line 24, in module
  import zope.security
File 
  /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/__init__.py,
   line 17, in module
  from zope.security.management import checkPermission
File 
  /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/management.py,
   line 20, in module
  from zope.security import interfaces
File 
  /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/interfaces.py,
   line 19, in module
  from zope.schema import Text, TextLine
File /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/__init__.py, 
  line 16, in module
  from zope.schema._field import Field, Container, Iterable, Orderable
File /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/_field.py, 
  line 78
  class SourceText(Text):
  ^
  SyntaxError: invalid syntax

I managed to reproduce it with Python 2.6.

It turned out to be a bug I introduced with the zope.schema 4.0.0
Python 3 support. I've fixed it in 123340 and released as 4.0.1.

-- 
Brian Sutherland
___
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: 8, OK: 39

2011-11-14 Thread Christophe Combelles 
Le 14/11/2011 01:52, Christophe Combelles a écrit :
 Le 13/11/2011 14:22, Tres Seaver a écrit :
 [1]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-November/052554.html

 This is the same hour-long timeout as yesterday in the buildout step:

 mr.developer: Updated 'zope.viewlet' with subversion.

 command timed out: 3600 seconds without output, killing pid 22071
 process killed by signal 9 program finished with exit code -1
 elapsedTime=4054.018485

 I have no idea what is failing.


 [2]FAILED  Zope 3.4 KGS / Python2.4.6 64bit linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052563.html


 [3]FAILED  Zope 3.4 KGS / Python2.5.5 64bit linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052564.html


 [4]FAILED  Zope 3.4 Known Good Set / py2.4-32bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052550.html


 [5]FAILED  Zope 3.4 Known Good Set / py2.4-64bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052548.html


 [6]FAILED  Zope 3.4 Known Good Set / py2.5-32bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052559.html


 [7]FAILED  Zope 3.4 Known Good Set / py2.5-64bit-linux
 https://mail.zope.org/pipermail/zope-tests/2011-November/052552.html

 If somebody who cares about the KGS could look at these failures and
 figure out why knew versions are slipping into the mix, that would be
 great.  Otherwise, we should just quit testing it.

 The initial build process of the kgs has no versions pinned, so it was being
 built with some of the latests libs that fail under python2.4.  I have added
 versions in the toplevel buildout.cfg so that it shouldn't fail again.

 I don't know if someone is interested but we have enough minor versions 
 upgrade
 available to be able to release a maintenance versions of the KGS: 3.4.2

fixed

http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/441







 [8]FAILED  winbot / z3c.form_py_265_32
 https://mail.zope.org/pipermail/zope-tests/2011-November/052551.html

 Stephan said yesterday he thought this was a chameleon bug.  I just
 tried to reproduce this on a Linux box with a fresh checkout, using
 Python 2.5.5.  The tests don't even run for me::

 Traceback (most recent call last):
 File /tmp/zft/bin/test, line 26, inmodule
   '--test-path', '/tmp/zft/src',
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
  line 30, in run
   failed = run_internal(defaults, args, script_parts=script_parts)
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/__init__.py,
  line 41, in run_internal
   from zope.testrunner.runner import Runner
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/runner.py, 
 line 46, inmodule
   import zope.testrunner.tb_format
 File 
 /tmp/zft/eggs/zope.testrunner-4.0.4-py2.5.egg/zope/testrunner/tb_format.py,
  line 19, inmodule
   import zope.exceptions.exceptionformatter
 File 
 /tmp/zft/eggs/zope.exceptions-3.6.1-py2.5.egg/zope/exceptions/__init__.py,
  line 24, inmodule
   import zope.security
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/__init__.py,
  line 17, inmodule
   from zope.security.management import checkPermission
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/management.py,
  line 20, inmodule
   from zope.security import interfaces
 File 
 /tmp/zft/eggs/zope.security-3.8.3-py2.5-linux-i686.egg/zope/security/interfaces.py,
  line 19, inmodule
   from zope.schema import Text, TextLine
 File 
 /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/__init__.py, line 
 16, inmodule
   from zope.schema._field import Field, Container, Iterable, Orderable
 File /tmp/zft/eggs/zope.schema-4.0.0-py2.5.egg/zope/schema/_field.py, 
 line 78
   class SourceText(Text):
   ^
 SyntaxError: invalid syntax



 Tres.
 ___
 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 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: 8, OK: 39

2011-11-14 Thread Tres Seaver 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/14/2011 04:50 PM, Christophe Combelles wrote:
 Le 14/11/2011 01:52, Christophe Combelles a écrit :
 Le 13/11/2011 14:22, Tres Seaver a écrit :

 If somebody who cares about the KGS could look at these failures
 and figure out why knew versions are slipping into the mix, that
 would be great.  Otherwise, we should just quit testing it.
 
 The initial build process of the kgs has no versions pinned, so it
 was being built with some of the latests libs that fail under
 python2.4.  I have added versions in the toplevel buildout.cfg so
 that it shouldn't fail again.
 
 I don't know if someone is interested but we have enough minor
 versions upgrade available to be able to release a maintenance
 versions of the KGS: 3.4.2
 
 fixed
 
 http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/441

I
 
don't understand why r123334 was needed to fix the KGS buildout:  I
thought the KGS was pinned by virtue of using its 'versions.cfg' file:

 http://download.zope.org/zope3.4/3.4.1/versions.cfg

(Actually, I don't know what the intended relationship is between that
file and http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg ).

Actually, I thought we were supposed to have a PyPI-like index which
ensured that no unwanted versions would creep in, e.g.::

 http://download.zope.org/zope3.4/3.4.1/index/

Can somebody who remembers how that dance was supposed to work enlighten us?


Tres.
- -- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7BlRMACgkQ+gerLs4ltQ7YhwCg2g8n/s26u0z5FvkrgwtTV+z8
ExQAoLrqxIAdMhQ+G1skUR2o7qa6LoOA
=BrQZ
-END PGP 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: 1, OK: 45, UNKNOWN: 1

2011-11-14 Thread Zope tests summarizer 
This is the summary for test reports received on the 
zope-tests list between 2011-11-13 00:00:00 UTC and 2011-11-14 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


   Bluebream / Python2.5.5 64bit linux
   Bluebream / Python2.6.7 64bit linux
   Bluebream / Python2.7.2 64bit linux
[1]UNKNOWN : Zope-trunk Python-2.6.6 : Linux
   ZTK 1.0 / Python2.4.6 Linux 64bit
   ZTK 1.0 / Python2.5.5 Linux 64bit
   ZTK 1.0 / Python2.6.7 Linux 64bit
   ZTK 1.0dev / Python2.4.6 Linux 64bit
   ZTK 1.0dev / Python2.5.5 Linux 64bit
   ZTK 1.0dev / Python2.6.7 Linux 64bit
   ZTK 1.1 / Python2.5.5 Linux 64bit
   ZTK 1.1 / Python2.6.7 Linux 64bit
   ZTK 1.1 / Python2.7.2 Linux 64bit
   ZTK 1.1dev / Python2.5.5 Linux 64bit
   ZTK 1.1dev / Python2.6.7 Linux 64bit
   ZTK 1.1dev / Python2.7.2 Linux 64bit
   Zope 3.4 KGS / Python2.4.6 64bit linux
   Zope 3.4 KGS / Python2.5.5 64bit linux
   Zope 3.4 Known Good Set / py2.4-32bit-linux
   Zope 3.4 Known Good Set / py2.4-64bit-linux
   Zope 3.4 Known Good Set / py2.5-32bit-linux
   Zope 3.4 Known Good Set / py2.5-64bit-linux
   Zope-2.10 Python-2.4.6 : Linux
   Zope-2.11 Python-2.4.6 : Linux
   Zope-2.12 Python-2.6.6 : Linux
   Zope-2.12-alltests Python-2.6.6 : Linux
   Zope-2.13 Python-2.6.6 : Linux
   Zope-2.13-alltests Python-2.6.6 : Linux
   Zope-trunk-alltests Python-2.6.6 : Linux
   winbot / ZODB_dev py_254_win32
   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.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
   winbot / ztk_dev py_265_win32
   winbot / ztk_dev py_265_win64
   winbot / ztk_dev py_270_win32
   winbot / ztk_dev py_270_win64

Non-OK results
--

[1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux
   https://mail.zope.org/pipermail/zope-tests/2011-November/052670.html


[2]FAILED  winbot / z3c.form_py_265_32
   https://mail.zope.org/pipermail/zope-tests/2011-November/052649.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 )

Re: [Zope-dev] zope-tests - FAILED: 8, OK: 39

2011-11-14 Thread Christophe Combelles 
Le 14/11/2011 23:24, Tres Seaver a écrit :
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 11/14/2011 04:50 PM, Christophe Combelles wrote:
 Le 14/11/2011 01:52, Christophe Combelles a écrit :
 Le 13/11/2011 14:22, Tres Seaver a écrit :

 If somebody who cares about the KGS could look at these failures
 and figure out why knew versions are slipping into the mix, that
 would be great.  Otherwise, we should just quit testing it.

 The initial build process of the kgs has no versions pinned, so it
 was being built with some of the latests libs that fail under
 python2.4.  I have added versions in the toplevel buildout.cfg so
 that it shouldn't fail again.

 I don't know if someone is interested but we have enough minor
 versions upgrade available to be able to release a maintenance
 versions of the KGS: 3.4.2

 fixed

 http://buildbot.afpy.org/kgs3.4/builders/Python2.4.6%2064bit%20linux/builds/441

 I

 don't understand why r123334 was needed to fix the KGS buildout:  I
 thought the KGS was pinned by virtue of using its 'versions.cfg' file:

   http://download.zope.org/zope3.4/3.4.1/versions.cfg

The problem doesn't come from the KGS itself, but from the package that creates 
the KGS, I mean zope.release. (which itself depends on the logic of zope.kgs).
During the release process, zope.release generates a buildout that will be used 
to launch tests. So there are 2 buildouts : the one from zope.release itself, 
and the one generated by the generate-buildout command.



 (Actually, I don't know what the intended relationship is between that
 file and http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg ).

The versions.cfg is generated from the controlled-packages file, and contains 
only the latest versions.  controlled-packages was supposed to track all the 
compatible versions (even older ones) of the KGS.
But it happens to be mathematically wrong and impossible, because the 
cobinatory 
explosion of versions makes it unrealistic to handle all the combinations.



 Actually, I thought we were supposed to have a PyPI-like index which
 ensured that no unwanted versions would creep in, e.g.::

   http://download.zope.org/zope3.4/3.4.1/index/

 Can somebody who remembers how that dance was supposed to work enlighten us?


Everything is here
http://svn.zope.org/zope.release/branches/3.4/README.txt?rev=89181view=auto

This is much simpler with the ZTK now.



 Tres.
 - --
 ===
 Tres Seaver  +1 540-429-0999  tsea...@palladion.com
 Palladion Software   Excellence by Designhttp://palladion.com
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAk7BlRMACgkQ+gerLs4ltQ7YhwCg2g8n/s26u0z5FvkrgwtTV+z8
 ExQAoLrqxIAdMhQ+G1skUR2o7qa6LoOA
 =BrQZ
 -END PGP 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 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: 8, OK: 39

2011-11-14 Thread Michael Howitz 
Am 14.11.2011 um 23:24 schrieb Tres Seaver:
[...]
 I don't understand why r123334 was needed to fix the KGS buildout:  I
 thought the KGS was pinned by virtue of using its 'versions.cfg' file:
 
 http://download.zope.org/zope3.4/3.4.1/versions.cfg


I think it would be a good idea to extend this file in the zope.release 
buildout.cfg. (So we can get rid of the lately manually added version pins.)
Any objections?


Yours sincerely,
-- 
Michael Howitz · m...@gocept.com · software developer
gocept gmbh  co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany
http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1
Zope and Plone consulting and development

___
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: 1, OK: 45, UNKNOWN: 1

2011-11-14 Thread Brian Sutherland 
On Tue, Nov 15, 2011 at 01:00:03AM +, Zope tests summarizer wrote:
 Non-OK results
 --
 
 [1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052670.html

Looks like a network failure

 [2]FAILED  winbot / z3c.form_py_265_32
https://mail.zope.org/pipermail/zope-tests/2011-November/052649.html

Today's run of this buildbot is green.

-- 
Brian Sutherland
___
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] force the output encoding to utf-8 in page templates

2011-11-14 Thread Yuri 
Il 11/11/2011 13:40, mor...@nidelven-it.no ha scritto:
 On Fri, 11 Nov 2011 12:56:30 +0100, Yuriy...@alfa.it  wrote:
 Il 11/11/2011 12:43, Yuri ha scritto:
 Hi all!

   I've a Zope2 application with Postgresql. All is ok and utf-8 but
 page templates. This means that non utf-8 data is sent to the
 database, and the database complain with:

 *Error Type: DataError*
 *Error Value: invalid byte sequence for encoding UTF8: 0xe82527
 HINT: This error can also happen if the byte sequence does not match
 the encoding expected by the server, which is controlled by
 client_encoding.

 *This does not happen if I manually switch the browser encoding
 (Firefox -  View -  character encoding -  Unicode (UTF-8)) and submit
 a form.

 So my question is: how do I tell to page templates to output utf-8
 instead of iso8859-15? The output_encoding property does anything.

 Obviously, changing default-zpublisher-encoding to utf-8 works, but
 other legacy applications will have problems on characted encoding.

 Any idea?
 **

 I've solved in page templates code:

   if not response.headers.has_key('content-type'):
   response.setHeader('content-type', self.content_type +
 ';charset='  + self.output_encoding)- here add the utf-8, the
 publisher will find this filled and avoid to put the default.

 on line 315 of ZopePageTemplate.py

 Is there a better way? Thanks!
 Look for setting the default publisher encoding in the zope.conf
 filesystem file and restart.  :)

 -Morten

Even forcing utf-8 in the content-type header, I still have this error 
on some web browser. For example, mozilla firefox 3.6.18 on windows 
gives this error:

Error Type: DataError
Error Value: invalid byte sequence for encoding UTF8: 0xe82075 HINT: 
This error can also happen if the byte sequence does not match the 
encoding expected by the server, which is controlled by client_encoding.

It's sad there's no standard or no way to be compliant.
___
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] force the output encoding to utf-8 in page templates

2011-11-14 Thread Andreas Jung 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You should be able to set the encoding of the response by

tal:def define=dummy python:
request.RESPONSE.setHeader('content-type', 'text/html; charset=utf-8') /

within your page template.

- -aj

Yuri wrote:
 Hi all!
 
 I've a Zope2 application with Postgresql. All is ok and utf-8 but
 page templates. This means that non utf-8 data is sent to the
 database, and the database complain with:
 
 *Error Type: DataError* *Error Value: invalid byte sequence for
 encoding UTF8: 0xe82527 HINT: This error can also happen if the
 byte sequence does not match the encoding expected by the server,
 which is controlled by client_encoding.
 
 *This does not happen if I manually switch the browser encoding
 (Firefox - View - character encoding - Unicode (UTF-8)) and submit
 a form.
 
 So my question is: how do I tell to page templates to output utf-8 
 instead of iso8859-15? The output_encoding property does anything.
 
 Obviously, changing default-zpublisher-encoding to utf-8 works, but 
 other legacy applications will have problems on characted encoding.
 
 Any idea? ** ___ 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 )

- -- 
ZOPYX Limited   | zopyx group
Charlottenstr. 37/1 | The full-service network for Zope  Plone
D-72070 Tübingen| Produce  Publish
www.zopyx.com   | www.produce-and-publish.com
- 
E-Publishing, Python, Zope  Plone development, Consulting


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJOwhBcAAoJEADcfz7u4AZj5hkLvjkql56PD0CzUKp1JZkLta4n
WirPCXII9j8tFptsVrMs8OuRg60TUDwF7MCGptI/gf5MAxsHbCgKH0NDYr1PHLQx
5BWtGXsQ/5t6Lblu7xJywuOWuBan82k6i6LDmvrW5OyFupNpMduhaLPad1Uy5s3L
now6drULzDkML4hvBGbsw63Ufh/7IIa4S71lf6pxtcS/O0zEXUrEJ4BNf4hIezOW
Usl7v98ZK4GppN3/rJgP/NQLQ23elkxysLWpK4YmpByAQ/7Lx/rdkqpqMA6DwgCJ
qDQiWvij6yHQwHmTbHIXd/NkexH4SU5UviQZhWdSG8a+ZqygYEd/sGXbHUhtTMRc
V0bE2v6zDhY1jpvk1VFthug8IbmNmOYeRiVuhb4mMMlXOnQ3BEaIrxe8ultJHVKM
OAwhWI7XHX/wL/TTmoZc1v4jhEkcD6sLE6TlqXd5XsNf2D84IA4hOSnajnuWg8nQ
zmJTTn7CZNo+p+13moXKqXaWErXFT/A=
=1Maw
-END PGP SIGNATURE-
attachment: lists.vcf___
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 - OK: 4

2011-11-14 Thread CMF tests summarizer 
This is the summary for test reports received on the 
cmf-tests list between 2011-11-13 00:00:00 UTC and 2011-11-14 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


   CMF-2.2 Zope-2.12 Python-2.6.6 : Linux
   CMF-2.2 Zope-2.13 Python-2.6.6 : Linux
   CMF-trunk Zope-2.13 Python-2.6.6 : Linux
   CMF-trunk Zope-trunk Python-2.6.6 : Linux

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