Hi all. As announced elsewhere (and described in https://dev.launchpad.net/OpenSourcing) , Canonical's Launchpad project is working towards open-sourcing the majority of the code base by this summer. Prior and subsequent to the "grand open-sourcing" date, the Launchpad developers are encouraged to abstract stand-alone code for distributions. Since Launchpad uses several Zope libraries, some of the stand-alone packages may be of special interest to the Zope community. Unsurprisingly (at least if you know Launchpad), the packages use bzr for revision control, and Launchpad for codehosting, bug tracking, and so on. Currently we are standardizing on zc.buildout-based releases for these packages. We have two at the moment: http://pypi.python.org/pypi/lazr.delegates Provides an interesting Python delegation pattern. Uses zope.interface. http://pypi.python.org/pypi/lazr.config Helps build a configuration system (of whatever, but used here for process configuration). I'm not the author, just a messenger and liaison (and the guy who made the distros, in this case). (I did add some cookie conveniences to testbrowser recenty though--check out zope.testbrowser 1.6a1 if you want a look. :-) I, or other folks, will hopefully get a chance to send out other announcements of this sort in the future! Gary
On Tue, Jan 13, 2009 at 1:27 PM, Gary Poster <gary.poster@gmail.com> wrote:
I, or other folks, will hopefully get a chance to send out other announcements of this sort in the future!
Very cool. -- Benji York Senior Software Engineer Zope Corporation
Hey Gary, Very cool to be hearing from the Launchpad project! Am I correct in that lazr.delegates implements a form of the decorator pattern? If so it'd be good if the documentation mentioned this somewhere. I know that Launchpad's use of Zope 3 has been evolving in its own direction for a while, and it'd be interesting to learn more about how. I'd like Zope to be informed by Launchpad's experiences. Things I know from hearing a thing or two over the last years is that Launchpad uses a relational database as its backend, with at least Storm planned for this (whether the transition has been completed, I don't know). I also know that template designers have various convenience adapters available to them within ZPT. There must be much more, however. I'd also like to know which Zope 3 libraries Launchpad currently uses (and what versions), and whether any libraries have been replaced or forked, and so on. Regards, Martijn
2009/1/13 Gary Poster <gary.poster@gmail.com>:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface.
I took a quick view at that lazr.delegates package. The code there is so small, so I think it can be merged in zope.interface itself, because it can be quite useful together with zope.interface's adapter pattern. What are you people think about including delegates code into zope.interface? -- WBR, Dan Korostelev
2009/1/14 Dan Korostelev <nadako@gmail.com>:
2009/1/13 Gary Poster <gary.poster@gmail.com>:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface.
I took a quick view at that lazr.delegates package. The code there is so small, so I think it can be merged in zope.interface itself, because it can be quite useful together with zope.interface's adapter pattern.
What are you people think about including delegates code into zope.interface?
Ah, its GPL. I should have checked out the license before talking about merging. :) -- WBR, Dan Korostelev
On Jan 13, 2009, at 4:15 PM, Dan Korostelev wrote:
2009/1/14 Dan Korostelev <nadako@gmail.com>:
2009/1/13 Gary Poster <gary.poster@gmail.com>:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface.
I took a quick view at that lazr.delegates package. The code there is so small, so I think it can be merged in zope.interface itself, because it can be quite useful together with zope.interface's adapter pattern.
What are you people think about including delegates code into zope.interface?
Ah, its GPL. I should have checked out the license before talking about merging. :)
LGPL, actually! An important distinction. If there were enough interest, I'd certainly be happy to propose it at Canonical and see if it could happen. I think there would be several advocates here. Gary
On Tue, Jan 13, 2009 at 4:14 PM, Dan Korostelev <nadako@gmail.com> wrote:
2009/1/13 Gary Poster <gary.poster@gmail.com>:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface.
I took a quick view at that lazr.delegates package. The code there is so small, so I think it can be merged in zope.interface itself, because it can be quite useful together with zope.interface's adapter pattern.
What are you people think about including delegates code into zope.interface?
-1 lazr.delegates looks very cool, is a small package, and compliments zope.interface well. However, it seems to me that zope.interface stands on its own without it and the two should remain separate. Luckily in today's setuptools-enabled world, adding in a new dependency is easy, so I don't see much reason to merge these two packages. -- Benji York Senior Software Engineer Zope Corporation
Benji York wrote:
On Tue, Jan 13, 2009 at 4:14 PM, Dan Korostelev <nadako@gmail.com> wrote:
2009/1/13 Gary Poster <gary.poster@gmail.com>:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface. I took a quick view at that lazr.delegates package. The code there is so small, so I think it can be merged in zope.interface itself, because it can be quite useful together with zope.interface's adapter pattern.
What are you people think about including delegates code into zope.interface?
-1
lazr.delegates looks very cool, is a small package, and compliments zope.interface well. However, it seems to me that zope.interface stands on its own without it and the two should remain separate.
I agree for the same reasons.... -1. - C
Chris McDonough wrote: [snip]
lazr.delegates looks very cool, is a small package, and compliments zope.interface well. However, it seems to me that zope.interface stands on its own without it and the two should remain separate.
I agree for the same reasons.... -1.
Me too, -1 Regards, Martijn
Hi Gary
Betreff: [Zope-dev] Some tools from the Launchpad project
Hi all.
As announced elsewhere (and described in https://dev.launchpad.net/OpenSourcing) , Canonical's Launchpad project is working towards open-sourcing the majority of the code base by this summer.
Prior and subsequent to the "grand open-sourcing" date, the Launchpad developers are encouraged to abstract stand-alone code for distributions. Since Launchpad uses several Zope libraries, some of the stand-alone packages may be of special interest to the Zope community.
Unsurprisingly (at least if you know Launchpad), the packages use bzr for revision control, and Launchpad for codehosting, bug tracking, and so on.
Currently we are standardizing on zc.buildout-based releases for these packages.
We have two at the moment:
http://pypi.python.org/pypi/lazr.delegates
Provides an interesting Python delegation pattern. Uses zope.interface.
cool ! 1+ for move this to zope.interface Regards Roger Ineichen
participants (6)
-
Benji York -
Chris McDonough -
Dan Korostelev -
Gary Poster -
Martijn Faassen -
Roger Ineichen