Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wed, Oct 15, 2008 at 01:15:15PM -0400, Benji York wrote: > On Wed, Oct 15, 2008 at 1:07 PM, Marius Gedminas <[EMAIL PROTECTED]> wrote: > > On Wed, Oct 15, 2008 at 10:59:24AM -0400, Benji York wrote: > >> On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> > >> wrote: > >> > Hi, > >> > It seems that buildout is broken: > >> > >> Are you referring to the Zope 3 trunk buildout? > > > > What's that, exactly? zope.release trunk? > > I was referring to svn://svn.zope.org/repos/main/Zope3/trunk. I can > only assume that's what the OP was referring to. That's not a buildout: it has no buildout.cfg, nor bin/buildout, nor bootstrap.py. What I was hoping to find was the equivalent for the KGS, but without explicit version restrictions; to test whether the latest versions of all the zope packages work together. Marius Gedminas -- The difference between Microsoft and 'Jurassic Parc': In one, a mad businessman makes a lot of money with beasts that should be extinct. The other is a film. signature.asc Description: Digital signature ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] thoughts about z3c.form-package
hey roger, thank you for your answers. really appreciated. :) @hook: i understand now, the applyChanges-method isnt a hook, its just a function so that the apply-thing can be used alone too. a hook is, as far as i understood this concept, a point of extensibility or variation. both isnt possible in this case. are their any different widget-implementations anywhere? i try to visualize that the form is rendered to different content with different widgets. i'm lacking use cases. =) i try to understand, why those fields are an abstraction of the widget or why this abstraction is needed. i have the feeling that there are only browser-widgets and when i have a look at the action, which is implemented in the z3c.form core-package (means not in browser), it already is a browser-widget (SubmitWidget), which means that the abstraction there doesnt exist anymore. if fields are the abstraction of widgets, ... - why should it be possible to use widgets without fields? - widgets shouldnt even be "known" to the user of z3c.form. what i'm trying to do with these questions is to find out the concepts behind z3c.form. i'm not used to functional programming style, its hard for me to get into the idea. thats why i'm trying to reimplement an object-oriented version with clear concepts that can be seen by the definition and arrangement of the classes. plus i think those are at least a little unobvious in z3c.form, that should be the reason why it is so hard to understand and "complex", since it in fact isnt, when understood once. but my problem is, i'm lacking experience in this kind of web-developement. i dont know about all possibilities that can be done with zope. thats why i'm asking you who has experience. :) you designed the package for a certain purpose and i try to reengineer this purpose so that my version doesnt miss any features. i hope that i'm not annoying you. :D just beeing curious. i'm thinking about two possibilities conceptualizing fields for my version. since i want to do it object-oriented, a field cant be only a collection of values of something (functional style). a field should have a responsibility for something. it is therefor able to encapsulate a concept -> concepts become obvious through the classes. 1.) a field is the abstraction of a widget. now there are two possibilites again: 1.1) widgets can be used stand-alone 1.2) widgets cant be used stand-alone as i wrote, if widgets are the abstraction of a field, then users shouldnt even get in contact with widgets. they should be a hidden concept. but since i dont want to loose possibilities regarding z3c.form, it has to be possible to use widgets stand-alone. but this results in forms that consist specialized widgets (for example browser-widgets) and general fields. such a form isnt general anymore. to keep concepts clean, widgets shouldnt be used stand-alone. 2.) a field is only a manager associating a widget with an attribute of a context if abstracted widgets arent needed, this would mean, that widgets can be used stand-alone. and this is the reason i asked those questions at the beginning. i'm thinking about if fields are an abstraction for the widgets... a) ... in z3c.form b) ... in general a): as i wrote, in z3c.form the actions are in fact already one kind of widget, namely the browser-widget SubmitWidget. at least here the concept of fields abstracting widgets is broken. b): maybe the field-concept isnt needed or overkill? as i sad, i'm lacking use cases. i try to visualize: one time a form is rendered to html, the other time the form is rendered to? which kind of request exists that renders the form to something else? ok, there is the pdf-example. with the field-concept, the fields should be rendered to pdf-code (in this case just html) and the render method then calls a different pagetemplate and embeds those widgets. since a call for rendering pdf-content isnt distinguishable from a call for rendering html-conent, the render-method has to be overwritten -> a new form emerges that is specialized creating pdf-output -> no field-abstraction needed, because this form will alway be for pdf-output. the aim of a general form with general fields should be, that if it is once defined, it can render itself to whatever output the request demands. in the pdf-example this would mean, that the form can render pdf-output just because of the request and if there was a different implementation using different widgets that render to something else than the browserwidgets, the field-abstraction would make perfectly sense. i'm trying to find out if this use case really exists. i hope you have the patience to enlighten me. :)) best regards, gards ;) -- View this message in context: http://www.nabble.com/thoughts-about-z3c.form-package-tp19869292p2780.html Sent from the Zope3 - users mailing list archive at Nabble.com. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.or
Re: [Zope3-Users] Buildout seems to be broken due to missin g back35.py in zope.app.component.
Am Mittwoch 15 Oktober 2008 19:28:55 schrieb Christophe Combelles: > Hermann Himmelbauer a écrit : > > Am Mittwoch 15 Oktober 2008 16:59:24 schrieb Benji York: > >> On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> wrote: > >>> Hi, > >>> It seems that buildout is broken: > >> > >> Are you referring to the Zope 3 trunk buildout? > > > > Well, Stephan Richter cleared things up a bit, I thought I was using the > > KGS, as I had the following in my buildout: > > > > [buildout] > > extends = http://download.zope.org/zope3.4/versions-3.4.0c2.cfg > > > > However, what I did not have was the "versions = versions" directive, > > thus the KGS was probably not used. I still don't really understand > > what's happening here. > > The versions-3.4.0c2.cfg only contains a [versions] section. This section > must be pointed in the main [buildout] section with version = section_name > (here the section_name is also 'versions', which is a bit confusing) Ah, now I get it, thanks! Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Hermann Himmelbauer a écrit : > Am Mittwoch 15 Oktober 2008 16:59:24 schrieb Benji York: >> On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> >> wrote: >>> Hi, >>> It seems that buildout is broken: >> Are you referring to the Zope 3 trunk buildout? > > Well, Stephan Richter cleared things up a bit, I thought I was using the KGS, > as I had the following in my buildout: > > [buildout] > extends = http://download.zope.org/zope3.4/versions-3.4.0c2.cfg > > However, what I did not have was the "versions = versions" directive, thus > the > KGS was probably not used. I still don't really understand what's happening > here. The versions-3.4.0c2.cfg only contains a [versions] section. This section must be pointed in the main [buildout] section with version = section_name (here the section_name is also 'versions', which is a bit confusing) Christophe > > I now have the "versions=versions" directive, and things look better now. > > Many thanks to all for help! > > Best Regards, > Hermann > ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wed, Oct 15, 2008 at 1:07 PM, Marius Gedminas <[EMAIL PROTECTED]> wrote: > On Wed, Oct 15, 2008 at 10:59:24AM -0400, Benji York wrote: >> On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> >> wrote: >> > Hi, >> > It seems that buildout is broken: >> >> Are you referring to the Zope 3 trunk buildout? > > What's that, exactly? zope.release trunk? I was referring to svn://svn.zope.org/repos/main/Zope3/trunk. I can only assume that's what the OP was referring to. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Am Mittwoch 15 Oktober 2008 16:59:24 schrieb Benji York: > On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> > wrote: > > Hi, > > It seems that buildout is broken: > > Are you referring to the Zope 3 trunk buildout? Well, Stephan Richter cleared things up a bit, I thought I was using the KGS, as I had the following in my buildout: [buildout] extends = http://download.zope.org/zope3.4/versions-3.4.0c2.cfg However, what I did not have was the "versions = versions" directive, thus the KGS was probably not used. I still don't really understand what's happening here. I now have the "versions=versions" directive, and things look better now. Many thanks to all for help! Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wed, Oct 15, 2008 at 10:59:24AM -0400, Benji York wrote: > On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> > wrote: > > Hi, > > It seems that buildout is broken: > > Are you referring to the Zope 3 trunk buildout? What's that, exactly? zope.release trunk? Marius Gedminas -- Premature optimization is the root of all evil. -- D.E. Knuth signature.asc Description: Digital signature ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Hermann Himmelbauer wrote: > Am Mittwoch 15 Oktober 2008 16:46:06 schrieb Hermann Himmelbauer: >> Hi, >> It seems that buildout is broken: >> >> A "bin/buildout" fetched some new packages, especially: >> zope.app.component-3.5.0 >> >> The previous version was: >> zope.app.component-3.4.1 >> >> The problem is, that a file, called "back35" is missing in >> zope.app.component-3.5.0 which is, however, imported/needed in several >> other files, e.g. in zope.app.form.browser.metadirectives.py: >> >> from zope.app.component.back35 import LayerField > > Hmmm, just tried a fresh buildout again, now I get this: > > src/zope/app/container/_zope_proxy_proxy.c:746: warning: initialization from > incompatible pointer type > error: Setup script exited with error: command 'gcc' failed with exit status 1 > An error occured when trying to install zope.app.container 3.6.1.Look above > this message for any errors thatwere output by easy_install. > While: > Installing app. > Getting distribution for 'zope.app.container'. > Error: Couldn't install: zope.app.container 3.6.1 > > What's happening here? Is somebody updating the packages? zope.app.container 3.6.1 has been released for a long time already. However, the C code hasn't been updated to Python 2.5 yet (and therefore breaks on 64bit systems). Bugfix releases for zope.app.container 3.5.x have long been available and you should've used one of those. However, I've now made another bugfix release of zope.app.container 3.6.x as well which contains the necessary fixes to the C code. > Is there perhaps a way to switch to an older release that works? Sure. Pin your versions, e.g. to the KGS. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Hermann Himmelbauer wrote: > Hi, > It seems that buildout is broken: > > A "bin/buildout" fetched some new packages, especially: > zope.app.component-3.5.0 > > The previous version was: > zope.app.component-3.4.1 > > The problem is, that a file, called "back35" is missing in > zope.app.component-3.5.0 which is, however, imported/needed in several other > files, e.g. in zope.app.form.browser.metadirectives.py: Right. back35.py contained backwards compatibility code so it was removed. Other packages were updated but not all of them were released immediately. I've now released the rest of the packages that were affected. > from zope.app.component.back35 import LayerField > > Ist there anything I can do about this? As the others suggested already, always pin all of your dependencies' versions, for instance using the KGS. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Am Mittwoch 15 Oktober 2008 16:46:06 schrieb Hermann Himmelbauer: > Hi, > It seems that buildout is broken: > > A "bin/buildout" fetched some new packages, especially: > zope.app.component-3.5.0 > > The previous version was: > zope.app.component-3.4.1 > > The problem is, that a file, called "back35" is missing in > zope.app.component-3.5.0 which is, however, imported/needed in several > other files, e.g. in zope.app.form.browser.metadirectives.py: > > from zope.app.component.back35 import LayerField Hmmm, just tried a fresh buildout again, now I get this: src/zope/app/container/_zope_proxy_proxy.c:746: warning: initialization from incompatible pointer type error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occured when trying to install zope.app.container 3.6.1.Look above this message for any errors thatwere output by easy_install. While: Installing app. Getting distribution for 'zope.app.container'. Error: Couldn't install: zope.app.container 3.6.1 What's happening here? Is somebody updating the packages? Is there perhaps a way to switch to an older release that works? Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wednesday 15 October 2008, Hermann Himmelbauer wrote: > Ist there anything I can do about this? You should really use the KGS. http://download.zope.org/zope3.4/intro.html You can then override versions that you find preferable. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> wrote: > Hi, > It seems that buildout is broken: Are you referring to the Zope 3 trunk buildout? -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
On Wed, Oct 15, 2008 at 10:46 AM, Hermann Himmelbauer <[EMAIL PROTECTED]> wrote: > Ist there anything I can do about this? Require version 3.4.1. We (ZC) have generally found that nailing down all versions, while tedious for getting updates, is the way to go to avoid unexpected failures due to too much being updated. The other packages need to have compatible 3.5.0 versions created and released. These kinds of deprecations and removals have always been a source of pain. -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Buildout seems to be broken due to missing back35.py in zope.app.component.
Hi, It seems that buildout is broken: A "bin/buildout" fetched some new packages, especially: zope.app.component-3.5.0 The previous version was: zope.app.component-3.4.1 The problem is, that a file, called "back35" is missing in zope.app.component-3.5.0 which is, however, imported/needed in several other files, e.g. in zope.app.form.browser.metadirectives.py: from zope.app.component.back35 import LayerField Ist there anything I can do about this? Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
