How to support IronPython 2.7 and 3.4 in one app? #1798

Activity

1. slozier commented on May 3, 2024

   

   slozier

   on May 3, 2024

   Contributor

   More actions

   I store the IronPython specific assemblies in separate (IronPython2/IronPython3) folders. I have an assembly resolver which is used to load the appropriate assemblies from their respective folders. Then, using a common DLR I create engines for each. Something like this:

   public sealed class PythonEngine
   {
       static PythonEngine()
       {
           AppDomain.CurrentDomain.AssemblyResolve += IronPythonResolver;
       }
   
       private static readonly Version Ipy2Version = new Version(2, 7, 12, 0);
       private static readonly Version Ipy3Version = new Version(3, 4, 1, 0);
   
       private static LanguageSetup GetLanguageSetup(int version)
       {
           if (version == 3)
           {
               return new LanguageSetup(
                   $"IronPython.Runtime.PythonContext, IronPython, Version={Ipy3Version}, Culture=neutral, PublicKeyToken=7f709c5b713576e1",
                   "IronPython 3",
                   new[] { "IronPython3" },
                   new[] { ".py" }
               );
           }
           else
           {
               return new LanguageSetup(
                   $"IronPython.Runtime.PythonContext, IronPython, Version={Ipy2Version}, Culture=neutral, PublicKeyToken=7f709c5b713576e1",
                   "IronPython 2",
                   new[] { "IronPython2" },
                   new[] { ".py" }
               );
           }
       }
   
       public static ScriptEngine Create(int version, IDictionary<string, object?>? options = null)
       {
           ScriptRuntimeSetup setup = new ScriptRuntimeSetup();
   
           var languageSetup = GetLanguageSetup(version);
   
           if (options != null)
           {
               foreach (var entry in options)
               {
                   setup.Options.Add(entry.Key, entry.Value);
               }
           }
   
           setup.LanguageSetups.Add(languageSetup);
           var runtime = new ScriptRuntime(setup);
           return runtime.GetEngine(languageSetup.Names[0]);
       }
   
       private static Assembly? IronPythonResolver(object? sender, ResolveEventArgs args)
       {
           if (args.Name is null) return null;
           var assemblyName = new AssemblyName(args.Name);
   
           if (assemblyName.Name != null && assemblyName.Version != null && (assemblyName.Name.StartsWith("Microsoft.Scripting", StringComparison.Ordinal) || assemblyName.Name == "Microsoft.Dynamic"))
           {
               var path = Path.Combine(Application.ProgramPath, assemblyName.Name + ".dll");
               return File.Exists(path) ? Assembly.LoadFile(path) : null;
           }
   
           if (assemblyName.Name != null && assemblyName.Version != null && assemblyName.Name.StartsWith("IronPython", StringComparison.Ordinal))
           {
               var path = Path.Combine(Application.ProgramPath, assemblyName.Version.Major == 3 ? "IronPython3" : "IronPython2", assemblyName.Name + ".dll");
               return File.Exists(path) ? Assembly.LoadFile(path) : null;
           }
   
           return null;
       }
   }
2. IronLanguages

   locked and limited conversation to collaborators on May 3, 2024
3. slozier

   converted this issue into a discussion #1799 on May 3, 2024