[issue12981] rewrite multiprocessing (senfd|recvfd) in Python

Charles-François Natali added the comment: > I don't think that it's a problem to remove private functions. > Alright. > Is it mandatory to send a non-empty message (first argument for sendmsg, b'x' > in your patch)? The original C function sends a random byte :-) > Some implementation can re

[issue6715] xz compressor support

Changes by Nadeem Vawda : Added file: http://bugs.python.org/file23158/95016f363e6c.diff ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue12857] Expose called function on frame object

Eric Snow added the comment: Nick, does thing look better? -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue12983] byte string literals with invalid hex escape codes raise ValueError instead of SyntaxError

Changes by Ezio Melotti : -- nosy: +ezio.melotti stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue12537] mailbox's _become_message is very fragile

R. David Murray added the comment: That is the first step, yes. In addition to that we need to have the various explain_to methods delete the special attributes that aren't valid for the new Message subtype. -- ___ Python tracker

[issue1172711] long long support for array module

STINNER Victor added the comment: @meadori: please write the version of your patch directly in the filename. For example, I use the pattern: name.patch, name-2.patch, name-3.patch, ... -- ___ Python tracker ___

[issue12537] mailbox's _become_message is very fragile

David Lam added the comment: Hi hi, noob here. I found this today after clicking 'Easy issues' link. Would something like this work? test_mailbox.py seems to pass. However, I'm not too sure what more needs to be done in the _explain_to. It seems like everything to convert headers/flags betw

[issue12984] XML NamedNodeMap ( attribName in NamedNodeMap fails )

New submission from Matthew Newcomb : I was cleaning up some old code to make it pep8 compliant and came across this bug. Switching from 'has_key' to 'in' does not work with a xml.dom.minidom.NamedNodeMap. An easy solution appears to be to add a '__contains__' method to NamedNodeMap. This

[issue12983] byte string literals with invalid hex escape codes raise ValueError instead of SyntaxError

New submission from Ned Deily : In behavior carried over from Python 2 string literals, Python 3 byte string literals raise a less helpful ValueError exception when an invalid hex escape code is given: >>> x = b'\x0' ValueError: invalid \x escape A string literal raises a SyntaxError

[issue12973] int_pow() implementation is incorrect

Stefan Krah added the comment: == CPython 2.7.2+ (2.7:a698ad2741da+, Sep 15 2011, 00:17:28) [GCC 4.2.1 Compatible Clang 3.0 (trunk 139637)] == FreeBSD-8.0-RELEASE-amd64-64bit-ELF little-endian == /usr/home/stefan/pydev/cpython/build/test_python_71451 With clang 3.0 from trunk, the pow() fa

[issue12980] segfault in test_json on AMD64 FreeBSD 8.2 2.7

Stefan Krah added the comment: I'm completely puzzled by this. I ran *all* tests manually on the same machine with clang with the same parameters as the buildbot (--with-pydebug, make buildbottest) and they pass. I reverted the buildbot to gcc, it'll be green again soon. Closing, since it can'

[issue9871] IDLE 3 crashes processing byte strings with invalid hex escape sequences

Ned Deily added the comment: Thanks for your suggested patch! A similar change was needed in idle lib/ScriptBinding.py to handle the same case for script files in edit windows. Applied in 3.2 (for 3.2.3) and default (for 3.3). -- assignee: -> ned.deily nosy: +ned.deily resolution:

[issue9871] IDLE dies when using some regex

Roundup Robot added the comment: New changeset e74860883a9c by Ned Deily in branch '3.2': Issue #9871: Prevent IDLE 3 crash when given byte stings http://hg.python.org/cpython/rev/e74860883a9c New changeset fe6c7771c25c by Ned Deily in branch 'default': Issue #9871: Prevent IDLE 3 crash when gi

[issue12980] segfault in test_json on AMD64 FreeBSD 8.2 2.7

STINNER Victor added the comment: I ran test_json (and then the full test suite using make buildbottest) on FreeBSD 8.2, with Python compiled by clang 2.8, and I'm unable to reproduce the bug. @skrah: Feel free to close the issue if we cannot reproduce it outside your buildbot :-) -

[issue12980] segfault in test_json on AMD64 FreeBSD 8.2 2.7

Changes by STINNER Victor : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12981] rewrite multiprocessing (senfd|recvfd) in Python

STINNER Victor added the comment: I don't think that it's a problem to remove private functions. Is it mandatory to send a non-empty message (first argument for sendmsg, b'x' in your patch)? The original C function sends a random byte :-) multiprocessing_recvfd() contains cmsg_level=SOL_SOCKE

[issue12678] test_packaging and test_distutils failures under Windows

Nadeem Vawda added the comment: Issue 12785 has a patch for the test_database failures. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue12678] test_packaging and test_distutils failures under Windows

STINNER Victor added the comment: test_packaging is still failing on Windows, example: == ERROR: test_uses (packaging.tests.test_database.TestDistribution) --

[issue12982] .pyo file cannot be imported

STINNER Victor added the comment: You need to run Python with -O command line option to ask Python to search for *.pyo files. -- nosy: +haypo ___ Python tracker ___ ___

[issue12982] .pyo file cannot be imported

New submission from Eric O. LEBIGOT : When creating a .pyo file (either with -O or -OO) and removing any .pyc or .py original file, import complains with "No module called ". The import does work with .pyc files. I'm not sure that this is the correct behavior, as the documentation does not

[issue11149] [PATCH] Configure should enable -fwrapv for clang

Stefan Krah added the comment: No, that's me playing around. I tried to use clang as the compiler for the build slave. I can't figure out yet why the segfaults occur. When I'm running the test manually, everything seems to work. -- ___ Python tracke

[issue12976] select module: only use EVFILT_TIMER if available (kqueue backend)

Changes by STINNER Victor : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/pytho

[issue12981] rewrite multiprocessing (senfd|recvfd) in Python

New submission from Charles-François Natali : Now that sendmsg()/recvmsg() are exposed in socketmodule, we could use them to replace the ad-hoc FD-passing routines used by multiprocessing.reduction. Antoine suggested adding sendfd()/recvfd() methods to socket objects, but I'm not sure about thi

[issue11149] [PATCH] Configure should enable -fwrapv for clang

STINNER Victor added the comment: The new issue #12980 may be a regression introduced by this issue. -- ___ Python tracker ___ ___ Py

[issue12980] segfault in test_json on AMD64 FreeBSD 8.2 2.7

New submission from STINNER Victor : http://www.python.org/dev/buildbot/all/builders/AMD64%20FreeBSD%208.2%202.7/builds/301 - [ 44/359] test_json Fatal Python error: Segmentation fault Current thread 0x0008010041c0: File "/usr/home/buildbot/bui

[issue12973] int_pow() implementation is incorrect

STINNER Victor added the comment: Aaaah, int_pow. I was testing Python 3.3. I tested Python 2.7 with clang 2.8, optimization level at -03 and without -fwrapv... I'm still unable to reproduce the issue. It's maybe an optimization introduced by clang 2.9. -- This issue remembers me the great

[issue12976] select module: only use EVFILT_TIMER if available (kqueue backend)

Charles-François Natali added the comment: Since this patch alone won't be enough to support MirBSD (and is required only for MirBSD), I suggest you to post the complete patch, and rename this issue "add support for MirBSD platform", or something along those lines. That way, we can consider th

[issue6560] socket sendmsg(), recvmsg() methods

Changes by Andrew Grover : -- nosy: -Andrew.Grover ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue12973] int_pow() implementation is incorrect

Mark Dickinson added the comment: I've got Clang from MacPorts, on OS X 10.6.8. iwasawa:cpython mdickinson$ clang --version clang version 2.9 (tags/RELEASE_29/final) Target: x86_64-apple-darwin10 Thread model: posix Without the patch (and before the -fwrapv inclusion), I get the following fai

[issue12973] int_pow() implementation is incorrect

STINNER Victor added the comment: > Thanks Victor; I just managed to install Clang, > and it looks I can reproduce the failures. What is your clang version? I ran ./python -m test -v test_long to check the issue. -- ___ Python tracker

[issue12973] int_pow() implementation is incorrect

Mark Dickinson added the comment: Thanks Victor; I just managed to install Clang, and it looks I can reproduce the failures. I'm testing right now to see if the patch fixes them all... -- ___ Python tracker

[issue12976] select module: only use EVFILT_TIMER if available (kqueue backend)

Benny Siegert added the comment: There are actually only two things that need to be touched for supporting MirBSD: This and the Configure script. I was planning to submit the Configure patches separately, I just started with this patch as it is so trivial. --

[issue12973] int_pow() implementation is incorrect

STINNER Victor added the comment: I removed -fwrapv from configure and Makefile, but I'm unable to reproduce the issue with clang 2.8 on x86_64 (Fedora 15). -- nosy: +haypo ___ Python tracker

[issue12976] select module: only use EVFILT_TIMER if available (kqueue backend)

Charles-François Natali added the comment: Hello, According to http://fxr.watson.org/fxr/ident?v=NETBSD;im=3;i=EVFILT_TIMER EVFILT_TIMER is defined on NetBSD. As for MirBSD, with all due respect, it really looks like a niche platform, definitely not officially supported by Python. Of course,

[issue12979] tkinter.font.Font object not usable as font option

New submission from ilikepython : If a Font object is passed as a font option to a Tk widget e. g.: import tkinter import tkinter.font f = tkinter.font.Font(family='Arial', size=30) root = Tk() label = tkinter.Label(root, text="Hello", font=f) label.pack() the font does not get respected at ru

[issue12978] Figure out extended attributes on BSDs

Ned Deily added the comment: Have you looked at Bob Ippolito's xattr module which has been out for some time and wraps Linux, OS X, BSD, and Solaris extended attributes? http://pypi.python.org/pypi/xattr -- nosy: +ned.deily ___ Python tracker

[issue12973] int_pow() implementation is incorrect

Mark Dickinson added the comment: Here's a simple patch. Is anyone in a good position to see if this fixes the tests failures for Clang (without the fwrapv flag)? -- keywords: +patch Added file: http://bugs.python.org/file23155/issue12975.diff ___

[issue7201] double Endian problem and more on arm

Meador Inge added the comment: The 'test_endian_double' test fails because the 'double' floating-point type for an interpreter built for OABI is unknown: >>> float.__getformat__("float") 'IEEE, little-endian' >>> float.__getformat__("double") 'unknown' According to [1], the double format disc

[issue7201] double Endian problem and more on arm

Meador Inge added the comment: OK, I got an OABI system setup. I am seeing the 'test_struct_return_2H' failure, which actually segfaults in my setup. The difference does, indeed, seem like an ABI mismatch. The test code that is failing has a Python side like: def test_struct_return_2H(s

[issue12936] armv5tejl segfaults: sched_setaffinity() vs. pthread_setaffinity_np()

Charles-François Natali added the comment: > I'd prefer to disable the misbehaving functions entirely on arm. -10 If we start disabling features on platforms with partly bogus implementations, we might as well drop threading on OpenBSD, sendmsg() on OS-X, etc. Furthermore, it's really just a

[issue12936] armv5tejl segfaults: sched_setaffinity() vs. pthread_setaffinity_np()

Stefan Krah added the comment: I'd prefer to disable the misbehaving functions entirely on arm. With the patch this combination of tests now works: ./python -m test -uall test_posix test_nntplib If you think the patch is good, I can run the whole test suite, too. [I'd rather wait for review

[issue12720] Expose linux extended filesystem attributes

Roundup Robot added the comment: New changeset f325439d7f84 by Benjamin Peterson in branch 'default': only compile xattrs on glibc (closes #12720) http://hg.python.org/cpython/rev/f325439d7f84 -- status: open -> closed ___ Python tracker

[issue12978] Figure out extended attributes on BSDs

New submission from Benjamin Peterson : Extended attribute support currently exists in the os module for Linux. BSD's (including OSX) have a similar (but of course incompatible) interface. They should be exposed through the same functions. For example, os.getxattr("myfile", "user.whatever") s

[issue12720] Expose linux extended filesystem attributes

Stefan Krah added the comment: The OS X buildbots fail to compile posixmodule.c: gcc -fno-strict-aliasing -g -O0 -Wall -Wstrict-prototypes-I. -I./Include -DPy_BUILD_CORE -c ./Modules/posixmodule.c -o Modules/posixmodule.o ./Modules/posixmodule.c: In function ‘try_getxattr’: ./Modules/p

[issue11149] [PATCH] Configure should enable -fwrapv for clang

Roundup Robot added the comment: New changeset 0f1e8c246a7b by Stefan Krah in branch '3.2': Issue #11149: recent versions of clang require the -fwrapv flag. http://hg.python.org/cpython/rev/0f1e8c246a7b New changeset 637c67b34a1a by Stefan Krah in branch 'default': Merge fix for issue #11149. h

[issue11149] [PATCH] Configure should enable -fwrapv for clang

Stefan Krah added the comment: > Does the test suite catch this bug? I think all of those fail due to the bug in pow(): 20 tests failed: test_array test_builtin test_bytes test_decimal test_float test_fractions test_getargs2 test_index test_int test_itertools test_list test_long te

[issue12977] socket.socket.setblocking does not raise exception if no data available

New submission from Florian Ludwig : The documentation states: > In non-blocking mode, if a recv() call doesn’t find any data, [...], a error > exception is raised; [0] Which is wrong. If no data is available recv() does not raise an exception but returns an empty string. [0] http://docs.pyt

[issue12960] threading.Condition is not a class

Nikolaus Rath added the comment: On 09/14/2011 04:29 AM, STINNER Victor wrote: > > STINNER Victor added the comment: > >> Yes, but further down it still says: >> >> """ >> class threading.Condition([lock]) >> >> If the lock argument is given and not None, [] >> """ > > What do you s

[issue12976] select module: only use EVFILT_TIMER if available (kqueue backend)

New submission from Benny Siegert : When building python-2.6 on MirBSD, building the select module (which uses the kqueue backend on this platform) fails. This is because EVFILT_TIMER is not available on the platform. The proposed patch is for python-2.6 but should apply to tip too. This was

[issue9871] IDLE dies when using some regex

Changes by Popa Claudiu : Added file: http://bugs.python.org/file23152/idle.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue9871] IDLE dies when using some regex

Popa Claudiu added the comment: Wrong patch. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9871] IDLE dies when using some regex

Changes by Popa Claudiu : Removed file: http://bugs.python.org/file23151/idle.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue9871] IDLE dies when using some regex

Popa Claudiu added the comment: I've attached a patch, hope it is ok. -- keywords: +patch Added file: http://bugs.python.org/file23151/idle.patch ___ Python tracker ___ _

[issue9871] IDLE dies when using some regex

Popa Claudiu added the comment: I found the culprit. I wrote b"\x" in IDLE and the window immediatly disappeared. Then, to traceback the problem, I started a python shell and typed the following lines. It seems that in showsyntaxerror, value is different that what was expected. C:\>python P

[issue12960] threading.Condition is not a class

Eli Bendersky added the comment: > What do you suggest? Replace it by class threading._Condition? -1 on this IMHO just documenting the situation as it is would make more sense -- nosy: +eli.bendersky ___ Python tracker

[issue12973] int_pow() implementation is incorrect

Martin v. Löwis added the comment: Notice that this "signed overflow" issue is also tracked as #1621. I don't mind keeping this issue open, though - it's unlikely that #1621 will be fixed within this decade. unless somebody does some heroic effort. -- nosy: +loewis __

[issue9871] IDLE dies when using some regex

Popa Claudiu added the comment: Hello. This happens with this version of IDLE too: Python 3.2.1 (default, Jul 10 2011, 21:51:15) [MSC v.1500 32 bit (Intel)] on win32. I could write a patch if I knew where to start. -- ___ Python tracker

[issue12386] packaging fails in install_distinfo when writing RESOURCES

Vinay Sajip added the comment: I looked at this bug again - I was getting a little confused about it ;-) The problem is happening not when writing out a resource, but the RESOURCES file listing the resources installed. This is a text file, of course, so my suggested fix of using open(resource

[issue12960] threading.Condition is not a class

STINNER Victor added the comment: > Yes, but further down it still says: > > """ > class threading.Condition([lock]) > > If the lock argument is given and not None, [] > """ What do you suggest? Replace it by class threading._Condition? --

[issue12973] int_pow() implementation is incorrect

Mark Dickinson added the comment: Reopening and assigning to me; it would be good to fix this in intobject.c as well as adding the Clang-specific -fwrapv fix. -- assignee: -> mark.dickinson nosy: +mark.dickinson status: closed -> open ___ Python t

[issue11149] [PATCH] Configure should enable -fwrapv for clang

Mark Dickinson added the comment: >>> 2**64 0 Urk! I'd call that a release blocker. -- ___ Python tracker ___ ___ Python-bugs-list