coderabbit fixes

Author: marcomq

README.md

@@ -101,8 +101,10 @@ That keeps calls independent and easy to use from Rust async code, but it is not
 the same as a shared long-running Python event loop. If you need shared Python
 async state, keep it in Python globals or wrap the behavior in a Python function.
 
-`call_async_function` is only available with the default PyO3 backend. The
-RustPython backend currently reports async function calls as unsupported.
+`call_async_function` is part of the public API for both backends, but only the
+default PyO3 backend provides runtime support for awaiting Python coroutines.
+With the RustPython backend, calling `call_async_function` returns an unsupported
+error at runtime.
 
 ### Thread Safety
 

src/rustpython_runner.rs

@@ -215,12 +215,7 @@ fn print_err_msg(vm: &VirtualMachine, error: PyRef<PyBaseException>) -> String {
         println!("Traceback (most recent call last):");
         for trace in tb.iter() {
             let file = trace.frame.code.source_path.as_str();
-            let original_line = trace.lineno.get();
-            let line = if file == "main.py" {
-                original_line - 2 // sys.path import has 2 additional lines
-            } else {
-                original_line
-            };
+            let line = trace.lineno.get();
             println!(
                 "  File \"{file}\", line {line}, in {}",
                 trace.frame.code.obj_name