You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company uses a lot of scientific python and we want to help people stay in line with SPEC 0. Currently the drop schedule is only published in a markdown table which is good for reading, but is a pain to parse. I want to build some tooling to help people determine what versions they should be supporting and to give them heads ups when they should drop something. For this, I'd love for the SPEC to be either published in a machine readable format like JSON, or exposed via an API so that a CI can grab them and check dependencies against them. I think this is also somewhat related to #177 and potentially #211.
Seeing as the SPEC0_versions.py already builds the dictionary to generate the table, it should be very easy to also dump them as a JSON at the very least. If the project would be open to this, I'd be happy to make a PR, just let me know.
The text was updated successfully, but these errors were encountered:
Hya folks,
My company uses a lot of scientific python and we want to help people stay in line with SPEC 0. Currently the drop schedule is only published in a markdown table which is good for reading, but is a pain to parse. I want to build some tooling to help people determine what versions they should be supporting and to give them heads ups when they should drop something. For this, I'd love for the SPEC to be either published in a machine readable format like JSON, or exposed via an API so that a CI can grab them and check dependencies against them. I think this is also somewhat related to #177 and potentially #211.
Seeing as the
SPEC0_versions.py
already builds the dictionary to generate the table, it should be very easy to also dump them as a JSON at the very least. If the project would be open to this, I'd be happy to make a PR, just let me know.The text was updated successfully, but these errors were encountered: