The issue here is pretty convoluted: the setup.py method of building was
originally added primarily to support shipping python-bindings as a separate
tarball, to support building multiple versions of the bindings. The former
never happened, and to support Py 2 vs 3 people have been building the bindings
in-tree with the setup.py method, which never really really worked.
Now that that Python 2 is no longer supported at all, I think the solution to
this is either axe the setup.py method entirely, or make it error-out if trying
to build in-tree.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/130#issuecomment-605944390
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
