Mailman 3 May 2016 - Python-Dev

Summary of Python tracker Issues
by Python tracker 13 May '16

13 May '16

ACTIVITY SUMMARY (2016-05-06 - 2016-05-13) 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 5501 ( -3) closed 33270 (+47) total 38771 (+44) Open issues with patches: 2383 Issues opened (28) ================== #22570: Better stdlib support for Path objects http://bugs.python.org/issue22570 reopened by gvanrossum #26857: gethostbyname_r() is broken on android http://bugs.python.org/issue26857 reopened by xdegaye #26971: python v3.5.1: sys.paths not respecting DESTDIRS and DESTSHARE http://bugs.python.org/issue26971 opened by yaro-yaro #26972: mistakes in docstrings in the import machinery http://bugs.python.org/issue26972 opened by Oren Milman #26974: Crash in Decimal.from_float http://bugs.python.org/issue26974 opened by serhiy.storchaka #26975: Decimal.from_float works incorrectly for non-binary floats http://bugs.python.org/issue26975 opened by serhiy.storchaka #26978: Implement pathlib.Path.link (Using os.link) http://bugs.python.org/issue26978 opened by cool-RR #26979: The danger of PyType_FromSpec() http://bugs.python.org/issue26979 opened by serhiy.storchaka #26980: The path argument of asyncio.BaseEventLoop.create_unix_connect http://bugs.python.org/issue26980 opened by texttheater #26981: add compatibility shim for enum34 backport http://bugs.python.org/issue26981 opened by ethan.furman #26982: Clarify forward annotations in PEP 484 http://bugs.python.org/issue26982 opened by James.Tatum #26983: float() can return not exact float instance http://bugs.python.org/issue26983 opened by serhiy.storchaka #26984: int() can return not exact int instance http://bugs.python.org/issue26984 opened by serhiy.storchaka #26985: Information about CodeType in inspect documentation is outdate http://bugs.python.org/issue26985 opened by xiang.zhang #26988: Add AutoNumberedEnum to stdlib http://bugs.python.org/issue26988 opened by John Hagen #26990: file.tell affect decoding http://bugs.python.org/issue26990 opened by mfmain #26991: Possible reference leak in MAKE_FUNCTION http://bugs.python.org/issue26991 opened by xiang.zhang #26992: 64-bit Python 2.7.11 hangs in 64-bit Windows 10 - CMD and Git http://bugs.python.org/issue26992 opened by sam.taylor.bs #26993: Copy idlelib *.py files with new names http://bugs.python.org/issue26993 opened by terry.reedy #26995: Add tests for parsing float and object arguments http://bugs.python.org/issue26995 opened by serhiy.storchaka #26997: Docs for pdb should note that __future__ magic doesn't work http://bugs.python.org/issue26997 opened by Martin Jones #27002: Support different modes in posixpath.realpath() http://bugs.python.org/issue27002 opened by serhiy.storchaka #27004: Handle script shbang options http://bugs.python.org/issue27004 opened by opoplawski #27006: C implementation of Decimal.from_float() bypasses __new__ and http://bugs.python.org/issue27006 opened by serhiy.storchaka #27007: Alternate constructors bytes.fromhex() and bytearray.fromhex() http://bugs.python.org/issue27007 opened by serhiy.storchaka #27010: email library could "recover" from bad mime boundary like (som http://bugs.python.org/issue27010 opened by Fedele Mantuano #27012: Rename the posix module to _os http://bugs.python.org/issue27012 opened by brett.cannon #27014: maximum recursion depth when using typing options http://bugs.python.org/issue27014 opened by Roy Shmueli Most recent 15 issues with no replies (15) ========================================== #27014: maximum recursion depth when using typing options http://bugs.python.org/issue27014 #27006: C implementation of Decimal.from_float() bypasses __new__ and http://bugs.python.org/issue27006 #27002: Support different modes in posixpath.realpath() http://bugs.python.org/issue27002 #26997: Docs for pdb should note that __future__ magic doesn't work http://bugs.python.org/issue26997 #26995: Add tests for parsing float and object arguments http://bugs.python.org/issue26995 #26990: file.tell affect decoding http://bugs.python.org/issue26990 #26982: Clarify forward annotations in PEP 484 http://bugs.python.org/issue26982 #26980: The path argument of asyncio.BaseEventLoop.create_unix_connect http://bugs.python.org/issue26980 #26979: The danger of PyType_FromSpec() http://bugs.python.org/issue26979 #26978: Implement pathlib.Path.link (Using os.link) http://bugs.python.org/issue26978 #26964: Incorrect documentation for `-u`-flag http://bugs.python.org/issue26964 #26955: Implement equivalent to `pip.locations.distutils_scheme` in di http://bugs.python.org/issue26955 #26954: Add Guido's rejection notice to the "with" FAQ http://bugs.python.org/issue26954 #26942: android: test_ctypes crashes on armv7 http://bugs.python.org/issue26942 #26937: android: test_tarfile fails http://bugs.python.org/issue26937 Most recent 15 issues waiting for review (15) ============================================= #27007: Alternate constructors bytes.fromhex() and bytearray.fromhex() http://bugs.python.org/issue27007 #27002: Support different modes in posixpath.realpath() http://bugs.python.org/issue27002 #26995: Add tests for parsing float and object arguments http://bugs.python.org/issue26995 #26991: Possible reference leak in MAKE_FUNCTION http://bugs.python.org/issue26991 #26985: Information about CodeType in inspect documentation is outdate http://bugs.python.org/issue26985 #26983: float() can return not exact float instance http://bugs.python.org/issue26983 #26982: Clarify forward annotations in PEP 484 http://bugs.python.org/issue26982 #26974: Crash in Decimal.from_float http://bugs.python.org/issue26974 #26972: mistakes in docstrings in the import machinery http://bugs.python.org/issue26972 #26970: Replace OpenSSL's CPRNG with system entropy source http://bugs.python.org/issue26970 #26964: Incorrect documentation for `-u`-flag http://bugs.python.org/issue26964 #26959: pickle: respect dispatch for functions again http://bugs.python.org/issue26959 #26948: Simplify PyImport_ImportModuleLevelObject: avoid temporary tup http://bugs.python.org/issue26948 #26939: android: test_functools hangs on armv7 http://bugs.python.org/issue26939 #26935: android: test_os fails http://bugs.python.org/issue26935 Top 10 most discussed issues (10) ================================= #26969: ascynio should provide a policy to address pass-loop-everywher http://bugs.python.org/issue26969 36 msgs #26439: ctypes.util.find_library fails when ldconfig/glibc not availab http://bugs.python.org/issue26439 12 msgs #26993: Copy idlelib *.py files with new names http://bugs.python.org/issue26993 9 msgs #26906: format(object.__reduce__) fails intermittently http://bugs.python.org/issue26906 8 msgs #6422: timeit called from within Python should allow autoranging http://bugs.python.org/issue6422 7 msgs #18531: Undocumented different between METH_KEYWORDS and **kws http://bugs.python.org/issue18531 7 msgs #26632: __all__ decorator http://bugs.python.org/issue26632 7 msgs #26983: float() can return not exact float instance http://bugs.python.org/issue26983 7 msgs #26039: More flexibility in zipfile write interface http://bugs.python.org/issue26039 6 msgs #26369: unicode.decode and str.encode are unnecessarily confusing for http://bugs.python.org/issue26369 6 msgs Issues closed (45) ================== #5062: Rlcompleter.Completer does not use __dir__ magic method http://bugs.python.org/issue5062 closed by martin.panter #11643: Use |version| instead of X.Y in the doc http://bugs.python.org/issue11643 closed by serhiy.storchaka #15721: PEP 3121, 384 Refactoring applied to tkinter module http://bugs.python.org/issue15721 closed by serhiy.storchaka #17765: weakref.ref ignores a 'callback' keyword argument http://bugs.python.org/issue17765 closed by serhiy.storchaka #18864: Implementation for PEP 451 (importlib.machinery.ModuleSpec) http://bugs.python.org/issue18864 closed by eric.snow #19444: mmap.mmap() allocates a file descriptor that isn't CLOEXEC http://bugs.python.org/issue19444 closed by martin.panter #21012: Figure out how to best leverage pip in devinabox http://bugs.python.org/issue21012 closed by brett.cannon #22143: rlcompleter.Completer has duplicate matches http://bugs.python.org/issue22143 closed by martin.panter #22274: subprocess.Popen(stderr=STDOUT) fails to redirect subprocess s http://bugs.python.org/issue22274 closed by martin.panter #23213: subprocess communicate() hangs when stderr isn't closed http://bugs.python.org/issue23213 closed by martin.panter #23640: int.from_bytes() is broken for subclasses http://bugs.python.org/issue23640 closed by serhiy.storchaka #23815: Segmentation fault when create _tkinter objects http://bugs.python.org/issue23815 closed by serhiy.storchaka #23921: Standardize documentation whitespace, formatting http://bugs.python.org/issue23921 closed by serhiy.storchaka #24550: maxint on 64 bit platforms breaks os.read http://bugs.python.org/issue24550 closed by serhiy.storchaka #25745: Reference leaks in test_curses http://bugs.python.org/issue25745 closed by serhiy.storchaka #26352: getpass incorrectly displays password prompt on stderr on fall http://bugs.python.org/issue26352 closed by serhiy.storchaka #26512: Vocabulary: Using "integral" in library/stdtypes.html http://bugs.python.org/issue26512 closed by martin.panter #26708: Constify C string pointers in the posix module http://bugs.python.org/issue26708 closed by serhiy.storchaka #26736: Use HTTPS protocol in links http://bugs.python.org/issue26736 closed by serhiy.storchaka #26881: modulefinder should reuse the dis module http://bugs.python.org/issue26881 closed by serhiy.storchaka #26889: Improve Doc/library/xmlrpc.client.rst http://bugs.python.org/issue26889 closed by serhiy.storchaka #26892: debuglevel not honored in urllib http://bugs.python.org/issue26892 closed by orsenthil #26911: lib2to3/tests/pytree_idempotency.py has broken imports http://bugs.python.org/issue26911 closed by terry.reedy #26912: Broken imports in test/test_email/torture_test.py, test_asian_ http://bugs.python.org/issue26912 closed by terry.reedy #26924: android: test_concurrent_futures fails http://bugs.python.org/issue26924 closed by berker.peksag #26925: android: test_multiprocessing_main_handling fails http://bugs.python.org/issue26925 closed by xdegaye #26960: urllib hangs when closing connection http://bugs.python.org/issue26960 closed by python-dev #26973: Dict View binops permit non-set types http://bugs.python.org/issue26973 closed by r.david.murray #26976: pathlib equivalent for os.path.realpath() http://bugs.python.org/issue26976 closed by serhiy.storchaka #26977: Unnecessary line in statistics.pvariance http://bugs.python.org/issue26977 closed by steven.daprano #26986: Enhance PyFunction_New documentation http://bugs.python.org/issue26986 closed by python-dev #26987: Comment/implementation disagreement in Thread._bootstrap_inner http://bugs.python.org/issue26987 closed by python-dev #26989: error in installation of ez_setup.py http://bugs.python.org/issue26989 closed by benjamin.peterson #26994: unexpected behavior for booleans in argparse http://bugs.python.org/issue26994 closed by r.david.murray #26996: Add secrets module as per PEP 506. http://bugs.python.org/issue26996 closed by steven.daprano #26998: Unable to import "site" in an embedded application http://bugs.python.org/issue26998 closed by steve.dower #26999: Add child separator keyword to logging.basicConfig and use it http://bugs.python.org/issue26999 closed by vinay.sajip #27000: improve document of filter http://bugs.python.org/issue27000 closed by r.david.murray #27001: Python Interface X-Plane 10.45 http://bugs.python.org/issue27001 closed by r.david.murray #27003: Python 3.5.1 fails at HTTPSTest with SSL CERT error http://bugs.python.org/issue27003 closed by martin.panter #27005: Faster float.fromhex() http://bugs.python.org/issue27005 closed by serhiy.storchaka #27008: error message of ord is not intuitive http://bugs.python.org/issue27008 closed by r.david.murray #27009: multiprocessing Connection data length limited to max(int32) http://bugs.python.org/issue27009 closed by serhiy.storchaka #27011: Identation error http://bugs.python.org/issue27011 closed by python-dev #27013: IDLE completion for dict keys http://bugs.python.org/issue27013 closed by terry.reedy

1 0

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals (revision 3)
by Guido van Rossum 12 May '16

12 May '16

OK, then PEP 515 is now officially accepted! Congratulations. Start the implementation work! --Guido (mobile) On May 11, 2016 10:33 PM, "Georg Brandl" <g.brandl(a)gmx.net> wrote: I'm happy with the latest version. Georg On 05/11/2016 06:46 PM, Guido van Rossum wrote: > If the authors are happy I'll accept it right away. > > (I vaguely recall there's another PEP that's ready for pronouncement -- but > which one?) > > On Wed, May 11, 2016 at 9:34 AM, Brett Cannon <brett(a)python.org > <mailto:brett@python.org>> wrote: > > Is there anything holding up PEP 515 at this point in terms of acceptance or > implementation? > > On Sat, 19 Mar 2016 at 11:56 Guido van Rossum <guido(a)python.org > <mailto:guido@python.org>> wrote: > > All that sounds fine! > > On Sat, Mar 19, 2016 at 11:28 AM, Stefan Krah <stefan(a)bytereef.org > <mailto:stefan@bytereef.org>> wrote: > > Guido van Rossum <guido <at> python.org <http://python.org>> writes: > >> So should the preprocessing step just be s.replace('_', ''), or should > >> it reject underscores that don't follow the rules from the PEP > >> (perhaps augmented so they follow the spirit of the PEP and the letter > >> of the IBM spec)? > >> > >> Honestly I think it's also fine if specifying this exactly is left out > >> of the PEP, and handled by whoever adds this to Decimal. Having a PEP > >> to work from for the language spec and core builtins (int(), float() > >> complex()) is more important. > > > > I'd keep it simple for Decimal: Remove left and right whitespace (we're > > already doing this), then remove underscores from the remaining string > > (which must not contain any further whitespace), then use the IBM grammar. > > > > > > We could add a clause to the PEP that only those strings that follow > > the spirit of the PEP are guaranteed to be accepted in the future. > > > > > > One reason for keeping it simple is that I would not like to slow down > > string conversion, but thinking about two grammars is also a problem -- > > part of the string conversion in libmpdec is modeled in ACL2, which > > would be invalidated or at least complicated with two grammars. > > > > > > > > Stefan Krah > > > > _______________________________________________ > > Python-Dev mailing list > > Python-Dev(a)python.org <mailto:Python-Dev@python.org> > > https://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > > > > -- > --Guido van Rossum (python.org/~guido <http://python.org/~guido>) > _______________________________________________ > Python-Dev mailing list > Python-Dev(a)python.org <mailto:Python-Dev@python.org> > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org > > > > > -- > --Guido van Rossum (python.org/~guido <http://python.org/~guido>) > > _______________________________________________ Python-Dev mailing list Python-Dev(a)python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org

2 2

Slow downloads from python.org
by Dima Tisnek 12 May '16

12 May '16

Sorry, this is probably wrong place to ask, but is it only me? I can't get more than 40KB/s downloading from python.org

2 2

PEP 515: Underscores in Numeric Literals (revision 3)
by Georg Brandl 12 May '16

12 May '16

Hi all, after talking to Guido and Serhiy we present the next revision of this PEP. It is a compromise that we are all happy with, and a relatively restricted rule that makes additions to PEP 8 basically unnecessary. I think the discussion has shown that supporting underscores in the from-string constructors is valuable, therefore this is now added to the specification section. The remaining open question is about the reverse direction: do we want a string formatting modifier that adds underscores as thousands separators? cheers, Georg ----------------------------------------------------------------- PEP: 515 Title: Underscores in Numeric Literals Version: $Revision$ Last-Modified: $Date$ Author: Georg Brandl, Serhiy Storchaka Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 10-Feb-2016 Python-Version: 3.6 Post-History: 10-Feb-2016, 11-Feb-2016 Abstract and Rationale ====================== This PEP proposes to extend Python's syntax and number-from-string constructors so that underscores can be used as visual separators for digit grouping purposes in integral, floating-point and complex number literals. This is a common feature of other modern languages, and can aid readability of long literals, or literals whose value should clearly separate into parts, such as bytes or words in hexadecimal notation. Examples:: # grouping decimal numbers by thousands amount = 10_000_000.0 # grouping hexadecimal addresses by words addr = 0xDEAD_BEEF # grouping bits into nibbles in a binary literal flags = 0b_0011_1111_0100_1110 # same, for string conversions flags = int('0b_1111_0000', 2) Specification ============= The current proposal is to allow one underscore between digits, and after base specifiers in numeric literals. The underscores have no semantic meaning, and literals are parsed as if the underscores were absent. Literal Grammar --------------- The production list for integer literals would therefore look like this:: integer: decinteger | bininteger | octinteger | hexinteger decinteger: nonzerodigit (["_"] digit)* | "0" (["_"] "0")* bininteger: "0" ("b" | "B") (["_"] bindigit)+ octinteger: "0" ("o" | "O") (["_"] octdigit)+ hexinteger: "0" ("x" | "X") (["_"] hexdigit)+ nonzerodigit: "1"..."9" digit: "0"..."9" bindigit: "0" | "1" octdigit: "0"..."7" hexdigit: digit | "a"..."f" | "A"..."F" For floating-point and complex literals:: floatnumber: pointfloat | exponentfloat pointfloat: [digitpart] fraction | digitpart "." exponentfloat: (digitpart | pointfloat) exponent digitpart: digit (["_"] digit)* fraction: "." digitpart exponent: ("e" | "E") ["+" | "-"] digitpart imagnumber: (floatnumber | digitpart) ("j" | "J") Constructors ------------ Following the same rules for placement, underscores will be allowed in the following constructors: - ``int()`` (with any base) - ``float()`` - ``complex()`` - ``Decimal()`` Prior Art ========= Those languages that do allow underscore grouping implement a large variety of rules for allowed placement of underscores. In cases where the language spec contradicts the actual behavior, the actual behavior is listed. ("single" or "multiple" refer to allowing runs of consecutive underscores.) * Ada: single, only between digits [8]_ * C# (open proposal for 7.0): multiple, only between digits [6]_ * C++14: single, between digits (different separator chosen) [1]_ * D: multiple, anywhere, including trailing [2]_ * Java: multiple, only between digits [7]_ * Julia: single, only between digits (but not in float exponent parts) [9]_ * Perl 5: multiple, basically anywhere, although docs say it's restricted to one underscore between digits [3]_ * Ruby: single, only between digits (although docs say "anywhere") [10]_ * Rust: multiple, anywhere, except for between exponent "e" and digits [4]_ * Swift: multiple, between digits and trailing (although textual description says only "between digits") [5]_ Alternative Syntax ================== Underscore Placement Rules -------------------------- Instead of the relatively strict rule specified above, the use of underscores could be limited. As we seen from other languages, common rules include: * Only one consecutive underscore allowed, and only between digits. * Multiple consecutive underscores allowed, but only between digits. * Multiple consecutive underscores allowed, in most positions except for the start of the literal, or special positions like after a decimal point. The syntax in this PEP has ultimately been selected because it covers the common use cases, and does not allow for syntax that would have to be discouraged in style guides anyway. A less common rule would be to allow underscores only every N digits (where N could be 3 for decimal literals, or 4 for hexadecimal ones). This is unnecessarily restrictive, especially considering the separator placement is different in different cultures. Different Separators -------------------- A proposed alternate syntax was to use whitespace for grouping. Although strings are a precedent for combining adjoining literals, the behavior can lead to unexpected effects which are not possible with underscores. Also, no other language is known to use this rule, except for languages that generally disregard any whitespace. C++14 introduces apostrophes for grouping (because underscores introduce ambiguity with user-defined literals), which is not considered because of the use in Python's string literals. [1]_ Open Proposals ============== It has been proposed [11]_ to extend the number-to-string formatting language to allow ``_`` as a thousans separator, where currently only ``,`` is supported. This could be used to easily generate code with more readable literals. Implementation ============== A preliminary patch that implements the specification given above has been posted to the issue tracker. [12]_ References ========== .. [1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3499.html .. [2] http://dlang.org/spec/lex.html#integerliteral .. [3] http://perldoc.perl.org/perldata.html#Scalar-value-constructors .. [4] http://doc.rust-lang.org/reference.html#number-literals .. [5] https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swif… .. [6] https://github.com/dotnet/roslyn/issues/216 .. [7] https://docs.oracle.com/javase/7/docs/technotes/guides/language/underscores… .. [8] http://archive.adaic.com/standards/83lrm/html/lrm-02-04.html#2.4 .. [9] http://docs.julialang.org/en/release-0.4/manual/integers-and-floating-point… .. [10] http://ruby-doc.org/core-2.3.0/doc/syntax/literals_rdoc.html#label-Numbers .. [11] https://mail.python.org/pipermail/python-dev/2016-February/143283.html .. [12] http://bugs.python.org/issue26331 Copyright ========= This document has been placed in the public domain.

9 21

ctypes compatibility with 2.3
by Martin Panter 11 May '16

11 May '16

I am working on <https://bugs.python.org/issue22636>, to fix shell injection problems with ctypes.util.find_library(). The proposal for Python 3 is to change os.popen(shell-script) calls to use subprocess.Popen(). However the Python 2.7 version of the module has a comment which says “This file should be kept compatible with Python 2.3, see PEP 291.” Looking at <https://www.python.org/dev/peps/pep-0291/>, it is not clear why we have to maintain this compatibility. My best guess is that there may be an external ctypes package that people want(ed) to keep compatible with 2.3, and also keep synchronized with 2.7. I would like to lift this restriction to at least 2.4, because that is when the “subprocess” module was added. I notice that there is already code that relies on the list.sort(key=...) feature, which was added in 2.4. Ideally I would prefer to drop the restriction and only require 2.7 compatibility. Would either of these options be a problem? If it is a problem, I think it is still possible to avoid the shell by passing a sequence of program arguments to os.popen(). But I prefer not to do this, because the function is marked as deprecated, and the code would be substantially different to Python 3. -Martin

4 8

Return type of alternative constructors
by Serhiy Storchaka 10 May '16

10 May '16

Some types have alternative constructors -- class methods used to create an instance of the class. For example: int.from_bytes(), float.fromhex(), dict.fromkeys(), Decimal.from_float(). But what should return these methods for subclasses? Should they return an instance of base class or an instance of subclass? Almost all alternative constructors return an instance of subclass (exceptions are new in 3.6 bytes.fromhex() and bytearray.fromhex() that return bare bytes and bytearray). But there is a problem, because this allows to break invariants provided by the main constructor. For example, there are only two instances of the bool class: False and True. But with the from_bytes() method inherited from int you can create new boolean values! >>> Confusion = bool.from_bytes(b'\2', 'big') >>> isinstance(Confusion, bool) True >>> Confusion == True False >>> bool(Confusion) True >>> Confusion False >>> not Confusion False bool is just the most impressive example, the same problem exists with IntEnum and other enums derived from float, Decimal, datetime. [1] The simplest solution is to return an instance of base class. But this can breaks a code, and for this case we should be use static method (like str.maketrans), not class method. Should alternative constructor call __new__ and __init__ methods? Thay can change signature in derived class. Should it complain if __new__ or __init__ were overridden? [1] http://bugs.python.org/issue23640

5 9

Wrong OSX platform in sysconfig.py causing installation problems
by Joseph Nunn 09 May '16

09 May '16

Hello Everyone, my first post. I would also like to subscribe but haven't seen how yet. So I've an issue with how the 3.5.1 OSX package installs on OSX. The problem was first made apparent when trying to create a virtual environment and `pip install ZODB`, which failed as clang and the linker could not find either the include or lib directories for a dependency. By adding a -v option to the compiler options I was able to see in the compiler flags the following: -isysroot /Developer/SDKs/MacOSX10.6.sdk Which was not present in the compiler flags of other people who I was talking with. The isysroot flag changes the location of includes and libs from the system default, which would be why they can't be found. After grepping around a bit I found this file: /Library/Frameworks/Python.framework/Versions/3.5 /lib/python3.5/_sysconfigdata.py Within which are many mentions of this flag, as so: 'CONFIGURE_CFLAGS': '-arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -g', 'CONFIGURE_CFLAGS_NODIST': '-Werror=declaration-after -statement', 'CONFIGURE_CPPFLAGS': '-isysroot /Developer/SDKs/MacOSX10.6.sdk', 'CONFIGURE_LDFLAGS': '-arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -g', 'CONFIG_ARGS': "'-C' '--enable-framework' '--enable- universalsdk=/Developer/SDKs/MacOSX10.6.sdk' '--with-universal-archs=intel' '--with-computed-gotos' '--without-ensurepip' 'LDFLAGS=-g' 'CFLAGS=-g' 'CC=gcc-4.2'", among others. By running Python 3.5's sysconfig.py as a module, via `python -m sysconfig`, I see the following at the beginning of the output: Platform: "macosx-10.6-intel" Python version: "3.5" Current installation scheme: "posix_prefix" And when I simply go into python interactive mode, import sysconfig, and type sysconfig.get_platform() it returns macosx-10.6-intel. I believe somehow the platform being reported is incorrect, but looking at my environment, I do not have any kind of compiler flags or anything else like that set in my bash init files. Can someone who has a working OSX 3.5 installation check their reported platform to see what it is and if anyone has an idea as to how this information is getting into the installation and where I might change it please let me know. Sincerely, Joseph josephnunn(a)gmail.com

4 7

Minor change to Enum -- should it go into 3.5.2?
by Ethan Furman 09 May '16

09 May '16

Currently, the Enum creation process ignores __dunder__ attributes, and blocks all _sunder_ attributes. Because of this, the enum34 backport used __order__ instead of _order_ to provide a mechanism for ordering the enum members (which I never really liked). However, I've been working on my aenum [1] package, which uses several other _sunder_ attributes (for python2 compatibility) so I enabled _order_ instead and promote that spelling in the docs. Unlike the other _sunder_ attributes, _order_ has no meaningful affect in Python 3 so I'd like to change the stdlib Enum to allow it (and either ignore completely, or check it is the same as the definition order). My question is: Should I put this change in 3.5.2? - Yes means 3.5.2+ will work with _order_, 3.4, 3.5.0, and 3.5.1 will not; - No means 3.4 and all of 3.5 will not. -- ~Ethan~ [1] https://pypi.python.org/pypi/aenum

4 8

Tracker Etiquette
by Ethan Furman 08 May '16

08 May '16

I just reviewed an issue on the tracker, and found that many, if not all, of my comments made at the time I completely disagree with (both now, and before -- I'm going to claim sleep deprivation). Obviously I should post a new comment explaining my thoughts about the issue, but what should I do with the old comments? Is it acceptable to delete them? -- ~Ethan~

7 7

Re: [Python-Dev] Wordcode: new regular bytecode using 16-bit units
by zreed＠fastmail.com 06 May '16

06 May '16

Here is something I wrote because I was also unsatisfied with byteplay's API: https://github.com/zachariahreed/byteasm. Maybe it's useful in a discussion of "minimum viable" api for bytecode manipulation.

2 1