Initial creation of the IronPython SDK

[Lamparter]

This is an initial start at creating IronPython.Sdk, which allows you to enjoy the beautiful SDK-style project feature that modern .NET uses.

This SDK is also compatible with non-IronPython projects.

[Lamparter]

For example

An IronPython project should probably look like:

<Project Sdk="IronPython.Sdk" ToolsVersion="4.0">
  <PropertyGroup>
    <!-- Below is the default, but you can also specify "CPython" -->
    <PythonInterpreter>IronPython</PythonInterpreter>
    <PythonVersion>3.4</PythonVersion>
  </PropertyGroup>
</Project>

[Lamparter]

Tell me this isn't awesome 😁

[BCSharp]

Is it intended to work on macOS/Linux too? If it supports the debugger in VSCode it will be awesome! I have noticed many people were struggling with IronPython debugging.

On a more practical side, how about placing the SDK in src/tooling/IronPython.Sdk (i.e. rename sdk to tooling). In this way the directory can logically contain other, non-SDK tooling. For example, I am working (well, was working) on IPython/Jupyter support. So far it works without significant workarounds, but the version for Python 3.4 is no longer supported, so it is conceivable that some dedicated fork for IronPython will be needed. Another project idea is scaffolding for pylint or another linter) that understands CLR and .NET namespaces.

[Lamparter]

I know some Visual Studio engineers as well and I've been wondering about creating a Visual Studio/VS Code extension for using IronPython easily.

In VS Code the experience should be the same as with Python, and interacting with IronPython projects should be kept minimal - perhaps via a CLI to make it easiest

[Lamparter]

And yes, SDK style projects are supported by the dotnet.exe command, meaning that they can build on macOS/Linux in theory.

[Lamparter]

Another project idea is scaffolding for pylint or another linter) that understands CLR and .NET namespaces.

Unless I remember wrong, PTVS included this as well.

[slozier]

Neat. I guess this is meant to be a replacement for the PTVS pyproj? The pyproj support in Visual Studio isn't too bad (though it's using the old ugly non-SDK style projects). Although no debugging for IronPython. 🤷

For my personal use case being able to easily pick interpreters/environments is important. PTVS does something like this to define interpreters:

  <ItemGroup>
    <InterpreterReference Include="Global|IronPython|3.4" />
    <InterpreterReference Include="Global|PythonCore|3.9" />
  </ItemGroup>
  <ItemGroup>
    <Interpreter Include="env\">
      <Id>env</Id>
      <Version>3.4</Version>
      <Description>env (IronPython 3.4 (64-bit))</Description>
      <InterpreterPath>Scripts\ipy.exe</InterpreterPath>
      <WindowsInterpreterPath>Scripts\ipy.exe</WindowsInterpreterPath>
      <PathEnvironmentVariable>IRONPYTHONPATH</PathEnvironmentVariable>
      <Architecture>X64</Architecture>
    </Interpreter>
  </ItemGroup>

Not saying it's the best thing to do... I like auto-detect that VSCode does to detect interpreters (although it doesn't handle IronPython very well).

[Lamparter]

The project extension will still be pyproj (I think this will work, there's no actual way of knowing until the SDK gets published)

[Lamparter]

I don't think this works

[Lamparter]

This will be ready soon, no idea why the CI is suddenly failing.
I want to split this into multiple PRs.
I'm also interested in adding support for the built-in Visual Studio "Build" and "Rebuild" commands using ipyc.

[Lamparter]

I also want to add proper support for PackageReference.

[GeorgeS2019]

Question: will there a plan to continue ironclad3?

[BCSharp]

Update your main to the new main tip from the IronPython repo, then rebase your branch (starting from commit a5b0c4f) onto the new main tip. The rebase should proceed without conflicts.

[Lamparter]

Yep, just strange that it happened.

[BCSharp]

It's because I force-pushed the main branch, apologies. You will need to force-push your rebased branch too.

[Lamparter]

@slozier this PR is ready for review

[Lamparter]

@slozier?

[slozier]

If you're changing the path you also need to update the csproj that are referencing it.

[slozier]

@slozier?

Sorry, I just need to find more than 5 minutes to sit down and properly try it out.