Skip to content

return element's updated index after heap change, skip news, skip issue#31226

Closed
ShiboXing wants to merge 1 commit into
python:mainfrom
ShiboXing:patch-1
Closed

return element's updated index after heap change, skip news, skip issue#31226
ShiboXing wants to merge 1 commit into
python:mainfrom
ShiboXing:patch-1

Conversation

@ShiboXing
Copy link
Copy Markdown

Simple change to return the final index of _siftdown, _siftup, heappush, making it convenient for user's potential indexable heap.
User could store index after heappush, and call _siftdown or _siftup after updating

Simple change to return the final index of _siftdown, _siftup, heappush, making it convenient for user's potential indexable heap.
User could store index after heappush, and call _siftdown or _siftup after updating
@the-knights-who-say-ni
Copy link
Copy Markdown

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@ShiboXing

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@ShiboXing ShiboXing changed the title return element's updated index after heap change return element's updated index after heap change, skip news, skip issue Feb 12, 2022
@JelleZijlstra
Copy link
Copy Markdown
Member

Thanks for your contribution!

This is a new feature and does need an issue and NEWS entry. It should also be documented in the heapq documentation.

I have no opinion on whether this feature should be added.

@github-actions
Copy link
Copy Markdown

This PR is stale because it has been open for 30 days with no activity. If the CLA is not signed within 14 days, it will be closed. See also https://devguide.python.org/pullrequest/#licensing

@github-actions github-actions Bot added the stale Stale PR or inactive for long period of time. label Mar 16, 2022
@github-actions
Copy link
Copy Markdown

Closing this stale PR because the CLA is still not signed.

@github-actions github-actions Bot closed this Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting review stale Stale PR or inactive for long period of time.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants