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

Re: [swig-py3][patch] interfacing bytes object instead of str

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 16 Dec 2018 16:28:03 +0000

Troy Curtis Jr wrote on Sun, 16 Dec 2018 09:59 -0500:
> But there was one item I wanted to talk about related to the patch. I
> agree that "svn_stringbuf_t" => "bytes" and "svn_string_t" => "str" is the
> right general path,

Are you sure about this? Property values can be binary data (so not
representable as 'str') but are usually represented by «svn_string_t *»;
for example, svn_repos_parse_fns3_t::set_node_property().

> but after the patch there is now a "svn_stringbuf_t
> *output" typemap that is still using "PyStr" instead of "PyBytes".
> Further, the only usage of "svn_stringbuf_t *output" is in
> "svn_fs_print_modules" and "svn_ra_print_modules", where the function
> parameter is actually an output parameter, so the appropriate typemap is
> probably "argout" instead of "in".
> Otherwise, the patch LGTM. Yasuhito, if you want to review my changes to
> your patch and perhaps address the issue in the last paragraph then I can
> commit your patch to swig-py3. I'll also start working more on the swig-py3
> branch to get it to the point that we can actually get this branch merged
> into trunk finally.

Great. :-)


Received on 2018-12-16 17:28:20 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.