Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Complete removal of PyCXX#3723

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
tacaswell merged 2 commits intomatplotlib:masterfromianthomas23:final_decxx
Oct 27, 2014
Merged

Conversation

@ianthomas23
Copy link
Member

This PR completes the removal of PyCXX from matplotlib following on from PR#3646.

There are 2 commits. The first converts the _tri module, the last module to use PyCXX, to use the Python/C API instead. I've followed the lead of#3646 so that we have some code consistency in terms of separate wrapper files, code layout, use of the same exception-catching macros, etc.

The second commit removes the PyCXX source code, the relevant sections of the setup scripts, and a few other places where it was mentioned.

It is always nice to write a PR that is such a net reduction in code!

@tacaswelltacaswell added this to thev1.5.x milestoneOct 26, 2014
@jenshnielsen
Copy link
Member

It looks good to me. I did a quick test locally and everything seems to work fine. 👍 on merging this from me.

tacaswell added a commit that referenced this pull requestOct 27, 2014
@tacaswelltacaswell merged commit04e006c intomatplotlib:masterOct 27, 2014
Copy link
Member

Choose a reason for hiding this comment

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

I think you need toPy_DECREF(segs) here.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Yes, well spotted.

@mdboom
Copy link
Member

Thanks for doing this! I appreciate how much work this was. Sorry about commenting after this was merged, but it looks like this was up for less than 24 hours!

@tacaswell
Copy link
Member

Sorry, I applied the logic of the other pycxx branch and merged it on trusting the test suite.

@mdboom
Copy link
Member

@tacaswell: No problem. It's more important that this works than anything else, so merging early is the best for that.

@ianthomas23
Copy link
MemberAuthor

@tacaswell: What should I do now that this PR has been merged? Should I just write a new PR for the changes and refer back to this one?

@tacaswell
Copy link
Member

Yes, that is probably the best way

On Mon, Oct 27, 2014 at 3:06 PM, Ian Thomasnotifications@github.com
wrote:

@tacaswellhttps://github.com/tacaswell: What should I do now that this
PR has been merged? Should I just write a new PR for the changes and refer
back to this one?


Reply to this email directly or view it on GitHub
#3723 (comment)
.

Thomas Caswell
tcaswell@gmail.com

mdboom added a commit that referenced this pull requestNov 3, 2014
@ianthomas23ianthomas23 deleted the final_decxx branchJuly 8, 2021 18:21
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

v2.1

Development

Successfully merging this pull request may close these issues.

5 participants

@ianthomas23@jenshnielsen@mdboom@tacaswell@QuLogic

[8]ページ先頭

©2009-2025 Movatter.jp