[issue15187] test_shutil does not clean up after itself

Larry Hastings added the comment: This was fixed in 1fa50bbcc21f1458c1dc00ea733b76e6405b8cbb . (I think the tracker had an aneurysm when the notification showed up.) -- ___ Python tracker

[issue15188] test_ldshared_value failure on OS X using python.org Pythons

New submission from Ned Deily : == FAIL: test_ldshared_value (test.test_sysconfig.TestSysConfig) -- Traceback (most recent call last): File "/Library/Framewor

[issue15187] test_shutil does not clean up after itself

Changes by Larry Hastings : -- assignee: -> larry priority: normal -> release blocker resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker __

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Petri Lehtinen added the comment: I created #15122 for adding an option to rewrite the contents of single-file mailboxes in-place. Closing this issue as wontfix. -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed superseder: -> Add an option to always rew

[issue15187] test_shutil does not clean up after itself

Georg Brandl added the comment: Yep. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue15184] Test failure in test_sysconfig_module

Georg Brandl added the comment: Sounds good. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue15186] Support os.walk(dir_fd=)

Larry Hastings added the comment: Whoops, you wrote "for most users" rather than talking about beginners. Sorry if I was responding to a point you weren't making ;-) I guess I assumed you were coming at this at least partially while wearing your "Python lecturer" hat. -- __

[issue15186] Support os.walk(dir_fd=)

Larry Hastings added the comment: p.s. Raymond: fwiw, I think "makes it easy / hard for beginners" is only of secondary importance. Certainly I think it's reasonable to point out in a discussion, and if the beginners are easy to accommodate then okay. But if there was something that was a b

[issue15178] Doctest should handle situations when test files are not readable

Bohuslav "Slavek" Kabrda added the comment: So I figured it might be best to first agree on the actual behaviour (what the patch will look like) and then I can write the tests. So here is my 3rd version: - It seems that returning 1 only if last file fails is intentional, as it is _inside_ the

[issue15184] Test failure in test_sysconfig_module

Changes by Ned Deily : Added file: http://bugs.python.org/file26164/issue15184_osx_support.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue13685] argparse update help msg for % signs

Changes by Senthil Kumaran : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue13685] argparse update help msg for % signs

Roundup Robot added the comment: New changeset c696416eb4e9 by Senthil Kumaran in branch '3.2': Issue #13685 - Update argparse help message for % sign usage. http://hg.python.org/cpython/rev/c696416eb4e9 New changeset 493d58c3c57f by Senthil Kumaran in branch 'default': merge from 3.2 - Issue13

[issue15186] Support os.walk(dir_fd=)

Larry Hastings added the comment: Actually I think Raymond makes a good point. Re: symmetry: tbh that's nonsense. The reason for symmetry among functions in the os module is because they do similar things--but this is because "form follows function". We didn't decide to decorate functions w

[issue15184] Test failure in test_sysconfig_module

Ned Deily added the comment: This test failure points at a few issues: - The CFLAGS modification should only be taking place on OS X systems. AFAICT, all of that code is protected by sys.platform checks. One possible culprit, though, might be distutils test test_unixccompiler which attempt

[issue13685] argparse update help msg for % signs

Changes by Senthil Kumaran : -- title: argparse does not sanitize help strings for % signs -> argparse update help msg for % signs ___ Python tracker ___ __

[issue15172] Document nasm-2.10.01 as required version for openssl

Stefan Krah added the comment: Good that it works now. I've tagged this as a documentation issue. -- assignee: -> docs@python components: +Documentation -Tests keywords: -buildbot nosy: +docs@python title: SHA1 failures on the 64-bit Windows buildbot -> Document nasm-2.10.01 as requi

[issue15187] test_shutil does not clean up after itself

Hynek Schlawack added the comment: LGTM -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15186] Support os.walk(dir_fd=)

Serhiy Storchaka added the comment: > Can you elaborate on why this is needed? 1. Unification with fwalk and other os functions. 2. Performance. Larry, can you use fwalk even for dir_fd is None (if fwalk exists, of cause)? -- nosy: +storchaka ___ P

[issue15178] Doctest should handle situations when test files are not readable

Bohuslav "Slavek" Kabrda added the comment: Sure, if you give me some time, I'll try to do everything as you suggest. -- ___ Python tracker ___ _

[issue12927] test_ctypes: segfault with suncc

Stefan Krah added the comment: Antoine, is it possible to add --with-system-ffi to the build rules of the Solaris/suncc bot? This will prevent the segfaults. -- nosy: +pitrou ___ Python tracker ___

[issue12927] test_ctypes: segfault with suncc

Justin Venus added the comment: I can confirm (see attachement) that `--with-system-ffi` prevents the segfault on test_ctypes with the solaris compiler on Solaris11 x86. I did not have to update the system at all for this switch to work. -- Added file: http://bugs.python.org/file2616

[issue15034] tutorial should use best practices in user defined exceptions section

Raymond Hettinger added the comment: This seems more like a Stack Overflow question or fodder for a blog post. When such best practices become well known and agreed upon, they can be added toa HOWTO document. The tutorial is problematic because beginners start there and sprinkling the nuan

[issue15187] test_shutil does not clean up after itself

Larry Hastings added the comment: Georg, you want this fixed for beta 1? -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bug

[issue14591] Value returned by random.random() out of valid range on 64-bit

Changes by Raymond Hettinger : -- assignee: rhettinger -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue15186] Support os.walk(dir_fd=)

Raymond Hettinger added the comment: Can you elaborate on why this is needed? The os.path.walk() API is already somewhat complex. Additional features can make the tool less usable/learnable for most users. -- nosy: +rhettinger ___ Python tracker

[issue15187] test_shutil does not clean up after itself

Larry Hastings added the comment: Patch attached. On my machine it used to leave six directories, now it leaves none. -- keywords: +patch Added file: http://bugs.python.org/file26161/larry.fix.shutil.test.tmp.dirs.1.diff ___ Python tracker

[issue15187] test_shutil does not clean up after itself

Changes by Larry Hastings : -- nosy: +larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12268] file readline, readlines & readall methods can lose data on EINTR

Gregory P. Smith added the comment: The uses of fwrite() and fflush() also need this EINTR treatment in 2.7. I haven't checked the write paths in 3.2 yet. Also, the fix change to 3.2's _io module needs backporting to 2.7's _io module for people using that. -- __

[issue12268] file readline, readlines & readall methods can lose data on EINTR

Roundup Robot added the comment: New changeset 67dc99a989cd by Gregory P. Smith in branch '2.7': Fixes issue #12268 for file readline, readlines and read() and readinto methods. http://hg.python.org/cpython/rev/67dc99a989cd -- ___ Python tracker

[issue6422] timeit called from within Python should allow autoranging

Raymond Hettinger added the comment: Looking at this again after more time has passes, I still think exposing autoranging is a good idea but I don't like the patch as it stands. It "infects" the API in a number of places and makes the overall module harder to use and learn. Ideally, ther

[issue8916] Move PEP 362 (function signature objects) into inspect

Changes by Éric Araujo : -- resolution: -> duplicate stage: needs patch -> committed/rejected status: open -> closed superseder: -> PEP 362 "Signature Objects" reference implementation ___ Python tracker _

[issue15187] test_shutil does not clean up after itself

New submission from R. David Murray : test_shutil leaves several (six) directories in /tmp. This eventually fills /tmp on my buildbots and causes subsequent test runs to fail. -- components: Tests keywords: buildbot messages: 164026 nosy: hynek, r.david.murray priority: normal severity

[issue15185] Validate callbacks in 'contextlib.ExitStack.callback()'

Nick Coghlan added the comment: I'm not comfortable adding a dependency on inspect to the contextlib module, and I think it would be undesirable to have too many cases where the early validation is silently skipped. While I like the idea of adding early signature validation to these APIs in

[issue15185] Validate callbacks in 'contextlib.ExitStack.callback()'

