-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 4, 2008, at 00:45, Jure Vrscaj wrote:
> Could this be fixed in 1.0? It breaks compatibility, I know. Although I'm not in any kind of position of making such a decision, I can make an educated guess: no. The reason is that most developers currently focus on getting a Django 1.0 out the door, and so there'll be little to no time for a core committer to actually look at the patch and commit it, adding tests and that. That said, you should *definitely* file a bug report, and attach a patch that fixes the misbehavior and also add a regression test. Doubt there'll be any docs needed for this. Also, what compatibility does it break? I can't see how this is a common use-case. Regards, Ludvig "toxik" Ericson [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkhtZp8ACgkQXnZ94Kd6KaettQCfbC6DfVjwbKj+1kcK4lXbnHs0 ar4AniFUpLSjQpe7PBjFnkluGqkSoJVS =o0QH -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
