René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Expose cairo antialiasing abilities","articleBody":"Currently, the cairo backend does not support setting antialiasing:\r\n```\r\n    #def set_antialiased(self, b):\r\n        # enable/disable anti-aliasing is not (yet) supported by Cairo\r\n```\r\nThis comment is no longer true; in fact many antialiasing modes have been supported for a while (and can be easily set):\r\nhttps://www.cairographics.org/manual/cairo-cairo-t.html#cairo-set-antialias\r\nhttps://www.cairographics.org/manual/cairo-cairo-t.html#cairo-antialias-t\r\n\r\nThe issue is that True/False is not sufficient to describe the antialiasing modes.  Should we, say, allow the user to pass in a string value (\"default\"/\"none\"/\"gray\"/etc.)?  Passing a \"native\" cairo value won't work, as they are simply integers (and exposed as such by cairocffi, and as int subclasses by pycairo), and ANTIALIAS_DEFAULT=0 (which includes some antialiasing) and ANTIALIAS_NONE=1, which will conflict with the integer values of False=0, True=1.","author":{"url":"https://github.com/anntzer","@type":"Person","name":"anntzer"},"datePublished":"2017-06-20T20:47:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/8784/matplotlib/issues/8784"}