You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/brettcannon'closed_at=<Date2008-09-05.18:35:20.964>created_at=<Date2008-09-04.20:11:19.162>labels= ['type-bug', 'library', 'release-blocker']
title='deprecate bsddb/dbhash in 2.6 for removal in 3.0'updated_at=<Date2008-09-05.18:35:20.962>user='https://github.com/brettcannon'
Attached patch raises Py3k warnings rather than plain deprecation
warnings, so it looks good to me (some of the discussions on python-dev
gave the impression that may have been getting full deprecation
warnings, implying its potential removal in 2.7 as well).
Sorry if that impression was given about 2.6 deprecation. The plan was
always just for 3.0 removal since removing in 2.6 really would not be
enough time to warn users.
I have assigned to myself to apply the patch when I have time (some time
tonight).
I was actually pretty sure the intention was to add Py3k warnings, but
the exact phrase being used in the python-dev thread was "deprecation
warnings" which made folks a little nervous.
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: