You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As in the last issue, the older distinction between the embedded-python branch and my master was based on dotnet2 compatibility. Since it is possible to compile and run the embedded-python code in dotnet2 with and older ironpython, I think the dotnet2/dotnet4 split can be re-thought after the embedded-python merger.
The text was updated successfully, but these errors were encountered:
As in the last issue, the older distinction between the embedded-python branch and my master was based on dotnet2 compatibility. Since it is possible to compile and run the embedded-python code in dotnet2 with and older ironpython, I think the dotnet2/dotnet4 split can be re-thought after the embedded-python merger.
The text was updated successfully, but these errors were encountered: