Skip to content

Commit f5d8304

Browse files
authored
Remove outdated content from Purpose and Scope document (data-apis#714)
* Remove outdated content from Purpose and Scope document * Fix typo * Backport content updates to the 2022 revision
1 parent 5555d41 commit f5d8304

File tree

2 files changed

+6
-8
lines changed

2 files changed

+6
-8
lines changed

spec/2022.12/purpose_and_scope.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ standard is shown in this diagram:
144144
_Rationale: execution is the domain of implementations. Attempting to specify
145145
execution behavior in a standard is likely to require much more fine-grained
146146
coordination between developers of implementations, and hence is likely to
147-
become an obstable to adoption._
147+
become an obstacle to adoption._
148148

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

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

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

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

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

spec/draft/purpose_and_scope.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ standard is shown in this diagram:
144144
_Rationale: execution is the domain of implementations. Attempting to specify
145145
execution behavior in a standard is likely to require much more fine-grained
146146
coordination between developers of implementations, and hence is likely to
147-
become an obstable to adoption._
147+
become an obstacle to adoption._
148148

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

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

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

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

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

0 commit comments

Comments
 (0)