HTTP 500 error since HG 1.9/1.9.1 - was fine previously (until HG 1.8.4)

[Lionel]

Is there any further trace/log I can activate, or kind of debugging, to get
more info?

(You were right - I made replies and not replies to all...)

-----Message d'origine-----
De : Adrian Buehlmann [mailto:adrian at cadifra.com] 
Envoyé : jeudi 18 août 2011 10:47
À : Lionel
Cc : mercurial at selenic.com
Objet : Re: HTTP 500 error since HG 1.9/1.9.1 - was fine previously (until
HG 1.8.4)

(please keep the list cc. Re-adding the list cc)

On 2011-08-18 10:13, Lionel wrote:
> Hi Adrian,
> 
> Indeed, the list of installed software in my first mail was scrambled - I
> have both python 2.7 64 bit (coming from python-2.7.2.amd64.msi) and
pywin32
> (pywin32-216.win-amd64-py2.7.exe). I didn't know that with HG 1.8 onwards,
> pywin32 was no more necessary for HG itself but, however, it is necessary
> for isap_wsgi.

Ok. In any case, installing pywin32-216.win-amd64-py2.7.exe shouldn't
harm Mercurial. Mercurial 1.8 and onward just won't use it.

> The two commands ctypes.util.find_msvcrt and
> ctypes.PyDLL(ctypes.util.find_msvcrt()) run fine (only diff is the output
> "handle 70060000 at XXX" where my XXX is slightly different but I assume
> it's specific to each pc).

Yeah. Don't bother about the handle value.

Ok. So we know ctypes is there and can at least be found when running
the python interpreter.

Question remains why it fails from within IIS.

> Note that the reason why I use pure python rather than a precompiled
package
> is because precisely, wih the precompiled packages, hgwebdir_wsgi.py
> couldn't find msvcrt90 (see my answer to Mads to see the trace in that
> case).

Which answer? I haven't seen it. I see no answer to Mads' mail. Did you
forget to cc the list in that answer too?