I guess I am not getting any of Vaclav's messages from this list, as I didn't get this one either. Not sure why, I don't see any indications in the various spam filters I use. I'll add your address to my whitelists and see if that helps.
I just found out that even wxPython 2.6.0 still uses monolithic build
of wxWidgets on MSW. Is there some deep reason for it? Because wxPython itself was already split into modules, I think it would make
sense to use the standard multilib build of wx as well. Am I missing
something?
There's two reasons, but neither of them are very serious. First is just to be consistent since I need to use monolithic on Mac because of some late-binding issues that break in multi-lib mode. Second is because the way that the wxPython modules are split does not match exactly with the way that the wx libs are split, so you end up with non-optimal dependencies. I tried to rectify some of those in 2.5, but others would have caused some compatibility issues and I was already getting slammed pretty hard on other breaks in compatibility in 2.5. 
wxPython's setup.py is able to handle either type of build (last I checked anyway) so it's not too hard to switch back and forth.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!