[issue12850] [PATCH] stm.atomic

Armin Rigo added the comment: That's why I don't really know which concept is the best: the core of transactionmodule.c is just about one page in length, so there are only so many ways to split this code between CPython and the module... Attached the latest suggestion. I am also fine if this

[issue12850] [PATCH] stm.atomic

Nick Coghlan added the comment: I quite like the last idea. Something like: _PyEval_SuspendOtherThreads(PyThreadState *tstate, PyThread_lock_type lock); All threads other than tstate will be prevented from executing further interpreter bytecodes until "lock" is released. Offering this API

[issue12871] Disable sched_get_priority_min/max if Python is compiled without threads

Charles-François Natali added the comment: > It builds correctly with -pthread or -lpthread, but it fails to build without > these options. > Not on Linux: this is specific to OpenBSD. > sched_get_priority_max() and sched_get_priority_min() come from libpthread on > OpenBSD, whereas Python o

[issue12852] POSIX level issues in posixmodule.c on OpenBSD 5.0

Remi Pointel added the comment: > Rémi : what happens if you manually add > extern DIR *fdopendir(int fd); > at the beginning of posixmodule.c? Hello, it seems to correctly work: ./python Lib/test/test_posix.py testNoArgFunctions (__main__.PosixTester) ... ok test_access (__main__.PosixTeste

[issue12850] [PATCH] stm.atomic

Armin Rigo added the comment: Antoine: we could take two lines from the current implementation of these hook from stm/transactionmodule.c, and move them to the interpreter core. CPython would end up with containing the core logic for transactions. A possible API would look like that: /* st

[issue12882] mmap crash on Windows

New submission from Abhijit Bhattacharjee : The following Code causes Python to crash import os import mmap data = mmap.mmap(open(,"r+").fileno(),os.path.getsize()) assuming is present in the current working directory -- components: Interpreter Core, Windows messages: 143378 nosy: itab

[issue2636] Adding a new regex module (compatible with re)

Steven D'Aprano added the comment: Ezio Melotti wrote: > Ezio Melotti added the comment: > > Also note that some behaviors are not "old" or "compatible", but just > different. For example why inline flags should be the old (or new) behavior? > Or e.g. the behavior of version 2 but not 0 an

[issue12881] ctypes: segfault with large structure field names

New submission from Meador Inge : Reproduced on Fedora 15 with tip Python: [meadori@motherbrain cpython]$ ./python Python 3.3.0a0 (default:3102951cc1ce+, Sep 1 2011, 22:19:06) [GCC 4.6.0 20110603 (Red Hat 4.6.0-10)] on linux Type "help", "copyright", "credits" or "license" for more informatio

[issue12764] segfault in ctypes.Struct with bad _fields_

Meador Inge added the comment: Vlad, Thanks for the patch. A few nits: 1. The test case is in 'test_bitfields.py'. I think it should go in 'test_structures.py'. 2. The test case would probably be cleaner using a 'with' context manager: with self.assertRaises(TypeE

[issue2636] Adding a new regex module (compatible with re)

Ezio Melotti added the comment: Also note that some behaviors are not "old" or "compatible", but just different. For example why inline flags should be the old (or new) behavior? Or e.g. the behavior of version 2 but not 0 and 1? Also what if I want zero-width splits but not nested sets and

[issue12819] PEP 393 - Flexible Unicode String Representation

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6006] ffi.c compile failures on AIX 5.3 with xlc

Changes by Meador Inge : -- assignee: theller -> nosy: -theller priority: normal -> low stage: -> patch review type: -> compile error ___ Python tracker ___ __

[issue5718] Problem compiling ffi part of build on AIX 5.3.

Changes by Meador Inge : -- assignee: theller -> nosy: -theller priority: normal -> low stage: -> needs patch ___ Python tracker ___ ___

[issue6980] fix ctypes build failure on armel-linux-gnueabi with -mfloat-abi=softfp

Meador Inge added the comment: Whoops. I meant to post a link to the commit before. It is here: http://hg.python.org/cpython/rev/584db03e5248. -- ___ Python tracker ___ __

[issue6980] fix ctypes build failure on armel-linux-gnueabi with -mfloat-abi=softfp

Meador Inge added the comment: This was, in fact, committed already. -- assignee: theller -> nosy: +meadori -theller resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue9175] ctypes doesn't build on hp-ux

Changes by Meador Inge : -- assignee: theller -> nosy: -theller priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list m

[issue9030] ctypes variable limits

Changes by Meador Inge : -- nosy: -theller stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue11920] ctypes: Strange bitfield structure sizing issue

Meador Inge added the comment: Hi Steve, There is currently no way to deal with this situation. Vlad has opened issue12528 with a proposal to make the allocation strategy configurable from the 'ctypes' API. Please follow that issue if you are still interested. I am closing this issue. --

[issue6069] casting error from ctypes array to structure

Meador Inge added the comment: I opened issue12880 for the doc bug. Closing this one out ... -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___

[issue6069] casting error from ctypes array to structure

Changes by Meador Inge : -- stage: test needed -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue12880] ctypes: clearly document how structure bit fields are allocated

New submission from Meador Inge : As issues like issue6069 and issue11920 allude to, figuring out how 'ctypes' allocates bit-fields is not very clear. The documentation should be enhanced to flesh this out in more detail. As an example, Microsoft documents the VC++ implementation in a reason

[issue12528] Implement configurable bitfield allocation strategy

Meador Inge added the comment: Hi Vlad, On Thu, Sep 1, 2011 at 1:30 PM, Vlad Riscutia wrote: > Vlad Riscutia added the comment: > > Well currently we pack bitfields with an algorithm that uses #ifdefs for GCC > and MSVC builds. This feature tries to remove the > hardcoded behavior and imple

[issue10882] Add os.sendfile()

Changes by Yury Selivanov : -- nosy: +Yury.Selivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue2636] Adding a new regex module (compatible with re)

Steven D'Aprano added the comment: Matthew Barnett wrote: > Matthew Barnett added the comment: > > I think I need a show of hands. > > Should the default be old behaviour (like re) or new behaviour? (It might be > old now, new later.) > > Should there be a NEW flag (as at present), or an OL

[issue2636] Adding a new regex module (compatible with re)

Ezio Melotti added the comment: In order to replace the re module, regex must have the same behavior (except for bugs, where the correct behavior is most likely preferred, even if it's different). Having re.OLD and warnings active by default in 3.3 (and possibly 3.4) should give enough time

[issue12852] POSIX level issues in posixmodule.c on OpenBSD 5.0

Antoine Pitrou added the comment: Rémi : what happens if you manually add extern DIR *fdopendir(int fd); at the beginning of posixmodule.c? -- nosy: +pitrou ___ Python tracker ___

[issue12852] POSIX level issues in posixmodule.c on OpenBSD 5.0

Changes by STINNER Victor : -- title: test_posix.test_fdlistdir() segfault on OpenBSD -> POSIX level issues in posixmodule.c on OpenBSD 5.0 ___ Python tracker ___ __

[issue10278] add time.wallclock() method

STINNER Victor added the comment: clock_gettime.patch: add time.clock_gettime() function and time.CLOCK_xxx constants. The patch requires to rerun "autoconf". For the documentation, I don't know the availability of this function. Is it available on Windows? CLOCK_REALTIME doc contains "Settin

[issue12636] IDLE ignores -*- coding -*- with -r option

Roundup Robot added the comment: New changeset fef1ed14 by Victor Stinner in branch '3.2': Issue #12636: IDLE reads the coding cookie when executing a Python script. http://hg.python.org/cpython/rev/fef1ed14 New changeset a8748022504f by Victor Stinner in branch 'default': Merge 3.2: Is

[issue12636] IDLE ignores -*- coding -*- with -r option

Changes by STINNER Victor : -- resolution: works for me -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue12636] IDLE ignores -*- coding -*- with -r option

STINNER Victor added the comment: Fixed, thanks for the report. Python 2.7 is not affected by this bug. -- versions: +Python 3.3 ___ Python tracker ___

[issue12871] Disable sched_get_priority_min/max on OpenBSD if Python is compiled without threads

Changes by STINNER Victor : -- title: Disable sched_get_priority_min/max if Python is compiled without threads -> Disable sched_get_priority_min/max on OpenBSD if Python is compiled without threads ___ Python tracker

[issue12871] Disable sched_get_priority_min/max if Python is compiled without threads

STINNER Victor added the comment: > For example, the following snippet builds correctly on Linux It builds correctly with -pthread or -lpthread, but it fails to build without these options. sched_get_priority_max() and sched_get_priority_min() come from libpthread on OpenBSD, whereas Python

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

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

[issue12494] subprocess: check_output() doesn't close pipes on error

STINNER Victor added the comment: > The second patch looks good. Tests? I don't see how to test that the pipes are closed, because the Popen object (and its stdout and stderr attributes) are not visible outside the patched functions. > I consider that this issue is a bug, so it should be fix

[issue12494] subprocess: check_output() doesn't close pipes on error

Roundup Robot added the comment: New changeset 86b7f14485c9 by Victor Stinner in branch 'default': Issue #12494: Close pipes and kill process on error in subprocess functions http://hg.python.org/cpython/rev/86b7f14485c9 -- nosy: +python-dev ___ Pyth

[issue8813] SSLContext doesn't support loading a CRL

Antoine Pitrou added the comment: Is it enough to just load a CRL file, or is other functionality usually needed? The following APIs should help us do it: - X509_STORE *SSL_CTX_get_cert_store(const SSL_CTX *ctx); - int X509_STORE_add_crl(X509_STORE *ctx, X509_CRL *x); - X509_CRL *d2i_X509_CRL_f

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Charles-François Natali added the comment: Committed. Rémi, thanks once again for this report! -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Roundup Robot added the comment: New changeset a29b72950795 by Charles-François Natali in branch 'default': Issue #12868: Skip test_faulthandler.test_stack_overflow() on OpenBSD: http://hg.python.org/cpython/rev/a29b72950795 -- nosy: +python-dev ___

[issue2636] Adding a new regex module (compatible with re)

Jeffrey C. Jacobs added the comment: On 1 September 2011 16:12, Matthew Barnett wrote: > > Matthew Barnett added the comment: > > I think I need a show of hands. For my part, I recommend literal flags, i.e. re.VERSION222, re.VERSION300, etc. Then you know exactly what you're getting and alth

[issue12879] "method-wrapper" objects are difficult to inspect

Benjamin Peterson added the comment: 51e27f42beda and friends. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

STINNER Victor added the comment: > As for rthreads support, a quick search seems to indicate that its API is > exactly the same as pthreads, and it's even binary compatible. Python will > automatically use it when run on a OpenBSD system with rthreads enabled. Well... not exactly. I asked on #

[issue2636] Adding a new regex module (compatible with re)

Antoine Pitrou added the comment: > I think I need a show of hands. > > Should the default be old behaviour (like re) or new behaviour? (It > might be old now, new later.) > > Should there be a NEW flag (as at present), or an OLD flag, or a > VERSION parameter (0=old, 1=new, 2=?)? VERSION mig

[issue12537] mailbox's _become_message is very fragile

Changes by Justin Wehnes : -- nosy: +jwehnes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue12528] Implement configurable bitfield allocation strategy

Terry J. Reedy added the comment: As a (Windows) user, I would like to be able to download any working pre-compiled shared library (.dll) and access it via ctypes. The particular compiler used to compile cpythonx.y.z should not determine whether a Pythonx.y program works. The use of VSC2008 i

[issue2636] Adding a new regex module (compatible with re)

Matthew Barnett added the comment: I think I need a show of hands. Should the default be old behaviour (like re) or new behaviour? (It might be old now, new later.) Should there be a NEW flag (as at present), or an OLD flag, or a VERSION parameter (0=old, 1=new, 2=?)? -- __

[issue11879] TarFile.chown: should use TarInfo.uid if user lookup fails

Changes by Doug Hellmann : -- nosy: +doughellmann ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue12879] "method-wrapper" objects are difficult to inspect

New submission from Antoine Pitrou : This is a bit unhelpful: >>> s = io.StringIO() >>> s.__getattribute__ >>> dir(s.__getattribute__) Traceback (most recent call last): File "", line 1, in TypeError: object does not provide __dir__ -- components: Interpreter Core messages: 143349 n

[issue12878] io.StringIO doesn't provide a __dict__ field

Antoine Pitrou added the comment: I'm not sure why that is. Note that you can still set and get arbitrary attributes, so there must be a dict somewhere, but it isn't exposed. Also, there wasn't any significant change in StringIO in the 3.1 line. Benjamin, do you have any idea? >>> s = io.Stri

[issue12802] Windows error code 267 should be mapped to ENOTDIR, not EINVAL

Antoine Pitrou added the comment: Committed now. Hopefully it won't break anything! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: -Python 2.7 ___ Python tracker

[issue12802] Windows error code 267 should be mapped to ENOTDIR, not EINVAL

Roundup Robot added the comment: New changeset 385c2ec78f16 by Antoine Pitrou in branch '3.2': Issue #12802: the Windows error ERROR_DIRECTORY (numbered 267) is now http://hg.python.org/cpython/rev/385c2ec78f16 New changeset d72d5c942232 by Antoine Pitrou in branch 'default': Issue #12802: the

[issue12876] Make Test Error : ImportError: No module named _sha256

Gregory P. Smith added the comment: The fact that it called __get_builtin_constructor implies that the ssl backed _hashlib module was not available. It looks like the non-openssl standalone _sha256 module (and likely the _sha512 module) both failed to be compiled. I would not expect that to

[issue12878] io.StringIO doesn't provide a __dict__ field

New submission from Eric Promislow : I see that going from Python 3.1.1 to 3.1.2 instances of io.StringIO no longer have a __dict__ field. Why? Is this to make them unpicklable? -- components: IO messages: 143344 nosy: ericp priority: normal severity: normal status: open title: io.Str

[issue2636] Adding a new regex module (compatible with re)

Ezio Melotti added the comment: Changing the name of the flag is fine with me. Having a warning for unescaped brackets that trigger set operations might also be a solution (once escaped they will still work on the old re). Maybe the same could also be done for scoped flags. FWIW I tried to

[issue12528] Implement configurable bitfield allocation strategy

Vlad Riscutia added the comment: Well currently we pack bitfields with an algorithm that uses #ifdefs for GCC and MSVC builds. This feature tries to remove the hardcoded behavior and implement it as a runtime option. This should improve interop with other compilers. Currently I provided these

[issue7171] Add inet_ntop and inet_pton support for Windows

Changes by Antoine Pitrou : -- components: +Library (Lib) -IO, Windows keywords: +easy versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ ___

[issue12850] [PATCH] stm.atomic

Antoine Pitrou added the comment: I'm worried that by allowing users to pass function pointers here, we are allowing all kinds of uses that we will have to more or less support later. What exactly "taking the GIL" means and when exactly it is done in the execution process is an implementation

[issue12876] Make Test Error : ImportError: No module named _sha256

Changes by Antoine Pitrou : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue2636] Adding a new regex module (compatible with re)

Antoine Pitrou added the comment: > Thanks for the explanation, but isn't this a backward incompatible > feature? > I think it should be enabled only when the re.NEW flag is passed. > The idiom [][...] is also quite common, so I think it might break > different programs if regex has a different

[issue12528] Implement configurable bitfield allocation strategy

Meador Inge added the comment: As stated, how a particular compiler allocates bitfields is *extremely* implementation specific. There can be differences in implementations between different compilers, different *versions* of the same compiler, and different invocations of the same compiler w

[issue6069] casting error from ctypes array to structure

Vlad Riscutia added the comment: Sounds good. Please nosy me in the doc bug. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue2636] Adding a new regex module (compatible with re)

Ezio Melotti added the comment: Thanks for the explanation, but isn't this a backward incompatible feature? I think it should be enabled only when the re.NEW flag is passed. The idiom [][...] is also quite common, so I think it might break different programs if regex has a different behavior.

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Changes by Charles-François Natali : Removed file: http://bugs.python.org/file23078/openbsd_sigaltstack.diff ___ Python tracker ___ ___ Python

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Charles-François Natali added the comment: Here's a patch with an updated skip message. As for rthreads support, a quick search seems to indicate that its API is exactly the same as pthreads, and it's even binary compatible. Python will automatically use it when run on a OpenBSD system with r

[issue6069] casting error from ctypes array to structure

Meador Inge added the comment: On Thu, Sep 1, 2011 at 9:45 AM, Vlad Riscutia wrote: > Vlad Riscutia added the comment: > > Meador, I believe this was the first issue on the tracker that got me looking > into bitfield allocation. > I agree that big-endian on MSVC doesn't make too much sense b

[issue2636] Adding a new regex module (compatible with re)

Matthew Barnett added the comment: The regex module supports nested sets and set operations, eg. r"[[a-z]--[aeiou]]" (the letters from 'a' to 'z', except the vowels). This means that literal '[' in a set needs to be escaped. For example, re module sees "[][()]..." as: [ start of set

[issue2636] Adding a new regex module (compatible with re)

Ezio Melotti added the comment: I tried to run a test suite of 3kloc (not just about regex, but regex were used in several places) and I had only one failure: >>> s = u'void foo ( type arg1 [, type arg2 ] )' >>> re.sub('(?<=[][()]) |(?!,) (?!\[,)(?=[][(),])', '', s) u'void foo(type arg1 [, type

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

STINNER Victor added the comment: > Great! I didn't know that! It's a new feature of Python 3.3. I added it to skip a test on old FreeBDB, see test_threadsignal.py: USING_PTHREAD_COND = (sys.thread_info.name == 'pthread' and sys.thread_info.lock

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Steffen Daode Nurpmeso added the comment: > In Python 3.3, you can use sys.thread_info to check which threading > library is used. Great! I didn't know that! -- ___ Python tracker __

[issue6069] casting error from ctypes array to structure

Vlad Riscutia added the comment: Meador, I believe this was the first issue on the tracker that got me looking into bitfield allocation. I agree that big-endian on MSVC doesn't make too much sense but you can disregard that - using default endianess will still yield different sizes of bitfiel

[issue12877] Popen(...).stdout.seek(...) throws "Illegal seek"

STINNER Victor added the comment: > Why does it have a 'seek' method then? Python doesn't remove a method if the operation is forbidden. For example, Python doesn't remove write() method if the file is read only, and it doesn't remove most methods after close(). I prefer to have files with a

[issue12877] Popen(...).stdout.seek(...) throws "Illegal seek"

Jonas H. added the comment: Why does it have a 'seek' method then? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue12876] Make Test Error : ImportError: No module named _sha256

STINNER Victor added the comment: Do you have OpenSSL headers? -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue12876] Make Test Error : ImportError: No module named _sha256

Wong Wah Meng added the comment: Thanks for your reply: This is the output of the make, _ctypes and termios are failed to build. Python build finished, but the necessary bits to build these modules were not found: _bsddb _curses_curses_panel _sqlite3 _ssl

[issue12877] Popen(...).stdout.seek(...) throws "Illegal seek"

STINNER Victor added the comment: stdout is a PIPE. You cannot seek in a PIPE. Write stdout into a file, or use maybe BytesIO or StringIO? -- nosy: +haypo resolution: -> invalid status: open -> closed ___ Python tracker

[issue12877] Popen(...).stdout.seek(...) throws "Illegal seek"

Nadeem Vawda added the comment: This is expected behaviour - you cannot seek on a pipe. -- nosy: +nadeem.vawda ___ Python tracker ___ ___

[issue12877] Popen(...).stdout.seek(...) throws "Illegal seek"

New submission from Jonas H. : from subprocess import Popen, PIPE p = Popen(['ls'], stdout=PIPE) p.wait() p.stdout.seek(0) Traceback (most recent call last): File "t.py", line 5, in p.stdout.seek(0) IOError: [Errno 29] Illegal seek Python 2.7.2, Arch Linux x86-64 (Kernel 3.0) -

[issue2771] Test issue

Roundup Robot added the comment: New changeset 90586887032e by Ezio Melotti in branch 'default': test: change the content of the p file so http://hg.python.org/test/rev/90586887032e -- nosy: +python-dev status: open -> closed ___ Python tracker

[issue2771] Test issue

Changes by Ezio Melotti : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue12386] packaging fails in install_distinfo when writing RESOURCES

Vinay Sajip added the comment: @Éric: I also noticed that your latest comment "All text is bytes, so we can do all I/O in bytes when writing resources and avoid special-casing." contradicts your earlier position: "I agree about the nonsense of opening in binary mode." If using text mode, w

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

STINNER Victor added the comment: > OpenBSD does support 1:1 threads via the RThread library > since 2005, thanks to tedu@ and more fantastic guys! > It about to be super-stable (one commit in 2011, last "real > fix" in april 2010). > (There is a techtalk from tedu@ (Ted Unangst) about this libr

[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data

Antoine Pitrou added the comment: If you're casting to a larger signed type, then the semantics change, since there is a sign extension. For example (unsigned int) 0x could be cast to (long long) -1. You could cast to size_t instead and compare the result to SOCKLEN_T_MAX (which curre

[issue8409] gettext should honor $LOCPATH environment variable

Changes by Barry A. Warsaw : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue12873] 2to3 incorrectly handles multi-line imports from __future__

Changes by Sebastian Wiesner : -- nosy: +lunar ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12876] Make Test Error : ImportError: No module named _sha256

Amaury Forgeot d'Arc added the comment: Please run the "make" command again. It will list the modules that were skipped and not compiled. Which modules do you see there? Also, which version of OpenSSL is installed? -- nosy: +amaury.forgeotdarc ___

[issue4153] Unicode HOWTO up to date?

Ezio Melotti added the comment: I also left a few comments on rietveld about other things that can be improved. Please reply and comment there. -- ___ Python tracker ___ __

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

Steffen Daode Nurpmeso added the comment: Heya. OpenBSD does support 1:1 threads via the RThread library since 2005, thanks to tedu@ and more fantastic guys! It about to be super-stable (one commit in 2011, last "real fix" in april 2010). (There is a techtalk from tedu@ (Ted Unangst) about this

[issue12876] Make Test Error : ImportError: No module named _sha256

New submission from Wong Wah Meng : Hi there, I just build python 2.7.1 on my HP 11.31 Itanium 64 bit machine using gcc. When I finished the build and run "make test". It gives me error as depicted below:- $ ./python Lib/test/regrtest.py -v Traceback (most recent call last): File

[issue8409] gettext should honor $LOCPATH environment variable

Danilo Segan added the comment: I believe it's invalid. GNU gettext itself doesn't honor the LOCPATH variable, LOCPATH is basically used by GNU libc for pointing to locale data. Even though this also includes LC_MESSAGES, gettext has never used it afaik. If it's not invalid (iow, gettext shou

[issue12494] subprocess: check_output() doesn't close pipes on error

Ross Lagerwall added the comment: > I consider that this issue is a bug, so it should be fixed in 2.7 and > 3.2. I agree that *killing* the process is a behaviour change, but we > can just close pipes on error for 2.7 and 3.2. Yeah, that seems right. -- _

[issue12494] subprocess: check_output() doesn't close pipes on error

STINNER Victor added the comment: > The second patch looks good. Tests? Ok, I will try to write a new patch with tests. > But, it *probably* shouldn't be applied to 2.7& 3.2 given that it is a > behaviour change. I consider that this issue is a bug, so it should be fixed in 2.7 and 3.2. I

[issue12868] test_faulthandler.test_stack_overflow() failed on OpenBSD

STINNER Victor added the comment: > @Victor: can I commit the patch? I don't like the skip message. It doesn't tell that the problem comes from sigaltstack() and it doesn't contain the issue number. I would expect something like: "Issue #12868: sigaltstack() doesn't work on OpenBSD if Python

[issue4153] Unicode HOWTO up to date?

Ezio Melotti added the comment: After the recent discussions on python-dev I went through the Unicode howto and fixed a few things, then I found this issue so I'm attaching the patch here. The patch addresses mostly markup issues, but it also removes the usage of 'byte string'. A few more thin

[issue12837] Patch for issue #12810 removed a valid check on socket ancillary data

Nick Coghlan added the comment: I tend to be fairly paranoid about operating systems doing occasionally bizarre things, so I like having clearly defined behaviour even when the OS does something arguably nuts, but permitted by the relevant standard. Hence I think keeping the check is the righ