[Zope-dev] Re: The bleak Future of Zope?
Joachim Werner wrote: The problem of Zope 2 is - don't kill me for saying that - Plone. Plone and its foundations in CMF have created a large momentum around a terribly horrible code base. Believe me or not, almost everything gets more complicated with CMF/Plone than with plain Zope. Building a framework on top of a broken framework on top of an ageing framework that is hardly documented isn't a very good idea after all. You are somewhat right. It's an absolute bitch to write Products for Plone. But it does shows what is actually needed for Zope to work as intended. In plain Z2 You could write a lot of products, and they would all work fine on your site. But others could not easily download and use/try out the products. What Plone really is a good example of, is the necessity of a practical reference implementation that all content types and tools can be tested up against. It the light house that everything is steering towards. I believe that's the reason for it's succes. It's hard to put a finger on exactly why it has become one. But obviously it has reached critical mass of being good enough for a lot of things. It is also flexible enough to be changed beyond recognition. So both novice users and developers can use it with a lot of succes. A short list of things that I think makes it an end user succes (even advanced developers are end users of others products): The skin Notably main_template.pt plone.css. It is absolute paramount to have a flexible template/styleguide to write up against. It has to be pretty enough to be used in production site out of the box, and easy to change. The CMS' skin apparently wasn't good enough. A site can be layed ot in umpteen ways, but the Plone guys has said this is how we think it should look and function, and put a working example out there. Apparently that has been a very succesfull strategy. There is also several layers at which it can be changed. From stylesheets to programming. So it can look completely different. But ther reference is allways there as a guide. Installation It is easy to install and try out new products, and they all work together, and all use the same skin. So if you install a new product it automatically has the look and feel of your site. Even though the site is heavily skinned. Development process --- Quick and non-bureaucratic. The Plone developers are pretty open for suggestions, and hang out on irc and maillists. There is a shared repository (the collective) for 3'rd party products. Which gives a good sense of comunity There is a lot of stuff that could be different in Plone, but on a basic level they got the right solution for making it possible to do distributed development of products that can still work together. regards Max M ___ 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: Nightly Zope 3 Binary Compiles for WIndows
Chris Withers wrote: Jim Fulton wrote: FYI, there's a similar zip file now containing the same kind of thing for a current Zope3 checkout (s/Zope2/Zope3/ in the URL). If this is good enough for people trying to work from CVS on Windows, let me know and I'll update them from time to time, and maybe move them to a saner location. If it's not good enough, sorry, but I don't anticipate having enough time to do more than this (which is just a trivial zip+upload step beyond the builds I have to do anyway). Thanks Tim. Hi Guys, Saw my name mentioned earlier but not sure whether Tim has solved the problem... I'd be happy to set up a nightly (or weekly, let me know which would be better) scheduled task (see, it's Widnows, there is no Cron, although Schedules Tasks do have a much nicer UI ;-) ) that checked out he latest HEAD of Zope 3, compiled it and PUT it up to my Zope.org member area I think that would be super. Nightly would be best. (I suspect the slowest part of this process will actually be uploading it to Zope.org - what's the plan to fix zope.org speed suckage? how about workflow suckage?) Do you have to go through all of that? Couldn't you put it up as a zip file, using ZMI, rather than CMF API's? Would it be helpful to get the nightly Windows tests running again? I stopped as a corollory of setting up my own company, but also because of lack of perceived support from people who could fix Windows problems I think making the binaries available will widen the pool of people who could fix windows problems. and the lack of caring of developers who only developed for Linux and broke stuff on Windows... has any of that changed? Don't confuse caring with time and priorities. I care about having Zope 3 run on Windows, and Mac OS X, and other platforms. I don't have time to do that though. I think it would be appropriate for others to help by working on windows and Mac OS X (etc.) issues. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: Bug days?
Chris Withers wrote: Lennart Regebro wrote: From: Chris Withers [EMAIL PROTECTED] Whatever happened to the plan to have a monthly bug day on the last monday of each month or somesuch? Nothing, as usual, I guess. Even since bugdays where first thought of, more of then and more regular bugdays have been promised, but it doesn't happen. What would happen if we, as a community, decided to have regular bug-days o nthe last Friday or Monday or every month? Accounce on [EMAIL PROTECTED], [EMAIL PROTECTED], zope.org itself (if it's ever working ;-) ) and the nget together on irc.freenode.net #zope-dev... I don't mind being the official announcer and hassler if people are happy for me to have that role :-) +1 Doesn't really need to be official though, does it? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] copypastemove.ObjectMover / Bug
package/class: zope.app.copypastemove.ObjectMover I think theres a bug or at least to less checks in the ObjectMover method moveableTo(). example that should raise a Error: The objects in a tree: root/folder2/folder2_2 if I copy folder2 to folder2_2 with: mover = IObjectMover(folder2) # or ObjectMover(folder2) if mover.moveableTo(folder2_2): mover.moveTo(folder2_2) the method moveableTo should return False, otherwise we get a tree like: root/ ..nothing.. /folder2_2/folder2 But the method moveableTo() checks just the constraints. Perhaps we can check if the path of the moveable object is somewhere in the path of the target. Regards Roger Ineichen _ END OF MESSAGE ___ 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] Decouple Interface and zope.interface (Martijn was right)
My plan has been to make zope.interface interfaces and Interface interfaces interoperate. Martijn Faassen has been complaining about this for a while, because, to use zope.interface and Interface together required a hard-to-install facade. If we drop the requirement to make the interfaces interoperate (e.g. extend one another, or be used in the same declarations), then, with a small change that Martijn has suggested, we can use zope.interface in Zope 2 without any other changes. The Interface package isn't used very heavily in Zope 2. When it is used, it's used solely for documentation. After further reflection, I don't really see a compelling reason to endure pain to make Interface interfaces usable for Zope 3 interface operations. IOW: Martijn was right and I was wrong. :) I propose to drop the dubious requirement for interoperability between Interface and zope.interface. I propose, instead, to add a requirement that they be able to coexist. This will require changing the name of an attribute used internally by zope.interfaces. It will also allow us to simplify certain aspects of the implementation in zope.interface that exists solely to support Interface interfaces. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] Change in repository approach to software sharing
The Zope project includes a number of interrelated subprojects, such as: - Zope 2 - Zope 3 - ZODB - ZConfig Software from the ZODB and ZConfig projects are shared by Zope 2 and Zope 3. We want this sharing to be very convenient for people working on Zope 2 and Zope 3. We don't want users of the Zope 2 and Zope 3 repository to have to do separate checkouts for ZODB and ZConfig. CVS supports such software sharing through it's module system. The module system has some flaws, so we use symbolic links instead. In a response to: http://dev.zope.org/Zope3/MovingSCMToSubversion John Belmonte has suggested that Zope 2 and Zope 3 should depend on specific versions of shared packages, rather than on the head. I'm inclined to agree. People working on ZODB and ZConfig have to test their changes against both Zope 2 and Zope 3 to avoid breakage. This is very burdensome and causes much pain when they get it wrong. Fortunately, subversion provides a mechanism for sharing specific revisions. We'll be able to have the convenience of getting ZODB and ZConfig (and other shared software) when we do a checkout *and* we'll be able to control what parts we get. To see how this will work, we'll look at ZConfig as an example (because it has a single package) of reusable software that we will include in Zope 3. In the repository, we'll have a top-level Zope3 project directory, with the standard svn subdirectories trunk, branches, and tags. We'll also have a top-level ZConfig project directory. The trunk of the ZConfig Python package will be in ZConfig/trunk/src/ZConfig. If we create a tag T1 of ZConfig, then the Python package for that tag will be in ZConfig/tags/T1/src/ZConfig. Now, when we set up the Zope 3 repository, we will create the ZConfig package in Zope 3 by copying a *tag* from the ZConfig project: svn copy svn+ssh://svn.zope.org/repos/ZConfig/tags/T1/src/ZConfig \ svn+ssh://svn.zope.org/repos/Zope3/trunk/src/ZConfig -m 'Bring ZConfig T1 into main branch' Then, whenever someone checks out the Z3 trunk, they'll get the ZConfig from T1. If we need to, we can even make Zope3-local changes to ZConfig. Later, we may decide to upgrade the Zope 3 head to use ZConfig tag 3. At that point, we can recopy from the tag, or we can merge changes made between the two tags. A similar technique can be used for external software, as described in: http://svnbook.red-bean.com/svnbook/ch07s04.html Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] CVS to svn conversion of the heads this Wednesday
I'd like to plan to convert the repository heads to subversion this Wednesday. I'll confirm this on Tuesday. It will be best of no one does any work on the head on Wednesday. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] Do we need a Packages directory in the new repository
Historically, we've had Packages, Products, Packages3 and Products3 directories in the CBS repository. I wonder of we need these going forward. Perhaps we should just have top-level projct directories in the new subversion repository. In the initial conversion, I plan to convert projects pretty selectively. Initially, we'll convert only parts needed for Zope 2, Zope 3 and ZODB. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] Need help with http://dev.zope.org/Subversion
I copied: http://dev.zope.org/CVS to: http://dev.zope.org/Subversion Can help by converting the Subversion wiki to reflect subversion? :) The new writable subversion repository will be at: svn+ssh://svn.zope.org/repos I hope to have something in place for testing on Monday. For example, to do a writable check out of Zope 3, you will use: cvs co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 I still have to figure out whether to use the sv server or HTTP for public checkouts, but I'll *probably use HTTP, in which case you'd use: cvs co http://svn.zope.org/repos/Zope3/trunk Zope3 for public checkouts. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: [Zope3-dev] Need help with http://dev.zope.org/Subversion
On Sunday 25 April 2004 12:29 pm, Jim Fulton wrote: cvs co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 That should be: svn co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 cvs co http://svn.zope.org/repos/Zope3/trunk Zope3 and this would be: svn co http://svn.zope.org/repos/Zope3/trunk Zope3 -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ 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: [Zope3-dev] Need help with http://dev.zope.org/Subversion
Fred Drake wrote: On Sunday 25 April 2004 12:29 pm, Jim Fulton wrote: cvs co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 That should be: svn co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 cvs co http://svn.zope.org/repos/Zope3/trunk Zope3 and this would be: svn co http://svn.zope.org/repos/Zope3/trunk Zope3 Oops. Thanks. I gues some habits will be hard to kick. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] Weird couldn't load state on Zope 2.6.2
Hi there,
When I click on the Advanced tab of one of my ZSQL Methods, I see this:
Traceback (innermost last):
Module ZPublisher.Publish, line 98, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 39, in call_object
Module Shared.DC.Scripts.Bindings, line 252, in __call__
Module Shared.DC.Scripts.Bindings, line 283, in _bindAndExec
Module App.special_dtml, line 174, in _exec
Module Shared.DC.ZRDB.DA, line 485, in manage_product_zclass_info
Module ZODB.Connection, line 554, in setstate
Module ZODB.Connection, line 590, in _set_ghost_state
Module ZODB.Connection, line 210, in _persistent_load
- __traceback_info__: XXdF
Module ZODB.Connection, line 149, in __getitem__
- __traceback_info__: ('\x00\x00\x00\x00\x00\x08dF',
'(cExtensionClass\nExtensionClass\nq\x01(U\x1dToDoClass_PropertySheetsClassq\x02(cZClasses.ZClass\nPersistentClass\nq\x03cProducts.ZPatterns.PropertySheets\nVirtualSheets\nq\x04cZClasses.Property\nZInstanceSheets\nq\x05tq\x06}q\x07(U\x04iconq\x08U\x00U\n_p_changedq\tK\x01U\x07__doc__q\nU\x19ToDoClass
Property
Sheetsq\x0bU\x11__propset_attrs__q\x0c(U\x05Basicq\rtq\x0eU\x05Basicq\x0f(U\x08\x00\x00\x00\x00\x00\x08d\\q\x10(U\x11ZClasses.Propertyq\x11U\x0eZInstanceSheetq\x12tq\x13tq\x14QU\x06_p_oidq\x15U\x08\x00\x00\x00\x00\x00\x002nq\x16U\n__module__q\x17NU\t_p_serialq\x18U\x08\x038;\xa2\xb7n[\xb3q\x19utq\x1at.N.')
Could not load oid XXdF, pickled data in traceback info may
contain clues.
Where the XX in XXdF are what my mailer is substituting for unprintable
characters.
And in in the event log I see:
2004-04-25T18:42:43 ERROR(200) ZODB Couldn't load state for '\x00\x00\x00\x00\x0
0\x08d'
Traceback (innermost last):
File E:\Zope\2.6.2\lib\python\ZODB\Connection.py, line 554, in setstate
File E:\Zope\2.6.2\lib\python\ZODB\Connection.py, line 590, in _set_ghost_stat
e
File E:\Zope\2.6.2\lib\python\ZODB\Connection.py, line 210, in _persistent_loa
d
(Info:dF)
File E:\Zope\2.6.2\lib\python\ZODB\Connection.py, line 149, in __getitem__
(Info: ('\x00\x00\x00\x00\x00\x08dF', '(cExtensionClass\nExtensionClass\nq\x
01(U\x1dToDoClass_PropertySheetsClassq\x02(cZClasses.ZClass\nPersistentClass\nq\
x03cProducts.ZPatterns.PropertySheets\nVirtualSheets\nq\x04cZClasses.Property\nZ
InstanceSheets\nq\x05tq\x06}q\x07(U\x04iconq\x08U\x00U\n_p_changedq\tK\x01U\x07_
_doc__q\nU\x19ToDoClass Property Sheetsq\x0bU\x11__propset_attrs__q\x0c(U\x05Bas
icq\rtq\x0eU\x05Basicq\x0f(U\x08\x00\x00\x00\x00\x00\x08d\\q\x10(U\x11ZClasses.P
ropertyq\x11U\x0eZInstanceSheetq\x12tq\x13tq\x14QU\x06_p_oidq\x15U\x08\x00\x00\x
00\x00\x00\x002nq\x16U\n__module__q\x17NU\t_p_serialq\x18U\x08\x038;\xa2\xb7n[\x
b3q\x19utq\x1at.N.'))
Could not load oiddF, pickled data in traceback info maycontain
clues
I've never seen anything like this, and I'm certainly not using ZClasses.
Anyone got a clue what's going on?
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
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: [Zope3-dev] Need help with http://dev.zope.org/Subversion
On Sunday 25 April 2004 01:00 pm, Jim Fulton wrote: Oops. Thanks. I gues some habits will be hard to kick. :) Yeah. Of course, CVS isn't just an old habit; it'll still be current practice, not just for Zope 2.6.x and 2.7.x, but for lots of projects. The general pain of two widely-used revision control systems will be with us for a long time. -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ 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] Policy for Collector-Issues 545 and 1217?
Hi, there are two collector-issues related to problems when Zope-Objects get ids like 'content_type' or 'URL1'. I think this problem exists for all names used in the REQUEST-object or general acquisitionable attributes of ObjectManagers. http://zope.org/Collectors/Zope/545 http://zope.org/Collectors/Zope/1217 I don't think that these issues cannot easily be solved in Zope2 without breaking the whole acquisition-magic. What to do? The problem exists, but a fix is hard to find... if at all. Accepting? Rejecting? Cheers, Maik ___ 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] The bleak Future of Zope?
Martijn Faassen wrote at 2004-4-24 22:49 +0200: ... In practice right now the picture is 'Use all of the CMF or none of it'. No, not really... We use SkinsTool, ActionsTool and DCWorkflow a lot, MembershipTool sometimes and most other tools not at all. -- Dieter ___ 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] How should an ideal Zope IDE look like?
[EMAIL PROTECTED] wrote: I agree with Andre. thanks ;-) ... My main concern would be it's adaptibility to custom content types. If I have my own Geospatial-ish content type, how would the IDE handle it ? How would I go about making it handle it ? etc ... Archetypes? But then much more generic than what they are now. -- Dr. Andre P. Meyerhttp://home.hccnet.nl/a.meyer/ TNO FEL Command Control and Simulation, http://www.fel.tno.nl/div2/ Delft Cooperation on Intelligent Systems, http://www.decis.nl/ ___ 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] Policy for Collector-Issues 545 and 1217?
Maik Jablonski wrote: Hi, there are two collector-issues related to problems when Zope-Objects get ids like 'content_type' or 'URL1'. I think this problem exists for all names used in the REQUEST-object or general acquisitionable attributes of ObjectManagers. http://zope.org/Collectors/Zope/545 http://zope.org/Collectors/Zope/1217 I don't think that these issues cannot easily be solved in Zope2 without breaking the whole acquisition-magic. Sure they can. The problem is DTML and people not correctly limiting their namespace stacks when they should. Its not pretty when fixed because the code gets extremely verbose, but thats price of DTML. What to do? The problem exists, but a fix is hard to find... if at all. Accepting? Rejecting? Accept, they are completely fixable. I've probably already fixed those bugs in my fork, I'll hunt around and see if I can find the relevant files and post followups to the bugs. -- Jamie Heilman http://audible.transient.net/~jamie/ ___ 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] Z2 HEAD in rough shape for b/c
Using the HEAD with old databases and code is a real adventure these days for these reasons: - It doesn't start, due to a tiny config bug which I'll check a fix in for shortly. - Many products create instances of the class Persistence.PersistentMapping.PersistentMapping which no longer exists (CMFCore's SkinsTool and CMFDefault DiscussionTool are two of these). These things either need to be migrated somehow to Persistence.PersistentMapping (*before* an update to the HEAD) or we need to provide some sort of b/c alias. That seems tricky given the current source layout. I've added an alias that seems to work: sys.modules['Persistence.PersistentMapping'] = sys.modules['Persistence.mapping'] But this is really odd because I don't know under what circumstance this alias shadows the effect of the line: from Persistence.mapping import PersistentMapping in Persistence's __init__.py module. If there is a shadowing problem with this alias, I'd suggest we go back to the old layout (where there really was a PersistentMapping.py module in Persistence) on the HEAD for sanity's sake. I'm sure there are reasons against this, but the other option is to require every CMF/Plone user to go through a really delicate migration before upgrading to 2.8, which doesn't seem like a good idea. - The HEAD apparently no longer allows URL access to methods that have inherited function docstrings, where older versions did. Lots of things depend for better or worse on this behavior and this breaks a lot of things. They are all shallow fixes (go add a docstring, typically) but it's difficult to figure out where you need to go do this. - The ZODBMountPoint product relies on a method of Connection objects named _getMountedConnection, which apparently no longer exists. This breaks any mounted databases (which breaks dbtab, which breaks sessions, which breaks lots of other things). Hopefully this is simple to fix, I haven't looked yet. - ZopeVersionControl doesn't work anymore due to various ZODB changes. - Various security declarations that used to allow access now deny. Bug reports don't get any more vague than that, but then again nobody's security machinery is any more vague about reporting its reasons for denying access than Zope's. ;-) I can try to make headway on some of this. Is anyone else willing to help? FWIW, after working through (and around) some of these issues I was able to get Plone running on the current HEAD (well, at least plope.com, which uses a lot of Plone), so I can happily report that Zope 2.8 isn't 100% backwards-incompatible yet. ;-) dig-the-hole-and-fill-it-up-again'ly y'rs, - C ___ 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: Mailing Log Entries in 2.7
On Saturday 24 April 2004 06:26 pm, Chris Withers wrote: And there was me looking forward to writing a product that added its own ZConfig section :'( You still can if you like. ;-) Okay, how can I get the log level and exception type into the subject? That's not currently possible, though it wouldn't be hard to add. Perhaps some future ZConfig revision would add this. -Fred -- Fred L. Drake, Jr. fred at zope.com PythonLabs at Zope Corporation ___ 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: [Zope3-dev] Need help with http://dev.zope.org/Subversion
On Sun, Apr 25, 2004 at 12:48:30PM -0400, Fred Drake wrote: On Sunday 25 April 2004 12:29 pm, Jim Fulton wrote: cvs co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 That should be: svn co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 cvs co http://svn.zope.org/repos/Zope3/trunk Zope3 and this would be: svn co http://svn.zope.org/repos/Zope3/trunk Zope3 Does that mean, that Zope will use svn with cleartext passowords for write access? Andreas ___ 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: [Zope3-dev] Need help with http://dev.zope.org/Subversion
Andreas Kostyrka wrote: On Sun, Apr 25, 2004 at 12:48:30PM -0400, Fred Drake wrote: On Sunday 25 April 2004 12:29 pm, Jim Fulton wrote: cvs co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 That should be: svn co svn+ssh://svn.zope.org/repos/Zope3/trunk Zope3 cvs co http://svn.zope.org/repos/Zope3/trunk Zope3 and this would be: svn co http://svn.zope.org/repos/Zope3/trunk Zope3 Does that mean, that Zope will use svn with cleartext passowords for write access? No. If you look at the URI above, you see that we use svn+ssh for writable checkouts. This is essentially just like the SSH tunelling of CVS. Philipp ___ 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 )
