[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

Changes by Benjamin Peterson : -- resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

R. David Murray added the comment: Ah, I missed the fact that this was a 3.2 change. Somehow I thought it was a 3.1 thing. So you are right, IMO, this would be feature creap. -- ___ Python tracker ___

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

Raymond Hettinger added the comment: It's the users wants not yours that matter. If someone already has 3.0 in production and is maintaining code in both 2.6 and 3.0, then this change will break their build. Also, it is not a necessary change. We already have a warning in-place to alert anyon

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

R. David Murray added the comment: I think 2to3 should target 3.1. We don't expect/want people to use 3.0 in production. -- nosy: +r.david.murray priority: -> normal stage: -> test needed ___ Python tracker

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

Raymond Hettinger added the comment: Doesn't that create an issue depending on whether your 2-to-3 target is 3.0 or 3.1? I don't think minor release changes should be conflated with the major release changes. -- nosy: +rhettinger ___ Python tracker

[issue6440] 2to3: convert deprecated string.maketrans to str.maketrans

New submission from Eric Eisner : string.maketrans has been deprecated in 3.x in favor of the more specific bytes.maketrans and str.maketrans (see issue5675). It would be nice if 2to3 would automatically translate this to one of those two (probably str.maketrans). I briefly looked at lib2to3/fix