Zope Toolkit - 1.0a1 release
Hi. On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. You can read more about the release at http://docs.zope.org/zopetoolkit/releases/overview-1.0a1.html. The first ZTK release supports all of Python 2.4, 2.5 and 2.6. To use the ZTK release, you can use: [buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg This first release focuses on getting something out and defining the actual technical outcome of a release. Currently the release outcome is tailored to the needs of the three frameworks. Now would be a good time for any direct users of the ZTK to speak up and note anything that would make a ZTK release more useful to them. In a first dev release created earlier last week we tried to create an easy_install friendly index for the release. But there have been questions about the exact contents of the such an index. Furthermore it isn't clear if such an index would be useful at all to any potential ZTK consumer. Since the three frameworks only use buildout and have no use for any other means, we decided to drop the index from the release procedure until it's usefulness and exact definition have become clear. The release team is currently discussing the further roadmap to a 1.0 final release and has some open discussion points to what remains to be done until we can call it a final release and the process for further releases and version upgrades. We post our meeting notes at http://docs.zope.org/zopetoolkit/releaseteam/index.html. Feel free to start discussing with us on this mailing list. All the best, Hanno
On 6/30/10 21:47 PM, Hanno Schlichting wrote:
To use the ZTK release, you can use:
[buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg
This first release focuses on getting something out and defining the actual technical outcome of a release. Currently the release outcome is tailored to the needs of the three frameworks.
Grok's groktoolkit now extends from this 1.0a1 release. After today's zc.catlog bugfix release, Grok is using the ZTK now without any issues. Thanks Hanno! regards, jw
Le 06/07/2010 16:38, Jan-Wijbrand Kolman a écrit :
On 6/30/10 21:47 PM, Hanno Schlichting wrote:
To use the ZTK release, you can use:
[buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg
This first release focuses on getting something out and defining the actual technical outcome of a release. Currently the release outcome is tailored to the needs of the three frameworks.
Grok's groktoolkit now extends from this 1.0a1 release. After today's zc.catlog bugfix release, Grok is using the ZTK now without any issues.
Same thing for BlueBream: the next version 1.0b3 will be using the ZTK 1.0a2. And There is no bbkit anymore. Eveything is in the bluebream package. Christophe
Thanks Hanno!
regards, jw
_______________________________________________ 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 )
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit.
I've yet to hear any response to my post about non-backward-compatible classes: https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fred Drake wrote:
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit.
I've yet to hear any response to my post about non-backward-compatible classes:
https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html
Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin?
Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes. Note that I dont use zope.{,app.}pluggableauthservice, and so have no skin in that particular game. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwzRPYACgkQ+gerLs4ltQ5G6QCghXIGoYcM9cyEISQ2vE+sbxK/ q58An28jL5EGrWytF3C4pi6zSM3Xu8O8 =beIj -----END PGP SIGNATURE-----
On 07/06/2010 05:00 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Fred Drake wrote:
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting<hanno@hannosch.eu> wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit.
I've yet to hear any response to my post about non-backward-compatible classes:
https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html
Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin?
Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes.
zope.pluggableauth doesn't seem to depend on zope.app.container? Or did you mean zope.container? I think you meant the latter. I have no objection to adding these back in (zope.container.contained.Contained, that is), as it doesn't change the dependency. Regards, Martijn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote:
On 07/06/2010 05:00 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Fred Drake wrote:
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting<hanno@hannosch.eu> wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. I've yet to hear any response to my post about non-backward-compatible classes:
https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html
Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin? Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes.
zope.pluggableauth doesn't seem to depend on zope.app.container? Or did you mean zope.container? I think you meant the latter. I have no objection to adding these back in (zope.container.contained.Contained, that is), as it doesn't change the dependency.
Fred was commenting on a change to zope.app.authentication, actually, which has dependencies on ZODB3 and zope.app.container. Sorry for any confusion. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwzWOAACgkQ+gerLs4ltQ4vgQCgt5Qnb3qBdKMqxJYGcG34o4Kv 6eMAoN0u3ZqCoeET0Jg5iclZMXbgoVG8 =MmRq -----END PGP SIGNATURE-----
On Tue, Jul 6, 2010 at 11:00 AM, Tres Seaver <tseaver@palladion.com> wrote:
Given that ZODB3 and zope.app.container are still non-optional dependencies of the package, I can't see any reason not to restore those base classes.
I mentioned it on IRC, but wanted to mention here as well for completeness: zope.pluggableauth 1.0.3 is out with the proposed change. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein
On Tue, Jul 6, 2010 at 4:54 PM, Fred Drake <fdrake@acm.org> wrote:
I've yet to hear any response to my post about non-backward-compatible classes:
https://mail.zope.org/pipermail/zope-dev/2010-July/040898.html
Is no one else concerned about the backward incompatibility introduced by zope.pluggableauth.plugins.session.SessionCredentialsPlugin?
Apparently not :) But your proposal sounded good to me. Just go ahead. Hanno
Am 30.06.2010 um 21:47 schrieb Hanno Schlichting:
Hi.
On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit.
You can read more about the release at http://docs.zope.org/zopetoolkit/releases/overview-1.0a1.html. The first ZTK release supports all of Python 2.4, 2.5 and 2.6.
To use the ZTK release, you can use:
[buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg
Tried it with a project of mine. It works nearly completely fine. I only saw some a test breaking because between zope.testbrowser 3.6.0a2 and 3.9.0 behavior of browser.goBack() seems to have changed. It does now a reload of the previous page (causing form re-submit in my test). But maybe this is caused by the new mechanize 0.2.x version. Yours sincerely, -- Michael Howitz · mh@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development
participants (7)
-
Christophe Combelles -
Fred Drake -
Hanno Schlichting -
Jan-Wijbrand Kolman -
Martijn Faassen -
Michael Howitz -
Tres Seaver