René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"autoscale differences between 1.5.1 and 2.0.0b3","articleBody":"Based on description of tight (\"If True, set view limits to data limits\"), I would have expected MPL 1.5.1 behavior (see code and image below).  Though perhaps there was a little margin added intentionally? \n\nEdit: I see this first part was intended, as change https://github.com/matplotlib/matplotlib/pull/5583. See second issue below.\n\n```\nimport matplotlib as mpl\n\nplt.plot([1,2,3,4])\nplt.autoscale(axis='both', tight=True)\n\nplt.show()\n```\n\n![limits_tight](https://cloud.githubusercontent.com/assets/15056721/17906688/62f63912-6946-11e6-9a96-baaea8a0b64c.png)\n\n---\n\nAside from this, MPL 1.x use to conveniently adjust view limits for log and symlog when tight autoscaling was not on, but MPL 2 does not seem to do this anymore. \n\nThis actually also looks like a result of https://github.com/matplotlib/matplotlib/pull/5583. I would argue the previous behavior was actually desirable in many instances. Is there a way to recover it? \n\n```\nimport matplotlib as mpl\n\nplt.plot([1,2,3,4])\n\nax = plt.gca()\nax.set_xscale('log')\nax.set_yscale('log')\n\nplt.show()\n```\n\n![log_scaling](https://cloud.githubusercontent.com/assets/15056721/17906913/4436397c-6947-11e6-947a-783118789c9d.png)\n\nPython 2.7 and 3.4\nUsing tkagg backend.\nWindows 7\n","author":{"url":"https://github.com/LevN0","@type":"Person","name":"LevN0"},"datePublished":"2016-08-23T19:37:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/6968/matplotlib/issues/6968"}