[Zope3-dev] Removing SSL/SSH-Keys from Skeleton
Hi, didn't we say at some point in time that we wanted to remove the SSH/SSL keys that we deliver by with Zope 3? In zopeskel/etc there are still server.pem and ssh_host_rsa_key as well as in the root of the trunk. Is there any reason not to remove them from there? Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: wading through zcml...
Chris Withers wrote:
Jim Fulton wrote:
If you want to specify the name of a template in ZCML, then you'll
have to invoke some magic.
Why can't IView (or whatever it is) just specify that the constructor
must accept a request, response and a template instance?
Because the template may not be passed in, and even if it is, where
would it be constructed and how would it be found again?
If you have this:
class MyView(object):
def __init__(self, context, request, template):
self.template = template # IView specifices template = a template
...
then you may as well not have a 'template' attribute for /> at all since you have to do so much work; you could just do this
(which you can do now, in fact)
class MyView(object):
template = ViewPageTemplateFile('mytemplate.pt')
def __init__(self, context, request):
self.context = context
self.request = request
If you have it done in ZCML, though, you can get a template-only view
without any Python at all, though:
Martin
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] speeding up buildout of individual parts
On Dec 6, 2006, at 4:03 PM, Christian Theune wrote: Hi, Jim Fulton wrote: This should work a lot better as of a couple of days ago. I noticed the updates in the last days, didn't change much for me though. The longest time is the 'svn up' in the Zope 3 checkout. It takes about 32 seconds when I run 'bin/buildout install zope3' (Zope 3 being a zc.recipe.zope3checkout). This is a long time if you're running bin/buildout many times while working on recipes or buildouts. However, in my case buildout installs/updates depending recipes too which in my case means updating a Zope 3 checkout (this takes a long time from Europe). It should only reinstall parts who's configuration has changed. Without any more specifics, it is hard to make a more specific comment. :) In particular, I'm not sure what you mean by "depending" above. ... Right. I guess 'depending' was a term I chose because I didn't know better. I'm pretty sure that I didn't change any configuration in the buildout at all, but the zope3checkout install is run every time, even when I specify just the zope3instance to be installed. So you meant depended on. You have a Zope 3 instance part that depends on a zope 3 installation which is a checkout. Now, when you install a part, any part it references will be included in the part list. The zope3checkout does an svn up whenever it runs. Any idea whether it would be reasonable/wise to have a mode that says "This part only please and I mean it!"? Perhaps, although we still have to initialize other parts that a part references so that they can compute data that the referencing part needs. Right. Again, that's not the time-critical part so not a problem. OK, I agree. So we'll either need another command, or an option on the install command (or maybe a buildout section option). Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] speeding up buildout of individual parts
Hi, Jim Fulton wrote: > This should work a lot better as of a couple of days ago. I noticed the updates in the last days, didn't change much for me though. The longest time is the 'svn up' in the Zope 3 checkout. It takes about 32 seconds when I run 'bin/buildout install zope3' (Zope 3 being a zc.recipe.zope3checkout). This is a long time if you're running bin/buildout many times while working on recipes or buildouts. >> However, in my case buildout installs/updates depending recipes too >> which in my case means updating a Zope 3 checkout (this takes a long >> time from Europe). > > It should only reinstall parts who's configuration has changed. > Without any more specifics, it is hard to make a more specific > comment. :) > In particular, I'm not sure what you mean by "depending" above. > ... Right. I guess 'depending' was a term I chose because I didn't know better. I'm pretty sure that I didn't change any configuration in the buildout at all, but the zope3checkout install is run every time, even when I specify just the zope3instance to be installed. >> Any idea whether it would be reasonable/wise to have a mode that says >> "This part only please and I mean it!"? > > Perhaps, although we still have to initialize other parts that a part > references > so that they can compute data that the referencing part needs. Right. Again, that's not the time-critical part so not a problem. -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] speeding up buildout of individual parts
On Dec 6, 2006, at 3:24 PM, Christian Theune wrote: Hi, I noticed that I started using the 'bin/buildout install ' option a lot to speed up re-building while developing a buildout. This should work a lot better as of a couple of days ago. However, in my case buildout installs/updates depending recipes too which in my case means updating a Zope 3 checkout (this takes a long time from Europe). It should only reinstall parts who's configuration has changed. Without any more specifics, it is hard to make a more specific comment. :) In particular, I'm not sure what you mean by "depending" above. ... Any idea whether it would be reasonable/wise to have a mode that says "This part only please and I mean it!"? Perhaps, although we still have to initialize other parts that a part references so that they can compute data that the referencing part needs. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] speeding up buildout of individual parts
Hi, I noticed that I started using the 'bin/buildout install ' option a lot to speed up re-building while developing a buildout. However, in my case buildout installs/updates depending recipes too which in my case means updating a Zope 3 checkout (this takes a long time from Europe). I can use the offline switch for now to avoid that, but potentially I'd want buildout to *do* online work while updating/installing the part I specified. Any idea whether it would be reasonable/wise to have a mode that says "This part only please and I mean it!"? Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] [Fwd: Re: zc.recipe.testrunner - Support additional eggs]
I hope this ends up in the right thread. Just for the record, as I forgot to post this to the list. -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development --- Begin Message --- Hi, Tres Seaver wrote: > Shouldn't the dependency information in the eggs-to-test be sufficient > for that? Ah. You're right. I've totally misunderstood eggs vs. buildout and Zope in this point. I've checked the docs and figured that the dependencies do take care -- if you declare them. Thanks for the pointer. Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature --- End Message --- signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Experiments with zope3instance
Hi, we're starting to try out some variations on the zope3instance recipe and I wrote a minimum amount of documentation to let other people know what we're doing. Feedback would be welcome. See http://svn.zope.org/zc.recipe.zope3instance/branches/gocept-zconf-slug-dev/src/zc/recipe/zope3instance/experiments.txt?rev=71454&view=auto Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: where are the eggs for the 3.3 release?
Olivier Grisel wrote: Philipp von Weitershausen a écrit : Olivier Grisel wrote: I was wondering where are the eggs for the version 3.3.0 of the main components of Zope3. I am mainly interested in the following components: - zope.interface - zope.component - zope.testing and their dependencies. I used to find them either on http://download.zope.org.distribution or on the cheeseshop but this time it seems like nobody did the release. Right. The overall Zope 3.3 release happened, but nobody did the actual eggs. Perhaps you'd like to do them? It should just be a matter of setting the external to the right tag and executing setup.py build_egg. Ok but I do not have the checkin privileges to add the missing tags on individual packages. It's easy to get those :) I'm sure Jim would also give you upload privileges to download.zope.org. What place is best? download.zope.org or cheeseshop.python.org ? Both. I think at least zope.interface and zope.component and their dependencies deserve a cheeseshop publication as they can be useful dependencies to non-zope projects. Yes. -- http://worldcookery.com -- Professional Zope documentation and training 2nd edition of Web Component Development with Zope 3 is now shipping! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope3 instance with no zodb
On 12/5/06, Chris Withers <[EMAIL PROTECTED]> wrote: Jim Fulton wrote: > > Yes. You have to configure an alternate publication object. Okay, any clues how to do that? Where's the default configuration done? What interfaces do I need to implement? I have some example code here that can help you. I've been meaning to release this for more than one year now, and maybe it's time. http://cheeseshop.python.org/pypi/snap/0.5 Hope that's of any help. The interesting bits are in configure.zcml ( directive) and publisher.py -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: where are the eggs for the 3.3 release?
Philipp von Weitershausen a écrit : > Olivier Grisel wrote: >> I was wondering where are the eggs for the version 3.3.0 of the main >> components >> of Zope3. I am mainly interested in the following components: >> >> - zope.interface >> - zope.component >> - zope.testing >> >> and their dependencies. >> >> I used to find them either on http://download.zope.org.distribution or >> on the >> cheeseshop but this time it seems like nobody did the release. > > Right. The overall Zope 3.3 release happened, but nobody did the actual > eggs. Perhaps you'd like to do them? It should just be a matter of > setting the external to the right tag and executing setup.py build_egg. Ok but I do not have the checkin privileges to add the missing tags on individual packages. > I'm sure Jim would also give you upload privileges to download.zope.org. What place is best? download.zope.org or cheeseshop.python.org ? I think at least zope.interface and zope.component and their dependencies deserve a cheeseshop publication as they can be useful dependencies to non-zope projects. -- Olivier ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: where are the eggs for the 3.3 release?
Olivier Grisel wrote: I was wondering where are the eggs for the version 3.3.0 of the main components of Zope3. I am mainly interested in the following components: - zope.interface - zope.component - zope.testing and their dependencies. I used to find them either on http://download.zope.org.distribution or on the cheeseshop but this time it seems like nobody did the release. Right. The overall Zope 3.3 release happened, but nobody did the actual eggs. Perhaps you'd like to do them? It should just be a matter of setting the external to the right tag and executing setup.py build_egg. I'm sure Jim would also give you upload privileges to download.zope.org. -- http://worldcookery.com -- Professional Zope documentation and training 2nd edition of Web Component Development with Zope 3 is now shipping! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: wading through zcml...
Chris Withers <[EMAIL PROTECTED]> wrote: > Martijn Faassen wrote: >> class TemplateView(grok.View): >> template = unassociated >> module_info = module_info_ > I'm not sure. Debugging becomes a nightmare with generated classes, > which is how I ran into these problems in the first place. > > Can you explain what the what the above code snippet actually does? It generates a view for a template file that doesn't have its own view. >> I've done it too recently in the form support. The *real* formlib-level >> form class is dynamically created for each grok-level form: >> >> class RealEditForm(form.EditForm): >> form_fields = get_form_fields(factory, context) >> actions = actions_ >> >> This one is a bit more scary, as the end-user interacts with an >> *instance* of this class; the form attribute on grok-level forms is one. > > There must be a nicer way :-S Possibly. It's not that bad right now. The difficulty is that I do need to generate a class, not an instance, as I can only initialize the instance when the view is initialized because the context and request are needed. I could probably do some scary hacking to make it an instance after all, but that will make the code far less easy to understand. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zc.recipe.testrunner - Support additional eggs
Tres Seaver <[EMAIL PROTECTED]> wrote: [snip] > Shouldn't the dependency information in the eggs-to-test be sufficient > for that? That's what I was going to say. The egg should normally just list its own dependencies in setup.py and buildout will handle this just fine. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: wading through zcml...
Jim Fulton wrote: If you want to specify the name of a template in ZCML, then you'll have to invoke some magic. Why can't IView (or whatever it is) just specify that the constructor must accept a request, response and a template instance? Now I'll go back to ignoring this thread, the desire to do so increased by the sort of extreme over-simplifying remarks made. Not sure what you mean by this... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope3 instance with no zodb
Martijn Faassen wrote: Quite a few bits and pieces of Zope 3 also depend on there being a __parent__, including the default security policy. You may therefore either need to establish such a __parent__ relationship, or write a new security policy. I hope this is all documented in interfaces? Chris, when you finish doing this please document it so it'll be an "of course" for the rest of us too. :) Sure, where would be the best place to put this doc? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: wading through zcml...
Martijn Faassen wrote: dynamically generated class for templates that don't have classes of themselves. I know you were there when we created this one. :) class TemplateView(grok.View): template = unassociated module_info = module_info_ of course the instances of this class do nothing the developer has to interact with. As soon as the developer provides a view class of their own, there's no dynamically generated class anymore. I think that this is an acceptable use of the pattern. I'm not sure. Debugging becomes a nightmare with generated classes, which is how I ran into these problems in the first place. Can you explain what the what the above code snippet actually does? I've done it too recently in the form support. The *real* formlib-level form class is dynamically created for each grok-level form: class RealEditForm(form.EditForm): form_fields = get_form_fields(factory, context) actions = actions_ This one is a bit more scary, as the end-user interacts with an *instance* of this class; the form attribute on grok-level forms is one. There must be a nicer way :-S cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope3 instance with no zodb
Jim Fulton wrote: Yes. You have to configure an alternate publication object. Okay, any clues how to do that? Where's the default configuration done? What interfaces do I need to implement? Launchpad does this. Cany any Launchpad'ers present tell me where to look in your source repository? other things, controls object traversal. The default publisher uses a database object as a starting point for traversal. An alternate publisher could use something else, including allowing multiple "root" objects. Cool :-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope3 instance with no zodb
> I remember Shane asking this a while ago and seem to remember the > answer was "no", but I'm hoping that's changed. > > Is it possible to have a Zope 3 instance that has no zodb backing at > all? > > I've been mocking up an app, currently in Zope 2, and have ended up > using PostGresSQL as the data store may be not exactly what your up to, but since your already on postgre, pgstorage might be an option for you: http://hathawaymix.org/Weblog/2006-02-11 Well, but as this is made by Shane, you probably already know it :-) Cheers, Sascha -- Lalisio GmbH www.lalisio.com Puschkinstraße 1 fon +49-(0)361/541 43 80 99084 Erfurt fax +49-(0)361/541 43 79 [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
