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
Currently, we clean temp file by @exit.register.
But some user need to delete temp file in run time.
I think it is natural that user expected release resources by garbage collector or __del__ method.
I mean,
rgf = RGFClassifier()
del rgf
But we should not expect to be called __del__ method every time.
For example, I confirmed test_parallel_gridsearch doesn't call __del__ method.
So we should also use @exit.register.
Another option to solve this problem is changing communication method between Python and C++.
For example, XGB uses ctypes.
The text was updated successfully, but these errors were encountered:
Delete temp file aggressively.
As refered in https://www.kaggle.com/tunguz/rgf-target-encoding-0-282-on-lb/code ,
sometimes user's environment has limited disk capacity, (ex. kaggle kernel has 1GB).
Currently, we clean temp file by
@exit.register
.But some user need to delete temp file in run time.
I think it is natural that user expected release resources by garbage collector or
__del__
method.I mean,
But we should not expect to be called
__del__
method every time.For example, I confirmed
test_parallel_gridsearch
doesn't call__del__
method.So we should also use
@exit.register
.Another option to solve this problem is changing communication method between Python and C++.
For example, XGB uses
ctypes
.The text was updated successfully, but these errors were encountered: