On 05.06.2018 0:54, Ivan Pozdeev wrote:
On 04.06.2018 23:52, Ivan Pozdeev wrote:
On 04.06.2018 20:11, Chris Angelico wrote:
On Tue, Jun 5, 2018 at 2:57 AM, Yury Selivanov
wrote:
On Mon, Jun 4, 2018 at 12:50 PM Chris Angelico
wrote:
On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner
wrote:
[..
On 04.06.2018 23:52, Ivan Pozdeev wrote:
On 04.06.2018 20:11, Chris Angelico wrote:
On Tue, Jun 5, 2018 at 2:57 AM, Yury Selivanov
wrote:
On Mon, Jun 4, 2018 at 12:50 PM Chris Angelico
wrote:
On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner
wrote:
[..]
For me, it's fine to catch any excepti
On 04.06.2018 20:11, Chris Angelico wrote:
On Tue, Jun 5, 2018 at 2:57 AM, Yury Selivanov wrote:
On Mon, Jun 4, 2018 at 12:50 PM Chris Angelico wrote:
On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner wrote:
[..]
For me, it's fine to catch any exception using "except:" if the block
contains "
On Mon, Jun 4, 2018 at 3:38 PM Victor Stinner wrote:
>
> 2018-06-04 18:45 GMT+02:00 Guido van Rossum :
> > It is currently a general convention in asyncio to only catch Exception, not
> > BaseException. I consider this a flaw and we should fix it, but it's
> > unfortunately not so easy -- the test
2018-06-04 18:45 GMT+02:00 Guido van Rossum :
> It is currently a general convention in asyncio to only catch Exception, not
> BaseException. I consider this a flaw and we should fix it, but it's
> unfortunately not so easy -- the tests will fail if you replace all
> occurrences of Exception with B
On Tue, Jun 5, 2018 at 2:57 AM, Yury Selivanov wrote:
> On Mon, Jun 4, 2018 at 12:50 PM Chris Angelico wrote:
>>
>> On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner wrote:
> [..]
>> > For me, it's fine to catch any exception using "except:" if the block
>> > contains "raise", typical pattern to cl
On Mon, Jun 4, 2018 at 12:50 PM Chris Angelico wrote:
>
> On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner wrote:
[..]
> > For me, it's fine to catch any exception using "except:" if the block
> > contains "raise", typical pattern to cleanup a resource in case of
> > error. Otherwise, there is a ri
> It is currently a general convention in asyncio to only catch Exception, not
> BaseException. I consider this a flaw and we should fix it, but it's
> unfortunately not so easy -- the tests will fail if you replace all
> occurrences of Exception with BaseException, and it is not always clear
>
On Tue, Jun 5, 2018 at 2:11 AM, Victor Stinner wrote:
> Hi,
>
> I just read a recent bugfix in asyncio:
>
> https://github.com/python/cpython/commit/9602643120a509858d0bee4215d7f150e6125468
>
> + try:
> + await waiter
> + except Exception:
> + transport.close()
> + raise
>
> Why only c
It is currently a general convention in asyncio to only catch Exception,
not BaseException. I consider this a flaw and we should fix it, but it's
unfortunately not so easy -- the tests will fail if you replace all
occurrences of Exception with BaseException, and it is not always clear
what's the ri
10 matches
Mail list logo
