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
In #61032 we have created a new base class BaseExecutionEngine that engines can subclass to handle apply and map operations. The base class has been initially created to allow third-party engines to be passed to DataFrame.apply(..., engine=third_party_engine). But our core engines Python and Numba can also be implemented as instances of this base class. This will make the code cleaner, more maintainable, and it may allow to move the Numba engine outside of the pandas code base easily.
The whole migration to the new interface is quite a big change, so it's recommended to make the transition step by step, in small pull requests.
The text was updated successfully, but these errors were encountered:
Thanks @arthurlw. A possible approach could be starting by numba only. The numba engine is only implemented for DataFrame.apply for now, and only for certain types of the parameters. For example, it doesn't work with ufuncs.
I think all the numba engine has been introduced in two PRs, #54666 and #55104, and hasn't change much. So it should be easy to see all the changes implemented for the engine.
I think having all the numba engine as a sublass of the base executor would be already quite valuable, and much easier than refactoring all the Python engine code.
In #61032 we have created a new base class
BaseExecutionEngine
that engines can subclass to handleapply
andmap
operations. The base class has been initially created to allow third-party engines to be passed toDataFrame.apply(..., engine=third_party_engine)
. But our core engines Python and Numba can also be implemented as instances of this base class. This will make the code cleaner, more maintainable, and it may allow to move the Numba engine outside of the pandas code base easily.The whole migration to the new interface is quite a big change, so it's recommended to make the transition step by step, in small pull requests.
The text was updated successfully, but these errors were encountered: