-
Notifications
You must be signed in to change notification settings - Fork 188
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
CPython3 - 'System.Reflection.Emit.TypeBuilder' was not found. #3008
Comments
Related issue |
@Cyril-Pop @AhmadEltobshy We have plans to update the PythonNET bridge project as per our roadmap that should resolve a lot of CPython parity issues with IronPython. We're not yet sure of the full extent, but it should be significantly better than today. |
@Amoursol |
@Cyril-Pop unfortunately no, the one thing we really cannot do is give out dates. What I can say is that we are in planning phase and active work will start on the 1st May and are committed to enhancing the CPython experience as much as we can within the bounds of resourcing, time and other commitments. It's the top of our priority list for Q2 (May - July). |
I have exactly the same problem with Civil 3D 2024.3. I also create a Form class. I will be praying for it to fix between May and July. Thank you for the information. |
I have the same error when using winforms. |
Was anybody able to find a solution for that? It seems that this is due to the fact that dynamo 2.19 uses cpython and not ironpython anymore |
Dynamo Version
Dynamo 2.19.3
Revit Version
Revit 2024.2
Operating System
Windows 11
What did you do?
try to use events subscription with CPython3
What did you expect to see?
No Error
What did you see instead?
a Python error
Example 1
Example 2
Stacktrace/logs
No response
Details
the error seems related to the build/compilation of PythonNet 2.5.2 (Python.Runtime) with Net.Standard 2.0 as target
there are potentially others PythonNet 2.5.2 issues due to this change (Net Framework -> Net.Standard 2.0),
will probably be resolved in PythonNet 3.x.x
The text was updated successfully, but these errors were encountered: