Re: [Zope-dev] Re: New-style ExtensionClasses (Zope 2.8) -- MRO issue
On Sat, Nov 01, 2003 at 09:10:11AM -0200, Sidnei da Silva wrote: | Couldn't get mro for | Products.GroupUserFolder.GroupUserFolder.GroupUserFolder | Couldn't get mro for Products.CMFFormController.Script.FSPythonScript | Couldn't get mro for | Products.CMFFormController.FSControllerValidator.FSControllerValidator | Couldn't get mro for | Products.CMFFormController.FSControllerPythonScript.FSControllerPythonScript | Couldn't get mro for Products.CMFPlone.PropertiesTool.PropertiesTool | 488 5 210 The ones in CMFPlone and CMFFormController seemed easy to fix, I haven't dived much into GroupUserFolder, as it's hieararchy seems very complex to me. I checked in the changes on separate branches of each product. In Plone I just changed Folder for ObjectManager, and in CMFFormController I separated the class into a mixin class with no bases, that is then mixed into FSPythonScript. The mrohell script is very nice, though I haven't really understood the output. I fixed those by trial and error :( []'s -- Sidnei da Silva <[EMAIL PROTECTED]> dreamcatching :: making your dreams come true http://awkly.org BYTE editors are people who separate the wheat from the chaff, and then carefully print the chaff. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] New-style ExtensionClasses (Zope 2.8) -- MRO issue
On Sat, Nov 01, 2003 at 12:18:47PM +0100, Stefan H. Holek wrote: | I am also very, very worried about breaking b/w compatibility in Zope 2. | | I am responsible for about 15 sites, with say 10 distinct products | each. Are you saying I have to evaluate/upgrade 150 products because I | want to go to Zope 2.8(9)? No customer is going to pay for that effort | (and I will likely not find the time to do it anyway) so I will be | locked in 2.7-land forever. Bah! | | So yes, option 3 it must be. Let's save the fundamental changes for | Zope 3. As far as I understand, even if we dont go with option 2 there will be *some* effort on migrating from 2.7 to 2.8. Adding the update of a few products may not be as bad as you painted here. I've analised the changes needed to make the current Plone from CVS to work with option 2 and they are not that intrusive. Its basically change the order of one or two base classes and nothing more than that. Now I have a interesting question to ask: *If* we go for option 3, and we fix some products to work with option 2, would that cause any incompatibility? -- Sidnei da Silva <[EMAIL PROTECTED]> dreamcatching :: making your dreams come true http://awkly.org The first version always gets thrown away. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] Re: New-style ExtensionClasses (Zope 2.8) -- MRO issue
Sorry, it was just on the wrong place. [EMAIL PROTECTED]:~/src/zope/2_7-mro$ find . -name "*mroh*" ./mrohell.py -- Sidnei da Silva <[EMAIL PROTECTED]> dreamcatching :: making your dreams come true http://awkly.org The steady state of disks is full. -- Ken Thompson ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] New-style ExtensionClasses (Zope 2.8) -- MRO issue
I am also very, very worried about breaking b/w compatibility in Zope 2. I am responsible for about 15 sites, with say 10 distinct products each. Are you saying I have to evaluate/upgrade 150 products because I want to go to Zope 2.8(9)? No customer is going to pay for that effort (and I will likely not find the time to do it anyway) so I will be locked in 2.7-land forever. Bah! So yes, option 3 it must be. Let's save the fundamental changes for Zope 3. IMHO, Stefan On Freitag, Okt 31, 2003, at 18:14 Europe/Vienna, Jim Fulton wrote: Thoughts? I am worried enough about breaking products that I'm inclined to go with option 3. Does anybody think we ought to use the new algorithm (option 2)? Jim -- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/ ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] Re: New-style ExtensionClasses (Zope 2.8) -- MRO issue
Not bad. On a 'stock' plone installation, i've got these results: [EMAIL PROTECTED]:~/src/instance/mro$ ./bin/zopectl debug Starting debugger (the name "app" is bound to the top-level Zope object) >>> import mrohell >>> base = mrohell.step1() >>> mrohell.step2(base, mroonly=True) Couldn't get mro for Products.GroupUserFolder.GroupUserFolder.GroupUserFolder Couldn't get mro for Products.CMFFormController.Script.FSPythonScript Couldn't get mro for Products.CMFFormController.FSControllerValidator.FSControllerValidator Couldn't get mro for Products.CMFFormController.FSControllerPythonScript.FSControllerPythonScript Couldn't get mro for Products.CMFPlone.PropertiesTool.PropertiesTool 488 5 210 I'm going to fix those (after my english class) and then try something harder ;) -- Sidnei da Silva <[EMAIL PROTECTED]> dreamcatching :: making your dreams come true http://awkly.org A modem is a baudy house. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] Re: New-style ExtensionClasses (Zope 2.8) -- MRO issue
On Fri, Oct 31, 2003 at 03:08:34PM -0500, Jim Fulton wrote: | Sidnei da Silva wrote: | >On Fri, Oct 31, 2003 at 02:39:28PM -0500, Jim Fulton wrote: | >| I've checked the results of my work into the mro-advanture-branch (waa, | >| I wish I cud spell) branch. | >| | >| You might find it entertaining to check out Zope on this branch: | >| | >| cvs co -rmro-advanture-branch Zope | >| | >| (and build it) (Note, Python2.3 is required.) | >| | >| Install your favorite products (CMF makes a nice example) | >| and then use the functions in the included mrohell module to | >| find out if you have a problem: | >| | >| cd Zope | >| bin/zopectl debug | >| >>> import mrohell | >| >>> base = merohell.step1() | >| >>> mrohell.step2(base, mroonly=True) ERmm am I missing something? [EMAIL PROTECTED]:~/src/zope/2_7-mro$ find . -name "mrohell" [EMAIL PROTECTED]:~/src/zope/2_7-mro$ cat CVS/Tag Tmro-advanture-branch [EMAIL PROTECTED]:~/src/instance/mro]$ ./bin/zopectl debug Starting debugger (the name "app" is bound to the top-level Zope object) >>> import mrohell Traceback (most recent call last): File "", line 1, in ? ImportError: No module named mrohell -- Sidnei da Silva <[EMAIL PROTECTED]> dreamcatching :: making your dreams come true http://awkly.org That does not compute. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-dev] New-style ExtensionClasses (Zope 2.8) -- MRO issue
Jim Fulton wrote: 3. Use a hybrid schema. I'll call this the "encapsulated base" scheme. Is it possible for the hybrid schema to generate a 'deprecation' warning for each instance of a class that doesn't match the requirements of the C3 resolution order when Zope is first started, and thus increase the chances that product authors will modify their products (or be coerced to do so :)), without actually breaking them? --Richard ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: [Zope-Coders] Bugday Reloaded: The Sequel
--On Dienstag, 28. Oktober 2003 9:40 Uhr -0500 Brian Lloyd <[EMAIL PROTECTED]> wrote: Hi all - I'd like to try to have another bug day next Tuesday (Nov 3) to make up for the one that was cut short last week, in preparation for a beta 2 release of Zope 2.7. Nov 3 is Monday, Tuesday would be the 4th. Please clearify :-) -ja ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
