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

Jump to bottom

Cython support should use new_build_ext #1270

Open
jaraco opened this issue Feb 4, 2018 · 4 comments
Open

Cython support should use new_build_ext #1270

jaraco opened this issue Feb 4, 2018 · 4 comments
Labels
bug deferred

Comments

@jaraco
Copy link
Member

jaraco commented Feb 4, 2018

In #1229 and this comment, scoder recommendeds to prefer new_build_ext to build_ext.
@jaraco jaraco closed this as completed in 038baa1 Feb 4, 2018
@jaraco jaraco mentioned this issue Feb 5, 2018
Closed
jaraco added a commit that referenced this issue Feb 6, 2018
@jaraco
Revert "Prefer new_build_ext for Cython builds as recommended by Cyth…
211b194 
…on project. Fixes #1270." Reopens #1270. Fixes #1271.

This reverts commit 038baa1.
@jaraco jaraco reopened this Feb 6, 2018
@jaraco
Copy link
Member Author

jaraco commented Feb 6, 2018

As observed in #1271, new_build_ext isn't viable without some transition support.

@pganssle pganssle added Needs Triage Issues that need to be evaluated for severity and status. bug deferred and removed Needs Triage Issues that need to be evaluated for severity and status. labels Oct 19, 2018
@jakirkham jakirkham mentioned this issue Mar 25, 2020
Merged
@jakirkham
Copy link
Contributor

Maybe we get stuck in some recursive case here?

@jakirkham
Copy link
Contributor

cc @scoder (for awareness)

@scoder
Copy link
Contributor

scoder commented Dec 20, 2021

The Cython project is currently updating new_build_ext here to match the older command:
cython/cython#4498

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug deferred
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jaraco @scoder @pganssle @jakirkham