What remains to be done for a release of IronPython2 to support .NET Core?
Cloning the repo and building locally works fine in my project, but it'd be
nice to know what issues remain that prevent a full release. If there's
something I can do to contribute, I'd be interested to know that as well.
T
Oops, I got the message to use groups.io and see my question is already
answered there. Cheers!
For the archives:
https://ironpython.groups.io/g/users/topic/dlr_and_ironpython/6249360?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,6249360
On Wed, Nov 1, 2017 at 2:06 PM Josiah Kiehl wrote
I'm trying to execute this example code:
https://stackoverflow.com/questions/32639893/call-dll-function-from-c-sharp-ironpython
I realize the posted question is a few years old at this point... has
something changed in how python, compiled to a DLL via clr.CompileModule,
is loaded?
I'm getting th
Oh, I'm on dotnet 2.0.3, if that's relevant information.
On Tue, Apr 3, 2018 at 2:15 PM Josiah Kiehl wrote:
> I'm trying to execute this example code:
>
> https://stackoverflow.com/questions/32639893/call-dll-function-from-c-sharp-ironpython
>
> I realize the post
ion of IronPython does not support assembly generation.
> I haven't tried it myself, but you could probably compile the assembly
> using the full framework version and then run it with .NET Core 2.0
> (assuming you're not using unsupported APIs).
>
> Stéphane
>
>
> O
2.0 application? The .NET Core API
> doesn't expose System.Runtime.CompilerServices.Closure so that might be the
> reason things are failing...
>
> Stéphane
>
> On Tue, Apr 3, 2018 at 5:53 PM, Josiah Kiehl wrote:
>
>> Sorry if I'm not understanding... when you
to
> compile the code for .NET Core and the assembly generated using full .NET
> doesn't work...
>
> Stéphane
>
> On Wed, Apr 4, 2018 at 1:38 PM, Josiah Kiehl wrote:
>
>> Oh! I understand now, thanks for clarifying. Yes, that's the problem. You
>> mentioned that t
