Finally, just two questions:
1) Has anybody (can be a user, a tester or a developer) be unhappy
or has issues with 2.5 or 2.7?
I think. No.
2) Does it make sense to have different versions of a library, that
*behave* differently according to the their version?
From this point of view, probably the most stupid thing to do!
Jean-Michel Fauth, Switzerland
jmf wrote:
1) Has anybody (can be a user, a tester or a developer) be unhappy
or has issues with 2.5 or 2.7?
I don't understand the question -- there were bugs, and quite a few API changes (particularly through the 2.5 cycle), but I'm not unhappy about that - that's what development versions are for.
2) Does it make sense to have different versions of a library, that
*behave* differently according to the their version?
Sure it does -- that's why they are different versions! We want wxPython to get better, and that does mean changes, not just bug fixes and added features. Oh, and a bug fix is a change in behavior, too.
From this point of view, probably the most stupid thing to do!
I know what you mean, stability of interface is a good thing, but progress is good, too. Personally, I'd rather see more progress at the expense of API stability on wxPython, but that's just me.
-CHB
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov