-
Notifications
You must be signed in to change notification settings - Fork 239
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
feat: adding enable #2048
base: main
Are you sure you want to change the base?
feat: adding enable #2048
Conversation
d7329df
to
a70d4b3
Compare
a70d4b3
to
8a54c9f
Compare
cc80f2c
to
bbc0a19
Compare
# For backwards compatibility, we are adding PyPy for now | ||
enable |= {EnableGroups.PyPy} |
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 guess this is where the question of !pypy
came from ?
I hadn't read the PR just yet when replying and it seems having the !
operator would invalidate the current implementation.
The idea would thus be to keep PyPy enabled in 2.22 but change the default to disabled in 3.0 ?
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.
bbc0a19
to
e2c5f24
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
e2c5f24
to
17df90f
Compare
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Close #2045. Adds
enable
, deprecates the old way of specifying these (remove in 3.0).