Skip to content

Conversation

@rgommers
Copy link
Member

@rgommers rgommers commented Aug 25, 2020

The main topic of this PR is the assumptions section. This includes:

  • hardware and software environments
  • dependencies (including abstract dependency diagram)
  • backwards compatibility
  • production code & interactive use

For the Python >=3.8 dependency I had to refer to the positional-only decision, so I factored out that content into a new section on function and method signatures (that shouldn't contain too much that's controversial).


Array libraries may know how to interoperate with each other, for example by
constructing their own array type from that of another library or by shared
memory use of an array (see [Data interchange mechanisms](design_topics/data_interchange.md)).
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everyone seemed happy with the assumptions in the call we discussed it in, 1.7 wks ago. The one comment on this data interchange was "can we just say now that this will be DLPack?". That should be in the section linked here, which is for another PR. So I'll go ahead and merge this as is.

This prevents repeating the same information multiple times;
we can refer to this instead.
Includes:
- hardware and software environments
- dependencies (including abstract dependency diagram)
- backwards compatibility
- production code & interactive use
@rgommers rgommers merged commit f801759 into master Sep 8, 2020
@rgommers rgommers deleted the assumptions branch September 8, 2020 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants