[forwarding to python-dev for general ack] > The changes to re are still throwing off signed/unsigned warnings. Can > you please get that fixed up? My changes to sre have nothing to do with these warnings. These are being caused by the fact that gcc throws a warning even with casts in the following situation: char i = 0; if ((int)i < 256) ... Unlike one might think, this is a valid test because the type of 'i' is not always char. I won't fix these warnings until I find an elegant solution to workaround the gcc stupidity. -- Gustavo Niemeyer http://niemeyer.net
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4