Re: [Zope-dev] Zope 4 roadmap

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2011 02:05 PM, Laurence Rowe wrote:
 On 17 November 2011 15:23, Martin Aspeli optilude+li...@gmail.com
 wrote:
 On 17 November 2011 14:46, Laurence Rowe l...@lrowe.co.uk wrote:

snip

 - Move authentication out to WSGI middleware.
 
 +1 - anything we can do to make AccessControl simpler and more 
 debuggable would be a big win.


Note that there is a counter-trend here among the Pyramid crew:  many
developers *want* tight integration of authentication, particularly the
login forms.


 Long term -
 
 - Move to WebOb as our request object. The wider Python web
 framework community seems to have settled on WebOb as their
 request object of choice, so to facilitate sharing of software
 components with other projects we should consider making WebOb our
 request object too (instead of just wrapping it). This will
 require buy-in from the wider ZTK community as the ZTK components
 will need
 
 +1


BBB concerns are likely going to keep us from replacing the request
entirely.  What really matters for re-use is that our requests provide
the same commonly-used subset of the WebOb request API.


 - Move to Python 3.
 
 +0
 
 I expect this will only become important several years down the line, 
 but the more we use other people's code who have already ported to 
 Python 3, the less code we will have to port ourselves.


FWIW, the port to Python3 of substantial existing web framework code is
already a dubious proposition:  nearly everybody doing it these days is
suffering pain (making their own code more complicated by straddling) in
order to gain hypothetical future benefits.

I would leave it off the roadmap completely until that landscape changes
substantially.



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/

iEYEARECAAYFAk7FZywACgkQ+gerLs4ltQ6IcwCgsJ6yQsbLOwOJ18JnV51nxqAg
hi4AoIFtnSJqWc5jCPrZdUEVQ1R9N6NO
=gaBY
-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 )

Re: [Zope-dev] Zope 4 release management

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/17/2011 03:14 PM, Laurence Rowe wrote:
 On 17 November 2011 19:45, Tres Seaver tsea...@palladion.com wrote:
 Again, this is a choice to be made by the foundation:  any polling
 will be done by the members of the foundation (this might be the
 biggest non-election item on the agenda for the next annual
 meeting).
 
 When is the next annual meeting?

Q1 2012 (date still to be set by the board).


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/

iEUEARECAAYFAk7FbKcACgkQ+gerLs4ltQ6hHgCYtQIoFi+NTdakkcjiBR4bsOfN
3wCcDerWtgsaNgB/XITcL63wTQYfZus=
=nyVH
-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 )

Re: [Zope-dev] Revert removal of ++skin++ in Zope4?

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/16/2011 07:28 AM, Lennart Regebro wrote:
 On Wed, Nov 16, 2011 at 12:53, Charlie Clark 
 charlie.cl...@clark-consulting.eu wrote:
 Am 16.11.2011, 12:49 Uhr, schrieb Lennart Regebro
 rege...@gmail.com:
 
 Right. Could we standardize on skins or browserlayers plz? Having
 both confuses the heck out of me.
 
 Definitely a topic that needs (re)-opening. From a CMF point of I
 think we're just about at the point where we could switch to browser
 layers, well, at least once CMF 2.3 has been released. But I think
 that CMF Skins still offer some functionality that you don't get
 with browser layers out of the box.
 
 When I said skins I meant ++skins++. CMF Skins must die.

Note that for all their warts, they are *massively* more successful than
the Z3 reimplementation, which was overengineered (I helped with that,
I'm sure).  In particular, the exceesive amount of ZCA majyk makes
complicaterd uses of the Z3 skins very fragile (easy to misconfigure,
hard to discover what you broke).


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/

iEYEARECAAYFAk7DtUkACgkQ+gerLs4ltQ6m1ACfefhRA+UQGJEuFs8DTl/ADj3b
IeUAoLcfBcOUTVAw9uLSYxRxdAMYV/An
=EJ4l
-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 )

Re: [Zope-dev] zope-tests - FAILED: 2, OK: 45

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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


This looks like maybe a transient network failure::

 While: Installing test. Getting distribution for
 'zope.app.pagetemplate==3.4.1'. Error: Couldn't find a distribution
 for 'zope.app.pagetemplate==3.4.1'.

AFIACT, http://pypi.python.org/pypi/zope.app.pagetemplate/3.4.1 is just fine.


 [2]FAILED  winbot / zope.app.publisher_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052705.html


And another::

 Download error: [Errno 10060] A connection attempt failed because the 
 connected party did not properly respond after a period of time, or 
 established connection failed because connected host has failed to
 respond -- Some packages may not be found! Couldn't find index page
 for 'zc.buildout' (maybe misspelled?)



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/

iEYEARECAAYFAk7DtmAACgkQ+gerLs4ltQ7iHACfcPihcr9YdL/vsro583ixqKfl
nh8AoNoqbb7k2Cm3tlm/EGvxDkt6QhyW
=oQuD
-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 )

Re: [Zope-dev] zope-tests - FAILED: 3, OK: 43

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  winbot / ZODB_dev py_270_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052734.html
 
 
 [2]FAILED  winbot / ZODB_dev py_270_win64 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052735.html


These two look like transient network failures during boostrapping.



 [3]FAILED  winbot / ztk_dev py_265_win64 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052766.html


This one too, only the boostrap failure was silent, so it blew up in the
buildout step.



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/

iEYEARECAAYFAk7EjUYACgkQ+gerLs4ltQ6f9gCg26uw9CfudCFOzmtO6w0fqVEb
9KsAoLwFL9UCvoOeE5nWTHG5oOCGvA0d
=j2Vw
-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 )

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

[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 )

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

[Tres Seaver]

 [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.



 [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



Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com

___
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

[Tres Seaver]

 [1]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052455.html

Looks like a transient network failure.


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

Why is the KGS pulling in new major versions?

 Getting distribution for 'zope.testing'.
 warning: no files found matching '*.test' under directory 'src'
 warning: no files found matching 'sampletests' under directory 'src'
 Got zope.testing 4.0.0.
 Getting distribution for 'zope.component==3.8.0'.
 Got zope.component 3.8.0.

(it then barfs on a Py-2.4-incompatible zope.schema).



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

Hmm, I don't get it:

 Getting distribution for 'zope.component==3.8.0'.
 Got zope.component 3.8.0.
 The version, 3.4.1, is not consistent with the requirement, 
 'zope.interface=3.6.0'.
 While:
   Installing test.
 Error: Bad version 3.4.1


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

More incompatible version stuff.


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

Like #2.


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

Like #3.


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

Like #2.


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

I can't parse the output from this one at all.



Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com

___
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: 9, OK: 39, UNKNOWN: 3

[Tres Seaver]

 [1]UNKNOWN UNKNOWN : ZTK 1.0 / Python2.4.6 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052491.html
 
 
 [2]UNKNOWN UNKNOWN : ZTK 1.0 / Python2.5.5 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052490.html
 
 
 [3]UNKNOWN UNKNOWN : ZTK 1.0 / Python2.6.7 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052492.html

These three all fail in the buildout step with no stdout, e.g.:

 buildout failed slave lost ( 33 mins, 5 secs )



 [4]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052507.html

Also a timeout, but this time with stdout.


 [5]FAILED  Zope 3.4 KGS / Python2.4.6 64bit linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052516.html
 
 
 [6]FAILED  Zope 3.4 KGS / Python2.5.5 64bit linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052517.html
 
 
 [7]FAILED  Zope 3.4 Known Good Set / py2.4-32bit-linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052502.html
 
 
 [8]FAILED  Zope 3.4 Known Good Set / py2.4-64bit-linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052500.html
 
 
 [9]FAILED  Zope 3.4 Known Good Set / py2.5-32bit-linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052506.html
 
 
 [10]   FAILED  Zope 3.4 Known Good Set / py2.5-64bit-linux
https://mail.zope.org/pipermail/zope-tests/2011-November/052504.html

These all look like newer versions getting installed (not the KGS ones)
and breaking builds (the same errors as yesterday).


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

Same inscrutable doctest failure as yesterday.


 [12]   FAILED  winbot / zope.app.basicskin_py_265_32
https://mail.zope.org/pipermail/zope-tests/2011-November/052505.html

Boostrap failure (looks like a timeout downloading zc.buildout).



Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com

___
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 - OK: 46

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

GOOOAL!


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/

iEYEARECAAYFAk68UlkACgkQ+gerLs4ltQ7jrACgoNV+YgxH2yQ2GpWgi+dXq1gh
t9cAoITswIK7FHXGNqjYAbsAytOx0GhH
=QyW+
-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 )

Re: [Zope-dev] zope-tests - FAILED: 3, OK: 45

[Tres Seaver]

 [1]FAILED  Total languishing bugs for zope2: 4
https://mail.zope.org/pipermail/zope-tests/2011-November/052262.html


Wow, only 4?


 [2]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
https://mail.zope.org/pipermail/zope-tests/2011-November/052267.html

Transient buildout failure:

 command timed out: 3600 seconds without output, killing pid 7166


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


Same as it ever was:  who was it again who feels responsible for
maintenance on z3c.form?



Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com

___
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: 45

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/07/2011 08:11 AM, Stephan Richter wrote:
 On Monday, November 07, 2011 07:32:04 AM Tres Seaver wrote:
 Same as it ever was:  who was it again who feels responsible 
 for maintenance on z3c.form?
 
 I am maintaining z3c.form, just not the Windows release, since 
 I have (a) no suitable setup and (b) really no interest to do 
 so.
 
 OK, cool.  The test failure here doesn't appear to be related to
  Windows (I think Hanno pinned lxml to work around earlier 
 failutres)
 
 http://winbot.zope.org/builders/z3c.form_py_265_32/builds/334/steps/test/log


 
s/stdio
 
 Fixed. It turned out that this test pointed out a bug in Chameleon 
 that has now been fixed. So all I needed to do is remove the test. 
 :-) Easy enough.
 
 I applied the fix to trunk, which is where this test was failing 
 from, right?

Correct.  Thanks very much -- I think tomorrow we should see a
completely green board for the first time in a long time.


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/

iEYEARECAAYFAk632YUACgkQ+gerLs4ltQ7EnQCggmPL/lTr/AKvZcL16Xv3Ca/N
NtgAn01QCkCI4L6/kGwC5BKQIgEhhBO7
=2Kwk
-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 )

Re: [Zope-dev] zope-tests - FAILED: 1, OK: 46

[Tres Seaver]

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


Ye!  That one is now green too!


Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com
___
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: 46

[Tres Seaver]

On 11/05/2011 09:00 PM, Zope tests summarizer wrote:

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



Same as yesterday (and the day before, and the day before, .)



 [2]FAILED  winbot / zope.app.debug_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052216.html






 
 
 [3]FAILED  winbot / zope.generations_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052217.html



This looks like transient network issues (or maybe a PyPI outage).



Tres.
-- 
===
Tres Seaver  +1 540-429-0999  tsea...@palladion.com
Palladion Software   Excellence by Designhttp://palladion.com

___
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: 46

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 Non-OK results --
 
 [1]FAILED  winbot / z3c.form_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052168.html

GOAL!
 
ZTK board grees, at last.


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/

iEYEARECAAYFAk61eAoACgkQ+gerLs4ltQ7YwQCfa7Zz9v0J13zZIbcTTuWrblsh
JI0AnjIX8nFz/+PHuUWFu7eRJTRw2kcJ
=5XmX
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052113.html

 
 
 [2]FAILED  ZTK 1.1 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052112.html

 
 
 [3]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052111.html

 
 
 [4]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052128.html

 
 
 [5]FAILED  ZTK 1.1dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052127.html

 
 
 [6]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052126.html


After
 
Michael Howitz's changes yesterday, these are now fixed:  they
won't show until tomorrow's report, but all six bots are green as of
right now.  YAY!


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

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


Same
 
expected traceback, got HTML error as yesterday.



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/

iEYEARECAAYFAk60N4MACgkQ+gerLs4ltQ5xxgCgnn8nKzsIWuUuzYRqm+jByfk1
tvsAmgMaX9vPuC15mrag6Xh4jPSIraNe
=36zN
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/03/2011 04:57 AM, Michael Howitz wrote:
 Am 03.11.2011 um 05:12 schrieb Tres Seaver: [...]
 [7]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052087.html

 
 - - [7] are all the unexpected Data.fs bug in 
 zope/testing/setupstack.txt.  Can somebody who cares about that
 module / feature figure out what is going on?
 
 
 I looked into this failure:
 
 - It only happens if the zope.testrunner tests are ran before
 zope.testing tests (on my laptop z3c.recipe.compattest sorts the
 tests differently by default.) Strangely I found no references of
 the string Data.fs in zope.testrunner maybe it changes the
 current working directory and another test puts the Data.fs there. 
 - zope/testing/setupstack.txt creates a file named Data.fs in a
 temporary directory, it asserts that is has been gone after stack
 tear down, but the assertion uses the wrong directory (cwd). - I
 fixed this test and released zope.testing 3.10.3. So this failure
 should be gone tomorrow.

Great, thank you very much!


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/

iEYEARECAAYFAk6zAbcACgkQ+gerLs4ltQ6owgCg11IcZr+DYyzqA/LQ2uAlquLj
Es4AoNsdcNqNzV2aSX+lNeW4yttir8jD
=xe4r
-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 )

Re: [Zope-dev] zope-tests - FAILED: 14, OK: 33

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  ZTK 1.0 / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052029.html

 
 
 [2]FAILED  ZTK 1.0 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052031.html

 
 
 [3]FAILED  ZTK 1.0 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052030.html


#1,
 
#2, and #3 need a side-port of the fix I checked in for
zope.testrunner:

http://svn.zope.org/zope.testrunner/trunk/?rev=123154view=rev



 [4]FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052044.html

 
 
 [5]FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052046.html

 
 
 [6]FAILED  ZTK 1.0dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052045.html


#4,
 
#5, and #6 need a backport of the following change to the
z.a.applicationcontrol 3.9 branch:

http://svn.zope.org/zope.app.applicationcontrol/trunk/?rev=123225view=rev


 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052042.html

 
 
 [8]FAILED  ZTK 1.1dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052041.html

 
 
 [9]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052040.html


#7,
 
#8, and #9 should clear up tommorow due to r123225 (they ran
yesterday before I checked in that fix).


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


Transient
 
network failure during a buildout (downloading a setuptools
nightly from PEAK).


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


The
 
same real failure as yesterday:  a doctest expected a traceback,
got a rendered page.


 [12]   FAILED  winbot / ztk_10 py_254_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052061.html


Transient
 
network failure (downloading ez_setup.py from PEAK).


 [13]   FAILED  winbot / ztk_dev py_270_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052059.html

 
 
 [14]   FAILED  winbot / ztk_dev py_270_win64 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052060.html


These
 
both seem to want 'buildout.exe' already installed:  do they
depend on having #12 not fail to install it?



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/

iEYEARECAAYFAk6xXAcACgkQ+gerLs4ltQ4XWACgwWkbcaL4Q/I0UHFzrbUXGxis
x4AAnRjdCPq4JVLuTPNvr91NEU6p1sCx
=j6w5
-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 )

Re: [Zope-dev] zope-tests - FAILED: 14, OK: 33

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/02/2011 11:04 AM, Tres Seaver wrote:

 #1, #2, and #3 need a side-port of the fix I checked in for 
 zope.testrunner:
 
 http://svn.zope.org/zope.testrunner/trunk/?rev=123154view=rev


I just side-ported r123154 to the zope.testing 3.9 branch:

 http://svn.zope.org/zope.testing/branches/3.9/?rev=123251view=rev

and made a release with that fix:

 http://pypi.python.org/pypi/zope.testing/3.9.7


 #4, #5, and #6 need a backport of the following change to the 
 z.a.applicationcontrol 3.9 branch:
 
 http://svn.zope.org/zope.app.applicationcontrol/trunk/?rev=123225view=rev


Actually,
 
I think they just needed a release with the fix:

 http://pypi.python.org/pypi/zope.app.applicationcontrol/3.5.10


I updated the ZTK 1.0 '*-versions.cfg' to include the new releases.



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/

iEYEARECAAYFAk6xZP0ACgkQ+gerLs4ltQ5BzACfcbEaALloizqljikA0yAV4U5g
XUkAn0kxgWoCJ8D2QJXJd4d5gM2zHalz
=CEn/
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


 [1]FAILED  ZTK 1.0 / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052076.html


This
 
issue should be fixed by yesterday's release of zope.testing 3.9.7.


 [2]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052075.html

 
 
 [3]FAILED  ZTK 1.1 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052074.html

 
 
 [4]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052073.html

 
 
 [5]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052088.html

 
 
 [6]FAILED  ZTK 1.1dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052089.html

 
 
 [7]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-November/052087.html


[2]
 
- - [7] are all the unexpected Data.fs bug in
zope/testing/setupstack.txt.  Can somebody who cares about that module
/ feature figure out what is going on?


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


Same
 
as yesterday (and the day before, and the day before).  Is nobody
maintaining this package?



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/

iEYEARECAAYFAk6yFKgACgkQ+gerLs4ltQ7NGQCgzwxcT6o5W5Bb2cl/dZDxGjU2
wiwAoMYZJenWEdn0aNdTUXwaZKZjgVAZ
=cpvb
-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 )

Re: [Zope-dev] zope-tests - FAILED: 13, OK: 40

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/31/2011 11:52 PM, Arfrever Frehtes Taifersar Arahesis wrote:

 Variables are checked in the following order: LC_ALL, LC_MESSAGES,
 LANG. I suggest to override LC_ALL in test suite.


Thanks for the pointer.  I was able to provoke the error by installing
the French locale data for subversion, and then setting LC_MESSAGES on
the command line:

 $ LC_MESSAGES=fr_FR.UTF-8 bin/test-zopeapp-zope.app.applicationcontrol


I have checked in a fix:

 http://svn.zope.org/zope.app.applicationcontrol/trunk/?rev=123225view=rev



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/

iEYEARECAAYFAk6v/KQACgkQ+gerLs4ltQ4KGgCeLmSFWMhedT5AlV8TTUBrvjv4
f9IAoNDwL5Paa2JCYfJxw+ALhZCWl/WW
=O3Yr
-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 )

Re: [Zope-dev] zope-tests - FAILED: 10, OK: 37

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051996.html


The
 
only failure here is in parsing the locale-influenced output from
'svn info':  I just checked in a fix which should make the test pass:

 http://svn.zope.org/zope.app.applicationcontrol/trunk/?rev=123225view=rev


 [2]FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051999.html


