Hey there! I’ve run into this exact problem before—nothing’s more frustrating than regex grabbing random strings that sort of look like your target format but aren’t actually valid. Let’s fix this for you.

First, the Core Pattern (Basic Format Match) #

If you just need to match the exact structure (and don’t need to validate that dates/times are actually calendar-valid, like avoiding 2008-13-32), use this regex:

\b\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2} [+-]\d{4}\b

Let’s break down what each part does:

• \b: Word boundary to prevent partial matches (e.g., it won’t grab abc2008-01-04 18:08:50 -0500def).
• \d{4}-\d{2}-\d{2}: Matches the date part (YYYY-MM-DD) with four-digit year, two-digit month, two-digit day.
• : Literal space separating date and time.
• \d{2}:\d{2}:\d{2}: Matches the time part (HH:MM:SS) with two-digit hour, minute, and second.
• : Another literal space separating time and timezone.
• [+-]\d{4}: Matches the timezone offset (either + or - followed by four digits, like -0500 or +0800).
• \b: Closing word boundary to stop the match at the end of the datetime.

For Strict Validation (Avoid Invalid Dates/Times) #

If you want to filter out impossible values (like 2008-13-32 or 25:61:62), use this stricter pattern that enforces basic calendar rules:

\b\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01]) ([01]\d|2[0-3]):[0-5]\d:[0-5]\d [+-]\d{4}\b

Key improvements here:

• (0[1-9]|1[0-2]): Ensures months are 01-12 (no 13 or 00).
• (0[1-9]|[12]\d|3[01]): Ensures days are 01-31 (covers all valid day ranges—note: this doesn’t account for February’s varying days; if you need that level of precision, post-processing with a datetime library is better than overcomplicating the regex).
• ([01]\d|2[0-3]): Ensures hours are 00-23 (no 25 or negative hours).
• [0-5]\d: Ensures minutes and seconds are 00-59 (no 60+ values).

Example Usage (Python) #

Here’s how you’d implement this to extract all matches from your file:

import re

# Load your text file content
with open("your_large_file.txt", "r") as f:
    text_content = f.read()

# Basic format match (grabs all structurally correct datetimes)
basic_pattern = r'\b\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2} [+-]\d{4}\b'
basic_matches = re.findall(basic_pattern, text_content)

# Strict validation match (returns only calendar-valid datetimes)
strict_pattern = r'\b(\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01]) ([01]\d|2[0-3]):[0-5]\d:[0-5]\d [+-]\d{4})\b'
strict_matches = [match[0] for match in re.findall(strict_pattern, text_content)]

# Output results
print("Basic format matches:", basic_matches)
print("Strict valid matches:", strict_matches)

Why You Might’ve Gotten Bad Results Before #

Chances are, your original regex was missing word boundaries (\b), which caused it to match partial strings embedded in longer text. Or you didn’t restrict the timezone to only +/- followed by four digits, leading to false positives like random number sequences that happened to have hyphens or colons.

内容的提问来源于stack exchange，提问作者ArchivistG