On 2020-01-21 6:17 PM, Maxime S wrote:
Hi,
Le ven. 17 janv. 2020 à 20:11, Frank Millman a écrit :
It works perfectly. However, some pdf's can be large, and there could be
concurrent requests, so I wanted to minimise the memory footprint. So I
tried passing the client_writer directly to the h
i mean numba instead of number ☺
On Wed, 22 Jan 2020, 1:34 am AAKASH JANA i have been fairly confused as to what would be the best option for an all
> in all python compiler (i am talking the cpython , number type compiler) to
> use for basic projects. Like sorting and searching algorithms to be
i have been fairly confused as to what would be the best option for an all
in all python compiler (i am talking the cpython , number type compiler) to
use for basic projects. Like sorting and searching algorithms to be
replicated without use of any builtins. Please help
On Tue, 21 Jan 2020, 9:52 p
Hi,
Le ven. 17 janv. 2020 à 20:11, Frank Millman a écrit :
> It works perfectly. However, some pdf's can be large, and there could be
> concurrent requests, so I wanted to minimise the memory footprint. So I
> tried passing the client_writer directly to the handler -
>
> await pdf_handler(
On Sat, Jan 18, 2020 at 6:09 AM Frank Millman wrote:
> So I
> tried passing the client_writer directly to the handler -
>
> await pdf_handler(client_writer)
> client_writer.write(b'\r\n')
>
> It works! ReportLab accepts client_writer as a file-like object, and
> writes to it directly. I
Hi all
I just tried something that I did not think had a snowball's chance of
working, but to my surprise it did. I thought I would share it, partly
for interest, and partly in case anyone can foresee any problems with it.
I use ReportLab to generate pdf files. I do not write them to disk, bu
