(Due to idle-dev mailing list low traffic, this mail was sent to
python-dev and idle-dev)
Hi all,
I'm now trying to figure out IDLE internal relation.
I got some module dependency graph and count.
The work is at HackMD:
https://hackmd.io/IwNg7AphDGBmsFoAsBOCAmZAGMBDBKsArEgruuiEkQCa5YBGsNQA
Is
On 13 June 2017 at 19:48, Victor Stinner wrote:
> While I'm not opposed to PYTHONCOERCECLOCALE=warn, I'm not sure that
> *developers* will use it. Usually, developers don't care of Unicode
> until enough users complain that their application don't work on a
> specific configuration on a specific p
On 13 June 2017 at 19:07, Victor Stinner wrote:
> Ok, if you want to have a more concrete example of regression
> introduced by this warning, look at test_tracemalloc failures on this
> FreeBSD buildbot:
> http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/419/s
2017-06-13 8:51 GMT+02:00 Nick Coghlan :
> If we turned the warning off by default, but retained an easy
> "on-switch" for the warning to help track places where locale coercion
> is triggering unexpectedly (e.g. "PYTHONCOERCECLOCALE=warn"), that
> would probably give us the best of both worlds.
H
Ok, if you want to have a more concrete example of regression
introduced by this warning, look at test_tracemalloc failures on this
FreeBSD buildbot:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/419/steps/test/logs/stdio
I expect that a *lot* of tests usin
On Tue, Jun 13, 2017 at 12:10 AM, Nick Coghlan wrote:
>
> reporting failures from concurrent.futures.wait:
> https://pythonhosted.org/futures/#concurrent.futures.wait
Yeah, and asyncio.gather is another example in the stdlib. Or there's
twisted's DeferredList. Trio is unusual in effectively for
On Tue, Jun 13, 2017 at 2:26 AM, Nathaniel Smith wrote:
> On Mon, Jun 12, 2017 at 6:29 AM, Stefan Ring wrote:
>>
>> > Yury in the comment for PR 2108 [1] suggested more complicated code:
>> >
>> > do_something()
>> > try:
>> > do_something_other()
>> > except BaseException as
On 13 June 2017 at 14:10, Nathaniel Smith wrote:
> On Mon, Jun 12, 2017 at 1:07 AM, Nick Coghlan wrote:
>> Since I don't see anything in the discussion so far that *requires*
>> changes to the standard library (aside from "we may want to use this
>> ourselves"), the right place to thrash out the
