Skip to content

Remove outdated content from Purpose and Scope document #714

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions spec/2022.12/purpose_and_scope.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ standard is shown in this diagram:
_Rationale: execution is the domain of implementations. Attempting to specify
execution behavior in a standard is likely to require much more fine-grained
coordination between developers of implementations, and hence is likely to
become an obstable to adoption._
become an obstacle to adoption._

3. Non-Python API standardization (e.g., Cython or NumPy C APIs)

Expand All @@ -153,14 +153,13 @@ standard is shown in this diagram:
this point in time to standardize anything. See
the [C API section](design_topics/C_API.md) for more details._

4. Standardization of these dtypes is out of scope: bfloat16, complex, extended
4. Standardization of these dtypes is out of scope: bfloat16, extended
precision floating point, datetime, string, object and void dtypes.

_Rationale: these dtypes aren't uniformly supported, and their inclusion at
this point in time could put a significant implementation burden on
libraries. It is expected that some of these dtypes - in particular
`bfloat16`, `complex64`, and `complex128` - will be included in a future
version of the standard._
`bfloat16` - will be included in a future version of the standard._

5. The following topics are out of scope: I/O, polynomials, error handling,
testing routines, building and packaging related functionality, methods of
Expand Down
7 changes: 3 additions & 4 deletions spec/draft/purpose_and_scope.md
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ standard is shown in this diagram:
_Rationale: execution is the domain of implementations. Attempting to specify
execution behavior in a standard is likely to require much more fine-grained
coordination between developers of implementations, and hence is likely to
become an obstable to adoption._
become an obstacle to adoption._

3. Non-Python API standardization (e.g., Cython or NumPy C APIs)

Expand All @@ -153,14 +153,13 @@ standard is shown in this diagram:
this point in time to standardize anything. See
the [C API section](design_topics/C_API.md) for more details._

4. Standardization of these dtypes is out of scope: bfloat16, complex, extended
4. Standardization of these dtypes is out of scope: bfloat16, extended
precision floating point, datetime, string, object and void dtypes.

_Rationale: these dtypes aren't uniformly supported, and their inclusion at
this point in time could put a significant implementation burden on
libraries. It is expected that some of these dtypes - in particular
`bfloat16`, `complex64`, and `complex128` - will be included in a future
version of the standard._
`bfloat16` - will be included in a future version of the standard._

5. The following topics are out of scope: I/O, polynomials, error handling,
testing routines, building and packaging related functionality, methods of
Expand Down