[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Vitaly added the comment: > The workaround should not be implemented in os.read because it is a very thin > wrapper around the system call and should stay that way. Although this issue was initially filed as "Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS", the s

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Chris Jerdonek added the comment: > Personally I think the best solution is to have the test framework allocate a > single test directory This is partially done. See here: http://hg.python.org/cpython/file/19c74cadea95/Lib/test/regrtest.py#l1810 # Run the tests in a context manager that temp

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Ronald Oussoren added the comment: The workaround should not be implemented in os.read because it is a very thin wrapper around the system call and should stay that way. -- ___ Python tracker _

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Trent Nelson added the comment: > Cleanup on test failure is supposed to be done. Cleanup on crash or > buildbot timeout isn't done as far as I know (and that was a concern I > had with the changes made to support.TESTFN and the cwd, but I didn't > articulate it very well). Ah, yeah, this is

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Trent Nelson added the comment: > > All my slaves' /tmp's are polluted with regrtest fluff. > Which "regrtest fluff" exactly? I was being lazy when I wrote that. By "regrtest fluff" I was referring to lingering files/directories in /tmp, owned by cpython, starting with tmp*. Few examples be

[issue15970] ElementTree HTML serialization incorrect for ,

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior versions: -Python 2.6, Python 3.1 ___ Python

[issue15970] ElementTree HTML serialization incorrect for ,

Roundup Robot added the comment: New changeset 3498ffd3cdee by Ezio Melotti in branch '2.7': #15970: xml.etree.ElementTree now serializes correctly the empty HTML elements "meta" and "param". http://hg.python.org/cpython/rev/3498ffd3cdee New changeset 17c528cff63f by Ezio Melotti in branch '3.2

[issue7559] TestLoader.loadTestsFromName swallows import errors

Changes by Julian Berman : -- nosy: +Julian ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue15971] Sporadic failure in test_dump_tracebacks_later_file (test_faulthandler)

New submission from Ezio Melotti: Seen on http://buildbot.python.org/all/builders/AMD64%20Lion%203.x/builds/428/steps/test/logs/stdio == FAIL: test_dump_tracebacks_later_file (test.test_faulthandler.FaultHandlerTests) -

[issue15970] ElementTree HTML serialization incorrect for ,

New submission from Joshua Biagio: There seems to be a very minor bug in the ElementTree.py file, for the so-called 'empty' elements that are serialized without a closing tag. The HTML_EMPTY tuple/set is used to lookup these tags. In the Lib/xml/etree/ElementTree.py file, the HTML_EMPTY tuple

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Nick Coghlan added the comment: The particular app that is getting affected is clearing out and rebuilding the logging configuration without restarting in response to a notification that the application config has changed. This was working OK on 2.6, but started misbehaving when ported to 2.7.

[issue11454] email.message import time

Ezio Melotti added the comment: re.compile seems twice as fast as pickle.loads: import re import pickle import timeit N = 10 s = "r = re.compile('[\\udc80-\\udcff]')" t = timeit.Timer(s, 'import re') print("%6.2f <- re.compile" % t.timeit(number=N)) s = "r = pickle.loads(p)" p = pickle.du

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Changes by Trent Nelson : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue7665] test_urllib2 and test_ntpath fail if path contains "\"

Changes by Ezio Melotti : -- nosy: +haypo stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Roundup Robot added the comment: New changeset 974a4cae6094 by Trent Nelson in branch 'default': #15965: Explicitly cast AT_FDCWD as (int). http://hg.python.org/cpython/rev/974a4cae6094 -- nosy: +python-dev ___ Python tracker

[issue8996] Add a default role to allow writing bare `len` instead of :func:`len`

Ezio Melotti added the comment: I think I'm -1 on this, for the following reasons: * it's less explicit; * it gives you less control (I'm thinking e.g. at the () added by :func:/:meth: but not :class:, so that :func:`int` and :class:`int` are rendered in different ways); * even though this m

[issue11664] Add patch method to unittest.TestCase

Ezio Melotti added the comment: IMHO a setattr-like API seems the obvious choice here, so that's what I would expect. I haven't used mock, so I wasn't familiar with mock.patch, but after skimming through the mock docs a bit I think I have to agree with Julian and RDM. In addition, I'm not sur

[issue15951] string.Formatter returns str for empty unicode template

Chris Jerdonek added the comment: Attached is a proposed patch. Some explanation behind the patch that stems from the above comments: The following is an example of Formatter.format() returning str in the current implementation that would break if we made Formatter.format() return unicode whe

[issue11664] Add patch method to unittest.TestCase

Chris Jerdonek added the comment: What about patch_object()? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11664] Add patch method to unittest.TestCase

Julian Berman added the comment: With all due respect, your response pretty much ignored mine completely. That's OK, I've agreed with you that patch seems more common. I'll point you additionally though to the fact that Éric's original post also used patch.object's semantics, as does test.test

[issue11664] Add patch method to unittest.TestCase

R. David Murray added the comment: I actually agree with Julian here. I much prefer patch.object and do my best to avoid mock.patch. support.patch is also equivalent to patch.object and not patch. That doesn't change the fact that other people prefer mock.patch, of course. I think mock.pat

[issue15415] Add temp_dir() and change_cwd() to test.support

Changes by Ezio Melotti : -- nosy: +ezio.melotti, flox type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue15304] Wrong path in test.support.temp_cwd() error message

Changes by Ezio Melotti : -- assignee: -> ezio.melotti nosy: +ezio.melotti type: -> behavior versions: +Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue7712] Add a context manager to change cwd in test.test_support and run the test suite in a temp dir.

Changes by Ezio Melotti : -- nosy: +cjerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue11664] Add patch method to unittest.TestCase

Michael Foord added the comment: Well, people vote with their code and find mock.patch vastly more useful than patch.object... -- ___ Python tracker ___

[issue11664] Add patch method to unittest.TestCase

Julian Berman added the comment: It's slightly less confusing -- "Where do I patch" is the question that will never go away, and the fact that you don't have the `sys` module imported is a small hint that you should be doing patch(mymodule.sys, "path") not patch("sys.path"). Also, the fact tha

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Antoine Pitrou added the comment: > All my slaves' /tmp's are polluted with regrtest fluff. Which "regrtest fluff" exactly? -- nosy: +pitrou ___ Python tracker ___ _

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

Antoine Pitrou added the comment: The patch looks ok to me. At least passing "fn" as keyword arg should be fixed. Passing "self" as keyword arg admittedly sounds a bit awkward. -- nosy: +pitrou ___ Python tracker

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13888] test_builtin failure when run after test_tk

Changes by STINNER Victor : -- components: +Tests, Tkinter -XML ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15923] Building from a fresh clone breaks on Parser/asdl_c.py

STINNER Victor added the comment: See also #15964. -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue15144] Possible integer overflow in operations with addresses and sizes.

STINNER Victor added the comment: > Perhaps the three new macros should be made available in a .h file? Good idea. Maybe pymacros.h? These macros need to be documented (with a comment in the .h file) -- nosy: +haypo ___ Python tracker

[issue13888] test_builtin failure when run after test_tk

STINNER Victor added the comment: "python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed." I get a similar XCB assertion error: "xcb_io.c:221: poll_for_event: Assertion `(((long) (event_sequence) - (long) (dpy->request)) <= 0)' failed." The problem

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

Changes by Brian Curtin : -- assignee: -> bquinlan nosy: +bquinlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

Christian Heimes added the comment: I think this might be related to #15923. It shouldn't be necessary to rebuild the AST definition unless you have modified the grammar and AST files. -- nosy: +christian.heimes ___ Python tracker

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

Changes by Mark Dickinson : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue15903] Make rawiobase_read() read directly to bytes object

Richard Oudkerk added the comment: > Are we talking about a big speedup here or could we perhaps just keep > the existing code? I doubt it is worth the hassle. But I did want to know if there was a clean way to do what I wanted. -- ___ Python track

[issue15903] Make rawiobase_read() read directly to bytes object

Antoine Pitrou added the comment: > Antoine Pitrou wrote: > > I don't think we want to expose a mutable bytes object to outside code, > > so IMO PyMemoryView_FromMemory() is preferrable. > > I agree, but PyMemoryView_FromMemory(PyBytes_AS_STRING(b), n, PyBUF_WRITE) > just hides the fact that a

[issue15954] No error checking after using of the wcsxfrm()

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

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

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

[issue8425] a -= b should be fast if a is a small set and b is a large set

Changes by STINNER Victor : -- versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15956] backreference to named group does not work

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15903] Make rawiobase_read() read directly to bytes object

Stefan Krah added the comment: Antoine Pitrou wrote: > I don't think we want to expose a mutable bytes object to outside code, > so IMO PyMemoryView_FromMemory() is preferrable. I agree, but PyMemoryView_FromMemory(PyBytes_AS_STRING(b), n, PyBUF_WRITE) just hides the fact that a mutable bytes o

[issue15956] backreference to named group does not work

Changes by Amaury Forgeot d'Arc : -- assignee: -> docs@python nosy: +docs@python stage: committed/rejected -> patch review ___ Python tracker ___ ___

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Changes by Arfrever Frehtes Taifersar Arahesis : -- title: AT_FDCWD is 0xffd19553 on Solaris 10,resulting in compiler warnings. -> AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings. ___ Python tracker

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15969] faulthandler: drop S from dump_tracebacks_later() function name to have consistent names

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15903] Make rawiobase_read() read directly to bytes object

Stefan Krah added the comment: Richard Oudkerk wrote: > Should PyMemoryView_Release() release the _PyManagedBufferObject by doing > mbuf_release(view->mbuf) even if view->mbuf->exports > 0? No, I think it should really just be a wrapper: diff --git a/Objects/memoryobject.c b/Objects/memoryobj

[issue15969] faulthandler: drop S from dump_tracebacks_later() function name to have consistent names

New submission from STINNER Victor: If it is not too late, I would like to "fix" the name of two functions of the new faulthandler module before the release of Python 3.3 final. Changes: * dump_tracebacks_later() => dump_traceback_later() * cancel_dump_tracebacks_later() => cancel_dump_traceb

[issue15903] Make rawiobase_read() read directly to bytes object

Antoine Pitrou added the comment: > So I think the combination of PyMemoryView_FromObject() with a call to > PyMemoryView_Release() should indeed work here. I don't think we want to expose a mutable bytes object to outside code, so IMO PyMemoryView_FromMemory() is preferrable. --

[issue15903] Make rawiobase_read() read directly to bytes object

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

[issue15903] Make rawiobase_read() read directly to bytes object

Richard Oudkerk added the comment: > You would need to call memory_release(). Perhaps we can just expose it on the > C-API level as PyMemoryView_Release(). Should PyMemoryView_Release() release the _PyManagedBufferObject by doing mbuf_release(view->mbuf) even if view->mbuf->exports > 0? Doing

[issue15744] missing tests for {RawIO,BufferedIO,TextIO}.writelines

Felipe Cruz added the comment: Updated based on Pitrou comments -- Added file: http://bugs.python.org/file27220/issue15744_v2.patch ___ Python tracker ___ ___

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Vitaly added the comment: > Nothing, except that there are probably other places in the stdlib > where we can get bitten by this bug. Note that this should eventually > be done for another reason, see http://bugs.python.org/issue15918 For greatest benefit, I think that the work-around should be

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

Chris Jerdonek added the comment: To follow up on David's comment, the unit tests in the test suite aren't consistent in their treatment of temp directories (e.g. they don't use a common API or code path). So it may be hard to address this globally short of wiping the entire temp directory (t

[issue15952] format(value) and value.__format__() behave differently with unicode format

Chris Jerdonek added the comment: To clarify, one of the sentences above should have read, "I feel the second sentence of the note *in the patch* was worth adding..." (not the second sentence of the PEP note I quoted). -- ___ Python tracker

[issue15956] backreference to named group does not work

Steve Newcomb added the comment: > I preferred the previous example "" because it's not obvious what > \042\047 is. Yeah, but the example I wrote has an in-pattern backreference and a real reason to use one. In the attached patch, I have changed [\042\047] to [\'\"]. That's certainly clear

[issue15952] format(value) and value.__format__() behave differently with unicode format

Chris Jerdonek added the comment: Here is a proposed patch. One note on the patch. I feel the second sentence of the note is worth adding because value.__format__() departs from what PEP 3101 says: "Note for Python 2.x: The 'format_spec' argument will be either a string object or a unicode ob

[issue15968] Incorporate Tcl/Tk/Tix into the Windows build process

New submission from Jeremy Kloth: This patch incorporates Tcl/Tk/Tix into the MSVC build in the same fashion as OpenSSL has been done. Highlights: - A new project, tcltk, is added that simply calls the Python script build_tkinter.py to build the externals. - New helper module PCbuild/buildlib.

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

R. David Murray added the comment: Cleanup on test failure is supposed to be done. Cleanup on crash or buildbot timeout isn't done as far as I know (and that was a concern I had with the changes made to support.TESTFN and the cwd, but I didn't articulate it very well). If you find tests th

[issue15956] backreference to named group does not work

Amaury Forgeot d'Arc added the comment: Thanks for the patch! The new formulation looks much better, but I'll let a native speaker have another check. Some comments: I preferred the previous example "" because it's not obvious what \042\047 is. And a bullet list would be less heavyweight IMO.

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Larry Hastings added the comment: Lgtm. Trent Nelson wrote: > >Trent Nelson added the comment: > >Easy fix, cast AT_FDCWD to (int): > > >% hg diff >diff -r 3a880d640981 Modules/posixmodule.c >--- a/Modules/posixmodule.c Tue Sep 18 07:21:18 2012 +0300 >+++ b/Modules/posixmodule.c Tue S

[issue15039] module/ found before module.py when both are in the CWD

Changes by Eric V. Smith : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Charles-François Natali added the comment: > What's wrong with working around this bug by reading a smaller amount? > How much data is there supposed to be? Nothing, except that there are probably other places in the stdlib where we can get bitten by this bug. Note that this should eventually be

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

New submission from Trent Nelson: All my slaves' /tmp's are polluted with regrtest fluff. I haven't checked yet, but I presume no cleanup is done if a test/run fails. nitrogen% find /tmp -user cpython 2> /dev/null | wc -l 197 netbsd51-x64-1$ find /tmp -user cpython 2> /dev/null | wc -l 14

[issue15956] backreference to named group does not work

Steve Newcomb added the comment: > But this way exists: (?P=startquote) is what you want. I know how I missed it: I searched for "backref" in the documentation. I did not find it in the discussion of the pattern language, because that word does not appear where contributions are welcome. Se

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

Trent Nelson added the comment: Solaris 10 release (i.e. optimized) build requires the following: ../../src/configure --without-gcc CFLAGS="-v -fsimple=0 -m64 -mt=yes -xbuiltin -xhwcprof -xF -xarch=native -xchip=native -fma=fused -g -xO5 -xlibmil -xlibmopt -xmemalign=8s -xregs=frameptr -xtarge

[issue15903] Make rawiobase_read() read directly to bytes object

Stefan Krah added the comment: Richard Oudkerk wrote: > The documentation is not very helpful. It just says that calls > to PyObject_GetBuffer() must be matched with calls to PyBuffer_Release(). Yes, we need to sort that out, see #15821. -- ___ Pyt

[issue15903] Make rawiobase_read() read directly to bytes object

Stefan Krah added the comment: Richard Oudkerk wrote: > PyObject_GetBuffer(b, &buf, PyBUF_WRITABLE); > view = PyMemoryView_FromBuffer(&buf); > // readinto view > PyBuffer_Release(&buf); > > Would attempts to access a "leaked" reference to view now result in > ValueError("operat

[issue15903] Make rawiobase_read() read directly to bytes object

Richard Oudkerk added the comment: I am rather confused about the ownership semantics when one uses PyMemoryView_FromBuffer(). It looks as though PyMemoryView_FromBuffer() "steals" ownership of the buffer since, when the associated _PyManagedBufferObject is garbage collected, PyBuffer_Release

[issue15956] backreference to named group does not work

Matthew Barnett added the comment: There needed to be a way of referring to named groups in the replacement template. The existing form \groupnumber clearly wouldn't work. Other regex implementations, such as Perl, do have \g and also \k (for named groups). In my implementation I added support

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Changes by Ralf Schmitt : -- nosy: +schmir ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue15896] Sporadic EINVAL in nonblocking pipe os.read when forked child fails on Mac OS

Vitaly added the comment: In the work-around, we need to watch out for what 'man 2 read' on Mac OS refers to as "normal file": == Upon successful completion, read(), readv(), and pread() return the number of bytes actually read and placed in the buffer. *The system guarantees to read th

[issue4711] Wide literals in the table of contents overflow in documentation

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

Michael Foord added the comment: The patch is just waiting for me to look over it and commit. I'll get to it ASAP. -- ___ Python tracker ___

[issue15961] Missing return value in ``system_message``

Éric Araujo added the comment: Thanks for the report and patch. I think a similar issue was reported for distutils2 (maybe only orally, not on this tracker, I have to search). How did you find the bug? In other words, can you add a unit test for this? :) -- components: +Distutils2 n

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

Changes by Éric Araujo : -- nosy: +eric.araujo, loewis versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue15957] README.txt points to broken "contributing" url in python wiki

Éric Araujo added the comment: Thanks for the report. I think the wiki was modified to redirect /thing to /moin/thing some months ago, so it may be the recent hardware migration that broke that. I’ll follow up with the pydotorg-www mailing list (or feel free to do it). -- assignee:

[issue15955] gzip, bz2, lzma: add method to get decompressed size

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

Mark Dickinson added the comment: Here's a patch. The solution is ugly enough that I'm wondering whether this is even worth fixing. -- keywords: +patch Added file: http://bugs.python.org/file27216/futures.patch ___ Python tracker

[issue2286] Stack overflow exception caused by test_marshal on Windows x64

Trent Nelson added the comment: Closing issue; this has been fixed. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-li

[issue15966] concurrent.futures: Executor.submit keyword arguments may not be called 'fn' (or 'self')

New submission from Mark Dickinson: The submit methods of concurrent.futures.ThreadPoolExecutor and concurrent.futures.ProcessPoolExectutor raise TypeError when submitting a callable with a keyword argument named 'fn' or 'self': Python 3.3.0rc2+ (default:3a880d640981, Sep 18 2012, 16:29:28

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Trent Nelson added the comment: Easy fix, cast AT_FDCWD to (int): % hg diff diff -r 3a880d640981 Modules/posixmodule.c --- a/Modules/posixmodule.c Tue Sep 18 07:21:18 2012 +0300 +++ b/Modules/posixmodule.c Tue Sep 18 16:04:58 2012 + @@ -414,7 +414,14 @@ #ifdef AT_FDCWD -#define

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

Changes by R. David Murray : -- nosy: +larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue15965] AT_FDCWD is 0xffd19553 on Solaris 10, resulting in compiler warnings.

New submission from Trent Nelson: On Solaris (s10/nitrogen): % find /usr/include -type f | xargs fgrep -ni AT_FDCWD /usr/include/sys/fcntl.h:320:#defineAT_FDCWD 0xffd19553 (AIX uses -2, FreeBSD uses -100.) Anyway, that results in: (cpython@nitrogen:ttypts/10) (Tu

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Vinay Sajip added the comment: I'm not against making this change, but I'm curious - why would a handler do clean-up I/O in its release() method (which is just for releasing the I/O lock) where it could just as easily override the close() method to do the same thing? It seems like programmer e

[issue15964] SyntaxError in asdl when building 2.7 with system Python 3

New submission from Chris Jerdonek: Building with-- ./configure --with-pydebug && make -j2 errors out after switching branches from default to 2.7 when the system Python is Python 3 (on Mac OS X 10.7.4 using MacPorts). To reproduce: $ sudo port select python python32 $ python No such file or

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9720] zipfile writes incorrect local file header for large files in zip64

Christian Heimes added the comment: Serhiy: If I understand you correctly it should be easy to fix. The code in close() has to check if any file is beyond the ZIP64 limit and then write all headers with extra args. Is that correct? -- keywords: +needs review nosy: +christian.heimes __

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

Trent Nelson added the comment: On the s10 slave (Solaris 10/nitrogen) for 3.x: (cpython@nitrogen:ttypts/4) (Tue/12:32) .. % ../../src/configure --with-pydebug -

[issue15963] Improve ./configure's support for 32/64-bit debug|release|profiled builds w/ vendor (non-gcc) compilers on proprietary UNIX systems (Solaris/HP-UX/AIX et al).

New submission from Trent Nelson: Gripe: if you want a 64-bit, non-gcc (i.e. vendor's cc) build on a proprietary UNIX system (i.e. Solaris, HP-UX, AIX etc), "you're going to have a bad time". Coercing a 64-bit build from a vendor's cc currently requires explicit CFLAGS/LDFLAGS/configure gymnas

[issue9720] zipfile writes incorrect local file header for large files in zip64

Changes by Kristof Keppens : -- nosy: +Kristof.Keppens ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

Changes by Trent Nelson : -- title: Numerous utime ns tests fail on FreeBSD w/ ZFS -> Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS) ___ Python tracker _

[issue15903] Make rawiobase_read() read directly to bytes object

Richard Oudkerk added the comment: The current non-test uses of PyMemoryView_FromBuffer() are in _io.BufferedReader.read(), _io.BufferedWriter.write(), PyUnicode_Decode(). It looks like they can each be made to leak a memoryview that references a deallocated buffer. (Maybe the answer is Don't

[issue8425] a -= b should be fast if a is a small set and b is a large set

Changes by Michele Orrù : -- nosy: +maker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue15962] Windows STDIN/STDOUT Redirection is actually FIXED

Changes by Ezio Melotti : -- keywords: +easy nosy: +brian.curtin, terry.reedy, tim.golden stage: -> needs patch type: -> enhancement versions: -Python 2.6, Python 3.1 ___ Python tracker _

[issue15962] Windows STDIN/STDOUT Redirection is actually FIXED

New submission from Nacsa Kristóf: The Python docs faq says that due to a bug in Windows NT's cmd.exe, the output redirection and piping won't work when started from file extension. http://docs.python.org/faq/windows.html#how-do-i-make-python-scripts-executable http://docs.python.org/py3k/faq/w

[issue15961] Missing return value in ``system_message``

New submission from Malthe Borch: When ``docutils`` are importable, distutils uses a reporter implementation that incorrectly drops a return value from the ``system_message`` override (see patch). -- assignee: eric.araujo components: Distutils files: patch.diff keywords: patch messages

[issue15903] Make rawiobase_read() read directly to bytes object

Richard Oudkerk added the comment: > Then the view owns a reference to the bytes object. But that does not > solve the problem that writable memoryviews based on a readonly object > might be hanging around. How about doing PyObject_GetBuffer(b, &buf, PyBUF_WRITABLE); view = PyMemoryView

[issue15903] Make rawiobase_read() read directly to bytes object

Stefan Krah added the comment: So the problem is that readinto(view) might result in several references to view? I don't think that can be solved on the memoryview side. One could do: view = PyMemoryView_FromObject(b); // Lie about writability ((PyMemoryViewObject *)view)->view.readonl

  1   2   >