In working with my recent contrib saga, I've been looking a bit into
newforms-admin, since it's going to be merged someday, and it looks
like it would give me some better options. However, one thing I was
hoping for doesn't seem to be there.
For my policy work, I'd like to be able to add in a
Django-values has had a long and rocky road thus far, with its name
not being the least of its problems. I finally put it to the masses in
a recent blog post, and I got back the simplest word I'm amazed I
didn't think of: policy. Organizations are very familiar with the idea
of policies and
On 5/18/07, Robert Coup <[EMAIL PROTECTED]> wrote:
> What about having a _first_set attribute on the proxy object that only
> allows laziness for the first time the value is set (ie. when it is set
> from the DB row)? Then any later set()s get live validation and coercion
> to geos objects.
I
On 5/18/07, Robert Coup <[EMAIL PROTECTED]> wrote:
> I think eventually, eliminating all the get_XXX_something() methods for
> fields (perhaps with the exception of display) would be an ideal case.
Yeah, get_FIELD_display would be fine, since that's not really
specific to any field type.
> What
On 5/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> No third-party app should expect to be installed in django.contrib,
> because that would require app users to modify their pristine (and
> possibly unwritable) Django source. Presumably django-values was written
> that way as some kind
On 5/18/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> I'm +1 on these changes, including using "!" as the "look somewhere
> else for the password" designator.
Would it really be "look somewhere else for the password" or would it
be more like "if you got this far (all other authentication
On 5/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Nice that it already exists as a standalone app, though, so that people
> can play with it a bit without having to apply patches. That's good
> development practice.
That's been a big part of shaping the current version of the app. I
On 5/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> The only thing holding me back from full support is the name; "values"
> doesn't explain enough about what the app does to me. Yes, it's
> bike-shedding, but Django's always had a nice color scheme. That is,
> names are important (to a
I like that approach to this rather tricky situation. With all my
recent work on DurationField, I took a chance at trying to make your
code into something generic enough to work for both needs, and
possibly others. I'm imagining a FileField that can act as a file-type
object, lazily opening the
I know I've been talking a lot about my DurationField submission
lately, and I finally have some better code to back it up. I just
submitted a new patch for #2443 that addresses the areas Malcolm
recommended to me recently, including newforms-admin.
It's still missing tests and documentation,
301 - 310 of 310 matches
Mail list logo
