You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the May 8th tools call, I noticed the macOS directory/archive was named 'MacOs'.
It would be nice if the capitalization was fixed to be either 'MacOS', or more correctly 'macOS' (see https://www.apple.com/macos/ventura/).
What Python version are you using?
Python 3.11
Reproduction steps
N/A
Expected behavior
N/A
Execution Environment
No response
Pip packages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
At least whenever I originally saw the case chosen, I preferred Pascal case because:
This project is within TianoCore and it is "edk2" pytool extensions and the EDK II C Coding Standard - Directory Names section explicitly uses Pascal case (e.g. IA32 -> Ia32, DXE -> Dxe, etc.).
From a programmatic standpoint, this directory name is consumed by other code, and I prefer consistency of those names rather than arbitrary naming choices which makes things especially more straightforward on case-sensitive systems.
If Pascal case is kept, it would be nice to change ARM to Arm. If case is matched to the origin name, I'd prefer macOS.
I don't really have a strong opinion either way just wanted to provide my perspective.
If Pascal case is kept, I'd prefer 'Macos' or "macos", treating it as a single word.
"Arm" is really more correct nowadays, except if you're referring to the Architecture Reference Manual!
They changed the capitalization from 'ARM' to 'Arm' in 2017.
Contact Details
[email protected]
Describe the Bug
On the May 8th tools call, I noticed the macOS directory/archive was named 'MacOs'.
It would be nice if the capitalization was fixed to be either 'MacOS', or more correctly 'macOS' (see https://www.apple.com/macos/ventura/).
What Python version are you using?
Python 3.11
Reproduction steps
N/A
Expected behavior
N/A
Execution Environment
No response
Pip packages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: