Skip to content

data-apis/array-api

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Array API standard

All Contributors

This repository contains documents, tooling and other content related to the API standard for arrays (or tensors).

These are relevant documents related to the content in this repository:

See CONTRIBUTING.md for how to go about contributing to this array API standard.

Building docs locally

The spec website is comprised of multiple Sphinx docs (one for each spec version), all of which exist in spec/ and rely on the modules found in src/ (most notably array_api_stubs). To install these modules and the additional dependencies of the Sphinx docs, you can use

$ pip install -e .[doc]  # ensure you install the dependencies extra "doc"

To build specific versions of the spec, run sphinx-build on the respective folder in spec/, e.g.

$ sphinx-build spec/draft/ _site/draft/

To build the whole website, which includes every version of the spec, you can utilize the make commands defined in spec/Makefile; e.g.,

$ make
$ ls _site/
2021.12/  draft/  index.html  latest/  versions.json

Making a spec release

The Sphinx doc at spec/draft/ should be where the in-development spec resides, with src/array_api_stubs/_draft/ containing its respective stubs. A spec release should involve:

  • Renaming src/array_api_stubs/_draft/ to src/array_api_stubs/_YYYY_MM

  • Renaming spec/draft/ to spec/YYYY.MM

  • Updating spec/YYYY.MM/conf.py

    ...
    - from array_api_stubs import _draft as stubs_mod
    + from array_api_stubs import _YYYY_MM as stubs_mod
    ...
    - release = "DRAFT"
    + release = "YYYY.MM"
    ...
  • Updating spec/_ghpages/versions.json

    {
    +     "YYYY.MM": "YYYY.MM",
    ...
  • Updating Makefile

    ...
    	-sphinx-build "$(SOURCEDIR)/PREVIOUS.VER" "$(BUILDDIR)/PREVIOUS.VER" $(SPHINXOPTS)
    + 	-sphinx-build "$(SOURCEDIR)/YYYY.MM" "$(BUILDDIR)/YYYY.MM" $(SPHINXOPTS)
    - 	-cp -r "$(BUILDDIR)/PREVIOUS.VER" "$(BUILDDIR)/latest"
    + 	-cp -r "$(BUILDDIR)/YYYY.MM" "$(BUILDDIR)/latest"
    ...

These changes should be committed and tagged. The next draft should then be created. To preserve git history for both the new release and the next draft:

  1. Create and checkout to a new temporary branch.
$ git checkout -b tmp
  1. Make an empty commit. This is required so merging the temporary branch (4.) is not automatic.
$ git commit --allow-empty -m "Empty commit for draft at YYYY.MM "
  1. Checkout back to the branch you are making a spec release in.
$ git checkout YYYY.MM-release
  1. Merge the temporary branch, specifying no commit and no fast-forwarding.
$ git merge --no-commit --no-ff tmp
Automatic merge went well; stopped before committing as requested
  1. Checkout the spec/draft/ files from the temporary branch.
$ git checkout tmp -- spec/draft/
  1. Commit your changes.
$ git commit -m "Copy YYYY.MM as draft with preserved git history"

You can run git blame on both spec/YYYY.MM and spec/draft files to verify we've preserved history. See this StackOverflow question for more background on the approach we use.

Contributors

Thanks goes to these wonderful people (emoji key):


Saul Shanabrook

🔧 🤔 🔬

Athan

🖋 🔣 🔧 🔬

Stephannie Jimenez Gacha

🔣 🖋 🔬

Aaron Meurer

🖋 ⚠️ 🔧

Tony Fast

🚧

Ralf Gommers

📝 💼 💻 🖋 📖 🔍 🚧 🤔 📆 📢

Travis E. Oliphant

💼 🔍 🤔

Leo Fang

👀 🤔 🖋

Tianqi Chen

🤔 👀

Stephan Hoyer

🤔 👀 💬

Alexandre Passos

🤔 👀

Paige Bailey

🔍

Adam Paszke

🤔 👀 📢

Andreas Mueller

🤔 👀

Sheng Zha

🤔 👀 📢

kkraus

🤔 👀 📢

Tom Augspurger

👀 💬

edloper

👀 💬

Areg Melik-Adamyan

👀 🔍

Oleksandr Pavlyk

👀 💬

tdimitri

🤔

Jack Pappas

🤔

Ashish Agarwal

👀 💬

Edward Z. Yang

🤔

Mike Ruberry

🤔

Eric Wieser

🤔

Carol Willing

🤔

Alex Rogozhnikov

🤔

Matthew Honnibal

🤔

This project follows the all-contributors specification. Contributions of any kind welcome!

About

RFC document, tooling and other content related to the array API standard

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages