Conflict Unload: remove multiple loaded modules matching one conflict constraint #215

Something weird we stumbled upon in 4.2.1 in this regard
module use ~/modules
module add python
module add python/3.6.0
module add mymodule
Loading mymodule
ERROR: mymodule cannot be loaded due to a conflict.
HINT: Might try "module unload python" first.

cat ~/modules/mymodule
#%Module1.0
module rm python

At the point mymodule is added, python/3.5.0 and python/3.6.0 are present.

Originally posted by @wenzler in #198 (comment)

There is no conflict declaration in the python modulefiles. it simply prepend path stuff in there but as soon as there are several versions of the same software loaded mymodule breaks it