-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: lru-cache usage #171
fix: lru-cache usage #171
Conversation
Hi, Thanks for your interest in Indeed, seems like with the current use of What would be the use case for a In the meantime what you can do as a workaround is to create a brand new object (not creating one with
|
Codecov Report
@@ Coverage Diff @@
## master #171 +/- ##
=======================================
Coverage 96.31% 96.31%
=======================================
Files 40 40
Lines 978 978
=======================================
Hits 942 942
Misses 36 36
Continue to review full report at Codecov.
|
After giving some thoughts about it, I think what @julia-shenshina is proposing is the way to go if we want to address this. |
Indeed, I do not remember why I did not use the decorator. We can change it also in Dynp and BottomUP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@julia-shenshina
Can you proceed to the following changes :
- Change the use of
lru_cache
to decorator also for BottomUp and Dynp - Rename the PR to
fix: lru-cache usage
Thanks a lot !
Thank you for your answers! Changed |
Merged, thx @julia-shenshina ! |
Hi!
I tried to use
copy.deepcopy
to copyBinseg
object and met a problem:binseg.single_bkp
anddeepcopy(binseg).single_bkp
referred to the same object. So, I can not usebinseg_copy.single_bkp
because it tries to use the data from the original object.It seems to be caused by the way
lru_cache
is used. Are there any reasons not to use it with@
decorator syntax?