Mailman 3 January 2010 - Python-Dev

GIL required for _all_ Python calls?
by MRAB Jan. 8, 2010

Jan. 8, 2010

Hi, I've been wondering whether it's possible to release the GIL in the regex engine during matching. I know that it needs to have the GIL during memory-management calls, but does it for calls like Py_UNICODE_TOLOWER or PyErr_SetString? Is there an easy way to find out? Or is it just a case of checking the source files for mentions of the GIL? The header file for PyList_New, for example, doesn't mention it! Thanks

8 15

Backported faster RLock to Python 2.6.
by Johan Gill Jan. 8, 2010

Jan. 8, 2010

Hi devs, the company where I work has done some work on Python, and the question is how this work, owned by the company, can be contributed to the community properly. Are there any license issues or other pitfalls we need to think about? I imagine that other companies have contributed before, so this is probably an already solved problem. Regards Johan Gill Agama Technologies

5 8

Re: [Python-Dev] Question over splitting unittest into a package
by Benjamin Peterson Jan. 8, 2010

Jan. 8, 2010

2009/12/30 Martin (gzlist) <gzlist(a)googlemail.com>: > Hi Benjamin, Hi! > > In rev 74094 of Python, you split the unittest module up, could you > point me at any bug entries or discussion over this revision so I can > catch up? This was mostly a discussion on IRC between Michael Foord and myself. > > As a side-effect you seem to have changed the method of marking a > module as not worth including in a traceback to be no longer > extensible. > > Before:… [View More]

4 6

test_ctypes failure on AIX 5.3 using python-2.6.2 and libffi-3.0.9
by swamy sangamesh Jan. 7, 2010

Jan. 7, 2010

Hi All, I built the python-2.6.2 with the latest libffi-3.0.9 in AIX 5.3 using xlc compiler. When i try to run the ctypes test cases, two failures are seen in test_bitfields. *test_ints (ctypes.test.test_bitfields.C_Test) ... FAIL test_shorts (ctypes.test.test_bitfields.C_Test) ... FAIL* I have attached the full test case result. If i change the type c_int and c_short to c_unit and c_ushort of class "BITS(Structure)" in file test_bitfields.py then no failures are seen. Has anyone faced the … [View More]

1 0

bug triage
by Chris Withers Jan. 7, 2010

Jan. 7, 2010

Hi All, Is there a high volume of incoming bugs to the Python tracker? If so, I'd like to help with triaging. I think I have all the necessary access, what I'm missing is the knowledge of how to set myself up to get notifications of new bugs... How do I do that? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

13 22

PEP 386 and PEP 345
by Tarek Ziadé Jan. 6, 2010

Jan. 6, 2010

Hi, I think we've reached a consensus on those two PEPs. Although, there's one last point that was forgotten in the discussions : I've introduced "rc" in the pre-releases markers, so PEP 386 is compatible with Python's own version scheme. "rc" comes right after "c" in the sorting. It's slightly redundant with the "c" marker but I don't think this really matters as long as consumers know how to order them (a < b < c < rc). I have also stated that "c" is the preferred marker for third … [View More]

3 2

Suggestion: new 3 release with backwards compatibility
by Juan Fernando Herrera J. Jan. 6, 2010

Jan. 6, 2010

How about a new python 3 release with (possibly partial) backwards compatibility with 2.6? I'm a big 3 fan, but I'm dismayed at the way major software hasn't been ported to it. I'm eager to use 3, but paradoxically, the 3 release makes me rather stuck with 2.6. Excuse me if this has been suggested in the past.

9 13

Pronouncement on PEP 389: argparse?
by Steven Bethard Jan. 4, 2010

Jan. 4, 2010

So there wasn't really any more feedback on the last post of the argparse PEP other than a typo fix and another +1. http://www.python.org/dev/peps/pep-0389/ Can I get a pronouncement? Here's a summary of the responses. (Please correct me if I misinterpreted anyone.) * Floris Bruynooghe +1 * Brett Cannon +1 * Nick Coghlan +1 * Michael Foord +1 * Yuval Greenfield +1 * Doug Hellmann +1 * Kevin Jacobs +1 * Paul Moore +1 * Jesse Noller +1 * Fernando Perez +1 * Jon Ribbens +1 * Vinay Sajip +1 * … [View More]

15 32

Proposing PEP 345 : Metadata for Python Software Packages 1.2
by Tarek Ziadé Jan. 4, 2010

Jan. 4, 2010

Hi, On behalf of the Distutils-SIG, I would like to propose to addition of PEP 345 (once and *if* PEP 386 is accepted). It's the metadata v1.2: http://www.python.org/dev/peps/pep-0345/ PEP 345 was initiated a while ago by Richard Jones, and reworked since then together with PEP 386, at Pycon last year and in Distutils-SIG. The major enhancements are: - being able to express dependencies on other *distributions* names, rather than packages names or modules names. This enhancement comes … [View More]

21 105

Providing support files to assist 3.x extension authors
by Case Vanhorsen Jan. 3, 2010

Jan. 3, 2010

Hello, When I ported gmpy (Python to GMP multiple precision library) to Python 3.x, I began to use PyLong_AsLongAndOverflow frequently. I found the code to slightly faster and cleaner than using PyLong_AsLong and checking for overflow. I looked at making PyLong_AsLongAndOverflow available to Python 2.x. http://bugs.python.org/issue7528 includes a patch that adds PyLong_AsLongAndOverflow to Python 2.7. I also included a file (py3intcompat.c) that can be included with an extension's source code … [View More]

4 4