-----BEGIN PGP SIGNED MESSAGE-----
On 02/16/2013 05:16 AM, Marius Gedminas wrote:
> Options: - add zope.untrustedpython to the ZTK - switch zope.security
> to the 3.9 branch
> I'm leaning towards option 1, but I don't know the procedure for
> adding something to the ZTK. Help?
+1 for adding it. The ZTK is still managed in SVN:
You should be able to add it to the three config files used to build /
test the ZTK:
> Incidentally, the changelog on the PyPI page for zope.security has no
> mention of 3.9.x, but the branch (and a 3.9.0 tag) exists in SVN?
> What happened there?
Just an oversight. The history goes something like:
- - I released zope.proxy 4.1.0, breaking BBB for then-current zope.security
3.8.3. which had been made from the trunk (2012-12-19).
- - I then made the 3.8 branch, and released 3.8.4, pinning z.proxy < 4.1dev
- - Discovering that 3.8.4 included the trunk version of the proxy.h header,
I made the 3.8.5 release, copying in the compatible header (2012-12-20).
- - FBO the ZTK trunk, I made the 3.9 release, pinning z.proxy >= 4.1.0,
and including the compatilbe proxy.h header.
We just need to fold in that history, which is present on the 3.8 and
3.9 branches, but not the trunk. I will check that in now.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -