[issue5748] Objects/bytesobject.c should include stringdefs.h, instead of defining its own macros

Eric Smith added the comment: Fixed in r76595. -- resolution: -> accepted stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue5748] Objects/bytesobject.c should include stringdefs.h, instead of defining its own macros

Eric Smith added the comment: This does not apply to 2.x. In both py3k and trunk, Objects/bytearrayobject.c uses stringlib with some private defines. But since those defines are only used in bytearrayobject.c, there's nothing to be gained by factoring then out into a bytearraydef.h file. So, I'

[issue5748] Objects/bytesobject.c should include stringdefs.h, instead of defining its own macros

Changes by Victor Godoy Poluceno : -- nosy: +victorpoluceno ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5748] Objects/bytesobject.c should include stringdefs.h, instead of defining its own macros

New submission from Eric Smith : All of the macros it defines around line 565 should either already be in stringdefs.h, or they should be added there. The same issue exists in Objects/bytearrayobject.c. I haven't looked in 2.7, but I assume the same problem exists there. -- assignee: er