[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

Richard Oudkerk added the comment: If you have a pending overlapped operation then the associated buffer should not be deallocated until that operation is complete, or else you are liable to get a crash or memory corruption. Unfortunately WinXP provides no reliable way to cancel a pending oper

[issue6208] path separator output ignores shell's path separator: / instead of \

ThurnerRupert added the comment: david, you mentioned working code. i am the opposite of an expert in the source code of python, but i thought i would be able to at least find where the code is for sys.stdout.write and sys.stderr.write, where i thought \ should be replaced by / when running in

[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

STINNER Victor added the comment: "For Vista and later versions of Windows these warnings are presumably unnecessary since CancelIoEx() is used." As close() on regular files, I would prefer to call explicitly cancel() to control exactly when the overlapped operation is cancelled. Can't you fix

[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

Richard Oudkerk added the comment: > As close() on regular files, I would prefer to call explicitly cancel() > to control exactly when the overlapped operation is cancelled. If you use daemon threads then you have no guarantee that the thread will ever get a chance to explicitly call cancel().

[issue6208] path separator output ignores shell's path separator: / instead of \

Nick Coghlan added the comment: You certainly can't replace *all* occurrences of backslash characters with forward slashes when running in a cygwin or msys shell anyway. Backslashes have many uses besides being (annoyingly) Windows path separators. -- _

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

New submission from STINNER Victor: When bytearray_setslice_linear() is called to shrink the buffer with lo=0 and PyByteArray_Resize() fails because of a memory error, the bytearray is leaved in an inconsistent state: ob_start has been updated but not the size. I found the issue using failmall

[issue19437] More failures found by pyfailmalloc

Roundup Robot added the comment: New changeset 8e40d07d3cd2 by Victor Stinner in branch 'default': Issue #19437: Fix PyImport_ImportModuleLevelObject(), handle http://hg.python.org/cpython/rev/8e40d07d3cd2 New changeset a217ea1671a8 by Victor Stinner in branch 'default': Issue #19437: Fix PyCDat

[issue6208] path separator output ignores shell's path separator: / instead of \

Eric V. Smith added the comment: Agreed with Nick. I think it's clear than any change to the behavior will have to take place inside os.path. I just don't know what that change would be. -- ___ Python tracker _

[issue19569] Use __attribute__((deprecated)) to warn usage of deprecated functions and macros

New submission from STINNER Victor: Python C API evolves. For example, the Unicode type has been rewriten for scratch to use a more efficient design. Would it be possible to mark deprecated functions as deprecated, so users will be noticed that the API evolved and Python has better functions?

[issue19570] distutils' Command.ensure_dirname fails on Unicode

New submission from Sascha Peilicke: Encountered an isssue with Unicode paths when invoking Sphinx' distutils command (i.e. 'setup.py build_sphinx'): $ python setup.py build_sphinx running build_sphinx error: 'source_dir' must be a directory name (got `doc/source`) ... (Pdb) l 96

[issue19570] distutils' Command.ensure_dirname fails on Unicode

STINNER Victor added the comment: This is more a feature request than a bug. You should use an encoded path, or upgrade to Python 3 which handles Unicode correctly. -- nosy: +haypo ___ Python tracker _

[issue19569] Use __attribute__((deprecated)) to warn usage of deprecated functions and macros

STINNER Victor added the comment: I just commited a change to avoid PyUnicode_GET_SIZE(): this function doesn't handle errors very well, if PyUnicode_AsUnicode() fails, the result is zero. The caller is unable to know that an error occurred. http://hg.python.org/cpython/rev/28f71af02b69 """ Do

[issue17828] More informative error handling when encoding and decoding

Nick Coghlan added the comment: Patch for the final version that I'm about to commit. - I realised the exception chaining would only trigger for the encode() and decode() methods, when it was equally applicable to the codecs.encode() and codecs.decode() functions, so I updated the test cases a

[issue19343] Expose FreeBSD-specific APIs in resource module

Claudiu.Popa added the comment: Hello. Here's a preliminary patch. -- keywords: +patch nosy: +Claudiu.Popa Added file: http://bugs.python.org/file32596/resource.patch ___ Python tracker

[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

Richard Oudkerk added the comment: I think the attached patch should fix it. Note that with the patch the RuntimeError can probably only occur on Windows XP. Shall I apply it? -- keywords: +patch Added file: http://bugs.python.org/file32597/dealloc-runtimeerror.patch

[issue19567] mimetypes.init() raise unhandled excption in windows

R. David Murray added the comment: This is a duplicate of issue 9291. Can you answer Victor's question over there for us? -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> mimetypes initialization fails on Windows be

[issue9291] mimetypes initialization fails on Windows because of non-Latin characters in registry

Changes by R. David Murray : -- nosy: +adamhj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue19570] distutils' Command.ensure_dirname fails on Unicode

Sascha Peilicke added the comment: Happens since Sphinx-1.2b3, here's some context: https://bitbucket.org/birkenfeld/sphinx/issue/1142 -- ___ Python tracker ___

[issue17828] More informative error handling when encoding and decoding

Roundup Robot added the comment: New changeset 854a2cea31b9 by Nick Coghlan in branch 'default': Close #17828: better handling of codec errors http://hg.python.org/cpython/rev/854a2cea31b9 -- nosy: +python-dev resolution: -> fixed stage: commit review -> committed/rejected status: open

[issue6208] path separator output ignores shell's path separator: / instead of \

Nick Coghlan added the comment: As noted above, it's still not clear the change *can* be implemented at the standard library level - we don't have the context to determine if a Windows native path or a POSIX path is more appropriate when a Windows build is being used in a POSIX environment. >

[issue19571] urlparse.parse_qs with empty string

New submission from stutiredboy: >>> import urlparse >>> urlparse.parse_qs('a=&b=1') {'b': ['1']} >>> why not: {'a' : [''], 'b' : ['1']} is this a bug? -- components: Library (Lib) messages: 202751 nosy: stutiredboy priority: normal severity: normal status: open title: urlparse.parse

[issue17839] base64 module should use memoryview

Roundup Robot added the comment: New changeset e53984133740 by Nick Coghlan in branch 'default': Issue #17839: mention base64 change in What's New http://hg.python.org/cpython/rev/e53984133740 -- ___ Python tracker

[issue19571] urlparse.parse_qs with empty string

R. David Murray added the comment: It is not a bug: >>> parse_qs('a=&b=1', keep_blank_values=True) {'a': [''], 'b': ['1']} -- nosy: +r.david.murray resolution: -> invalid stage: -> committed/rejected status: open -> closed type: -> behavior ___ Py

[issue18861] Problems with recursive automatic exception chaining

Nick Coghlan added the comment: So, I've been pondering the idea of traceback/frame annotations and exception trees a bit. And what I'm wondering is if it may make sense to have the ability to annotate *frames* at runtime, and these annotations can be qualified by module names. So, for exampl

[issue9291] mimetypes initialization fails on Windows because of non-Latin characters in registry

Tim Golden added the comment: Only just been reminded of this one; it's possible that it's been superseded by Issue15207. At the least, that issue resulted in a code change in this area of mimetypes. I'll have a look later. -- nosy: +tim.golden ___

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

STINNER Victor added the comment: Also reproduced on "x86 Ubuntu Shared 3.x" buildbot. http://buildbot.python.org/all/builders/x86%20Ubuntu%20Shared%203.x/builds/9012/steps/test/logs/stdio == ERROR: test_close (test.test_asynci

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

STINNER Victor added the comment: Attached patch should fix this issue. BaseChildWatcher constructors calls set_loop() which calls _do_waitpid_all(). The problem is that _do_waitpid_all() is called before FastChildWatcher own attributes are set. -- keywords: +patch Added file: http://b

[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

STINNER Victor added the comment: >> Can't you fix multiprocessing and/or the unit test to ensure that all >> overlapped operations are completed or cancelled? > On Vista and later, yes, this is done in the deallocator using > CancelIoEx(), although there is still a warning. I don't understand

[issue18861] Problems with recursive automatic exception chaining

Nick Coghlan added the comment: Walter suggested annotating the exceptions directly might work: https://mail.python.org/pipermail/python-dev/2013-November/130155.html However, that potentially runs into nesting problems (e.g. the idna codec invokes the ascii codec), although Walter suggested a

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Guido van Rossum added the comment: Hmm... That fix works, and if you're concerned about the buildbots, by all means check it in. But I think the root cause is a poor API for initializing ChildWatchers. This is currently done at the end of __init__() -- it calls self.set_loop() which is imp

[issue19565] test_multiprocessing_spawn: RuntimeError and assertion error on windows xp buildbot

Richard Oudkerk added the comment: On 13/11/2013 3:07pm, STINNER Victor wrote: >> On Vista and later, yes, this is done in the deallocator using >> CancelIoEx(), although there is still a warning. > > I don't understand. The warning is emitted because an operating is not done > nor cancelled. Wh

[issue19462] Add remove_argument() method to argparse.ArgumentParser

Artem Ustinov added the comment: What is the way to 'hide' the argument from being parsed? E.g. we have self.parser.add_argument('foo') in parent class, how can we modify it in child class so that it would not to appear in --help strings and not populated to child's Namespace? -- _

[issue19462] Add remove_argument() method to argparse.ArgumentParser

paul j3 added the comment: `argparse.SUPPRESS` should do the trick. According to the documentation it can be used with `default` and `help` parameters. -- ___ Python tracker __

[issue19572] Report more silently skipped tests as skipped

New submission from Zachary Ware: (Nosy list copied from #18702) Grepping for "^\s+return$" and "^\s+pass$" in Lib/test turned up several more tests that are silently skipped (along with many legitimate uses of each). The attached patch turns each into a skip in a few various ways, including

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

Serhiy Storchaka added the comment: You can't "un-memmove" because you already lost bytes between new_hi and hi. -- nosy: +pitrou ___ Python tracker ___ _

[issue6208] path separator output ignores shell's path separator: / instead of \

Laurent Birtz added the comment: First, I apologize for my overly harsh tone. A dismissive comment above struck a nerve but that doesn't excuse it. @Lawrence: from my perspective it is a bug: the Python interpreter doesn't handle paths correctly on MinGW as I'd expect. As Nick said, the ide

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Anthony Baire added the comment: I confirm the fix. It is clear that the separation between BaseChildWatcher and its subclasses is far from ideal. The first implementation was clean, but as the patch evolved interactions got complex to the point that BaseChildWatcher should not be considered

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Guido van Rossum added the comment: TBH the test structure is also rather fragile. I need to think about it more; the global state to hold the current test instance smells, as do the various class-level functions (waitpid(), WIFEXITED() etc.) that aren't methods but used as mock functions. T

[issue10734] test_ttk test_heading_callback fails with newer Tk 8.5

Changes by Serhiy Storchaka : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue19572] Report more silently skipped tests as skipped

Serhiy Storchaka added the comment: See also issue19492 and issue19493. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Guido van Rossum added the comment: I pushed Victor's temporary patch so the buildbots can have peace. -- ___ Python tracker ___ ___ P

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Roundup Robot added the comment: New changeset 8e0eeb4cc8fa by Guido van Rossum in branch 'default': asyncio: Temporary fix by Victor Stinner for issue 19566. http://hg.python.org/cpython/rev/8e0eeb4cc8fa -- nosy: +python-dev ___ Python tracker

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Anthony Baire added the comment: I put a cleaner patch here: https://codereview.appspot.com/26220043/ -- ___ Python tracker ___ ___ P

[issue19573] Fix the docstring of inspect.Parameter and the implementation of _ParameterKind

New submission from Antony Lee: The following patch corrects the docstring of `inspect.Parameter`, as the `default` and `annotation` attributes are in fact set to `empty` if no value is provided, and the `kind` attribute is in fact an `int` (more precisely, a `_ParameterKind`). It also reimpl

[issue19570] distutils' Command.ensure_dirname fails on Unicode

Changes by Ned Deily : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue19572] Report more silently skipped tests as skipped

Zachary Ware added the comment: Starting a review of #19492, I realized my original regexs didn't take comments into account. Grepping "^\s+return\s*(#.*)?$" instead turned up a couple more skips, including some in test_tempfile that said "return # ugh, can't use SkipTest", relics of the day

[issue19493] Report skipped ctypes tests as skipped

Zachary Ware added the comment: Grepping with the same regexes I used for #19572 come up with some extra skips in the ctypes tests too; would you like me to create a new patch including them or would you like to do it, Serhiy? -- nosy: +zach.ware __

[issue19492] Report skipped distutils tests as skipped

Changes by Zachary Ware : -- nosy: +zach.ware ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

STINNER Victor added the comment: > Hmm... That fix works, and if you're concerned about the buildbots, by all > means check it in. > (...) > I pushed Victor's temporary patch so the buildbots can have peace. Yes, I'm concerned by buildbots, I would like to check if my last changes did not int

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

STINNER Victor added the comment: (So thanks for having applied my fix.) -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue19574] Negative integer division error

New submission from Vatroslav Suton: integer division obviously uses float division with math.floor, which produces invalid result when result is less than 0, simply try the following 5/2 versus -5/2. Please use math.ceil function for results less than 0. btw is there any way to patch that in _

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

New submission from Bernt Røskar Brenna: Running the following task using concurrent.futures.ThreadPoolExecutor works with max_workers == 1 and fails when max_workers > 1 : def task(): dirname = tempfile.mkdtemp() f_w = open(os.path.join(dirname, "stdout.txt"), "w") f_r = open(os.p

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

Bernt Røskar Brenna added the comment: Simpler task method that still reproduces the problem: def task(): dirname = tempfile.mkdtemp() f_w = open(os.path.join(dirname, "stdout.txt"), "w") e_w = open(os.path.join(dirname, "stderr.txt"), "w") with subprocess.Popen("dir", shell=T

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

STINNER Victor added the comment: > You can't "un-memmove" because you already lost bytes between new_hi and hi. Oh, that's why I prefered a review. You're right, bytes are lost. Here is a different approach which updates the size to ensure that the object is consistent on memory allocation fa

[issue19574] Negative integer division error

R. David Murray added the comment: This is not an aspect of Python that can possibly change, I'm afraid, for backward compatibility reasons. -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Integer division for negat

[issue19574] Negative integer division error

Mark Dickinson added the comment: See also http://docs.python.org/2/faq/programming.html#why-does-22-10-return-3 BTW, integer division does not use float division internally. That would fail for integers too large to be exactly representable as floats. The implementation can be seen in Objec

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

R. David Murray added the comment: It doesn't look like you are waiting for the subprocess to complete (and therefore close the files) before doing the rmtree. What happens if you do that? -- nosy: +r.david.murray ___ Python tracker

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

R. David Murray added the comment: Nevermind, I forgot that the context manager also does the wait. -- ___ Python tracker ___ ___ Pyth

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

R. David Murray added the comment: Most likely this is a case of a virus scanner or file indexer having the file open when rmtree runs. See issue 7443, which was about solving this for our test suite. My last message there asks about exposing the workaround in shutil, but no one appears to h

[issue19576] "Non-Python created threads" documentation doesn't mention PyEval_InitThreads()

New submission from STINNER Victor: While working on a unit test for the issue #14432, I hit a bug. My C thread got the GIL with PyGILState_Ensure(), but it was strange because the main Python thread also had the GIL... Then I saw that gil_created() returned false. The solution is to call PyE

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

Bernt Røskar Brenna added the comment: No indexing and no virus scanner running. Note that it never fails if running in a single thread. IMO, this indicates that external processes interfering is not the problem. -- ___ Python tracker

[issue19575] subprocess.Popen with multiple threads: Redirected stdout/stderr files still open after process close

Bernt Røskar Brenna added the comment: Here's an improved repro script. I believe it demonstrates that it is the combination of subprocess.Popen and threading that causes the problem. Here's the output from my Windows XP VM: *** c:\...> c:\Python33\python.exe repro_improved.py Windows-XP-5.1

[issue19249] Enumeration.__eq__

Ethan Furman added the comment: changeset ca909a3728d3 -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue6208] path separator output ignores shell's path separator: / instead of \

Nick Coghlan added the comment: We can't change os.sep globally for the process because the Windows APIs don't reliably accept forward slashes. Changing it when the Windows binary is run through msys would thus mean potentially breaking currently working applications. Using the Cygwin Python ins

[issue19493] Report skipped ctypes tests as skipped

Serhiy Storchaka added the comment: > Grepping with the same regexes I used for #19572 come up with some extra > skips in the ctypes tests too; would you like me to create a new patch > including them or would you like to do it, Serhiy? Please do this Zachary. -- __

[issue19572] Report more silently skipped tests as skipped

Serhiy Storchaka added the comment: I added some comments on Rietveld to the first patch. In general it LGTM. I will made a review for additional skips tomorrow. I suggest extract importlib related changes in separated issue. Bratt Cannon should review them. -- __

[issue6208] path separator output ignores shell's path separator: / instead of \

Nick Coghlan added the comment: However, coming up with a way to detect that msys is in use, and publishing that information for use by applications like Mercurial, or creating a catalogue of which Windows APIs still don't accept forward slashes as path separators could help the issue progress.

[issue19572] Report more silently skipped tests as skipped

Serhiy Storchaka added the comment: > I will made a review for additional skips tomorrow. Additional skips LGTM. -- ___ Python tracker ___ __

[issue14432] Bug in generator if the generator in created in a C thread

STINNER Victor added the comment: Updated patch for Python 3.4: - remove PyFrameObject.f_tstate attribute: the thread state can be easily retrieved, it is known where it is needed (see the patch). There is one function which doesn't know the thread state: _PyEval_CallTracing(), but this funct

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

Serhiy Storchaka added the comment: Why the object with updated size is more consistent? -- ___ Python tracker ___ ___ Python-bugs-lis

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

STINNER Victor added the comment: This issue is tricky, I will try to explain it. To understand the bug, I wrote the following function: static int _PyByteArray_CheckConsistency(PyByteArrayObject *obj) { assert(obj != NULL); assert(PyByteArray_Check(obj)); assert(Py_SIZE(obj) >= 0)

[issue19183] PEP 456 Secure and interchangeable hash algorithm

Changes by Christian Heimes : Added file: http://bugs.python.org/file32606/ac521cef665a.diff ___ Python tracker ___ ___ Python-bugs-list maili

[issue19183] PEP 456 Secure and interchangeable hash algorithm

Christian Heimes added the comment: Hi Nick, I have updated the patch and the PEP text. The new version has small string hash optimization disabled. The other changes are mostly cleanup, reformatting and simplifications. Can you please do a review so I can get the patch into 3.4 before beta1

[issue16487] Allow ssl certificates to be specified from memory rather than files.

Christian Heimes added the comment: What's the status of this patch? I need a way to load CA certs from memory for another patch of mine. -- ___ Python tracker ___ _

[issue19566] ERROR: test_close (test.test_asyncio.test_unix_events.FastChildWatcherTests)

Roundup Robot added the comment: New changeset eb42adc53923 by Guido van Rossum in branch 'default': asyncio: Fix from Anthony Baire for CPython issue 19566 (replaces earlier fix). http://hg.python.org/cpython/rev/eb42adc53923 -- ___ Python tracker <

[issue9816] random.jumpahead and PRNG sequence independence

Craig McQueen added the comment: I notice that the C++11 library has a discard() member function for its random generators, which is effectively a jumpahead operation. It seems that the C++11 library has implemented discard() for the Mersene Twister generator. If jumpahead() is technically pos

[issue9816] random.jumpahead and PRNG sequence independence

Craig McQueen added the comment: C++11 Mersenne Twister discard() member function: http://www.cplusplus.com/reference/random/mersenne_twister_engine/discard/ -- ___ Python tracker ___

[issue9816] random.jumpahead and PRNG sequence independence

Craig McQueen added the comment: StackOverflow question about Mersenne Twister jumpahead: http://stackoverflow.com/q/4184478/60075 which refers to this: http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/JUMP/index.html -- ___ Python tracker

[issue6208] path separator output ignores shell's path separator: / instead of \

Laurent Birtz added the comment: I agree with the "no magic bullet" point and that Microsoft is fully to blame for the situation. About the catalogue of Windows APIs that accept slashes. I've read in various places that the only problematic case is the legacy shell API. The power shell seems

[issue19577] memoryview bind (the opposite of release)

New submission from mpb: I'm writing Python code to parse binary (byte oriented) data. I am (at least somewhat) aware of the performance implications of various approaches to doing the parsing. With performance in mind, I would like to avoid unnecessary creation/destruction/copying of memory/

[issue17828] More informative error handling when encoding and decoding

Roundup Robot added the comment: New changeset 99ba1772c469 by Christian Heimes in branch 'default': Issue #17828: va_start() must be accompanied by va_end() http://hg.python.org/cpython/rev/99ba1772c469 -- ___ Python tracker

[issue19578] del list[a:b:c] doesn't handle correctly list_resize() failure

New submission from STINNER Victor: "del list[start:stop:step]" instruction doesn't handle list_resize() failure when step != 1. Attached patch notifies the caller that list_resize() fails. On case of failure, the list is modified (items are deleted), it's just that list buffer could be small

[issue19568] bytearray_setslice_linear() leaves the bytearray in an inconsistent state on memory allocation failure

STINNER Victor added the comment: See also issue #19578, similar issue in list. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue19578] del list[a:b:c] doesn't handle correctly list_resize() failure

Changes by STINNER Victor : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue19437] More failures found by pyfailmalloc

Roundup Robot added the comment: New changeset eea54395797c by Victor Stinner in branch 'default': Issue #19437: Fix fold_unaryops_on_constants() of the peephole optimizer, clear http://hg.python.org/cpython/rev/eea54395797c New changeset 7d0323556c53 by Victor Stinner in branch 'default': Issue

[issue17828] More informative error handling when encoding and decoding

Roundup Robot added the comment: New changeset 26121ae22016 by Christian Heimes in branch 'default': Issue #17828: _PyObject_GetDictPtr() may return NULL instead of a PyObject** http://hg.python.org/cpython/rev/26121ae22016 -- ___ Python tracker

[issue17828] More informative error handling when encoding and decoding

Christian Heimes added the comment: Coverity has found two issues in your patch. I have fixed them both. -- nosy: +christian.heimes ___ Python tracker ___ ___

[issue19579] test_asyncio: test__run_once timings should be relaxed

New submission from STINNER Victor: On Windows, the monotonic timer has a resolution of 15 ms in the worst case. The timing should accept a greater error. http://buildbot.python.org/all/builders/x86%20XP-4%203.x/builds/9547/steps/test/logs/stdio

[issue6208] path separator output ignores shell's path separator: / instead of \

Terry J. Reedy added the comment: subprocess has a 'shell=True' option, although its use is discouraged unless really necessary. To pursue this, I suggest running the test suite on Windows (including xp) with os.sep changed. -- ___ Python tracker <

[issue19576] "Non-Python created threads" documentation doesn't mention PyEval_InitThreads()

Antoine Pitrou added the comment: Perhaps we can fix PyGILState to call PyEval_InitThreads automatically? -- ___ Python tracker ___ __

[issue19577] memoryview bind (the opposite of release)

Antoine Pitrou added the comment: > In the context of the above example, I think it might be nice if I > could rebind an existing memoryview to a new object. It would be nice how so? Can you try to estimate the speed gain? -- nosy: +pitrou ___ Python

[issue19563] Changing barry's email to ba...@python.org

Antoine Pitrou added the comment: Do we want to cut a new release quickly in order to spread the fix? -- nosy: +pitrou ___ Python tracker ___

[issue19371] timing test too tight

Changes by Antoine Pitrou : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue19371] timing test too tight

Changes by Guido van Rossum : -- resolution: -> duplicate superseder: -> test_asyncio: test__run_once timings should be relaxed ___ Python tracker ___ _

[issue19579] test_asyncio: test__run_once timings should be relaxed

Changes by Guido van Rossum : -- nosy: +ezio.melotti, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue19291] Add docs for asyncio package (Tulip, PEP 3156)

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue19579] test_asyncio: test__run_once timings should be relaxed

Roundup Robot added the comment: New changeset f91550e7e2b7 by Guido van Rossum in branch 'default': asyncio: Relax timing requirement. Fixes issue 19579. http://hg.python.org/cpython/rev/f91550e7e2b7 -- nosy: +python-dev ___ Python tracker

[issue19577] memoryview bind (the opposite of release)

mpb added the comment: It would be nice in terms of avoiding malloc()s and free()s. I could estimate it in terms of memoryview creations per message parse. I'll be creating 10-20 memoryviews to parse each ~100 byte message. So... I guess I'd have to build a test to see how long a memoryview