Describe the bug
CI is failing on Windows for (recently released) Python 3.12.0a5.
==============================================================================
FAIL: tests/platforms/android/gradle/test_create.py::test_extract_packages[test_sources8-"leading"]
------------------------------------------------------------------------------
test_sources=['//leading']
app.test_sources=['//leading']
{'extract_packages': '""',
'safe_formal_name': 'First App',
'version_code': '100'}
Traceback (most recent call last):
File "C:\Users\user\github\beeware\briefcase\tests\platforms\android\gradle\test_create.py", line 112, in test_extract_packages
assert context["extract_packages"] == expected
AssertionError: assert '""' == '"leading"'
- "leading"
+ ""
==============================================================================
FAIL: tests/platforms/android/gradle/test_create.py::test_extract_packages[test_sources21-"leading"]
------------------------------------------------------------------------------
test_sources=['\\\\leading']
app.test_sources=['\\\\leading']
{'extract_packages': '""',
'safe_formal_name': 'First App',
'version_code': '100'}
Traceback (most recent call last):
File "C:\Users\user\github\beeware\briefcase\tests\platforms\android\gradle\test_create.py", line 112, in test_extract_packages
assert context["extract_packages"] == expected
AssertionError: assert '""' == '"leading"'
- "leading"
+ ""
------------------------------------------------------------------------------
(output augmented to include additional information)
Steps to reproduce
Run CI.
Expected behavior
CI should succeed.
I believe this CPython change is causing this new behavior.
I am not entirely sure what is necessary to resolve this, though. Based on the CPython fix, these are not really valid paths for Windows.
Notably, this CPython fix was backported to 3.11.
Screenshots
No response
Environment
- Operating System: Windows 10
- Python version:
3.12.0a5
- Software versions:
- Briefcase:
0.3.13.dev33+g8d503064.d20230208
Logs
No response
Additional context
No response
Describe the bug
CI is failing on Windows for (recently released) Python 3.12.0a5.
(output augmented to include additional information)
Steps to reproduce
Run CI.
Expected behavior
CI should succeed.
I believe this CPython change is causing this new behavior.
I am not entirely sure what is necessary to resolve this, though. Based on the CPython fix, these are not really valid paths for Windows.
Notably, this CPython fix was backported to 3.11.
Screenshots
No response
Environment
3.12.0a50.3.13.dev33+g8d503064.d20230208Logs
No response
Additional context
No response