René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Backend choice reset inside of threads","articleBody":"Inside a new thread, Arrayfire uses the default backend rather than the backend set by the parent thread:\r\n\r\n```python\r\n\u003e\u003e\u003e import arrayfire as af\r\n\u003e\u003e\u003e af.get_available_backends()\r\n('cpu', 'cuda', 'opencl')\r\n\u003e\u003e\u003e af.get_active_backend()\r\n'cuda'\r\n\u003e\u003e\u003e af.set_backend('opencl')\r\n\u003e\u003e\u003e af.get_active_backend()\r\n'opencl'\r\n\u003e\u003e\u003e from threading import Thread\r\n\u003e\u003e\u003e Thread(target=lambda: print(af.get_active_backend())).start()\r\ncuda\r\n```\r\n\r\nIs this expected behavior and/or documented anywhere? I would think that the active backend should be process local rather than thread local.\r\n\r\nIf it matters, here's my version info:\r\nOS: Ubuntu 20.04\r\narrayfire: 3.9.0 (commit [955152b6](https://github.com/arrayfire/arrayfire/commit/955152b6570c608ae74ebd9e6b31d48351cb8a16))\r\narrayfire-python: 3.8.10\r\n\r\ncuda: 11.4.0-1\r\nocl-icd-libopencl1: 2.2.11-1\r\nintel-mkl: 2020.0.166-1","author":{"url":"https://github.com/hexane360","@type":"Person","name":"hexane360"},"datePublished":"2021-07-07T06:58:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/257/arrayfire-python/issues/257"}