Originally reported at https://github.com/legoktm/toolforge/issues/12
With the recent internal rename of the webservice package to use toolforge, there's now a naming collision between that and the toolforge helper library I maintain.
Luckily there is not any practical impact yet because the webservice one is Python 2 only while the helper library is Python 3 only. However it's definitely confusing that import toolforge can do 2 different things.
I'd suggest renaming the webservice package to something else, mostly because that can be done all in one repository versus updating a bunch of tools.