whit wrote:
> Jim Fulton wrote:
>> whit wrote:
>> ...
Specific use cases would help to guide this.
>>> the main usecase for me is the following... hanno writes a recipe for
>>> plone, and I want to use that recipe as part of setting up a
>>> openplans development environment (for example ins
Philipp von Weitershausen wrote:
Rocky Burt wrote:
On Thu, 2007-25-01 at 05:07 -0800, Martin Aspeli wrote:
I do wonder what would happen if you had both
lib/python/Products/CMFCore
and Products/CMFCore, though. Would there be an explicit preference
or would
Zope fail to start up with a confli
Jim Fulton wrote:
Ian Bicking wrote:
Martin Aspeli wrote:
whit wrote:
actually, in my current workplace, workingenv is the standard way to
set up one's dev environment. but in the context of the previous
statement, familar is perhaps a better word.
I'm still not clear how widely used work
On Jan 29, 2007, at 2:25 PM, Ian Bicking wrote:
Jim Fulton wrote:
Similarly, say I had two applications, one in Zope and one in
Pylons, part of the same deployment (possibly interwoven using
wsgi). If I installed elementtree as an egg in buildout.cfg, I'd
expect it to be available to both
On Jan 29, 2007, at 2:03 PM, Ian Bicking wrote:
Jim Fulton wrote:
Ian Bicking wrote:
What I would *like* the distinction between workingenv and
buildout to be is that workingenv is interactive (i.e., install
with easy_install) and buildout is declarative (i.e., specify
your environment w
Jim Fulton wrote:
Similarly, say I had two applications, one in Zope and one in Pylons,
part of the same deployment (possibly interwoven using wsgi). If I
installed elementtree as an egg in buildout.cfg, I'd expect it to be
available to both. If that means patching some of pylon's confg files
Jim Fulton wrote:
Ian Bicking wrote:
What I would *like* the distinction between workingenv and buildout to
be is that workingenv is interactive (i.e., install with easy_install)
and buildout is declarative (i.e., specify your environment with
buildout.cfg).
Well said. I was looking for a
Ian Bicking wrote:
What I would *like* the distinction between workingenv and buildout
to be is that workingenv is interactive (i.e., install with
easy_install) and buildout is declarative (i.e., specify your
environment with buildout.cfg).
Well said. I was looking for a way to bring thi
Martin Aspeli wrote:
>> Unless Utopia really exists I think developers all have their own
>> thoughts about setting up their development environment.
>
> Maybe. Except if we (the plone core developers) use ploneout then we are
> all using the same environment, and we duplicate less work.
Same r
Summary of messages to the zope-tests list.
Period Sun Jan 28 12:00:00 2007 UTC to Mon Jan 29 12:00:00 2007 UTC.
There were 7 messages: 7 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.6 Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Sun Jan 28 21:05:38 EST 2007
URL
10 matches
Mail list logo
