[issue8879] Implement os.link on Windows

Hirokazu Yamamoto added the comment: r86733 introduces st_ino setup in attribute_data_to_stat(), but Fild ID is not guaranteed to be same when file is not opened. So I think it's meaningful only for os.fstat(). Please see http://msdn.microsoft.com/en-us/library/aa363788%28v=VS.85%29.aspx -

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Amaury Forgeot d'Arc added the comment: issue9200 already proposes a similar change to str.is* methods. -- ___ Python tracker ___ ___

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Changes by Ezio Melotti : -- nosy: +amaury.forgeotdarc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Alexander Belopolsky added the comment: Here is another proof of concept patch for the isalpha issue that introduces a higher level abstraction macro - Py_UNICODE_NEXT. It should be possible to reuse this macro in all isxyz methods and other places where surrogates are currently processed.

[issue2986] difflib.SequenceMatcher not matching long sequences

Eli Bendersky added the comment: Terry, I agree with Simon re closing and opening a new feature request. This issue has too much baggage in it, and you we always link to it. A new feature request should be opened strictly for 3.2 If you want I can close this issue and open a new one, but I'm

[issue2986] difflib.SequenceMatcher not matching long sequences

Simon Cross added the comment: My vote is that this bug be closed and a new feature request be opened. Failing that, it would be good to have a concise description of what else we would like done (and the priority should be downgraded, I guess). -- ___

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Ezio Melotti added the comment: I think that methods like str.isalpha can and should be fixed. Since _PyUnicode_IsAlpha now accepts a Py_UCS4, the body of unicode_isalpha can be changed to convert normal chars and surrogates pairs to a Py_UCS4 before calling Py_UNICODE_ISALPHA. The attached p

[issue2986] difflib.SequenceMatcher not matching long sequences

Terry J. Reedy added the comment: Since I am not sure I will be able to do any more before the 3.2b1 feature freeze, I went ahead with the minimal patch after checking the differences from the 2.7 version and redoing the Misc/News entry. (I suspect putting a new entry immediately after the app

[issue10525] Added mouse and colour support to Game of Life curses demo

Senthil Kumaran added the comment: On Thu, Nov 25, 2010 at 05:44:21AM +, Dafydd Crosby wrote: > I created a patch that adds those two wishlist items. Given that > mouse support and the use of curses.flash() are missing from the > demo programs, I think it's a bit of an upgrade ;-) > Pretty

[issue9014] Incorrect documentation of the PyObject_HEAD macro

Ray.Allen added the comment: Additionally, I prefer move the discussion of Py_TRACE_REFS under the documentation of PyObject: http://docs.python.org/dev/py3k/c-api/structures.html?highlight=pyobject_head#PyObject, since they'are connected directly. The doc of PyObject_HEAD should only saying

[issue10525] Added mouse and colour support to Game of Life curses demo

New submission from Dafydd Crosby : I was just going through the source of the curses demo Game of Life (life.py), and saw that the TODO had mouse support and colour. I created a patch that adds those two wishlist items. Given that mouse support and the use of curses.flash() are missing from t

[issue10402] sporadic test_bsddb3 failures

Hirokazu Yamamoto added the comment: This should be duplicate of #3892. I suppose timeout in this test might be very short. Refers to http://www.systomath.eu/doc/BerkeleyDb-4.7/html/api_c/rep_timeout.html timeout is in microseconds, so self.dbenvMaster.rep_set_timeout(db.DB_REP_CONNECTION_RET

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Alexander Belopolsky added the comment: Here is another str method not ready for non-BMP chars: >>> u = '\U00010140' >>> u.translate({ord(u):ord('A')}) '𐅀' (expected 'A') >>> u = 'B' >>> u.translate({ord(u):ord('A')}) 'A' -- ___ Python tracker <

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Changes by Alexander Belopolsky : -- Removed message: http://bugs.python.org/msg122313 ___ Python tracker ___ ___ Python-bugs-list mai

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Alexander Belopolsky added the comment: On Wed, Nov 24, 2010 at 3:37 PM, Marc-Andre Lemburg wrote: .. > I don't think we should change that for the formatting methods. That's a reasonable position. What about >>> unicodedata.category('\N{OLD ITALIC LETTER A}') 'Lo' >>> '\N{OLD ITALIC LETTER

[issue8481] doc: ctypes no need to explicitly allocate writable memory with Structure

Ray.Allen added the comment: I think not only Structures but also other ctypes can be passed with byref() to functions expecting pointer to mutable memory. -- nosy: +ysj.ray ___ Python tracker

[issue9509] argparse FileType raises ugly exception for missing file

akira <4kir4...@gmail.com> added the comment: updated patch on http://codereview.appspot.com/3251041/ -- ___ Python tracker ___ ___ Pyt

[issue9509] argparse FileType raises ugly exception for missing file

akira <4kir4...@gmail.com> added the comment: Attached patch for argparse.py (argparse.diff -- without tests, see tests in test_argparse.diff) where ValueError is raises in FileType.__call__ and additional details printed on ArgumentError -- Added file: http://bugs.python.org/file19807

[issue9509] argparse FileType raises ugly exception for missing file

akira <4kir4...@gmail.com> added the comment: I've added tests for readonly files. SilentGhost's patch doesn't handle this case. -- Added file: http://bugs.python.org/file19806/test_argparse.diff ___ Python tracker

[issue10154] locale.normalize strips "-" from UTF-8, which fails on Mac

Changes by MunSic JEONG : -- nosy: +ruseel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue10027] os.lstat/os.stat don't set st_nlink on Windows

Hirokazu Yamamoto added the comment: Thank you for commit! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5800] make wsgiref.headers.Headers accept empty constructor

Ramiro Batista da Luz added the comment: I reviewed the patch. - I applied all the patchs(3 files). - Ran make and make html in the Doc directory. - Ran the test_wsgiref.py - Ran the python interpreter and typed the suggested code: >>> from wsgiref.headers import Headers >>> headers = Head

[issue9509] argparse FileType raises ugly exception for missing file

SilentGhost added the comment: Attached patch with the try-except clause as suggested by Steven, Doug's example now produces the following output: $ ./python argparse_filetype_error.py usage: argparse_filetype_error.py [-h] [-i I] argparse_filetype_error.py: error: no such file or directory '

[issue3063] memory leak in random number generation

Amaury Forgeot d'Arc added the comment: For the record, this was finally fixed with issue2862: gc.collect() now clears the free-lists during the collection of the highest generation. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Dave Malcolm added the comment: FWIW, I was able to do an almost full run of regrtest on this box with: -x test_multiprocessing test_concurrent_futures Other than those two, all tests pass. So _something_ is going wrong w.r.t. threads, though I'm not sure what at this stage. -- __

[issue8879] Implement os.link on Windows

Amaury Forgeot d'Arc added the comment: The patch uses the ANSI version, and converts the filename from unicode to bytes; this will fail for names that cannot be encoded with the "mbcs" codec. All other functions in the posix module first try the Wide version of the win32 API, and use the ANS

[issue5800] make wsgiref.headers.Headers accept empty constructor

SilentGhost added the comment: Here is the correction for the docs. I would love to see this making it into 3.2 release. -- Added file: http://bugs.python.org/file19804/wsgiref.rst.diff ___ Python tracker

[issue10299] Add index with links section for built-in functions

Ezio Melotti added the comment: Backported in r86735 (3.1) and r86736 (2.7). -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue10515] csv sniffer does not recognize quotes at the end of line

Ned Deily added the comment: (Thanks. I've unpacked and uploaded the three files from your tar file.) -- stage: unit test needed -> patch review Added file: http://bugs.python.org/file19803/p2.patch ___ Python tracker

[issue10515] csv sniffer does not recognize quotes at the end of line

Changes by Ned Deily : -- keywords: +patch Added file: http://bugs.python.org/file19802/p1.patch ___ Python tracker ___ ___ Python-bug

[issue10524] Patch to add Pardus to supported dists in platform

New submission from Onur Küçük : Attached patch adds Pardus to supported dists in platform. Diff is against current release27-maint, but it applies to release31-maint and py3k too. -- components: Library (Lib) files: pardus_platform_release27-maint.patch keywords: patch messages: 122315

[issue10515] csv sniffer does not recognize quotes at the end of line

Changes by Ned Deily : Added file: http://bugs.python.org/file19800/test.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue10523] argparse has problem parsing option files containing empty rows

Changes by Michal Pomorski : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue10523] argparse has problem parsing option files containing empty rows

New submission from Michal Pomorski : When using the argument file option, i.e @file_with_arguments the following problems arise: 1. argparse crashes when the file contains an empty line (even if it is the last line) - arg_string[0] is done when arg_string is empty. This is caused by the

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Alexander Belopolsky added the comment: On Wed, Nov 24, 2010 at 3:37 PM, Marc-Andre Lemburg wrote: .. > I don't think we should change that for the formatting methods. That's a reasonable position. What about 'Lo' >>> '\N{OLD ITALIC LETTER A}'.isalpha() False the str.isalpha() method is und

[issue10515] csv sniffer does not recognize quotes at the end of line

Martin Budaj added the comment: Units test and two patches for 2.7 are included. p1.patch fixes testEnd case reported yesterday After running unittest it seems that also other case is broken (testAl -- if there is just one data item on the line, enclosed in quotes). Patch p2 fixes it, but sh

[issue10520] Build with --enable-shared fails

Changes by Éric Araujo : -- nosy: +benjamin.peterson, eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue8938] Mac OS dialogs(Save As..., Load) translation

Ned Deily added the comment: There seem to be several different issues being reported here. As far as I can tell, the only issue that directly relates to code in the Python standard library is the lack of internationalization for EasyDialogs. EasyDialogs depends on deprecated OS X Carbon in

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > New submission from Alexander Belopolsky : > 'xyz'.center(20, '\U00100140') > Traceback (most recent call last): > File "", line 1, in > TypeError: The fill character must be exactly one character long > > str.ljust

[issue10518] Bring back callable()

Ezio Melotti added the comment: I'm not sure it's worth bringing callable() back at this point. It would have made more sense for 3.1, but now we already have 2 callable()-less versions of Python if we do it for 3.2 (what about the moratorium though?) or 3 if we do it for 3.3. Also if isinst

[issue10520] Build with --enable-shared fails

Barry A. Warsaw added the comment: BTW, I am not sure it's worth backporting this to 3.1 and 2.7. It seems like a corner case that will not affect most users. -- ___ Python tracker __

[issue10520] Build with --enable-shared fails

Barry A. Warsaw added the comment: r86734 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue8879] Implement os.link on Windows

Brian Curtin added the comment: Fixed in r86733. -- stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue8879] Implement os.link on Windows

Brian Curtin added the comment: Removing link to #10027. It's fixed for py3k but the issue should stay open for backport to other branches. -- dependencies: -os.lstat/os.stat don't set st_nlink on Windows resolution: -> fixed ___ Python tracker <

[issue10299] Add index with links section for built-in functions

Benjamin Peterson added the comment: Okay. 2010/11/24 Ezio Melotti : > > Ezio Melotti added the comment: > > Committed in r86732 on py3k, will backport on 3.1/2.7 if Benjamin is OK with > that. > > -- > nosy: +benjamin.peterson > > ___ > Python trac

[issue10299] Add index with links section for built-in functions

Ezio Melotti added the comment: Committed in r86732 on py3k, will backport on 3.1/2.7 if Benjamin is OK with that. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue10497] Incorrect use of gettext in argparse

Steven Bethard added the comment: Looks like a great fix. And yes, anyone who knows anything about gettext, please feel free to add a test or ten. ;-) I just copied optparse when I put that stuff in, so I have no confidence in how it's done now. -- __

[issue9509] argparse FileType raises ugly exception for missing file

Steven Bethard added the comment: I'm not sure about the patch - this will convert *all* IOErrors into command line error messages, while we should really only be converting the ones raised by FileType. Instead, the try/except should be in FileType.__call__, and you should raise an ArgumentTy

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10519] setobject.c no-op typo

Raymond Hettinger added the comment: A few lines later, a similar change can be made for set_discard. -- assignee: anthonybaxter -> arigo ___ Python tracker ___

[issue9807] deriving configuration information for different builds with the same prefix

Barry A. Warsaw added the comment: r86731 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue10519] setobject.c no-op typo

Raymond Hettinger added the comment: Try to match the whitespace convention of the surrounding code. -- assignee: rhettinger -> anthonybaxter nosy: +anthonybaxter resolution: -> accepted ___ Python tracker __

[issue8938] Mac OS dialogs(Save As..., Load) translation

Changes by Terry J. Reedy : -- nosy: -terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Alexander Belopolsky added the comment: On Wed, Nov 24, 2010 at 10:33 AM, Antoine Pitrou wrote: .. > The question is, what should it do with such an input? I think the rule for such functions should be that if input.encode('utf-8') is the same on wide and narrow builds, then the output.encode(

[issue10519] setobject.c no-op typo

Changes by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Dave Malcolm added the comment: By strategically adding print() and input() calls, I was able to isolate the error to this line in test_multiprocessing.py's test_main: ManagerMixin.pool = ManagerMixin.manager.Pool(4) specifically, to the construction: ManagerMixin.manager.Pool(4) Minimal

[issue8938] Mac OS dialogs(Save As..., Load) translation

gius.dima added the comment: I'm using Python 2.7, PyQt 4.8.1, qt 4.7.1 on OS X Leopard 10.6.5 and have just the same problem. In C++ and qt all dialog's messages are in italian, in PyQt dialogs are partially in english. -- nosy: +gius.dima Added file: http://bugs.python.org/file19798

[issue10518] Bring back callable()

SilentGhost added the comment: What is the reason for this? Why do we need it? -- nosy: +SilentGhost ___ Python tracker ___ ___ Pytho

[issue10516] Add list.clear() and list.copy()

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

[issue10518] Bring back callable()

Éric Araujo added the comment: Does the plan include deprecating collections.Callable? -- nosy: +eric.araujo ___ Python tracker ___ _

[issue10520] Build with --enable-shared fails

Stefan Krah added the comment: Since I'm on Linux, I did a prior install into /usr/local. But I'm pretty sure that BSD ports (which you might view as the system install) also use /usr/local. -- ___ Python tracker

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Changes by Łukasz Langa : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Dave Malcolm added the comment: Seems to be an issue within (or triggered by) multiprocessing (test_threads and test_threading pass OK, fwiw): $ ./python -m test.test_multiprocessing Fatal Python error: Invalid thread state for this thread Traceback (most recent call last): File "/home/dmalco

[issue4147] xml.dom.minidom toprettyxml: omit whitespace for text-only elements

anatoly techtonik added the comment: This one is bug. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Dave Malcolm added the comment: Minimal reproducer: $ ./python -c "from concurrent.futures import * ; e = ProcessPoolExecutor() ; e.submit(pow, 2, 5)" Fatal Python error: Invalid thread state for this thread -- ___ Python tracker

[issue4147] xml.dom.minidom toprettyxml: omit whitespace for text-only elements

Changes by anatoly techtonik : -- nosy: +techtonik ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue10516] Add list.clear() and list.copy()

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Dave Malcolm added the comment: I'm able to reliably reproduce this on a RHEL 5 box (i386 in this case). All of the "ProcessPool*" unittest subclasses within Lib/test/test_concurrent_futures.py exhibit this hang, each printing out just the name of the first test (so presumably either within t

[issue10520] Build with --enable-shared fails

Matthias Klose added the comment: -L. should appear before -L/usr/local/lib. -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-li

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Eric Smith added the comment: str.__format__ and friends (int, float, complex) also have this same problem. For example, when they're computing the "fill" character: >>> format('', 'x^') '' >>> format('', '\U00100140^') Traceback (most recent call last): File "", line 1, in ValueError: Inv

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

Antoine Pitrou added the comment: The question is, what should it do with such an input? Pretend it's a single char (but other chars in the source string won't get the same treatment)? Treat it as a two-char string (but then center() and friends should logically be extended to accept strings

[issue10520] Build with --enable-shared fails

Barry A. Warsaw added the comment: I'm bumping the status down since this likely won't affect the average user, only developers who do their own source installs. -- assignee: -> barry priority: critical -> high ___ Python tracker

[issue10520] Build with --enable-shared fails

Barry A. Warsaw added the comment: So, you must have done a 'make install' or 'make altinstall' to get a build into /usr/local, right? Without that of course it works fine. You're probably still right about changing the order so it picks up the local copy first. --

[issue10522] test_telnet exception

New submission from Antoine Pitrou : This has just occurred on the Solaris buildbot: test_telnetlib Exception in thread Thread-452: Traceback (most recent call last): File "/home2/buildbot/slave/2.7.loewis-sun/build/Lib/threading.py", line 530, in __bootstrap_inner self.run() File "/hom

[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build

New submission from Alexander Belopolsky : >>> 'xyz'.center(20, '\U00100140') Traceback (most recent call last): File "", line 1, in TypeError: The fill character must be exactly one character long str.ljust and str.rjust are similarly affected. -- components: Interpreter Core messag

[issue10517] test_concurrent_futures crashes with "Fatal Python error: Invalid thread state for this thread"

Changes by Dave Malcolm : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10520] Build with --enable-shared fails

Changes by Antoine Pitrou : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue7238] frame.f_lineno doesn't get updated after local trace function assigned to it

Ray.Allen added the comment: It's not a bug. What happens is like this: 1, You set trace function using sys.settrace(tracer). 2, When the following func() is called, tracer is called with a "call" event, so the trace function in PyThreadState is set to NULL since "sys.settrace(None)" is execu

[issue10520] Build with --enable-shared fails

New submission from Stefan Krah : Building the modules fails if --enable-shared is used. The linker picks up an existing library from /usr/local/lib, which has not been compiled with -fPIC: gcc -pthread -shared build/temp.linux-x86_64-3.2/home/stefan/svn/py3k/Modules/_struct.o -L/usr/local/li

[issue10520] Build with --enable-shared fails

Changes by Stefan Krah : -- nosy: skrah priority: normal severity: normal status: open title: Build with --enable-shared fails ___ Python tracker ___

[issue5800] make wsgiref.headers.Headers accept empty constructor

Changes by Dirkjan Ochtman : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue10518] Bring back callable()

Benjamin Peterson added the comment: I think we should lift the py3k warning after 3.2 is released, but leave the 2to3 fixer in for the time being. -- ___ Python tracker ___ __

[issue5800] make wsgiref.headers.Headers accept empty constructor

SilentGhost added the comment: Re-submitting the patch for Lib/wsgiref/headers.py w/o the isinstance change -- keywords: +patch Added file: http://bugs.python.org/file19797/headers.py.diff ___ Python tracker __

[issue5800] make wsgiref.headers.Headers accept empty constructor

Changes by SilentGhost : Removed file: http://bugs.python.org/file19680/headers.py.diff ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue10027] os.lstat/os.stat don't set st_nlink on Windows

Brian Curtin added the comment: Committed to py3k in r86727. I think this should be backported to the maintenance branches, but not until after the upcoming point releases. Although those branches won't have the ability to create hard links, they should have the ability to view information

[issue10519] setobject.c no-op typo

Changes by Antoine Pitrou : -- nosy: +rhettinger, stutzbach versions: +Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-l

[issue10519] setobject.c no-op typo

New submission from Armin Rigo : Probably a typo in setobject.c. The patch attached here does not really change anything but fixes the typo, leading to slightly clearer code and avoiding one level of recursion. All tests still pass. -- components: Interpreter Core files: diff1 messag

[issue10518] Bring back callable()

New submission from Antoine Pitrou : It was just resting. Here is a patch to wake it up for 3.2 (or 3.3 pending moratorium interpretation). As for the py3k warning in 2.x (and the 2to3 fixer), it's not obvious what we should do: callable() clearly doesn't exist in 3.0 and 3.1. -- assi

[issue10496] "import site failed" when Python can't find home directory

Changes by Ned Deily : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue10496] "import site failed" when Python can't find home directory

Ned Deily added the comment: The problem is reproducible on a current Debian Linux system although with different results for current versions of Python (only security issues are accepted against 2.6). Unlike with 2.6, 3.1 reports no error. 2.7 and 3.2 both fail with an exception: Tracebac

[issue10496] "import site failed" when Python can't find home directory

Changes by Ned Deily : -- Removed message: http://bugs.python.org/msg122051 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue9852] test_ctypes fail with clang

Ned Deily added the comment: OK, then if you care to follow up, I suggest pursuing with the Clang project. -- resolution: -> invalid status: open -> closed ___ Python tracker __

[issue10513] sqlite3.InterfaceError after commit

Anders Blomdell added the comment: The culprit seems to be 'pysqlite_do_all_statements(self, ACTION_RESET, 0)' in pysqlite_connection_commit, which resets all active statements, but subsequent fetch/fetchall seems to trash the sqlite3 state in the statements. Removing the ACTION_RESET seems t

[issue9852] test_ctypes fail with clang

Ismail Donmez added the comment: No interesting option. But this looks like a clang bug, compiling _ctypes_test.c with -O0 fixes the issue. So this is a compiler optimization bug. -- ___ Python tracker ___

[issue10430] _sha.sha().digest() method is endian-sensitive. and hexdigest()

Kristján Valur Jónsson added the comment: Found the issue and it wasn't with sha1. Turned out that the code was doing somethign like sha1(buffer(unicode('str'))) which exposed the endianness of the unicode representation. Sorry for wasting your time. -- resolution: -> invalid status:

[issue9852] test_ctypes fail with clang

Ned Deily added the comment: Can you say exactly what arguments are given to clang for this compile? (As you probably know, CPython builds on OS X for python.org installers use gcc, not clang.) -- nosy: +ned.deily ___ Python tracker

[issue10498] calendar.LocaleHTMLCalendar.formatyearpage() results in traceback with 'unsupported locale setting' on Windows

Ned Deily added the comment: Your analysis is correct. Sorry, I should have noted that the OS X "UTF8" vs "UTF-8" discrepancy has already been discussed in Issue10090 and Issue10154. -- ___ Python tracker __