[Zope-dev] zope.container broken
Hi The zope.container package was broken. I added a missing ComponentLookupError import. Can someone with a linux/windows system release zope.component with the C extensions? Regards Roger Ineichen _ END OF MESSAGE ___ 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: [Zope-dev] choice of test runner...
2009/3/8 Chris Withers : > Wichert Akkerman wrote: >> I would like to see a move away from zope testing frameworks to a more >> standard testing infrastructure: setup.py test, possibly combined with >> using nose. > > I'd love to see a side-by-side feature comparison of the major python > test discovering and runner frameworks. It would then be interesting to > see if there's a compelling enough reason for The Zope Framework > steering committee to make a pronouncement on which one to use... +1 -- WBR, Dan Korostelev ___ 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: [Zope-dev] deprecating the deprecation system?
Hi Chris > Betreff: Re: [Zope-dev] deprecating the deprecation system? > > Martijn Faassen wrote: > > Thoughts? > > + sys.maxint to all of that from me :-) > > I think documenting that something is going to go away is > useful, but ultimately, people only really worry about it > when something stops working. > > I've got way to bored to the millions of meaningless > deprecation warnings emitted by *released* zope/plone/blah > versions over the years... Millions, that doesn't sound like serious statement. Can you give an example of a meaningless deprecation warning? I don't know of any useless deprecation message. Every message makes me faster if I update my or zope code. Could it be that you depend on packages for a long time which deprecated code and don't have time to update them? I allways update my projects and migrate them if I work on something. This way I don't see any deprecation message on my production system. Or if so, I know what I have to for a next release. Regards Roger Ineichen > Chris > > ___ > 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 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: [Zope-dev] non-zodb persistent registries
Tres Seaver wrote: >> The reason being that, for a long time, I've wanted to see a persistent >> registry that stored in a rdb rather than zodb. > > I don't know what that would look like. I have ideas about what I'd like it to look like from a user's perspective, but sadly not much in the way of code, rdb schema, etc... >> However, I'm a bit stumped at how to implement this and certainly having >> the zodb-based registry mixed in with the zope.component code confused >> the hell out of me when I last looked. The one that particularly got me >> was how, in a multi-process/multi-thread setup such as a wsgi app, you >> would get other threads'/processes' registries to update themselves when >> a registry in one thread/process was changed. Any ideas how to do this? > > Nope. I've never given it any thought. I have, and as a result I'd happilly *pay* someone else to develop a decent solution ;-) >> We do actually have this problem with the text-file based registry, it's >> just that we accept a restart of the server is needed when that text >> file changes. A "nice to have" would be an equivalent of apache's reload >> command. > > I don't actually understand the usecase: changing configure.zcml is a > development activity, not a sysadmin one. Yeah yeah, whatever ;-) I'm a developer, and I edit httpd.conf plenty, I think this distinction is pretty meaningless... >> Is anyone else interested in this kind of stuff? > > Theoretically, yes. Practically, no: I'd rather keep my startup times > under a second. ;) Well, what I really care about doesn't actually have to do with startup times. I'd like sub-second startup times too, but I'd also like to have an ISite (what a horrible, wrong name :-S) implementation that worked in a multi-threaded and/or multi-process environment and didn't store its data in ZODB. I'd *also* like: >>> a = root.siteA.objecta >>> b = root.siteB.objectb >>> a.__class__ is b.__class__ True >>> adapter1 = getAdapter(a,ISomething,context=a) >>> adapter2 = getAdapter(b,ISomething,context=b) >>> adapter1.__class__ == adapter2.__class__ False ...if you see what I mean? (ie: adapter lookup based on object traversal path rather than some notion of "current overall request traversal path", which doesn't make sense if siteA and siteB register different ISomething adapters for a.__class__. Of course, having ISomething(a) and ISomething(b) do this would be super super cool ;-) As I said, I'm prepared to pay for anyone who can make this happen :-) cheers, Chris ___ 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: [Zope-dev] deprecating the deprecation system?
Chris Withers wrote: > I think documenting that something is going to go away is useful, but > ultimately, people only really worry about it when something stops working. I think it's not that simple. Look at the amount of work people put into the Zope stack in recent month to get rid of DeprecationWarnings for the sha, md5 or sets modules or various other warnings emitted by Python 2.6. There's lots of energy spent on those warnings *before* they break anything. > I've got way to bored to the millions of meaningless deprecation > warnings emitted by *released* zope/plone/blah versions over the years... Yes, me too. But I feel our use of the system wasn't very good. I have seen people putting in deprecation warnings for things they didn't like, but without there being an alternative. At other times we deprecated particular single methods of something to move them some place else without much clear win. To me it seems that we get warnings from the Python level on a somewhat broader level, like: the entire package X is going away, use Y now. The message itself is short and concise, but you can look up detailed documentation about the new package and its API. There must be something to learn from that. Hanno ___ 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] choice of test runner...
Wichert Akkerman wrote: > I would like to see a move away from zope testing frameworks to a more > standard testing infrastructure: setup.py test, possibly combined with > using nose. I'd love to see a side-by-side feature comparison of the major python test discovering and runner frameworks. It would then be interesting to see if there's a compelling enough reason for The Zope Framework steering committee to make a pronouncement on which one to use... cheers, Chris ___ 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: [Zope-dev] deprecating the deprecation system?
Martijn Faassen wrote: > Thoughts? + sys.maxint to all of that from me :-) I think documenting that something is going to go away is useful, but ultimately, people only really worry about it when something stops working. I've got way to bored to the millions of meaningless deprecation warnings emitted by *released* zope/plone/blah versions over the years... Chris ___ 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] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sat Mar 7 12:00:00 2009 UTC to Sun Mar 8 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 7 20:23:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011247.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 7 20:25:50 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011248.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 7 20:27:50 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011249.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 7 20:29:51 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011250.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 7 20:31:52 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011251.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 7 20:33:53 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011252.html ___ 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 )
