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
Importing fails in scenarios where a base class exposes a virtual properties that is in a nuget package and the library was built but not published.
This occurs even if that property is marked [CLSCompliant(false)].
The class that exposes that property often will import just fine, and some but not all classes that derive from it will import successfully. I've yet to decipher the pattern.
The main issue is that the error message does not identify with useful information what is wrong. It simply cannot import the type exposing the property.
Steps to Reproduce
In C#, create a (generic?) class that exposes a public virtual property with type that comes from a nuget package.
Derive from this class a (non-generic?) child class
Build your solution
Link IronPython to the resulting DLL
Try to import the type in IronPython
Expected behavior:
ipy identifies the dependency on a nuget package (potentially not technically possible) OR
ipy produces a meaningful error that states the type exposed by the property cannot be found
Actual behavior:
A non-helpful error message that it cannot import one or more classes deriving from the base class that exposes the property
Work around / Solution
Publish the C# DLL, don't just build it. This should have been done in the first place - my error - but ipy gives such an unhelpful error message that it has cost a lot of development time to discover the issue.
Version Information
IronPython 3.4.2 (3.4.2.1000)
[.NETCoreApp,Version=v8.0 on .NET 8.0.11 (64-bit)]
The text was updated successfully, but these errors were encountered:
Then in IronPython I can import Class2 without issues. If I try to use it I do get a FileNotFoundError with the expected error message:
FileNotFoundError: [Errno 2] Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. The system cannot find the file specified.
I have since altered the code that lead to that exact example and not kept the old version, but something similar is as follows.
C# Code. TorchSharp is a NuGet package. Canary is there for a sanity check.
namespace FlipProof.Torch;
public class Canary { }
public abstract class BobBase
{
[CLSCompliant(false)]
public TorchSharp.Reduce MyProperty { get; init; }
}
public sealed class Bob : BobBase
{ }
Publish then and delete the torchsharp dll or, I suppose, just build the code and check torchsharp hasn't been copied into the bin dir.
Then in python
import clr
import sys
import os
csharpLibraryDir = path-to-the-bin-dir-for-c#
sys.path.append(csharpLibraryDir)
clr.AddReferenceToFileAndPath("FlipProof.Torch")
from FlipProof.Torch import Canary # Passes
from FlipProof.Torch import Bob # ImportError: Cannot import name Bob
from FlipProof.Torch import BobBase # ImportError: Cannot import name BobBase
then call ipy <name of your python file>
Some important notes:
both the child and base classes fail to import here, which differs from my initial report. Both have been seen.
In this example, virtual doesn't make a difference. In my other code, removing virtual solved the issue
I have an example that will fail in the way I said originally but the codebase is much more complicated and so I don't think it's a good starting point...
If torch.Size is changed to a reference type, no error occurs
Prerequisites
Description
Importing fails in scenarios where a base class exposes a
virtual
properties that is in a nuget package and the library was built but not published.This occurs even if that property is marked
[CLSCompliant(false)]
.The class that exposes that property often will import just fine, and some but not all classes that derive from it will import successfully. I've yet to decipher the pattern.
The main issue is that the error message does not identify with useful information what is wrong. It simply cannot import the type exposing the property.
Steps to Reproduce
Expected behavior:
Actual behavior:
A non-helpful error message that it cannot import one or more classes deriving from the base class that exposes the property
Work around / Solution
Publish the C# DLL, don't just build it. This should have been done in the first place - my error - but ipy gives such an unhelpful error message that it has cost a lot of development time to discover the issue.
Version Information
IronPython 3.4.2 (3.4.2.1000)
[.NETCoreApp,Version=v8.0 on .NET 8.0.11 (64-bit)]
The text was updated successfully, but these errors were encountered: