Repository navigation
OSF is not supported anymore #52852
Description
| BPO | 8606 |
|---|---|
| Nosy | @loewis, @jcea |
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 = 'https://github.com/jcea'
closed_at = <Date 2010-05-03.21:38:41.152>
created_at = <Date 2010-05-03.20:14:55.211>
labels = ['type-feature']
title = 'OSF is not supported anymore'
updated_at = <Date 2010-05-03.21:38:41.150>
user = 'https://github.com/jcea'bugs.python.org fields:
activity = <Date 2010-05-03.21:38:41.150>
actor = 'jcea'
assignee = 'jcea'
closed = True
closed_date = <Date 2010-05-03.21:38:41.152>
closer = 'jcea'
components = []
creation = <Date 2010-05-03.20:14:55.211>
creator = 'jcea'
dependencies = []
files = []
hgrepos = []
issue_num = 8606
keywords = []
message_count = 2.0
messages = ['104875', '104888']
nosy_count = 2.0
nosy_names = ['loewis', 'jcea']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue8606'
versions = ['Python 3.2', 'Python 3.3']
Activity
jcea commentedon May 3, 2010
OSF* platform seems to be pretty dead. We are moving it to unsupported state, as documented in PEP-11.
The first phase is Python 3.2: Configure will fail win OSF* platforms. This configuration failure will be trvivially reversible.
If nobody stands up to take care of OSF*, support will be removed in Python 3.3.
Discussion:
http://mail.python.org/pipermail/python-dev/2010-April/099718.html
http://mail.python.org/pipermail/python-dev/2010-May/099899.html
jcea commentedon May 3, 2010
I am unsupporting OSF* systems. If that is too much to deprecate, change it to deprecate only OSF1.
Commit at r80728.