Message281253
| Author |
lemburg |
| Recipients |
lemburg, vstinner, xdegaye, yan12125 |
| Date |
2016年11月20日.08:10:37 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<58315A7B.4010200@egenix.com> |
| In-reply-to |
<CAMpsgwai26L+Pe2vifzCKhStRMOcshN4u8i7uAjcyL2=cawytQ@mail.gmail.com> |
| Content |
On 20.11.2016 00:59, STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
>> I think we must use the reliable build time Android API level and
> implement sys.getandroidapilevel() (Victor patch) for knowing, in the
> standard library, whether we are running on an Android platform, and
> provide a best effort platform.android_ver() for the Android run time
> version. Things are changing very fast with the Android project and the OEM
> may add their own changes too.
>
> Hum, IMO we should at least use a structure with names for the sys function
> to be able to return more information later.
>
> Maybe call the function sys.getandroidversion()?
Since this is an OS level interface, it should either go into
the os module or, if it doesn't rely on a C API, into the platform
module (see e.g. the platform.win32_ver() and .mac_ver() APIs
as example).
I don't think the sys module is the right place to put the API,
since it doesn't have anything to do with the Python system
internals. |
|