Ignore that. The version that p2pool advertises is not based on the code itself, but instead on the git history of the branch that you're logged into. Specifically, p2pool runs "git describe --dirty --always" in order to determine its version number. git describe will look for the most recent tag that is reachable from a commit. As I haven't tagged any new versions yet (though I totally should have), git describe doesn't say anything helpful. For some unknown reason, it shows up as 16.0-7-* on my nodes but 15.0-43-* on the nodes that other people have made from cloned repositories, even though the code is exactly the same.

If you run "git log", that will list the most recent changes that were made on the branch you're using. As of today, the most recent commit should be:

commit cc6fd7d227f869aa02cdf9f89e8349aa9d2a4344
Author: Jonathan Toomim
Date:   Wed May 10 06:11:49 2017 -0700

    Don't attempt retransmission of shares when transactions are missing (avoid hang on sync)