Comment 6 for bug 14648

Hi Ron,

> thanks for the detailed description of where things went wrong
> for you, everything is currently in the process of being shuffled
> around to support concurrent installs of 2.4 and 2.5 so some of
> these are known and a different fix is on its way -- as doko noted,
> we don't really _want_ these things to conflict, otherwise it
> becomes very hard for people to migrate from one version to
> the next -- I've got a couple of things queued up while I wait
> for upstream cvs to stabilise around my latest changes again,
> but as soon as we can make a clean snapshot once more I'll get one
> uploaded to fix this and other things.

Thanks for explaining that :) I can see that it is tangled and I'm glad
I'm not the one having to sort it all out...

What happened is that the Debian Women group is running a little bug
squashing effort, in conjunction with the main BSP, so I was hanging
about asking someone if there was a nice easy bug I could look at, and
Steve Langasek suggested 287623, which pleased me because I use
wxWidgets all the time, so I know something about it already. So I
looked to see if there were other overlapping files between wxWindows2.4
and wxWidgets2.5, realised there were quite a lot, and changed the bug
to reflect that (I asked some advice on what to do - as you might guess
I haven't had much practise at this kind of thing, yet).

>>E)
>>wx.pth and wxversion.py
>>are in usr/lib/python2.3/site-packages in wxpython2.5.3
>
>
> This one is curious though, as they surely don't conflict with
> any wx2.4 package. What was the trouble there?

Ahh, sorry! That shouldn't be there. It's a leftover from when I went
through listing things that didn't have "versioned" names in wx*2.5 and
therefore might have overlapping things in wx*2.4. Please ignore that
and sorry for the mistake.

Best wishes,

Helen.