Nicolas Lehuen wrote .. > 2006/2/2, Graham Dumpleton <[EMAIL PROTECTED]>: > > > The only > > > problem is that apache.import_module is still as crappy as ever and > > > that we don't have any grand unified theory of module importing that > > > would support both handlers and published modules. > > > > Actually I do believe I have a grand unified theory and I have working > > code for it was well. I simply gave up pushing it some time back because > > the initial discussions I started about it on the mailing list > > degenerated into a multitude of threads with everyone giving their own > > viewpoints, with many not really understanding what I was proposing and > > others not understanding why it had to be changed anyway. Thus I gave > > up and reverted to just documenting the issues I find on my web site. > > In time I will also add documentation for how my proposed changes and > > code actually address or don't address the issues I have documented. > > Until that is done, making any code available isn't going to help. > > > > Graham > > > > Don't worry, I'm aware of what you did and what you have up your > sleeves :). It only reinforce my feeling that we should release the > 3.2.X ASAP so that we can switch to 3.3 development and solve this > issue once and for all.
Which is why I have been in part been acting like a release Nazi in trying to get 3.2.6 released as final and avoid any further delay. I was so restricted last year from progressing much of anything because of personal happenings in my life, and now that I am free once again to be coding, much pent up energy for moving forward a lot of things. Although, my new wife would be much happier if I directed this energy towards finishing the documentation on my own software rather than working on mod_python. ;-) Now, I have to say though that the stat.ST_MTIME issue is probably enough to say that there should be a 3.2.7. That is one that really could come back to bite us if there is a portability issue with it. It might even be a good idea if both Jim and I, and anyone else who wants to, have another quick look over that code to make sure there are no other non obvious gotchas in there as not sure how much it may have been reviewed by others. We should also agree that if we do do a 3.2.7 what will be fixed in it and this time set a strict time frame on how long we let it be tested. Do we leave it at stat.ST_MTIME, or also add the connection handler fix as well if we are happy with that? Is a "b" designation needed or are we happy to try from a real release candidate again? > Having read your work on Vampire (and its > module importing mechanism) I'm pretty sure it won't be long. The new importer is actually a complete rewrite and some things are done quite differently to what was done in Vampire. I have in effect rewritten most of what is currently in the mod_python.apache module, which is why you kept seeing me posting all manner of wierd problems in JIRA of late. You may be happy to know though that only a one line change is required in your current incarnation of mod_python.publisher. Namely: module = page_cache[req] gets changed to: module = apache.import_module(req.filename) That may even tell you something about what I will be proposing. And yes it is backwards compatible. BTW, I now have SVN commit access. So will not be expecting you guys to do all the hard work of trying to integrate all the fixes I have been posting on JIRA. As to the module importer, wasn't expecting to be integrating that real soon. Was planning on providing a separate package that people could install against 3.2.X which allowed them to try it out and see if it works on existing code and thus whether it is acceptable or not. Graham
