On Fri, Feb 5, 2010 at 7:03 PM, FeatherDark <msensei...@gmail.com> wrote:
> Good? :) > Just trying to help. > The errors sure felt real enough, I hope no one else has this problem. > Alex did not say the errors were not real, he said he doubted the problem is the fault of Django and was probably more likely a bug in the package you added -- meaning you'd likely have better luck moving forward on getting a fix by looking into the possibility of it being a bug in that package. In fact other people have had this problem, as a Google search reveals: http://sourceforge.net/tracker/index.php?func=detail&aid=2905909&group_id=78018&atid=551954 It sounds like the problem may be that a DLL is getting loaded twice, under slightly different names. Whatever code includes the assert thinks this may cause a problem, so it dies. Apparently removing the assert has worked as a fix for a couple of people. That may not be a good fix. A good way to proceed would probably be to follow-up on that ticket and see if you can get enough help there to identify what exactly is going wrong and where the fault lies. Starting with the code that is actually issuing the failing assert is likely to be more productive than starting with Django, because nobody who works on Django has a clue what that assert in some other code package is attempting to protect against or what Django (or your application code) might be doing to cause whatever is leading to the assertion failure. Whoever wrote the assert in the first place (or is currently maintaining that code) is far more likely to be able to give guidance on what might be causing the problem and how it might be correctly fixed. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
