@jfernandz The main project and the python bindings are built from the same sources released at the same time, hence the split package. This is the correct arrangement and your AUR tooling should be fixed to handle this, there are many such projects around.
There is no pjusa package listed in official Arch repos or the AUR, so there is no reason for this package to list it as a conflict. If there are externally built packages somewhere the onus is on them to mark conflicts with anything available in the Arch ecosystem. Anything installed from source is on you.
Pinned Comments
alerque commented on 2020-02-22 05:37 (UTC)
PSA: I've started hosting this and also many other packages I maintain in the AUR as prebuilt packages in my repository for those that want to install them using
pacman
without messing around with building from the AUR.