[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Changes by Terry J. Reedy : -- resolution: later -> rejected stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyth

[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Mark Lawrence added the comment: Given the last two comments can this be closed as won't fix? -- nosy: +BreamoreBoy ___ Python tracker ___

[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Benjamin Peterson added the comment: What's the point of '{}'.format() anyway given the format() builtin? -- nosy: +benjamin.peterson ___ Python tracker ___ _

[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Raymond Hettinger added the comment: This proposal hasn't gotten much love or support and I'm no longer interested in it. Aside from ''.join and '{}'.format, there doesn't seem to be many common cases, so there's no big win here. -- assignee: rhettinger -> resolution: -> later vers

[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Changes by Raymond Hettinger : -- priority: -> low versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue6133] LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST

Changes by Demur Rumed : -- title: LOAD_CONST followed by LOAD_ATTR can be optimized to justbe a LOAD_COST -> LOAD_CONST followed by LOAD_ATTR can be optimized to just be a LOAD_CONST ___ Python tracker