From: Kenneth P. <pro...@sk...> - 2004-04-08 20:54:28
|
On Thu, Apr 08, 2004 at 01:22:03PM -0700, Kevin Altis wrote: > We are shooting for PythonCard 1.x working with wxPython 2.6, the next > stable API release of wxWidgets/wxPython. The wxPython 2.5.x API won't > stabilize completely until 2.6 is released, which is this summer at the > earliest, and could be toward the end of the year. If and when the > 2.5.x API changes, each version of PythonCard will have to track those > changes and the minimum version requirement may change until we get to > wxPython 2.6.x. For example, PythonCard release 0.8 may require > wxPython 2.5.1.5 as a minimum and release 0.8.1 or 0.9 might require > wxPython 2.5.2.1, etc. For Debian, I may have a hard time tracking individual releases of wxPython, since I don't maintain that package. We'll have to see. For the time being, the wxPython 2.5 packages are only in Debian's 'experimental' distribution. This is not a mainline distribution, i.e. packages from 'experimental' do not get automatically propogated to 'testing'. This means that whenever you start requiring 2.5, I'll need to release my PythonCard packages to the 'experimental' distribution instead of 'unstable', until 2.5 itself moves into 'unstable'. > A less important decision is whether to require Python 2.3.x or higher. Python 2.3 is the standard Python in Debian 'sarge', which will be the next stable release. I do not (and will not) support any backports to earlier Debian releases, so from my perspective, it would be OK to require Python 2.3. KEN -- Kenneth J. Pronovici <pro...@sk...> Personal Homepage: http://www.skyjammer.com/~pronovic/ "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, Historical Review of Pennsylvania, 1759 |