[issue7228] %lld for PyErr_Format (Modules/_io/bufferedio.c)

Hirokazu Yamamoto added the comment: I think your patch is correct. (I couldn't check the behavior on error condition itself, because I wasn't sure how, but I checked test_io run on windows) -- ___ Python tracker _

[issue7387] More precise document on os.path.normpath()

Changes by Benjamin Peterson : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7383] test_multiprocessing leaks

R. David Murray added the comment: This started just after r76438, which is an additional test for multiprocessing. Given build delays this is only a correlation not a definite cause, but it is suspicious. -- nosy: +r.david.murray ___ Python tracker

[issue7387] More precise document on os.path.normpath()

New submission from pengyu.ut : os.path.normpath() doesn't return the trailing '/', if the path is a directory. But the document doesn't mention this fact. I recommend document this feature. -- assignee: georg.brandl components: Documentation messages: 95662 nosy: georg.brandl, pengyu.u

[issue7386] More precise document on os.path.normpath()

New submission from pengyu.ut : os.path.normpath() doesn't return the trailing '/', if the path is a directory. But the document doesn't mention this fact. I recommend document this feature. -- assignee: georg.brandl components: Documentation messages: 95661 nosy: georg.brandl, pengyu.u

[issue7385] MemoryView_FromObject crashes if PyBuffer_GetBuffer fails

New submission from Pauli Virtanen : In Objects/memoryobject.c:PyMemoryView_FromObject there's a _PyObject_GC_UNTRACK unpaired with corresponding _PyObject_GC_TRACK, which seems to cause a segmentation fault. This can be triggered by calling PyMemoryView_FromObject on an object whose bf_getbuffer

[issue7372] Regression in pstats

Alexander Belopolsky added the comment: It would be fairly easy to change format before dumping stats to disk, but unfortunately Profile does not encapsulate it's run-time data and changing its format would be a mess. Of course, one can hack around that by turning Profile.stats into a computed

[issue7117] Backport py3k float repr to trunk

Mark Dickinson added the comment: r76474: Remove %f -> %g switch. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue7372] Regression in pstats

Georg Brandl added the comment: Alexander, how hard would it be to change the profile output? -- ___ Python tracker ___ ___ Python-bug

[issue7383] test_multiprocessing leaks

Jesse Noller added the comment: AFAIK; I haven't changed anything which would introduce refleaks in the code. So, it's going to be a matter of chasing down all of the changes since the refleaks popped up and see which one triggered it. -- ___ Pytho

[issue7128] cPickle looking for non-existent package copyreg

Georg Brandl added the comment: Patch looks ok to me, do you want to apply it? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue644744] bdist_rpm fails when installing man pages

Toshio Kuratomi added the comment: Agreed. The substitution is still needed. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: Patch could be applied to Python 2.6 and trunk too. -- versions: +Python 2.6, Python 2.7 ___ Python tracker ___ __

[issue7384] test_curses crash on FreeBSD buildbots

New submission from Mark Dickinson : test_curses is currently causing the test runs to abort on the FreeBSD 6.4 and 7.2 buildbots. I can reproduce this on a FreeBSD 7.2 /amd64 machine by doing ./python Lib/test/regrtest.py -uall test___all__ test_curses This dumps core, and the traceback poin

[issue7345] calendar.TextCalendar().formatyear wrong argument list

Georg Brandl added the comment: Fixed in r76471. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue6071] no longer possible to hash arrays

Antoine Pitrou added the comment: > As for the checks for bf_releasebuffer: I still think they are > necessary. If an object implements bf_releasebuffer, that means that the > object may change the buffer underneath, unless proper locking and > unlocking takes place. I know, but the problem is

[issue7383] test_multiprocessing leaks

New submission from Antoine Pitrou : This has started a few days ago. I don't know if this was triggered by a multiprocessing change or an unrelated one. On trunk: test_multiprocessing beginning 6 repetitions 123456 .. test_multiprocessing leaked [277, 277, 277] references, sum=831 On py3k:

[issue644744] bdist_rpm fails when installing man pages

Thomas Vander Stichele added the comment: Hi Toshio, I'd probably also go for the wildcarding, but you'd still need to 'change' the INSTALLED_FILES file to do so, so you'd still use the same mechanism. -- ___ Python tracker

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by flox : Removed file: http://bugs.python.org/file15391/issue7376_usage.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by flox : Added file: http://bugs.python.org/file15392/issue7376_usage.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: Patch proposed. -- Added file: http://bugs.python.org/file15391/issue7376_usage.diff ___ Python tracker ___ __

[issue1488943] difflib.Differ() doesn't always add hints for tab characters

Senthil Kumaran added the comment: fixed r76469 (py3k) and r76470(release31-maint). Closing the issue. -- status: open -> closed ___ Python tracker ___ ___

[issue1488943] difflib.Differ() doesn't always add hints for tab characters

Senthil Kumaran added the comment: merged to 26-maint in revision 76468 and shall merge in py3k too. -- ___ Python tracker ___ ___

[issue7117] Backport py3k float repr to trunk

Mark Dickinson added the comment: r76465 removes the fixed-length buffer for formatting floats, hence removes the restriction on the precision. This should make removal of the %f -> %g switch straightforward. -- ___ Python tracker

[issue644744] bdist_rpm fails when installing man pages

Toshio Kuratomi added the comment: sed is one of the programs we assume is always present when we build packages in Fedora which is probably also what is wanted here. (A default install of Fedora will include sed but someone might be able to create a minimal install that did not include it.) No

[issue1488943] difflib.Differ() doesn't always add hints for tab characters

Senthil Kumaran added the comment: Yes, I noticed the issue and found the patch to be good as well. Unfortunate it was pending for a long time. Fixed and Committed revision 76464 (trunk). -- assignee: -> orsenthil nosy: +orsenthil resolution: -> fixed

[issue1222585] C++ compilation support for distutils

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

[issue1222585] C++ compilation support for distutils

Michael Droettboom added the comment: Here's another patch against release25_maint for the benefit of those still using Python 2.5. It's different only in some whitespace changes. -- Added file: http://bugs.python.org/file15390/py25_cxx_compiler.patch _

[issue7380] uuid.UUID.bytes gives a bytearray() instead of bytes

Changes by flox : Removed file: http://bugs.python.org/file15385/issue7380_uuid.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue1222585] C++ compilation support for distutils

Michael Droettboom added the comment: Attached is a patch against the release26-maint branch. This works for me on Sun Workshop 6. Note that on Sun, the C compiler is 'cc' and the C++ compiler is 'CC', but distutils uses 'cc' and 'c++'. However, the CXX environment variable now works (after a

[issue7380] uuid.UUID.bytes gives a bytearray() instead of bytes

flox added the comment: Patch with documentation included. (branches/py3k) -- assignee: -> georg.brandl components: +Documentation nosy: +georg.brandl Added file: http://bugs.python.org/file15388/issue7380.diff ___ Python tracker

[issue7371] Windows 64-bit build "skips" several projects in VS 2008

Sridhar Ratnakumar added the comment: [...] Step 6. Build Solution The OS was 64-bit Windows XP (w/ Service Pack 2). Are you sure you were running a 64-bit operating system (i.e., not cross-compiling)? -- ___ Python tracker

[issue7369] Fibonacci example does not include 0; section 4.6

Mark Dickinson added the comment: Fixed in r76460 through r76463. -- resolution: -> fixed status: open -> closed versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: Forget the "python2.5 -m doctest /usr/lib/python2.5/subprocess.py" in first message msg95625. This command does not do what I guessed. And there's no doctest in the Python2.5 "subprocess" module. The attached patch may be enough to fix the docstring inconsistencies with

[issue7379] Docstring for fractions.Fraction.limit_denominator fails

Mark Dickinson added the comment: Thanks for the report! Fixed in r76456 through r76459. -- nosy: +mark.dickinson resolution: -> fixed status: open -> closed versions: +Python 2.6, Python 2.7 -Python 3.0 ___ Python tracker

[issue7382] bytes.__getnewargs__ is broken; copy.copy() therefore doesn't work on bytes, and bytes subclasses can't be pickled by default

R. David Murray added the comment: Confirmed on py3k trunk. We no longer do bug fixes in 3.0, which is why I'm removing it from versions. -- keywords: +easy nosy: +r.david.murray priority: -> high stage: -> test needed versions: +Python 3.2 -Python 3.0 __

[issue1222585] C++ compilation support for distutils

Michael Droettboom added the comment: I'm testing this against release25_maint and release26_maint as we speak. I'll post new patches when that's done. -- ___ Python tracker

[issue7382] bytes.__getnewargs__ is broken; copy.copy() therefore doesn't work on bytes, and bytes subclasses can't be pickled by default

New submission from Sebastian Hagen : In either python 3.0, bytes instances cannot be copied, and (even trivial) bytes subclasses cannot be unpickled unless they explicitly override __getnewargs__() or __reduce_ex__(). Copy problem: >>> import copy; copy.copy(b'foo') Traceback (most recent call

[issue1222585] C++ compilation support for distutils

Tarek Ziadé added the comment: Has someone tried to apply it with a recent Python ? I can work on it but I'll need some help from someone matplotlib or Sage I guess.. -- assignee: -> tarek ___ Python tracker _

[issue7371] Windows 64-bit build "skips" several projects in VS 2008

Martin v. Löwis added the comment: I can't reproduce this. If I do your steps 1 to 5, *nothing* is build - not surprisingly, since these steps don't invoke a build at all. When I then select, in the context menu of "Solution 'pcbuild'", the menu item "Build solution", it builds everything. Als

[issue1222585] C++ compilation support for distutils

Michael Droettboom added the comment: This is a rather serious bug for matplotlib -- since the C++ compiler is not correctly selected, it can't be built with many Unix compilers, such as Sun Studio. -- nosy: +mdboom ___ Python tracker

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

flox added the comment: I am ok with the proposal of removing the current "selftest" default behavior. And thank you for the tip. I tried the command "python -m doctest Lib/*.py" and I found interesting things: * #7379 about Lib/fractions.py * #7380 about Lib/uuid.py * #7381 about Lib/subpro

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: It may be fixed with "# doctest: +ELLIPSIS" and "# doctest: +SKIP" directives... But it is probably platform-dependent. I have tested only with Debian Lenny. -- ___ Python tracker _

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

flox added the comment: I fixed the docstring inconsistency (see patch) and some obvious things. But I still have errors. ~ $ python3 -m doctest py3_failed/subprocess.py ** File "py3_failed/subprocess.py", line 139, in subpro

[issue7381] subprocess.check_output: "docstring has inconsistent leading whitespace"

New submission from flox : I've tested the docstring of the module subprocess. Python 2.5 is OK, but Python 3.1 fails. ~ $ python2.5 -m doctest /usr/lib/python2.5/subprocess.py ... -- Ran 15 tests in 0.012s OK ~ $ p

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Marc-Andre Lemburg added the comment: Eric pointed me to this ticket after having raised the question on python-dev: http://www.mail-archive.com/python-...@python.org/msg43841.html I think the discussion should be continued there instead of on this ticket. Just for completeness, I'm copying my

[issue7380] uuid.UUID.bytes gives a bytearray() instead of bytes

flox added the comment: Attached patch gives coherence: * both UUID.bytes and UUID.bytes_le return a "bytes" object * the random tests are explicitly skipped Then the documentation needs fixing, too. -- keywords: +patch Added file: http://bugs.python.org/file15385/issue7380_uuid.diff

[issue7380] uuid.UUID.bytes gives a bytearray() instead of bytes

New submission from flox : I've tried some experiments with module uuid, and I meet some inconsistencies between the documentation, the docstring and the real behavior of the module. An interactive session is worth a thousand words: >>> import uuid >>> uuid.UUID(bytes='\x12\x34\x56\x78'*4) Trac

[issue7353] cporting docs recommend using Include/intobject.h, which was removed in 3.1?

Eric Smith added the comment: MvL made this comment in http://www.mail-archive.com/python-...@python.org/msg43844.html I'm copying it here so it doesn't get lost and because I think he makes a good point that many people would miss (at least I didn't think of it). --

[issue7379] Docstring for fractions.Fraction.limit_denominator fails

New submission from flox : Yes, you can reduce the fraction 1234/5678. Bad Luck :p ~ $ python3 -m doctest /usr/lib/python3.1/fractions.py ** File "/usr/lib/python3.1/fractions.py", line 165, in fractions.Fraction.limit_denomina

[issue644744] bdist_rpm fails when installing man pages

Tarek Ziadé added the comment: I'd rather see sed called from within Distutils. But I am not sure how to handle it after install has been called. Do you know if sed is *always* present on a fresh Fedora ? (I am nosying Toshio as well) -- assignee: -> tarek nosy: +a.badger type: -> b

[issue7376] "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner

Changes by R. David Murray : -- title: FAIL: Doctest: __main__.DebugRunner -> "python -m doctest" results in FAIL: Doctest: __main__.DebugRunner ___ Python tracker ___ __

[issue7376] FAIL: Doctest: __main__.DebugRunner

R. David Murray added the comment: python -m doctest does accept file arguments. Running the self-test is the default if no arguments are supplied. python -m doctest Lib/doctest.py passes. So perhaps we should just remove the default and instead issue an error message about missing arguments.

[issue7378] unexpected truncation of traceback

New submission from Greg Hewgill : Quite by accident, I came across a case where Python would quit generating traceback text and skip printing the actual exception information. Here is a sample program: exec(compile("spam()", ".", "exec")) and the output in Python 3.1 ("spam" is undefined):

[issue644744] bdist_rpm fails when installing man pages

Thomas Vander Stichele added the comment: Attaching a reworked patch of the patch attached in http://bugs.python.org/issue1169193 This worked for me on f-11, with python 2.6 -- keywords: +patch nosy: +thomasvs Added file: http://bugs.python.org/file15383/distutils.bdist_rpm.patch

[issue6071] no longer possible to hash arrays

Martin v. Löwis added the comment: I think the error is really in _hashlib, not in the array object. It should not require 3.x style buffers, but continue to support 2.x readbuffers. Attached is a patch that takes this route to fixing the bug. As for the checks for bf_releasebuffer: I still thi