Skip to content

Conversation

@sbz
Copy link

@sbz sbz commented Nov 21, 2020

@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

CLA Missing

Our records indicate the following people have not signed the CLA:

@sbz

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

locals()['crash_37'] = crash_36
locals()['crash_38'] = crash_38
locals()['crash_39'] = crash_38
locals()['crash_310'] = crash_38
Copy link
Member

Choose a reason for hiding this comment

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

The test suite only ever runs on the current version of python. I think you can restrict this to just crash_38 code, since at best this would be backported to 3.8 and 3.9.

2.7 is no longer maintained, so that can definitely be removed.

Copy link
Author

Choose a reason for hiding this comment

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

Thanks @ericvsmith for your suggestions. I have removed the 2.7 part and keep only the crash_38 for master 🤝


py_ver = "".join(platform.python_version_tuple()[0:2])
crash_func = "crash_{}".format(py_ver)
locals()[crash_func]()
Copy link
Member

Choose a reason for hiding this comment

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

You should remove all of the tests for the version number, and just call the code directly here. It just needs to be a one liner.

Copy link
Author

@sbz sbz Nov 23, 2020

Choose a reason for hiding this comment

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

Alright, it's done as expected 🙇

Copy link
Author

Choose a reason for hiding this comment

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

Hi, are we good for merging it now? Let me know if anything else is needed 🤝

Copy link
Member

Choose a reason for hiding this comment

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

There's a discussion on the bug tracker issue discussing whether this crasher is needed, given what's already present.

@github-actions
Copy link

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Dec 27, 2020
@vstinner
Copy link
Member

I'm not sure of the purpose of Lib/test/crashers/null_code_obj.py : Python is not going to get a bytecode verifier soon https://bugs.python.org/issue42422

It's a known fact that you can easily crash Python by executing malicious bytecode.

@sbz
Copy link
Author

sbz commented Apr 22, 2021

Tests crashers were updated in the PR#23939 after my submission.

I'm closing it.

@sbz sbz closed this Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting review skip news stale Stale PR or inactive for long period of time.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants