[issue7564] test_ioctl may fail when run in background

Changes by Florent Xicluna : -- assignee: -> flox priority: low -> normal versions: -Python 2.6, Python 3.1 ___ Python tracker <http://bugs.python.org/

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Florent Xicluna added the comment: With ET 1.3, you should have an explicit keyword argument "xml_declaration": # if xml_declaration or (xml_declaration is None and encoding not in ("utf-8", "us-ascii")):

[issue1731717] race condition in subprocess module

Florent Xicluna added the comment: Previous buildbot failures were in test_multiprocessing: http://bugs.python.org/issue1731717#msg100430 Now it should be fixed: - r78777, r78787, r78790 on 2.x - r78798 on 3.x -- resolution: -> fixed stage: test needed -> committed/rejected

[issue7805] test_multiprocessing failure

Florent Xicluna added the comment: This last bug is fixed, too. http://bugs.python.org/issue1731717#msg100643 -- status: pending -> closed ___ Python tracker <http://bugs.python.org/iss

[issue2777] subprocess unit tests for kill, term and send_signal flaky

Florent Xicluna added the comment: All this flakiness is fixed: - r78736, r78759, r78761, r78767, r78788, r78789 on 2.x - r78797 on 3.x Note: because of #3137, the send_signal(SIGINT) is retried 2 times on some platforms. -- resolution: -> fixed stage: patch review -> com

[issue1731717] race condition in subprocess module

Florent Xicluna added the comment: >>> import subprocess, signal >>> signal.signal(signal.SIGCLD, signal.SIG_IGN) 0 >>> subprocess.Popen(['echo','foo']).wait() foo Traceback (most recent call last): File "", line 1, in Fi

[issue1731717] race condition in subprocess module

Changes by Florent Xicluna : -- keywords: -buildbot ___ Python tracker <http://bugs.python.org/issue1731717> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7624] isinstance(... , collections.Callable) fails with oldstyle class instances

Florent Xicluna added the comment: Fixed in r78800. Additional tests backported to 3.x. -- resolution: accepted -> fixed stage: commit review -> committed/rejected status: open -> closed title: isinstance(... ,collections.Callable) fails with oldstyle class i nstances ->

[issue8088] assertSameElements fails with sequences that contain unorderable types

Changes by Florent Xicluna : -- keywords: +patch resolution: -> accepted stage: needs patch -> patch review Added file: http://bugs.python.org/file16495/issue8088_unordered_elements.diff ___ Python tracker <http://bugs.python.org/

[issue8088] assertSameElements fails with sequences that contain unorderable types

Florent Xicluna added the comment: Patch against trunk. -- ___ Python tracker <http://bugs.python.org/issue8088> ___ ___ Python-bugs-list mailing list Unsub

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Florent Xicluna added the comment: So we keep buffer() as the standard way to create BLOBs for 2.x? It is the only use of "py3k deprecated" buffer() which cannot be replaced in 2.x. Set to "release blocker" until a decision is made. -- priority: critica

[issue1530559] struct.pack raises TypeError where it used to convert

Florent Xicluna added the comment: I would suggest to raise a py3k warning instead of a plain warning. AFAIU the implicit conversion is OK in 2.7, and it is removed in 3.x. -- nosy: +flox ___ Python tracker <http://bugs.python.org/issue1530

[issue8088] assertSameElements fails with sequences that contain unorderable types

Florent Xicluna added the comment: It could be fixed as part of #7832. -- superseder: -> assertSameElements([0, 1, 1], [0, 0, 1]) does not fail ___ Python tracker <http://bugs.python.org/iss

[issue8088] assertSameElements fails with sequences that contain unorderable types

Changes by Florent Xicluna : -- status: open -> pending ___ Python tracker <http://bugs.python.org/issue8088> ___ ___ Python-bugs-list mailing list Unsubscri

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

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16087/issue7832_assertItemsEqual.diff ___ Python tracker <http://bugs.python.org/issue7832> ___ ___

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

Florent Xicluna added the comment: Patch with documentation, tests, Misc/NEWS, following a discussion with Michael, Ezio and JP. -- priority: low -> normal Added file: http://bugs.python.org/file16500/issue7832_assertSameElements_v2.d

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

Florent Xicluna added the comment: Gregory P. Smith wrote: > Looking through the thousands of uses of assertSameElements in our internal > code base at work I see many uses of it that are likely not hashable items > in the sequences being compared. The method assertSameElements w

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

Changes by Florent Xicluna : -- priority: low -> normal ___ Python tracker <http://bugs.python.org/issue7832> ___ ___ Python-bugs-list mailing list Unsubscri

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16075/issue7092_py3k_warnings_args_v2.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16076/issue7092_py3k_warnings_noargs_v2.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16113/issue7092_test_support_v2.diff ___ Python tracker <http://bugs.python.org/issue7092> ___ ___

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Florent Xicluna added the comment: Silence the last warnings, using check_py3k_warnings. But we could provide a smaller patch, if #7832 is fixed before. -- dependencies: +assertSameElements([0, 1, 1], [0, 0, 1]) does not fail Added file: http://bugs.python.org/file16507

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

Florent Xicluna added the comment: Some real use case for the fixed behavior: - the patch for #7092 has a workaround to fix the comparison locally, both in test_decimal and test_set - test_cgi was changed, before noticing that SameElements has a flaw: http://svn.python.org/view/python

[issue8091] TypeError at the end of 'make test'

Changes by Florent Xicluna : -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue8091> ___ ___ Python-bugs-list mailing list Unsubscri

[issue5099] subprocess.POpen.__del__() AttributeError (os module == None!)

Changes by Florent Xicluna : -- nosy: +flox versions: +Python 3.2 -Python 3.0 ___ Python tracker <http://bugs.python.org/issue5099> ___ ___ Python-bugs-list mailin

[issue8091] TypeError at the end of 'make test'

Changes by Florent Xicluna : -- resolution: -> duplicate status: pending -> open ___ Python tracker <http://bugs.python.org/issue8091> ___ ___ Python-bugs-

[issue8091] TypeError at the end of 'make test'

Changes by Florent Xicluna : -- stage: -> committed/rejected status: open -> pending superseder: -> subprocess.POpen.__del__() AttributeError (os module == None!) type: -> behavior ___ Python tracker <http://bugs.pytho

[issue7772] test_py3kwarn fails when running the whole test suite

Florent Xicluna added the comment: Fixed with r78815. Issue #7092 should silence py3k warnings (soon). Next step is to activate "-3" on some buildbot. -- assignee: -> flox dependencies: -Test suite emits many DeprecationWarnings when -3 is enabled priority: -> n

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

New submission from Florent Xicluna : There's such failure on trunk and py3k when openssl 0.9.8m is installed. (Debian platform) No failure with 0.9.8k. test_ftplib Exception in thread Thread-40: Traceback (most recent call last): File "./Lib/threading.py", line 530, in __

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Changes by Florent Xicluna : -- nosy: +giampaolo.rodola, haypo, pitrou ___ Python tracker <http://bugs.python.org/issue8108> ___ ___ Python-bugs-list mailin

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Florent Xicluna added the comment: It occurs only for trunk and 3.x, where the "ftp over ssl" is implemented. See #2054. And the Debian alpha buildbots have the same library 0.9.8m: http://www.python.org/dev/buildbot/all/builders/alpha%20Debian%20trunk http://www.python.org/dev/bu

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Florent Xicluna added the comment: OpenSSL changelog (scroll to 0.9.8m): http://www.openssl.org/news/changelog.html -- ___ Python tracker <http://bugs.python.org/issue8

[issue8110] subprocess.py doesn't correctly detect Windows machines

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker <http://bugs.python.org/issue8110> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8110] subprocess.py doesn't correctly detect Windows machines

Florent Xicluna added the comment: Proposed patch, with duck subprocessing. :D -- keywords: +patch Added file: http://bugs.python.org/file16518/issue8110_subprocess_mswindows.diff ___ Python tracker <http://bugs.python.org/issue8

[issue7880] sysconfig does not like symlinks

Florent Xicluna added the comment: Fixed in r78828 and r78829 (py3k), except for the part related to #7774. (It was turning buildbots red, after Victor fixed #3137) -- resolution: -> fixed stage: patch review -> committed/rejected status: open ->

[issue7774] sys.executable: wrong location if zeroth command argument is modified.

Florent Xicluna added the comment: Fixed test failures related to incorrect sys.executable, which were visible after #3137 was fixed. Changesets r78830 and r78831. Note: there's 2 comments related to #7774. To review when this issue is fixed: - Lib/sysconfig.py - Lib/test/test_subproce

[issue7774] sys.executable: wrong location if zeroth command argument is modified.

Florent Xicluna added the comment: Actually there's 3 steps to fix this: 1) do not absolutize the sys.executable if it is empty (in Modules/getpath.c) 2) change sysconfig.py to deal with empty sys.executable (see this patch) 3) do a best effort to provide a valid sys.executable. It shou

[issue6472] Update ElementTree with upstream changes

Florent Xicluna added the comment: Fixed on trunk with r78838. Some extra work is required to port it to 3.x. Thank you Fredrik and Antoine for reviewing this patch. -- resolution: -> fixed stage: patch review -> committed/rejected ___

[issue1538691] Patch cElementTree to export CurrentLineNumber

Florent Xicluna added the comment: ElementTree fixed in 2.7. See #6472. -- dependencies: -Update ElementTree with upstream changes resolution: postponed -> fixed stage: patch review -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upst

[issue3475] _elementtree.c import can fail silently

Florent Xicluna added the comment: Fixed with latest xml.etree. -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upstream changes versions: -Python

[issue3151] elementtree serialization bug for weird namespace urls

Florent Xicluna added the comment: Fixed in trunk. -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upst

[issue6565] improper use of __setitem__ in ElementTree for Python 3.1

Florent Xicluna added the comment: Fixed in 2.7 with #6472. It should be ported to 3.x later. -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed superseder: -> Update Elem

[issue6230] ElementTree.Element and cElementTree.Element have slightly different repr

Florent Xicluna added the comment: Fixed in trunk with #6472. -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upst

[issue6265] cElementTree & ElementTree use different exceptions for XML Errors

Changes by Florent Xicluna : -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upstream changes ___ Python tr

[issue6232] Improve test coverage of ElementTree and cElementTree

Changes by Florent Xicluna : -- dependencies: -Update ElementTree with upstream changes priority: -> normal resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> Update ElementTree with u

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

Florent Xicluna added the comment: Fixed with #6472. -- dependencies: -Update ElementTree with upstream changes resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed superseder: -> Update ElementTree with upst

[issue6472] Update ElementTree with upstream changes

Florent Xicluna added the comment: Patch to merge ElementTree 1.3 in 3.x. -- Added file: http://bugs.python.org/file16528/issue6472_upstream_py3k_v3.diff ___ Python tracker <http://bugs.python.org/issue6

[issue6472] Update ElementTree with upstream changes

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16192/issue6472_etree_upstream_py3k_v2.diff ___ Python tracker <http://bugs.python.org/issue6

[issue6472] Update ElementTree with upstream changes

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16244/issue6472_etree_upstream_v5a.diff ___ Python tracker <http://bugs.python.org/issue6

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Florent Xicluna added the comment: I plan to merge ET 1.3 in the 3.x branch tomorrow (See #6472) Currently, the patch is consistent with 3.1 behaviour. It could be changed later, depending on the pronouncement on this compatibility issue. > Previously, in ElementTree, serialising without

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Florent Xicluna added the comment: >>> tree = parse("out.xml") Actually the test in my previous message does not prove anything. locale.getpreferredencoding() returns "UTF-8" != "utf-8". :) -- ___ Python tra

[issue8130] except-as in Py3 eats variables

Florent Xicluna added the comment: See also #4617, with some patch. -- nosy: +flox superseder: -> SyntaxError when free variable name is also an exception target ___ Python tracker <http://bugs.python.org/iss

[issue4617] SyntaxError when free variable name is also an exception target

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16341/unnamed ___ Python tracker <http://bugs.python.org/issue4617> ___ ___ Python-bugs-list mailin

[issue4617] SyntaxError when free variable name is also an exception target

Changes by Florent Xicluna : -- components: +Interpreter Core nosy: +flox stage: -> test needed type: -> behavior ___ Python tracker <http://bugs.python.org/

[issue8128] String interpolation with unicode subclass fails to call __str__

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker <http://bugs.python.org/issue8128> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8129] Wrong arguments in sqlite3.connect() documentation

Changes by Florent Xicluna : -- priority: -> normal stage: -> needs patch ___ Python tracker <http://bugs.python.org/issue8129> ___ ___ Python-bugs-list

[issue7808] test_bsddb3 leaks references

Florent Xicluna added the comment: The tool is called regrtest: ~ $ ./python -m test.regrtest -R 2:3: -uall test_bsddb3 Some devs and some buildbots hunt refleaks in the test suite. Even if the test-related refleaks are not important, they may hide real refleaks in the source code

[issue7808] test_bsddb3 leaks references

Florent Xicluna added the comment: > I confirm the leaks in the C code. How do you find them? I've done it manually, disabling some tests, and running "regrtest -R" repeatedly until I isolate the function which is responsible. Then I studied the source code, looking for t

[issue6472] Update ElementTree with upstream changes

Florent Xicluna added the comment: Merged in 3.x with r78942 and r78945. See #8047 for a discussion about the `encoding` argument of the serializer (used for .write() method and tostring() tostringlist() functions). Currently the output is not encoded by default in 3.1 and 3.x. It is encoded

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Florent Xicluna added the comment: Currently "tree.write(file)" returns Unicode in 3.1 (and 3.x). I would propose the following change: >>> tree.write(file) # ==> encode to ASCII without xml declaration (compatible 2.x) >>> tree.write(file, encoding="utf

[issue1652] subprocess should have an option to restore SIGPIPE to default action

Florent Xicluna added the comment: Fixed an oversight on the switch None ==> -1 which prevents compilation on some buildbot. See r78961. -- nosy: +flox ___ Python tracker <http://bugs.python.org/iss

[issue7808] test_bsddb3 leaks references

Florent Xicluna added the comment: Jesús, your patch looks good. I prefer your approach. My use of the weakrefs was an ugly workaround, I admit. Maybe the "close()" method in the C module should be in charge of DECREFing the handlers and freeing memory. I did not look furth

[issue8024] upgrade to Unicode 5.2?

Florent Xicluna added the comment: It is just a matter of running "makeunicodedata" affter changing "5.1" -> "5.2". It generates the 3 db files: * Modules/unicodedata_db.h * Modules/unicodename_db.h * Objects/unicodetype_db.h Then you adjust th

[issue7946] Convoy effect with I/O bound threads and New GIL

Florent Xicluna added the comment: On some platforms the difference is not so important. I ran it in Debian Lenny AMD64 "Core2 Duo P9600 @2.66GHz". # Python 3.2a0 (py3k:78982M, Mar 15 2010, 15:40:42) # [GCC 4.3.4] on linux2 0.67s without thread 0.84s with spinn

[issue7946] Convoy effect with I/O bound threads and New GIL

Florent Xicluna added the comment: With line buffering, I see the issue. * 6 s without thread * 115 s with the spinning thread (varying: 60 s, 98 s) * 16 s with the spinning thread and the last "gilinter.patch" # Modified version of the test case, with bufsize=1 from thread

[issue8024] upgrade to Unicode 5.2?

Florent Xicluna added the comment: > So the Unicode database format itself has not changed ? No. The changes listed below have no impact afai-have-tested. - - - - - - - F. Unicode Character Database Changes The detailed listing of

[issue8024] upgrade to Unicode 5.2

Changes by Florent Xicluna : -- title: upgrade to Unicode 5.2? -> upgrade to Unicode 5.2 ___ Python tracker <http://bugs.python.org/issue8024> ___ ___ Python-

[issue7787] Add an argument to test_support.open_urlresource to invalidate the cache

Florent Xicluna added the comment: Done with r78986. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.o

[issue7783] test_normalization fails when NormalizationTest.txt is outdated

Florent Xicluna added the comment: Done with r78986. -- ___ Python tracker <http://bugs.python.org/issue7783> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7783] test_normalization fails when NormalizationTest.txt is outdated

Changes by Florent Xicluna : -- priority: -> normal resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.pytho

[issue767645] incorrect os.path.supports_unicode_filenames

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15842/issue767645_test_pep277.py ___ Python tracker <http://bugs.python.org/issue767645> ___ ___

[issue767645] incorrect os.path.supports_unicode_filenames

Florent Xicluna added the comment: With r78594, test_pep277 is active on all platforms having Unicode-friendly filesystem encoding. -- type: -> behavior ___ Python tracker <http://bugs.python.org/issue

[issue8142] libffi update to 3.0.9

Florent Xicluna added the comment: I noticed some failures on Sparc Solaris10 buildbots (both trunk and 3.x) == FAIL: test_ulonglong (ctypes.test.test_callbacks.Callbacks

[issue8163] DictionaryServices module broken in python2.6 and later

Florent Xicluna added the comment: See also: * http://pypi.python.org/pypi/pyobjc-framework-DictionaryServices/ -- nosy: +flox ___ Python tracker <http://bugs.python.org/issue8

[issue8142] libffi update to 3.0.9

Florent Xicluna added the comment: re-opened to track the issue on Sparc Solaris -- resolution: fixed -> stage: -> needs patch status: closed -> open ___ Python tracker <http://bugs.python.o

[issue3783] dbm.sqlite proof of concept

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker <http://bugs.python.org/issue3783> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Florent Xicluna added the comment: > Checking the pybsddb 4.8.4devel with current trunk I still see this: It is because the "test_early_close" module calls resetwarnings(). It defeats the filter in the "threading" module. You may change the test case with a c

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: here come the patch. -- components: +Tests keywords: +easy, patch stage: test needed -> patch review versions: +Python 2.7 Added file: http://bugs.python.org/file16572/issue8155_check_warnings_quiet.diff ___ Pyt

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: I hesitate to do it differently: with check_warnings(('', RuntimeWarning)): ==> translate to check_warnings(('', RuntimeWarning), quiet=False) with check_warnings(): ==> translate to check_warnings(quiet=True) If the developer pa

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file16572/issue8155_check_warnings_quiet.diff ___ Python tracker <http://bugs.python.org/issue8

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: Patch updated. -- Added file: http://bugs.python.org/file16573/issue8155_check_warnings_quiet_v2.diff ___ Python tracker <http://bugs.python.org/issue8

[issue8142] libffi update to 3.0.9

Florent Xicluna added the comment: > no access to solaris hardware. please could you run the libffi > testsuite on this machine? make sure that expect is installed. I don't have access to such hardware. I noticed the buildbot failures since libffi was upgraded. -- keywords

[issue8155] Incompatible change to test.test_support.check_warnings behaviour

Florent Xicluna added the comment: Fixed with r79049 and r79050. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 3.2 ___ Python tracker <http://bugs.python.o

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Done with r79059 and r79062. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.o

[issue7643] What is a Unicode line break character?

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15806/issue7643_remove_deprecation.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7643] What is a Unicode line break character?

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15807/issue7643_use_LineBreak.diff ___ Python tracker <http://bugs.python.org/issue7643> ___ ___

[issue7643] What is a Unicode line break character?

Florent Xicluna added the comment: Cleanup committed as r78982 Patch for LineBreak.txt updated after UCD upgrade to 5.2. See details: http://bugs.python.org/issue7643#msg97483 Tests added to test_unicodedata. Backward compatibility concern: * it adds VT u'\x0b' and FF u'\x0c&

[issue8024] upgrade to Unicode 5.2

Florent Xicluna added the comment: Reverted in 3.x: it triggers some failures. Symptoms: * repr('\uaaa') gives an empty string * test_bigmem fails -- resolution: fixed -> accepted stage: committed/rejected -> commit review status

[issue7643] What is a Unicode line break character?

Changes by Florent Xicluna : -- nosy: -Chris.Carter ___ Python tracker <http://bugs.python.org/issue7643> ___ ___ Python-bugs-list mailing list Unsubscribe:

[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

[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 <http://bugs.python.o

[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

[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 <http://bugs.python.o

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

Florent Xicluna added the comment: The changes enabled more tests for all *path related modules. Please try attached patch. -- components: +Macintosh keywords: +patch priority: -> normal resolution: -> accepted type: -> behavior versions: +Python 3.2 Added f

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

Florent Xicluna added the comment: This patch should fix the test on OS X platforms. -- components: +Macintosh, Unicode keywords: +patch priority: -> normal resolution: -> accepted stage: needs patch -> patch review type: -> behavior versions: +Python 3.2 Adde

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

Changes by Florent Xicluna : -- stage: needs patch -> patch review ___ Python tracker <http://bugs.python.org/issue8179> ___ ___ Python-bugs-list mai

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

Florent Xicluna added the comment: A patch with more Unicode normalization tests. Could you test it on Windows or Mac OS X? -- Added file: http://bugs.python.org/file16600/issue8180_pep277_additions.diff ___ Python tracker <http://bugs.python.

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

Changes by Florent Xicluna : -- nosy: +brett.cannon ___ Python tracker <http://bugs.python.org/issue8180> ___ ___ Python-bugs-list mailing list Unsubscribe:

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

Florent Xicluna added the comment: Note: issue #8180 is related to the same NFC/NFD issue. http://developer.apple.com/mac/library/qa/qa2001/qa1173.html -- components: +Macintosh, Unicode nosy: +flox resolution: -> accepted ___ Python tracker &l

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

Florent Xicluna added the comment: Could you tell if the patch fix the issue? -- keywords: +patch stage: -> patch review Added file: http://bugs.python.org/file16601/issue8133_test_imp.diff ___ Python tracker <http://bugs.python.org/iss

<    2   3   4   5   6   7   8   9   10   11   >