Same
 
as #1, but also has what looks to be a timing-related failure,
perhaps requiring a backport of r from zope.testrunner to the ZTK
1.0 equivalent branch of zope.testing:

- -- % 
 File
 /home/ccomb/ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/src/zope.testing/src/zope/testing/testrunner/testrunner-layers-buff.txt,
 line 70, in testrunner-layers-buff.txt Failed example: for line,
 time in record: if time-last_time = pause: # We paused! print
 'PAUSE FOUND BETWEEN THESE LINES:' print ''.join([last_line, line,
 '-'*70]) last_line, last_time = line, time # doctest: +ELLIPSIS 
 Expected: PAUSE FOUND BETWEEN THESE LINES:... Running: 
 test_something (sampletests_buffering.TestSomething2) 
 --

 
PAUSE FOUND BETWEEN THESE LINES:
 test_something (sampletests_buffering.TestSomething2) 
 test_something2 (sampletests_buffering.TestSomething2) 
 --

 
Got:
 PAUSE FOUND BETWEEN THESE LINES: BLANKLINE Running
 sampletests_buffering.Layer2
 tests:--

 
PAUSE FOUND BETWEEN THESE LINES:
 BLANKLINE Running in a subprocess. 
 --

 
PAUSE FOUND BETWEEN THESE LINES:
 Running: test_something (sampletests_buffering.TestSomething2) 
 --

 
PAUSE FOUND BETWEEN THESE LINES:
 test_something (sampletests_buffering.TestSomething2) 
 test_something2 (sampletests_buffering.TestSomething2) 
 --

 
PAUSE FOUND BETWEEN THESE LINES:
 Tear down sampletests_buffering.Layer2 ... not supported Total: 3
 tests, 0 failures, 0 errors in N.NNN
 seconds.--
- --
 
% 


 [3]FAILED  ZTK 1.0dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051998.html


Same
 
as #1.


 [4]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051980.html

 
 
 [5]FAILED  ZTK 1.1 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051979.html

 
 
 [6]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051978.html


These
 
three are all showing the unexpected Data.fs failure in the
zope.testing.setupstack test ('parts/zope.testing/working-directory').
 If that file is coming back, we need to figure out what is creating it.


 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051995.html

 
 
 [8]FAILED  ZTK 1.1dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051994.html

 
 
 [9]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051993.html


Same
 
as #1.


 [10]   FAILED  winbot / z3c.form_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051987.html


This
 
looks like a real failure in
'form-chameleon-issue-repeat-addons.txt':  it expects a traceback, but
gets a rendered HTML page.


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/

iEYEARECAAYFAk6wACoACgkQ+gerLs4ltQ7ErwCgn0Li3LDWqyRIIagJ5F6yE9za
/6MAoN00snerNERKe4aF1UciTvOvBnYO
=sRcV
-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 )

Re: [Zope-dev] zope-tests - FAILED: 10, OK: 37

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/31/2011 05:06 AM, Michael Howitz wrote:
 Am 29.10.2011 um 18:44 schrieb Tres Seaver:

 [10]   FAILED  winbot / zope.dublincore_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051843.html



 
This one is odd -- I wonder if we have a DST issue on the machine?
 
 It looks like a bug fixed in 3.8.2: Updated DATETIME regex 
 normalizer to guard against test failure when a datetime's
 microseconds value is zero.


Good diagnoisis.


 File 
 c:\eggs\zope.dublincore-3.7.0-py2.6.egg\zope\dublincore\tests\timeannotators.txt,

 
line 53, in timeannotators.txt Failed example: content.created
 Expected: datetime.datetime(DATETIME, tzinfo=UTC) Got: 
 datetime.datetime(2011, 10, 28, 2, 14, 8, tzinfo=UTC)
 
 
 The tested egg is rather old, the current version is 3.8.2. I
 updated buildout.cfg to use the checkout instead of the version
 pinned in ZTK.


Great, thanks!


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/

iEYEARECAAYFAk6usJIACgkQ+gerLs4ltQ5kJACfXHkdt7mixrLuYJH01ZRczwen
U0gAniF3XPvvOiCMRGjffShS2aJxcMaX
=l0oq
-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 )

Re: [Zope-dev] zope-tests - FAILED: 13, OK: 40

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/31/2011 04:43 AM, Wichert Akkerman wrote:
 On 10/31/2011 07:21 AM, Tres Seaver wrote:
 These are all failures in the following zopeapp test::
 
 -  zope/app/applicationcontrol/tests/test_zope_version.py
  def test_WrongLocale(self): Demonstrate bug
 177733 currentPath =
 os.path.dirname(os.path.abspath(__file__)) if isSVNAvailable()
 and isSVNCheckout(currentPath): zv = ZopeVersion(currentPath) 
 zv.getZopeVersion() # check that we don't get a
 'Development/Unknown' version 
 self.assert_(zv.result.startswith('Development/Revision: ')) -
 --


 
I have no theory for how that test could suddenly start failing (nor
 even what it is really supposed to test).  It doesn't fail on my 
 machine on any version of Python.
 
 Different version of subversion installed perhaps?


Hmmm, that would seem odd.  Christophe, has that machine recently
updated its subversion (between the test runs reported Saturday night
and those reported last night)?



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/

iEYEARECAAYFAk6usU8ACgkQ+gerLs4ltQ40qQCgn2nSoCZwQD4cmLqjT0Vn7qPr
+qQAoJwDGF7nazXcKvoCbKQmAlw37nLF
=Jlqy
-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 )

Re: [Zope-dev] zope-tests - FAILED: 13, OK: 40

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/31/2011 11:48 AM, Christophe Combelles wrote:
 Le 31/10/2011 15:31, Tres Seaver a écrit : On 10/31/2011 04:43 AM,
 Wichert Akkerman wrote:
 On 10/31/2011 07:21 AM, Tres Seaver wrote:
 These are all failures in the following zopeapp test::
 
 - 
 zope/app/applicationcontrol/tests/test_zope_version.py 
  def test_WrongLocale(self): Demonstrate bug 
 177733 currentPath = 
 os.path.dirname(os.path.abspath(__file__)) if
 isSVNAvailable() and isSVNCheckout(currentPath): zv =
 ZopeVersion(currentPath) zv.getZopeVersion() # check that
 we don't get a 'Development/Unknown' version 
 self.assert_(zv.result.startswith('Development/Revision:
 ')) - 
 --




 
I have no theory for how that test could suddenly start failing (nor
 even what it is really supposed to test).  It doesn't fail
 on my machine on any version of Python.
 
 Different version of subversion installed perhaps?
 
 
 Hmmm, that would seem odd.  Christophe, has that machine recently 
 updated its subversion (between the test runs reported Saturday
 night and those reported last night)?
 
 I've launched the test with a pdb in zopeversion.py, and it looks
 like a locale problem.
 
 (Pdb) !print self._getSVNInfoOutput().read() Chemin?\194?\160: 
 /home/ccomb/ztk1.1dev-slave/Python2.7.2-Linux-64bit/build/src/zope.app.applicationcontrol/src/zope/app/applicationcontrol/tests

 
URL?\194?\160:
 svn://svn.zope.org/repos/main/zope.app.applicationcontrol/trunk/src/zope/app/applicationcontrol/tests

 
Racine du d?\195?\169p?\195?\180t?\194?\160: svn://svn.zope.org/repos/main
 UUID du d?\195?\169p?\195?\180t?\194?\160:
 62d5b8a3-27da-0310-9561-8e5933582275 R?\195?\169vision?\194?\160:
 123191 Type de n?\197?\147ud?\194?\160: r?\195?\169pertoire 
 T?\195?\162che programm?\195?\169e?\194?\160: normale Auteur de
 la derni?\195?\168re modification?\194?\160: menesis 
 R?\195?\169vision de la derni?\195?\168re modification?\194?\160:
 121717 Date de la derni?\195?\168re modification: 2011-05-18
 21:23:30 +0200 (Wed 18 May 2011)
 
 Then :
 
 (Pdb) print info {'UUID du
 d?\\195?\\169p?\\195?\\180t?\\194?\\160': 
 '62d5b8a3-27da-0310-9561-8e5933582275', 'Date de la
 derni?\\195?\\168re modification': '2011-05-18 21:23:30 +0200
 (Wed 18 May 2011)', 'R?\\195?\\169vision de la
 derni?\\195?\\168re modification?\\194?\\160': '121717', 'Racine
 du d?\\195?\\169p?\\195?\\180t?\\194?\\160': 
 'svn://svn.zope.org/repos/main', 'Type de
 n?\\197?\\147ud?\\194?\\160': 'r?\\195?\\169pertoire',
 'T?\\195?\\162che programm?\\195?\\169e?\\194?\\160': 'normale',
 'Auteur de la derni?\\195?\\168re modification?\\194?\\160': 
 'menesis', 'URL?\\194?\\160': 
 'svn://svn.zope.org/repos/main/zope.app.applicationcontrol/trunk/src/zope/app/applicationcontrol/tests',
  'Chemin?\\194?\\160': 
 '/home/ccomb/ztk1.1dev-slave/Python2.7.2-Linux-64bit/build/src/zope.app.applicationcontrol/src/zope/app/applicationcontrol/tests',
  'R?\\195?\\169vision?\\194?\\160': '123191'}
 
 (Pdb) info.get(Revision, ) ''
 
 The key is not the same. It just means the method to read svn
 data is not robust.


Hmm, there is code in the test which tries to ensure that the locale
for the 'svn' process is set to 'C'::

 $ export ZSVN=svn+ssh://svn.zope.org/repos/main
 $ svn log -r85956 $ZSVN/zope.app.applicationcontrol/trunk
 r85956 | lgs | 2008-05-01 03:37:07 -0400 (Thu, 01 May 2008) | 1 line

 Add a test and a fix for bug 177733, that was causing ZopeVersion to
 report an unknown version when running on a machine with a locale
 different than english
 $ svn diff -c 85956 $ZSVN/zope.app.applicationcontrol/trunk
 ...(elide add of now-failing test)
 --- src/zope/app/applicationcontrol/zopeversion.py...85955)
 +++ src/zope/app/applicationcontrol/zopeversion.py...85956)
 @@ -63,7 +63,7 @@
  def _getSVNInfoOutput(self):
  try:
  proc = subprocess.Popen('svn info %s' % self.path,
 -shell=True, stdout=subprocess.PIPE)
 +shell=True, stdout=subprocess.PIPE, env={'LANG': 'C'})
  except OSError:
  pass
  else:

I guess it is not clever enough.  Nevertheless, that test was not
failing on any buildslave before yesterday's report.


 For the Data.fs problem, I had removed all the Data.fs* from all
 the builders, but they all came back again:
 
 ccomb@boa:~$ find . -name 'Data.fs*' 
 ./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.lock 
 ./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.tmp 
 ./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs.index 
 ./ztk1.1-slave/Python2.5.5-Linux-64bit/build/Data.fs 
 ./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.lock 
 ./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.tmp 
 ./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs.index 
 ./ztk1.1-slave/Python2.6.7-Linux-64bit/build/Data.fs 
 ./ztk1.1-slave/Python2.7.2-Linux-64bit/build/Data.fs.lock 
 ./ztk1.1

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 37

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/29/2011 08:13 PM, Christophe Combelles wrote:
 Le 28/10/2011 19:21, Tres Seaver a ?crit :
 The failures here look to be due to binary incompatbility (old
 Python was UCS4, new one is UCS2) in already-built eggs.
 Christophe, can you please remove any 'py2.6-linux-x86_64' eggs
 and let them get rebuilt?
 
 done
 
 So, except for the binary eggs built under the UCS4 Python 2.6.5
 not working with the new UCS2 Python 2.6.7, we have exactly the
 one failure left to deal with.  Looking more closely:  that
 failure occurs on the very last line of 'setupstack.txt', where
 the working directory has been restored:  thus, the issue is that
 there are 'Data.fs' files in the *main working trees* on the
 buildbot.afpy.org machine. Christophe, can you please find and
 remove such files?
 
 done too

Tr?s bien, merci beaucoup!


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/

iEYEARECAAYFAk6svOsACgkQ+gerLs4ltQ6hNwCgsZ7yHB6xsFKJ/EpYfxqEpRaV
5gwAoNwRVbFkmF61Pp5Dsm+nlW1MixzZ
=rCLD
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 37

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Bluebream / Python2.6.7 64bit linux 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051792.html


I'm
 
assuming thie is the same UCS4 / UCS2 iaaue as #2 and #3.


 [2]FAILED  ZTK 1.0 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051828.html


Same
 
as yesterday:

  The failures here look to be due to binary incompatbility (old Python
  was UCS4, new one is UCS2) in already-built eggs.  Christophe, can you
  please remove any 'py2.6-linux-x86_64' eggs and let them get rebuilt?


 [3]FAILED  ZTK 1.0dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051799.html


Ditto.



 
[4]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051830.html


This
 
is the unexpected Data.fs problem in zope/testing/setupstack.txt.


 [5]FAILED  ZTK 1.1 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051827.html


Same
 
as #2 / #3.


 [6]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051829.html


Same
 
as #4.


 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051798.html


Same
 
as #4.


 [8]FAILED  ZTK 1.1dev / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051790.html


Same
 
as #2 / #3.


 [9]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051797.html


Same
 
as #4.


So, except for the binary eggs built under the UCS4 Python 2.6.5 not
working with the new UCS2 Python 2.6.7, we have exactly the one
failure left to deal with.  Looking more closely:  that failure occurs
on the very last line of 'setupstack.txt', where the working directory
has been restored:  thus, the issue is that there are 'Data.fs' files
in the *main working trees* on the buildbot.afpy.org machine.
Christophe, can you please find and remove such files?


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/

iEYEARECAAYFAk6q5IAACgkQ+gerLs4ltQ5XkgCeIAPYR3AD6XgSSkyLrH2Gv70F
tCQAnRT6v63PKa8qqAqY7Xf9rzUw+QiI
=dbzU
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  ZTK 1.0 / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051738.html


This
 
one 404s for me.


 [2]FAILED  ZTK 1.0 / Python2.6.7 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051782.html


The
 
failures here look to be due to binary incompatbility (old Python
was UCS4, new one is UCS2) in already-built eggs.  Christophe, can you
remove any 'py2.6-linux-x86_64' eggs and let them get rebuilt?


 [3]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051784.html


This
 
is the unexpected Data.fs bug in zope/testing/setupstack.txt.
'svn log' suggests that Jim, Fred, and Lennart are best suited to
diagnose. ;)



 [4]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051736.html


Ditto.



 
[5]FAILED  ZTK 1.1 / Python2.6.5 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051735.html


404.



 
[6]FAILED  ZTK 1.1 / Python2.6.7 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051781.html


Same
 
as #2.


 [7]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051783.html


Same
 
as #3.


 [8]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051734.html


Same
 
as #3.


 [9]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051751.html


Same
 
as #3.


 [10]   FAILED  ZTK 1.1dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051749.html


404.



 
[11]   FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit
 https://mail.zope.org/pipermail/zope-tests/2011-October/051750.html


Same
 
as #3.


 [12]   FAILED  winbot / z3c.form_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051752.html


Same
 
failure as yesterday:  perhaps it ran before Hanno's pinning fix.



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/

iEYEARECAAYFAk6pimIACgkQ+gerLs4ltQ5eZgCg1ww3wG9CaYW8KQfkH7lZwjPp
fYoAoNIi7kL7eHwAzRyUcFbRngdgOeLQ
=BCRR
-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 )

Re: [Zope-dev] zope-tests - FAILED: 7, OK: 41

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/26/2011 06:54 AM, Christophe Combelles wrote:
 Le 26/10/2011 03:57, Tres Seaver a écrit :

 This run has the same two failures, plus the command-line error
 for the 'cProfile' option.  Christophe, can you please verify
 that the Python 2.6.5 used to run these tests was built from
 source, and has the 'cProfile.py' module?  I suspect we may be
 using a system Python on an OS which splits out the devtools
 into a separate OS-level distribution (e.g., 'python-dev' or some
 such).
 
 
 It's a system python 2.6.5 indeed, I'm replacing it with a new
 build of 2.6.7


Great!  that should leave use with only the unexpected
Data.fs-in-tempdir failure to diagnose.


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/

iEYEARECAAYFAk6oDf4ACgkQ+gerLs4ltQ4XEQCfU/AAQtbv2zdS7NTNrU+NSS7a
JxAAn2DDLzvH3gz8pvIsDsr9+/gqgCSG
=dz9V
-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 )

Re: [Zope-dev] [Zope] Hotfix for security vulnerability

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/25/2011 07:44 AM, yuppie wrote:
 Laurence Rowe wrote:
 This hotfix addresses a serious vulnerability in the Zope2 
 application server.  Affected versions of Zope2 include:
 
 - - 2.12.x= 2.12.20
 
 - - 2.13.x= 2.13.6
 
 Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.
 
 Can you confirm whether or not Zope 2.13.6 through 2.13.10 are 
 affected?
 
 They are affected. 2.13.6 seems to be a typo. But AFAICT Plone
 is not affected because it doesn't use the default user folder 
 implementation shipped with Zope.

Yuppie is correct on both points.


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/

iEYEARECAAYFAk6mwGIACgkQ+gerLs4ltQ48MwCaA5LjyoIIPIZOGdliV5c8kKs+
teEAoMqrJtdYCOfPjt8UK3Ehq8nh7Jb7
=gk5u
-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 )

Re: [Zope-dev] [Zope] Hotfix for security vulnerability

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/25/2011 07:28 AM, Laurence Rowe wrote:
 On 24 October 2011 22:54, Tres Seaver tsea...@palladion.com
 wrote:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 On behalf of the Zope security response team, I would like to
 announce the availability of a hotfix for a vulnerability
 inadvertently published earlier today.
 
 'Products.Zope_Hotfix_20111024' README 
 ==
 
 Overview - 
 
 This hotfix addresses a serious vulnerability in the Zope2 
 application server.  Affected versions of Zope2 include:
 
 - - 2.12.x = 2.12.20
 
 - - 2.13.x = 2.13.6
 
 Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.
 
 Can you confirm whether or not Zope 2.13.6 through 2.13.10 are
 affected?

Yes, I typoed the version.  All existing 2.13 releases are affected.


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/

iEYEARECAAYFAk6m2ogACgkQ+gerLs4ltQ65HQCeJsiLA5MiGmjI94O46BL8WCgU
cFIAoJDe7lrp/f12Nauk7SRJ2XFqGQCK
=DndQ
-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 )

