[issue26959] pickle: respect dispatch for functions again

Changes by SilentGhost : -- nosy: +alexandre.vassalotti, pitrou stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list ma

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Serhiy Storchaka added the comment: Yet one difference is that kwargs can be NULL in C function if no keyword arguments are supplied. Here is a patch that adds tests for exact types of args and kwargs arguments in C functions. I think that we should keep passing NULL as kwargs for performance

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Changes by Serhiy Storchaka : Removed file: http://bugs.python.org/file42742/test_args_kwargs_types.patch ___ Python tracker ___ ___ Python-bu

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file42743/test_args_kwargs_types.patch ___ Python tracker ___ ___ Python-bugs

[issue26931] android: test_distutils fails

Xavier de Gaye added the comment: The last two failed tests: test_sysconfig_compiler_vars test_sysconfig_module are caused by LDFLAGS being set in the environment both when configure is run and when make is run. Removing LDFLAGS from the environment when running make fixes these tests.

[issue26931] android: test_distutils fails

Xavier de Gaye added the comment: The attached patch skips some tests when the interpreter was cross-compiled. When the interpreter has been cross-compiled, there is probably no compiler on the host system. -- keywords: +patch Added file: http://bugs.python.org/file42744/cross-compiled

[issue26931] android: test_distutils fails

Xavier de Gaye added the comment: On android, the shell path is /system/bin/sh. The attached patch fixes this, assuming that there is a platform.android_ver() as per issue #26855: add platform.android_ver() for android. This could be changed for a test on sys.platform if there was a specific s

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Serhiy Storchaka added the comment: Proposed patch converts var-keyword arguments to exact dict. Since it changes the behavior of str.format() it can be pushed only in 3.6. -- Added file: http://bugs.python.org/file42746/ceval_kwargs_exact_dict.patch ___

[issue15753] No-argument super in method with variable arguments raises SystemError

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

[issue26970] Replace OpenSSL's CPRNG with system entropy source

Changes by Cory Benfield : -- nosy: +Lukasa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue26970] Replace OpenSSL's CPRNG with system entropy source

New submission from Christian Heimes: The patch adds a new RAND engine for OpenSSL. The engine uses the system's entropy source (/dev/urandom, CryptGenRandom(), getentropy() ...). The engine is automatically installed with OpenSSL as default RAND engine. The new engine fixes the fork() bug onc

[issue15071] TLS get keys and randoms

Christian Heimes added the comment: This request is an advanced use case. I'd rather keep the Python _ssl module simple and suggest PyOpenSSL + PyCA/cryptography for advanced features. -- status: open -> languishing versions: +Python 3.6 -Python 3.4

[issue26959] pickle: respect dispatch for functions again

Hrvoje Nikšić added the comment: You can simplify pickle_lambda in the test by using marshal.dumps(code_obj) and marshal.loads(code_obj) to dump and load the code object without going through its entire guts. It would be a shame to have to change a pickle test just because some detail of the c

[issue26756] fileinput handling of unicode errors from standard input

Changes by Serhiy Storchaka : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue26970] Replace OpenSSL's CPRNG with system entropy source

Antoine Pitrou added the comment: What are the helper methods good for? I don't think we want to expose them for now. -- ___ Python tracker ___ _

[issue26970] Replace OpenSSL's CPRNG with system entropy source

Christian Heimes added the comment: I have used the helper methods during development. They are also used in unit tests. -- ___ Python tracker ___ __

[issue26970] Replace OpenSSL's CPRNG with system entropy source

Antoine Pitrou added the comment: Then I'd say just keep them private. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue17765] weakref.ref ignores a 'callback' keyword argument

Serhiy Storchaka added the comment: no_weakref_kwargs_2.patch LGTM. -- components: +Extension Modules nosy: +serhiy.storchaka stage: needs patch -> commit review type: enhancement -> behavior versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4 _

[issue26870] Unexpected call to readline's add_history in call_readline

Changes by Tyler Crompton : -- keywords: +patch Added file: http://bugs.python.org/file42748/set_auto_history.patch ___ Python tracker ___ ___

