[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: The other changes are in the patch "issue13248_obsolescence_v3.diff". AFAIU, they will not be removed in 3.3, in order to facilitate transition from Python 2. *asyncore* shortcut "dispatcher.*" for "dispatcher.socket.*" attributes *base64* functions "en

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file26297/issue13248_io_max_buffer_size.diff ___ Python tracker ___ ___ Pyt

[issue13248] deprecated in 3.2, should be removed in 3.3

Terry J. Reedy added the comment: We do not document removals after they are done as they are not an issue for back-compatibility (unlike changes and additions). Deprecation Warnings are optionally available for checking forward-compatibility. Deprecations are sometimes noted in the regular t

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: Eric, I will check but I thought they were not documented. -- ___ Python tracker ___ ___ Python-bu

[issue13248] deprecated in 3.2, should be removed in 3.3

Éric Araujo added the comment: Flox, could you put versionchanged (or versiondeprecated-removed, which could also go into 3.2) to note the removals in the doc? -- ___ Python tracker __

[issue13248] deprecated in 3.2, should be removed in 3.3

Roundup Robot added the comment: New changeset 5393382c1b1d by Florent Xicluna in branch 'default': Issue #13248: argparse: Remove obsolete argument "version" of ArgumentParser. http://hg.python.org/cpython/rev/5393382c1b1d New changeset 700f989afbad by Florent Xicluna in branch 'default': Issu

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : Added file: http://bugs.python.org/file26301/issue13248_obsolescence_v3.diff ___ Python tracker ___ ___ Python-bu

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file23929/issue13248_obsolescence_v2.diff ___ Python tracker ___ ___ Python-

[issue13248] deprecated in 3.2, should be removed in 3.3

Antoine Pitrou added the comment: > Do we agree to remove the "max_buffer_size" from the "io" module in 3.3? Yes! -- ___ Python tracker ___

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file23928/issue13248_argparse_io_lib2to3.diff ___ Python tracker ___ ___ Py

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: Do we agree to remove the "max_buffer_size" from the "io" module in 3.3? This argument is unused, and deprecated. Just dead code. See attachment. -- Added file: http://bugs.python.org/file26297/issue13248_io_max_buffer_size.diff _

[issue13248] deprecated in 3.2, should be removed in 3.3

Ezio Melotti added the comment: I don't mind if they are removed in 3.3 or 3.4, as long as they are documented in all the versions where they are present. -- ___ Python tracker ___

[issue13248] deprecated in 3.2, should be removed in 3.3

Raymond Hettinger added the comment: Ezio, I'm was thinking of marking the code and its docstring as removed/unused, but if you want the code removed altogether, that would be fine. -- ___ Python tracker

[issue13248] deprecated in 3.2, should be removed in 3.3

Ezio Melotti added the comment: Raymond, I think it's better to leave the documentation and use "deprecated-removed" to signal clearly that those functions are deprecated and when they will be removed (even if this means 3.4). IME removing documentation creates more confusion because people

[issue13248] deprecated in 3.2, should be removed in 3.3

Roundup Robot added the comment: New changeset 0ddb78341290 by Raymond Hettinger in branch 'default': Issue #13248: Removed docs for two deprecated unittest features. To be conservative, the code is left in for one more release. http://hg.python.org/cpython/rev/0ddb78341290 -- _

[issue13248] deprecated in 3.2, should be removed in 3.3

Roundup Robot added the comment: New changeset b30171bbc571 by Benjamin Peterson in branch 'default': remove get_prefix and set_prefix (#13248) http://hg.python.org/cpython/rev/b30171bbc571 -- ___ Python tracker _

[issue13248] deprecated in 3.2, should be removed in 3.3

Raymond Hettinger added the comment: In unittest, DictContainsSubset() should be removed from 3.3. It was defective by design (wrong argument order). I concur with Ezio that the other unittest methods should remain intact. I'm not sure whether assertSameElements() should stay or go (when G

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13248] deprecated in 3.2, should be removed in 3.3

Ezio Melotti added the comment: I think it would be better to decide in what version each thing will be removed and then mark them with the deprecated-removed directive in the doc. -- ___ Python tracker _

[issue13248] deprecated in 3.2, should be removed in 3.3

Éric Araujo added the comment: Given the discussions we’ve had this month and a few months earlier about people porting directly to 3.2 or 3.3, I think the second patch needs to wait for 3.4 or 3.5. (I have no opinion on the first patch, not being a customer of lib2to3 or pyio.) --

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: I removed object.__format__ from the patch because it is not planned for removal in 3.3, but in 3.4 (see issue #9856). I've fixed the documentation *versionchanged* and split the patch in two. The first is less controversial. The second might be delayed a lit

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file23905/issue13248_obsolescence.diff ___ Python tracker ___ ___ Python-bug

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : -- dependencies: -Change object.__format__(s) where s is non-empty to a TypeError Added file: http://bugs.python.org/file23928/issue13248_argparse_io_lib2to3.diff ___ Python tracker __

[issue13248] deprecated in 3.2, should be removed in 3.3

Antoine Pitrou added the comment: I think most of these shouldn't be removed, as it would make porting from 2.x significantly more tedious. Things that I think can be removed: - max_buffer_size (io is new and that argument was never used by anybody) - get_prefix / set_prefix (the internal lib2

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by Florent Xicluna : -- dependencies: +Change object.__format__(s) where s is non-empty to a TypeError ___ Python tracker ___

[issue13248] deprecated in 3.2, should be removed in 3.3

STINNER Victor added the comment: .. versionchanged:: 3.2 - The *strict* parameter is deprecated. HTTP 0.9-style "Simple Responses" + The *strict* parameter is removed. HTTP 0.9-style "Simple Responses" are not supported anymore. Such change looks wrong: the parameter exists

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: I know it won't be committed as-is, but this is the patch with most of the deprecated things removed. I skipped all the modules where a veto has been pronounced explicitly. -- keywords: +patch Added file: http://bugs.python.org/file23905/issue13248_o

[issue13248] deprecated in 3.2, should be removed in 3.3

Roundup Robot added the comment: New changeset f82ebf9b3a52 by Florent Xicluna in branch 'default': Issue #13248: turn 3.2's PendingDeprecationWarning into 3.3's DeprecationWarning (cgi, importlib, nntplib, smtpd). http://hg.python.org/cpython/rev/f82ebf9b3a52 -- _

[issue13248] deprecated in 3.2, should be removed in 3.3

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13248] deprecated in 3.2, should be removed in 3.3

Terry J. Reedy added the comment: The difflib deprecations are mine and I think they should happen in 3.3. This will serve as a reminder. -- nosy: +terry.reedy ___ Python tracker __

[issue13248] deprecated in 3.2, should be removed in 3.3

Éric Araujo added the comment: distutils will not change. I’ll ask if removing the deprecation warnings is okay, otherwise they’ll stay. For ConfigParser.readfp, it would ease porting between 2.x and 3.x if the method could stay longer, or forever. -- nosy: +eric.araujo ___

[issue13248] deprecated in 3.2, should be removed in 3.3

Ezio Melotti added the comment: Maybe a 2to3 fixer to convert the names should be added? -- ___ Python tracker ___ ___ Python-bugs-li

[issue13248] deprecated in 3.2, should be removed in 3.3

Antoine Pitrou added the comment: > *array* > "fromstring" and "tostring" methods I think these ones (and other well-known 2.x methods) should be kept to ease porting to 3.x. -- nosy: +pitrou ___ Python tracker

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: I missed these warnings in C modules. *array* "fromstring" and "tostring" methods *io* (like _pyio) argument "max_buffer_size" of BufferedWriter and BufferedRWPair *sys* "sys.getcheckinterval" and "sys.setcheckinterval" and some complaints from Object

[issue13248] deprecated in 3.2, should be removed in 3.3

Roundup Robot added the comment: New changeset 221638ba5d2a by Mark Dickinson in branch 'default': Issue #13248, issue #8540: Remove deprecated Context._clamp attribute from Decimal module. http://hg.python.org/cpython/rev/221638ba5d2a -- nosy: +python-dev

[issue13248] deprecated in 3.2, should be removed in 3.3

Ezio Melotti added the comment: *unittest* "assert{DictContainsSubset,RaisesRegexp,RegexpMatches}", "fail*" The "fail*" should stay. The general idea is that with Python3 we can wait a bit more before getting rid of things, because if someone jumps from 2.7 to 3.3, he might not find things

[issue13248] deprecated in 3.2, should be removed in 3.3

Florent Xicluna added the comment: In addition, we have some object and attributes which are triggering "PendingDeprecationWarning" in 3.2. We may keep these warnings in 3.3, or choose to turn some of them into "DeprecationWarning", to prepare their removal in 3.5. *cgi* "cgi.escape" *dist

[issue13248] deprecated in 3.2, should be removed in 3.3

New submission from Florent Xicluna : The PEP 387 suggests that deprecated objects or arguments are removed in version (n+1). I've listed these DeprecationWarnings in 3.2, which are still in 3.3. I assume that most of these deprecated objects or arguments could be removed before next release.