Mailman 3 July 2015 - Python-Dev

Datetime SIG created
by Brett Cannon July 29, 2015

July 29, 2015

https://mail.python.org/mailman/listinfo/datetime-sig In the future feel free to redirect date- and time-related discussions to the SIG since datetime stuff requires such a specific domain knowledge that most of us have. I am also looking for people to be admins of the list. If you're willing to admin the list please let me know and I will add you.

2 1

Building python 2.7.10 for Windows from source
by Mark Kelley July 28, 2015

July 28, 2015

I have been using Python for some time but it's been a decade since I've tried to build it from source, back in the 2.4 days. Things seem to have gotten a little more complicated now. I've read through the PCBuild/README file and got most stuff compiling. I find it a little odd that there are special instructions for the building the release version of tcl/tk. Is that what the developers actually do when they cut a release, or is there some other, top-level script that does this … [View More]

4 5

Please create the datetime-sig mailing list
by Brett Cannon July 28, 2015

July 28, 2015

[bcc'ed python-dev] Initial admin can be me and I will be in charge of finding more suitable admins to manage the list.

1 0

PyCapsule_Import semantics, relative imports, module names etc.
by John Dennis July 26, 2015

July 26, 2015

While porting several existing CPython extension modules that form a package to be 2.7 and 3.x compatible the existing PyObject_* API was replaced with PyCapsule_*. This introduced some issues the existing CPython docs are silent on. I'd like clarification on a few issues and wish to raise some questions. 1. Should an extension module name as provided in PyModule_Create (Py3) or Py_InitModule3 (Py2) be fully package qualified or just the module name? I believe it's just the module name (… [View More]see item 5 below) Yes/No? 2. PyCapsule_Import does not adhere to the general import semantics. The module name must be fully qualified, relative imports are not supported. 3. PyCapsule_Import requires the package (e.g. __init__.py) to import *all* of it's submodules which utilize the PyCapsule mechanism preventing lazy on demand loading. This is because PyCapsule_Import only imports the top level module (e.g. the package). From there it iterates over each of the module names in the module path. However the parent module (e.g. globals) will not contain an attribute for the submodule unless it's already been loaded. If the submodule has not been loaded into the parent PyCapsule_Import throws an error instead of trying to load the submodule. The only apparent solution is for the package to load every possible submodule whether required or not just to avoid a loading error. The inability to load modules on demand seems like a design flaw and change in semantics from the prior use of PyImport_ImportModule in combination with PyObject. [One of the nice features with normal import loading is setting the submodule name in the parent, the fact this step is omitted is what causes PyCapsule_Import to fail unless all submodules are unconditionally loaded). Shouldn't PyCapsule_Import utilize PyImport_ImportModule? 4. Relative imports seem much more useful for cooperating submodules in a package as opposed to fully qualified package names. Being able to import a C_API from the current package (the package I'm a member of) seems much more elegant and robust for cooperating modules but this semantic isn't supported (in fact the leading dot syntax completely confuses PyCapsule_Import, doc should clarify this). 5. The requirement that a module specifies it's name as unqualified when it is initializing but then also has to use a fully qualified package name for PyCapsule_New, both of which occur inside the same initialization function seems like an odd inconsistency (documentation clarification would help here). Also, depending on your point of view package names could be considered a deployment/packaging decision, a module obtains it's fully qualified name by virtue of it's position in the filesystem, something at compile time the module will not be aware of, another reason why relative imports make sense. Note the identical comment regarding _Py_PackageContext in modsupport.c (Py2) and moduleobject.c (Py3) regarding how a module obtains it's fully qualified package name (see item 1). Thanks! -- John [View Less]

3 2

[RELEASED] Python 3.5.0b4 is now available
by Larry Hastings July 26, 2015

July 26, 2015

On behalf of the Python development community and the Python 3.5 release team, I'm delighted to announce the availability of Python 3.5.0b4. Python 3.5.0b4 is scheduled to be the last beta release; the next release will be Python 3.5.0rc1, or Release Candidate 1. Python 3.5 has now entered "feature freeze". By default new features may no longer be added to Python 3.5. This is a preview release, and its use is not recommended for production settings. An important reminder for Windows users … [View More]

