Skip to content

Make array data allocator configurable #5470

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

Closed
wants to merge 5 commits into from

Conversation

pitrou
Copy link
Member

@pitrou pitrou commented Jan 20, 2015

This is an alternative to #5457: it allows to configure the array data allocator at runtime using a C API.

@pitrou
Copy link
Member Author

pitrou commented Jan 20, 2015

Note this isn't as simple as it would ideally be, as the use of PyDataMem_ APIs is currently diverse and there's also the internal caching APIs.

@WarrenWeckesser
Copy link
Member

This pull request was created in in 2015, and has had no reviews. This PR is described as an alternative to gh-5457, which had only a couple comments from @juliantaylor, and has also had no activity since early 2015.

@pitrou, are these pull requests still viable? I hesitate to suggest fixing the merge conflicts if it will just end up sitting here unreviewed for a few more years.

Other NumPy devs: the evidence suggests there is no interest in these PRs. OK to close?

@seberg
Copy link
Member

seberg commented Sep 8, 2021

Thanks for this! I will close it, since it is now superseded by gh-17582 and NEP 49 — Data allocation strategies.

@seberg seberg closed this Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants