You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LadybugDB has a C-API that's used by all languages, except for python.
Python bindings use C++ based pybind, with special handling for arrow, dataframes, json values etc. However, it has a few problems:
Memory management is less efficient than C-API. Have to close long running connections to fully release memory
After recent decoupling of repos, I'd like to see ladybug and ladybug-python to be connected via a well defined contract.
If there are N platforms and M python versions, we build ladybug N * M times without ccache. Makes release builds slow.
LadybugDB/ladybug-python#7 is an alternative. It implements a backward compatible python binding on top of the C-API. Proposal: over time, we gradually migrate to this backend by copying/moving functionality.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
LadybugDB has a C-API that's used by all languages, except for python.
Python bindings use C++ based pybind, with special handling for arrow, dataframes, json values etc. However, it has a few problems:
LadybugDB/ladybug-python#7 is an alternative. It implements a backward compatible python binding on top of the C-API. Proposal: over time, we gradually migrate to this backend by copying/moving functionality.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions