Skip to content
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

Rename py long > py int #4260 #4284

Closed
wants to merge 9 commits into from

Conversation

shreyash2002
Copy link

Thank you for contributing to PyO3!

By submitting these contributions you agree for them to be dual-licensed under PyO3's MIT OR Apache-2.0 license.

Please consider adding the following to your pull request:

  • an entry for this PR in newsfragments - see [https://pyo3.rs/main/contributing.html#documenting-changes]
    • or start the PR title with docs: if this is a docs-only change to skip the check
  • docs to all new functions and / or detail in the guide
  • tests for all new or changed functions

PyO3's CI pipeline will check your pull request, thus make sure you have checked the Contributing.md guidelines. To run most of its tests
locally, you can run nox. See nox --list-sessions
for a list of supported actions.

-  PyLong is primarily a historical accident based on the fact that Python 2's integers were split between int and long types, and so the Python C API is based on PyLongObject etc. 

- So, renaming it to PyInt
-PyLong is primarily a historical accident based on the fact that Python 2's integers were split between int and long types, and so the Python C API is based on PyLongObject etc. 

- So, renaming it to PyInt
@shreyash2002
Copy link
Author

@davidhewitt
I have created a draft PR with some changes. Can you review it and suggest what more i should do?

Copy link
Contributor

@LilyFoote LilyFoote left a comment

Choose a reason for hiding this comment

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

Hey, thanks for taking a look at this.

I don't think you should need to change any code in pyo3-ffi for this issue. Once you've reverted those changes, I suspect you'll start getting more helpful error messages about which bits of the codebase still do need to change.

src/types/num.rs Outdated Show resolved Hide resolved
pyo3-ffi/README.md Outdated Show resolved Hide resolved
pyo3-ffi/README.md Outdated Show resolved Hide resolved
pyo3-ffi/README.md Outdated Show resolved Hide resolved
@MatthijsKok
Copy link
Contributor

Superseded by #4347

@davidhewitt
Copy link
Member

Thanks all!

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.

4 participants