[wxPython-users] Multi-version installs, happyness?, feedback please!

[Christopher Barker]

jmf wrote:
> - I gave up with this feature and do no more implement a version
> selection in my code.

I do you it less than I used to -- the days of change in the 2.5 series 
really called for it!

> - To summurize: PLEASE, LET ME SELECT THE WXPYTHON 2.8.N I WISH

I totally agree. I really miss this.

> ... and do not tell me a 2.2m.n+1 is just a debugged release of a 2.2m.n,
> they are just too different.

Well, in theory, they are, but when a new release comes out 
(particularly a pre-release), I like to be able to test it easily, 
without breaking any existing running code.

Christian K wrote:
> why do you want to create software which depends on the minor version number?

I don't, but I do want to test software that way. You can always leave 
off the third version number if you don't want to, which is what I'd 
always do with anything I release (or even use in "production" mode my 
self).

Key is that the third digit has always been optional -- but why remove 
functionality?

Kevin Ollivier wrote:
>  What you're asking for is a way to ignore bugs in later versions of
> a stable release series, but I really don't think we should make that 
> super easy to do, because I think wxPython would be a lot better off if 
> people reported bugs when they found them so that we could once again 
> have the stable releases working as expected.

But having this option makes it EASIER to test, therefor I'll be more 
likely to do it, and we'll find regressions more quickly.

-Chris

-- 
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 at noaa.gov