pytask-io

pytask-io copied to clipboard

result_exec_date not being set when the unit of work task is executed.

joegasewicz

By default we should automatically call stop after all items in the queue are processed. Unless a user chooses to keep running forever (theres should be an option for this)...

joegasewicz

The `PyTaskIO.stop()` method needs to be explained in the docs

joegasewicz

The low level logging variable `PYTASKIO_DEBUG` is not in the Readme or docs. example should read: ``` # For development of low level libraries, you can get debug level logging...

joegasewicz

metadata should have an` uow_error` key to log errors

joegasewicz

Close asyncio loop in teardown

1

Close asyncio loop in teardown test method.

joegasewicz

Add tools to keep the code style consistent

2

As title says, tools like **black** and **isort** help to keep the code style consistent. Maybe add a pre-commit file to make it more like run-and-forget.

piotr-kopacki

Not handled exception when unit of work throws an exception

1

Not handled exception when unit of work throws an exception: https://github.com/joegasewicz/pytask-io/blob/0a917e3538052c3f9b82e2f13f1a27c5f75c0214/pytask_io/worker.py#L27

joegasewicz

Exception thrown: cannot schedule new futures after interpreter shutdown

1

Exception thrown: cannot schedule new futures after interpreter shutdown

joegasewicz

`test_worker` unit test fails

joegasewicz