Marius Gedminas wrote: * distros splitting the Python profiler into a separate package due to licencing problems, with a helpful stub that prints an informational message (go apt-get install python-profiler) instead of raising ImportError. On this one, I raised it with the
Hi everyone, I built my first Zope 3 instance with buildout yesterday. After I got an initial version working, I found it pretty lame to use zope.app.zcmlfiles. With zope.app.zcmlfiles I had 100 eggs without it 84 eggs (this is somewhat project-specific.) However, I had to add several
On 5/23/07, Stephan Richter [EMAIL PROTECTED] wrote: This solution would not be fully backward-compatible with people including package configure.zcml files manually. I think this is okay, since people often do not even want the browser stuff. That's hard to predict; some do, some don't, I
On May 23, 2007, at 12:35 PM, Tres Seaver wrote: I don't know what is blocking a 3.4 release. AFAIK, eggification is on the roadmap for 3.5, right? So we should be focused on stabilizing the last zpkg build, while still allowing the eggified / broken-out project model to move forward.
On 5/23/07, Tres Seaver [EMAIL PROTECTED] wrote: Hmm, the use case for slugs was to support application with separately installed extensions; Fred, I think your view is prejudiced by the fact that you don't have any need for pluggability / extensibility. Possibly so. I'm certainly not
On Wed, May 23, 2007 at 09:37:33AM +0200, Philipp von Weitershausen wrote: Marius Gedminas wrote: On Mon, May 21, 2007 at 10:44:47AM -0400, Jim Fulton wrote: On May 21, 2007, at 1:39 AM, Martijn Pieters wrote: Come again? Using the system python when developing has always been fine;
On May 23, 2007, at 6:40 PM, Brian Sutherland wrote: Hi, In schooltool, we depend on zope.wfmc and zope.app.wfmc, and we want to make a release sometime. Unfortunately it looks like those have never been released with zope 3 or individually. Anyone object to me making a release of these