Test failure on Windows/Python 3.13 and Multiple debug print statements in test suite

[Shrikantgiri25]

Hi DRF maintainers!

I've encountered a couple of issues while running the test suite on Windows 11 with Python 3.13 that may need to be addressed.

---

Issue 1: TestRegularFieldMappings.test_regular_fields Fails on Windows/Python 3.13

What's Happening

The test tests/test_model_serializer.py::TestRegularFieldMappings::test_regular_fields fails with:

AssertionError: assert None is not None

The regex pattern doesn't match the serializer's repr() output.

Environment

• OS: Windows 11
• Python: 3.13.x
• DRF: Latest main branch

Root Cause

After debugging, I identified three platform-specific issues:

1. Windows file path format

   • tempfile.gettempdir() returns C:\Users\USERNAME\AppData\Local\Temp with backslashes
   • The regex pattern doesn't escape these backslashes properly
   • Causes pattern match to fail

2. Platform-specific object representations

   • Memory addresses in <tests.test_model_serializer.CustomField: custom_field> vary
   • Strict regex expects exact match but gets platform variations

3. Python 3.13 repr() changes

   • Some field representations like IntegerField(max_value=...) include additional details
   • Breaks the strict pattern matching

Proposed Solution

1. Escape backslashes in Windows paths using replace('\', r'\\') or re.escape(tempfile.gettempdir()).
2. Relax regex for dynamic fields like IntegerField or CustomField using .* to accommodate platform-specific details.
3. Use re.DOTALL flag in re.search to allow multi-line matching.
4. Keep static fields strictly validated (e.g., char_field, date_field) to maintain integrity of the test.

This maintains validation integrity while accommodating platform differences.

---

Issue 2: Debug Print Statements in test_openapi.py

What's Happening

The file tests/schemas/test_openapi.py contains multiple print() statements that appear to be leftover debugging code.

Impact

• Clutters test output
• Makes it harder to identify actual test failures
• Doesn't follow test best practices

Proposed Solution

Remove all print() statements from the file for cleaner test output.

---

Questions for Maintainers

1. Windows support: Is running the test suite on Windows a priority for DRF? Should these tests work cross-platform?

2. Approach validation: Does making the regex more flexible (using .* for dynamic fields) align with the test's validation intent?

3. PR structure: Would you prefer:

   • One PR addressing both issues
   • Separate PRs for each
   • Just focus on the test failure for now

---

Impact If Fixed

1. Windows developers can run the full test suite locally
2. Cleaner, more professional test output
3. Maintains validation logic while supporting multiple platforms

---

My Testing

I've already:

• Tested the proposed regex fix locally on Windows 11/Python 3.13
• Verified all other tests in the file still pass
• Confirmed validation logic is maintained
• Identified the specific print statements to remove

I'm ready to submit a PR once I get feedback on the approach!

---

Additional Context

1. I'm working on contributing to DRF and want to ensure my local test environment is fully functional. This led me to discover these issues that likely affect other Windows developers as well.
2. I have tested the failing test on WSL (Ubuntu) and it passes there, but it fails when running directly on Windows, indicating a platform-specific issue.

Thanks for maintaining such an excellent project!

Looking forward to your guidance on how to proceed.

Screenshots

[Shrikantgiri25]

Hi DRF maintainers ,

I have submitted a Pull Request addressing the above issues:

• Fixes TestRegularFieldMappings.test_regular_fields on Windows/Python 3.13 by updating regex and escaping Windows paths.
• Removes leftover print() statements in test_openapi.py.
• Ensures all tests pass locally and validation logic is preserved.

PR link: #9808

Looking forward to your feedback!
Thank you for your time and consideration.