Fix regex patterns in pyproject.toml

[Banana-sa]

User description

fixing unescaped backslashes in regular expressions within the TOML strings.
this original was causing error during installation on ubuntu 22.04.

---

PR Type

Bug fix

---

Description

• Fix unescaped backslashes in regex patterns within pyproject.toml

• Escape backslash characters in exclude_lines patterns

• Resolve installation errors on Ubuntu 22.04

---

Diagram Walkthrough

flowchart LR
  A["Unescaped regex patterns"] -- "Add backslash escapes" --> B["Valid TOML regex strings"]
  B -- "Fixes installation" --> C["Successful package installation"]

Loading

File Walkthrough

	Relevant files
Bug fix	pyproject.toml Escape regex backslashes in coverage exclude patterns        pyproject.toml Escaped backslash in \b word boundary to \\b in class pattern Escaped backslash in \. literal dot to \\. in abstractmethod pattern Ensures proper regex interpretation in TOML string context +3/-3

---

Summary by CodeRabbit

• Chores
  • Fixed coverage configuration to properly handle regex escape sequences.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The changes fix regex pattern escaping in the pyproject.toml coverage exclude list by replacing improperly escaped backslash sequences with double-escaped forms, ensuring valid regex patterns for coverage exclusion rules.

Changes

Cohort / File(s)	Summary
Coverage configuration pyproject.toml	Fixed regex escape sequences in coverage exclude patterns by properly escaping backslashes (e.g., \\b → \\\\b, \\ → \\\\)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify regex escape sequences are correctly doubled to match TOML string literal requirements

Poem

🐰 A backslash walks in, then another, then one more,
Escaping escapes till the patterns restore!
Double-double the slashes, the coverage runs free,
Regex rules reign supreme in the TOML decree! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Fix regex patterns in pyproject.toml' directly and accurately reflects the main change: correcting improperly escaped backslashes in regex patterns within the TOML configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 396af7e and 241406b.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

🔇 Additional comments (1)

pyproject.toml (1)

71-72: Correct and necessary TOML string escaping for regex patterns.

The changes properly escape backslashes in double-quoted TOML strings. Within basic strings, backslashes must be escaped to produce literal regex metacharacters:

• \\b produces the regex word boundary \b
• \\. produces the regex escaped dot \.
• \\) produces the regex escaped paren \)

Without these fixes, the TOML parser would reject the unescaped sequences, causing the installation failure reported on Ubuntu 22.04. The regex patterns themselves are semantically correct for coverage exclusion.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.