Use _PyLong_GetOne() in long_pow()

[hikariyo]

Just another place like what #125044 did. It makes code clearer.

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[nineteendo]

Can you update the branch?

[bedevere-app]

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

[rruuaanng]

Please add title label, like this

gh-<issue_id>: xxx

[hikariyo]

Please add title label, like this

gh-<issue_id>: xxx

This is a trivial change which might skip issue 😊

[rruuaanng]

And, this has been rejected by the core-dev, I don't think this modification is meaningful.

[hikariyo]

And, this has been rejected by the core-dev, I don't think this modification is meaningful.

But similar change has been merged as I mentioned, and I think the last PR has been rejected because it changed so many places which makes code ugly, different from this PR.

I think it is meaningful to keep the code style the same in the same file.

[rruuaanng]

My suggestion is to open an issue and listen to other people's opinions.

[hikariyo]

My suggestion is to open an issue and listen to other people's opinions.

Since a core-dev has approved similar change, and I'm just doing something to finish his incomplete change, it should be just fine.

I found this place when studying this file and want to do something to make the code style the same 🥲

[rruuaanng]

You might be talking about this
https://github.com/python/cpython/pull/125044/files

In fact, changing the code style alone isn't allowed. You should also modify other functions to pass.

[hikariyo]

Okay, sorry to trouble you 🙏.

[erlend-aasland]

And, this has been rejected by the core-dev, I don't think this modification is meaningful.

@rruuaanng, please try and keep a polite tone.

@hikariyo: Thanks for the PR, but as has been noted, pretty much all code changes, including refactorings¹, need issues. Please see the devguide for more info :)

Footnotes

1. this PR counts as refactoring ↩

[rruuaanng]

And, this has been rejected by the core-dev, I don't think this modification is meaningful.

@rruuaanng, please try and keep a polite tone.

@hikariyo: Thanks for the PR, but as has been noted, pretty much all code changes, including refactorings¹, need issues. Please see the devguide for more info :)

I'm sorry, I'm not hostile. Maybe I should bring a smile🙂

Footnotes

1. this PR counts as refactoring ↩

[erlend-aasland]

I'm sorry, I'm not hostile. Maybe I should bring a smile

It often helps to use more friendly words. Instead of "I don't think this modification is meaningful", try instead to ask what the author intends to achieve with the change. @rruuaanng, see also https://opensource.guide/how-to-contribute/#how-to-submit-a-contribution.