You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Declaring oldsize as Py_ssize_t instead of size_t at Objects/bytesobject.c:2812 takes care of the warning, but I'm not comfortable saying that's a correct change.
Activity
zware commentedon May 5, 2014
Issue bpo-21377 introduced a compiler warning on Windows:
..\Objects\bytesobject.c(2824): warning C4018: '>' : signed/unsigned mismatch [P:\ath\to\cpython\PCbuild\pythoncore.vcxproj]
zware commentedon May 6, 2014
Declaring oldsize as Py_ssize_t instead of size_t at Objects/bytesobject.c:2812 takes care of the warning, but I'm not comfortable saying that's a correct change.
tjguk commentedon May 6, 2014
Well PyBytes_GET_SIZE is documented as returning a Py_ssize_t so I'd say it's perfectly valid.
python-dev commentedon May 6, 2014
New changeset 6234f4caba57 by Zachary Ware in branch 'default':
Issue bpo-21442: Fix MSVC compiler warning introduced by bpo-21377.
http://hg.python.org/cpython/rev/6234f4caba57
zware commentedon May 6, 2014
I should have looked a little harder, thanks Tim!