On Jan 31, 3:23 am, "Honza Král" <[EMAIL PROTECTED]> wrote:
> the ticket has been accepted I am only waiting for decision on whether
> to prepend an empty choice ("", "--") or any suggestion on other
> ways of doing that...
In /django/db/models/fields/__init__.py, line 20 there is
# The value
On Jan 30, 9:36 am, "noahz" <[EMAIL PROTECTED]> wrote:
> I ran into the same issue recently, and I got to thinking... Are
> validators going to go away when manipulators do?
I believe they are going away, in favor of creating custom subclasses
of Field and using its clean() method to validate.
>
On Jan 30, 8:37 pm, Vadim Macagon <[EMAIL PROTECTED]> wrote:
> A two line change to BoundField will do the trick, I can submit a patch
> if desired.
I would suggest filing a ticket so that your suggestion and patch
don't get forgotten.
http://code.djangoproject.com/simpleticket
--~--~-
On Feb 2, 3:13 pm, "Ramiro Morales" <[EMAIL PROTECTED]> wrote:
> * A test case that tries to demonstrate it isn't a dupe of #2076 and trying
> to justify a reopen.
FYI, there are a couple other tickets needing reopening too:
http://code.djangoproject.com/query?status=closed&keywords=%7Ereopen&
On Feb 2, 5:29 pm, "Daniel" <[EMAIL PROTECTED]> wrote:
> I would like to implement this as an extension of the existing auth
> code. Is there any interest in a trunk patch to achieve this? If so,
> any suggestions on best practices?
I would suggest taking a look at ticket #3011 (and its attache
Greetings,
I'm developing an application where http://ajaxpatterns.org/
Lazy_Registration">Lazy Registration is on my feature list, and I
believe this can be accomplished pretty cleanly using the django auth
system.
I would like to implement this as an extension of the existing auth
code. Is th
On Jan 28, 2007, at 7:02 AM, ak wrote:
> 1. how do they want to support templates and python code (views/
> scripts) in native encodings if django itself would be all in unicode.
`Why do you need to support it, that's the first question that comes
to mind. If you have input requirements,
decod
On Jan 27, 2007, at 6:44 PM, ak wrote:
> And another thing I still don't understand is: let's pretend I use
> MySQL 4.0 with national charset and my templates are in the same
> charset too. How would work:
It should not work.
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at j
On Jan 27, 2007, at 6:44 PM, ak wrote:
> 1. newforms are with unicode inside
> 2. ORM is with str inside
3. welcome to the world of pain
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You received this message
On Feb 2, 1:17 pm, "Frankie Robertson"
<[EMAIL PROTECTED]> wrote:
> Sorry, I had some trouble understanding your situation. So I'm not
> sure, but isn't this what prefixes are for? I suppose they're a bit
> tedious to use (what with having to inject the id of the child row
> into the clean_data
Adrian Holovaty wrote:
>
> I've
> also taken the opportunity to refactor some admin-specific options --
> raw_id_admin and prepopulate_from -- so that they're defined in the
> "class Admin" rather than in the model fields themselves.
with this change to the raw_id_admin, what is the recommended
> I agree this approach is a huge improvement over the current syntax,
> but I wonder whether it can be expanded even more. Instead of
> dictionaries, let's use objects:
Woah... inline that is specified by objects that can be subclasses?
I'll have to wrap my head around that one.
Would it be pos
On 02/02/07, jfagnani <[EMAIL PROTECTED]> wrote:
>
> I've been using Django for a few months now and have recently started
> looking into newforms. I was hoping that it would solve some issues I
> was having with the old Manipulator/FormWrapper way, but one thing is
> still a little painful to do
Hi,
I've just added in a comment to that ticket:
* A test case that tries to demonstrate it isn't a dupe of #2076 and trying
to justify a reopen.
* A tentative patch that would solve the issue but it depends on the
proposed fix for
ticket #2076 being applied first.
Regards,
--
Ramiro Mo
On Feb 2, 12:01 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> The Jan. 31 deadline for merging the newforms-admin has passed, so I
> thought I'd give a status update:
Kudos on these changes (& newforms, of course). I really like that
admin is now as "legit" as regular forms for public views
The Jan. 31 deadline for merging the newforms-admin has passed, so I
thought I'd give a status update:
I'm really excited about the changes made so far in this branch. In a
nutshell, the way admin options are specified has gotten *much* more
flexible, resulting in easier and more powerful customi
I've been using Django for a few months now and have recently started
looking into newforms. I was hoping that it would solve some issues I
was having with the old Manipulator/FormWrapper way, but one thing is
still a little painful to do when it seems like it could be handled
automatically.
I ha
Hi all,
Could a core developer please take a look and see if this ticket
http://code.djangoproject.com/ticket/1541 can be closed?
This has been discussed here http://groups.google.com/group/django-
developers/browse_thread/thread/9f9f1ff61e9314a5/4a8229f580711c96
and another attempt to initiate
When specifying labels for fields in a newforms Form, I use _()
gettext to provide localized versions of the field label. The problem
is the language may change midway, and the label binding is done at
Form initialization when the class is defined. The following code is
what sets the actually prin
I actually just ran into this problem. I was assuming that if my
form's clean() hook were called, that clean_data would have at the
very least empty entries for the already-validated fields. In my case,
I don't need to do complex validation (database hits) unless the
previous fields are valid, and
20 matches
Mail list logo