2 1

Summary of Python tracker Issues
by Python tracker July 24, 2015

July 24, 2015

ACTIVITY SUMMARY (2015-07-17 - 2015-07-24) 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 4957 (+10) closed 31511 (+43) total 36468 (+53) Open issues with patches: 2254 Issues opened (34) ================== #23591: Add IntFlags http://bugs.python.org/issue23591 reopened by r.david.murray #24619: async/await parser issues http://bugs.python.org/… [View More]

1 0

[python_default-nightly] Benchmark Results for 3bbd0cbfe836511dd3e05fcc30ffb5bdbfe686ea
by lp_benchmark_robot July 24, 2015

July 24, 2015

Hi Internals, This is the first message from Intel's language optimization team. We would like to provide the Python internals developer community with a daily service which will monitor latest committed patches performance regressions against well known workloads. Our aim is to run a multitude of workloads as well as real-life scenarios which the community considers relevant. The service will send daily bulletins containing latest measurements for daily variations and variations against … [View More]latest stable release run on our Intel-enabled servers. The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp(a)lists.01.org. You can also check our website: https://www.01.org/lp Results for project python_default-nightly, build date 2015-07-24 09:02:02 commit: 3bbd0cbfe836511dd3e05fcc30ffb5bdbfe686ea revision date: 2015-07-24 07:43:44 environment: Haswell-EP cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB mem: 128 GB os: CentOS 7.1 kernel: Linux 3.10.0-229.4.2.el7.x86_64 Note: Baseline results were generated using release v3.4.3, with hash b4cbecbc0781e89a309d03b60a1f75f8499250e6 from 2015-02-25 12:15:33+00:00 -------------------------------------------------------------------------------- benchmark unit change since change since last run v3.4.3 -------------------------------------------------------------------------------- :-) django_v2 sec 1.12735% 7.47953% :-( pybench sec -0.53822% -2.40216% :-( regex_v8 sec 0.61774% -2.32010% :-| nbody sec 1.75860% -0.76206% :-) json_dump_v2 sec 2.13422% -0.56930% Our lab does a nightly source pull and build of the Python project and measures performance changes against the previous stable version and the previous nightly measurement. This is provided as a service to the community so that quality issues with current hardware can be identified quickly. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. This document may contain information on products, services and/or processes in development. Contact your Intel representative to obtain the latest forecast, schedule, specifications and roadmaps. The products and services described may contain defects or errors known as errata which may cause deviations from published specifications. Current characterized errata are available on request. (C) 2015 Intel Corporation. [View Less]

1 0

Python automatic optimization
by Andrew Steinberg July 24, 2015

July 24, 2015

Hello everybody, I am using Python 2.7 as a backbone for some mathematical simulations. I recently discovered a tool called AutoFDO and I tried compiling my own Python version, but I did not manage to get it working. My question is, will sometime in the future Python include this tool? Thank you,Andrew

3 2

Reminder: Python 3.5 beta 4 is tagged in one week
by Larry Hastings July 23, 2015

July 23, 2015

Approximately a week from when I post this, I'll be tagging Python 3.5 beta 4, which is the last beta before we go to release candidates. Please wind up all your bug fixes soon, I'd really like checkins to 3.5 to stop soon. And a minor reminder: when we hit Release Candidate 1, I'll be switching the canonical repo for 3.5 to a public Bitbucket repo. Any bug fixes that go in between RC 1 and final will only be merged using Bitbucket "pull requests". The new workflow experiment continues, //arry/

2 4

Devguide - Add Communications Quick Start Section
by Carol Willing July 23, 2015

July 23, 2015

I would like to add a "Communications Quick Start" section to the beginning of the Python Developer's Guide. Productive communication between each other will always be critical to future development of CPython and maintaining releases, infrastructure, documentation, and more. Unproductive communication saps energy of contributors, reduces engagement in the project, and limits creativity and fulfillment in contributing. As a contributor who finds great value in the power and zen of … [View More]

6 6