On Oct 2, 2008, at 6:37 PM, Ian Bicking wrote:
Jim Fulton wrote:
On Oct 2, 2008, at 6:15 PM, Ian Bicking wrote:
Jim Fulton wrote:
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
On Fri, Oct 3, 2008 at 2:57 PM, Jim Fulton [EMAIL PROTECTED] wrote:
In a system in which most data is managed automatically, asking the user
before doing anything that might remove or overwrite data is, in my
experience, counterproductive. It's like a security system that constantly
asks for
Tarek Ziadé wrote:
[buildout]
...
prompt-before-delete =
var
...
Or maybe:
[buildout]
...
prompt-before-delete =
var/filestorage/*.fs
I like this idea :-)
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Jim Fulton wrote:
Instead of using open(), etc, to write files, there's an instance of
Maker which holds some of the settings (--interactive, --simulate, a
base directory). Then you do all your file operations like:
maker.ensure_file('path/to/file.txt', content)
If that file exists with
On Oct 1, 2008, at 6:34 AM, Tarek Ziadé wrote:
Hello
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
Nevertheless, it happens from time to time that a developer lose some
content
Jim Fulton wrote:
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
Nevertheless, it happens from time to time that a developer lose some
content because of a misconfiguration,
or a zealous
On Oct 2, 2008, at 6:15 PM, Ian Bicking wrote:
Jim Fulton wrote:
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
Nevertheless, it happens from time to time that a developer lose
some
On Fri, Oct 3, 2008 at 12:09 AM, Jim Fulton [EMAIL PROTECTED] wrote:
A better option might be something like move-aside-on-uninstall, which
would move files or directories aside rather than deleting them.
ok why not,
I still think it would be better to just fix the broken recipes.
I agree
Jim Fulton wrote:
On Oct 2, 2008, at 6:15 PM, Ian Bicking wrote:
Jim Fulton wrote:
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
Nevertheless, it happens from time to time that a
On Fri, Oct 3, 2008 at 12:37 AM, Ian Bicking [EMAIL PROTECTED] wrote:
Can you be a little more specific?
Instead of using open(), etc, to write files, there's an instance of Maker
which holds some of the settings (--interactive, --simulate, a base
directory). Then you do all your file
Hello
I know it is a bad practice for a recipe to return some paths that
contains important data in the install() method,
because zc.buildout might remove them.
Nevertheless, it happens from time to time that a developer lose some
content because of a misconfiguration,
or a zealous recipe. That
11 matches
Mail list logo
