FIX: Changing Python version comparison from StrictVersion to LooseVersion

[hhslepicka]

Due to some bugs with weird Python versions, e.g. 2.7.12+.

As reported by @arkilic, see https://gist.github.com/arkilic/77443a88a77abce029064c6cc21ca828, after the changes he faced an error when compiling pvaPy under system python in ubuntu 16.04 LTS.

@arkilic, please test again with your system that was presenting the error. I did some tests and it works for me here.

[epics-jenkins]

Can one of the admins verify this patch?

[ghost]

Tested locally, fixes the issue mentioned

[ralphlange]

retest this please

[hhslepicka]

@ralphlange , I retested it here on my environment and it works. Would you be able to provide more details? Thanks

[anjohnson]

@hhslepicka The wording of @ralphlange 's message was actually an instruction to our Jenkins CI-server to tell it to go ahead and run the tests on your pull-request, he was responding to the earlier message from @epics-jenkins . For security reasons Jenkins will only test-build a pull-request from a developer who it doesn't know when instructed to do so by one who it does.

Ralph, could adding @epics-jenkins at the start of the message be made to work? That should reduce the confusion about who it's addressing. It would also be helpful if the original message from Jenkins could tell us exactly what we need to say to trigger the pull-request build, I can never remember it...

[hhslepicka]

Ooops... I'm sorry about that! It is the first time that I face this process.
Thanks for clarifying @anjohnson and I'm sorry about the message @ralphlange .