Wireshark-dev: Re: [Wireshark-dev] no more Python 2.1.1
From: Ulf Lamping <[email protected]>
Date: Thu, 19 Apr 2007 19:43:20 +0200
Gerald Combs wrote:
I've checked in a change (in r21459) that should fix the immediate mtime
issue.  The Python section Developer's Guide says "version 2.2 and above
should be working fine."  Should we enforce Python >= 2.2 in autoconf
and/or win32-setup.sh?

Don't know about autoconf, but adding a check to win32 sounds good to me.

However, I don't have a good idea how to actually do it - maybe getting the version string and doing a version string compare in bash ...
Regards, ULFL