-
Notifications
You must be signed in to change notification settings - Fork 33
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
Stop creating unused variables #68
Stop creating unused variables #68
Conversation
Is it reasonable to first try to merge it to cpython? |
Generally we do it the other way: we merge stuff here and I sync them from time to time in batches. |
Ok, I see. |
Probably a good time to say, that two tests are failing on the |
Getting #66 in first would make sense to get CIs to test on more versions. |
Well, then what's about distributing credit/blame for the changes? Will those changes be cherry-picked into cpython? |
No, they will be directly included in one batch and blame/credit is lost. |
Aww, isn't this a reason to make a direct pr to cpython? Well, not like it's that important, but it would be nice if the credit/blame was preserved! |
No, we don't generally merge individual PRs in CPython for pegen because it makes syncing much more complicated.
Well, the canonical code for |
@0dminnimda Can you rebase on main so that we get an extended test run ? |
Oh yeah, workflow activation, what a lovely github feature ♥ |
Bye, I am leaving this repo now. |
oh .. bye well, we need to get back to the work 3.10 didn't pass, it seems like versoin of python that tox runs is somehow different from the other ones I don't quite understand why it happens |
#71 will fix the failure on 3.10 (3.10.5 fixed an issue for which we had a workaround) |
Closing and opening to triger the ci |
oh yeah, forgot to merge |
Is there any additional comments or this can be merged? |
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.
I found one concerning issue regarding cut (and I find even more concerning that no test found the issue). I also left a couple of comment/question.
Should I add the tests for it here? Tho seems appropriate for another pr |
Maybe @pablogsal have other comments? |
I will try to review this soon but currently, I am very busy with the 3.11.0b5 release :( |
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.
I left a minor suggestions for improvement and a question otherwise LGTM.
@MatthieuDartiailh can you allow the workflow? |
Done |
@pablogsal would you have time to look at this ? or do you want to defer the final review to me maybe (since you seem quite busy ATM). |
I apologize for the late reply @MatthieuDartiailh. Unfortunately the release of 3.11 is being ridiculously challenging and I'm expending all my OSS time on that :( Please, go ahead and merge it if you feel confident. I trust your criteria 👍 |
Co-authored-by: Matthieu Dartiailh <marul@laposte.net>
I wanted to add a couple small comments but apparently I cannot push to your repo. S I will merge and add the comment directly on main. |
Weird usually there's no problem in that |
No description provided.