This message was deleted.

Hi @Jack Norman, a BentoML service consists of multiple components, namely API and Runner Servers. A service object would need to know about the runners (through the

runners

argument) to start. Being able to use the runner handle in the global scope can be simply considered as a syntactic sugar.

Thanks @Sean! I noticed that if I didn’t pass the runner into the service, then accessing the runner from the global scope resulted in an error because the runner hadn’t been initialized (which happens by the service). So I’m guessing the syntactic sugar works because, whether you use the runner from the global scope or from the svc’s class variable, it’s pointing to the same object. Thanks for clearing this up. Ever since I first read the docs I was a bit confused how/why it worked this way.