decimal.InvalidContext is unused

[skrah]

BPO	21388
Nosy	@rhettinger, @mdickinson, @skrah

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2014-04-29.19:11:23.441>
created_at = <Date 2014-04-29.13:39:31.014>
labels = ['type-bug', 'invalid']
title = 'decimal.InvalidContext is unused'
updated_at = <Date 2014-04-29.19:11:23.440>
user = 'https://github.com/skrah'

bugs.python.org fields:

activity = <Date 2014-04-29.19:11:23.440>
actor = 'skrah'
assignee = 'none'
closed = True
closed_date = <Date 2014-04-29.19:11:23.441>
closer = 'skrah'
components = []
creation = <Date 2014-04-29.13:39:31.014>
creator = 'skrah'
dependencies = []
files = []
hgrepos = []
issue_num = 21388
keywords = []
message_count = 3.0
messages = ['217519', '217525', '217539']
nosy_count = 3.0
nosy_names = ['rhettinger', 'mark.dickinson', 'skrah']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21388'
versions = ['Python 3.5']

[skrah]

We could remove decimal.InvalidContext, which is completely unused
both in decimal.py and _decimal.

[mdickinson]

It's part of the specification, though. For me, that's a good enough reason to keep it.

[skrah]

Okay, also it is easier to keep it. I was just busy with the exception
docs and found the InvalidContext situation slightly odd.

Of course, there is a very small chance that external software is
using it.