[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Merging branches/swig-py3 to trunk

From: Branko ─îibej <brane_at_apache.org>
Date: Tue, 22 Oct 2019 21:39:23 +0200

Hi everyone,

The support for Swig bindings for Python 3 (on branches/swig-py3) seems
to be complete. Or at least complete enough that any changes that might
still be needed can be done on trunk. I /think/ that includes
documenting the required Swig version (>= 3.0.9, < 4.0, IIUC).

In light of the conversation about 1.13 and Python 3 support, I propose
that:

 1. we release 1.13.0 as planned next week when the soak period ends
    (pending any last-minute critical bugs found, of course);

 2. immediately after the 1.13.0 release, we merge the swig-py3 branch
    to trunk; and,

 3. proceed with 1.14.0 as planned.

*If* we find there's lots of user demand for Python 3 support, we can
always release 1.14.0 early as a regular release, and make 1.15,
released in April, the next LTS.

Given the planned EOL of Python 2, I will, in the following weeks,
change the (macOS) build slaves I control to build with Python 3 by
default, leaving just the one trunk (and possibly one LTS) build to
exercise Python 2 for the build scripts and bindings. I'm also planning
to add an arm32/Raspbian build slave, but got pre-empted by $dayjob, so
that will have to wait a while.

Last but by no means least, I'd like to thank everyone who helped make
this rather important feature work:

$ svn info --show-item=relative-url
^/subversion/branches/swig-py3
$ svn log --stop-on-copy | egrep '^r\d+ \|' | cut -d '|' -f 2 | sort -u
 cmpilato
 danielsh
 futatuki
 luke1410
 troycurtisjr

-- Brane
Received on 2019-10-22 21:39:27 CEST

This is an archived mail posted to the Subversion Dev mailing list.