[issue42970] File path with blank causes open error in 3.8, not in 3.7

Ronald Oussoren added the comment: This might be a security feature in Big Sur, access to some locations is restricted by default. I'm not sure if that includes ~/Library, it definitely affects access to ~/Documents. I'd expect to see a security pop-up from the system though. I cannot repro

[issue42970] File path with blank causes open error in 3.8, not in 3.7

Serhiy Storchaka added the comment: Please provide complete script that reproduces the issue. The provided three lines do not open any file and cannot generate such error. It could help to add the debug prints: print(f'mySrcFldr = {mySrcFldr!a}') print(f'srcFldr = {srcFldr!a}') print(f'f = {

[issue42970] File path with blank causes open error in 3.8, not in 3.7

Ronald Oussoren added the comment: What kind of error do you get? -- nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-l

[issue42970] File path with blank causes open error in 3.8, not in 3.7

Doug Day added the comment: To clarify: either python version generates the same path. On 3.8.2 though an open error results -- ___ Python tracker ___ ___

[issue42970] File path with blank causes open error in 3.8, not in 3.7

New submission from Doug Day : The following code generates a path that works in Pythons 3.7.6 on macOS Big Sur but not in Catalina with 3.8.2.. mySrcFldr="~/Library/Mobile Documents/com~apple~CloudDocs/Utilities/" srcFldr=os.path.expanduser(mySrcFldr) f=os.path.join(srcFldr,"mortgage.py") W