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
._rawData vs. .raw_data - Lazy Loading #2202
Comments
Hello, I faced the same issue. The main problem here, as I see Here the example of my case
The Objects in How can I avoid spending hundreds and thousands API requests per program launch w/o accessing a protected attribute |
Excuse me, dear @jacquev6, @adamtheturtle, and @sfdye (mentioning you since activity on GH). Don't you consider the mentioned fact that accessing |
I assume, because of that one can't get Any thoughts, please? |
This issue forced me to write our own wrapper around the annoying issue, so we spend magnitude fewer requests than it could be https://github.com/ClickHouse/ClickHouse/blob/469b7e7/tests/ci/github_helper.py#L102 It as well uses local caching. It as well helps to reduce the number of requests many times. |
I agree, it is surprising that |
I am confused about the difference of the ._rawData and the .raw_data attributes of GitubObjects.
While the ._rawData attributes returns stored data instantaneously, the .raw_data attribute tries to redownload the content - even though it is allready in the memory.
Let me provide a minimal example:
The text was updated successfully, but these errors were encountered: