Skip to content
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

Fix #11117 #11147

Merged
merged 1 commit into from
May 7, 2015
Merged

Fix #11117 #11147

merged 1 commit into from
May 7, 2015

Conversation

ihnorton
Copy link
Member

@ihnorton ihnorton commented May 6, 2015

It's croaking here.
We backported 97381df (fix for #9773) which gives the nice error message,
but didn't remove the related assert, which was removed in 2604610.

I think this is safe to remove, but I don't have a 0.3 build handy. cc @tkelman

@tkelman
Copy link
Contributor

tkelman commented May 6, 2015

I'm confused, how did backporting an error message change make an assert no longer applicable?

@pao
Copy link
Member

pao commented May 6, 2015

I don't think it's that the first change causes the second, it's that the backport got the cosmetic part of the fix but not the actual fix?

@ihnorton
Copy link
Member Author

ihnorton commented May 6, 2015

@tkelman, you are right. Also, I realized there is potentially an unsafe branch if someone tried to redefine a non-generic with keyword args. Will update this later to error out instead of asserting.

@ihnorton
Copy link
Member Author

ihnorton commented May 7, 2015

Updated.

@tkelman
Copy link
Contributor

tkelman commented May 7, 2015

That makes more sense to me, thanks.

tkelman added a commit that referenced this pull request May 7, 2015
@tkelman tkelman merged commit e75612c into release-0.3 May 7, 2015
@tkelman tkelman deleted the fix11117 branch May 7, 2015 16:22
@tkelman
Copy link
Contributor

tkelman commented May 7, 2015

Guess this could've used a test too?

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.

None yet

3 participants