> Troy Curtis Jr wrote:
>> James McCoy wrote:
>>> Finishing(?) and merging the Python3 support would be ideal. That would
>>> give one release for broader feedback before being in an LTS release.
>>
>> It needs to get reintegrated with trunk again with the latest changes, but the linux side of the house was looking good. It was in trying to get my Windows Dev environment back up and running again that got me frustrated and gave me an excuse to wander off doing other things... IIRC, there is a build issue with the Py2 bindings in that branch on Windows, but I never got far enough to check it out.
Stefan Sperling wrote:
> If it helps, we could require Py3-only on Windows, going forward.
> That particular ecosystem has been dragging its feet for long enough ;)
What Py3 support are we talking about anyway? svn build? svn test suite?
swig-py bindings?
Stefan Kueng, how would that be for you and TortoiseSVN? If it's fine
for you, I would be very happy to release Subversion 1.13.0 with Py3 the
only supported version on Windows, if we can get it integrated to trunk
in the next few days.
>> If there was someone who could help out on the Windows side, I can jump in and get the branch up to trunk and retested in order to get this thing over the finish line.
Johan Corveleyn wrote:
> I might be able to devote some time to this in the coming week(s), if
> you can tell me what I need to do / test / validate / ... :-).
Until Troy says something more specific, if you could switch to the
branch, catch-up merge from trunk, and see how much works on Py3 and on
Py2, that would be helpful.
Can someone else check the same on *nix please?
1.13 is a "regular release" with emphasis on new features etc. rather
than stability. Of course we always like to have as much stability as
possible as well, but please let's take this opportunity to get
something of this important work integrated right now rather than
waiting until it's absolutely finished.
- Julian
Received on 2019-09-02 11:45:46 CEST