I had a look at this and it seems like it may be related to the order in which the test cases run. I can reproduce it sometimes with the test setup from the packaging scripts, but not using the ones that we bundle with the package (`python setup.py test`). I've reported it upstream and will continue to look at it: https://github.com/alastair/python-musicbrainzngs/issues/211
Thanks On 19 November 2016 at 16:48, Chris Lamb <la...@debian.org> wrote: > > I'm unable to reproduce the issue. Are you still able to do so? > > Indeed, yes. > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk > `- > >
