Wireshark mailing list archives

Re: Supported Python versions?


From: Guy Harris <guy () alum mit edu>
Date: Tue, 24 Mar 2015 10:47:09 -0700


On Mar 24, 2015, at 10:17 AM, Peter Wu <peter () lekensteyn nl> wrote:

On Sun, Mar 22, 2015 at 04:58:14PM +0100, Pascal Quantin wrote:
2015-03-22 16:48 GMT+01:00 Peter Wu <peter () lekensteyn nl>:

Hi,

Triggered by a build error due to html2text.py, I have recently started
with adding Python 3 support to various Python scripts[1][2]. The change
to html2text.py[1] was tested with Python 2.6, 2.7, 3.2 and 3.4.

The configure script however checks for Python >= 2.5 which was first
released in 2006 with the last security update in 2011. This version
also lacks support for nice language constructs such as 'with'.
checklicenses.py is already incompatible with this.

Any objections if this gets bumped to 2.6 or even 2.7? The
dfilter-test.py script already requires 2.7 (or newer).


Hi Peter,

the OSX 10.5 x86 buildbot still runs Python 2.5, so bumping the minimum
Python  version would require updating the buildbot. So it's better to keep
compatibility for the scripts used during build steps.

Pascal.

According to the ComputerWorld source listed by Wikipedia[1], OS X 10.5
became unsupported since June 2011. Python 2.5 also does not receive
security updates anymore. (OS X 10.6 has Python 2.7 which is still
supported.)

The OS X x86 buildbot is running 10.6 (and building against the 10.5 SDK and building with a "minimum deployment 
version" of 10.5).

So the question is whether we care about users trying to build Wireshark on a 10.5 system.  macosx-setup.sh doesn't 
work on 10.5, when last I looked at it, so it's a bit harder to set up building on 10.5.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: