From: Steven P. <n9...@n9...> - 2003-12-04 16:10:34
|
On Dec 4, 2003, at 2:18 AM, Roger Binns wrote: >>>> pubsub.py: >>>> from wx.lib.pubsub import Publication >>> >>> It looks like pubsub is being changed somewhat drastically. >> >> I dunno, I never used the old version. > > The old version doesn't even have a Publication class/member whatever > that is. VERY Strange... I didn't change that bit of code except to make it wx.lib.pubsub isntead of wxPython.lib.pubsub. It was importing Publication in the code I had downloaded from CVS. Anyway, this is irrelevant since we're not going to be concerned about compatibility between versions at this time anyway. :-) > I am not going to switch over to wxPython probably until 2.5.1 > is release (the .0 versions always have issues). You are welcome > to maintain your own set of patches to work with 2.5 but I don't > think it is a particularly good use of your time, especially since > there haven't even been any beta releases yet. Well, it's a good use of my time if it allows me to use the project on my system, which I cannot use otherwise. ;-) I had tried to install the other versions of wxWindows/wxPython/etc and it didn't work, which is why I started down this road to make a version that did. But you are right, as far as the project itself goes, it is a waste of time because any changes that have no chance (any time soon) of getting into the development tree are indeed a waste of time to keep re-implementing. But for me, it works. > Something that is desperately needed on the Mac is to package > everything up into a normal Mac package. I will see what I can do. Theoretically, if everything is bundled right, you may even be able to take a given package and just drop the new .py modules into it to do an update. Maybe. I'm not sure. I'll get back to you on it. Thanks for all your great work, it *IS* much appreciated. Steve -. ----. -.-- - -.-- Steve Palm - n9...@n9... -. ----. -.-- - -.-- |