-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Revert "Re-enable parallel builds in CI" #51952
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
Conversation
This reverts commit 4d74fbd.
Didn't follow this last week. This breaks other stuff that you want to fix, that's why we are reverting? |
Yes
…On Tue, Mar 14, 2023 at 3:59 PM Patrick Hoefler ***@***.***> wrote:
Didn't follow this last week. This breaks other stuff that you want to
fix, that's why we are reverting?
—
Reply to this email directly, view it on GitHub
<#51952 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5UM6EBY5WV6ZWSPYYWHQTW4DZ6ZANCNFSM6AAAAAAVZW7TYM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ATM I can't maintain the C parts of the datetime code, which is unacceptable. |
Sorry that it took me so long, I was going through the initial PR. If I understand it correctly it did not fix anything user visible and might get simpler if we can upstream stuff to NumPy? So should be good to revert, hopefully will get simpler in the future. |
This shouldn't be reverted. The whole point of this and the capsule PR is to clean up our symbol management and make an internal API for our extensions. Reverting this puts us back into a place of hacks and guesses until things work. Can we revert this revert? |
Fine |
This reverts commit c8ea34c.
Reverts #51902
Depends on #51525 which is reverted by #51951