Given that PQM is primarily written in python, I'd have to argue that a setup.py is much easier to understand for the majority of people that would be looking to work with the code. By keeping autoconf and automake you are scaring away potential contributors.
Given that PQM is primarily written in python, I'd have to argue that a setup.py is much easier to understand for the majority of people that would be looking to work with the code. By keeping autoconf and automake you are scaring away potential contributors.
I'd vote for moving to setup.py.