IronLanguages / IronLanguages/ironpython3
future feature is not defined:annotations
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
python: 3.11.2
ironpython: 3.4.0
vs studio: vs 2022
Description
`
ScriptRuntime pyRuntime = Python.CreateRuntime();
var engine = Python.CreateEngine();
var pyScope = engine.CreateScope();
var paths = engine.GetSearchPaths();
string pathToVirtualEnv = @"C:\Program Files\Python311";
paths.Add(pathToVirtualEnv +@"\Lib");
paths.Add(pathToVirtualEnv + @"\Lib\site-packages");
paths.Add(pathToVirtualEnv + @"\DLLs");
engine.SetSearchPaths(paths);
dynamic py = engine.ExecuteFile(AppContext.BaseDirectory + @"IAMed/prescript_cluster.py");
`
when run at " dynamic py = engine.ExecuteFile(AppContext.BaseDirectory + @"IAMed/prescript_cluster.py");"
show error: future feature is not defined:annotations
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported failure in the C# host using Python 3.11 and the referenced IAMed/prescript_cluster.py file, focusing on the ExecuteFile call and the annotations future feature. Trace the IronPython handling of that feature and compare the behavior with the script's expected Python syntax; done means the script loads without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100