[issue8613] Decimal module flags undetermined when a signal is trapped.

Change by Cheryl Sabella : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue8613] Decimal module flags undetermined when a signal is trapped.

Stefan Krah added the comment: This only affects the Python version and is probably not a problem in practice. Setting to pending, in case you want to keep it open. -- resolution: -> wont fix stage: test needed -> resolved status: open -> pending __

[issue8613] Decimal module flags undetermined when a signal is trapped.

Mark Dickinson added the comment: Unassigning. -- assignee: mark.dickinson -> ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8613] Decimal module flags undetermined when a signal is trapped.

Éric Araujo added the comment: Foehn, bugs.python.org is used for discussing and solving bugs in Python, not general discussion about programming. There are Web forums and IRC rooms where your question could get answered. I will answer you, but please do not post other unrelated messages. Try

[issue8613] Decimal module flags undetermined when a signal is trapped.

Changes by Antoine Pitrou : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/op

[issue8613] Decimal module flags undetermined when a signal is trapped.

Foehn of blue added the comment: Can you teach me how to Writing programs? Please!!! I'm from Taiwan That's my e-mail:foehnofb...@kimo.com -- nosy: +foehn blue ___ Python tracker ___

[issue8613] Decimal module flags undetermined when a signal is trapped.

Mark Dickinson added the comment: Umm. Please pretend I didn't write this: > One simple change that might help would be to have all Decimal > exceptions derive from a common `DecimalException` superclass, making > it easier to catch just decimal exceptions in a try-except block. DecimalExcep

[issue8613] Decimal module flags undetermined when a signal is trapped.

Mark Dickinson added the comment: Hmm. The 'delay_traps' context manager idea doesn't quite work here. A problem occurs if (for example) an Overflow occurs during the with block; in that case, Overflow should be raised at the end of the with block. That's fine, except that we no longer kn

[issue8613] Decimal module flags undetermined when a signal is trapped.

Mark Dickinson added the comment: Yes, that's a good point. It would be nice for e.g. "Inexact => Rounded" invariants to be, well, invariant. I agree that the cdecimal behaviour is the correct one. I'm looking for wiggle room here because I don't really want to make a set of complicated and

[issue8613] Decimal module flags undetermined when a signal is trapped.

Stefan Krah added the comment: I agree that the spec is not unambiguous, but consider the Overflow and Underflow passages here: http://speleotrove.com/decimal/daexcep.html ==> Overflow ==> In all cases, Inexact and Rounded will also be raised. "Raise" here of course means raising the

[issue8613] Decimal module flags undetermined when a signal is trapped.

New submission from Mark Dickinson : In an effort to keep to one issue per tracker item, I'm pulling this issue out of the comments on issue 8567. Issue: if a Decimal operation raises several signals, and one or more of those signals is trapped, how should that operation affect flags? Decima