Avoid stopping function my_logs() at premium cache #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see #117
I have changed the function my_logs() so that if cache can be read by guid it is read by guid and otherwise -- i. e. if the cache is only for premium members -- it reads the cache by the GC code. So my_logs() doesn't throw an error and you can get the information of the caches you have found before the PMonly cache. It is even possible to get some information on the PMonly cache by cache.load_quick().