On 16.02.2021 20:15, Nathan Hartman wrote:
Update to 1.14.1 break out-of-tree build of python bindings (with python 3.7).Are you building from a distribution tarball? (As opposed to a checkout or export of the 1.14.1 tag in our repository...) If so, did you run autogen.sh? I noticed some changes in
I'm using distribution tarball, `autogen.sh` was not run.
subversion/bindings/swig/INSTALL on trunk that haven't been backported to 1.14.x. It's possible they (or some of them) should be backported. You can generate a diff to view the changes with: $ svn diff \ https://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/INSTALL \ https://svn.apache.org/repos/asf/subversion/tags/1.14.1/subversion/bindings/swig/INSTALL Since your system shows the issue and Yasuhito couldn't reproduce it, would you be able to run a bisect on the 1.14.x branch, between r1877950 and r1886195 to identify which backport commit introduces the problem? That would be an immense help.
I found cause, but as I'm not python programmer, I don't understand it. Old "import _XXX" (like "import _core" in subversion/bindings/swig/python/core.py) works, new "from . import XXX" doesn't. I've patched these lines in 8 files (all in subversion/bindings/swig/python/) and it helps. But I don't know why :) Please note, that I've changed only these lines, I didn't revert whole changes (which is much larger) around these lines. -- // Black Lion AKA Lev Serebryakov
