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

Re: [offlist] Re: Merging branches/swig-py3 to trunk

From: Yasuhito FUTATSUKI <futatuki_at_poem.co.jp>
Date: Sat, 23 Nov 2019 14:37:46 +0900

On 2019/11/12 12:13, Nathan Hartman wrote:
> On Fri, Nov 8, 2019 at 3:13 AM Julian Foad <julianfoad_at_apache.org> wrote:
>
>> Nathan Hartman wrote:
>>> Question: Some Python scripts have not been updated for Python 3.x
>>> yet. Should those be listed in the release notes under "Known Issues"?
>>> Should a bug be filed? Or both?
>>
>> Both: an Issue tracking which ones are known broken or untested, and a
>> pointer to it in the release notes.
>>
>
> Recently, Yasuhito posted a thread titled "List of Python scripts
> importing svn.*" I think those are the scripts that need to be checked
> for Python 3 compatibility? Or is it necessary to check all Python
> scripts?

Perhaps it is necessary to check all Python scripts except those we
use on build and release which are already checked.

At least I found those in tools/server-side couldn't work on Python 3:

tools/server-side/fsfs-reshared.py
     (try to write str object on binary mode stream in
      write_fs_format())
tools/server-side/svn-backup-dumps.py
     (fixed in r1870204)
tools/server-side/svnpredumpfilter.py
     (AttributeError: module 'string' has no attribute 'strip')
tools/server-side/svn_server_log_parse.py
     (import svn.core, bytes vs str)
tools/server-side/test_server_log_parse.py
     (import svn.core, bytes vs str)

(I didn't check files in tools/server-side/svnpubsub)

Cheers,

-- 
Yasuhito FUTATSUKI <futatuki_at_yf.bsdclub.org>/<futatuki_at_poem.co.jp>
Received on 2019-11-23 06:38:49 CET

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