{"push_id":614961989,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"94e81923ec029282dd55fa1b494edc38be8fa074","before":"48f2aa6acb2b77b593313d399e75237a294e2323","commits":[{"sha":"94e81923ec029282dd55fa1b494edc38be8fa074","author":{"email":"f36fc6860e49d8eb9d34d2c3911295ed4e593a48@icloud.com","name":"Waylan Limberg"},"message":"Use entry points to load extensions by name.\n\nAll previously supported methods of loading an extension given a string\nname have now been replaced with entry points. Extension classes must be\nregistered as entry points in the 'markdown.extensions' group to support\nstring names. The old module-level 'makeExtension' function is no longer\nneeded. In fact, multiple extensions could be defined in one module\nand still use string names if entry points are defined pointing to\neach Extension subclass.\n\nAll of the build-in extensions are now registered with names that\nmimic their paths (using dot notation). That may change in the future.\nIt is expected that all extensions will use short names. We may support\nboth ('extra' & 'markdown.extensions.extra') in the interim.\n\nAlso, all extension configs must now be dicts. Support for a list\nof tuples has been removed.","distinct":true,"url":"https://api.github.com/repos/Python-Markdown/markdown/commits/94e81923ec029282dd55fa1b494edc38be8fa074"}]}