[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +1030 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-24 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset 398ff91ac0b8f4d930cd5d9e3e6a4bf247f810ef by Yury Selivanov in branch 'master': bpo-28893: Set __cause__ for errors in async iteration protocol (#407) https://github.com/python/cpython/commit/398ff91ac0b8f4d930cd5d9e3e6a4bf247f810ef -- _

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-17 Thread Larry Hastings
Changes by Larry Hastings : -- pull_requests: +624 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-03 Thread Yury Selivanov
Changes by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-02 Thread Yury Selivanov
Yury Selivanov added the comment: New changeset dea5101ae101aefed14de98e6bb1658f4cae8712 by Yury Selivanov in branch '3.6': bpo-28893: Set __cause__ for errors in async iteration protocol (#407) https://github.com/python/cpython/commit/dea5101ae101aefed14de98e6bb1658f4cae8712 --

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-02 Thread Yury Selivanov
Changes by Yury Selivanov : -- pull_requests: +345 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2017-03-02 Thread Yury Selivanov
Changes by Yury Selivanov : -- pull_requests: +339 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2016-12-07 Thread Yury Selivanov
Yury Selivanov added the comment: Ned, sounds good. Serhiy, we don't have _PyErr_FormatFromCause in 3.5, so I'll probably commit the patch as is in 3.5. For 3.6 is definitely makes sense to use _PyErr_FormatFromCause. -- ___ Python tracker

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2016-12-07 Thread Ned Deily
Ned Deily added the comment: Yury, sounds like a bug to me so it would be appropriate for a maintenance release. And not a showstopper release critical. -- ___ Python tracker _

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2016-12-06 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Should the original exception be stored on the __context__ or the __cause__ attribute? In the latter case you should use _PyErr_FormatFromCause(). -- ___ Python tracker

[issue28893] Make sure exceptions raised in __aiter__ are properly chained in ceval

2016-12-06 Thread Yury Selivanov
New submission from Yury Selivanov: Originally reported in http://bugs.python.org/issue28885#msg282538 Ned, please take a look at the attached patch. While I think that the change is quite small & safe to merge, I think it's OK if we push this only in 3.6.1. It's a nice usability improvement