On Sat, 2007-03-10 at 17:30 +0100, Marek Kubica wrote: > Hi, > > On Fri, 09 Mar 2007 20:08:41 +1100, Malcolm Tredinnick wrote: > > > I should add: "... and we put a big note in the release notes and on the > > backwards compatible page" if we take option (B). I'm not (totally) > > heartless. > Maybe a warning would be enough? Something like "Django requires MySQLdb > Version X.Y_pZ, older Versions may cause strange errors" might do the > trick. It does not force people to update (which can be hard sometimes) > but tells them what could be causing the problems.
We already have a minimum requirement in the installation docs and it will also probably be in the release notes. However, the more I think about this the more I think we should be throwing an error if they are using an older version, particularly in the new (0.96) release. If you are using the older version you will see bugs. There is no question about this. It's just dangerous in production environments. So we should be up front about it. However, I'm wanting to hear one or hopefully three of other core developers chime in. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
