[issue6000] compile error - PyNumber_InPlaceOr(newfree, allfree) < 0

Benjamin Peterson added the comment: Fixed in r72589. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pytho

[issue6000] compile error - PyNumber_InPlaceOr(newfree, allfree) < 0

Changes by Benjamin Peterson : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson priority: critical -> release blocker ___ Python tracker ___ ___

[issue6000] compile error - PyNumber_InPlaceOr(newfree, allfree) < 0

Mark Dickinson added the comment: The error's also in 3.0. -- nosy: +marketdickinson versions: +Python 3.0 ___ Python tracker ___ ___

[issue6000] compile error - PyNumber_InPlaceOr(newfree, allfree) < 0

Antoine Pitrou added the comment: Hmm, PyNumber_InPlaceOr() returns a PyObject*, no wonder why the compiler complains. I suppose gcc and MSVC and /really/ laxist to let this error fall through. -- keywords: +easy nosy: +pitrou priority: -> critical stage: -> needs patch title: compile