Mailman 3 February 2011 - Python-Dev

Re: [Python-Dev] [Python-checkins] r88484 - in python/branches/py3k: Lib/test/subprocessdata/fd_status.py Lib/test/test_subprocess.py Misc/NEWS
by Victor Stinner Feb. 22, 2011

Feb. 22, 2011

Le 21/02/2011 22:55, antoine.pitrou a écrit : > Author: antoine.pitrou > Date: Mon Feb 21 22:55:48 2011 > New Revision: 88484 > > Log: > Issue #10826: Prevent sporadic failure in test_subprocess on Solaris due > to open door files. > > if __name__ == "__main__": > - print(','.join(str(fd) for fd in range(0, _MAXFD) if isopen(fd))) > + fds = [] > + for fd in range(0, _MAXFD): > + try: > + st = os.fstat(fd) > + … [View More]

1 0

Distutils2 next steps
by Tarek Ziadé Feb. 21, 2011

Feb. 21, 2011

Hello Now that Python 3.2 is out, I am planning to do the following with Distutils2: 1 - release a new alpha before Pycon for community feedback 2 - add distutils2 back in the trunk, along with the changes in pkgutil and sysconfig 3 - continue the ongoing work in Distutils2 to prepare the first Python 3.3 release If you want me to give more details here on what is going to be done precisely in the various stdlib parts, let me know. I plan to do 2. as a sprint task, and will be looking for … [View More]

3 4

Bug in linking to gomp with python; causes crash in matplotlib.
by Hoyt Koepke Feb. 21, 2011

Feb. 21, 2011

Hello, I've encountered a strange bug that appears to be either in gcc's gomp implementation or in how python loads extension modules linked against gomp. Here's the error: Using gcc (multiple versions) on linux, I compile an empty c extension module and pass -lgomp as a linker arg. If I import it, running a simple script in matplotlib causes a segfault. Not passing -lgomp or not loading the empty module makes the code works fine. More specifically, if I compile: #include "Python.h" … [View More]static struct PyMethodDef methods[] = { {0, 0, 0, 0} }; PyMODINIT_FUNC initempty(void) { Py_InitModule4("empty", methods, 0, 0, PYTHON_API_VERSION); } using ``ext_modules = [Extension("empty", ["empty.c"], extra_link_args = ["-lgomp"])]``, then import empty import matplotlib.pylab as plt plt.figure() plt.plot([0,1], [0,1], '-b') plt.show() causes the program to segfault (removing ``import empty`` makes it fine). Looking at a traceback: #0 0x00f78bc7 in __cxa_allocate_exception () from /usr/lib/libstdc++.so.6 #1 0x008f51f2 in py_to_agg_transformation_matrix (obj=0x8223f58, errors=false) at src/agg_py_transforms.cpp:20 #2 0x008fdd73 in _path_module::update_path_extents (this=0x8e45f90, args=...) at src/path.cpp:378 #3 0x009048bd in Py::ExtensionModule<_path_module>::invoke_method_varargs (this=<value optimized out>, method_def=0x8e9ae30, args=...) at ./CXX/Python2/ExtensionModule.hxx:184 #4 0x008f0d96 in method_varargs_call_handler (_self_and_name_tuple=0x8e6eeac, _args=0x94e683c) at CXX/Python2/cxx_extensions.cxx:1714 #5 0x080dc0d0 in PyEval_EvalFrameEx () #6 0x080dddf2 in PyEval_EvalCodeEx () While occurring in some of matplotlib's extension code (and I haven't found another library that crashes it), the fact that the deciding factor is whether I link against gomp indicates the it's probably upstream somewhere. I encountered this error a year ago and asked about it on the matplotlib mailing list, but found a quick workaround then, and with deadline pressure I forgot about it. However, it's come up again, and then I was asked to bump it to python-dev, which is why I'm posting it here. I can reproduce it on the following systems. In all cases, matplotlib is compiled from source on the development branch (r8969) and uses QT4Agg as the backend, as is numpy, scipy, etc. If needed, I can track down more versions. gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.4, 64bit, Python 2.6.6, ubuntu 10.10 gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3, 64bit, Python 2.6.5, ubuntu 10.04 gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1, 32bit, Python 2.6.4, ubuntu 9.10 gcc 4.5.2 (source build), Python 2.6.5, ubuntu 10.04. On this build, the given source example does not produce the result, and I haven't been able to tweak it so it does. However, linking to a much larger extension library that uses many different parts of openmp causes exactly the same crash. If I recompile that library without openmp support, then everything works fine; with openmp support it corrupts something and matplotlib crashes in exactly the same way. gcc 4.3.2, Python 2.6.2, ubuntu 9.04 (I don't have access to this system any more, since it got upgraded, but it had the same problem a year ago). I'd be happy to provide any more information if needed. I attached example code that reproduces it. Let me know if I should file a bug report (and where to file it -- which is why I haven't yet). Thanks, --Hoyt ++++++++++++++++++++++++++++++++++++++++++++++++ + Hoyt Koepke + University of Washington Department of Statistics + http://www.stat.washington.edu/~hoytak/ + hoytak(a)gmail.com ++++++++++++++++++++++++++++++++++++++++++ [View Less]

2 2

w9xpopen.exe is still in 3.2
by anatoly techtonik Feb. 21, 2011

Feb. 21, 2011

Python definitely needs a development Roadmap to avoid things like w9xpopen.exe slipping off radar from release to release. We don't support Windows 9x since Python 2.6. What this file does in 3.x distributions? http://bugs.python.org/issue2405 -- anatoly t.

4 5

Gsoc 2011 ideas
by yeswanth swami Feb. 20, 2011

Feb. 20, 2011

Hi everyone, I am planning to apply for Gsoc 2011 for the PSF . I would like to know if any of you have any ideas which can be implemented this summer. I guess the gsoc 2011 ideas page has not been put up as yet. So I thought maybe any of you can suggest some ideas . Thanks Yeswanth

3 2

"Some" .pyc files not ending up in __pycache__ during installation
by Stefan Behnel Feb. 20, 2011

Feb. 20, 2011

Hi, sorry for asking here instead of filing a bug, but given that 3.2 final is pretty close, I wanted to make sure this gets considered. A Cython user noticed that the installation (setup.py install or bdist) puts several .pyc files into the installed source directory, instead of moving them into __pycache__. The latter is still used, and most of the .pyc files end up there, but not all of them. Some even end up in both directories, once with a ".cpython-32.pyc" suffix in __pycache__ and … [View More]

5 9

Finally fix installer to add Python to %PATH% on Windows
by anatoly techtonik Feb. 20, 2011

Feb. 20, 2011

Hi, I'd like to You probably know that after installation on Windows system it is possible to call Python from Explorer's Run dialog (Win-R). It is because Python path is added to App Paths registry key and Windows Explorer shell checks this key when looking for executable. But Python doesn't work from cmd session and, more importantly, *Python doesn't work from .bat files*. It is because cmd shell doesn't know about App Paths and relies on system PATH to find executable. As far as I remember,… [View More]

13 29

What's L2R status?
by INADA Naoki Feb. 19, 2011

Feb. 19, 2011

Ref: http://bugs.python.org/issue448679 Has this bug fixed already? This bug seems not be fixed for Python 2.6 and Python 3.2rc3. Python 3.2rc3 (r32rc3:88413, Feb 15 2011, 18:31:14) [GCC 4.4.5] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> C=0 >>> def x(): ... global C ... C += 1 ... return C ... >>> {x(): x(), x(): x()} {2: 1, 4: 3} -- INADA Naoki <songofacandy(a)gmail.com>

2 2

Summary of Python tracker Issues
by Python tracker Feb. 18, 2011

Feb. 18, 2011

ACTIVITY SUMMARY (2011-02-11 - 2011-02-18) 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 2655 (+28) closed 20370 (+22) total 23025 (+50) Open issues with patches: 1130 Issues opened (41) ================== #7284: optparse - display version in usage by default http://bugs.python.org/issue7284 reopened by techtonik #11195: next fixer fooled by … [View More]

1 0

3.2.0
by Terry Reedy Feb. 18, 2011

Feb. 18, 2011

I would like the next release called 3.2.0 rather than just 3.2. 'x.y' is known to be ambiguous and confusing. In most actual usages, I believe, it refers to the latest x.y.z release. On the site, the 'x.y' docs are almost always the latest version of the docs (actually x.y.z+additional fixes). In discussions on python-list, for instance, advice to use 'x.y' means to download and use the latest x.y.z release, not the initial x.y(.0) release. Similarly on the tracker, 'what happens with x.… [View More]

12 16