karolyjozsa

Validating 'aaa' as an integer is pretty confusing. ``` >>> validate({"d":'aaa'}, {"d":'integer|min:1'}, return_info=True) (True, {'d': 'aaa'}, {}) ``` I think the root issue is that the request is somehow converted...

I was to raise this issue, then found this. I wonder whether there is a work-around (e.g. somehow patching the WebRequest) so that we can use it before the bug...

I followed the steps in quick build (I also had to install Windows SDK), but it seems to look explicitly for Win7 SDK and does not work on Win10. Also,...

I suspect that even if I could build it from master, I would get stuck in ResourceHandler.ReadResponse, because its data_out[0] has str type, and should also be bytes. Or does...

When I put this print into my ReadResponse method, It states def ReadResponse(self, data_out, bytes_to_read, bytes_read_out, callback): print(f"ReadResponse(f"{type(data_out[0])}") And I might have found the reason in handlers/resource_handler.pyx, line 153: dataOut...

I managed to install Win7 SDK on Win10 and trying to build it from master, but the 66.1 zip package seems to be missing the "lib" folder. Linking "subprocess" fails...

I managed to compile it with the lib as well as the bin copied over from v66-upstream, thanks. I had to modify resource_handler.pyx, line 165: `if dataOut[0] and IsString(dataOut[0]):` -->...

Indeed, IsString() returns True on a bytes object. Well, I see still no point having this check as the data must always be bytes. Unfortunately, the code still does not...

I needed the same for demoing my package on the web without forcing users to install my package. Well, I also need it for development, i.e. need the changing Python...