Yury Selivanov added the comment: (my previous message edit: no support for 'atexit' - it's implemented in C) -- ___ Python tracker ___ _

[issue15186] Support os.walk(dir_fd=)

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

[issue15186] Support os.walk(dir_fd=)

New submission from Larry Hastings : Adds dir_fd support to os.walk(). Just re-yields from os.fwalk(), removing the last element. Note: Python 3.4. -- assignee: larry files: larry.os.walk.dir_fd.1.diff keywords: patch messages: 164023 nosy: larry priority: normal severity: normal stag

[issue15185] Validate callbacks in 'contextlib.ExitStack.callback()'

Changes by Yury Selivanov : -- nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue8916] Move PEP 362 (function signature objects) into inspect

Yury Selivanov added the comment: Éric, yes, please close it. -- nosy: +Yury.Selivanov ___ Python tracker ___ ___ Python-bugs-list mai

[issue15185] Validate callbacks in 'contextlib.ExitStack.callback()'

New submission from Yury Selivanov : With this patch 'contextlib.ExitStack.callback(callback, *args, **kwds)' will validate that the passed callback actually accept the passed '*args' and '**kwds'. P.S. If this patch comes through - I'll create two more issues for 'atexit.register' and 'unitt

[issue15179] An infinite loop happens when we use SysLogHandler with eventlet

Roundup Robot added the comment: New changeset 99f0c0207faa by Vinay Sajip in branch '2.7': Issue #15179: Closed socket on connection failure. Thanks to Kazutaka Morita for the patch. http://hg.python.org/cpython/rev/99f0c0207faa New changeset 1bc1a14feb70 by Vinay Sajip in branch '3.2': Issue

[issue15169] Clear C code under PyImport_ExecCodeModuleObject()

Brett Cannon added the comment: The problem of deferring to 3.4 is that it will lock in semantics which are honestly weird and not desirable for PyImport_ExecCodeModuleObject() which is new in 3.3. -- ___ Python tracker

[issue15184] Test failure in test_sysconfig_module

Changes by Ned Deily : -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue15110] strange Tracebacks with importlib

Antoine Pitrou added the comment: About this proposal: > - trim errors raised when executing the code of an imported module (i.e. in > _LoaderBasics._load_module()) The exec() could be isolated in a distinctly-named submethod (e.g. _exec_module()), so that it is easy to detect it in a traceb

[issue15110] strange Tracebacks with importlib

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

[issue15110] strange Tracebacks with importlib

Antoine Pitrou added the comment: Ah, you're right. But it could become confusing if some error is raised inside of importlib itself (not an ImportError, something else - perhaps a bug). So I would suggest the following: - trim ImportErrors - trim errors raised when executing the code of an im

[issue15110] strange Tracebacks with importlib

Amaury Forgeot d'Arc added the comment: No, the example above is a SyntaxError, and I claim the importlib frames should be removed as well. -- ___ Python tracker ___ __

[issue15110] strange Tracebacks with importlib

Antoine Pitrou added the comment: Perhaps at least the trimming should only be done for ImportErrors, then? -- ___ Python tracker ___ ___

[issue15110] strange Tracebacks with importlib

Amaury Forgeot d'Arc added the comment: I tried to do it in importlib, with code like raise original_exception.with_traceback(trimmed_traceback) but the function containing this very line would always be part of the displayed stack trace. -- __

[issue15110] strange Tracebacks with importlib

Antoine Pitrou added the comment: Wouldn't it be better to do it in pure Python in importlib itself? -- nosy: +pitrou ___ Python tracker ___

[issue15110] strange Tracebacks with importlib

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

[issue13672] Add co_qualname attribute in code objects

Antoine Pitrou added the comment: PyCode_New and PyCode_NewEmpty are documented public APIs, so you can't change their signatures like that. -- nosy: +georg.brandl stage: needs patch -> patch review ___ Python tracker

[issue13672] Add co_qualname attribute in code objects

Arfrever Frehtes Taifersar Arahesis added the comment: Could this patch be included in Python 3.3? -- ___ Python tracker ___ ___ Pyth

[issue15110] strange Tracebacks with importlib

Amaury Forgeot d'Arc added the comment: Here is a patch which removes "" frames from tracebacks. Tests are missing, but this gives good result on the few samples I tried. "python -v" does not suppress importlib frames. -- keywords: +patch Added file: http://bugs.python.org/file26158/

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Jeremy Kloth added the comment: Ok, the final verdict on this issue is that nasm is to blame. I had nasm 2.09.02 installed. I upgraded it to version 2.10.01 and magically OpenSSL started working. >From the nasm changelog is seems that the added instruction sets in 2.10 are required for buildi

[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2

Éric Araujo added the comment: This may have caused failures on non-darwin unix OSes: #15184 -- ___ Python tracker ___ ___ Python-bug

[issue14443] Distutils test_bdist_rpm failure

Roundup Robot added the comment: New changeset a9a12ad553f0 by David Malcolm in branch 'default': Issue #14443: ensure that brp-python-bytecompile is invoked with the correct http://hg.python.org/cpython/rev/a9a12ad553f0 -- ___ Python tracker

[issue1522400] irda socket support

Changes by Charles-François Natali : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue14698] test_posix failures - getpwduid()/initgroups()/getgroups()

Changes by Charles-François Natali : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue14443] Distutils test_bdist_rpm failure

Dave Malcolm added the comment: (with the patch, it also continues to work on a test Fedora 15 box) -- ___ Python tracker ___ ___ Pyt

[issue15184] Test failure in test_sysconfig_module

New submission from Georg Brandl : On default, have this single failure on my box (Gentoo amd64): == FAIL: test_sysconfig_module (distutils.tests.test_sysconfig.SysconfigTestCase)

[issue1599254] mailbox: other programs' messages can vanish without trace

Petri Lehtinen added the comment: It seems to me that there are three separate issues here: 1) Concurrent access to a single-file mailbox will discard some messages even if locking is correctly used. This is demonstrated by mailbox-test.patch, which despite its age applies on top of 3.2 and f

[issue14443] Distutils test_bdist_rpm failure

Dave Malcolm added the comment: The approach Nick suggests seems reasonable, but rpm.expandMacro isn't usable: there's no guarantee that the machine has Python bindings for rpm installed (especially not for the version of Python that we've just built). However, we can get at the macro by shel

[issue13698] Mailbox module should support other mbox formats in addition to mboxo

Petri Lehtinen added the comment: endolith wrote: > > - If the mailbox is written using the mboxrd format and read using > > - the mboxo format, lines that were meant to start with ">From " > > - are changed to ">>>From ". This is a new type of corruption. > > Well, yes. So the choices are: >

[issue14814] Implement PEP 3144 (the ipaddress module)

Hynek Schlawack added the comment: And the origin of the bytes seems to be: # Compatibility function to cast str to bytes objects _cb = lambda bytestr: bytes(bytestr, 'charmap') -- ___ Python tracker

[issue15183] it should be made clear that the statement in the --setup option and the setup kw arg aren't included in the count

Tshepang Lekhonkhobe added the comment: sorry, I meant 'python -m timeit -h' -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15183] it should be made clear that the statement in the --setup option and the setup kw arg aren't included in the count

New submission from Tshepang Lekhonkhobe : I looked at 'python -m time -h' and the timeit doc, and it was not clear to me (after a quick read) that the statement(s) inside --setup option and setup keyword argument weren't included in the speed test. I had to check for myself by writing code.

[issue5633] fix for timeit when the statement is a string and the setup is not (and tests)

Changes by Tshepang Lekhonkhobe : -- title: fix for timeit when the statment is a string and the setup is not (and tests) -> fix for timeit when the statement is a string and the setup is not (and tests) ___ Python tracker

[issue6422] timeit called from within Python should allow autoranging

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue14702] os.makedirs breaks under autofs directories

Antoine Pitrou added the comment: +1 for closing. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14702] os.makedirs breaks under autofs directories

Charles-François Natali added the comment: I still don't like the idea of adding such a kludge to work around OS bugs, so I'd suggest closing as won't fix. -- ___ Python tracker ___

[issue15152] test_subprocess fqailures on awfully slow builtbots

Charles-François Natali added the comment: > You could make the test a loop, with the timeout increasing each time through > the loop, failing only if all tries fail.  That way on faster machines the > test will pass faster.  It'll take even longer on slow machines, but they are > slow anyway

[issue15165] test_email: failure on Windows

Alexander Belopolsky added the comment: Is this something that has to be fixed during the freeze? The fix is trivial: s/1970/1990/g, but I planned to revisit TZ-dependent tests during the beta period. I think we don't use run_with_tz() enough. It would also be great to make it work on wind

[issue15155] sporadic failure in RecvmsgSCTPStreamTest

Changes by Charles-François Natali : -- resolution: -> duplicate status: open -> closed superseder: -> Sporadic failure in test_socket ___ Python tracker ___ __

[issue15165] test_email: failure on Windows

Stefan Krah added the comment: My timezone is CET, so that fits your explanation. Indeed, the failure also occurs on Windows 32-bit. -- title: test_email: failure on Windows 64-bit -> test_email: failure on Windows ___ Python tracker

[issue15165] test_email: failure on Windows 64-bit

Alexander Belopolsky added the comment: I am surprised that we don't see the same failure on 32-bit windows buildbot. Windows mktime does not support negative time_t in either 32 or 64 bit version: http://msdn.microsoft.com/en-us/library/d1y53h2a(v=vs.110).aspx We are probably just lucky and

[issue12268] file readline, readlines & readall methods can lose data on EINTR

Antoine Pitrou added the comment: I don't think setitimer() is the culprit, rather the fact that the timeout is too short. You could try setting it to e.g. 0.4. -- ___ Python tracker _

[issue12415] Missing: How to checkout the Doc sources

Philip Olson added the comment: I think you should make the commit. Also, the aforementioned [old] Subversion reference for Sphinx is a real issue here. And I think the "Without make" section should link to http://sphinx.pocoo.org/ -- ___ Python

[issue10142] Support for SEEK_HOLE/SEEK_DATA

Georg Brandl added the comment: As long as we have a test confirming that SEEK_HOLE/SEEK_DATA are *accepted* by the io module (which is a big part of the patch), it is fine. E.g. calling seek() with the constants and check that it only raises OSError or nothing should work, right? --

[issue15181] importlib.h: suncc warnings

Stefan Krah added the comment: Antoine Pitrou wrote: > > +fprintf(outfile, "%d,", (unsigned int) data[i]); > > > > Hmm, "%u"? :) > > It doesn't change anything, since data[i] is between 0 and 255. > (unless C `int` is 8 bits on your computer, but I doubt it :-)) That's true, but

[issue15181] importlib.h: suncc warnings

Antoine Pitrou added the comment: Le lundi 25 juin 2012 à 15:47 +, Stefan Krah a écrit : > > +fprintf(outfile, "%d,", (unsigned int) data[i]); > > Hmm, "%u"? :) It doesn't change anything, since data[i] is between 0 and 255. (unless C `int` is 8 bits on your computer, but I do

[issue15181] importlib.h: suncc warnings

Stefan Krah added the comment: +fprintf(outfile, "%d,", (unsigned int) data[i]); Hmm, "%u"? :) -- ___ Python tracker ___ ___

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Stefan Krah added the comment: Jeremy Kloth wrote: > I've narrowed this down to a CPU capabilities issue with OpenSSL. > What CPU are you using? I have a Q9450 (Core2 Quad) Core 2 Duo E8500. But I run Windows under Linux/kvm/qemu, in case that matters. -- ___

[issue15181] importlib.h: suncc warnings

Antoine Pitrou added the comment: It should be fixed now! -- nosy: +pitrou resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue15181] importlib.h: suncc warnings

Roundup Robot added the comment: New changeset 6dc9472346de by Antoine Pitrou in branch 'default': Issue #15181: importlib bytecode is unsigned and shouldn't have negative numbers. http://hg.python.org/cpython/rev/6dc9472346de -- nosy: +python-dev _

[issue14814] Implement PEP 3144 (the ipaddress module)

Hynek Schlawack added the comment: Ok I looked into it. It uses str() to convert objects into text representation which it then parses. -- ___ Python tracker ___ __

[issue15180] Cryptic traceback from os.path.join when mixing str & bytes

Antoine Pitrou added the comment: Just a nit, you can use double quotes instead of escaping apostrophes ;) -- nosy: +pitrou ___ Python tracker ___ __

[issue15179] An infinite loop happens when we use SysLogHandler with eventlet

Antoine Pitrou added the comment: > This seems a flawed contract; either connect() should work (in which > case the socket will need closing when it's finished with) or it should > fail, not connect and not require a close call (as it isn't connected) socket.close() closes the file descriptor,

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Antoine Pitrou added the comment: > If I set OPENSSL_ia32cap to 0 the self tests work. I'm now off to > debug OpenSSL CPUID support... :( At this point, I think asking for help on an OpenSSL mailing-list or IRC channel is a good idea. (unless you want to do the debugging yourself, that is :))

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Jeremy Kloth added the comment: I've narrowed this down to a CPU capabilities issue with OpenSSL. What CPU are you using? I have a Q9450 (Core2 Quad) If I set OPENSSL_ia32cap to 0 the self tests work. I'm now off to debug OpenSSL CPUID support... :( -- __

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Stefan Krah added the comment: The openssl self tests also pass here. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue15179] An infinite loop happens when we use SysLogHandler with eventlet

Vinay Sajip added the comment: Why should the socket need closing if the connect fails? This seems a flawed contract; either connect() should work (in which case the socket will need closing when it's finished with) or it should fail, not connect and not require a close call (as it isn't conn

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Stefan Krah added the comment: It worked out of the box for me. These are the versions I use: # openssl version: svn export http://svn.python.org/projects/external/openssl-1.0.1c # nasm version (installer): nasm-2.10.01-installer.exe Let me see what I did: cd openssl-1.0.1c nmake -f ms\nt.m

[issue13698] Mailbox module should support other mbox formats in addition to mboxo

endolith added the comment: > - If the mailbox is written using the mboxrd format and read using the mboxo > format, lines that were meant to start with ">From " are changed to ">>>From > ". This is a new type of corruption. Well, yes. So the choices are: mboxrd as default: Sometimes result

[issue12927] test_ctypes: segfault with suncc

Meador Inge added the comment: Stefan, nope -- I never got a reply. I will try again. -- ___ Python tracker ___ ___ Python-bugs-list

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Jeremy Kloth added the comment: The OpenSSL (64-bit build) does not pass its own tests, while the 32-bit build from the same source works just fine. Stefan, how did you get your 64-bit build to work? -- ___ Python tracker

[issue15180] Cryptic traceback from os.path.join when mixing str & bytes

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

[issue15172] SHA1 failures on the 64-bit Windows buildbot

Antoine Pitrou added the comment: By contrast, 2.7 and 3.2 look ok. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue12927] test_ctypes: segfault with suncc

Changes by Stefan Krah : -- nosy: +Justin.Venus ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue15171] Fix 64-bit building for buildbot scripts (3.2)

Stefan Krah added the comment: The buildbot works with the HOST_PYTHON hack. Should we just leave this as a permanent solution? -- I don't feel like touching the project files for stable releases. [%CD% should probably be quoted in the patch.] -- components: +Build resolution: -> fixe

[issue15178] Doctest should handle situations when test files are not readable

R. David Murray added the comment: Great, thanks. There's a loop around testfiles. I think it would be nicer to not call sys.exit. You could at the same time fix what appears to be a bug in the loop code. It looks like 1 is currently returned only if the last file fails. Hmm, and given th

  1   2   >