Re: 1.13.x and swig-py3

2019-10-22 Thread Nathan Hartman
I'll respond to Mark, Julian, Stefan, and James below... Mark Phippard wrote: > I thought the frequent release/LTS plan was a worth a try, I just do > not see where it is working out and yielding benefits. I'd like to point out that I have made several proposals but was (politely) reminded that w

Re: 1.13.x and swig-py3

2019-10-22 Thread James McCoy
On Mon, Oct 21, 2019 at 01:35:45PM +0200, Branko Čibej wrote: > On 21.10.2019 13:16, Julian Foad wrote: > > Johan Corveleyn wrote: > >> Nathan Hartman wrote: > >>     Branko Čibej  wrote: > >> > By the principle of least surprise, I think it > >> > would be better to merge to trunk, creat

Re: Supported SWIG version on swig-py3

2019-10-22 Thread Yasuhito FUTATSUKI
I ran check-swig-{py|pl|rb} with some SWIG versions on swig-py3 branch. Environment: OS: FreeBSD 11.2 Python 2: 2.7.16 Python 3: 3.7.3 Perl: 5.28.2 Ruby: 2.5.5p157 Results are below. SWIG 1.3.24: I couldn't build swig itself. SWIG 2.0.0: Python 2 ... OK (skipped=1) Python 3

Merging branches/swig-py3 to trunk

2019-10-22 Thread Branko Čibej
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

Re: 1.13.x and swig-py3

2019-10-22 Thread Stefan Sperling
On Tue, Oct 22, 2019 at 10:13:04AM -0400, Mark Phippard wrote: > I do not think the current 1.13 release is worth releasing. I think we > should merge the Py 3 branch and release that as 1.13 once we think it is > ready. That should essentially become the release we maintain until there > is some

Re: 1.13.x and swig-py3

2019-10-22 Thread Mark Phippard
Julian's email reminded me I planned to reply to this one. On Mon, Oct 21, 2019 at 10:59 AM Stefan Sperling wrote: > On Mon, Oct 21, 2019 at 10:25:01AM -0400, Mark Phippard wrote: > > Yes. Go back to having new releases when there is enough interesting > > content to justify the release. We ca

Re: 1.13.x and swig-py3

2019-10-22 Thread Julian Foad
Stefan Sperling wrote: [...] it sounds like we are very close to having full support for Python 3 on trunk already or will have it soon. Which means it will be ready in time for 1.14 LTS as originally scheduled. Is that really not enough? Stefan, thank you for articulating so clearly, especial