Re: [Zope-dev] zope-tests - FAILED: 7, OK: 41

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Woohoo -- down to just seven!


 [1]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051688.html

This
 
has the sub-process buffer failure for which I checked in a fix
today from Jonathan Ballet:  I'm hopeful that it clears up tomorrow.

This run also has the unexpected Data.fs in a tempdir failure.


 [2]FAILED  ZTK 1.1 / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051687.html

This
 
run has the same two failures, plus the command-line error for
the 'cProfile' option.  Christophe, can you please verify that the
Python 2.6.5 used to run these tests was built from source, and has
the 'cProfile.py' module?  I suspect we may be using a system Python
on an OS which splits out the devtools into a separate OS-level
distribution (e.g., 'python-dev' or some such).


 [3]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051686.html

This
 
run has only the unexpected Data.fs failure.


 [4]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051703.html

Same
 
failures as #1.


 [5]FAILED  ZTK 1.1dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051701.html

Same
 
failures as #2.


 [6]FAILED  winbot / z3c.form_py_265_32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051704.html

I'm
 
ignoring this one, except to note that it is *not* lxml related.


 [7]FAILED  winbot / ztk_dev py_254_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051719.html

This
 
build should be disabled:  the ZTK trunk is no longer compatible
with Python 2.5.


So, in summary, we can get back to a green board if we can figure
out the three distinct errors here:

- - A 'Data.fs' present in what is supposed to be a newly-created tempdir,
  in zope.testrunner/src/zope/testrunner/testrunner-subunit.txt.

- - The subprocess buffer failure I hope I fixed today.

- - THe 'cProfile' issue, only on ccomb's Python 2.6.5.




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/

iEYEARECAAYFAk6naScACgkQ+gerLs4ltQ51EwCeIpofX9MxjDUJhzNTWg4YGA4l
WCQAoJabPy9M7l4TQOL14mE35Oj1HI3C
=c3wo
-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 )

Re: [Zope] Hotfix for security vulnerability

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/25/2011 06:52 AM, Encolpe Degoute wrote:
 Hello,
 
 Both of these url are not available: - 
 http://download.zope.org/Zope2/index/2.12.21/versions.cfg - 
 http://download.zope.org/Zope2/index/2.13.11/versions.cfg

The hotfix announcement says, as soon as they become available.  Those
releases have not yet been made.


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/

iEYEARECAAYFAk6mxVMACgkQ+gerLs4ltQ75+ACg0awuEwyyiq3M8qx96jKPTFcO
j/sAoJVbpnQwJtmNBiH1RU5PX7Z8wwry
=OanC
-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-Checkins] SVN: Zope/hotfixes/Products.Zope_Hotfix_20111024/ Hotfix for vulnerability reported today.

[Tres Seaver]

Log message for revision 123147:
  Hotfix for vulnerability reported today.

Changed:
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/tags/
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/

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

[Zope-Checkins] SVN: Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/ Add hotfix for vulnerability reported today.

[Tres Seaver]

Log message for revision 123148:
  Add hotfix for vulnerability reported today.

Changed:
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/CHANGES.txt
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/
  A   
Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/Zope_Hotfix_20111024/
  A   
Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/Zope_Hotfix_20111024/__init__.py
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/__init__.py
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/README.txt
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/setup.py

-=-
Added: Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/CHANGES.txt
===
--- Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/CHANGES.txt   
(rev 0)
+++ Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/CHANGES.txt   
2011-10-24 21:46:18 UTC (rev 123148)
@@ -0,0 +1,8 @@
+'Products.Zope_Hotfix_20111024' Changelog
+=
+
+
+1.0 (2011-10-24)
+
+
+- Initial release.

Added: 
Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/Zope_Hotfix_20111024/__init__.py
===
--- 
Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/Zope_Hotfix_20111024/__init__.py
 (rev 0)
+++ 
Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/Zope_Hotfix_20111024/__init__.py
 2011-10-24 21:46:18 UTC (rev 123148)
@@ -0,0 +1,4 @@
+def initialize(context):
+from AccessControl.User import BasicUserFolder
+from App.class_init import InitializeClass
+InitializeClass(BasicUserFolder)

Added: Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/__init__.py
===
--- Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/__init__.py  
(rev 0)
+++ Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/Products/__init__.py  
2011-10-24 21:46:18 UTC (rev 123148)
@@ -0,0 +1,6 @@
+# See http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages
+try:
+__import__('pkg_resources').declare_namespace(__name__)
+except ImportError:
+from pkgutil import extend_path
+__path__ = extend_path(__path__, __name__)

Added: Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/README.txt
===
--- Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/README.txt
(rev 0)
+++ Zope/hotfixes/Products.Zope_Hotfix_20111024/trunk/README.txt
2011-10-24 21:46:18 UTC (rev 123148)
@@ -0,0 +1,78 @@
+'Products.Zope_Hotfix_20111024' README
+==
+
+Overview
+
+
+This hotfix addresses a serious vulnerability in the Zope2 application
+server.  Affected versions of Zope2 include:
+
+- 2.12.x = 2.12.20
+
+- 2.13.x = 2.13.6
+
+Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.
+
+The Zope2 security response team recommends that all users of these 
+releases upgrade to an unaffected release (2.12.21 or 2.13.11) as soon as
+they become available.
+
+Until that upgrade is feasible, deploying this hotfix also mitigates the
+vulnerability.
+
+
+Installing the Hotfix:  Via 'easy_install'
+---
+
+If the Python which runs your Zope instance has 'setuptools' installed (or
+is a 'virtualenv'), you can install the hotfix directly from PyPI::
+
+  $ /prefix/bin/easy_install Products.Zope_Hotfix_20111024
+
+and then restart the Zope instance, e.g.:
+
+  $ /path/to/instance/bin/zopectl restart
+
+
+Installing the Hotfix:  Via 'zc.buildout'
+-
+
+If your Zope instance is managed via 'zc.buildout', you can install
+the hotfix directly from PyPI.  Edit the 'buildout.cfg' file, adding
+Products.Zope_Hotfix_20111024 to the eggs section of the instance.
+E.g.::
+
+  [instance]
+  recipe = plone.recipe.zope2instance
+  #...
+  eggs =
+${buildout:eggs}
+Products.Zope_Hotfix_20111024
+
+Next, re-run the buildout::
+
+  $ /path/to/buildout/bin/buildout
+
+and then restart the Zope instance, e.g.:
+
+  $ /path/to/buildout/bin/instance restart
+
+
+Installing the Hotfix:  Manual Installation
+---
+
+You may also install this hotfix by unpacking the tarball and adding a
+'products' key to the 'etc/zope.conf' of your instance.   E.g.::
+
+  products /path/to/Products.Zope_Hotfix_20111024/Products
+
+
+Verifying the Installation
+--
+
+After restarting the Zope instance, check the 'Control_Panel/Products'
+folder in the Zope Management Interface, e.g.:
+
+  http://localhost:8080/Control_Panel/Products/manage_main
+
+You should see the 'Zope_Hotfix_20111024' product folder there.

Added: 

[Zope-Checkins] SVN: Zope/hotfixes/Products.Zope_Hotfix_20111024/tags/1.0/ Tag hotfix for vulnerability reported today.

[Tres Seaver]

Log message for revision 123149:
  Tag hotfix for vulnerability reported today.

Changed:
  A   Zope/hotfixes/Products.Zope_Hotfix_20111024/tags/1.0/

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

[Zope-Checkins] SVN: Zope/branches/2.12/ Fix serious authentication vulnerability in stock configuration.

[Tres Seaver]

Log message for revision 123150:
  Fix serious authentication vulnerability in stock configuration.
  

Changed:
  U   Zope/branches/2.12/doc/CHANGES.rst
  U   Zope/branches/2.12/src/AccessControl/User.py

-=-
Modified: Zope/branches/2.12/doc/CHANGES.rst
===
--- Zope/branches/2.12/doc/CHANGES.rst  2011-10-24 21:47:09 UTC (rev 123149)
+++ Zope/branches/2.12/doc/CHANGES.rst  2011-10-24 22:23:09 UTC (rev 123150)
@@ -8,6 +8,7 @@
 2.12.21 (unreleased)
 
 
+- Fixed serious authentication vulnerability in stock configuration.
 
 2.12.20 (2011-10-04)
 

Modified: Zope/branches/2.12/src/AccessControl/User.py
===
--- Zope/branches/2.12/src/AccessControl/User.py2011-10-24 21:47:09 UTC 
(rev 123149)
+++ Zope/branches/2.12/src/AccessControl/User.py2011-10-24 22:23:09 UTC 
(rev 123150)
@@ -1027,7 +1027,9 @@
  returns true if domain auth mode is set to true
 return getattr(self, '_domain_auth_mode', None)
 
+InitializeClass(BasicUserFolder)
 
+
 class UserFolder(BasicUserFolder):
 
 Standard UserFolder object

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

[Zope-Checkins] SVN: Zope/branches/2.12/src/AccessControl/tests/testUser.py Add a unittest for today's fix.

[Tres Seaver]

Log message for revision 123151:
  Add a unittest for today's fix.

Changed:
  U   Zope/branches/2.12/src/AccessControl/tests/testUser.py

-=-
Modified: Zope/branches/2.12/src/AccessControl/tests/testUser.py
===
--- Zope/branches/2.12/src/AccessControl/tests/testUser.py  2011-10-24 
22:23:09 UTC (rev 123150)
+++ Zope/branches/2.12/src/AccessControl/tests/testUser.py  2011-10-24 
22:29:40 UTC (rev 123151)
@@ -227,7 +227,15 @@
 # TODO class Test_readUserAccessFile(unittest.TestCase)
 
 
-# TODO class BasicUserFoldertests(unittest.TestCase)
+class BasicUserFolderTests(unittest.TestCase):
+ 
+def _getTargetClass(self):
+from AccessControl.User import BasicUserFolder
+return BasicUserFolder
+ 
+def test_manage_users_security_initialized(self):
+uf = self._getTargetClass()()
+self.assertTrue(hasattr(uf, 'manage_users__roles__'))
 
 
 class UserFolderTests(unittest.TestCase):
@@ -494,11 +502,12 @@
 
 
 def test_suite():
-suite = unittest.TestSuite()
-suite.addTest(unittest.makeSuite(BasicUserTests))
-suite.addTest(unittest.makeSuite(SimpleUserTests))
-suite.addTest(unittest.makeSuite(SpecialUserTests))
-suite.addTest(unittest.makeSuite(UnrestrictedUserTests))
-suite.addTest(unittest.makeSuite(NullUnrestrictedUserTests))
-suite.addTest(unittest.makeSuite(UserFolderTests))
-return suite
+return unittest.TestSuite((
+unittest.makeSuite(BasicUserTests),
+unittest.makeSuite(SimpleUserTests),
+unittest.makeSuite(SpecialUserTests),
+unittest.makeSuite(UnrestrictedUserTests),
+unittest.makeSuite(NullUnrestrictedUserTests),
+unittest.makeSuite(BasicUserFolderTests),
+unittest.makeSuite(UserFolderTests),
+))

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

[Zope-Checkins] SVN: Zope/branches/2.13/ Fix serious authentication vulnerability in stock configuration.

[Tres Seaver]

Log message for revision 123152:
  Fix serious authentication vulnerability in stock configuration.
  

Changed:
  U   Zope/branches/2.13/doc/CHANGES.rst
  U   Zope/branches/2.13/src/OFS/tests/test_userfolder.py
  U   Zope/branches/2.13/src/OFS/userfolder.py

-=-
Modified: Zope/branches/2.13/doc/CHANGES.rst
===
--- Zope/branches/2.13/doc/CHANGES.rst  2011-10-24 22:29:40 UTC (rev 123151)
+++ Zope/branches/2.13/doc/CHANGES.rst  2011-10-24 22:39:13 UTC (rev 123152)
@@ -8,6 +8,7 @@
 2.13.11 (unreleased)
 
 
+- Fixed serious authentication vulnerability in stock configuration.
 
 2.13.10 (2011-10-04)
 

Modified: Zope/branches/2.13/src/OFS/tests/test_userfolder.py
===
--- Zope/branches/2.13/src/OFS/tests/test_userfolder.py 2011-10-24 22:29:40 UTC 
(rev 123151)
+++ Zope/branches/2.13/src/OFS/tests/test_userfolder.py 2011-10-24 22:39:13 UTC 
(rev 123152)
@@ -17,7 +17,15 @@
 # TODO class Test_readUserAccessFile(unittest.TestCase)
 
 
-# TODO class BasicUserFoldertests(unittest.TestCase)
+class BasicUserFolderTests(unittest.TestCase):
+ 
+def _getTargetClass(self):
+from OFS.userfolder import BasicUserFolder
+return BasicUserFolder
+ 
+def test_manage_users_security_initialized(self):
+uf = self._getTargetClass()()
+self.assertTrue(hasattr(uf, 'manage_users__roles__'))
 
 
 class UserFolderTests(unittest.TestCase):
@@ -171,6 +179,8 @@
 
 
 def test_suite():
-suite = unittest.TestSuite()
-suite.addTest(unittest.makeSuite(UserFolderTests))
+suite = unittest.TestSuite((
+unittest.makeSuite(BasicUserFolderTests),
+unittest.makeSuite(UserFolderTests),
+))
 return suite

Modified: Zope/branches/2.13/src/OFS/userfolder.py
===
--- Zope/branches/2.13/src/OFS/userfolder.py2011-10-24 22:29:40 UTC (rev 
123151)
+++ Zope/branches/2.13/src/OFS/userfolder.py2011-10-24 22:39:13 UTC (rev 
123152)
@@ -293,7 +293,9 @@
 message='Cannot change the id of a UserFolder',
 action='./manage_main'))
 
+InitializeClass(BasicUserFolder)
 
+
 class UserFolder(accesscontrol_userfolder.UserFolder, BasicUserFolder):
 Standard UserFolder object
 

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

[Zope-Checkins] SVN: Zope/trunk/ Fix serious authentication vulnerability in stock configuration.

[Tres Seaver]

Log message for revision 123153:
  Fix serious authentication vulnerability in stock configuration.
  

Changed:
  U   Zope/trunk/doc/CHANGES.rst
  U   Zope/trunk/src/OFS/tests/test_userfolder.py
  U   Zope/trunk/src/OFS/userfolder.py

-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst  2011-10-24 22:39:13 UTC (rev 123152)
+++ Zope/trunk/doc/CHANGES.rst  2011-10-24 22:41:46 UTC (rev 123153)
@@ -11,6 +11,8 @@
 Bugs Fixed
 ++
 
+- Fixed serious authentication vulnerability in stock configuration.
+
 - Fixed a regression in webdav support that broke external editor feature.
 
 - Restore ability to undo multiple transactions from the ZMI by using the

Modified: Zope/trunk/src/OFS/tests/test_userfolder.py
===
--- Zope/trunk/src/OFS/tests/test_userfolder.py 2011-10-24 22:39:13 UTC (rev 
123152)
+++ Zope/trunk/src/OFS/tests/test_userfolder.py 2011-10-24 22:41:46 UTC (rev 
123153)
@@ -17,7 +17,15 @@
 # TODO class Test_readUserAccessFile(unittest.TestCase)
 
 
-# TODO class BasicUserFoldertests(unittest.TestCase)
+class BasicUserFolderTests(unittest.TestCase):
+ 
+def _getTargetClass(self):
+from OFS.userfolder import BasicUserFolder
+return BasicUserFolder
+ 
+def test_manage_users_security_initialized(self):
+uf = self._getTargetClass()()
+self.assertTrue(hasattr(uf, 'manage_users__roles__'))
 
 
 class UserFolderTests(unittest.TestCase):
@@ -171,6 +179,8 @@
 
 
 def test_suite():
-suite = unittest.TestSuite()
-suite.addTest(unittest.makeSuite(UserFolderTests))
+suite = unittest.TestSuite((
+unittest.makeSuite(BasicUserFolderTests),
+unittest.makeSuite(UserFolderTests),
+))
 return suite

Modified: Zope/trunk/src/OFS/userfolder.py
===
--- Zope/trunk/src/OFS/userfolder.py2011-10-24 22:39:13 UTC (rev 123152)
+++ Zope/trunk/src/OFS/userfolder.py2011-10-24 22:41:46 UTC (rev 123153)
@@ -293,7 +293,9 @@
 message='Cannot change the id of a UserFolder',
 action='./manage_main'))
 
+InitializeClass(BasicUserFolder)
 
+
 class UserFolder(accesscontrol_userfolder.UserFolder, BasicUserFolder):
 Standard UserFolder object
 

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

Re: [Zope-dev] zope-tests - FAILED: 21, OK: 31

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/24/2011 07:24 AM, Brian Sutherland wrote:
 On Thu, Oct 20, 2011 at 11:58:09AM -0400, Tres Seaver wrote:

 Syntax errors due to Py3k compatibility changes in 'zope.schema'.
 The ZTK 1.1dev checkouts pull in the trunk of 'zope.schema',
 which is now backward-incompatible (it drops support for Python
 2.5).  I think we should be creating a '3.8' branch of
 'zope.schema' (copied from 3.8.1), and make the ZTK 1.1dev
 checkout use that.
 
 Thanks for fixing these. I didn't realize that the buildouts would
 break because of my change. I should have though.
 
 (I've also given up looking at the buildout perma-failures a long
 time ago)

We should probably look at *all* '/trunk' dependencies in the ZTK as
future sources of such problems:  people working on trunk development
know that the released ZTK pins versions, but may not realize that the
'-dev' checkouts are possibly affected.

Preemptively switching ZTK dev checkouts to use only release branches
would make that problem go away, but at the cost of requiring
bugfix-only changes to be backported:  today, in many packages, the
trunk remains identical to a release branch for a long time.

Rather than such a drastic step, I think we need to adopt a new policy
that the developer who makes the first non-bugfix change to the
trunk (i.e., adding a new feature or dependency, a
backward-incompatibility, or dropping support for a Python version) is
also responsible for finding an fixing any ZTK breakage (e.g., by
creating the release branch and changing the ZTK configuration to use it).


 [21]   FAILED  winbot / ztk_dev py_254_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html


 
This is the same Python 2.5 incompatibility problem which afflicts #7.
 
 This is a tricky issue, there are 2 parts:
 
 * Supporting python 2.5 in zope.schema is not hard, but will make 
 the code quite ugly (no class decorator for implements) * I'm not
 sure if the next version of the ZTK will need to support Python
 2.5
 
 So there seem to be 3 options to fix this buildout issue:
 
 1. Point the ZTK trunk at the zope.schema 3.8 branch 2. Make the
 zope.schema code uglier and support 2.5 3. Declare that the next
 ZTK version drops support for 2.5 and stop the buildbot for Python
 2.5 + ZTK trunk
 
 I'm partial to option 1 to get the buildbot working and defer the
 Python 2.5/ugly code decision to later.

I also prefer that we drop 2.5 compatibility on the ZTK trunk.  The
2.5.6 release page says[1]:

  This release is most likely the final release of Python 2.5; under
  the current release policy, no security issues in Python 2.5 will be
  fixed after October, 2011.

[1] http://www.python.org/download/releases/2.5.6/



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/

iEYEARECAAYFAk6lf24ACgkQ+gerLs4ltQ53lgCcCAuxGG5Up+0XfFRquXyaLxtK
XiMAnjhY+HzfjTddr3afk8kk66U345C/
=BJmV
-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] Hotfix for security vulnerability

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Zope security response team, I would like to announce
the availability of a hotfix for a vulnerability inadvertently
published earlier today.

'Products.Zope_Hotfix_20111024' README
==

Overview
- 

This hotfix addresses a serious vulnerability in the Zope2
application server.  Affected versions of Zope2 include:

- - 2.12.x = 2.12.20

- - 2.13.x = 2.13.6

Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.

The Zope2 security response team recommends that all users of
these releases upgrade to an unaffected release (2.12.21 or
2.13.11) as soon as they become available.

Until that upgrade is feasible, deploying this hotfix also
mitigates the vulnerability.


Installing the Hotfix:  Via 'easy_install'
- ---

If the Python which runs your Zope instance has 'setuptools'
installed (or is a 'virtualenv'), you can install the hotfix
directly from PyPI::

  $ /prefix/bin/easy_install Products.Zope_Hotfix_20111024

and then restart the Zope instance, e.g.:

  $ /path/to/instance/bin/zopectl restart


Installing the Hotfix:  Via 'zc.buildout'
- -

If your Zope instance is managed via 'zc.buildout', you can
install the hotfix directly from PyPI.  Edit the 'buildout.cfg'
file, adding Products.Zope_Hotfix_20111024 to the eggs
section of the instance.  E.g.::

  [instance] recipe = plone.recipe.zope2instance #...  eggs =
  ${buildout:eggs} Products.Zope_Hotfix_20111024

Next, re-run the buildout::

  $ /path/to/buildout/bin/buildout

and then restart the Zope instance, e.g.:

  $ /path/to/buildout/bin/instance restart


Installing the Hotfix:  Manual Installation
- ---

You may also install this hotfix manually.  Download the tarball from
the PyPI page:

 http://pypi.python.org/pypi/Products.Zope_Hotfix_20111024

Unpack the tarball and add a 'products' key to the 'etc/zope.conf' of
your instance.  E.g.::

  products /path/to/Products.Zope_Hotfix_20111024/Products

and restart.


Verifying the Installation
- --

After restarting the Zope instance, check the
'Control_Panel/Products' folder in the Zope Management Interface,
e.g.:

  http://localhost:8080/Control_Panel/Products/manage_main

You should see the 'Zope_Hotfix_20111024' product folder there.



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/

iEYEARECAAYFAk6l3pQACgkQ+gerLs4ltQ66AgCfT1cd94LXzBtdzNiBqKXnGBIF
7dwAoISO0AkuvERn+cw4W0cPo82c5r+D
=xRBY
-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] Hotfix for security vulnerability

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On behalf of the Zope security response team, I would like to announce
the availability of a hotfix for a vulnerability inadvertently
published earlier today.

'Products.Zope_Hotfix_20111024' README
==

Overview
- 

This hotfix addresses a serious vulnerability in the Zope2
application server.  Affected versions of Zope2 include:

- - 2.12.x = 2.12.20

- - 2.13.x = 2.13.6

Older releases (2.11.x, 2.10.x, etc.) are not vulnerable.

The Zope2 security response team recommends that all users of
these releases upgrade to an unaffected release (2.12.21 or
2.13.11) as soon as they become available.

Until that upgrade is feasible, deploying this hotfix also
mitigates the vulnerability.


Installing the Hotfix:  Via 'easy_install'
- ---

If the Python which runs your Zope instance has 'setuptools'
installed (or is a 'virtualenv'), you can install the hotfix
directly from PyPI::

  $ /prefix/bin/easy_install Products.Zope_Hotfix_20111024

and then restart the Zope instance, e.g.:

  $ /path/to/instance/bin/zopectl restart


Installing the Hotfix:  Via 'zc.buildout'
- -

If your Zope instance is managed via 'zc.buildout', you can
install the hotfix directly from PyPI.  Edit the 'buildout.cfg'
file, adding Products.Zope_Hotfix_20111024 to the eggs
section of the instance.  E.g.::

  [instance] recipe = plone.recipe.zope2instance #...  eggs =
  ${buildout:eggs} Products.Zope_Hotfix_20111024

Next, re-run the buildout::

  $ /path/to/buildout/bin/buildout

and then restart the Zope instance, e.g.:

  $ /path/to/buildout/bin/instance restart


Installing the Hotfix:  Manual Installation
- ---

You may also install this hotfix manually.  Download the tarball from
the PyPI page:

 http://pypi.python.org/pypi/Products.Zope_Hotfix_20111024

Unpack the tarball and add a 'products' key to the 'etc/zope.conf' of
your instance.  E.g.::

  products /path/to/Products.Zope_Hotfix_20111024/Products

and restart.


Verifying the Installation
- --

After restarting the Zope instance, check the
'Control_Panel/Products' folder in the Zope Management Interface,
e.g.:

  http://localhost:8080/Control_Panel/Products/manage_main

You should see the 'Zope_Hotfix_20111024' product folder there.



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/

iEYEARECAAYFAk6l3pQACgkQ+gerLs4ltQ66AgCfT1cd94LXzBtdzNiBqKXnGBIF
7dwAoISO0AkuvERn+cw4W0cPo82c5r+D
=xRBY
-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-dev] zope-tests - FAILED: 21, OK: 37

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/21/2011 09:00 PM, Zope tests summarizer wrote:

 [1]FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051475.html

 
 
 [2]FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051477.html

 
 
 [3]FAILED  ZTK 1.0dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051476.html

These
 
are faulres in the zope.app.apidoc tests, due to a
BBB-incompatible change on the zope.deprecation trunk:

 ConfigurationExecutionError: class
'zope.configuration.exceptions.ConfigurationError': Help Topic
definition
/home/ccomb/ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/src/zope.deprecation/src/zope/deprecation/README.txt
does not exist
   in:
   File
/home/ccomb/ztk1.0dev-slave/Python2.5.5-Linux-64bit/build/src/zope.app.apidoc/src/zope/app/apidoc/bookmodule/book.zcml,
line 201.4-205.10
   bookchapter
   id=deprecation
   title=Deprecation API
   doc_path=README.txt
   /

I just checked in a change which updates ZTK 1.0 to use a new 3.4
branch of zope.deprecation.


 [4]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051457.html

 
 
 [5]FAILED  ZTK 1.1 / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051456.html

 
 
 [6]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051455.html

These
 
are still showing a failure due to an unexpected 'Data.fs' file
in what is supposed to be a newly-created tempdir (in doctest file
'zope/testing/setupstack.txt').  I don't understand the failure (nor
the test).

#4 and #5 also have another obnoxious doctest failure in file
 'zope/testrunner/testrunner-layers-buff.txt':  maybe there is a
Python platform incompatibility here?

#5 shows a failure in the zope.testrunner.subunit tests::

  Usage: test [options] [MODULE] [TEST]

  test: error: option --profile: invalid choice: 'cProfile' \
 (choose from )

I don't think anybody the the Canonical guys knows this code well.


 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051472.html

This
 
shows the same 'zope/testrunner/testrunner-layers-buff.txt'
failure as #4 / #5.

Also, the zope.testbrowser tests are failing due to use of WebOb
1.2b2, which drops compatibility with Python 2.5.  We should not be
pulling in the trunk of zope.app.testing or zope.app.wsgi, but rather
branches which correspond to the versions released in ZTK 1.1.


 [8]FAILED  ZTK 1.1dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051471.html

This
 
report includes the unexpected Data.fs failure (as #4, #5, and
#6), the subprocess bufferning failure (as #4 and #5), and the
'--profile=cProfile' error (as #5).


 [9]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051470.html

This
 
report fails only due to the unexpected Data.fs failure (as #4,
#5, #6, and #8).


#10 - 20 omitted:  perma-failing z3c.* tests esse delendam!


 [21]   FAILED  winbot / ztk_dev py_254_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051498.html

This
 
test is failing due to inclusion of the zope.schema trunk:  I
think the recipe should be clearing, or at least force-updating, the
checked out trees under 'src' before testing.



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/

iEYEARECAAYFAk6jHHQACgkQ+gerLs4ltQ6k9QCeIM3q7KSy9kXfTUwqTYGQ3gjl
KlYAoLnFBDm8f4SxJDZIoTmcCc+h6Kq2
=Hha/
-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 )

Re: [Zope-dev] zope-tests - FAILED: 21, OK: 31

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051353.html

 
 
 [2]FAILED  ZTK 1.0dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051351.html

 
 
 [3]FAILED  ZTK 1.0dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051352.html

These
 
are all failing due to a missing version pin for 'six', which
should not happen:  the ZTK 1.0 package set should not include the new
version of 'zope.schema' which introduced this dependency.


 [4]FAILED  ZTK 1.1 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051398.html

 
 
 [5]FAILED  ZTK 1.1 / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051397.html

 
 
 [6]FAILED  ZTK 1.1 / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051396.html

This
 
failure is due to the unexpected presence of a 'Data.fs' file in
what is supposed to be a newly-created tempdir.  I don't understand
how that is supposed to work, but the bug seems real.


 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html

Syntax
 
errors due to Py3k compatibility changes in 'zope.schema'.  The
ZTK 1.1dev checkouts pull in the trunk of 'zope.schema', which is
now backward-incompatible (it drops support for Python 2.5).  I think
we should be creating a '3.8' branch of 'zope.schema' (copied from
3.8.1), and make the ZTK 1.1dev checkout use that.  Meanwhile, I
think we should update the 'zope.schema' trunk to indicate that it is
targeting a new major version, 4.0, due to new dependencies and
dropping Python 2.5 compatibility.


 [8]FAILED  ZTK 1.1dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051356.html

There
 
is an odd 'zope.testrunner' failure here:

 Usage: test [options] [MODULE] [TEST]

 test: error: option --profile: invalid choice: 'cProfile' (choose from )


 Failure in test
/home/ccomb/ztk1.1dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testrunner/src/zope/testrunner/testrunner-subunit.txt
 Failed doctest test for testrunner-subunit.txt

And also the unexpected Data.fs issue which affected #4, 5, and 6.


 [9]FAILED  ZTK 1.1dev / Python2.7.2 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051355.html

This
 
is the unexpected Data.fs issue which affected #4, 5, and 6.


I'm ignoring the 'z3c.*' failures:  I still want these tests either
fixed or else dropped from the daily report.


 [21]   FAILED  winbot / ztk_dev py_254_win32 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html

This
 
is the same Python 2.5 incompatibility problem which afflicts #7.



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/

iEYEARECAAYFAk6gRRAACgkQ+gerLs4ltQ7/DwCePrkkEc0JzRq5ukPaPpvgx/YC
MZ4Anj0IM4SH/uWPnvVVOXbtO2fBCEfu
=rxze
-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 )

Re: [Zope-dev] zope-tests - FAILED: 21, OK: 31

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/20/2011 11:58 AM, Tres Seaver wrote:

 [7]FAILED  ZTK 1.1dev / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html

 
 Syntax errors due to Py3k compatibility changes in 'zope.schema'.
 The ZTK 1.1dev checkouts pull in the trunk of 'zope.schema',
 which is now backward-incompatible (it drops support for Python
 2.5).  I think we should be creating a '3.8' branch of
 'zope.schema' (copied from 3.8.1), and make the ZTK 1.1dev
 checkout use that.  Meanwhile, I think we should update the
 'zope.schema' trunk to indicate that it is targeting a new major
 version, 4.0, due to new dependencies and dropping Python 2.5
 compatibility.

Both ZTK 1.0 and 1.1 include zope.schema 3.7.1.  I just made a '3.7'
branch, copying from the '3.7.1' tag, and updated the 'ztk.cfg' for
both ZTK branches to use it, rather than the 'zope.schema' trunk.


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/

iEYEARECAAYFAk6gSlcACgkQ+gerLs4ltQ4JYACfX/1UncaAc9maneofMz9Mwezu
iCoAn2DDHh/EVnVC+AvS2+2Wx+wbR1dV
=fU6h
-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-Checkins] SVN: Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py Remove tests which assert no-longer-supported cookie special case behavior.

[Tres Seaver]

Log message for revision 123095:
  Remove tests which assert no-longer-supported cookie special case behavior.

Changed:
  U   Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py

-=-
Modified: Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py
===
--- Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py 2011-10-14 14:53:12 UTC 
(rev 123094)
+++ Zope/trunk/src/ZPublisher/tests/testHTTPResponse.py 2011-10-17 13:26:13 UTC 
(rev 123095)
@@ -409,28 +409,6 @@
 self.assertEqual(response.headers['location'],
  'http://www.ietf.org/rfc/rfc2616.txt')
 
-def test_setHeader_Set_Cookie_special_case(self):
-# This is crazy, given that we have APIs for cookies.  Special
-# behavior will go away in Zope 2.13
-response = self._makeOne()
-response.setHeader('Set-Cookie', 'foo=bar')
-self.assertEqual(response.getHeader('Set-Cookie'), None)
-self.assertEqual(response.accumulated_headers,
- [('Set-Cookie', 'foo=bar')])
-
-def test_setHeader_drops_CRLF_when_accumulating(self):
-# RFC2616 disallows CRLF in a header value.
-# This is crazy, given that we have APIs for cookies.  Special
-# behavior will go away in Zope 2.13
-response = self._makeOne()
-response.setHeader('Set-Cookie', 'allowed=OK')
-response.setHeader('Set-Cookie',
-   'violation=http://www.ietf.org/rfc/\r\nrfc2616.txt;')
-self.assertEqual(response.accumulated_headers,
-[('Set-Cookie', 'allowed=OK'),
- ('Set-Cookie',
-  'violation=http://www.ietf.org/rfc/rfc2616.txt;')])
-
 def test_appendHeader_no_existing(self):
 response = self._makeOne()
 response.appendHeader('foo', 'foo')

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

[Zope-dev] Getting back to green

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

We've lost our discipline about keeping the daily tests passing.  I
think this is due to two factors:

- - We are running tests for code that nobody is actively maintaining
  (e.g., all the 'z3c.*' packages which have been broken for months).

- - Because of the noise of those failures, we've gotten complacent about
  seeing multiple failures in the daily test report, and thus quit
  trying to find and fix new failures in code which is maintained.

I would like to propose that we quit reporting test failures for the
unmaintained packages ('zc3.*', for a start.  If somebody really
thinks there is value in such testing, we could perhaps run those
tests only weekly (like the others which have expected failures).


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/

iEYEARECAAYFAk6cNvcACgkQ+gerLs4ltQ5N+gCfYAD2UM6Y5ikE92VHERoTk24o
YpkAmwVy9SvDWBW/vrNyR3nDmryDAPXZ
=9kh3
-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 )

Re: [Zope-dev] Getting back to green

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/17/2011 10:21 AM, Adam GROSZER wrote:
 Hello,
 
 On Mon, 17 Oct 2011 10:08:55 -0400 you wrote:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 We've lost our discipline about keeping the daily tests passing.
 I think this is due to two factors:
 
 - - We are running tests for code that nobody is actively
 maintaining (e.g., all the 'z3c.*' packages which have been
 broken for months).
 
 If you mean the failures on windowze, I think most of them fail on
 lxml not having windows egg :-S, someone should kick Sidnei(???)

If the z3c.* packages are being maintained, but not by folks who can
resolve that issue on Windows, then we should do the testing on a
platform where the maintainers *can* get the tests to pass.  Having
the board stay red destroys its value for *everybody*, including those
who don't need or care about those packages.

 - - Because of the noise of those failures, we've gotten
 complacent about seeing multiple failures in the daily test
 report, and thus quit trying to find and fix new failures in
 code which is maintained.
 
 I would like to propose that we quit reporting test failures for
 the unmaintained packages ('zc3.*', for a start.  If somebody
 really thinks there is value in such testing, we could perhaps
 run those tests only weekly (like the others which have
 expected failures).
 
 If it's about suppressing the *reporting* then suppress that, not
 the test runs please. Just in case someone wants to maintain a
 package ;-)

Why waste any resources on tests if nobody is going to find and fix
failures?


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/

iEYEARECAAYFAk6cQq8ACgkQ+gerLs4ltQ4aegCgsdOW/Fs9LxVqwo3Pb2OXDw2N
4NIAn3b+OuPml61WVj+n107FpbHf3c2u
=upzk
-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] Security vulnerabiity 20110928: Arbitrary Code Execution (pre-announcement)

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The Zope security response team is pre-announcing a fix for a
vulnerability in Zope 2.12.x and Zope 2.13.x that allows execution of
arbitrary code by anonymous users.

This is a severe vulnerability that allows an unauthenticated attacker
to employ a carefully crafted web request to execute arbitrary commands
with the privileges of the Zope service.

Versions Affected:  Zope 2.12.x and Zope 2.13.x.

Versions Not Affected: Zope 2.9.x, Zope 2.10.x, Zope 2.11.x

This is a pre-announcement. Due to the severity of this issue we are
providing an advance warning of an upcoming patch, which will be
released 2011-10-04 15:00 UTC.


What you should do in advance of patch availability
===

Due to the nature of the vulnerability, the security team has decided to
pre-announce that a fix is upcoming before disclosing the details. This
is to ensure that concerned users can plan around the release.  As the
fix being published will make the details of the vulnerability public,
we are recommending that all users plan a maintenance window for 30
minutes either side of the announcement where your site is completely
inaccessible in which to install the fix.

Meanwhile, we STRONGLY recommend that you take the following steps to
protect your site:

- - Make sure that the Zope service is running with with minimum
  privileges. Ideally, the Zope and ZEO services should be able to
  write only to log and data directories.

- - Use an intrusion detection system that monitors key system resources
  for unauthorized changes.

