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

[3.6] bpo-31482: Missing bytes support for random.seed() version 1 (GH-3614) #3629

Closed
wants to merge 1 commit into
base: 3.6
from

Conversation

Projects
None yet
6 participants
@miss-islington

miss-islington commented Sep 17, 2017

bpo-31482: Missing bytes support for random.seed() version 1 GH-3614
(cherry picked from commit 132a7d7)

https://bugs.python.org/issue31482

[3.6] bpo-31482: Missing bytes support for random.seed() version 1 (G…
…H-3614)

bpo-31482: Missing bytes support for random.seed() version 1 GH-3614
(cherry picked from commit 132a7d7)
@the-knights-who-say-ni

This comment has been minimized.

Show comment
Hide comment
@the-knights-who-say-ni

the-knights-who-say-ni Sep 17, 2017

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

the-knights-who-say-ni commented Sep 17, 2017

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

@serhiy-storchaka

This comment has been minimized.

Show comment
Hide comment
@serhiy-storchaka

serhiy-storchaka Sep 17, 2017

Member

Why this PR is closed?

Member

serhiy-storchaka commented Sep 17, 2017

Why this PR is closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment