Hi all,
This morning I proposed on the plone.dev list to create a anon http
mirror of svn.zope.org and to include links to that in the plone
bundles. It is one of those perpetual proposals that turn up from time
to time buried at the tail end of mailinglist threads. "It would be nice
if...". So I started a separate thread for it to get it discussed for
real :-)
Wiggy rightfully suggested I'd ask it here first, as it would be
something that's best handled by svn.zope.org itself. I searched the
mailinglist a bit and it seemed that write access using https is out of
the question policy-wise, but that http anonymous access could happen.
plone's svn has a read-only mirror at google code now, perhaps that's a
good option for svn.zope.org, too?
So: will anon http svn access happen?
Reinout
--
Reinout van Rees r.van.rees @ zestsoftware.nl
http://vanrees.org/weblog/http://zestsoftware.nl/
"Military engineers build missiles. Civil engineers build targets."
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of Zope Corporation and the Zope community I am pleased to
announce the release of Zope 2.8.9.1. You can download the sources
from "http://www.zope.org/Products/Zope/2.8.9.1/",
http://www.zope.org/Products/Zope/2.8.9.1
This bugfix release corrects a problem introduced in 2.8.9, which
prevented starting Zope in "background" / "daemonized" mode.
New features of Zope 2.8.x
- ZODB 3.4 with MVCC (multi version concurrency control) support.
MVCC solves nearly every problem with ZODB read-conflict errors
which is very important for high-traffic Zope sites.
- Extension Classes were rewritten as Python new-style classes making
all features of Python new-style classes available in Zope
objects. This includes support for cyclic garbage collection.
- Integration of Zope 3 technologies through Five
(see http://codespeak.net/z3/five/)
More Information
For more information on what is new in this release, see the
CHANGES.txt files for the release:
"http://www.zope.org/Products/Zope/2.8.9.1/CHANGES.txt",
http://www.zope.org/Products/Zope/2.8.9.1/CHANGES.txt
See also:
"http://www.zope.org/Wikis/DevSite/Projects/Zope2.8/OverView"
http://www.zope.org/Wikis/DevSite/Projects/Zope2.8/OverView
For more information on the available Zope releases, guidance for
selecting the right distribution and installation instructions,
please see:
"http://www.plope.com/Books/2_7Edition/InstallingZope.stx",
http://www.plope.com/Books/2_7Edition/InstallingZope.stx
Reporting Bugs
Please report all the bugs you have found to the Zope bugtracker:
"http://collector.zope.org/Zope",
http://collector.zope.org/Zope
Supported Python versions
At this time the only **supported** and **recommended** Python
versions are 2.3.5 and 2.3.6.
Using Python 2.4.X is **not supported** and **not recommended** at
this time. Python 2.4.X will be supported when a security audit takes
place.
This means that you are using Python 2.4 + Zope 2.8 at **your own
risk**. This warning also applies to binary packages that install Zope
packages ogether with a system wide Python 2.4 installation (e.g.
Fedora, SuSE...).
Such installations are in general not supported. In addition there
some third-party products and Python packages that don't work with
Python 2.4 and can cause trouble when using Python 2.4.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGDCIL+gerLs4ltQ4RAjV8AJ4qc4gChSxhoDQC2E+l+5UbbTr2kgCgiDZf
f23x570Y4wNvsWcS55QZ8+o=
=CNr8
-----END PGP SIGNATURE-----
Looks like there is a bug in Zope 2.10.2 with OFS/Traversable.py on line
228:
if not ok:
if (container is not None or
guarded_getattr(obj, name, _marker)
is not next):
raise Unauthorized(name)
Here is my debugging session:
(Pdb) guarded_getattr(obj, name, _marker)
'Guo Zhonghai'
(Pdb) obj
<Contact at /creme/Contacts/Contact_1125>
(Pdb) name
'title'
(Pdb) guarded_getattr(obj, name, _marker)
'Guo Zhonghai'
(Pdb) p next
'Guo Zhonghai'
(Pdb) guarded_getattr(obj, name, _marker) == next
True
(Pdb) guarded_getattr(obj, name, _marker) is next
False
(Pdb) type(guarded_getattr(obj, name, _marker)), type(next)
(<type 'str'>, <type 'str'>)
(Pdb) id(guarded_getattr(obj, name, _marker))
46912619931440
(Pdb) id(next)
46912619931720
Thus, often string attributes will fail with this check.
In my opinion the code should read:
if not ok:
if (container is not None or
guarded_getattr(obj, name, _marker)
!= next):
raise Unauthorized(name)
If you agree that his is a bug, I'll log it.
--
Roché Compaan
Upfront Systems http://www.upfrontsystems.co.za