Skip to content

Fix bad html report bug #710

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

Merged
merged 1 commit into from
Jun 15, 2015
Merged

Fix bad html report bug #710

merged 1 commit into from
Jun 15, 2015

Conversation

o11c
Copy link
Contributor

@o11c o11c commented Jun 13, 2015

Previously, HTML reports were horribly broken. The stub .pyi files for the standard library would be overwritten with the html report for the same file, so mypy could only run once.

This fixes both of the bugs that let that happen.

There should probably be a testcase to make sure this sort of things would not happen again.

@JukkaL
Copy link
Collaborator

JukkaL commented Jun 15, 2015

Ouch, that was a nasty bug. Thanks for fixing it!

Yeah, there should be test cases for HTML report generation. The report generator hasn't received a lot of love recently -- it was originally a quick hack and I haven't really touched it since.

JukkaL added a commit that referenced this pull request Jun 15, 2015
@JukkaL JukkaL merged commit 6cafa35 into python:master Jun 15, 2015
@o11c
Copy link
Contributor Author

o11c commented Jun 15, 2015

It might be saner to rewrite report generation to "output" (even if not on disk) XML, then use XSLT to generate the HTML.

This would require adding a dependency on lxml and shipping a couple of data files.

@o11c o11c deleted the html-report-bug branch June 15, 2015 03:37
@o11c
Copy link
Contributor Author

o11c commented Jun 23, 2015

Note for posterity, I did the XSLT thing in #713

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.

2 participants