specs
specs copied to clipboard
scientific-python
Scientific Python Ecosystem Coordination (SPEC) documents
As discussed briefly during Scipy 2023. cc @bsipocz @lagru _after all we were asked for opinionated ideas_ _be careful what you wish for_ _Might be useful. Even if just to...
We are doing some work at the summit on security best practices and vulnerability disclosure came up. So we'll add it as SPEC 11. Here's the scope for the spec:...
It would be good to mention what projects are actually using for accessibility like the themes. Starting with these two themes we should probably check whether they meet our accessibility...
What are the core libraries, that should be here, but are missing? We of course cannot just add them, but there should be discussion and agreement: https://scientific-python.org/specs/core-projects/#how-do-you-add-a-project
I belive ``` [testenv] indexserver = # we use Spec 4 index server that contain nightly wheel. # this will be used only when using --pre with tox/pip as it...
Some of the specs are full of links to third party pages of tools and other resources. We need to make sure these links don't rot over time.
I'm trying to capture what was mentioned during a SPEC meeting. - Probably there should be some discussion about the process of tracking issues (email vs github vs etc.) -...
There is a lot of discussions in projects around what it means to endorse vs what is written on each SPEC. To help clarify things, I propose that we create...
See among other https://github.com/scientific-python/summit-2023/issues/3 - [ ] job that tests nightly wheels/dev versions. Maybe a separate job that tests pre-releases. - [ ] job that tests the oldest supported versions...
Currently, the SPEC 0 schedule shows dates by which to *drop* certain packages. It would be helpful to instead see which minimum versions to pin to. Example output could be:...
Metadata
Owner
Metadata
Scientific Python Ecosystem Coordination (SPEC) documents