No commit message

dd Michael Dunstan's "explicit abort after error propagates into publisher" patch as documented in http://zope.org/Collectors/Zope/789 and as required by recent changes to ZODB which prevent a connection from being cleanly closed if modifications are extant in that connection.

(Merge from 2.7 branch)

via distutils to a relative path.

(corresponds with ZopeX3-3.0 branch revision 27434)

in HTTPRequest.keys() - it caches URLN and BASEN in other.

- synced interface and help file with implementation

from 'guarded_getattr'.

     - Collector #1267: applied patch to fix segmentation faults on 
       x86_64 systems

On a tip from Dieter, ensure that our hasattr replacement doesn't invoke __len__ on objects retrieved by getattr due to Python boolean magic!

I wish a miserable plague upon boolean magic that calls __len__ and the exception-hiding behavior of hasattr.

       corresponding output_encoding property of the ZReST instance. In addition
       changing the encodings through the Properties tab did not re-render 
       the HTML.

updated

       operations from the command line (through zopectl)

the logging module of Python

Collector #1441: Removed headers introduced to make Microsoft webfolders and office apps happy, since they make a lot of standards-compliant things unhappy AND they trick MS Office into trying to edit office files stored in Zope via WebDAV even when the user isn't allowed to edit them and is only trying to download them.

Collector #1445: Fixed bad interaction between -p and -v(v) options to test.py that resulted in exceptions being printed when they shouldn't have been.

No commit message

for a better and unique error handling