Tackling ZODB support in Models

I've been developing some fun stuff with django for about a month now and I've been thinking of taking on a big challenge, adding ZODB support to Models. I _love_ the django models, but there are a few things I wish to do in which I need a full object persistence. I'm sending this to the l

Re: would is_loggedin be better than is_anonymous?

I can see a use case where you use 'anonymous' as a kind of temporary account for users who access the site in some way other than the usual means.For example if a user gets an invitation to something, like an evite or calendar, an url could be generated that auto-authenticated them into the 'anony

CustomAddManipulator -- Is this useful to anyone else?

I have to update multiple models a lot via post, and I love the django AddManipulators but they don't help that much out of the box because they are tied to a specific model. I wrote this as a way to define CustomAddManipulators that relate fields to multiple models and get all the benefit

Re: CustomAddManipulator -- Is this useful to anyone else?

f a model-tied manipulator. -Mikeal On Aug 4, 2006, at 1:46 AM, Aidas Bendoraitis wrote: > > As far as I understand, these two models are absolutely separate (just > haing the same field "blah"). What about models with relationships? I > think, that is a tricky part. Especially, wh

Using test.client.Client.post with body?

I'm a little confused as to how to really use the test client for a json-rpc request. I need to send a serialized object in the body, but the method seems to be designed to simulate form post and may not contain this option. Is there a way to do this that I'm missing or does this need to be

Test framework in memory database

I'm working on adding some selenium support in to the test framework.The first thing i obviously had to do was get the test server up and running at the beginning of the tests. I completed this but ran in to one large issue.The test framework defaults to using an in memory database if it sees that

Re: Test framework in memory database

> Excuse me for being very dense here, but I'm missing what's going on > here. You found a problem with in-memory SQLite and then did or didn't > solve it? Or you just worked around it? Sorry for the confusion. I worked around it. It's still an outstanding issue, I'm not that familiar with the

Re: GSoC 2009: Testing Upgrades/Awesomeness

Figured I should chime in on this. I'm one of the co-creators of the Windmill project and I thought I should clarify the different levels of support Windmill has for django and nose. Windmill tests have a fairly integrated test framework of their own. Many months back we added a feature that all