On 2/25/08, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> what was the problem?
Just something weird where the timeline forgot about all the word we'd
done over the past eight months or so. trac-admin resync kept failing,
but the tenth or so time I tried it worked.
Jacob
--~--~-~--~---
On 25-Feb-08, at 11:45 PM, Jacob Kaplan-Moss wrote:
>> I'll have it fixed as soon as I can figure out what the hell's
>> going on.
>
> OK, fixed.
what was the problem?
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Foss Conference for the common man: http://reg
On 2/25/08, konryd <[EMAIL PROTECTED]> wrote:
> The modelforms, however, don't have that feature. I nees to set the
> instance, or the initial data every time I instanciate a form.
Or, if you've always got the same initial object, simply override
__init__ to work the way you'd like. For example
I really liked the two, now deprecated, methods (form_for_model and
form_for_instance) for working with newforms. I could reuse the dead-
simple logic (if post: validate and save else: display once again) and
pass the generated Form class in both add and edit. Let me show you:
def processForm(Pro
On 2/25/08, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> I'll have it fixed as soon as I can figure out what the hell's going on.
OK, fixed.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develope
Howdy folks --
Quick note: I just broke Trac. Don't worry - no data's been lost, but
something's borked with Trac's SVN history browsing and such. I'm
working to fix, but just wanted to let y'all know so there's no
freaking out.
I'll have it fixed as soon as I can figure out what the hell's goin
