github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/14#issuecomment-381446906 | https://api.github.com/repos/simonw/datasette/issues/14 | 381446906 | MDEyOklzc3VlQ29tbWVudDM4MTQ0NjkwNg== | 9599 | 2018-04-15T23:31:58Z | 2018-04-15T23:34:10Z | OWNER | Once I've got the plugins mechanism stable and people start releasing plugins it would be useful to have a dedicated Trove classifier on PyPI for Datasette plugins - `Framework :: Datasette` for example. This would help me build a Datasette equivalent of the http://plugincompat.herokuapp.com/ site, which works by scanning PyPI for items with the ``Framework :: Pytest`` classifier: https://github.com/pytest-dev/plugincompat/blob/8bdf1a6fb82807091ece0c68c196103ee8270194/update_index.py#L52-L53 It looks like the mechanism for requesting new PyPI classifiers is to file a ticket against warehouse, like these ones: https://github.com/pypa/warehouse/issues/3570 and https://github.com/pypa/warehouse/issues/2881 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/203#issuecomment-381446554 | https://api.github.com/repos/simonw/datasette/issues/203 | 381446554 | MDEyOklzc3VlQ29tbWVudDM4MTQ0NjU1NA== | 9599 | 2018-04-15T23:25:54Z | 2018-04-15T23:26:03Z | OWNER | I built a prototype of the `convert_units()` custom SQL function as a plugin over in https://github.com/simonw/datasette/issues/14#issuecomment-381446511 | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
313837303 | |
https://github.com/simonw/datasette/issues/14#issuecomment-381446511 | https://api.github.com/repos/simonw/datasette/issues/14 | 381446511 | MDEyOklzc3VlQ29tbWVudDM4MTQ0NjUxMQ== | 9599 | 2018-04-15T23:25:04Z | 2018-04-15T23:25:04Z | OWNER | Here's a demo of the `convert_units()` SQL function I prototyped in f2720b0c6b7172ebe88 ![2018-04-15 at 4 23 pm](https://user-images.githubusercontent.com/9599/38784633-8c43821e-40c9-11e8-97dd-697755a0f858.png) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/14#issuecomment-381443728 | https://api.github.com/repos/simonw/datasette/issues/14 | 381443728 | MDEyOklzc3VlQ29tbWVudDM4MTQ0MzcyOA== | 9599 | 2018-04-15T22:39:00Z | 2018-04-15T22:39:00Z | OWNER | Tox is a good example of a project that uses pluggy in the way I want to use it (function hooks rather than classes): https://github.com/tox-dev/tox/blob/master/tox/hookspecs.py | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/14#issuecomment-381442494 | https://api.github.com/repos/simonw/datasette/issues/14 | 381442494 | MDEyOklzc3VlQ29tbWVudDM4MTQ0MjQ5NA== | 9599 | 2018-04-15T22:17:59Z | 2018-04-15T22:17:59Z | OWNER | Datasette 1.0 will be the release of Datasette that attempts to provide a stable plugin API: https://github.com/simonw/datasette/milestone/7 There's a lot of work to be done before then, but as a starting point I'm going to support two very simple extension mechanisms: * Template system plugins - where the hook gets passed the Jinja environment and can freely register new template tags and filters * SQLite connection plugins - where the hook gets passed a new SQLite connection and can register custom SQLite functions The template system hook will go near here: https://github.com/simonw/datasette/blob/efbb4e83374a2c795e436c72fa79f70da72309b8/datasette/app.py#L1225-L1228 The SQLite connection hook will go near here: https://github.com/simonw/datasette/blob/efbb4e83374a2c795e436c72fa79f70da72309b8/datasette/app.py#L1094-L1098 These two feel simple enough that I'm not worried that I might design an API that I later regret. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 | |
https://github.com/simonw/datasette/issues/14#issuecomment-381442233 | https://api.github.com/repos/simonw/datasette/issues/14 | 381442233 | MDEyOklzc3VlQ29tbWVudDM4MTQ0MjIzMw== | 9599 | 2018-04-15T22:13:06Z | 2018-04-15T22:13:06Z | OWNER | I started a thread on Twitter asking people for good examples of Python projects with a strong plugin ecosystem: https://twitter.com/simonw/status/985377670388105216 The most impressive example that came back was pytest - which now has nearly 400 plugins: https://plugincompat.herokuapp.com/ The pytest plugin infrastructure is available as an independent package called pluggy - which appears to offer everything I need for Datasette. I'm going to give that a go and see how well it works: https://pluggy.readthedocs.io/en/latest/ | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
267707940 |