René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unclosed Session/SSLSocket","articleBody":"When I run the following python code with a debugger attached -\r\n```\r\npolygon_api = polygon.RESTClient()\r\nresponse = polygon_api.stocks_equities_aggregates('AAPL', 30, 'minute', '2020-06-30', '2020-06-30')\r\n```\r\nI get a post-run warning from my debugger -\r\n```\r\nResourceWarning: unclosed \u003cssl.SSLSocket type=SocketKind.SOCK_STREAM, raddr=('38.133.177.84', 443)\u003e\r\n```\r\nBut if I run -\r\n```\r\npolygon_api = polygon.RESTClient()\r\nresponse = polygon_api.stocks_equities_aggregates('AAPL', 30, 'minute', '2020-06-30', '2020-06-30')\r\npolygon_api._session.close()\r\n```\r\nThe polygon client cleans up and my debugger is happy.\r\n\r\nLooking into why this is, `Session` will only call its own `close()`  from its `__exit__` method, which is only called if the class is being used as a context manager (e.g. using `with Session() as s:` statement, as suggested by [their docs](https://requests.readthedocs.io/en/master/user/advanced/#session-objects)) - and RESTClient is not using it in this manner, so `close()` is just never being called and resources are being left open.\r\n\r\n","author":{"url":"https://github.com/sky-coding","@type":"Person","name":"sky-coding"},"datePublished":"2020-07-01T17:18:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/29/client-python/issues/29"}