[Python-ideas] os.architecture
anatoly techtonik
techtonik at gmail.com
Wed Jan 1 12:58:35 CET 2014
On Mon, Dec 30, 2013 at 3:13 PM, Andrew Barnert <abarnert at yahoo.com> wrote:
> On Dec 30, 2013, at 0:56, anatoly techtonik <techtonik at gmail.com> wrote:
>
>> Ok. Architecture is a fail in terminology. The word "OS architecture"
>> can mean many things, and it will be the same design flaw as os.name.
>>
>> How about os.bitness instead?
>
> You missed the part where you were told that os is for OS services, not platform (including hardware, interpreter, and OS) information.
I've heard your opinion. Now why do you think os is for OS services?
Docs say os is about OS interfaces, to which bitness or architecture
is interface information.
> Anyway, "bitness" by itself doesn't tell you whether it will return 32 or 64 when running a 32-bit Python on 64-bit Windows
That's why it is "os.bitness", not "interpreter.bitness" or "cpu.bitness".
> It's just as potentially ambiguous as the functions that already exist
Do you still think so after my example above?
More information about the Python-ideas
mailing list