-
Notifications
You must be signed in to change notification settings - Fork 229
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
Wrapping __import__ affects accessibility of some properties #805
Labels
Comments
Thanks for the report. It looks like when Here's a slightly simplified check.py:
Unfortunately I can't think of a workaround, but please let me know if you find a solution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
IronPython 2.7.11 (2.7.11.1000) NETFramework,Version=v4.5 on .NET Framework 4.8.4300.0 (64-bit)]
Description
Wrapping __builtin__.__import__ appears to affect visibility/accessibility of certain properties of builtin classes,
but only when it is done outside of __main__.
Specifically, when trying to check the type of a generic list by reading the PropertyType of its Item property
and using the unmodified import, this will succeed:
Adding a simple wrapper around __import__ will also work:
But once the wrapper is moved to its own module, the assertion fails and the PropertyType is no longer accessible:
However, access to the property can be restored by importing List again using the unmodified __import__ function.
The text was updated successfully, but these errors were encountered: