Re: Proposal: allow optional user-defined functions to be passed into serializers.deserialize()

2008-01-30 Thread Wyley
In case anyone is interested, I have come up with a solution to the problem of importing foreign data that seems to work pretty well, at least for my project. The components are as follows: 1. A custom Serializer/Deserializer pair of classes which are subclassed on those in django.core.serializ

Re: Proposal: allow optional user-defined functions to be passed into serializers.deserialize()

2008-01-26 Thread Wyley
Jacob, Thanks for your feedback. > Though I see what you're trying to solve here, I can't quite see how > this actually improves anything. That is, what's the difference > between your proposed:: > > objs = deserialize("xml", stream, map=some_function) > > and the possible-right-now:: > >

Proposal: allow optional user-defined functions to be passed into serializers.deserialize()

2008-01-25 Thread Wyley
Hi everyone, Below is an idea I've got for how to make the deserialization interface a bit more flexible, since I and other users have expressed a need for it. I am willing to work on implementing this idea (indeed, I will probably need to, even if it's just for my own project), but I wanted to