This was fixed in c1c202e2d45d, which has been in main for a while now.

Fwiw,
on my Windows 2000,

|version 1.0.1+20080525| (Mercurial-1.0.1.exe)
has this bug, importing a patch generated by 'hg export'.

|version 626cb86a6523+tortoisehg| (TortoiseHg 0.4rc2 (installer))
(which includes a much older Hg version) works fine.

Just to clarify, the problem exists in the release installed by the Installer,
_NOT_ in a release that is built locally.

Problem is that demandimport cannot find walk in the canned build (py2exe).

Hmm, I think I ran into the same problem with a locally compiled hg, on Windows
with 2.5. Did you indeed try exactly the same patch? Kind of weird.

I was able to locally compile the sources at rev 1.0.1 on windows with python2.5
and -c mingw32

This version applied the patch successfully. I think therefore we should turn
our attention to the installer and the bundled python and/or modules.

from issue1206

My patch was created by hg export, so the issue is not just limited to mq patches.

Oh, and the workaround would be to use bundle/unbundle rather than import/export.

Adding nosy from issue1206.

I should add that someone had this problem in IRC last night as well, so it
seems this is getting more common (I don't think the reporter for 1206 and the
IRC person were the same, but not sure).

The solution might be to disable demandimport for email, since email has it's
own form of lazy importing, IIRC.

Copying a traceback from duplicate issue1150 for reference:

D:\dsh_bcb>hg import change.patch
applying change.patch
** unknown exception encountered, details follow
** report bug details to http://www.selenic.com/mercurial/bts
** or mercurial@selenic.com
** Mercurial Distributed SCM (version 1.0.1+20080525)
Traceback (most recent call last):
  File "hg", line 20, in <module>
  File "mercurial\dispatch.pyc", line 20, in run
  File "mercurial\dispatch.pyc", line 29, in dispatch
  File "mercurial\dispatch.pyc", line 45, in _runcatch
  File "mercurial\dispatch.pyc", line 364, in _dispatch
  File "mercurial\dispatch.pyc", line 417, in _runcommand
  File "mercurial\dispatch.pyc", line 373, in checkargs
  File "mercurial\dispatch.pyc", line 356, in <lambda>
  File "mercurial\commands.pyc", line 1513, in import_
  File "mercurial\patch.pyc", line 81, in extract
  File "mercurial\demandimport.pyc", line 70, in __call__
TypeError: <unloaded module 'walk'> object is not callable

This isn't really a Windows issue in the sense that it probably happens on other
OSes as well, if they used Mercurial's internal patch code.

Adding Steve and Lee in nosy list

This is a problem with demandimport. email.message.Message() has "from
email.Iterators import walk" in it's class definition, which is apparently
something demandimport cannot handle. I don't know enough about demandimport yet
to fix this, but I'll look into it tonight.

This error is still in crew. Trying to see if I can fix it.

i worn in hg 0.9.5 win32 with win extras installer
using mq i have crate an patch? and try to import and commit it in main pero.
tryint to acces by ./.hg/patches/xxxx was failed, and i copy this patch in parent
dir and try again. this failed too. log and repo attached.