Comment 1 for bug 1867919

Ok, I guess it makes no sense to stop since we already started going this route - if the MIR team feels that a newer version would be recommended, let's do it. I glimpsed through the changes between v1.4.1 and v1.5.2 and didn't see anything that could potentially break anybody. That being said, let's keep a look out for people reporting new bugs against python-maxminddb suddenly acting crazy.

I approve of this FFe.