[issue8151] [patch] convenience links for subprocess.call()

Changes by anatoly techtonik : -- versions: +Python 2.6, Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > Reverted in 3.x: it triggers some failures. > > Symptoms: > * repr('\uaaa') gives an empty string > * test_bigmem fails repr() for Unicode doesn't use the Unicode database. Are you sure

[issue3690] sys.getsizeof wrong for Py3k bool objects

Mark Dickinson added the comment: I don't think there's anything worth fixing here. It's true that getsizeof is sometimes going to return results that are too small, because there are a good few places in the longobject internals where it's not predictable in advance exactly how much space i

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: The bug was a side-effect of the update. Code point "\u" is now assigned to a printable character: ;TAI VIET LETTER LOW VO;Lo;0;L;N; And test_bigmem relies on this code point being non-printable. I changed it for a char in the Low surrogate

[issue8048] doctest assumes sys.displayhook hasn't been touched

Noam Yorav-Raphael added the comment: Here is a better and much shorter patch: I use sys.__displayhook__ instead of implementing it in Python, which has the nice side effect of not changing pdb behaviour. -- Added file: http://bugs.python.org/file16581/patch _

[issue3690] sys.getsizeof wrong for Py3k bool objects

Martin v. Löwis added the comment: Closing this as "won't fix", then. -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ __

[issue8024] upgrade to Unicode 5.2

Amaury Forgeot d'Arc added the comment: > Looking closer at the patch, you also changed the unicodetype mappings > and since this removes a lot of entries, it looks like the Unicode > consortium either moved some mappings out of the UCD file into a > separate file or made some massive changes to

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > The bug was a side-effect of the update. Code point "\u" is now assigned > to a printable character: > > ;TAI VIET LETTER LOW VO;Lo;0;L;N; > > And test_bigmem relies on

[issue8024] upgrade to Unicode 5.2

Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > >> Looking closer at the patch, you also changed the unicodetype mappings >> and since this removes a lot of entries, it looks like the Unicode >> consortium either moved some mappi

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Changes by Ned Deily : -- versions: +Python 3.1 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: Per discussion with Ronald and Benjamin, attaching a revised patch (issue-sl-configure-32-31-rev3.txt) for 3.1 which ports the changes committed in r78813 and r78816 along with the Mac/README changes. In the process of producing the revised 3.1 patch, I discovered

[issue8175] 2.6.5 OS X 10.5 --with-universal-archs=all (4-way) fails building pythonw-64

New submission from Ned Deily : A change made to Mac/Makefile in r78813 for 2.6.5 does not work correctly when the --with-universal-archs=all (4-way) framework configure option is selected. The build of pythonw-64 fails with an incorrect gcc command: "gcc-4.0 64 -arch x86_64". The attached

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Ned Deily added the comment: (2.6.5 -> Issue8175) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8176] Interpreter crash with "double free or corruption" message

New submission from Carlos Ribeiro : I was running Django in development mode (python manage.py runserver 0.0.0.0:8002). I saved a python source file; Django automatically detected the change and reloaded the module (that's the usual behavior). Then a backtrace from glibc appeared in the middl

[issue8176] Interpreter crash with "double free or corruption" message

STINNER Victor added the comment: Python was displaying an error: did you saw the error? I don't know where Django logs stderr. Could you also run Python in verbose mode? Set PYTHONVERBOSE=2 environment variable. It should write useful informations before the crash. -- nosy: +haypo

[issue8142] libffi update to 3.0.9

Ned Deily added the comment: (Adding Ronald for OS X.) -- nosy: +ned.deily, ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list

[issue8176] Interpreter crash with "double free or corruption" message

Carlos Ribeiro added the comment: I know I have little information but unfortunately I couldn't reproduce the crash. Seems like a racing condition or something similar. I'll see what I can do about it. On Fri, Mar 19, 2010 at 07:46, STINNER Victor wrote: > > STINNER Victor added the comment:

[issue6081] str.format_from_mapping()

Eric Smith added the comment: I believe this patch fixes the issue. Tests and documentation are still needed, of course. -- Added file: http://bugs.python.org/file16585/issue6081.diff ___ Python tracker __

[issue6081] str.format_from_mapping()

Eric Smith added the comment: Added a comment to explain the change. -- Added file: http://bugs.python.org/file16586/issue6081.diff ___ Python tracker ___ ___

[issue6081] str.format_from_mapping()

Changes by Eric Smith : Removed file: http://bugs.python.org/file16585/issue6081.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue3135] inspect.getcallargs()

Changes by George Sakkis : Removed file: http://bugs.python.org/file16579/getcallargs.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3135] inspect.getcallargs()

George Sakkis added the comment: Renamed the Testcase classes to conform with the rest in test_inspect.py, added a few more tests for tuple args and patched against the latest trunk (r79086). -- Added file: http://bugs.python.org/file16587/getcallargs.patch ___

[issue3135] inspect.getcallargs()

Benjamin Peterson added the comment: The patch will also need docs in inspect.rst. -- nosy: +benjamin.peterson ___ Python tracker ___

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Merged with r79093 -- resolution: accepted -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue8154] os.execlp('true') crashes the interpreter on 2.x

Matthias Klose added the comment: commited to the trunk, commit to the 2.6 branch pending -- ___ Python tracker ___ ___ Python-bugs-li

[issue8142] libffi update to 3.0.9

Matthias Klose added the comment: On 18.03.2010 16:44, Thomas Heller wrote: > > Thomas Heller added the comment: > >> the ports which are maintained separately still need an update: >> >> libffi_msvc >>libffi trunk now has a port to x86/msvc. might require some >>extra updates from li

[issue7860] 32-bit Python on 64-bit Windows reports incorrect architecture

Brian Curtin added the comment: #7347 depends on this for proper testing, and arch_misrepresented.diff seems to have been labeled as acceptable. Would anyone be willing to check it in? -- ___ Python tracker __

[issue8177] Incoherent error with keyword argument follow by unpacking argument lists

New submission from Ghislain Hivon : Take a fonction with a parameter and *args def foo(bar, args*) pass then call it like this myargs = [1, 2, 3, 4, 5] foo(bar=1, *myargs) The call produce this error : TypeError: foo() got multiple values for keyword argument 'bar' Sould the error be more

[issue8151] [patch] convenience links for subprocess.call()

Brian Curtin added the comment: This was fixed in r78206 for trunk, but it doesn't look like it made it's way into any of the other branches. -- nosy: +brian.curtin priority: -> low type: -> behavior ___ Python tracker

[issue6474] Inconsistent TypeError message on function calls with wrong number of arguments

George Sakkis added the comment: Which version are you running ? I don't get the "positional" word in 2.6 and 2.7a4. In my opinion it should report how many required arguments are passed, regardless of how they are passed (positionally or by name). So in your example it should say "1 given"

[issue8142] libffi update to 3.0.9

Thomas Heller added the comment: > We should revert the following chunk for configure.ac to generate the > Makefile's again, so that we are able to run the testsuite at least with > dejagnu: > > -AC_CONFIG_FILES(include/Makefile include/ffi.h Makefile testsuite/Makefile > man/Makefile libffi

[issue8173] test_subprocess leaks

Gregory P. Smith added the comment: py3k r79097 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs

[issue6474] Inconsistent TypeError message on function calls with wrong number of arguments

George Sakkis added the comment: Attached patch for displaying the number of missing required arguments. -- keywords: +patch Added file: http://bugs.python.org/file16589/6474.patch ___ Python tracker __

[issue8142] libffi update to 3.0.9

Matthias Klose added the comment: > Can you make this change, run autoconf, and commit please? done, and updated the patch for the merge from the trunk. -- Added file: http://bugs.python.org/file16590/libffi-update3.diff ___ Python tracker

[issue8142] libffi update to 3.0.9

Changes by Matthias Klose : Removed file: http://bugs.python.org/file16588/libffi-update2.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue3135] inspect.getcallargs()

George Sakkis added the comment: - Added docs in inspect.rst - Fixed TypeError message for zero-arg functions ("takes no arguments" instead of "takes exactly 0 arguments") + added test. -- Added file: http://bugs.python.org/file16591/getcallargs2.patch

[issue8142] libffi update to 3.0.9

Thomas Heller added the comment: > done, and updated the patch for the merge from the trunk. > > -- > Added file: http://bugs.python.org/file16590/libffi-update3.diff This patch passes the ctypes tests and libffi testsuite on this system: Linux tubu64 2.6.24-27-generic #1 SMP Fri Ma

[issue8133] test_imp fails on OS X 10.6; filename normalization issue.

Changes by Benjamin Peterson : -- assignee: -> brett.cannon priority: -> release blocker ___ Python tracker ___ ___ Python-bugs-list

[issue3135] inspect.getcallargs()

Benjamin Peterson added the comment: Would you upload this patch to Rietveld for review? -- ___ Python tracker ___ ___ Python-bugs-lis

[issue6081] str.format_from_mapping()

Filip Gruszczyński added the comment: Could you point me, where to add tests and documentation? I would happily add those. -- ___ Python tracker ___

[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6

Benjamin Peterson added the comment: Fixed 3.1 in r79117. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ P

[issue8133] test_imp fails on OS X; filename normalization issue.

Ned Deily added the comment: (BTW, the problem exists on other versions of OS X, not just 10.6.) -- title: test_imp fails on OS X 10.6; filename normalization issue. -> test_imp fails on OS X; filename normalization issue. ___ Python tracker

[issue8068] OS X Installer: merge python2 and python3 build-installer.py script

Benjamin Peterson added the comment: I applied the update in r79119. Thanks! -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6081] str.format_from_mapping()

Eric Smith added the comment: http://docs.python.org/library/stdtypes.html#str.format, for starters. This is in Doc/library/stdtypes.rst. For tests, probably in Lib/test/test_unicode.py. I'm not sure if we should add this to 2.7 (or even 3.2, for that matter), but if so, we should start by p

[issue2698] Extension module build fails for MinGW: missing vcvarsall.bat

Tarek Ziadé added the comment: Done for 3.1.x in r79121. I am now waiting for 3.1.2 to be taggued, then I'll revert the 3.x branch into a state the closest possible to 3.1.x. Next, Distutils will be feature-frozen in 3.x like it is in 2.x, as things are now happening in distutils2. Only bugs

[issue3135] inspect.getcallargs()

George Sakkis added the comment: Uploaded at http://codereview.appspot.com/659041/show -- ___ Python tracker ___ ___ Python-bugs-list

[issue6081] str.format_from_mapping()

Filip Gruszczyński added the comment: Ok, unfortunately this code won't work for certain tests. Take those: self.assertEqual("My name is {0}".format('Fred'), "My name is Fred") We pass only one argument, which is a dict and this won't satisfy such test. We need to think about a differ

[issue4892] Sending Connection-objects over multiprocessing connections fails

Changes by Stein Magnus Jodal : -- nosy: +jodal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7755] copyright clarification for audiotest.au

Changes by Barry A. Warsaw : -- priority: deferred blocker -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue3928] os.mknod missing on Solaris

Changes by Barry A. Warsaw : -- priority: deferred blocker -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8178] test_thread fails on POSIX

New submission from Florent Xicluna : The test fails randomly on POSIX platforms since r78527 (fixing issue #7242). The failure is in the new TestCase: TestForkInThread. $ ./python -m test.regrtest -uall -R :: test_thread test_thread beginning 9 repetitions 123456789 Unhandled exception in thr

[issue8178] test_thread fails on POSIX

Florent Xicluna added the comment: Fixed with r79127 and r79128. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: +Python 3.2 ___ Python tracker ___

[issue7860] 32-bit Python on 64-bit Windows reports incorrect architecture

R. David Murray added the comment: I think it is actually pretty straightforward to write a *unit* test for this. We just need to check that the logic works correctly given the expected presence or absence of the environment variables. That doesn't test whether or not the right thing happen

[issue2548] Undetected error in exception handling

Sean Reifschneider added the comment: The final word on this seems to be this: - Wait until when we aren't in a beta release. (DONE) - Quoting: Well, For Py3K at least we might need to consider going through the C API and fixing it so that these incorrect assumptions that functio

[issue8154] os.execlp('true') crashes the interpreter on 2.x

Matthias Klose added the comment: committed to the 2.6 branch as well -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue7443] test.support.unlink issue on Windows platform

Sean Reifschneider added the comment: Andrew: There have been changes committed within the last week to #7712, which Florent suggested might be related. Can you please re-test this to see if it still exists, and if it does, bug me and I'll try to get some more movement on this. -- n

[issue4961] Inconsistent/wrong result of askyesno function in tkMessageBox

Matthias Klose added the comment: committed to the 2.6 branch as well -- assignee: gpolo -> status: pending -> closed ___ Python tracker ___

[issue7356] parsing of ldconfig output in ctypes/utils.py depends on the locale

Matthias Klose added the comment: committed to the 2.6 branch as well -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue2356] fixer for sys.exitfunc -> atexit

Sean Reifschneider added the comment: I've posted to python-dev asking for a reviewer for this, the thread is at http://mail.python.org/pipermail/python-dev/2010-March/098597.html -- nosy: +jafo ___ Python tracker

[issue2356] fixer for sys.exitfunc -> atexit

Benjamin Peterson added the comment: Sean, are you referring to the warning or the 2to3 fixer? -- ___ Python tracker ___ ___ Python-bu

[issue2356] fixer for sys.exitfunc -> atexit

Changes by Benjamin Peterson : -- assignee: collinwinter -> benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8179] Test failure in test_macpath.py test_realpath (Mac OS X)

New submission from Michael Foord : On Mac OS X 10.6.2 == ERROR: test_realpath (__main__.MacCommonTest) -- Traceback (most recent call last): File "/compile/

[issue8180] Unicode File Test failures (PEP 277 on Mac OS X)

New submission from Michael Foord : I'm *assuming* this is a Mac OS X issue. (10.6.2) ./python.exe Lib/test/test_pep277.py test_directory (__main__.UnicodeFileTests) ... ok test_failures (__main__.UnicodeFileTests) ... ok test_listdir (__main__.UnicodeFileTests) ... FAIL test_open (__main__.Unic

[issue8180] Unicode File Test failures (PEP 277 on Mac OS X)

Changes by Michael Foord : -- stage: -> needs patch versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail

Michael Foord added the comment: Committed in revision 79132. For Python 2.7 I renamed assertSameElements to assertItemsEqual (assertSameElements has never been released on 2.X). In 3.2 assertItemsEqual will be new and assertSameElements will be de-documented / deprecated. -- __

[issue5649] OS X Installer: only include PythonSystemFixes package if target includes 10.3

Ned Deily added the comment: With the installer build updates referenced by Issue8068, PythonSystemFixes is now only included in installers targeted for 10.3. -- status: open -> closed ___ Python tracker _

[issue7347] Add {Create|Delete}KeyEx to _winreg, doc and test updates

Gabriel Genellina added the comment: Why the *Ex names? Can't we just add additional arguments to the original names? The Python names do not necesarily have to match the API calls. Having QueryValue and QueryValueEx was a mistake in the first place, and I would prefer not continuing doing su

[issue8179] Test failure in test_macpath.py test_realpath (Mac OS X)

Ned Deily added the comment: This failure seems to be caused by major changes to test_macpath. I'm not sure how much of this is really applicable to macpath which implements the obsolete MacOS 9 path functions. Perhaps leave well enough alone? -- nosy: +flox, ned.deily

[issue8180] Unicode File Test failures (PEP 277 on Mac OS X)

Ned Deily added the comment: r78585 to test_pep277.py recently enabled this test for all POSIX systems but note the warning in r33595. -- nosy: +flox, ned.deily ___ Python tracker _