cylc-uiserver icon indicating copy to clipboard operation
cylc-uiserver copied to clipboard

Published 20 hours ago • verified publisher icon cylc

dependency sustainability

Open oliver-sanders opened this issue 2 years ago • 4 comments

Cylc UI Server has two dependencies from the graphql-python org that are starting to look worrying:

  • graphene-tornado
    • GitHub last commit
    • Adds tornado support to Graphene.
    • Bruno maintains the conda-forge feedstock.
    • A v3 beta was started but never released.
    • One bug we have spotted may be related - https://github.com/cylc/cylc-uiserver/issues/328
  • graphql-ws
    • GitHub last commit
    • Adds websocket support to GraphQL).
    • Hillary & Bruno maintain the conda-forge feedstock.
    • The project was forked for Graphene 3, but then abandoned.

These projects are fairly small and live in the graphql-python organisation, however, are in need of a little TLC. They are currently stuck on Graphene 2, Graphene has since moved onto version 3 (Nov 2021).

Unfortunately it is relatively unusual to write GraphQL servers in Python (clients less unusual), GraphQL came out the JS ecosystem where the most popular server lives. Consequently there isn't that much interest from the wider community in some of these more niche integrations in the Python ecosystem.

To safeguard the future of these projects they need to make it to Graphene 3, unfortunately this requires an understanding of Graphene that we don't have which makes it difficult for us to help.

What can/should we do and when can we afford the time to do it?

oliver-sanders avatar Mar 23 '22 17:03 oliver-sanders