Re: dh_python and python policy analysis
On Mon, 14 Aug 2006 11:21:07 +1000, Robert Collins <robertc@robertcollins.net> said:
> On Sun, 2006-08-13 at 19:56 -0500, Manoj Srivastava wrote:
>> Here there are two cases. Either module foo can't be written at all
>> for version 2.6, or it the same functionality can be provided with
> This is a little simplistic.
> The parser changes fairly routinely in python versions. This means
> that a version conditional is not sufficient to provide
> compatability with older pythons - the module will not parse.
> The usual thing done for cross version support is to write in the
> older version of python, or in extreme cases (i.e. where performance
> really hurts) have two separate modules _foo_2_5 and _foo_2_6 and
> conditionally do 'from _foo_2_5 import *' etc.
Either conditional code or conditional inclusion are
variations on the common theme I alluded to in my admittedly, and
designedly, simplified example.
manoj
--
There's too much beauty upon this earth for lonely men to
bear. Richard Le Gallienne
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: