René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"AutoDateFormatter shows too much precision","articleBody":"When trying to plot some date-based values, I noticed that the default labels show too much precision. I was trying to plot some data points over a minutes to hours interval, and the default plot kept showing times using a micro-second precision. Given that the major ticks were minutes apart, this seems overkill to me (and the extra digits quickly clutter the display, making the labels overlap).\n\nDiving into the code, it seems the default \"scaled\" member of the\nAutoDateFormatter, which determines what formats to use when, can be\nimproved. Currently, it:\n- Uses microsecond precision when the ticks are minutes or less apart.\n- Uses second precision when the ticks are hours apart\n- Uses day-precision, month or year precision when the ticks are days\n  or more apart (these are fine, so I lumped them together).\n\nI think it should be like this:\n- Use microsecond precision when the ticks less than a second apart\n- Use second precision when the ticks are seconds apart\n- Use minute precision when the ticks are minutes or hours apart\n- Use day-precision, month or year precision when the ticks are days\n  or more apart (unchanged).\n\nNote that there is no point in displaying only the hour when the ticks\nare hours apart, since then it won't be immediately clear that a time is\nbeing displayed. Adding the (technically superfluous) :00 for the\nminutes should prevent this, which is why the minute precision should\nalso be used when the ticks are hours apart.\n\nThe above would be implemented by the following change (documentation\nnot updated yet):\n\n```\n@@ -563,8 +573,9 @@\n         self.scaled = {DAYS_PER_YEAR: '%Y',\n                        DAYS_PER_MONTH: '%b %Y',\n                        1.0: '%b %d %Y',\n-                       1. / HOURS_PER_DAY: '%H:%M:%S',\n-                       1. / (MINUTES_PER_DAY): '%H:%M:%S.%f'}\n+                       1. / HOURS_PER_DAY: '%H:%M',\n+                       1. / SEC_PER_DAY: '%H:%M:%S',\n+                       1. / MUSECONDS_PER_DAY: '%H:%M:%S.%f'}\n\n     def __call__(self, x, pos=None):\n         locator_unit_scale = float(self._locator._get_unit())\n```\n\nDoes this sound reasonable?\n","author":{"url":"https://github.com/matthijskooijman","@type":"Person","name":"matthijskooijman"},"datePublished":"2015-07-28T14:40:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/4808/matplotlib/issues/4808"}