Skip to content

bpo-13349: Improve the error message for tuple.index #1309

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 1 commit into from

Conversation

Zaharid
Copy link

@Zaharid Zaharid commented Apr 26, 2017

When the required value is not found, use the same template as
list.index and display the missing value instead of 'x'. The original issue with the discussion is: https://bugs.python.org/issue13349

When the required value is not found, use the same template as
list.index and display the missing value instead of 'x'.
@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 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!

@mention-bot
Copy link

@Zaharid, thanks for your PR! By analyzing the history of the files in this pull request, we identified @serhiy-storchaka, @rhettinger and @tiran to be potential reviewers.

@louisom
Copy link
Contributor

louisom commented Apr 27, 2017

@Zaharid You will need to put the bpo issue number at the front of the title: bpo-13349: Improve..., also, you will need to signed the CLA first.

@Zaharid Zaharid changed the title Improve the error message for tuple.index bpo-13349: Improve the error message for tuple.index Apr 27, 2017
@DimitrisJim
Copy link
Contributor

Hi, @Zaharid and thanks for the patch. I had already created a PR for this issue here #876 already, though :-).

@berkerpeksag
Copy link
Member

berkerpeksag commented Apr 27, 2017

Closing this as a duplicate of #876.

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

Successfully merging this pull request may close these issues.

6 participants