Mailman 3 August 2014 - Python-Dev

Re: [Python-Dev] sum(...) limitation
by Stephen J. Turnbull Aug. 14, 2014

Aug. 14, 2014

Glenn Linderman writes: > On 8/10/2014 1:24 AM, Stephen J. Turnbull wrote: > > Actually ... if I were a fan of the "".join() idiom, I'd seriously > > propose 0.sum(numeric_iterable) as the RightThang{tm]. Then we could > > deprecate "".join(string_iterable) in favor of "".sum(string_iterable) > > (with the same efficient semantics). > Actually, there is no need to wait for 0.sum() to propose "".sum... but > it is only a spelling change, so no real benefit. IMO it's worse than merely a spelling change, because (1) "join" is a more evocative term for concatenating strings than "sum" and (2) I don't know of any other sums that allow "glue". I'm overall -1 on trying to change the current situation (except for adding a join() builtin or str.join class method). We could probably fix everything in a static-typed language (because that would allow picking an initial object of the appropriate type), but without that we need to pick a default of some particular type, and 0 makes the most sense. I can understand the desire of people who want to use the same syntax for summing an iterable of numbers and for concatenating an iterable of strings, but to me they're really not even formally the same in practical use. I'm very sympathetic to Steven's explanation that "we wouldn't be having this discussion if we used a different operator for string concatenation". Although that's not the whole story: in practice even numerical sums get split into multiple functions because floating point addition isn't associative, and so needs careful treatment to preserve accuracy. At that point I'm strongly +1 on abandoning attempts to "rationalize" summation. I'm not sure how I'd feel about raising an exception if you try to sum any iterable containing misbehaved types like float. But not only would that be a Python 4 effort due to backward incompatibility, but it sorta contradicts the main argument of proponents ("any type implementing __add__ should be sum()-able").

12 17

Commit-ready patches in need of review
by Nikolaus Rath Aug. 12, 2014

Aug. 12, 2014

Hello, The following commit-ready patches have been waiting for review since May and earlier.It'd be great if someone could find the time to take a look. I'll be happy to incorporate feedback as necessary: * http://bugs.python.org/issue1738 (filecmp.dircmp does exact match only) * http://bugs.python.org/issue15955 (gzip, bz2, lzma: add option to limit output size) * http://bugs.python.org/issue20177 (Derby #8: Convert 28 sites to Argument Clinic across 2 files) I only wrote the patch for one file because I'd like to have feedback before tackling the second. However, the patches are independent so unless there are other problems this is ready for commit. Best, Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«

1 0

pathlib handling of trailing slash (Issue #21039)
by Isaac Schwabacher Aug. 11, 2014

Aug. 11, 2014

I see this as a parallel to the question of `pathlib.PurePath.resolve()`, about which `pathlib` is (rightly!) very opinionated. Just as `foo/../bar` shouldn't resolve to `bar`, `foo/` shouldn't be truncated to `foo`. And if `PurePath` doesn't do this, `Path` shouldn't either, because the difference between a `Path` and a `PurePath` is the availability of filesystem operations, not the identities of the objects involved. On another level, I think that this is a simple decision: `PosixPath` claims right there in the name to implement POSIX behavior, and POSIX specifies that `foo` and `foo/` refer (in some cases) to different directory entries. Therefore, `foo` and `foo/` can't be the same path. Moreover, `PosixPath` implements several methods that have the same name as syscalls that POSIX specifies to depend on whether their path arguments end in trailing slashes. (Even `stat` [http://pubs.opengroup.org/onlinepubs/9699919799/functions/stat.html], which explicitly follows symbolic links regardless of the presence of a trailing slash, fails with ENOTDIR if given "path/to/existing/file/".) It feels pathological for `pathlib.PosixPath` to be so almost-compliant. -ijs

1 0

sum(...) limitation
by Andrea Griffini Aug. 11, 2014

Aug. 11, 2014

help(sum) tells clearly that it should be used to sum numbers and not strings, and with strings actually fails. However sum([[1,2,3],[4],[],[5,6]], []) concatenates the lists. Is this to be considered a bug? Andrea

22 40

python2.7 infinite recursion when loading pickled object
by Schmitt Uwe (ID SIS) Aug. 11, 2014

Aug. 11, 2014

Dear all, I discovered a problem using cPickle.loads from CPython 2.7.6. The last line in the following code raises an infinite recursion class T(object): def __init__(self): self.item = list() def __getattr__(self, name): return getattr(self.item, name) import cPickle t = T() l = cPickle.dumps(t) cPickle.loads(l) loads triggers T.__getattr__ using "getattr(inst, "__setstate__", None)" for looking up a "__setstate__" method, which is not implemented for T. As the item attribute is missing at this time, the ininfite recursion starts. The infinite recursion disappears if I attach a default implementation for __setstate__ to T: def __setstate__(self, dd): self.__dict__ = dd This could be fixed by using „hasattr“ in pickle before trying to call „getattr“. Is this a bug or did I miss something ? Kind Regards, Uwe

6 6

class Foo(object) vs class Foo: should be clearly explained in python 2 and 3 doc
by John Yeuk Hon Wong Aug. 10, 2014

Aug. 10, 2014

Hi. Referring to my discussion on [1] and then on #python this afternoon. A little background would help people to understand where this was coming from. 1. I write Python 2 code and have done zero Python-3 specific code. 2. I have always been using class Foo(object) so I do not know the new style is no longer required in Python 3. I feel "stupid" and "wrong" by thinking (object) is still a convention in Python 3. 3. Many Python 2 tutorials do not use object as the base class whether for historical reason, or lack of information/education, and can cause confusing to newcomers searching for answers when they consult the official documentation. While Python 3 code no longer requires object be the base class for the new-style class definition, I believe (object) is still required if one has to write a 2-3 compatible code. But this was not explained or warned anywhere in Python 2 and Python 3 code, AFAIK. (if I am wrong, please correct me) I propose the followings: * It is desirable to state boldly to users that (object) is no longer needed in Python-3 **only** code and warn users to revert to (object) style if the code needs to be 2 and 3 compatible. * In addition, Python 2 doc [2] should be fixed by introducing the new-style classes. This problem was noted a long long time ago according to [4]. * I would like to see warnings from suggested action item 1 on [2] and [3], for python 2 and 3 documentations. Possible objections(s): * We are pushing toward Python 3, some years later we don't need to maintain both Python 2 and 3 code. And many people, especially the newcomers will probably have no need to maintain Python 2 and 3 compatible codes. My answer to that is we need to be careful with marketing. First, it is a little embarrassing to assume and to find out the assumption is not entirely accurate. Secondly, Python 2 will not go away any time soon and most tutorials available on the Internet today are still written for Python 2. Furthermore, this CAN be a "gotcha" for new developers knowing only Python 3 writing Python 2 & 3 compatible code. * Books can do a better job I haven't actually reviewed/read any Python 3 books knowing most of my code should work without bothering Python 3-2 incompatibility yet. So I don't have an accurate answer, but a very very quick glance over a popular Python 3 book (I am not sure if naming it out is ethical or not so I am going to grey it out here) the book just writes class Foo: and doesn't note the different between 2 and 3 with classes. It is not wrong since the book is about programming in Python 3, NOT writing 2 and 3, but this is where the communication breaks. Docs and books don't give all the answers needed. P.S. Sorry if I should've have asked on #python-dev first or made a ticket but I've decided to send to mailing list before making a bug ticket. First time! Thanks. Best, Yeuk Hon [1]: https://news.ycombinator.com/item?id=8154471 [2]: https://docs.python.org/2/tutorial/classes.html https://docs.python.org/3/tutorial/classes.html [3]: https://docs.python.org/3/tutorial/classes.html [4]: https://www.python.org/doc/newstyle/

7 7

Summary of Python tracker Issues
by Python tracker Aug. 8, 2014

Aug. 8, 2014

ACTIVITY SUMMARY (2014-08-01 - 2014-08-08) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 4602 (+10) closed 29340 (+43) total 33942 (+53) Open issues with patches: 2177 Issues opened (39) ================== #21039: pathlib strips trailing slash http://bugs.python.org/issue21039 reopened by pitrou #21591: "exec(a, b, c)" not the same as "exec a in b, c" in nested fun http://bugs.python.org/issue21591 reopened by Arfrever #22121: IDLE should start with HOME as the initial working directory http://bugs.python.org/issue22121 opened by mark #22123: Provide a direct function for types.SimpleNamespace() http://bugs.python.org/issue22123 opened by mark #22125: Cure signedness warnings introduced by #22003 http://bugs.python.org/issue22125 opened by dw #22126: mc68881 fpcr inline asm breaks clang -flto build http://bugs.python.org/issue22126 opened by ivank #22128: patch: steer people away from codecs.open http://bugs.python.org/issue22128 opened by Frank.van.Dijk #22131: uuid.bytes optimization http://bugs.python.org/issue22131 opened by kevinlondon #22133: IDLE: Set correct WM_CLASS on X11 http://bugs.python.org/issue22133 opened by sahutd #22135: allow to break into pdb with Ctrl-C for all the commands that http://bugs.python.org/issue22135 opened by xdegaye #22137: Test imaplib API on all methods specified in RFC 3501 http://bugs.python.org/issue22137 opened by zvyn #22138: patch.object doesn't restore function defaults http://bugs.python.org/issue22138 opened by chepner #22139: python windows 2.7.8 64-bit wrong binary version http://bugs.python.org/issue22139 opened by Andreas.Richter #22140: "python-config --includes" returns a wrong path (double prefix http://bugs.python.org/issue22140 opened by Michael.Dussere #22141: rlcompleter.Completer matches too much http://bugs.python.org/issue22141 opened by donlorenzo #22143: rlcompleter.Completer has duplicate matches http://bugs.python.org/issue22143 opened by donlorenzo #22144: ellipsis needs better display in lexer documentation http://bugs.python.org/issue22144 opened by François-René.Rideau #22145: <> in parser spec but not lexer spec http://bugs.python.org/issue22145 opened by François-René.Rideau #22147: PosixPath() constructor should not accept strings with embedde http://bugs.python.org/issue22147 opened by ischwabacher #22148: frozen.c should #include <importlib.h> instead of "importlib.h http://bugs.python.org/issue22148 opened by jbeck #22149: the frame of a suspended generator should not have a local tra http://bugs.python.org/issue22149 opened by xdegaye #22150: deprecated-removed directive is broken in Sphinx 1.2.2 http://bugs.python.org/issue22150 opened by berker.peksag #22153: There is no standard TestCase.runTest implementation http://bugs.python.org/issue22153 opened by vadmium #22154: ZipFile.open context manager support http://bugs.python.org/issue22154 opened by Ralph.Broenink #22155: Out of date code example for tkinter's createfilehandler http://bugs.python.org/issue22155 opened by vadmium #22156: Fix compiler warnings http://bugs.python.org/issue22156 opened by haypo #22157: FAIL: test_with_pip (test.test_venv.EnsurePipTest) http://bugs.python.org/issue22157 opened by snehal #22158: RFC 6531 (SMTPUTF8) support in smtpd.PureProxy http://bugs.python.org/issue22158 opened by zvyn #22159: smtpd.PureProxy and smtpd.DebuggingServer do not work with dec http://bugs.python.org/issue22159 opened by zvyn #22160: Windows installers need to be updated following OpenSSL securi http://bugs.python.org/issue22160 opened by alex #22161: Remove unsupported code from ctypes http://bugs.python.org/issue22161 opened by serhiy.storchaka #22163: max_wbits set incorrectly to -zlib.MAX_WBITS in tarfile, shoul http://bugs.python.org/issue22163 opened by edulix #22164: cell object cleared too early? http://bugs.python.org/issue22164 opened by pitrou #22165: Empty response from http.server when directory listing contain http://bugs.python.org/issue22165 opened by jleedev #22166: test_codecs "leaking" references http://bugs.python.org/issue22166 opened by zach.ware #22167: iglob() has misleading documentation (does indeed store names http://bugs.python.org/issue22167 opened by roysmith #22168: Turtle Graphics RawTurtle problem http://bugs.python.org/issue22168 opened by Kent.D..Lee #22171: stack smash when using ctypes/libffi to access union http://bugs.python.org/issue22171 opened by wes.kerfoot #22173: Update lib2to3.tests and test_lib2to3 to use test discovery http://bugs.python.org/issue22173 opened by zach.ware Most recent 15 issues with no replies (15) ========================================== #22173: Update lib2to3.tests and test_lib2to3 to use test discovery http://bugs.python.org/issue22173 #22171: stack smash when using ctypes/libffi to access union http://bugs.python.org/issue22171 #22166: test_codecs "leaking" references http://bugs.python.org/issue22166 #22164: cell object cleared too early? http://bugs.python.org/issue22164 #22163: max_wbits set incorrectly to -zlib.MAX_WBITS in tarfile, shoul http://bugs.python.org/issue22163 #22161: Remove unsupported code from ctypes http://bugs.python.org/issue22161 #22159: smtpd.PureProxy and smtpd.DebuggingServer do not work with dec http://bugs.python.org/issue22159 #22158: RFC 6531 (SMTPUTF8) support in smtpd.PureProxy http://bugs.python.org/issue22158 #22155: Out of date code example for tkinter's createfilehandler http://bugs.python.org/issue22155 #22153: There is no standard TestCase.runTest implementation http://bugs.python.org/issue22153 #22149: the frame of a suspended generator should not have a local tra http://bugs.python.org/issue22149 #22143: rlcompleter.Completer has duplicate matches http://bugs.python.org/issue22143 #22140: "python-config --includes" returns a wrong path (double prefix http://bugs.python.org/issue22140 #22135: allow to break into pdb with Ctrl-C for all the commands that http://bugs.python.org/issue22135 #22115: Add new methods to trace Tkinter variables http://bugs.python.org/issue22115 Most recent 15 issues waiting for review (15) ============================================= #22173: Update lib2to3.tests and test_lib2to3 to use test discovery http://bugs.python.org/issue22173 #22165: Empty response from http.server when directory listing contain http://bugs.python.org/issue22165 #22163: max_wbits set incorrectly to -zlib.MAX_WBITS in tarfile, shoul http://bugs.python.org/issue22163 #22161: Remove unsupported code from ctypes http://bugs.python.org/issue22161 #22159: smtpd.PureProxy and smtpd.DebuggingServer do not work with dec http://bugs.python.org/issue22159 #22158: RFC 6531 (SMTPUTF8) support in smtpd.PureProxy http://bugs.python.org/issue22158 #22156: Fix compiler warnings http://bugs.python.org/issue22156 #22150: deprecated-removed directive is broken in Sphinx 1.2.2 http://bugs.python.org/issue22150 #22149: the frame of a suspended generator should not have a local tra http://bugs.python.org/issue22149 #22148: frozen.c should #include <importlib.h> instead of "importlib.h http://bugs.python.org/issue22148 #22143: rlcompleter.Completer has duplicate matches http://bugs.python.org/issue22143 #22141: rlcompleter.Completer matches too much http://bugs.python.org/issue22141 #22138: patch.object doesn't restore function defaults http://bugs.python.org/issue22138 #22137: Test imaplib API on all methods specified in RFC 3501 http://bugs.python.org/issue22137 #22133: IDLE: Set correct WM_CLASS on X11 http://bugs.python.org/issue22133 Top 10 most discussed issues (10) ================================= #19838: test.test_pathlib.PosixPathTest.test_touch_common fails on Fre http://bugs.python.org/issue19838 23 msgs #21448: Email Parser use 100% CPU http://bugs.python.org/issue21448 14 msgs #22123: Provide a direct function for types.SimpleNamespace() http://bugs.python.org/issue22123 11 msgs #21965: Add support for Memory BIO to _ssl http://bugs.python.org/issue21965 10 msgs #14910: argparse: disable abbreviation http://bugs.python.org/issue14910 9 msgs #21308: PEP 466: backport ssl changes http://bugs.python.org/issue21308 9 msgs #22046: ZipFile.read() should mention that it might throw NotImplement http://bugs.python.org/issue22046 9 msgs #21091: EmailMessage.is_attachment should be a method http://bugs.python.org/issue21091 8 msgs #22118: urljoin fails with messy relative URLs http://bugs.python.org/issue22118 8 msgs #22160: Windows installers need to be updated following OpenSSL securi http://bugs.python.org/issue22160 8 msgs Issues closed (43) ================== #5411: Add xz support to shutil http://bugs.python.org/issue5411 closed by serhiy.storchaka #11763: assertEqual memory issues with large text inputs http://bugs.python.org/issue11763 closed by ezio.melotti #13540: Document the Action API in argparse http://bugs.python.org/issue13540 closed by jason.coombs #15114: Deprecate strict mode of HTMLParser http://bugs.python.org/issue15114 closed by ezio.melotti #15826: Increased test coverage of test_glob.py http://bugs.python.org/issue15826 closed by ezio.melotti #15974: Optional compact and colored output for regrest http://bugs.python.org/issue15974 closed by pitrou #17665: convert test_wsgiref to idiomatic unittest code http://bugs.python.org/issue17665 closed by ezio.melotti #18034: Last two entries in the programming FAQ are out of date (impor http://bugs.python.org/issue18034 closed by ezio.melotti #18142: Tests fail on Mageia Linux Cauldron x86-64 with some configure http://bugs.python.org/issue18142 closed by ned.deily #18588: timeit examples should be consistent http://bugs.python.org/issue18588 closed by ezio.melotti #19055: Regular expressions: * does not match as many repetitions as p http://bugs.python.org/issue19055 closed by ezio.melotti #20056: Got deprecation warning when running test_shutil.py on Windows http://bugs.python.org/issue20056 closed by serhiy.storchaka #20170: Derby #1: Convert 137 sites to Argument Clinic in Modules/posi http://bugs.python.org/issue20170 closed by larry #20402: List comprehensions should be noted in for loop documentation http://bugs.python.org/issue20402 closed by rhettinger #20977: pyflakes: undefined "ctype" in 2 except blocks in the email mo http://bugs.python.org/issue20977 closed by ezio.melotti #21047: html.parser.HTMLParser: convert_charrefs should become True by http://bugs.python.org/issue21047 closed by berker.peksag #21539: pathlib's Path.mkdir() should allow for "mkdir -p" functionali http://bugs.python.org/issue21539 closed by barry #21972: Bugs in the lexer and parser documentation http://bugs.python.org/issue21972 closed by loewis #21975: Using pickled/unpickled sqlite3.Row results in segfault rather http://bugs.python.org/issue21975 closed by serhiy.storchaka #22077: Improve the error message for various sequences http://bugs.python.org/issue22077 closed by terry.reedy #22092: Executing some tests inside Lib/unittest/test individually thr http://bugs.python.org/issue22092 closed by ezio.melotti #22097: Linked list API for ordereddict http://bugs.python.org/issue22097 closed by rhettinger #22104: test_asyncio unstable in refleak mode http://bugs.python.org/issue22104 closed by python-dev #22105: Idle: Hang during File "Save As" http://bugs.python.org/issue22105 closed by terry.reedy #22110: enable extra compilation warnings http://bugs.python.org/issue22110 closed by neologix #22114: You cannot call communicate() safely after receiving an except http://bugs.python.org/issue22114 closed by amrith #22116: Weak reference support for C function objects http://bugs.python.org/issue22116 closed by pitrou #22119: Some input chars (i.e. '++') break re.match http://bugs.python.org/issue22119 closed by ezio.melotti #22120: Return converter code generated by Argument Clinic has a warni http://bugs.python.org/issue22120 closed by larry #22122: turtle module examples should all begin "from turtle import *" http://bugs.python.org/issue22122 closed by mark #22124: Rotating items of list to left http://bugs.python.org/issue22124 closed by zach.ware #22127: performance regression in socket getsockaddrarg() http://bugs.python.org/issue22127 closed by loewis #22129: Please add an equivalent to QString::simplified() to Python st http://bugs.python.org/issue22129 closed by serhiy.storchaka #22130: Logging fileConfig behavior does not match documentation http://bugs.python.org/issue22130 closed by python-dev #22132: Cannot copy the same directory structure to the same destinati http://bugs.python.org/issue22132 closed by eric.araujo #22134: string formatting float rounding errors http://bugs.python.org/issue22134 closed by ned.deily #22136: Fix _tkinter compiler warnings on MSVC http://bugs.python.org/issue22136 closed by python-dev #22142: PEP 465 operators not described in lexical_analysis http://bugs.python.org/issue22142 closed by python-dev #22146: Error message for __build_class__ contains typo http://bugs.python.org/issue22146 closed by python-dev #22162: Activating a venv - Dash doesn't understand source http://bugs.python.org/issue22162 closed by vinay.sajip #22169: sys.tracebacklimit = 0 does not work as documented in 3.x http://bugs.python.org/issue22169 closed by ned.deily #22170: Typo in iterator doc http://bugs.python.org/issue22170 closed by ezio.melotti #22172: Local files shadow system modules, even from system modules http://bugs.python.org/issue22172 closed by ncoghlan

1 0

pathlib handling of trailing slash (Issue #21039)
by Isaac Schwabacher Aug. 8, 2014

Aug. 8, 2014

pathlib.Path currently strips trailing slashes from pathnames, but this behavior contradicts POSIX (http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag…), which specifies that the resolution of the pathname of a symbolic link to a directory in the context of a function that operates on symbolic links shall depend on whether the pathname has a trailing slash: > 4.12 Pathname Resolution > ======================== > > [...] > > A pathname that contains at least one non- <slash> character and that ends with one or more trailing <slash> characters shall not be resolved successfully unless the last pathname component before the trailing <slash> characters names an existing directory or a directory entry that is to be created for a directory immediately after the pathname is resolved. Interfaces using pathname resolution may specify additional constraints[1] when a pathname that does not name an existing directory contains at least one non- <slash> character and contains one or more trailing <slash> characters. > > If a symbolic link is encountered during pathname resolution, the behavior shall depend on whether the pathname component is at the end of the pathname and on the function being performed. If all of the following are true, then pathname resolution is complete: > > 1. This is the last pathname component of the pathname. > 2. The pathname has no trailing <slash>. > 3. The function is required to act on the symbolic link itself, or certain arguments direct that the function act on the symbolic link itself. > > In all other cases, the system shall prefix the remaining pathname, if any, with the contents of the symbolic link. [...] The following sentence appeared in an earlier version of POSIX (http://pubs.opengroup.org/onlinepubs/009604499/basedefs/xbd_chap04.html#tag…) but has since been removed: > A pathname that contains at least one non-slash character and that ends with one or more trailing slashes shall be resolved as if a single dot character ( '.' ) were appended to the pathname. Is this important enough to preserve trailing slashes? - Isaac Schwabacher

6 8

Re: [Python-Dev] [Python-checkins] Daily reference leaks (09f56fdcacf1): sum=21004
by Brett Cannon Aug. 7, 2014

Aug. 7, 2014

test_codecs is not happy. Looking at the subject lines of commit emails from the past day I don't see any obvious cause. On Thu Aug 07 2014 at 4:35:05 AM <solipsis(a)pitrou.net> wrote: > results for 09f56fdcacf1 on branch "default" > -------------------------------------------- > > test_codecs leaked [5825, 5825, 5825] references, sum=17475 > test_codecs leaked [1172, 1174, 1174] memory blocks, sum=3520 > test_collections leaked [0, 2, 0] references, sum=2 > test_functools leaked [0, 0, 3] memory blocks, sum=3 > test_site leaked [0, 2, 0] references, sum=2 > test_site leaked [0, 2, 0] memory blocks, sum=2 > > > Command line was: ['./python', '-m', 'test.regrtest', '-uall', '-R', > '3:3:/home/antoine/cpython/refleaks/reflogdA4OO6', '-x'] > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > https://mail.python.org/mailman/listinfo/python-checkins >

2 2

Exposing the Android platform existence to Python modules
by Shiz Aug. 4, 2014

Aug. 4, 2014

Hi folks, I’m working on porting CPython to the Android platform, and while making decent progress, I’m currently stuck at a higher-level issue than adding #ifdefs for __ANDROID__ to C extension modules. The idea is, not only CPython extension modules have some assumptions that don’t seem to fit Android’s mold, some default Python-written modules do as well. However, whereas CPython extensions can trivially check if we’re building for Android by checking the __ANDROID__ compiler macro, Python modules can do no such check, and are left wondering how to figure out if the platform they are currently running on is an Android one. To my knowledge there is no reliable way to detect if one is using Android as a vehicle for their journey using any other way. Now, the main question is: what would be the best way to ‘expose’ the indication that Android is being ran on to Python-living modules? My own thought was to add sys.getlinuxuserland(), or platform.linux_userland(), in similar vein to sys.getwindowsversion() and platform.linux_distribution(), which could return information about the userland of running CPython instance, instead of knowing merely the kernel and the distribution. This way, code could trivially check if it ran on the GNU(+associates) userland, or under a BSD-ish userland, or Android… and adjust its behaviour accordingly. I would be delighted to hear comments on this proposal, or better yet, alternative solutions. :) Kind regards, Shiz P.S.: I am well aware that Android might as well never be officially supported in CPython. In that case, consider this a thought experiment of how it /would/ be handled. :)

11 28