Re: [Zope-dev] Re: Grok 0.11 released!
On Saturday 10 November 2007, Stephan Richter wrote: Could we create a grok KGS which is generated by a python-script, that takes the correct zope3 KGS as a base? Based on my son's behavior today, you will be able to do this in a few hours. Okay, this is now done. It is all documented here: http://svn.zope.org/zope.release/trunk/src/zope/release/README.txt?view=markup Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
AW: [Zope-dev] Re: Grok 0.11 released!
Hi Tres Whoever released those two eggs (the '.dev-r#' ones) need to release real updated packages, and then grok 0.11.1 should be released using them. DEATH TO FAUX PACKAGES! As far as I understand, this does not happen if you depend on a KGS, right? Does the grok release not use the KGS from Stephan? Regards Roger Ineichen Tres. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: AW: [Zope-dev] Re: Grok 0.11 released!
On Friday 09 November 2007, Roger Ineichen wrote: Hi Tres Whoever released those two eggs (the '.dev-r#' ones) need to release real updated packages, and then grok 0.11.1 should be released using them. DEATH TO FAUX PACKAGES! As far as I understand, this does not happen if you depend on a KGS, right? Does the grok release not use the KGS from Stephan? I agree with Roger, Grok should use the KGS and all will be fine. ;-) Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Grok 0.11 released!
Lennart Regebro wrote: On Nov 9, 2007 4:06 PM, Roger Ineichen [EMAIL PROTECTED] wrote: Create our own locked down index? I think so because, Surely there must be a way to say I want to use THAT KGS over there. Except for this module, that should hav this version. And of course, all these bunch of eggs which isn't dfined in that KGS at all. Because that's what we all need. So it must be possible, right? The KGS is just that, a Known Good Set. It must be possible to in your build out override a version here and add packages there? Those are exactly the problems with the locked down index: * You can always use *more* packages but you'll have to lock them down yourself, can't use another KGS for those * You cannot say I know the KGS prefers zope.frobnaz 1.2.3, but I deliberately want to upgrade to zope.frobnaz 2.0.2. It won't work because the index simply doesn't expose the 2.0.2 version of zope.frobnaz. So the locked down index doesn't support two important use cases. And building your own index isn't really a solution, IMO. The average cavemen programmer won't do that... ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Grok 0.11 released!
On Friday 09 November 2007, Philipp von Weitershausen wrote: Those are exactly the problems with the locked down index: * You can always use *more* packages but you'll have to lock them down yourself, can't use another KGS for those But this is a limitation of setuptools. I think this could be solved using find-links for now. * You cannot say I know the KGS prefers zope.frobnaz 1.2.3, but I deliberately want to upgrade to zope.frobnaz 2.0.2. It won't work because the index simply doesn't expose the 2.0.2 version of zope.frobnaz. You can use find-links and point to the new location. So the locked down index doesn't support two important use cases. And building your own index isn't really a solution, IMO. The average cavemen programmer won't do that... The problem here is that setuptools is too immature to handle those cases properly. We will have to write a lot more software to do this correctly. The KGS index approach was just something that would give us sanity with very little new software. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Grok 0.11 released!
On Nov 9, 2007 4:34 PM, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Those are exactly the problems with the locked down index: * You can always use *more* packages but you'll have to lock them down yourself, can't use another KGS for those Could we create a grok KGS which is generated by a python-script, that takes the correct zope3 KGS as a base? * You cannot say I know the KGS prefers zope.frobnaz 1.2.3, but I deliberately want to upgrade to zope.frobnaz 2.0.2. It won't work because the index simply doesn't expose the 2.0.2 version of zope.frobnaz. This needs to be fixed in setup tools some time in the future, then, because it will severly limit the usablility of a KGSs if you can't use this. You very often need to upgrade one package... -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Grok 0.11 released!
On Friday 09 November 2007, Lennart Regebro wrote: On Nov 9, 2007 4:34 PM, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Those are exactly the problems with the locked down index: * You can always use *more* packages but you'll have to lock them down yourself, can't use another KGS for those Could we create a grok KGS which is generated by a python-script, that takes the correct zope3 KGS as a base? With a little bit more software, yes. * You cannot say I know the KGS prefers zope.frobnaz 1.2.3, but I deliberately want to upgrade to zope.frobnaz 2.0.2. It won't work because the index simply doesn't expose the 2.0.2 version of zope.frobnaz. This needs to be fixed in setup tools some time in the future, then, because it will severly limit the usablility of a KGSs if you can't use this. You very often need to upgrade one package... Right, I agree. But there are solutions. You can use find-links to get a newer version. The beautiful thing about not nailing versions is that you can overwrite what the index says. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Grok 0.11 released!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hi everybody,
The Grok team is happy to announce the release of Grok 0.11! Grok is
a web application framework built with Zope 3 technologies that aims
to be easy to use.
Grok 0.11 is a feature release of Grok, introducing important new features:
* Layers and skinning support. It is now easy to place views in
layers, and to define skins so that these layers can be browsed.
* REST support. There is an easy way to create RESTful web services
with Grok now. Create special REST protocols that support GET, POST,
PUT and DELETE. See http://grok.zope.org/minitutorials/rest.html for
more information.
* pluggable template languages. Besides the built-in support for Zope
Page Templates, Grok now allows you to plug in other template
languages as well. See
http://grok.zope.org/minitutorials/template-languages.html for
instructions on how to integrate a template language into Grok. We are
planning on releasing a Genshi plugin for Grok next week.
* Improved permission and role support. See
http://grok.zope.org/minitutorials/permissions.html for more
information. If you were already using these in your existing Grok
code you need to change your code a bit. See
http://grok.zope.org/upgrade.html contains more information about
these changes.
One important change is rather hidden from view so bears a bit of
explanation. Grok is based on Zope 3. Grok could always reuse Zope 3
libraries without problems. The other way around wasn't so nice
however: Zope 3-based code could not use Grok-based code so easily, as
Grok would not emit configuration actions. Grok 0.11 now does emit
such configuration actions and this is a major step on the way towards
backwards compatibility with Zope 3. If you have custom Grokkers in
your code, you probably have to change them: please see
http://grok.zope.org/upgrade.txt for information how to upgrade these.
For the detailed changelog, see Grok's PyPI entry page:
http://pypi.python.org/pypi/grok
For upgrade notes, including how to change your application, see
http://grok.zope.org/upgrade.html
For installation instructions and much more on how to use Grok, see
the Grok tutorial: http://grok.zope.org/tutorial.html
If you enjoy Grok, please subscribe to the grok-dev mailing list
http://mail.zope.org/mailman/listinfo/grok-dev
and join us in the #grok channel on irc.freenode.net
We hope to see you there!
The new grok-0.11.cfg adds dependencies on eggs which should *not* exist:
$ diff -u configs/grok-0.1{0.2,1}.cfg
- --- configs/grok-0.10.2.cfg 2007-10-29 18:32:29.0 -0400
+++ configs/grok-0.11.cfg 2007-11-08 19:44:06.0 -0500
@@ -1,8 +1,8 @@
[versions]
- -grok = 0.10.2
+grok = 0.11
ClientForm = 0.2.7
docutils = 0.4
- -martian = 0.9
+martian = 0.9.1
mechanize = 0.1.7b
Pygments = 0.8.1
pytz = 2007g
@@ -44,7 +44,7 @@
zope.app.preference = 3.4.0a1
zope.app.principalannotation = 3.4.0a1
zope.app.publication = 3.4.2
- -zope.app.publisher = 3.4.0
+zope.app.publisher = 3.5.0a2
zope.app.renderer = 3.4.0a1
zope.app.rotterdam = 3.4.0a1
zope.app.schema = 3.4.0a1
@@ -86,16 +86,16 @@
zope.modulealias = 3.4.0a1
zope.pagetemplate = 3.4.0a1
zope.proxy = 3.4.0
- -zope.publisher = 3.4.1
+zope.publisher = 3.5.0a1.dev-r78838
zope.schema = 3.4.0
zope.security = 3.4.0b5
- -zope.server = 3.4.1
+zope.server = 3.5.0a2
zope.session = 3.4.1
zope.size = 3.4.0
zope.structuredtext = 3.4.0
zope.tal = 3.4.0b1
zope.tales = 3.4.0a1
zope.testbrowser = 3.4.1
- -zope.testing = 3.4
+zope.testing = 3.5.1
zope.thread = 3.4
- -zope.traversing = 3.4.0
+zope.traversing = 3.5.0a1.dev-r78730
Whoever released those two eggs (the '.dev-r#' ones) need to release
real updated packages, and then grok 0.11.1 should be released using them.
DEATH TO FAUX PACKAGES!
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHM7Gd+gerLs4ltQ4RAumxAJ9wIYGXkQIhNHqmktgu05U8HY9PYgCgoSph
tLjLyiWXmmR4982xesFWgd0=
=25Rh
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