- - Monitor your Zope, reverse-proxy request and system logs for unusual
  activity.

In this case, these are standard precautions that should be employed on
any production system.

Extra help
==

Should you not have in-house server administrators or a service
agreement looking after your website you can find consultancy companies
on plone.net.

There is also free support available online via Zope mailing lists and
the #zope IRC channels.

Questions and Answers
=

Q: When will the patch be made available?
A: The Security Team will release the patch at 2011-10-04 15:00 UTC.

Q. What will be involved in applying the patch?
A. Patches are made available as tarball-style archives that may be
unpacked into the “products” folder of a buildout installation and as
Python packages that may be installed by editing a buildout
configuration file and running buildout.  Patching is generally easy and
quick to accomplish.

Q: How was this vulnerability found?
A: This issue was found as part of a routine audit performed by the
Plone Security team.

Q: My site is highly visible and mission-critical. I hear the patch has
already been developed. Can I get the fix before the release date?
A: No. The patch will be made available to all users at the same time.
There are no exceptions.

Q: If the patch has been developed already, why isn't it already made
available to the public?
A: The Security Team is still testing the patch and running various
scenarios thoroughly. The team is also making sure everybody has
appropriate time to plan to patch their Zope installation(s). Some
consultancy organizations have hundreds of sites to patch and need the
extra time to coordinate their efforts with their clients.

Q: How does one exploit the vulnerability?
A: This information will not be made available until after the patch is
made available.

Q: Is there a CVE record for this vulnerability?
A: Not yet. This information will be added when available.

If you have specific questions about this vulnerability or its handling,
contact the Zope Security Team, security-respo...@zope.org.

To report potentially security-related issues, please send a mail to the
Zope Security Team at security-respo...@zope.org. The security team is
always happy to credit individuals and companies who make responsible
disclosures.

Information for vulnerability database maintainers
==

CVSS Base Score
7.5 (AV:N/AC:L/Au:N/C:P/I:P/A:P/E:P/RL:O/RC:C)

Impact Subscore
6.4

Exploitability Subscore
10

CVSS Temporal Score
5.9

Credit
Alan Hoey


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/

iEYEARECAAYFAk6DlaMACgkQ+gerLs4ltQ7D+gCgz6WA6J44vxkhjnJGquBzCR33
nPgAn3cl0/do5VB+B6h9WmM22yIGOb7Z
=/HcQ
-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-dev] zope.sqlalchemy+py3 test failures.

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 09/27/2011 02:01 AM, Chris McDonough wrote:
 On Mon, 2011-09-26 at 21:47 -0400, Chris McDonough wrote:
 In case anyone is interested, I've made a stab at porting 
 zope.sqlalchemy to Python 3 at 
 http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ .
 Several tests still fail.  I could use some help fixing them.
 
 To run the test suite:
 
 - Create a Python 3.2 virtualenv.
 
 - Install nose into the virtualenv.
 
 - Check out the chrism-py3 transaction branch from 
 svn://svn.zope.org/repos/main/transaction/branches/chrism-py3
 
 - Install the chrism-py3 transaction checkout into the
 virtualenv, e.g. $env32/bin/python setup.py develop.
 
 - Install this package into the virtualenv eg. run
 $env32/bin/python setup develop.
 
 - Run $env32/bin/python setup.py nosetests.
 
 Currently 2 tests fail:
 
 
 Mike Merickel solved this...
 
 This is because the setuptools (and nose) testrunners do not respect
 the ``test_suite`` stanza at the bottom of ``tests.py``; these
 shouldn't be getting run unless the DSN has postgres in it, and they
 are getting run regardless (under sqlite).
 
 That brings up how to cope with running test suites that depend on 
 zope.testrunner features in a cross-platform way.  Currently the 
 bootstrap script in this package wont run under Py3.

This bootstrap is from Jim's '2' branch of zc.buildout:

 
http://svn.zope.org/zc.buildout/branches/2/bootstrap/bootstrap.py?rev=121484view=auto

It is designed to work with Py3k.


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/

iEYEARECAAYFAk6B/IYACgkQ+gerLs4ltQ6XOwCeNuYNhjXbasb5Qfr729Howd5N
6sAAoIpnbXpvLMP340cyt3PghRjrah34
=933g
-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-Checkins] SVN: Zope/branches/2.12/src/OFS/misc_.py PEP8.

[Tres Seaver]

Log message for revision 122955:
  PEP8.

Changed:
  U   Zope/branches/2.12/src/OFS/misc_.py

-=-
Modified: Zope/branches/2.12/src/OFS/misc_.py
===
--- Zope/branches/2.12/src/OFS/misc_.py 2011-09-26 19:54:53 UTC (rev 122954)
+++ Zope/branches/2.12/src/OFS/misc_.py 2011-09-26 20:44:02 UTC (rev 122955)
@@ -13,9 +13,15 @@
 
 from os.path import dirname
 
+import AccessControl
 from AccessControl.SecurityInfo import ClassSecurityInfo
+import App
 from App.class_init import InitializeClass
 from App.ImageFile import ImageFile
+import HelpSys
+import OFS
+import TreeDisplay
+import webdav
 
 
 class misc_:
@@ -34,21 +40,17 @@
 here = dirname(__file__)
 broken = ImageFile('www/broken.gif', here)
 
-import AccessControl
 User_icon = ImageFile('www/User_icon.gif', dirname(AccessControl.__file__))
 
 locked = ImageFile('www/modified.gif', here)
 lockedo = ImageFile('www/locked.gif', here)
 
-import webdav
 davlocked = ImageFile('www/davlock.gif', dirname(webdav.__file__))
 
-import TreeDisplay
 treedisplay_dir = dirname(TreeDisplay.__file__)
 pl = ImageFile('www/Plus_icon.gif', treedisplay_dir)
 mi = ImageFile('www/Minus_icon.gif', treedisplay_dir)
 
-import App
 app_dir = dirname(App.__file__)
 rtab = ImageFile('www/rtab.gif', app_dir)
 ltab = ImageFile('www/ltab.gif', app_dir)
@@ -56,7 +58,6 @@
 r_arrow_gif = ImageFile('www/r_arrow.gif', here)
 l_arrow_gif = ImageFile('www/l_arrow.gif', here)
 
-import OFS
 ofs_dir = dirname(OFS.__file__)
 ControlPanel_icon = ImageFile('www/ControlPanel_icon.gif', ofs_dir)
 ApplicationManagement_icon = ImageFile('www/cpSystem.gif', app_dir)
@@ -76,7 +77,6 @@
 Properties_icon = ImageFile('www/Properties_icon.gif', ofs_dir)
 Propertysheets_icon = ImageFile('www/Properties_icon.gif', ofs_dir)
 
-import HelpSys
 helpsys_dir = dirname(HelpSys.__file__)
 ProductHelp_icon=ImageFile('images/productHelp.gif', helpsys_dir)
 HelpTopic_icon=ImageFile('images/helpTopic.gif', helpsys_dir)

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

[Zope-Checkins] SVN: Zope/branches/2.13/src/OFS/misc_.py PEP8

[Tres Seaver]

Log message for revision 122956:
  PEP8

Changed:
  U   Zope/branches/2.13/src/OFS/misc_.py

-=-
Modified: Zope/branches/2.13/src/OFS/misc_.py
===
--- Zope/branches/2.13/src/OFS/misc_.py 2011-09-26 20:44:02 UTC (rev 122955)
+++ Zope/branches/2.13/src/OFS/misc_.py 2011-09-26 20:44:29 UTC (rev 122956)
@@ -15,7 +15,11 @@
 
 from AccessControl.class_init import InitializeClass
 from AccessControl.SecurityInfo import ClassSecurityInfo
+import App
 from App.ImageFile import ImageFile
+import HelpSys
+import OFS
+import webdav
 
 
 class misc_:
@@ -34,20 +38,17 @@
 here = dirname(__file__)
 broken = ImageFile('www/broken.gif', here)
 
-import OFS
 ofs_dir = dirname(OFS.__file__)
 User_icon = ImageFile('www/User_icon.gif', ofs_dir)
 
 locked = ImageFile('www/modified.gif', here)
 lockedo = ImageFile('www/locked.gif', here)
 
-import webdav
 davlocked = ImageFile('www/davlock.gif', dirname(webdav.__file__))
 
 pl = ImageFile('www/Plus_icon.gif', ofs_dir)
 mi = ImageFile('www/Minus_icon.gif', ofs_dir)
 
-import App
 app_dir = dirname(App.__file__)
 rtab = ImageFile('www/rtab.gif', app_dir)
 ltab = ImageFile('www/ltab.gif', app_dir)
@@ -73,7 +74,6 @@
 Properties_icon = ImageFile('www/Properties_icon.gif', ofs_dir)
 Propertysheets_icon = ImageFile('www/Properties_icon.gif', ofs_dir)
 
-import HelpSys
 helpsys_dir = dirname(HelpSys.__file__)
 ProductHelp_icon=ImageFile('images/productHelp.gif', helpsys_dir)
 HelpTopic_icon=ImageFile('images/helpTopic.gif', helpsys_dir)

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

[Zope-Checkins] SVN: Zope/trunk/src/OFS/misc_.py PEP8.

[Tres Seaver]

Log message for revision 122859:
  PEP8.

Changed:
  U   Zope/trunk/src/OFS/misc_.py

-=-
Modified: Zope/trunk/src/OFS/misc_.py
===
--- Zope/trunk/src/OFS/misc_.py 2011-09-20 15:19:58 UTC (rev 122858)
+++ Zope/trunk/src/OFS/misc_.py 2011-09-20 17:23:47 UTC (rev 122859)
@@ -15,6 +15,7 @@
 
 from AccessControl.class_init import InitializeClass
 from AccessControl.SecurityInfo import ClassSecurityInfo
+import App
 from App.ImageFile import ImageFile
 
 
@@ -31,7 +32,6 @@
 security = ClassSecurityInfo()
 security.declareObjectPublic()
 
-import App
 app_dir = dirname(App.__file__)
 zopelogo_png = ImageFile('www/zopelogo.png', app_dir)
 

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

Re: [Zope-dev] web sites are keep crashing

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/26/2011 10:24 PM, Babylakshmi Muthusamy wrote:

 We have 3 sites running in the same web server. In one of them, i
 migrated the database from ZODB to mySQL.

Do you mean that you migrated from Filestorage to RelStorage, backed by
MySQL, or do you mean that you re-wrote your application to use MySQL
directly (maybe via Products.ZMySQLDA)?

 After uploading the migrated site back, all the sites are crashing
 very often.

Crashing seems to imply that your Zope server is stopping:  the
indivdual sites you serve from that serve can't crash, per se.  Or do
you mean that they are displaying error pages?

If the Zope server process is actually stopping, there may be something
in the error log which helps diagnose the problem.

If there is nothing in the error log, then it seems likely that your
server is segfaulting (maybe due to a bug in the MySQL library, or else
it is built improperly).  In that case, you might learn something by
running the server in the foreground (e.g, 'bin/zopectl fg', instead of
'bin/zopectl start'), or with coredumps enabled.



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/

iEYEARECAAYFAk5ZAgcACgkQ+gerLs4ltQ74qgCeLodVOTuV+G59rJk76zFncqnI
OaUAn19SEnaQvVj9kCw0ow25SNisXlbT
=A3Wv
-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 )

Re: [Zope-CMF] cmf-tests - OK: 2, UNKNOWN: 2

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]UNKNOWN UNKNOWN : CMF-trunk Zope-2.13 Python-2.6.6 : Linux 
 https://mail.zope.org/pipermail/cmf-tests/2011-August/015148.html
 
 
 [2]UNKNOWN UNKNOWN : CMF-trunk Zope-trunk Python-2.6.6 : Linux 
 https://mail.zope.org/pipermail/cmf-tests/2011-August/015149.html

Both are download failures during bootstrap.


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/

iEYEARECAAYFAk5SowUACgkQ+gerLs4ltQ7u/QCgjiuWddrrO8kSyYlxHwBjn0BK
hVkAoNp6zTUcPl4lpic5ZQleuoBplItc
=GRXL
-END PGP SIGNATURE-

___
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

Re: [Zope-dev] zope-tests - FAILED: 10, OK: 28, UNKNOWN: 3

[Tres Seaver]

 / Python2.5.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-August/048306.html
 
 
 [7]FAILED  ZTK 1.0dev / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-August/048305.html

These two seem to be failing in the same way as the 2.4.6 tests.


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/

iEYEARECAAYFAk5Omd8ACgkQ+gerLs4ltQ61pwCgpcHORBFMR8RzMPBDxgId/z6p
8a4An3h7WqzAtMgKcYvAIqChenfr2Y8f
=noEb
-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 )

Re: [Zope-dev] SVN: zope.interface/trunk/ Fix a regression introduced in 3.6.4, that made one zope.app.interface test fail

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/17/2011 12:01 PM, Gediminas Paulauskas wrote:
 2011/8/6 Tres Seaver tsea...@palladion.com:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 On 08/04/2011 10:18 AM, Gediminas Paulauskas wrote:
 Log message for revision 122462: Fix a regression introduced in 
 3.6.4, that made one zope.app.interface test fail
 
 
 Changed: U   zope.interface/trunk/CHANGES.txt U 
 zope.interface/trunk/src/zope/interface/interface.py
 
 -=- Modified: zope.interface/trunk/CHANGES.txt 
 ===

 
- --- zope.interface/trunk/CHANGES.txt  2011-08-04 13:44:20 UTC (rev
 122461) +++ zope.interface/trunk/CHANGES.txt  2011-08-04 14:18:37
 UTC (rev 122462) @@ -11,10 +11,12 @@
 
 - Fix testing deprecation warnings issued when tested under
 Py3K.
 
 +- Fix ``InterfaceClass.__hash__`` to match comparison function.
 + 3.6.4 (2011-07-04) --
 
 -- LP 804951:  InterfaceClass instances were unhashable under
 Python 3.x. +- LP #804951:  InterfaceClass instances were
 unhashable under Python 3.x.
 
 3.6.3 (2011-05-26) --
 
 Modified: zope.interface/trunk/src/zope/interface/interface.py 
 ===

 
- --- zope.interface/trunk/src/zope/interface/interface.py  2011-08-04
 13:44:20 UTC (rev 122461) +++ 
 zope.interface/trunk/src/zope/interface/interface.py  2011-08-04 
 14:18:37 UTC (rev 122462) @@ -682,7 +682,8 @@ return (n1  n2) -
 (n1  n2)
 
 def __hash__(self): -return hash((self.__name__, 
 self.__module__)) +return hash((getattr(self,
 '__name__', ''), + getattr(self,
 '__module__', '')))
 
 I don't think this is a regression -- how do you legitimately
 create an interface without both those attributes?   The point of
 the comparison function is to work even when handed a non-Interface
 object as one of the two terms being compared, which doesn't apply
 to the case of a hash. If there is code in zope.app.interface which
 is constructing a class derived from Interface but which doesn't
 call Interface.__init__ before hashing the instance, that code is
 *broken*, and should be fixed.
 
 It was my attempt to fix tests that were failing for more than a
 week, and it worked. zope.app.interface might be broken, but I
 couldn't understand why it failed, especially the foreign
 connection exception. Here I saw asymmetry between __eq__ and
 __hash__, and I still feel that my fix was better than returning 1.

For the relevant case (an instance whose '__name__' and '__module__'
attributes were not set) your fix returned the hash of '('', '')', which
is hardly an improvement over another fixed constant.  The changes I
checked into zope.app.interface make the PersistentInterface class do
its equality testing / hashing based on its _p_jar and _p_oid:

  http://svn.zope.org/zope.app.interface/trunk/?rev=122544view=rev

 In addition to zope.app.interface, there was another problem with 
 Tahoe-LAFS: https://bugs.launchpad.net/zope.interface/+bug/811792
 that Tres helped to solve.

The new releases don't really solve their problem:  they still have
code which tries to store derived interface obejcts into a module-scope
dist from within the instance's '__new__'.  That code is still broken
(the objects won't be findable in the dict later), but it no longer
raises exceptions during module imoprt:  instead, it issues a UserWarning.


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/

iEYEARECAAYFAk5Na+0ACgkQ+gerLs4ltQ5PEACfUITfcCYeHGJpH/IAAUeP4Bfx
CAIAn3W8hYltSft2UPSbjnNgYL2NpCZt
=lP14
-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 )

Re: [Zope-dev] zope.interface versions, ZTK 1.0 and later

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/17/2011 10:03 AM, Tres Seaver wrote:

 [1] 
 http://buildbot.afpy.org/ztk1.0/builders/Python2.6.5%20Linux%2064bit/builds/344/steps/test%20ztk/logs/stdio

 
 I
 
 cannot reproduce that failure.  The assertion is actually
 backported, along with the updated fix for comparing same-named
 interfaces in different modules.

OK, I can reproduce this, but only sporadically, on x86-64 system.  I
have just checked in a fix (adding '__le__' and '__ge__' methods) which
should get those tests passing again on the 3.6 branch.

 http://svn.zope.org/zope.interface/branches/3.6/?view=revrev=122609



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/

iEYEARECAAYFAk5NdMkACgkQ+gerLs4ltQ4/oQCgzEq3/eHefb/6ah6VGgYcrhPu
HWAAoMHz8D/n0BUrk+FTuCkKA46z+C0Q
=2laj
-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 )

Re: [Zope-dev] RFC: Proposal for merging jbohman-zope.registry branch of zope.component

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/17/2011 02:12 AM, Adam GROSZER wrote:
 Hello,
 
 On Tue, 16 Aug 2011 22:50:42 -0400 you wrote:
 
 - - Merge the 'jbohman-zope.registry' branch of zope.component to
 the trunk, and bump its minor version accordingly.
 
 That sounds to me to rather have a *major* version number bump.

Moving from zope.component 3.10.x to 3.11.0 signals new dependencies /
new features, but backwards compatible, which fits here, I think.
Moving to 4.0 would signal likely backwards incompatible.

I'm fine either way.



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/

iEYEARECAAYFAk5LsHcACgkQ+gerLs4ltQ7CFgCeN7o+1vf09gzh5PHWxNuMfMqf
z5kAnAzGW/Xv5iHZbbkYhF/3bM4snuVS
=EguO
-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 )

Re: [Zope-dev] zope.interface versions, ZTK 1.0 and later

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/17/2011 09:56 AM, Gediminas Paulauskas wrote:
 2011/8/13 Tres Seaver tsea...@palladion.com:
 
 On 08/12/2011 02:46 PM, Tres Seaver wrote:
 
  % 
  Proposal 
 
 - Revert ZTK 1.0 to use zope.interface 3.6.1.  (We can skip this
 part if the next step goes quickly).
 
 - Create a 3.6 branch in SVN, and revert all the post-3.6.1
 changes on it.  Release a new 3.6.6 from this branch, possibly
 after applying a new, more minimal fix for LP #570942.
 
 - Bump ZTK 1.0 to use the zope.interface 3.6.6.
 
 - Freeze development on the 3.6 branch.
 
 - Release a 3.7.0 version from the trunk, with all the porting 
 changes intact.  Update ZTK 1.1 to use 3.7.0, 
  % 
 
 
 Done.
 
 It's all good, except that the tests of alternative solution in
 3.6.6 do not pass [1].
 
 Also I thought 3.6.2 was good for ZTK 1.0, as it worked on python 2.4
 - 3.2. Only the sorting improvement in next versions broke
 something.

Nothing in 3.6.2 helps legacy uses -- its only changes were Python3
porting tweaks and a non-fucntional change to how documentation was
displayed on PyPI.

 [1]
 http://buildbot.afpy.org/ztk1.0/builders/Python2.6.5%20Linux%2064bit/builds/344/steps/test%20ztk/logs/stdio

I
 
cannot reproduce that failure.  The assertion is actually backported,
along with the updated fix for comparing same-named interfaces in
different modules.


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/

iEYEARECAAYFAk5LykUACgkQ+gerLs4ltQ7S7gCgrh3vYHaE6UGZTjnEb3yEAtdT
5hQAn36EjEDzGHh30VrQGQFHza1ozqDD
=pPmX
-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] RFC: Proposal for merging jbohman-zope.registry branch of zope.component

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rationale
- 

The focus of the 2011 Pyramid GSoC project has been to port crucial
Pyramid dependencies to Python3:

 https://github.com/Pylons/pyramid/wiki/Python-3-Porting

At the end of this year's US PyCon, Lennart Regebro labelled[1]
zope.component as high-hanging fruit, due to the following factors::

- - magic

- - Mostly tested via doctests

- - Hairy dependencies (e.g., zope.proxy, zope.security)

- - Many more optional / testing dependencies (ZODB3, zope.schema,
  zope.configuration, etc.)

Based on IRC discussion at project kickoff[2], Joel Bohman, one of the
two Pyramid GSoC students, has tackled this issue by factoring
zope.component into two pieces:

- - Joel has moved the core registry bits into a new 'zope.registry'
  package, now hosted in the Zope SVN repository:

http://svn.zope.org/zope.registry/trunk

  Notes on the new package:

  - The tests in this package have been converted to standard unit
tests:  they all pass on Python 2.6, 2.7, and 3.2.

  - The hairy and optional / testing dependencies drop out:
zope.registry depends only on zope.interface and zope.event.

- - Joel made zope.component depend on zope.registry in a branch:

http://svn.zope.org/zope.component/jbohman-zope.registry

  This branch leaves BBB imports intact.

Proposal
- 

On bahalf of Joel and the Pyramid GSoC project, I would like to propose
the following changes to the ZTK trunK:

- - Land 'zope.registry' as a full ZTK package, with its own Launchpad
  artifacts, etc.  This step may also involve moving bugs from
  zope.component to zope.registry.

- - Merge the 'jbohman-zope.registry' branch of zope.component to the
  trunk, and bump its minor version accordingly.

- - Cut releases of both packages.

Once done, the remaining work to port zope.component should be smaller
(much of the magic bits are now in zope.registry).  We will update
pyramid to use zope.registry in place of zope.component.


[1] http://permalink.gmane.org/gmane.comp.web.zope.devel/26373

[2]
http://irclogs.rulim.de/%23pyramid/%23pyramid.2011-05-19.log.html#t2011-05-19T22:59:44-



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/

iEYEARECAAYFAk5LLIIACgkQ+gerLs4ltQ5qGACg1gskkWeTVrGZDusspMgaRlzF
TrwAoJdkhRjjudB9gcDtrisV2v+8JSpG
=kv7y
-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 )

Re: [Zope-dev] zope-tests - FAILED: 2, OK: 36, UNKNOWN: 3

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


 [4]FAILED  ZTK 1.0 / Python2.6.5 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-August/048124.html

I can't reproduce this with Python 2.6 running against a zope.interface
3.6.6 checkout.


 [5]FAILED  ZTK 1.0dev / Python2.4.6 Linux 64bit 
 https://mail.zope.org/pipermail/zope-tests/2011-August/048094.html

This one is also in zope.interface:  it looks as though the test ran
before I reverted the ZTK 1.0 checkout to use the new 3.6 branch, which
remains Python 2.4 compatible.



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/

iEYEARECAAYFAk5H96YACgkQ+gerLs4ltQ5TQACfTVb/wSWylUyH5jIoees/sRa4
kqgAn3zf6yd7mcybeCEb6vy6f8CAUtW+
=rog+
-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 )

Re: [Zope-dev] zope.interface versions, ZTK 1.0 and later

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/12/2011 02:46 PM, Tres Seaver wrote:

  %
  Proposal 
 
 - Revert ZTK 1.0 to use zope.interface 3.6.1.  (We can skip this part
 if the next step goes quickly).
 
 - Create a 3.6 branch in SVN, and revert all the post-3.6.1 changes
 on it.  Release a new 3.6.6 from this branch, possibly after applying
 a new, more minimal fix for LP #570942.
 
 - Bump ZTK 1.0 to use the zope.interface 3.6.6.
 
 - Freeze development on the 3.6 branch.
 
 - Release a 3.7.0 version from the trunk, with all the porting
 changes intact.  Update ZTK 1.1 to use 3.7.0, 
  %
 

Done.


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/

iEYEARECAAYFAk5GvUoACgkQ+gerLs4ltQ4BDgCgtVyxaWLwfusKVZxoi2CrCayH
zpAAn1ZeUD1vgb1lKq5F0smOovz1qbQz
=aO2L
-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.interface versions, ZTK 1.0 and later

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've been wrestling with Launchpad bugs for zope.interface lately, and
would like to hear from folks about the issues involved.

-  % 
Overview
- -

- - Version 3.6.1 was the original ZTK 1.0 version.  The substantial
  changes since then have been mostly due to issues which showed up
  while working on Python3 compatibility:

  o LP # 675064:  Specify return value type for C optimizations module
init under Python 3 (fixed in zope.interface 3.6.2).

  o LP 804951:  InterfaceClass instances were unhashable under Python
3.x. (fixed in zope.interface 3.6.4).

  The fix here actually provoked the following bugs / fixes:

  o LP #811792:  work around buggy behavior in some subclasses of
'zope.interface.interface.InterfaceClass', which invoke '__hash__'
before initializing '__module__' and '__name__'.

  o Fix Python 2.5 incompatibility introduced in new tests of
'__hash__'.

  o LP #825249: Fix test failure (only under 'python setup.py test')
in those same new tests.

  At this point, the tests for the trunk (but not the main module
  itself) are not Python 2.4 compatible, because they try to test that
  a UserWarning is emitted using a 'with' statement.

- - This fix is for non-CPython platforms:

  o LP #804832:  Do not build C extension under PyPy or Jython.

- - There is one issue not directly related to porting:

  o LP #570942:  Now correctly compare interfaces from different
modules but with the same names (fixed in 3.6.3).

  This fix is in two parts:  it corrects extracting the '__module__'
  attribute, and adds the missing rich comparison operators
  ('__eq__', '__ne__', '__le__', '__ge__')


  The real slippery slope was adding '__eq__':  it then required
  adding '__hash__', because Python's dictionary semantics require that
  objects which compare equal also hash equal, which then provokes the
  issues with subclasses which stash the instances in a dict before
  initializing the '__module__' and '__name__' attributes.

- - The ZTK 1.0 branch was bumped to include zope.interface 3.6.3, which
  contained a number of the higer-risk changes, mostly made for porting
  purposes.


Proposal
- 

- - Revert ZTK 1.0 to use zope.interface 3.6.1.  (We can skip this part if
  the next step goes quickly).

- - Create a 3.6 branch in SVN, and revert all the post-3.6.1 changes on
  it.  Release a new 3.6.6 from this branch, possibly after applying a
  new, more minimal fix for LP #570942.

- - Bump ZTK 1.0 to use the zope.interface 3.6.6.

- - Freeze development on the 3.6 branch.

- - Release a 3.7.0 version from the trunk, with all the porting changes
  intact.  Update ZTK 1.1 to use 3.7.0,
-  % 

Thoughts?


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/

iEYEARECAAYFAk5FdRAACgkQ+gerLs4ltQ5dnACfRSDauatZn1iMmefLsIQABcDJ
nSgAoNyJu8AS3M9ndEWveo/pbIVEfSRU
=gSl/
-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 )

Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/11/2011 04:21 PM, Hanno Schlichting wrote:

 Any code that does manual __of__ wrapping is suspicious and suggests 
 there's Acquisition problems lurking somewhere - I just got lucky to 
 finding this one so fast ;)

Hanno, didn't you hear the song?  All you need is __of___ (DAH, dah,
dadah dum).  Seriously, if manual '__of__' wrapping breaks, it is a
sign that somebody was mucking with code they didn't really understand.
;)  In this case, I truly don't understand the impatience to scrap
acquisition:  it is doing *exactly* what is wanted here.

 The ValueError: 'Access contents information' not found in
 inherited permissions failures remain, which are next on my
 list.
 
 That's fixed as well.
 
 The FS objects no longer have the Access contents information 
 permission. They only got that through the OFS.ZDOM base class,
 which is gone in Zope 4.


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/

iEYEARECAAYFAk5EQRMACgkQ+gerLs4ltQ63xgCgjuFsRSEEgUd6TB7taO2IgJRx
tSwAn3YtFAVCoFL/3ijsYhMfoX1AzxU4
=Rs6q
-END PGP SIGNATURE-

___
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

Re: [Zope-dev] SVN: zope.interface/trunk/ Fix a regression introduced in 3.6.4, that made one zope.app.interface test fail

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/04/2011 10:18 AM, Gediminas Paulauskas wrote:
 Log message for revision 122462: Fix a regression introduced in
 3.6.4, that made one zope.app.interface test fail
 
 
 Changed: U   zope.interface/trunk/CHANGES.txt U
 zope.interface/trunk/src/zope/interface/interface.py
 
 -=- Modified: zope.interface/trunk/CHANGES.txt 
 === 
 --- zope.interface/trunk/CHANGES.txt  2011-08-04 13:44:20 UTC (rev
 122461) +++ zope.interface/trunk/CHANGES.txt  2011-08-04 14:18:37 UTC
 (rev 122462) @@ -11,10 +11,12 @@
 
 - Fix testing deprecation warnings issued when tested under Py3K.
 
 +- Fix ``InterfaceClass.__hash__`` to match comparison function. + 
 3.6.4 (2011-07-04) --
 
 -- LP 804951:  InterfaceClass instances were unhashable under Python
 3.x. +- LP #804951:  InterfaceClass instances were unhashable under
 Python 3.x.
 
 3.6.3 (2011-05-26) --
 
 Modified: zope.interface/trunk/src/zope/interface/interface.py 
 === 
 --- zope.interface/trunk/src/zope/interface/interface.py  2011-08-04
 13:44:20 UTC (rev 122461) +++
 zope.interface/trunk/src/zope/interface/interface.py  2011-08-04
 14:18:37 UTC (rev 122462) @@ -682,7 +682,8 @@ return (n1  n2) - (n1
  n2)
 
 def __hash__(self): -return hash((self.__name__,
 self.__module__)) +return hash((getattr(self, '__name__',
 ''), + getattr(self, '__module__', '')))

I don't think this is a regression -- how do you legitimately create an
interface without both those attributes?   The point of the comparison
function is to work even when handed a non-Interface object as one of
the two terms being compared, which doesn't apply to the case of a hash.
If there is code in zope.app.interface which is constructing a class
derived from Interface but which doesn't call Interface.__init__ before
hashing the instance, that code is *broken*, and should be fixed.


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/

iEYEARECAAYFAk48WjQACgkQ+gerLs4ltQ7ceACcCIkqWBXaISkGj44RIFTPqdyx
d5kAn1H9biD8xF5T2Jf6kN/FQNBLRkbb
=aTGc
-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 )

Re: [Zope-dev] SVN: Zope/branches/2.13/src/ micro optimizations

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/29/2011 10:36 PM, Nikolay Kim wrote:
 Log message for revision 122429: micro optimizations

Assuming we have really good test coverage for the affected modules, the
micro-optimizations mostly look fine.  However, the following diff
changes semantics, and not just performance::

 --- Zope/branches/2.13/src/ZPublisher/HTTPRequest.py  2011-07-29
 19:11:59 UTC (rev 122428) +++
 Zope/branches/2.13/src/ZPublisher/HTTPRequest.py  2011-07-30 02:36:10
 UTC (rev 122429) @@ -1296,7 +1290,7 @@ if n: n = n - 1 if len(path) 
 n: -raise KeyError, key +
 return default
 
 v = self._script + path[:n] else:

If such a chenge is deemed to be backward compatible (I can't figure it
out from here) then it needs both a new test (or updates to the test
which asserted the old behavior) and a note in CHANGES.txt.


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/

iEYEARECAAYFAk423MAACgkQ+gerLs4ltQ63aQCeOO9RRa8qJrScQFj7EkxfawP2
jd8An1C8FOW9K7MWUBsBVMcmup1C6n/c
=ppJj
-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 )

Re: [Zope-dev] SVN: Zope/branches/2.13/src/ micro optimization

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/01/2011 02:25 AM, Nikolay Kim wrote:
 Log message for revision 122433: micro optimization
 
 Changed: U   Zope/branches/2.13/src/OFS/ObjectManager.py U
 Zope/branches/2.13/src/OFS/Traversable.py U
 Zope/branches/2.13/src/Products/PageTemplates/Expressions.py U
 Zope/branches/2.13/src/ZPublisher/HTTPRequest.py
 
 -=- Modified: Zope/branches/2.13/src/OFS/ObjectManager.py 
 === 
 --- Zope/branches/2.13/src/OFS/ObjectManager.py   2011-07-30 11:49:07
 UTC (rev 122432) +++ Zope/branches/2.13/src/OFS/ObjectManager.py
 2011-08-01 06:25:44 UTC (rev 122433) @@ -425,7 +425,7 @@ # Returns a
 list of actual subobjects of the current object. # If 'spec' is
 specified, returns only objects whose meta_type # match 'spec'. -
 return [ self._getOb(id) for id in self.objectIds(spec) ] +
 return [ getattr(self, id) for id in self.objectIds(spec) ]
 
 security.declareProtected(access_contents_information,
 'objectItems') def objectItems(self, spec=None):

You cannot replace '_getOb' with 'getattr':  subclasses (e.g.,
BTreeFolder) don't necessarily use attributes to store items.  Even if
all the subclasses in the Zope tree also override the affected methods,
you cannot know that third-party code won't break here.


 @@ -763,7 +763,7 @@ return self.manage_delObjects(ids=[name])
 
 def __getitem__(self, key): -v=self._getOb(key, None) +
 v=getattr(self, key, None) if v is not None: return v if
 hasattr(self, 'REQUEST'): request=self.REQUEST

Same here.

 Modified:
 Zope/branches/2.13/src/Products/PageTemplates/Expressions.py 
 === 
 --- Zope/branches/2.13/src/Products/PageTemplates/Expressions.py
 2011-07-30 11:49:07 UTC (rev 122432) +++
 Zope/branches/2.13/src/Products/PageTemplates/Expressions.py
 2011-08-01 06:25:44 UTC (rev 122433) @@ -71,7 +71,7 @@ while
 path_items: name = path_items.pop() if
 OFS.interfaces.ITraversable.providedBy(object): -object =
 object.restrictedTraverse(name) +object =
 object.unrestrictedTraverse(name, restricted=True) else: object =
 traversePathElement(object, name, path_items, request=request)

This change defeats a security check:  I don't believe it is suitable
for a stable release (one might argue for such a change on the trunk,
but it is *not* an optimization).


 Modified: Zope/branches/2.13/src/ZPublisher/HTTPRequest.py 
 === 
 --- Zope/branches/2.13/src/ZPublisher/HTTPRequest.py  2011-07-30
 11:49:07 UTC (rev 122432) +++
 Zope/branches/2.13/src/ZPublisher/HTTPRequest.py  2011-08-01 06:25:44
 UTC (rev 122433) @@ -169,6 +169,9 @@
 
 retry_max_count = 3
 
 +def __conform__(self, iface): +return
 iface.__adapt__(self) + def supports_retry(self): if self.retry_count
  self.retry_max_count: time.sleep(random.uniform(0, 2 **
 (self.retry_count)))

'__conform__' is intended to allow an object to do something different
than the standard adapation:  it makes no sense (and cannot be faster,
since it introduces another Python function call) to add a '__conform__'
which returns exactly what the code in 'Interface.__call__' would do.


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/

iEYEARECAAYFAk4231AACgkQ+gerLs4ltQ4xygCeLTa8LWRPlKuzhmxQBq4vkS5u
9RkAn3K7LXdDQ1Z5/HNIzjp9tK9a8NhB
=1X2t
-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 )

