Skip to content

Fix crash due to deserialization of TypedDict type objects #3275

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 2 commits into from
Apr 28, 2017

Conversation

JukkaL
Copy link
Collaborator

@JukkaL JukkaL commented Apr 28, 2017

A TypeInfo attribute was not handled during fixup, causing a crash when
using a TypedDict type imported from a deserialized module in an
annotation (when using -i).

Fixes #3272.

JukkaL added 2 commits April 28, 2017 14:07
A TypeInfo attribute was not handled during fixup, causing a crash when
using a TypedDict type imported from a deserialized module in an
annotation.

Fixes #3272.
JukkaL added a commit that referenced this pull request Apr 28, 2017
The test cases use a serialized module in incremental mode
in various ways to make sure that all important information
in the AST nodes is preserved during serialization and
deserialization.

These are all very straightforward. The idea is to help catch
regressions early and to make it easier to refactor or optimize
serialization code. These found 2 issues -- separated the first
to PR #3275. The second issue (#3274) is still unfixed and there
is a skipped test case for it.

More complex cases such as import cycles will still go to
check-incremental.test.
@JukkaL
Copy link
Collaborator Author

JukkaL commented Apr 28, 2017

Appveyor failures seem to be flakes (access denied errors).

@gvanrossum
Copy link
Member

Appveyor failures seem to be flakes (access denied errors).

Hopefully #3239 should fix that. But I feel the need to review it very carefully before merging it.

This PR looks fine and I'm merging it now.

@gvanrossum gvanrossum merged commit 088e7e3 into master Apr 28, 2017
@gvanrossum gvanrossum deleted the fix-typeddict-deserialize branch April 28, 2017 17:53
JukkaL added a commit that referenced this pull request May 5, 2017
The test cases use a serialized module in incremental mode
in various ways to make sure that all important information
in the AST nodes is preserved during serialization and
deserialization.

These are all very straightforward. The idea is to help catch
regressions early and to make it easier to refactor or optimize
serialization code. These found 2 issues -- separated the first
to PR #3275. The second issue (#3274) is still unfixed and there
is a skipped test case for it.

More complex cases such as import cycles can still go to
check-incremental.test.
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.

Incremental crash caused by TypedDict deserialization
2 participants