[Zope-CMF] sluggish images in CMF?

Dieter Maurer dieter at handshake.de
Sun Dec 5 06:36:52 EST 2004

Hi Chris,

Chris Withers wrote at 2004-12-4 16:54 +0000:
>Dieter Maurer wrote:
>>>Are there any open collector issues for this?
>> Unless you (or someone else) closed it inadequately!
>Well maybe you could be so good as to give me a link to it, or even just 
>the issue number would be fine? ;-)

You already know: I never search for others...

It is the one we have had a lengthy discussion about...

>> The extreme slowness with debug mode on Windows (due to
>> excessive "os.path.walk") is still there, in any case!
>What version of CMF are you referring to?

CMF 1.4.

>As I said, in 1.5 there only 
>appears to be one platform dependent path. That does involve a 
>path.walk, but there's a very clear comment just above that explainign 
>why it's there.

The cause for the slowness is the "badOS=os.name=='nt'"
in ".../CMFCore/DirectoryView.py".

I doubt that the comment (yes, there is one) truely reflects
what Windows does. Rather, I expect that the comment was inspired by
the limited time resolution effect (we discussed it for
a long period) that caused test failures.

I am not sure, though, as I do not use Windows...

But even when I were wrong (and the comment true),
there is no need to walk the complete
tree; checking just the content of the current directory (with "os.listdir")
(without sub-directories!) would be sufficient!


More information about the Zope-CMF mailing list