-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
DOC: Add "build C extensions" note #46055
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
DOC: Add "build C extensions" note #46055
Conversation
The C extensions must also be created when you bind your local repository for the first time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, minor request
|
||
python setup.py build_ext -j 4 | ||
|
||
You might need to rebuild the C extensions if/when you merge your repo with upstream/main. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might need to rebuild the C extensions if/when you merge your repo with upstream/main. | |
You need to rebuild the C extensions anytime the Cython code in ``pandas/core/_libs`` changes. This most frequently occurs when changing or merging branches. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even better would be to separate out this into a new section, something like "Rebuilding the C extensions" and going into a bit more detail as to the why/how/when. But certainly okay to leave it here for this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Is
pandas/core/_libs
right? Because such a folder does not exist. I think you meanpandas/_libs
?
Even better would be to separate out this into a new section, something like "Rebuilding the C extensions"... But certainly okay to leave it here for this PR.
- That's a good idea. I can create a new issue if that is OK for you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, an issue would be great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, an issue would be great.
I created one.
looks ok @rhshadrach merge when ready |
Thanks @rendner! |
Co-authored-by: Daniel Schmidt <rendner@users.noreply.github.com>
This PR adds the missing information that the C extensions must be built when a local pandas repo was bind for the first time.
I also adjusted the docker commands to:
--build-arg gh_username=yourname
was missing)-w /home/pandas
, to directly start in the right directory