Fair enough. Forget I mentioned it :-/
On Fri, Feb 22, 2008 at 1:20 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> I agree with Graham because you don't know where python will be
> executed from what would the path be relative to?
>
> On Feb 22, 9:33 am, "Justin Lilly" <[EMAIL PROTECTED]>
I agree with Graham because you don't know where python will be
executed from what would the path be relative to?
On Feb 22, 9:33 am, "Justin Lilly" <[EMAIL PROTECTED]> wrote:
> I would personally vote on making it an optional parameter if RELATIVE_FIELD
> (or something like that) is present. If
I would personally vote on making it an optional parameter if RELATIVE_FIELD
(or something like that) is present. If it isn't present, require it just
like always.
-justin
On Fri, Feb 22, 2008 at 9:46 AM, Graham Carlyle <
[EMAIL PROTECTED]> wrote:
>
> In your example I think RELATIVE_FIELD would
In your example I think RELATIVE_FIELD would be relative to the django
python process's current working directory which seems a bit arbitrary.
Having an absolute path parameter seems a good thing, but storing this
prefix for each record seems redundant and inflexible.
Graham
On Fri, 2008-02-22 a
What would stop you from doing something akin to:
upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
recursive=True)
where RELATIVE_FIELD is defined in your settings.py file? Perhaps I've
missed the mark on this.. I'm relatively new to django-dev discussions.
-justin
On Fri, Feb
I'd like to request that FilePathField should have an extra option that
causes it to only save a relative path (to the path parameter), say
called "relative".
Having an absolute path stored makes it harder to move data between
machines that are set up differently (say development and production)
