Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEATURE] add log_dtypes to pandas_utils

See original GitHub issue

I might also want to log the dtypes between each step in a pandas pipeline. It’s probably best to add a separate logger for both the dtype as well as the shape.

Should the column names be seperate too? Maybe worth a discussion.

It would also be nice if these features were documented on the documentation page together with some other pandas_utils functions.

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

koaningcommented, Jul 18, 2020

The print step would do a very similar thing to what log_step would do but it would use print instead of using the python logging framework. The reason why matplotlib is generating warnings is because we’ve configured a logger to work in the notebook. This allows you to receive logs from log_step (this is awesome for production) but you might also get the logs from other libraries (which is not awesome in a notebook).

0reactions

koaningcommented, Sep 22, 2020

This got adressed.