Howdy FeatherDark, I've been looking for an answer to this same error, might have found a "solution" for you - it's worked for me anyway.
Just a quick description of how the problem came about for me - I have two Django based web sites running under the same Apache HTTP server; once the HTTP service was started (or restarted) whichever site was accessed first was fine and would continue to work, but the second one would fail immediately with the "old_mod" assertion error. This behaviour seems to fit the theory mentioned by Karen Tracey that the problem arises because a DLL is being loaded twice... but that doesn't make the problem go away. Anyway, on to the bit you really want to know - I was using the latest pyWin32 build available from the download site (build 214 at the time of writing), so I uninstalled that and started working backwards through the previous releases. Luckily I didn't need to go too far - for me build 212 made the problem go away. Looks like there may be a bug in the newer package. So not really a fix, as such, but... Worth a try, anyway, unless you need the latest build for some particular reason, of course. Cheers! On Feb 6, 7:47 am, FeatherDark <msensei...@gmail.com> wrote: > So I installed pyWin32 today and all of my Django sites went POOF into > non-happyland > > I was prompted to post so here's a dpaste of just 1 of the errors in > the apache log > > I removed pyWin32 and all my Django woes vanished... other than I > needed pyWin32.... > > http://dpaste.com/155209/ > > assert sys.modules[modname] is old_mod -- 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.