Re: [Zope-dev] SVN: Zope/trunk/ Optimized the `OFS.Traversable.getPhysicalPath` method to avoid excessive amounts of method calls. Thx to Nikolay Kim from Enfold

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/14/2011 04:16 AM, Hanno Schlichting wrote:
 Log message for revision 122213: Optimized the
 `OFS.Traversable.getPhysicalPath` method to avoid excessive amounts
 of method calls. Thx to Nikolay Kim from Enfold
 
 
 Changed: U   Zope/trunk/doc/CHANGES.rst U
 Zope/trunk/src/OFS/Traversable.py
 
 -=- Modified: Zope/trunk/doc/CHANGES.rst 
 === 
 --- Zope/trunk/doc/CHANGES.rst2011-07-14 07:16:04 UTC (rev 122212) 
 +++ Zope/trunk/doc/CHANGES.rst2011-07-14 08:16:08 UTC (rev 122213) 
 @@ -19,6 +19,9 @@ Features Added ++
 
 +- Optimized the `OFS.Traversable.getPhysicalPath` method to avoid
 excessive +  amounts of method calls. + - During startup open a
 connection to every configured database, to ensure all of them can
 indeed be accessed. This avoids surprises during runtime when 
 traversal to some database mountpoint could fail as the underlying
 storage
 
 Modified: Zope/trunk/src/OFS/Traversable.py 
 === 
 --- Zope/trunk/src/OFS/Traversable.py 2011-07-14 07:16:04 UTC (rev
 122212) +++ Zope/trunk/src/OFS/Traversable.py 2011-07-14 08:16:08 UTC
 (rev 122213) @@ -114,14 +114,47 @@ access this object again later,
 for example in a copy/paste operation. getPhysicalRoot() and
 getPhysicalPath() are designed to operate together. + +This
 implementation is optimized to avoid excessive amounts of function +
 calls while walking up from an object on a deep level.  -
 path = (self.getId(),) +try: +id = self.id +
 except AttributeError: +id = self.getId() +else: 
 +if id is None: +id = self.getId()
 
 p = aq_parent(aq_inner(self)) +if p is None: +
 return (id, )
 
 -if p is not None: -path = p.getPhysicalPath() +
 path +path = [id] +func =
 self.getPhysicalPath.im_func +while p is not None: +
 if func is p.getPhysicalPath.im_func: +try: +
 pid = p.id +except AttributeError: +
 pid = p.getId() +else: +if pid is
 None: +pid = p.getId()
 
 +path.insert(0, pid) +try: +
 p = p.__parent__ +except AttributeError: +
 p = None +else: +if
 IApplication.providedBy(p): +path.insert(0, '') +
 path = tuple(path) +else: +path =
 p.getPhysicalPath() + tuple(path) +break + return
 path
 
 security.declarePrivate('unrestrictedTraverse')

While we're at it, 'list.insert(0,foo)' is known to be slower in a tight
loop than 'list.append(foo)', with a 'reversed' at the end of the loop::

 $ python -m timeit -s from string import letters path = [] \
for  letter in letters: path.append(letter) \
result = tuple(reversed(path))
 10 loops, best of 3: 15.9 usec per loop

 $ python -m timeit -s from string import letters path = [] \
   for letter in letters: path.insert(0, letter) \
   result = tuple(path)
 1 loops, best of 3:  25.3 usec per loop


For the sake of comparison, the original tuple addition is actually
between the two:

 $ python -m timeit -s from string import letters result = () \
   for letter in letters: result += (letter,)
 1 loops, best of 3: 21.6 usec per loop



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/

iEYEARECAAYFAk4fD4gACgkQ+gerLs4ltQ7b3QCg1z+oZKKDZ5IhuMvAockJ9mvx
SO4AoIr3IEMnq78m70DZAOc0yV9+++y4
=8vOY
-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 )

Re: [Zope-dev] SVN: Zope/trunk/ Optimized the `OFS.Traversable.getPhysicalPath` method to avoid excessive amounts of method calls. Thx to Nikolay Kim from Enfold

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/14/2011 11:47 AM, Tres Seaver wrote:

 While we're at it, 'list.insert(0,foo)' is known to be slower in a
 tight loop than 'list.append(foo)', with a 'reversed' at the end of
 the loop::
 
 $ python -m timeit -s from string import letters path = [] \ for
 letter in letters: path.append(letter) \ result =
 tuple(reversed(path)) 10 loops, best of 3: 15.9 usec per loop
 
 $ python -m timeit -s from string import letters path = [] \ for
 letter in letters: path.insert(0, letter) \ result = tuple(path) 
 1 loops, best of 3:  25.3 usec per loop
 
 
 For the sake of comparison, the original tuple addition is actually 
 between the two:
 
 $ python -m timeit -s from string import letters result = () \ 
 for letter in letters: result += (letter,) 1 loops, best of 3:
 21.6 usec per loop

A further micro-optimization is to pre-allocate a big list in a thread
local.  Running the attached script produces::

 $ python perftest.py
 Via insert_0: 24.8401839733
 Via append: 15.6596238613
   speedup: 37.0%
 Via tuple_add: 21.9555268288
   speedup: 11.6%
 Via prealloc: 10.5278339386
   speedup: 57.6%



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/

iEYEARECAAYFAk4fIVAACgkQ+gerLs4ltQ6BlACguSHcHLWGjVIVJlQYIpL42RNc
mqMAn1Y16tyVmUkxd2ipNrZSeZpSFVEA
=oJJY
-END PGP SIGNATURE-


perftest.py
Description: application/httpd-cgi
___
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] Tag BASE without port number

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/13/2011 08:37 AM, Jaroslav Lukesh wrote:
 Hi all,
 
 is it possible to hide port bumber in case of reverse proxy
 redirecting? I have POUND as reverse proxy and Zope 2.10.13 on port
 930, but html BASE tag contain this port number, which I does not
 want to have there.
 
 I do not want to explicit specify base tag at all pages.
 
 I prepare new installation, but I cannot remember nor find what I was
 make before at my old installation, it is 5 years ago. Google does
 not help me.

Configure pound to rewrite onto a Virtual Host Monster URL, which will
make all the URLs generated by Zope code match the public URL space.
See http://docs.zope.org/zope2/zope2book/VirtualHosting.html


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/

iEYEARECAAYFAk4duecACgkQ+gerLs4ltQ4B9QCguS04sQPrWnZ045l5+zs27TJm
BJMAn3Kr6LlztG7r+EWnD1uHnQUp4NzI
=ZYA7
-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-dev] direction

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/07/2011 03:24 AM, Shane Hathaway wrote:
 On 07/06/2011 10:59 AM, Hanno Schlichting wrote:
 The ZMI is a highly insecure, completely outdated and
 user-unfriendly interface.
 
 As I read this, I got an idea for a possible way forward.  I haven't
  been reading zope-dev much lately, so forgive me if something like
 this has been mentioned already.
 
 What if we had decorators that let us disable old code by default,
 yet allowed users to enable the old code with configuration?
 Something like this:
 
 
 import zope.oldcode
 
 class SomeClass(SimpleObject):
 
 @zope.oldcode.zmi def manage_edit(self, REQUEST): # ...
 
 
 The idea here is we'll create a zope.oldcode egg and fill it with 
 decorators for pervasive features of Zope that need to be removed
 over time, such as the current ZMI.  We'll also create a
 configuration switch for each of those old features so that people
 can keep using them for a reasonable period of time.  When the zmi
 feature is disabled, the code above will replace the manage_edit
 method with a zope.oldcode.Disabled object that raises a helpful
 exception if anyone tries to call it.
 
 It would also be good to make these decorators implement __nonzero__
 to allow conditional attribute definition:
 
 if zope.oldcode.zmi: manage_properties = (...)
 
 I would want to make sure conditional tests are possible as well:
 
 @zope.oldcode.zmi def test_manage_edit(self): # ...
 
 (The zope.oldcode package probably ought to enable all old features
 by default when running tests.)
 
 What do you think?

Neat -- sounds like an interesting thing to try a spike on, anyway.



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/

iEYEARECAAYFAk4WLuwACgkQ+gerLs4ltQ46IgCgivBo8ucn91ix8YlsYknNG7HB
+fcAn2wyEQoKNNpZ+yv5OXHi9vKmtiHh
=Dm5a
-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 )

Re: [Zope] about the leakage in Shared.DC.ZRDB.Results.Results

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/03/2011 12:54 PM, Fernando Martins wrote:
 Regarding the leakage in Shared.DC.ZRDB.Results.Results mentioned
 in:
 
 https://mail.zope.org/pipermail/zope/2011-January/176106.html
 
 which might very well be the leakage introduced in 2.10 that made
 ZSQL methods useless, what are the chances of being solved?
 
 I see that Tres Seaver made a new package, SQL Adaptor (not useful to
  me) because of this bug. Is it an indication the bug is too hard to
 fix?

The leakage occurs due to a feature (caseless column aliases) which
would break backward compatibiltiy if removed.  If you can live without
that feature (your app already uses the column names spelled the same
way as the RDBMS returns them, or you can change it to do so), you
should be able to apply the attached patch to remove the leaking feature.



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/

iEYEARECAAYFAk4R3DEACgkQ+gerLs4ltQ4gjQCglmXM907m+ysUeVyUnOHo0+sO
jUgAoJ7VWMc8XCmTQgzZ9nL8OxbZJkAO
=QTY8
-END PGP SIGNATURE-
=== modified file 'lib/python/Shared/DC/ZRDB/Results.py'
--- lib/python/Shared/DC/ZRDB/Results.py	2005-11-18 14:39:19 +
+++ lib/python/Shared/DC/ZRDB/Results.py	2011-01-27 16:09:13 +
@@ -38,7 +38,6 @@
 self._names=names=[]
 self._schema=schema={}
 self._data_dictionary=dd={}
-aliases=[]
 if zbrains is None: zbrains=NoBrains
 i=0
 for item in items:
@@ -49,10 +48,6 @@
 if schema.has_key(name):
 raise ValueError, 'Duplicate column name, %s' % name
 schema[name]=i
-n=name.lower()
-if n != name: aliases.append((n, SQLAlias(name)))
-n=name.upper()
-if n != name: aliases.append((n, SQLAlias(name)))
 dd[name]=item
 names.append(name)
 i=i+1
@@ -70,11 +65,6 @@
 if k[:2]=='__':
 setattr(r,k,getattr(Record,k))
 
-# Add SQL Aliases
-for k, v in aliases:
-if not hasattr(r, k):
-setattr(r, k, v)
-
 if hasattr(brains, '__init__'):
 binit=brains.__init__
 if hasattr(binit,'im_func'): binit=binit.im_func

___
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-dev] zope-tests - OK: 82, UNKNOWN: 6

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13_win-py2.7
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044722.html
 
 
 [2]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.5
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044725.html
 
 
 [3]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1_win-py2.5
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044728.html
 
 
 [4]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1_win-py2.6
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044729.html
 
 
 [5]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.5
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044730.html
 
 
 [6]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.6
 slave-win 
 https://mail.zope.org/pipermail/zope-tests/2011-July/044731.html

These are all directory not empty errors in the 'svn' step.


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/

iEYEARECAAYFAk4PQQcACgkQ+gerLs4ltQ6ZtwCg20WiVaq916XINegiZ4bU24yB
se8AoLx+8O1QTwUztZuQr8k2ntEKuhQz
=n4DE
-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 )

Re: [Zope-dev] zope-tests - FAILED: 1, OK: 85

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2011-June/044495.html

Two errors:

- - In ZEO.tests.testZEO.test_server_status:

   File
c:\buildslave\zodb_dev_py_265_win64\build\src\ZEO\zrpc\connection.py,
line 783, in wait
raise DisconnectedError()
DisconnectedError

  while trying 'db = ZEO.DB(addr)'

- - Plus a tearDown error for the same test:

   WindowsError: [Error 145] The directory is not empty:
'c:\\buildslave\\ZODB_dev_py_265_win64\\build\\parts\\test\\tmp\\testgoe6dv'


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/

iEYEARECAAYFAk4Mh1wACgkQ+gerLs4ltQ67FgCfRefvwCStAQAiT9d1Fl0lbh2Y
SyMAn11HX1dlyosK1SQYJn1+jGMwsqi3
=P6+8
-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 )

Re: [Zope-dev] zope-tests - OK: 85, UNKNOWN: 1

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-June/044329.html

exceptions.WindowsError: [Error 145] The directory is not empty:
'C:\\Users\\richard\\Desktop\\buildslave\\zope2.13_win-py2.6_slave-win\\build\\src\\Products\\Sessions\\.svn'
]

- -- 
===
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/

iEYEARECAAYFAk4Jyj4ACgkQ+gerLs4ltQ4f8gCeNV/G2LmcHJ4ikhu/j6hP7vsF
hNYAoLSVtJJNXhwxP2p+hyIn6R79USJV
=TOMj
-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 )

Re: [Zope-dev] zope-tests - FAILED: 4, OK: 86, UNKNOWN: 1

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/27/2011 07:42 AM, Lennart Regebro wrote:
 Will not having open bug reports as a fail again turn the buildbots
 red again, and hence return the overview to uselessness?

The buildbots don't turn red for these once-per-week quasi-failure reports:

 [1]FAILED  Repository policy check found errors in 305 projects
   https://mail.zope.org/pipermail/zope-tests/2011-June/044221.html


 [2]FAILED  Total languishing bugs for zope: 59
   https://mail.zope.org/pipermail/zope-tests/2011-June/044218.html


 [3]FAILED  Total languishing bugs for zopeapp: 2
   https://mail.zope.org/pipermail/zope-tests/2011-June/044216.html


 [4]FAILED  Total languishing bugs for zopetoolkit: 200
   https://mail.zope.org/pipermail/zope-tests/2011-June/044217.html




 [5]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13_win-py2.6 slave-win
   https://mail.zope.org/pipermail/zope-tests/2011-June/044243.html

This is a particularly useless error in the 'svn' phase:  Failure:
exceptions.WindowsError is all that prints.



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/

iEYEARECAAYFAk4IhXwACgkQ+gerLs4ltQ463wCg3Bb1XoyQzYja4iZJeVrzkYVe
IXIAnjQKYPH4MbgSiUNOSfI/dEmsBdOQ
=S9Wv
-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 )

Re: [Zope-dev] weird intermittent error with apache2 and mod_wsgi

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/27/2011 11:36 AM, Chris Withers wrote:
 RuntimeError: class.__dict__ not 
 accessible in restricted mode


Let me google that for you:

- - http://mail.zope.org/pipermail/zodb-dev/2009-June/012607.html

- -
http://mediacore.com/blog/hosting-multiple-wsgi-applications-with-apache/

- - http://trac.edgewall.org/ticket/3371


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/

iEYEARECAAYFAk4IsFoACgkQ+gerLs4ltQ5VIwCgsoZ7ujvlOsZ+U+YAiPushoyF
Dm4AniLcNiyWrbPuIHOpS8zNmAW0B2lZ
=4gYU
-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 )

Re: [Zope] ZSQL not shown in list to add new method

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/27/2011 12:49 PM, c k wrote:
 Now i installed zope2 2.13.7 and just added products.zsqlmethods in
 buildout.cfg and also added entry as products.sqlmethods = 2.13.3 in
 versions.cfg.
 Then run the buildout and mkzopeinstance.
 After instance is created, checked to add new zsql method.
 But still there is no option to add it.
 Also checked the egg file and it is compiled and buildout has ot shown any
 error for zsql.
 What's going wrong?

Are you including the ZCML for Products.ZSQLMethods in your buildout.cfg
instance section?


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/

iEYEARECAAYFAk4Izm8ACgkQ+gerLs4ltQ4cZQCfVikIOmxqACvKOjwRNULkm3mw
o7kAn0K0oyihIx5OQNCDte6EQobiS+1s
=IEoh
-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] ZSQL not shown in list to add new method

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/27/2011 02:39 PM, Tres Seaver wrote:
 On 06/27/2011 12:49 PM, c k wrote:
 Now i installed zope2 2.13.7 and just added products.zsqlmethods in
 buildout.cfg and also added entry as products.sqlmethods = 2.13.3 in
 versions.cfg.
 Then run the buildout and mkzopeinstance.
 After instance is created, checked to add new zsql method.
 But still there is no option to add it.
 Also checked the egg file and it is compiled and buildout has ot shown any
 error for zsql.
 What's going wrong?
 
 Are you including the ZCML for Products.ZSQLMethods in your buildout.cfg
 instance section?

FWIW, I just did the following::

-  % ---
$ /opt/Python-2.6.5/bin/virtualenv --no-site-package /tmp/zsql
...
$ /tmp/zsql/bin/easy_install Zope==2.13.7 Products.ZSQLMethods==2.13.3
...
$ /tmp/zsql/bin/mkzopeinstance -d /tmp/zsqlinst
...
$ /tmp/zsqlinst/zopectl fg
-  % ---

and was able to add ZSQL methods TTW in the ZMI.



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/

iEYEARECAAYFAk4I0CIACgkQ+gerLs4ltQ6AeACglTsnRwkY/8LjTL4mEvwNgoZw
MZcAnRi4Ww47JVDLLYrk+viy2kWlDKxS
=3bpR
-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-dev] zope-tests - OK: 84, UNKNOWN: 2

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-June/044176.html
 
 
 [2]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-June/044183.html

The links for both runs return 404s.


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/

iEYEARECAAYFAk4HMw8ACgkQ+gerLs4ltQ7AzwCfeIInEUFUZXFAlsEWx/pRWX5i
jDUAoNwzFtA9bksjum3HcXrfoVYKcclA
=f1vr
-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 )

Re: [Zope-dev] zope-tests - FAILED: 1, OK: 62

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope Buildbot / zopetoolkit_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-June/044045.html

Proxy error on the buildout page: DNS lookup failure for:
tha209.thehealthagency.com.


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/

iEYEARECAAYFAk4Eqs4ACgkQ+gerLs4ltQ5Z3ACgrlvpgLla8i0AYFaqkcI7jLx3
ALEAoK+wrEzrSfLqQ9TQpkGcf4B7PfC5
=fhGe
-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 )

Re: [Zope] CMF -?- Zope

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/23/2011 01:52 PM, Eric d'Halibut wrote:
 On 6/23/11, Tres Seaver tsea...@palladion.com wrote:
 
 Unpack the CMFCore sdist tarball, e.g.:

  $ cd /tmp
  $ wget \

 http://pypi.python.org/packages/source/P/Products.CMFCore/Products.CMFCore-2.2.4.tar.gz
  $ cd /usr/local
  $ sudo tar xzf /tmp/Products.CMFCore-2.2.4.tar.gz

 and then add the unpacked directory to the 'products' section of your
 instance's 'zope.conf', e.g.:

  $ grep ^products /usr/local/Zopeish/etc/zope.conf
  products /usr/local/Products.CMFCore-2.2.4/
 
 No joy. Thanks. I am giving up on my NetBSD, and, when I get some time
 later today, redo all this on a linux box.

FTR, my original example was wrong.  It should have been:

 $ grep ^products /usr/local/Zopeish/etc/zope.conf
 products /usr/local/Products.CMFCore-2.2.4/Products/

and CMFCore requires that 'five.localsitemanager' be importable
(buildout and easy_install would have guaranteed that).


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/

