Skip to content

bpo-31955: Correct distinguish of list and string values in set_executable() #4296

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

Closed
wants to merge 5 commits into from

Conversation

PavelStishenko
Copy link

@PavelStishenko PavelStishenko commented Nov 6, 2017

The check "if isinstance(value, str)" is incorrect, because type of value can be unicode, while it should be splitted as well.

https://bugs.python.org/issue31955

@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 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!

@PavelStishenko PavelStishenko changed the title Correct distinguish of list and string values in set_executable() Correct distinguish of list and string values in set_executable() bpo-31955 Nov 6, 2017
@PavelStishenko
Copy link
Author

I do not understand how to add the label "skip news". And I have signed CLA.

@PavelStishenko PavelStishenko changed the title Correct distinguish of list and string values in set_executable() bpo-31955 bpo-31955: Correct distinguish of list and string values in set_executable() Nov 6, 2017
@vstinner
Copy link
Member

vstinner commented Nov 6, 2017

And I have signed CLA.

Thank you: this part is correct :-)

I do not understand how to add the label "skip news"

Since it's a bug fix, it would be better to document the bugfix in a NEWS entry, rather than skipping this part. Use the blurb tool to add a NEWS entry, see:
https://devguide.python.org/committing/#what-s-new-and-news-entries

Copy link
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

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

I'm not sure that we need to fix Python 3: see https://bugs.python.org/issue31955

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@PavelStishenko
Copy link
Author

Submitted new PR #4316 Closing this one because it is not needed for Python 3.

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

Successfully merging this pull request may close these issues.

4 participants