[issue26870] Unexpected call to readline's add_history in call_readline

Changes by Tyler Crompton : -- status: pending -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue26870] Unexpected call to readline's add_history in call_readline

Tyler Crompton added the comment: I couldn't think of a way to test input() with the unittest module without bypassing readline or requesting the input from the user. With that said, this informal script verifies proper behavior. -- status: open -> pending Added file: http://bugs.pytho

[issue1528167] Tweak to make string.Templates more customizable

Serhiy Storchaka added the comment: I seconded Raymond. Now the approach is argued against twice. And the patch itself is outdated. I suggest to close this issue. If somebody want to implement Raymond's idea, his can reopen this issue or open new issue. -- nosy: +serhiy.storchaka

[issue13173] Default values for string.Template

Changes by Serhiy Storchaka : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python

[issue26939] android: test_functools hangs on armv7

Chi Hsuan Yen added the comment: FWIW, test_functools passes on ASUS Zenfone 2 Laser ZE500KL with stock ROM (rooted) and my patchset. [1] The CPU is ARM64 and the Python is built as 32-bit ARM binaries. test_threading (#26941) and test_importlib (#26940) pass, too. test_concurrent_futures (#26

[issue26959] pickle: respect dispatch for functions again

Vsevolod Velichko added the comment: I was trying to avoid additional imports in the test. But your point of view seems more reasonable, so I reupload the fixed patch. -- Added file: http://bugs.python.org/file42751/function_pickle.patch ___ Python tr

[issue20291] Argument Clinic should understand *args and **kwargs parameters

Serhiy Storchaka added the comment: I think at first step we can support var-positional parameter only when there are no other positional parameters, and var-keyword parameter only when there are no other keyword parameters. So print, max and dict.update will be supported, but __build_class__,

[issue26156] Bad name into power operator syntax

Robert Jordens added the comment: Ack to the new patch. It is semantically confusing that the await expression also served as the power base without any await. -- ___ Python tracker ___

[issue26537] ConfigParser has optionxform, but not sectionxform

Xiang Zhang added the comment: I write a patch to add sectionxform. It wraps necessary section name operation I think. Hope to have some feedback. -- keywords: +patch Added file: http://bugs.python.org/file42752/add_sectionxform.patch ___ Python trac

[issue15786] IDLE code completion window can hang or misbehave with mouse

suddha sourav added the comment: I reported the issue in 2012, and it's not nice to see that in four years the flagship editor of Python in all platforms I know is still something I have to avoid. I am not writing this mail to vent; I'm asking: what can we do, and through which channels we can go

[issue26939] android: test_functools hangs on armv7

Antoine Pitrou added the comment: I suspect this bug is caused by memory ordering differences between x86 and ARM (see https://en.wikipedia.org/wiki/Memory_ordering#Runtime_memory_ordering ), which is why it may not reproduce easily (may depend on the particular CPU implementation and/or vario

[issue26939] android: test_functools hangs on armv7

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

[issue25745] Reference leaks in test_curses

Berker Peksag added the comment: In case someone wants to work on this, the suspicious tests are test_userptr_memory_leak and test_userptr_segfault. See also issue 18113. -- nosy: +berker.peksag stage: -> needs patch versions: +Python 3.5 ___ Python

[issue26939] android: test_functools hangs on armv7

Antoine Pitrou added the comment: Xavier, as a strating point, can you try the following patch? (atomic_explicit.patch) If it solves the issue, can you also measure the performance drop compared to unpatched (on a non-debug build)? `python -m test.pystone` should be sufficient. -- keyw

[issue21890] wsgiref.simple_server sends headers on empty bytes

Changes by Berker Peksag : -- nosy: +berker.peksag stage: -> patch review versions: +Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ __

[issue17888] docs: more information on documentation team

Berker Peksag added the comment: issue17888.patch looks good to me. I'd probably remove the "necessary skills" part. -- nosy: +berker.peksag stage: needs patch -> patch review versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue20971] HTML output of difflib

Changes by Berker Peksag : -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Modernize HTML output of difflib.HtmlDiff.make_file() ___ Python tracker ___

[issue25745] Reference leaks in test_curses

Serhiy Storchaka added the comment: Thank you for the tip Berker. Now I see how to fix the leak. -- assignee: -> serhiy.storchaka ___ Python tracker ___

[issue25974] Fix statistics.py after the Decimal.as_integer_ratio() change

Berker Peksag added the comment: statistics_as_integer_ratio.diff has been committed in 7b2fafd78c1d. -- nosy: +berker.peksag resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker

[issue26002] make statistics.median_grouped more efficient

Changes by Berker Peksag : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue20554] Use specific asserts in optparse test

Berker Peksag added the comment: The patch looks simple, but I don't see much gain to apply it since optparse is a deprecated module. I'm in favor of closing this as 'wont fix'. -- priority: normal -> low ___ Python tracker

[issue25745] Reference leaks in test_curses

Serhiy Storchaka added the comment: Here is simple patch that fixes a leak. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file42754/curses_panel_dealloc_userptr.patch ___ Python tracker

[issue20554] Use specific asserts in optparse test

Changes by Serhiy Storchaka : -- resolution: -> wont fix stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue12135] The spawn function should return stderr.

Changes by Berker Peksag : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue18841] math.isfinite fails with Decimal sNAN

Changes by Berker Peksag : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue17888] docs: more information on documentation team

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue22107] tempfile module misinterprets access denied error on Windows

Serhiy Storchaka added the comment: Billy, no, the parent directory is tested intentionally. If it isn't a directory, we should fail. May be there is a way to distinguish a failure because the name is already used for a subdirectory from a failure because we don't have permission to create a

[issue26282] Add support for partial keyword arguments in extension functions

Serhiy Storchaka added the comment: If there are no objections I'm inclined to commit pyarg_parse_positional_only_and_keywords_2.patch in short time. -- assignee: -> serhiy.storchaka ___ Python tracker __

[issue26156] Bad name into power operator syntax

R. David Murray added the comment: Sounds like it is a bit more than just confusion: given that power can be used outside a coroutine but await can't, Serhiy's formulation would seem to me to be more semantically correct, even if syntactically it is the same as the current. I think it would r

[issue26939] android: test_functools hangs on armv7

Xavier de Gaye added the comment: Android has stdatomic.h and HAVE_STD_ATOMIC is defined. The build fails with the patch, see the errors in the attached file. This is the native compilation of python, the patches in my build system are also applied to the native build so that they can be check

[issue26967] argparse: allow_abbrev=False stops -vv from working

Michael Kruse added the comment: I think the allow_abbrev option should be orthogonal on how short options are parsed. I am using parse_known_args() to forward the unrecognized args to another program, therefore allow_abbrev=False is essential. There is a special handling for short options in

[issue26939] android: test_functools hangs on armv7

Antoine Pitrou added the comment: Oops, sorry, hadn't seen the patch didn't compile. Can you tried with this new patch? (atomic_explicit2.patch) -- Added file: http://bugs.python.org/file42756/atomic_explicit2.patch ___ Python tracker

[issue26632] __all__ decorator

Barry A. Warsaw added the comment: Here's a C implementation. I'm a bit under the weather so please do double check my refcounting logic. ;) No tests or docs yet, but those would be easy to add. Here's an example: @public class Foo: pass public(qux=3) print(qux) @public def zzz():

[issue1528167] Tweak to make string.Templates more customizable

Barry A. Warsaw added the comment: Agreed with Serhiy. Raymond's approach is nicer, but I'm still not convinced about the use case. Closing. If someone wants to run with this again, an updated patch would be needed, and the issue could be reopened, but I also suggest following through with

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Changes by Barry A. Warsaw : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Barry A. Warsaw added the comment: Eric should chime in on the str.format() implications. -- ___ Python tracker ___ ___ Python-bugs-li

[issue26632] __all__ decorator

Barry A. Warsaw added the comment: I think I missed a decref. New diff. -- Added file: http://bugs.python.org/file42758/26632-in-c-2.diff ___ Python tracker ___

[issue26939] android: test_functools hangs on armv7

Xavier de Gaye added the comment: Still hangs at test_lru_cache_threaded with this last patch :( -- ___ Python tracker ___ ___ Python-

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Eric V. Smith added the comment: I think it's okay to change this as far as str.format() goes. Interestingly enough, the motivating case to add str.format_map() in issue 6081 was exactly this kind of code. Although I notice that the example in that issue, which it shows as failing, works in bo

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Guido van Rossum added the comment: Can't you easily write such a policy yourself? Why does it have to be a standard part of asyncio? -- ___ Python tracker ___ __

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Barry A. Warsaw added the comment: On May 06, 2016, at 03:41 PM, Eric V. Smith wrote: >I agree it would be a 3.6 only change (and I've change the versions to >reflect that). The reason the other versions were included was because this was originally reported as a documentation bug. It should p

[issue25628] Make namedtuple "verbose" and "rename" parameters into keyword only arguments

Guido van Rossum added the comment: And by "safely" I mean that I don't mind if some code breaks when they upgrade to a new feature release. FWIW the code most likely to break is code that wraps these functions with an identical interface. -- ___ P

[issue25628] Make namedtuple "verbose" and "rename" parameters into keyword only arguments

Guido van Rossum added the comment: I think such a change can be safely made in a feature release (say 3.6) without further deprecation. But not in a bugfix release (say 3.5.2). -- ___ Python tracker _

[issue26632] __all__ decorator

Serhiy Storchaka added the comment: Added a couple of comments on Rietveld. But sorry, the overall idea looks unpythonic to me. I'm strong -1. -- ___ Python tracker ___

[issue26939] android: test_functools hangs on armv7

Xavier de Gaye added the comment: > Can you post the backtraces of all threads (at least the innermost frames)? There are two threads, gdb does not print the backtrace of the other thread. My current gdb setup with a connection to a gdb-server misses some stuff (access to the loader or some li

[issue25628] Make namedtuple "verbose" and "rename" parameters into keyword only arguments

Serhiy Storchaka added the comment: Then namedtuple_keywords.diff LGTM. But please document changes. -- assignee: -> rhettinger stage: patch review -> commit review ___ Python tracker _

[issue26906] format(object.__reduce__) fails intermittently

Guido van Rossum added the comment: Sadly it's been a very long time since I wrote that code and I don't recall much about it. I presume there was a good reason for not to do it in _PyType_Lookup(), but who knows -- maybe the oroginal approach was just too naive and nobody cared? I'm not excited

[issue18726] json functions have too many positional parameters

Serhiy Storchaka added the comment: Guido's decision on similar issue25628 is that changing keyword-or-positional parameters to keyword-only is safe and can be made without deprecation. If we started the deprecation period in 3.4, we could finish it in 3.6. Proposed simple patch changes all op

[issue26156] Bad name into power operator syntax

Guido Treutwein added the comment: I'm with David here, in that a change would improve ease of comprehension: I still find it strange, that the grammar symbol has the same name as the keyword (or in the proposed version keyword+'expr'), which is never done on more widely used levels. I would have

[issue18726] json functions have too many positional parameters

Guido van Rossum added the comment: > Guido's decision on similar issue25628 is that changing keyword-or-positional > parameters to keyword-only is safe and can be made without deprecation. > If we started the deprecation period in 3.4, we could finish it in 3.6. That makes little sense. You c

[issue18531] Undocumented different between METH_KEYWORDS and **kws

Eric V. Smith added the comment: Okay. Adding back 3.5 and 2.7, in case someone wants to document the behavior there. I'm not sure if we fix docs in 3.4 still. -- versions: +Python 2.7, Python 3.5 ___ Python tracker

[issue26939] android: test_functools hangs on armv7

Xavier de Gaye added the comment: The strace of test_lru_cache_threaded: ... gettimeofday({1462553238, 580860}, NULL) = 0 clock_gettime(CLOCK_REALTIME, {1462553238, 581276772}) = 0 gettimeofday({1462553238, 581672}, NULL) = 0 clock_gettime(CLOCK_REALTIME, {1462553238, 582078767}) = 0 gettimeofda

[issue18726] json functions have too many positional parameters

Serhiy Storchaka added the comment: My remark was just about that I proposed to start a deprecation period at the time of developing Python 3.4. If this did accepted, the deprecation period would already finished and we would come up to the same code in 3.6. It doesn't matter now. --

[issue26632] __all__ decorator

Barry A. Warsaw added the comment: Updated. -- Added file: http://bugs.python.org/file42760/26632-in-c-3.diff ___ Python tracker ___ _

[issue11063] uuid.py module import has heavy side effects

Michael Felt added the comment: I cannot comment on uuid directly, but for me, this is yet another example of how assumptions can break things. imho - if you know the exact version of s shared library that you want, calling cdll directly should be find. Maybe find_library is historic. However

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

R. David Murray added the comment: Can we at least make it part of the documentation? It's not obvious to me, at least, how to do it. (Maybe I just haven't thought about it carefully enough.) For that matter, it wasn't obvious to me it could even be done, so I've been passing loop everywher

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Yury Selivanov added the comment: > Currently if one needs lazily resolve event loop depending on where awaitable > is being awaited have to pass loop everywhere explicitly. That quickly > becomes an unnecessary noise in interfaces of callables. Why don't you just use 'loop = asyncio.get_even

[issue26632] __all__ decorator

R. David Murray added the comment: "This will cause more problems than it solves" and "this looks unpythonic" are, IMO, not strong arguments against it without butressing discussion. If we can have some examples of problems it will cause, or a concrete explanation of wy something that makes c

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

R. David Murray added the comment: Because, as indicated by the OP, I'm not using the default event loop of the thread. Thinking about my code, I now remember that the reason I went down this path was because I wanted to make sure that my functions, like asyncio functions, accepted the option

[issue26939] android: test_functools hangs on armv7

Antoine Pitrou added the comment: > Still hangs at test_lru_cache_threaded with this last patch :( What about the other tests (test_importlib, test_threading)? Do you know in which precise test it hangs? (use "-v" to print test names) > There are two threads, gdb does not print the backtrace o

[issue26967] argparse: allow_abbrev=False stops -vv from working

Xiang Zhang added the comment: I agree with you. But right now, it seems parsing short options and allow_abbrev both rely on the same logic. If you turn off allow_abbrev, short options parsing also disabled. Separating them seems nontrivial. -- ___

[issue26163] FAIL: test_hash_effectiveness (test.test_set.TestFrozenSet)

Serhiy Storchaka added the comment: I can stably reproduce this. PYTHONHASHSEED=36 ./python -m test.regrtest -vm test_hash_effectiveness test_set -- nosy: +serhiy.storchaka ___ Python tracker

[issue26889] Improve Doc/library/xmlrpc.client.rst

Terry J. Reedy added the comment: This is my first reading of this doc. The formatting improvements look good. A definite enhancement. Review contains a few comments. My main difficulty is separating creation of a proxy instance from use of a proxy instance. Some of the creation parameters

[issue26903] ProcessPoolExecutor(max_workers=64) crashes on Windows

Terry J. Reedy added the comment: The example runs fine, in about 1 second, on my 6 core (which I guess is 12 logical cores) Pentium. I am guessing that the default number of workers needs to be changed, at least on Windows, to min(#logical_cores, 60) -- nosy: +bquinlan, terry.reedy

[issue26941] android: test_threading hangs on armv7

Xavier de Gaye added the comment: Adding the back trace. -- Added file: http://bugs.python.org/file42761/test_threading_gdb_bt.txt ___ Python tracker ___

[issue26906] format(object.__reduce__) fails intermittently

Terry J. Reedy added the comment: Is there a way to have format() try to force the initialization, by explicitly doing the equivalent of obj.__format__, at least for types, instead of raising the TypeError? -- nosy: +terry.reedy ___ Python tracker

[issue26906] format(object.__reduce__) fails intermittently

Guido van Rossum added the comment: But the problem isn't limited to format()... Why would format() be special? -- ___ Python tracker ___

[issue26940] android: test_importlib hangs on armv7

Xavier de Gaye added the comment: Adding gdb backtrace. -- Added file: http://bugs.python.org/file42762/test_importlib_gdb_bt.txt ___ Python tracker ___ _

[issue26938] android: test_concurrent_futures hangs on armv7

Xavier de Gaye added the comment: The strace output, the process is blocked in a futex system call: root@generic:/ # strace -p 1304 Process 1304 attached futex(0xb6f24880, FUTEX_WAIT_PRIVATE, 2, NULL -- ___ Python tracker

[issue26889] Improve Doc/library/xmlrpc.client.rst

Serhiy Storchaka added the comment: Thank you for your review Terry. Updated patch addresses most of your comments. But I'm unable to expand ServerProxy description as you suggest. May you can do this? My purpose was modest. Just fix some incorrect and outdated sentences. Then I fixed some for

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Ilya Kulakov added the comment: > Why does it have to be a standard part of asyncio? I've only seen few libraries that deal with asyncio so far (aiohttp, pyzmq), but my general impression is that this is a generic problem. With asyncio code should be (ideally) written as a set of coroutines wh

[issue26911] lib2to3/tests/pytree_idempotency.py has a broken import

Roundup Robot added the comment: New changeset 3279c910d0e0 by Terry Jan Reedy in branch '3.5': Issue 26911: fix import (other problems remain). https://hg.python.org/cpython/rev/3279c910d0e0 -- nosy: +python-dev ___ Python tracker

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Yury Selivanov added the comment: > Probably it would make sense to modify behavior of the default policy to make > get_event_loop to return Thread-local event loop when called from > out-of-event-loop and return currently running event loop when called from > within a coroutine. The problem

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Yury Selivanov added the comment: To clarify: the problem lies in "return currently running event loop when called from within a coroutine" -- what if there is no GIL and we have a few event loops running? You'd need to use a threadlocal storage. In this case I'm not sure how this is differe

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Ilya Kulakov added the comment: > In this case I'm not sure how this is different from the current > "get_event_loop" Thread may have multiple event loops, but only one, explicitly associated, is default. And it's not necessary one which is currently running. I think what I propose here can b

[issue26906] format(object.__reduce__) fails intermittently

Serhiy Storchaka added the comment: There is one test (ClassPropertiesAndMethods.test_mutable_bases_with_failing_mro in test_descr) that crashes with the code from issue551412 because _PyType_Lookup() is recursive called from PyType_Ready(). Is this the reason? My patch prevents recursive cal

[issue26939] android: test_functools hangs on armv7

Xavier de Gaye added the comment: > Do you know in which precise test it hangs? They are named in the first msg of each issue, the issues are: issue #26938: android: test_concurrent_futures hangs on armv7 issue #26939: android: test_functools hangs on armv7 issue #26940: android: tes

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Yury Selivanov added the comment: > Thread may have multiple event loops, but only one, explicitly associated, is > default. And it's not necessary one which is currently running. Ah, I got it. You know what, this actually is starting to make sense. Guido, what do you think about this? Essen

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Guido van Rossum added the comment: Honestly I think it's pretty crazy and out there to have multiple event loops in the same thread. That feels like an anti-pattern inspired by some other event loop APIs (in other languages) that encourage this. But asyncio was not designed for that. --

[issue26906] format(object.__reduce__) fails intermittently

Guido van Rossum added the comment: Probably. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue26969] ascynio should provide a policy to address pass-loop-everywhere problem

Yury Selivanov added the comment: > Honestly I think it's pretty crazy and out there to have multiple event loops in the same thread. That feels like an anti-pattern inspired by some other event loop APIs (in other languages) that encourage this. But asyncio was not designed for that. I agree.

  1   2   >