REGEXVAULT
Dev & Systems/Log Parsing
ReDoS Checked

Python Stack Trace Frame Regex for PHP

/^\s*File "[^"]+", line [0-9]+, in [^\s]+$/

All five implementations are free. Switch engines without signing in.

What this pattern does

This page provides a well-structured, multi-part regular expression for matching python stack trace frame, ported and verified for PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.

Php Implementation

Php
<?php
// Python Stack Trace Frame
// ReDoS-checked | RegexVault — Dev & Systems > Log Parsing

define('PYTHON_STACK_TRACE_FRAME_PATTERN', '/^\s*File "[^"]+", line [0-9]+, in [^\s]+$/');

function validate_python_stack_trace_frame(string $input): bool {
    return (bool) preg_match(PYTHON_STACK_TRACE_FRAME_PATTERN, $input);
}

// Example
var_dump(validate_python_stack_trace_frame("  File "/app/main.py", line 42, in main")); // bool(true)

Test Cases

Matches (Valid)
Rejects (Invalid)
File "/app/main.py", line 42, in mainFile main.py, line 42, in main
File "<stdin>", line 1, in <module> File main.py, line 42
File "/usr/lib/python3.11/threading.py", line 1016, in _bootstrapTraceback (most recent call last):

When to use this pattern

This pattern is drawn from the Dev & Systems > Log Parsing category and has been checked for ReDoS risk. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

<module> (top-level code) and <listcomp> (list comprehension) are valid function name fields. The pattern's [a-zA-Z_] start allows these via the <> inclusion.

Technical Notes

Groups: 1=file path (can be <stdin> or <string>), 2=line number, 3=function name (<module> for top-level code). The < > characters in group 3 handle <module>, <listcomp>, etc.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Submissions join the review queue after automated validation.

Submit a Pattern