2009/7/1 Alexander Belchenko <email address hidden>:
> Martin, why is there separate packages for each Linux distro? Why is
> there separate packages for each Ubuntu version?
>
> Because they're different?
>
> That's why there is different installers for different python versions @
> win32, because there is compiled C/Pyrex extensions, and these
> extensions are built against specific python version. You can't
> workaround this fact.
Perhaps the bug title is unclear. Yes, of course it makes sense that
there are different builds for different python versions. The problem
as I see it is the distinction between the python-based installers and
bzr.exe. Is that really needed?
On Ubuntu, there is just one bzr package, which (in Jaunty, as of
1.16+4485+116) includes extensions built against python2.5 and 2.6,
and it can be imported as a library by plugins. It would be nice if
we could get closer to that on Windows.
2009/7/1 Alexander Belchenko <email address hidden>:
> Martin, why is there separate packages for each Linux distro? Why is
> there separate packages for each Ubuntu version?
>
> Because they're different?
>
> That's why there is different installers for different python versions @
> win32, because there is compiled C/Pyrex extensions, and these
> extensions are built against specific python version. You can't
> workaround this fact.
Perhaps the bug title is unclear. Yes, of course it makes sense that
there are different builds for different python versions. The problem
as I see it is the distinction between the python-based installers and
bzr.exe. Is that really needed?
On Ubuntu, there is just one bzr package, which (in Jaunty, as of
1.16+4485+116) includes extensions built against python2.5 and 2.6,
and it can be imported as a library by plugins. It would be nice if
we could get closer to that on Windows.
-- launchpad. net/~mbp/>
Martin <http://