René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Technical Indicators incorrect Time Conversion","articleBody":"**Describe the bug**\r\nThe time conversion is done from `datetime` when querying for technical indicators is to a nanoseconds resolution which conflicts with what Polygon is expecting (milliseconds). This, in turn, leads to Polygon thinking the wrong period is queried. \r\n\r\n**Code Links**\r\n- https://github.com/polygon-io/client-python/blob/b47b85245c24dcfd116ee93338ceba0c5f341f77/polygon/rest/base.py#L157-L166\r\n- https://github.com/polygon-io/client-python/blob/b47b85245c24dcfd116ee93338ceba0c5f341f77/polygon/rest/base.py#L186-L187\r\n\r\nAs you can see, this is different from the way say the Aggregates call is done:\r\nhttps://github.com/polygon-io/client-python/blob/b47b85245c24dcfd116ee93338ceba0c5f341f77/polygon/rest/aggs.py#L41-L45\r\n\r\nThe aggregates call is the right way. The SMA indicator also expects a millisecond timestamp: https://polygon.io/docs/stocks/get_v1_indicators_sma__stockticker\r\n","author":{"url":"https://github.com/TheBlackPlague","@type":"Person","name":"TheBlackPlague"},"datePublished":"2024-06-22T08:51:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/689/client-python/issues/689"}