-
Notifications
You must be signed in to change notification settings - Fork 635
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
[DYN-2322] Add PythonNet 3.7 CPython as a selectable engine. #10548
Conversation
Still needs to uncomment python autocompletion code and fix one failing test.
We can’t remove these - patch installer yada yada - if you want we can replace them with empty binaries.
… On Apr 17, 2020, at 2:07 AM, reddyashish ***@***.***> wrote:
@reddyashish commented on this pull request.
In test/Libraries/DynamoPythonTests/IronPythonTests.csproj:
> @@ -46,18 +46,6 @@
<HintPath>..\..\..\src\packages\IronPython.2.7.9\lib\net45\IronPython.dll</HintPath>
<Private>True</Private>
</Reference>
- <Reference Include="IronPython.Modules, Version=2.7.9.0, Culture=neutral, PublicKeyToken=7f709c5b713576e1, processorArchitecture=MSIL">
Removed these IronPython.Modules, IronPython.SQLLite and IronPython.Wpf binaries as they were not being used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Also I am fairly certain ironpython modules is used to include certain parts of the standard modules - like math - they may not be required if the std library we include includes them but I would be wary about these - anything used by ironpython may only have runtime dependencies - not compile time - so if proving it’s not used will be hard.
… On Apr 17, 2020, at 2:07 AM, reddyashish ***@***.***> wrote:
@reddyashish commented on this pull request.
In test/Libraries/DynamoPythonTests/IronPythonTests.csproj:
> @@ -46,18 +46,6 @@
<HintPath>..\..\..\src\packages\IronPython.2.7.9\lib\net45\IronPython.dll</HintPath>
<Private>True</Private>
</Reference>
- <Reference Include="IronPython.Modules, Version=2.7.9.0, Culture=neutral, PublicKeyToken=7f709c5b713576e1, processorArchitecture=MSIL">
Removed these IronPython.Modules, IronPython.SQLLite and IronPython.Wpf binaries as they were not being used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@mjkkirschner Yes, will add them back. |
</ItemGroup> | ||
<ItemGroup> | ||
<EmbeddedResource Include="Resources\property.png" /> | ||
</ItemGroup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any specific reason for moving things from PythonNodeModelsWpf
to here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These property are being used for the auto-completion feature and we have moved all the auto-completion code to the DSIronPython project. The idea was not to have this PythonNodeModelsWPF project directly depend on any python binaries.
</assembly> | ||
<namespaces> | ||
<namespace name="DSIronPython"> | ||
<category>Core.Scripting</category> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@reddyashish why is this being deleted? This will effect where nodes go in the library won't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure where this xml is used but the python node is being saved in the Script -> Editor folder in the library section(same as before).
Overall looks good to me and fairly safe to merge into the feature branch for our next moves.
@aparajit-pratap @mjkkirschner Any other notes? |
…t being used. These binaries are added as reference to the DSIronPython project and the private flag is set to true. So the binaries are being copied to the bin folder.
<Reference Include="ICSharpCode.AvalonEdit"> | ||
<HintPath>..\..\..\extern\avalonEdit\ICSharpCode.AvalonEdit.dll</HintPath> | ||
<Private>False</Private> | ||
</Reference> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mjkkirschner The IronPython SQL, Modules and WPF binaries are already added as references here to the DSIronPython project and the private flag is set to true. So the binaries are copied to the bin folder.
@QilongTang Yes, I will add an empty project in place of DynamoPython. |
@reddyashish Looks good, can we merge this now? |
@DynamoDS/dynamo I am merging this so that BRE can test branch builds on new VM.. |
<ProjectReference Include="..\DSIronPython\DSIronPython.csproj"> | ||
<Project>{9eef4f42-6b3b-4358-9a8a-c2701539a822}</Project> | ||
<Name>DSIronPython</Name> | ||
<Private>False</Private> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@reddyashish FYI
Purpose
This PR is a cloned from the original PR(#10472) by @Dewb.
The auto-completion part for the IronPython is fixed. The IronPythonCompletionData and IronPythonCompletionProvider classes have been moved from the PythonNodeModelsWPF project to the DSIronPython project. We can extend this similarly with the new DSCPython.
There is only one failing test left that is related to function marshaling: FirstClassFunctions
Declarations
Check these if you believe they are true
*.resx
filesReviewers
@DynamoDS/dynamo