On 08/06/12 20:01, Anssi Kääriäinen wrote:
> On 8 kesä, 19:42, Carl Meyer wrote:
>> Yuck. I am not at all convinced that this cure isn't worth than the
>> disease. In every case where Django has introduced flattened
>> pseudo-namespaces in place of Python's existing namespace system, I think
>> it
On 08/06/12 17:42, Carl Meyer wrote:
> Hi Andrew,
>
> On Thursday, June 7, 2012 11:17:51 AM UTC-6, Andrew Godwin wrote:
>
> - Requiring that all fields expose a method which says how to
> reconstruct them.
>
> Essentially, it returns the positional and keyword arguments you would
>
On 08/06/12 16:45, Jacob Kaplan-Moss wrote:
> Hi Andrew --
>
> Generally I'm +1, and I think I see the point pretty clearly. Just a
> couple of questions:
>
> On Thu, Jun 7, 2012 at 7:17 PM, Andrew Godwin wrote:
>> - Requiring that all fields expose a method which says how to
>> reconstruct the
On 08/06/12 16:16, Anssi Kääriäinen wrote:
> I did a little digging into South code, and I think I now understand
> the needs. Basically, when you migrate a model, you might need to read
> the database data by using the old model definitions. You can't use
> the currently installed model definition
On 08/06/12 18:16, Michael Manfre wrote:
>
>
> On Thursday, June 7, 2012 4:16:12 PM UTC-4, Alex Ogier wrote:
>
> This isn't particularly robust. The SQL string generated by a
> particular backend isn't considered part of any API, and might change
> formatting or semantics on minor up
