[issue13119] Newline for print() is \n on Windows, and not \r\n as expected

STINNER Victor added the comment: > On Windows, stdin, stdout and stderr are creates using TextIOWrapper(..., > newline=None). > In this case, TextIOWrapper._writenl is os.linesep and so '\r\n'. Oh, I was wrong: stdin is created with newline=None, but stdout and stderr are created with newline

[issue12073] regrtest: use faulthandler to dump the tracebacks on SIGUSR1

STINNER Victor added the comment: The change was already done in another issue. I'm closing this one. changeset: 71315:30f91fbfc8b3 user:Victor Stinner date:Wed Jul 13 23:47:21 2011 +0200 files: Lib/test/regrtest.py description: Issue #12550: regrtest displays the Python

[issue15213] _PyOS_URandom documentation

STINNER Victor added the comment: So can we close this issue, or should we start to document private functions? -- ___ Python tracker ___

[issue13992] Segfault in PyTrash_destroy_chain

Manu Cupcic added the comment: I am also hitting this issue. I have been able to reproduce it in python 2.5 and 2.7, on debian 6 (64 bits) Exactly like the reporter, I am making extensive use of threads. I am also using SQLalchemy. All my threads but one are waiting (probably for the GIL) : (g

[issue15520] Document datetime.timestamp() in 3.3 What's New

New submission from Dirkjan Ochtman: It seems nice if datetime.timestamp() would be mentioned in the What's New. Does that seem acceptable? I'm happy to whip up a patch. -- assignee: docs@python components: Documentation messages: 167096 nosy: djc, docs@python priority: normal severity:

[issue15488] Closed files keep their buffer alive

Serhiy Storchaka added the comment: Agree with Meador. -- nosy: +storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8847] crash appending list and namedtuple

Roundup Robot added the comment: New changeset 5a8c5631463f by Martin v. Löwis in branch '2.7': Issue #8847: Disable COMDAT folding in Windows PGO builds. http://hg.python.org/cpython/rev/5a8c5631463f -- nosy: +python-dev ___ Python tracker

[issue15521] Dev Guide should say how to run tests in 2.7

New submission from Chris Jerdonek: The Dev Guide should say the preferred way (or even a way) to run tests using the Python 2.7 build: http://docs.python.org/devguide/runtests.html This will help submitters who want to check that their patch works with 2.7. In Python 2.7, this did not work (

[issue8847] crash appending list and namedtuple

Roundup Robot added the comment: New changeset 2638ce032151 by Martin v. Löwis in branch '3.2': Issue #8847: Disable COMDAT folding in Windows PGO builds. http://hg.python.org/cpython/rev/2638ce032151 New changeset 029cde4e58c5 by Martin v. Löwis in branch 'default': Issue #8847: Disable COMDAT

[issue8847] crash appending list and namedtuple

Martin v. Löwis added the comment: Thanks for the research and the fix! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue15510] textwrap.wrap('') returns empty list

Chris Jerdonek added the comment: I verified that this patch can be applied to 2.7 and that those tests pass as well. -- ___ Python tracker ___ _

[issue15521] Dev Guide should say how to run tests in 2.7

Ezio Melotti added the comment: FWIW this is already mentioned in the quick start [0]. Do you want to propose a patch for runtest.rst? [0]: http://docs.python.org/devguide/#quick-start -- type: -> enhancement ___ Python tracker

[issue15521] Dev Guide should say how to run tests in 2.7

Chris Jerdonek added the comment: > FWIW this is already mentioned in the quick start [0]. I didn't catch that, thanks. > Do you want to propose a patch for runtest.rst? Sure. -- ___ Python tracker _

[issue15037] curses.unget_wch and test_curses fail when linked with ncurses 5.7 and earlier

STINNER Victor added the comment: To debug this issue, it would help to have the following information: - locale encoding: encoding variable - tested character: ch - character read by ncurses: read Can someone reproducing the issue try to add: print("encoding=%s, ch=%r, read=%r" % (encoding,

[issue8847] crash appending list and namedtuple

STINNER Victor added the comment: You didn't add any test for non regression?? -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15522] impove 27 percent performance on stringpbject.c( by prefetch and loop optimization)

New submission from abael: Python-2.7.3/Objects/stringobject.c( SHA256SUM ad7795c75e2a25247e4dea4cc5327c225c4da03b7c7d57226c817ba6d12a316c) static PyObject *string_join(PyStringObject *self, PyObject *orig); OLD IMPLEMENT LOGIC(Pseudo code): char *sep = PyString_AS_STRING(self);

[issue15522] impove 27 percent performance on stringpbject.c( by prefetch and loop optimization)

Changes by abael : -- components: +Interpreter Core -Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue15521] Dev Guide should say how to run tests in 2.7

Chris Jerdonek added the comment: Attaching a patch for review. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file26645/issue-15521-1.patch ___ Python tracker ___

[issue15523] Block on close TCP socket in SocketServer.py

New submission from Jarvis: In the Python 2.4, it closes the socket only by calling request.close() method. There is a risk by using this method to close socket. If the socket handle count does not reach zero because another process still has a handle to the socket then the connection is not c

[issue13072] Getting a buffer from a Unicode array uses invalid format

Stefan Krah added the comment: Is it possible without too much effort to keep the old behavior ('u' -> Py_UNICODE)? Then I'd say that should go into 3.3. The problem with the current behavior is that it's neither backwards compatible nor PEP-3118 compliant. If it is too much work to restore th

[issue13072] Getting a buffer from a Unicode array uses invalid format

STINNER Victor added the comment: Here is a patch reverting changes of the PEP 393, as suggested by Martin von Loewis. With the patch, array uses Py_UNICODE* type for the 'u' format. So array.array('u', '\u0010')[0] should return '\uDBFF' on Windows. -- keywords: +patch Added file:

[issue8847] crash appending list and namedtuple

Martin v. Löwis added the comment: > You didn't add any test for non regression?? Please rephrase your question: what tests did I not add? I did add the tests that Stefan proposed. -- ___ Python tracker ___

[issue15231] update PyPI upload doc to say --no-raw passed to rst2html.py

Chris Jerdonek added the comment: > Please backport and leave open for distutils2. Éric, is there a place where updates to the distutils2 docs can be viewed and made prior to reinclusion in the main Python repo? For example, the documentation here: http://packages.python.org/Distutils2/devre

[issue13992] Segfault in PyTrash_destroy_chain

Charles-François Natali added the comment: > Is there something else I can do to help resolve this bug ? I can help > debugging this, but I am not sure how to proceed. I have a --with-pydebug > interpreter stopped at the segfault in gdb. Could you post the output of : """ p op """ and """ th

[issue13992] Segfault in PyTrash_destroy_chain

Manu Cupcic added the comment: (gdb) p op $12 = (PyObject *) 0x4dc7bc0 thread all apply bt is going to be very long no ? Could you tell me what you want to know that is not in info threads maybe ? I can definitely post it here, but it's going to be a lot of output. I can be available on IRC i

[issue15524] Dict items() ordering varies across interpreter invocations

New submission from Dmitry Dvoinikov: The following line prints different things each time you run it: python3 -c "print(', '.join({ '1': '2', '3': '4' }.keys()))" The output is either "1, 3" or "3, 1". Is such indeterministic behavior intentional ? Using Python 3.3.0b1 (default, Aug 1 2012,

[issue15488] Closed files keep their buffer alive

Antoine Pitrou added the comment: This has to wait for 3.4, since it's an enhancement, not a bug. -- versions: +Python 3.4 -Python 3.3 ___ Python tracker ___

[issue15213] _PyOS_URandom documentation

Antoine Pitrou added the comment: The comment needs to be fixed before the issue is closed. -- ___ Python tracker ___ ___ Python-bugs-

[issue13072] Getting a buffer from a Unicode array uses invalid format

Stefan Krah added the comment: The diff between b9558df8cc58 and default with array_revert_pep393.patch applied is small, but I noticed that in some places you switched back to Py_UNICODE typecode and in others not. For instance, in struct arraydescr typecode is still char. I'm not sure why type

[issue8847] crash appending list and namedtuple

STINNER Victor added the comment: > Please rephrase your question: what tests did I not add? > I did add the tests that Stefan proposed. Ah yes, you added new tests to Python 3.2 and 3.3, but no to Python 2.7. Why not adding these new tests to Python 2.7? -- ___

[issue15524] Dict items() ordering varies across interpreter invocations

Antoine Pitrou added the comment: Yes, because hash randomization is now enabled by default: http://docs.python.org/dev/reference/datamodel.html#object.__hash__ If you want deterministic behaviour, just set e.g. PYTHONHASHSEED=0. (or any other fixed value) -- nosy: +pitrou

[issue13072] Getting a buffer from a Unicode array uses invalid format

STINNER Victor added the comment: > The diff between b9558df8cc58 and default with array_revert_pep393.patch > applied is small, but I noticed that in some places you switched back to > Py_UNICODE typecode and in others not. I just copied code from Python 3.2, I forgot to update typecode type (P

[issue15524] Dict items() ordering varies across interpreter invocations

Changes by Antoine Pitrou : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue15522] impove 27 percent performance on stringpbject.c( by prefetch and loop optimization)

Antoine Pitrou added the comment: Hi, several points: - Python 2.7 is in bugfix mode; you need to work from the default Mercurial branch as explained in http://docs.python.org/devguide/ . In practice, this means your patch will target the future Python 3.4, and therefore either PyUnicode_Join

[issue15425] Another strange Tracebacks with importlib

Nick Coghlan added the comment: Indeed, there are still a couple of Windows failures, but they aren't related to this. -- status: pending -> closed ___ Python tracker ___ __

[issue15525] test_multiprocessing failure on Windows XP

New submission from Nick Coghlan: test_multiprocessing failed on one of the XP buildbots with a permission error: http://buildbot.python.org/all/builders/x86%20XP-4%203.x/builds/7223/steps/test/logs/stdio The immediate rerun also failed, but the one at the end of the test run succeeded. -

[issue13072] Getting a buffer from a Unicode array uses invalid format

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

[issue8847] crash appending list and namedtuple

Martin v. Löwis added the comment: > Ah yes, you added new tests to Python 3.2 and 3.3, but no to Python > 2.7. Why not adding these new tests to Python 2.7? The tests don't crash Python 2.7. So they are not useful as a test whether the bug has been worked-around. I actually don't know how to te

[issue15526] regrtest crash on Windows 7 AMD64

New submission from Nick Coghlan: regrtest bailed out completely on one of the Windows 7 builders due to a problem with accessing the temporary working directory: http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/410/steps/test/logs/stdio It's seems a touch suspicious

[issue15519] finish exposing WindowsRegistryImporter in importlib

Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue15526] regrtest crash on Windows 7 AMD64

Antoine Pitrou added the comment: Well, test_startfile seems to be a common issue on that buildbot. -- nosy: +jeremy.kloth, pitrou ___ Python tracker ___

[issue15522] impove 27 percent performance on stringpbject.c( by prefetch and loop optimization)

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15519] finish exposing WindowsRegistryImporter in importlib

Antoine Pitrou added the comment: I'm not sure why some finders are named "Finder" and others "Importer". It makes things confusing. -- nosy: +pitrou ___ Python tracker ___

[issue15510] textwrap.wrap('') returns empty list

Antoine Pitrou added the comment: Uh, how is this a bug? An empty text doesn't contain lines at all, so returning an empty list of lines sounds right. Furthermore, by "fixing" this, you may break existing software. -- nosy: +pitrou ___ Python tracke

[issue15520] Document datetime.timestamp() in 3.3 What's New

Antoine Pitrou added the comment: Yes, of course. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue15496] harden directory removal for tests on Windows

Jeremy Kloth added the comment: I must also add that the proposed solution works well within the test suite as the access denied error can also occur when creating subsequent files, not just removing them. This solution eliminates the need to wrap all creation calls with access denied handlin

[issue15526] regrtest crash on Windows 7 AMD64

Jeremy Kloth added the comment: > Well, test_startfile seems to be a common issue on that buildbot. I wouldn't really call it common (twice in the last 30 runs). However I would wager that the PermissionError is being caused by an unknown (without having Process Monitor running when the error o

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Barry A. Warsaw added the comment: I've mostly run out of time to work on the docs, but I do want to say that I thought long and hard about all the terminology decisions. Please don't change them lightly, and definitely don't change them until you've tried to go through the documentation and mak

[issue15496] harden directory removal for tests on Windows

Changes by Antoine Pitrou : -- nosy: +brian.curtin stage: -> patch review versions: +Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue15519] finish exposing WindowsRegistryImporter in importlib

Brett Cannon added the comment: The importers can both find and load modules (e.g. BuiltinImporter defines both find_module() and load_module()), while the finders only find modules (e.g. only define find_module()). It's defined in the glossary, so maybe more links to that would help. ---

[issue15519] finish exposing WindowsRegistryImporter in importlib

Antoine Pitrou added the comment: > The importers can both find and load modules (e.g. BuiltinImporter > defines both find_module() and load_module()), while the finders only > find modules (e.g. only define find_module()). Ah, fair enough. I thought loader objects were always distinct from find

[issue15527] Double parents in functions references

New submission from Serhiy Storchaka: :c:func:`PyMem_Malloc(n)` on Doc/c-api/memory.rst:109 rendered in HTML as PyMem_Malloc(1)() (note double parents). There are many other examples on this and other pages. The issue is actual for all modern versions of Python. -- assignee: docs@pytho

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Brett Cannon added the comment: So just to weigh in on this, I think "meta path finder" and "path entry finder" (as Barry stated in the glossary already) clearly delineate what is from sys.meta_path and what is from some path entry hook by having a clarifying word to go with "finder" (either k

[issue6308] termios fix for QNX breaks HP-UX

Dirkjan Ochtman added the comment: Can we have someone take a look at this? It seems fairly innocuous. -- nosy: +djc ___ Python tracker ___ ___

[issue15521] Dev Guide should say how to run tests in 2.7

Ezio Melotti added the comment: Thanks for the patch. I'm not sure it's necessary to add a new section though, unless you are planning to add more differences there. +base command instead of the one described above: :: You can just use "... above::" here. -- _

[issue15527] Double parens in functions references

Changes by Antoine Pitrou : -- title: Double parents in functions references -> Double parens in functions references ___ Python tracker ___

[issue15468] Edit docs to hide hashlib.md5()

Daniel Holth added the comment: re-tweak treatment of md5 in hashlib docs (the SHA-2 family is currently recommended by http://csrc.nist.gov/groups/ST/toolkit/secure_hashing.html) -- Added file: http://bugs.python.org/file26648/hashlib.patch ___ Pyth

[issue15528] Better support for finalization with weakrefs

New submission from Richard Oudkerk: A patch with docs and tests for the idea I suggested on python-ideas: http://comments.gmane.org/gmane.comp.python.ideas/15863 To repeat what I wrote there, the current issues with weakref callbacks include: 1. They are rather low level, and working out

[issue15529] PyIter_Check evaluates to 0 for Python list object

New submission from Tom Tromey: I was debugging this bug reported against gdb: http://sourceware.org/bugzilla/show_bug.cgi?id=14386 It turns out that what went wrong in this code was that PyIter_Check evaluates to 0 when its argument is a Python list. This happens because the PyIter_Check macr

[issue15529] PyIter_Check evaluates to 0 for Python list object

Benjamin Peterson added the comment: That's because lists are iterators not iterable. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker __

[issue15525] test_multiprocessing failure on Windows XP

Roundup Robot added the comment: New changeset b99a82bc2cde by Richard Oudkerk in branch 'default': Issue #15525: Increase timeout when TerminateProcess() fails http://hg.python.org/cpython/rev/b99a82bc2cde -- nosy: +python-dev ___ Python tracker

[issue15525] test_multiprocessing failure on Windows XP

Richard Oudkerk added the comment: I would guess that the process has already terminated (or is being torn down) but the timeout is not long enough to let the parent join child. Let's see if increasing the timeout fixes the failures. -- ___ Python t

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Eric Snow added the comment: @Barry: I'm fine with what you've said. My big concern is that we be really consistent here because of the complexity of the import system. Things are at a point that I think we're pretty close in the regard, so I'm mostly fine if we stay put. My only real regre

[issue15519] finish exposing WindowsRegistryImporter in importlib

Eric Snow added the comment: Also, WindowsRegistryImporter is misnamed. It should be WindowsRegistryFinder (see issue15502). Depending on the patch there, I'll update the one here. -- dependencies: +Meta path finders and path entry finders are different, but share an ABC ___

[issue15519] finish exposing WindowsRegistryImporter in importlib

Eric Snow added the comment: I guess the real question here is if anyone has problems with adding WindowsRegistryFinder to importlib.machinery (and to the importlib docs). If it should stay private than I'd like to throw a _ on the name of the class. The change to importlib.abc would likely

[issue15519] finish exposing WindowsRegistryImporter in importlib

Brett Cannon added the comment: It should be exposed (i.e. if SourcelessFileLoader is documented and exposed then so should WindowsRegistryFinder). -- ___ Python tracker ___ ___

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Brett Cannon added the comment: The patch will have Finder break all subclasses that don't define find_loader which is backwards-incompatible. And if you really want to deprecate Finder you should have a warning in an __init__ method (as one would hope people are calling super() as necessary).

[issue15463] test_faulthandler can fail if install path is too long

Roundup Robot added the comment: New changeset 6e03f9b72c61 by Victor Stinner in branch 'default': Issue #15463: Write a test for faulthandler truncating the name of functions http://hg.python.org/cpython/rev/6e03f9b72c61 -- ___ Python tracker

[issue15463] test_faulthandler can fail if install path is too long

STINNER Victor added the comment: I added a test checking that faulthandler truncates strings to MAX_STRING_LENGTH characters using a very long function name. I consider this issue as done. -- resolution: -> fixed status: open -> closed ___ Python

[issue14811] decoding_fgets() truncates long lines and fails with a SyntaxError("Non-UTF-8 code starting with...")

STINNER Victor added the comment: > Are we going to fix this before 3.3? Any objections to Victor's patch? detect_truncate.patch is now raising an error if a line is longer than BUFSIZ, whereas Python supports lines longer than BUFSIZ bytes (it's just that the encoding cookie is ignored if the

[issue15479] Allow MAX_STRING_LENGTH limits to be changed at runtime

STINNER Victor added the comment: > Sounds totally overkill to me. I changed the maximum length of a string to 500 characters instead of 100. It should be enough for most cases. -- ___ Python tracker _

[issue15213] _PyOS_URandom documentation

STINNER Victor added the comment: > The comment needs to be fixed before the issue is closed. Ah yes, here is a patch updating the comment of _PyOS_URandom() and the doc of the os module. -- keywords: +patch Added file: http://bugs.python.org/file26650/urandom_doc.patch ___

[issue15441] test_posixpath fails on Japanese edition of Windows

Roundup Robot added the comment: New changeset 3edc71ed19e7 by Victor Stinner in branch 'default': Issue #15441: Skip test_nonascii_abspath() of test_genericpath on Windows http://hg.python.org/cpython/rev/3edc71ed19e7 -- nosy: +python-dev ___ Python

[issue15441] test_posixpath fails on Japanese edition of Windows

STINNER Victor added the comment: This issue (the test) should be fixed, see the issue #15478 for the real fix. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue15463] test_faulthandler can fail if install path is too long

Chris Jerdonek added the comment: > I didn't want to write such test, but I can review a patch adding such test. Victor, did you see and review my patch? There is currently no test to check that a long file path (longer than 100 characters) will render, which was the original issue that was f

[issue15463] test_faulthandler can fail if install path is too long

STINNER Victor added the comment: > Victor, did you see and review my patch? There is currently no test to check > that a long file path (longer than 100 characters) will render, which was the > original issue that was fixed. The patch provides such a test. Yes, I saw your patch, but I don't

[issue15530] Enhance Py_MIN and Py_MAX

New submission from STINNER Victor: Attached patch enhances Py_MIN and Py_MAX to check that types of both arguments are compatible at compile time. Checks are only done if the compiler is GCC. The patch uses also Py_MIN and Py_MAX in more places. (The commit may be done in two parts.) ---

[issue15463] test_faulthandler can fail if install path is too long

Chris Jerdonek added the comment: > Yes, I saw your patch, but I don't want to create very long filename. Not all platforms support paths longer than 500 characters. I think you may have a slight misunderstanding. My patch was not meant to test paths over 500 characters. It tests a path *unde

[issue15531] os.path symlink docs missing

New submission from Dave Abrahams: the docs for os.path don't mention the following facts which I think are important (in fact I assumed the facts would be the reverse): os.path.realpath(l) works when l is a broken symbolic link, returning the path to the (missing) target os.path.readlink(l)

[issue15529] PyIter_Check evaluates to 0 for Python list object

Brett Cannon added the comment: I think Benjamin meant to say lists are iterables not iterators. =) -- nosy: +brett.cannon ___ Python tracker ___

[issue13072] Getting a buffer from a Unicode array uses invalid format

Stefan Krah added the comment: array_revert_pep393-2.patch looks good (checked against 7042a83f37e and all following commits that should be kept). -- ___ Python tracker ___ _

[issue15500] Python should support naming threads

Christian Heimes added the comment: +1 win32 supports thread names, too. http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx -- nosy: +christian.heimes ___ Python tracker ___

[issue15468] Edit docs to hide hashlib.md5()

Changes by Christian Heimes : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue15510] textwrap.wrap('') returns empty list

Chris Jerdonek added the comment: Here are additional test cases impacted by this issue: >>> wrap(" ") [] >>> wrap("\n\n\n") [] >>> wrap("\n\n\n", replace_whitespace=False) [] >>> wrap(" \n\n", replace_whitespace=False) [] -- ___ Python tracker <

[issue15530] Enhance Py_MIN and Py_MAX

Martin v. Löwis added the comment: I think that's too late for 3.3. It's not a bug fix. If we use this kind of feature, we either need to declare a minimum supported GCC version (any GCC older than 10 years can be dropped IMO), or check for the specific version of GCC in which all the necessar

[issue9635] Add Py_BREAKPOINT and sys._breakpoint hooks

Dave Malcolm added the comment: Note to self: a messy way of forcing gdb to do the equivalent of a breakpoint directly from Python is: os.kill(os.getpid(), signal.SIGTRAP) -- ___ Python tracker __

[issue15532] "for line in file" is *still* broken in Python 2.7

New submission from Andy Lutomirski: This program: import subprocess, sys p = subprocess.Popen(['bash', '-c', 'while true; do echo x; sleep 1; done'], bufsize=0, stdout=subprocess.PIPE) for line in p.stdout: sys.stdout.buffer.write(line) sys.stdout.flush() sits around and does nothing

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Nick Coghlan added the comment: As a final attempt at giving the path import machinery the emphasis it deserves without misusing the "importer" term, how about: 1. "path import subsystem" for that whole section of the import machinery; and 2. "path import finder" specifically for the meta path fi

[issue15530] Enhance Py_MIN and Py_MAX

STINNER Victor added the comment: > I think that's too late for 3.3. It's not a bug fix. Oops, I chose 3.3 instead of 3.4. Fixed. > If we use this kind of feature, we either need to declare a minimum supported > GCC version typeof() and __builtin_types_compatible_p() were introduced to gcc in

[issue13072] Getting a buffer from a Unicode array uses invalid format

STINNER Victor added the comment: @Georg: are you ok with this change? It reverts the behaviour of Python 3.2 and avoids to have to maintain an API that nobody wants to use ('u' format using Py_UCS4, 32 bits unsigned). -- nosy: +georg.brandl ___ Pyt

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Barry A. Warsaw added the comment: On Aug 01, 2012, at 10:03 PM, Nick Coghlan wrote: >1. "path import subsystem" for that whole section of the import machinery; >and >2. "path import finder" specifically for the meta path finder that >importlib calls "PathFinder" and the new docs currently call

[issue1521950] shlex.split() does not tokenize like the shell

Changes by Vinay Sajip : -- versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14713] PEP 414 installation hook fails with an AssertionError

Changes by Vinay Sajip : -- versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue15525] test_multiprocessing failure on Windows XP

Changes by STINNER Victor : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue15525] test_multiprocessing failure on Windows XP

STINNER Victor added the comment: > Let's see if increasing the timeout fixes the failures. At least, the 3 following builds succeed (let's see the next builds). -- nosy: +haypo ___ Python tracker

[issue15532] "for line in file" is *still* broken in Python 2.7 on pipes

Changes by Andy Lutomirski : -- title: "for line in file" is *still* broken in Python 2.7 -> "for line in file" is *still* broken in Python 2.7 on pipes ___ Python tracker ___ _

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Nick Coghlan added the comment: The problem with "path importer" is it's just plain *wrong*. That object is not an importer and thus calling it one makes it much harder to learn the finder/loader/importer distinctions correctly. "import finder" is only slightly longer than "importer" and has the

[issue15502] Meta path finders and path entry finders are different, but share an ABC

Barry A. Warsaw added the comment: On Aug 01, 2012, at 10:44 PM, Nick Coghlan wrote: >The problem with "path importer" is it's just plain *wrong*. That object is >not an importer and thus calling it one makes it much harder to learn the >finder/loader/importer distinctions correctly. The term "

[issue15321] bdist_wininst installers may terminate with "close failed in file object destructor:\nsys.excepthook is missing\nlost sys.stderr"

Roundup Robot added the comment: New changeset 014b36383a54 by Eli Bendersky in branch '3.2': Issue #15321: update PyPI upload doc to say --no-raw passed to rst2html.py http://hg.python.org/cpython/rev/014b36383a54 -- ___ Python tracker

[issue15231] update PyPI upload doc to say --no-raw passed to rst2html.py

Roundup Robot added the comment: New changeset 29bdbcadf299 by Eli Bendersky in branch '2.7': Issue #15231: update PyPI upload doc to say --no-raw passed to rst2html.py http://hg.python.org/cpython/rev/29bdbcadf299 -- ___ Python tracker

  1   2   >