By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,660 Members | 1,105 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,660 IT Pros & Developers. It's quick & easy.

__getslice__ depreciation

P: n/a
If __getslice__ is depreciated (since version 2.0) why are neither
__setslice__ or __delslice__ depreciated?
http://docs.python.org/ref/sequence-methods.html

Jun 1 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Jun 1, 7:50 pm, Screamingfi...@gmail.com wrote:
If __getslice__ is depreciated (since version 2.0) why are neither
__setslice__ or __delslice__ depreciated?http://docs.python.org/ref/sequence-methods.html
Sorry disregard that, I should have RTFA

Jun 1 '07 #2

P: n/a
Sc************@gmail.com wrote:
On Jun 1, 7:50 pm, Screamingfi...@gmail.com wrote:
>If __getslice__ is depreciated (since version 2.0) why are neither
__setslice__ or __delslice__ depreciated?http://docs.python.org/ref/sequence-methods.html

Sorry disregard that, I should have RTFA
A request to have the docs changed so that "Deprecated since release
2.0." in bold appears next to all three would not go amiss.
--
Michael Hoffman
Jun 3 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.