iEYEARECAAYFAk4ErkUACgkQ+gerLs4ltQ5vfgCcDtYcvj7oPzoW1jreBPawtIxh
CQsAoKD3w22NQK26MxEYfp1FSBDO+QFZ
=J4w0
-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] CMF -?- Zope

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/23/2011 12:48 AM, Eric d'Halibut wrote:
 I am a straggler returning to Zope after years away from it. I come
 from a time when to install a product into one's Zope one simply
 untarred it into one's Products folder and restarted. Now I am looking
 at easy_install, buildout, and the new mania for eggs. Imagine my
 discomfiture.
 
 But never mind all that. I now have a running instance of Zope 2.12.10
 installed in NetBSD 5.1. I want to install CMF into it, which used to
 be one's first product chore (almost) since plone depended on it and I
 was heading for a plone install, (and later on ran Silva for a couple
 of years.) But I am here tonight to say, I am stumped.
 
 How do get CMFCore into my zope instance the right way? Can someone
 lay out the steps for me?
 
 My python is: /usr/pkg/bin/python2.6
 
 My Zope is at: /usr/local/src/Zope2-2.12.10
 
 My instance is at: /usr/local/Zopeish

Unpack the CMFCore sdist tarball, e.g.:

 $ cd /tmp
 $ wget \

http://pypi.python.org/packages/source/P/Products.CMFCore/Products.CMFCore-2.2.4.tar.gz
 $ cd /usr/local
 $ sudo tar xzf /tmp/Products.CMFCore-2.2.4.tar.gz

and then add the unpacked directory to the 'products' section of your
instance's 'zope.conf', e.g.:

 $ grep ^products /usr/local/Zopeish/etc/zope.conf
 products /usr/local/Products.CMFCore-2.2.4/

You can repeat the 'products' bit to add other products.

 I have banged around with easy_install, which writes things into my
 NetBSD /usr/pkg hierarchy, of which I very much disapprove.

I recommend using 'virtualenv', which gives you a sandboxed
environment for installing non-system packages.

 Buildout
 seems always to want to build the original gazillion (not
 complaining!) Zope packages every time I ry to use it.
 
 So...glad to be back. Need help. Will write if I get work. Wish you were here.
 
 nb. The running Zope instance is live on the net, so if one needs to
 examine my ZMI I can provide URL and login. Just ask, please.



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/

iEYEARECAAYFAk4DUSUACgkQ+gerLs4ltQ4J+ACeIV6Pph5BZ4b6nrU2jNIsRJ7T
caUAmQHVIDaboFyFVv3TllFoXABMDgWr
=vAra
-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-dev] zope-tests - FAILED: 7, OK: 65

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [5]FAILED  Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx
https://mail.zope.org/pipermail/zope-tests/2011-June/043761.html

I can't get to the buildbot page due to a 503:

  Reason: DNS lookup failure for: tha209.thehealthagency.com



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/

iEYEARECAAYFAk3/VNMACgkQ+gerLs4ltQ63cwCeLjApCzrqKhFPUf9UDGwg6K2T
9kQAn3g8WVxDVa8bQA9TPn3pNXmHJFDn
=IaC9
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 63

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope 3.4 KGS / Python2.5.5 64bit linux
https://mail.zope.org/pipermail/zope-tests/2011-June/043657.html

This one is a timeout in the 'buildout' step::

-  % -
 Develop: '/home/ccomb/kgs3.4-slave/Python2.5.5-64bit-linux/build/.'
Updating test.

command timed out: 1200 seconds without output, killing pid 28277
process killed by signal 9
-  % -

 [9]FAILED  winbot / ztk_10 py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-June/043695.html

This is the same obnoxious doctest-driving-the-testrunner issue which
makes my eyeballs bleed when it (sporadically) fails::

-  % -
File
c:\eggs\zope.testing-3.9.6-py2.5.egg\zope\testing\testrunner\testrunner-layers-buff.txt,
line 131, in testrunner-layers-buff.txt
Failed example:
for line, time in record:
if time-last_time = pause:
# We paused!
print 'PAUSE FOUND BETWEEN THIS OUTPUT:'
print '\n'.join([last_line, line, '-'*70])
last_line, last_time = line, time
# doctest: +ELLIPSIS
Expected:
PAUSE FOUND BETWEEN THIS OUTPUT:...
.
.
--
PAUSE FOUND BETWEEN THIS OUTPUT:
.
 LAYER FINISHED
--
Got:
PAUSE FOUND BETWEEN THIS OUTPUT:
.
.
--
PAUSE FOUND BETWEEN THIS OUTPUT:
.
]
BLANKLINE
--
-  % -


- -- 
===
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/

iEYEARECAAYFAk39+WQACgkQ+gerLs4ltQ7CPACgtUXJ82Jxj+duwvOs2TnIcJ1Z
tbMAnR0Tnfr8cSUBGKvcy0hWcJcAch0t
=zr2x
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32
https://mail.zope.org/pipermail/zope-tests/2011-June/043603.html


This is a weird one:  I have no idea why it would show up now::

- --- % 
Error in test testMKDLIST (zope.server.ftp.tests.test_ftpserver.Tests)
Traceback (most recent call last):
  File /usr/lib/python2.6/unittest.py, line 289, in run
self.tearDown()
  File
/home/zope/.buildout/eggs/zope.server-3.8.4-py2.6.egg/zope/server/ftp/tests/test_ftpserver.py,
line 106, in tearDown
self.fail('Leaked a socket: %s' % `asyncore.socket_map`)
  File /usr/lib/python2.6/unittest.py, line 317, in fail
raise self.failureException, msg
AssertionError: Leaked a socket: {6:
zope.server.ftp.server.PassiveListener listening 127.0.0.1:0 at
0x91eca4c, 9: select-trigger (pipe) at 91e106c}
- --- % 



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/

iEYEARECAAYFAk38uMwACgkQ+gerLs4ltQ57FACfUGieICFh+ztc4+kq62ekPEgT
9ZEAn3Olg1CaCV49MVydfeKoMKbTTImx
=vJ3I
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 105

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope Buildbot / zope2.13-py2.6 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/043391.html

Network failure during bootstrap.

 [2]FAILED  Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/043390.html

Ditto.


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/

iEYEARECAAYFAk36GJYACgkQ+gerLs4ltQ4u2ACeLh8Mwt+NRAUhwjWkq4T5ZO+g
c1QAn0wQdHJN/lh+SHGLFgyP9M8ozOta
=a4ow
-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 )

Re: [Zope-dev] zope-tests - FAILED: 12, OK: 53

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/13/2011 01:00 AM, Zope tests summarizer wrote:

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

This fails (wihtout much other information) trying to download
'ClientForm==0.2.10':

-  % --
Getting distribution for 'ClientForm==0.2.10'.
While:
  Installing test.
  Getting distribution for 'ClientForm==0.2.10'.
Error: Couldn't find a distribution for 'ClientForm==0.2.10'.
-  % --

Which looks like a bogus error to me, given that the egg has been
released to PyPI since 2008-12-03:

  http://pypi.python.org/pypi/ClientForm


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/

iEYEARECAAYFAk319xQACgkQ+gerLs4ltQ7gFQCgv3nfxqP0ryEqBCcBoVBEg1iY
yRQAni+MMJX4mmPGGzEOWcCp1fEXktam
=Tmh2
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope 3.4 KGS / Python2.5.5 64bit linux
https://mail.zope.org/pipermail/zope-tests/2011-June/043112.html

A presumably transient failure in downloading the setuptools egg.


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/

iEYEARECAAYFAk30wnEACgkQ+gerLs4ltQ4bzwCgiqUzotTzleSkpSp6IvWsvp6e
/y4An3vyimFpcVROM23xDG3S3smJ4ego
=xXDn
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/11/2011 11:36 AM, Hanno Schlichting wrote:
 On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting ha...@hannosch.eu wrote:
 $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit
 Running zope.testrunner.layer.UnitTests tests:
  Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
 Segmentation fault

 I haven't yet tried to debug the problem itself.
 
 I took the time to investigate this. It came down to the same issue
 noted in https://bugs.launchpad.net/bugs/675064. Some code treated a C
 int as a pointer. Apparently on most platforms sizeof(int) ==
 sizeof(pointer), but there's some where that's not the case.
 
 In this particular case it was a simple mistake of using the wrong variable:
 
 PyObject *expl=0;
 int explicit=1;
 
 UNLESS (PyArg_ParseTupleAndKeywords(
  args, kw, O|i, acquire_args+1,
  name, filter, extra, explicit, defalt, containment
  ))
 return NULL;
 
 if (expl) explicit=PyObject_IsTrue(expl);
 
 The fix was to pass expl instead of explicit into
 PyArg_ParseTupleAndKeywords. Almost the same code existed in
 Wrapper_acquire_method and module_aq_acquire and only
 Wrapper_acquire_method got it wrong.
 
 I released a new Acquisition version and put it into Zope 2.x.
 Hopefully the buildbots will finally get green again.

Excellent!  Thanks very much for tracking the beast to its lair and
aq_wrenching of its arm (now we just need to watch out for its mother ;)


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/

iEYEARECAAYFAk3zjhIACgkQ+gerLs4ltQ5KSgCgqGXWqmpqbPJiolsWjLY9nGmM
xyUAoIZBc5acuHPzpiY/WV9wqtOYX0l1
=wIQ8
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [8]FAILED  winbot / ztk_10 py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-June/042814.html

Network timeout in bootstrap, trying to find the zc.buildout egg.


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/

iEYEARECAAYFAk3vffIACgkQ+gerLs4ltQ5zogCgjFq5/mj7eI506TfbojNurEMM
7+4Amwf66UlniwdDLbwCRyHmmWiirEa1
=Dqow
-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 )

Re: [Zope-dev] Reg. persisting data in ZODB via forms

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/08/2011 01:40 PM, Marius Gedminas wrote:
 On Wed, Jun 08, 2011 at 06:20:26PM +0530, Joe Steeve wrote:
 As I mentioned on a follow-up post, we figured the 'Persistent' part. :)

 On Wed, 2011-06-08 at 13:29 +0100, Laurence Rowe wrote:
 My guess is that the ObjectModifiedEvent is dispatched to your
 object's parent and causes something to change there, with the side
 effect of storing your updated object.

 Even if the object's parent (a btree-container) had changed, will it
 attempt to force-store its entire child-tree? I am trying to imagine the
 effect of it on a huge tree.
 
 The smallest unit that is ever written to a ZODB is one persistent object
 (with all its nonpersistent attributes/items, recursively).
 
 BTrees use multiple persistent buckets for their state and are very
 efficient, storage-wise.  But this only matters when you're
 adding/removing items to a BTree.  If you're modifying a persistent
 object stored in a BTree, the BTree itself remains unmodified and does
 not need to be re-written 

Likewise, if you modify a non-persistent attribute of a persistent
object which also has some attributes which are themselves persistent,
only that object is re-written.



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/

iEYEARECAAYFAk3vtXcACgkQ+gerLs4ltQ6fMQCfcdevBmf4yA3HBnZal/8map5h
q2sAnj7acU3CjN2DACvCA2Ij213VvW/k
=w9IP
-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 )

Re: [Zope-dev] zope-tests - FAILED: 13, OK: 81

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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

Timeout while running 'virtualenv' (PyPI or peak.telecommunity.com down?)


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

Ditto.


 [3]FAILED  Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042703.html
 
 
 [4]FAILED  Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042705.html

I'm seeing a 503 on these two, so I can't check the output, but I'm
assuming this is the same segfault we have been seeing.


 [5]FAILED  winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2011-June/042677.html

Looks like PyPI is down here, too.


 [13]   FAILED  winbot / zope.cachedescriptors_py_265_32
https://mail.zope.org/pipermail/zope-tests/2011-June/042690.html

Ditto.



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/

iEYEARECAAYFAk3uKO8ACgkQ+gerLs4ltQ5PQQCfSgb+0lACY5hGyruVtYdAlHnD
1DMAn0N1eqJYuUft7YlpbDxQOeURju6F
=ECUr
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/05/2011 02:24 PM, Hanno Schlichting wrote:
 On Sun, Jun 5, 2011 at 6:31 PM, Tres Seaver tsea...@palladion.com wrote:
 [1]FAILED  Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html


 [2]FAILED  Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html

 These two are both the segfault-at-exit issue.
 
 I finally took the time to install me a virtual machine with Ubuntu
 64bit on it. And I was able to reproduce the issue!
 
 It's not a segfault at exit, but actually happens inside a test:
 
 test_interfaces (Acquisition.tests) (0.001 s)
 test_mixed_explicit_and_explicit (Acquisition.tests)Segmentation fault
 
 Or to get the issue quicker:
 
 $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit
 Running zope.testrunner.layer.UnitTests tests:
   Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
 Segmentation fault
 
 I haven't yet tried to debug the problem itself.

I cannot reproduce on my native Ubuntu x86_64 machine using a
built-from-scratch Python 2.7.1::

- -- % -
$ uname -a
Linux xxx.example.com 2.6.32-31-server #61-Ubuntu SMP Fri Apr 8 19:44:42
UTC 2011 x86_64 GNU/Linux
$ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Z2
...
$ cd Z2
$ /opt/Python-2.7.1/bin/python bootstrap.py  bin/buildout
...
$ bin/alltests
...
Running OFS.tests.testCopySupportEvents.EventLayer tests:
  Set up OFS.tests.testCopySupportEvents.EventLayer in 0.094 seconds.
  Ran 14 tests with 0 failures and 0 errors in 0.042 seconds.
Running OFS.tests.testCopySupportHooks.HookLayer tests:
  Tear down OFS.tests.testCopySupportEvents.EventLayer in 0.000 seconds.
  Set up OFS.tests.testCopySupportHooks.HookLayer in 0.094 seconds.
  Ran 14 tests with 0 failures and 0 errors in 0.044 seconds.
Running Testing.ZopeTestCase.layer.ZopeLite tests:
  Tear down OFS.tests.testCopySupportHooks.HookLayer in 0.000 seconds.
  Set up Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds.
  Ran 220 tests with 0 failures and 0 errors in 4.660 seconds.
Running Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer tests:
  Set up Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.002
seconds.
  Ran 18 tests with 0 failures and 0 errors in 0.027 seconds.
Running Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer
tests:
  Tear down Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.001
seconds.
  Set up Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer
in 0.001 seconds.
  Ran 2 tests with 0 failures and 0 errors in 0.005 seconds.
Running zope.testrunner.layer.UnitTests tests:
  Tear down
Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001
seconds.
  Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds.
  Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
  Ran 2492 tests with 0 failures and 0 errors in 44.382 seconds.
Tearing down left over layers:
  Tear down zope.testrunner.layer.UnitTests in 0.000 seconds.
Total: 2760 tests, 0 failures, 0 errors in 50.124 seconds.
- -- % -



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/

iEYEARECAAYFAk3s6LYACgkQ+gerLs4ltQ4+LQCgrb7gVVmL41An8qCaKO0Bhww+
RG0AoI39SQwpYLs3v0K3APkp0ovZt74d
=mtma
-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 )

Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 [1]FAILED  Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html
 
 
 [2]FAILED  Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html


These two are both the segfault-at-exit issue.



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/

iEYEARECAAYFAk3rr3oACgkQ+gerLs4ltQ7S5wCeOlLJiSalEwFi78KxTwdWYhBW
jHMAoIVtBwTjbGgVpAsA/oltZkYoOqDG
=qHVi
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/04/2011 01:00 AM, Zope tests summarizer wrote:
 This is the summary for test reports received on the 
 zope-tests list between 2011-06-02 00:00:00 UTC and 2011-06-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
 
 
Bluebream / Python2.4.6 64bit linux
Bluebream / Python2.5.5 64bit linux
Bluebream / Python2.6.5 64bit linux
ZTK 1.0 / Python2.4.6 Linux 64bit
ZTK 1.0 / Python2.5.5 Linux 64bit
ZTK 1.0 / Python2.6.5 Linux 64bit
ZTK 1.0dev / Python2.4.6 Linux 64bit
ZTK 1.0dev / Python2.5.5 Linux 64bit
ZTK 1.0dev / Python2.6.5 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 Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32
Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32
Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win
 [1]Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win
Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32
Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32
Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win
Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32
Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64
Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32
Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64
Zope Buildbot / zopetoolkit_win-py2.5 slave-win
Zope Buildbot / zopetoolkit_win-py2.6 slave-win
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 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.coverage_py_265_32
 [3]winbot / z3c.rml_py_265_32
 [4]winbot / zc_buildout_dev py_254_win32
 [5]winbot / zc_buildout_dev py_265_win32
 [6]winbot / zc_buildout_dev py_265_win64
 [7]winbot / zc_buildout_dev py_270_win32
 [8]winbot / zc_buildout_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
winbot / ztk_dev py_254_win32
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]FAILED  Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-June/042475.html

This is a failure in the bootstrap step:

-  % -
Downloading
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
error: The directory is not empty built-in function rmdir
c:\windows\temp\easy_install-6qiqjt\zc.buildout-1.4.4\build\lib\zc
Traceback (most recent call last):
  File bootstrap.py, line 121, in module
assert exitcode == 0
AssertionError
-  % -


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/

iEYEARECAAYFAk3qXKwACgkQ+gerLs4ltQ5a+ACgpftuJn7EMS5OoOYhDeBb+7Y8
36oAn2yet6onDEHxgUBJBN4ZNZYdQ31V
=iVj7
-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 )

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

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

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

This looks like a No space left on device error.


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/

iEYEARECAAYFAk3pKe4ACgkQ+gerLs4ltQ6IcACcDvXHhxzXDhF0rG2vWHlaRDqY
pu8AoNSNAs9TrUkNJf1JnmnmzTzme+CU
=p395
-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 )

Re: [Zope-CMF] GenericSetup backport

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/31/2011 10:05 AM, Godefroid Chapelle wrote:
 Le 31/05/11 15:36, Hanno Schlichting a écrit :
 My proposal is then the following : I would publish a
  Products.GenericSetup 1.4.6dev001 release from my backported branch to 
 PyPi.
 Sorry, but publishing dev releases is frowned upon on PyPi.
 
 The arguments against the proposal seem lighter and lighter.
 
 I begin to feel zope-dev like stop energy.

Godefroid, Hanno is pushing back on your desire to add features to
long-feature-frozen release branches:  that isn't stop energy, but
just our normal policy.  Please don't push to release an official
1.4.x or 1.5.x with such a change in it.

Folks who need stability have to be able to live with its costs:  if
they want your feature, they should be prepared to upgrade to get it.


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/

iEYEARECAAYFAk3lHTIACgkQ+gerLs4ltQ7RJwCgj4ONCJprO33UhZ6RaHda9aDd
4U4AoKdJ6R14fV5twnJrroMa0QNryv8o
=mXta
-END PGP SIGNATURE-

___
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