[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_5540":5541,"_5542":57,"_5543":15,"_5544":15,"_5545":15,"_5546":15,"_5547":15,"_5548":15,"_5549":5550},"routes/s.$postId",{"_9":10,"_11":12,"_13":-7,"_14":15,"_16":15,"_17":18},"kind","post_with_profile","postWithProfile",{"_19":20,"_21":22},"referrer","preferIntrinsicAspectRatioForOgImage",false,"enforceRenderedOgImg","defaultOgDescription","ChatGPT helps you get answers, find inspiration, and be more productive.","post",{"_41":42,"_43":44,"_45":-5,"_46":-5,"_47":-5,"_48":49,"_50":51,"_34":52,"_53":54,"_55":15},"profile",{"_23":24,"_25":24,"_26":27,"_28":-5,"_29":-5,"_30":31,"_32":15,"_33":-5,"_34":-5,"_35":-5,"_36":15,"_37":-5,"_38":-5,"_39":-5,"_40":15},"user_id","anonymous","username","profile_picture_url","https://cdn.openai.com/sora/images/profile_placeholder_v4.png","profile_picture_id","is_default_profile_picture","follower_count",0,"is_following","display_name","permalink","can_cameo","verified","character_count","owner_profile","social_context","follows_you","id","cd_6995ade5dc5c8191b849f23fa8525f9c","posted_at",1771417061.860915,"text","og_title","og_description","attachments",[63],"preview_image_url","https://ogimg.chatgpt.com/?postId=cd_6995ade5dc5c8191b849f23fa8525f9c","https://chatgpt.com/s/cd_6995ade5dc5c8191b849f23fa8525f9c","permissions",{"_56":57,"_58":15,"_59":15,"_60":57,"_61":62},"use_experimental_unfurl","can_read",true,"can_write","can_delete","can_remix","share_setting","public",{"_41":64,"_65":66,"_9":67,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":-5},"cd_6995ade5dc5c8191b849f23fa8525f9c-attachment-0","tags",[],"codex","task",{"_41":466,"_118":5501,"_271":5502,"_5503":57,"_81":82,"_5504":15,"_5505":5506,"_235":15,"_5507":5508,"_5509":-5,"_5510":5511},"current_user_turn",{"_91":285,"_41":83,"_95":285,"_2900":5492,"_2902":5493,"_2904":2905,"_131":-5,"_118":2906},"current_assistant_turn",{"_91":92,"_41":82,"_93":-5,"_94":-5,"_95":92,"_96":4218,"_98":4219,"_100":101,"_102":-5,"_103":4220,"_105":4221,"_107":4222,"_109":4223,"_111":112,"_113":-5,"_114":115,"_116":4224,"_118":119,"_120":-5,"_121":122,"_123":4225,"_125":126,"_127":128,"_129":-5,"_130":-5,"_131":83,"_132":4226,"_134":4227,"_136":-5,"_137":15,"_138":139,"_140":-5},"current_diff_task_turn",{"_91":92,"_41":82,"_93":-5,"_94":-5,"_95":92,"_96":2944,"_98":2945,"_100":101,"_102":-5,"_103":2946,"_105":2947,"_107":2948,"_109":2949,"_111":112,"_113":-5,"_114":115,"_116":2950,"_118":119,"_120":-5,"_121":122,"_123":2951,"_125":126,"_127":128,"_129":-5,"_130":-5,"_131":83,"_132":2952,"_134":2953,"_136":-5,"_137":15,"_138":139,"_140":-5},"turns",{"_79":80,"_81":82},"example_task_info","turn_mapping",{"_83":84,"_82":85},"current_turn_id","task_e_6995ade3452c8323a4bb7d7eb8515f97~assttrn_e_6995ade4b1288323814814276480260b","task_e_6995ade3452c8323a4bb7d7eb8515f97~usertrn_e_6995ade4a9548323a8e5932f3dbccc3c",{"_41":83,"_86":2898,"_88":2899,"_90":-5},{"_41":82,"_86":87,"_88":89,"_90":83},"turn",{"_91":92,"_41":82,"_93":-5,"_94":-5,"_95":92,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":104,"_105":106,"_107":108,"_109":110,"_111":112,"_113":-5,"_114":115,"_116":117,"_118":119,"_120":-5,"_121":122,"_123":124,"_125":126,"_127":128,"_129":-5,"_130":-5,"_131":83,"_132":133,"_134":135,"_136":-5,"_137":15,"_138":139,"_140":-5},"children",[],"parent","type","assistant","sibling_turn_ids","attempt_placement","role","output_items",[1951,1952,1953],"child_turns",[],"conversation_id","None","error","latest_event",{"_1946":1947,"_45":1948,"_1949":1950},"worklog",{"_1920":1921},"app_server_events",{"_299":1338},"thread_events",{"_299":300},"turn_status","completed","cancellation_requested_at","pull_request_status","externally_created","pull_request_data",{"_263":264,"_254":265,"_266":267,"_268":57,"_269":15,"_270":15,"_271":272,"_273":274,"_275":227,"_276":126,"_277":278,"_279":280,"_281":282,"_283":-5,"_284":-5,"_285":286,"_287":288,"_289":290,"_291":292,"_293":294},"created_at",1771417060.692088,"internal_only_rollouts","environment_id","687602d255408191b30732a90eeaf718","environment",{"_41":122,"_174":175,"_176":177,"_178":15,"_179":180,"_181":182,"_183":184,"_185":-5,"_186":-5,"_187":188,"_189":190,"_191":192,"_193":194,"_195":196,"_197":198,"_199":-5,"_200":201,"_202":203,"_204":205,"_206":207,"_53":-5,"_118":208,"_209":-5,"_210":211,"_212":213,"_214":15},"branch","feature/s3-backend","base_commit_sha","2827e109cd308c3595f163ee7a0bc2590d18e7e8","branch_name","direct_push_pushed_commit_sha","previous_turn_id","logs",{"_132":159},"proxy_events",[141,142],"debug_metadata","discarded","model_version","gpt-5.3-codex-1p-codexswic-ev3","languages",{"_143":157,"_145":146,"_147":148,"_149":158,"_151":152,"_153":154,"_155":31,"_156":-5},{"_143":144,"_145":146,"_147":148,"_149":150,"_151":152,"_153":154,"_155":31,"_156":-5},"timestamp","2026-02-18T12:19:13.917595","decision","allow","reason","checks passed","method","GET","domain","api.openai.com:18080","protocol","HTTP/1.1","size","path","2026-02-18T12:19:13.861529","CONNECT",[160,161],{"_162":170,"_164":171},{"_162":163,"_164":165},"key",{"_166":167,"_91":168,"_118":169},"value","file_00000000a688722f901f71ca620ff1cc","name","userscript_1771417100","UserSetupScript","2026-02-18T12:18:20.683395",{"_166":172,"_91":168,"_118":173},"file_000000000f58722f9f3e1c859234128f","setup_autodetect","2026-02-18T12:18:15.732641","machine_id","wham-public/wham-universal","label","python-cachier/cachier","is_pinned","description","","workspace_dir","/workspace","agent_network_access",{"_257":258,"_259":67,"_260":-5,"_261":-5,"_262":57},"codex_github_direct","github_connector_id","repos",[217],"setup",[256],"maintenance_setup",[180],"repo_map",{"_217":218},"env_vars",{},"secrets",{},"secrets_with_domains","task_count",22,"creator_id","user-RRJ4ONkRYkMXARjd7XbB4ap2","share_settings","workspace","share_targets",[],1752564434.333186,"auto_setup_settings","cache_settings",{"_215":57,"_216":180},"etag","\"3e01cbb5-0000-0200-0000-69940c440000\"","enable_authtranslator","post_setup_cache_enabled","cache_invalidation_key","github-66466789",{"_41":219,"_166":220,"_221":222,"_223":177,"_224":225,"_226":227,"_228":229,"_230":231,"_232":233,"_234":62,"_235":-5,"_236":15,"_237":15,"_238":15,"_239":57,"_240":57,"_241":-5,"_155":242,"_243":-5,"_53":244},"66466789","cachier","owner",{"_248":249,"_41":250,"_91":251,"_252":253,"_254":255},"repository_full_name","clone_url","https://github.com/python-cachier/cachier.git","default_branch","master","git_commits_url","https://api.github.com/repos/python-cachier/cachier/git/commits{/sha}","git_refs_url","https://api.github.com/repos/python-cachier/cachier/git/refs{/sha}","git_url","git://github.com/python-cachier/cachier.git","visibility","archived","allow_auto_merge","allow_merge_commit","allow_rebase_merge","allow_squash_merge","allow_update_branch","language",798,"master_branch",{"_245":57,"_246":57,"_247":57},"admin","push","pull","login","python-cachier",119668473,"Organization","avatar_url","https://avatars.githubusercontent.com/u/119668473?v=4","url","https://api.github.com/users/python-cachier","python -m pip install --upgrade pip\npython -m pip install -e . -r tests/requirements.txt\npython -m pip install -r tests/requirements_mongodb.txt\npython -m pip install -r tests/requirements_redis.txt\npython -m pip install -r tests/requirements_postgres.txt","mode","on","preset_allowlist","allowlist_domains","denylist_domains","safe_methods_only","number",338,"https://github.com/python-cachier/cachier/pull/338","state","closed","merged","mergeable","draft","title","Add S3 backend core","body","## Summary\n\nCloses #41.\n\nAdds a new `s3` backend to cachier, allowing function results to be persistently cached in AWS S3 (or any S3-compatible service: MinIO, localstack, etc.).\n\n- **New backend:** `@cachier(backend=\"s3\", s3_bucket=\"my-bucket\")` - same decorator API as all other cores\n- **Flexible client config:** pass a pre-built boto3 client (`s3_client`), a callable factory (`s3_client_factory`), or let the core auto-create one from `s3_region` / `s3_endpoint_url` / `s3_config`\n- **Data model:** one pickled `CacheEntry` per cache key, stored at `//.pkl`\n- **Async:** async cached functions are supported via `asyncio.to_thread` delegation (boto3 is sync-only)\n- **No import-time warnings:** boto3 absence is only signalled when the S3 core is actually instantiated\n\n## Files changed\n\n| File | Change |\n|---|---|\n| `src/cachier/cores/s3.py` | New `_S3Core` class implementing the full `_BaseCore` interface |\n| `src/cachier/_types.py` | Add `S3Client` type alias; extend `Backend` literal with `\"s3\"` |\n| `src/cachier/core.py` | Wire S3 decorator parameters; import and instantiate `_S3Core` |\n| `pyproject.toml` | Add `s3` pytest marker; add `[project.optional-dependencies]` extras |\n| `tests/s3_tests/` | 18 tests using `moto[s3]` (no real AWS account required) |\n| `tests/requirements_s3.txt` | `boto3` + `moto[s3]` test deps |\n| `examples/s3_example.py` | Runnable demo |\n\n## Test plan\n\n- [x] `pytest -m s3` - all 18 S3 tests pass (uses moto for offline mocking)\n- [x] `pytest -m \"not (mongo or redis or sql or s3)\"` - 219 existing tests pass, 0 regressions\n- [x] `ruff check` - no linting errors on changed files\n- [x] `mypy src/cachier/` - only pre-existing SQL overload error; boto3 stubs handled with `# type: ignore[import-untyped]`\n\n## Open questions (from issue)\n\nThe following points from the original issue are left for follow-up if desired:\n- Async `s3_client_factory` (currently sync-only, matching boto3's nature)\n- Server-side encryption options in the core API\n- Multipart uploads for very large cached values\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)","base","head","base_sha","d3b000afa34f14cd8398e7ec02a3b27d9e9359da","head_sha","6b3e2978efd0ea581918b51b5b46e54709d8c77c","merge_commit_sha","b8c7815e5be23f284646c40016f0d3e765169a12","comments","diff","user",{"_248":295,"_166":295,"_296":-5,"_252":297,"_41":298},"commits",9,"changed_files",14,"additions",1627,"deletions",21,"shaypal5","email","https://avatars.githubusercontent.com/u/917954?v=4",917954,"events",[301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352,353,354,355,356,357,358,359,360,361,362,363,364,365,366,367,368,369,370,371,372,373,374,375,376,377,378,379,380,381,382,383,384,385,386,387,388,389,390,391,392,393,394,395,396,397,398,399,400,401,402,403,404,405,406,407,408,409,410,411,412,413,414,415,416,417,418,419,420,421,422,423,424,425,426,427,428,429,430,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445,446,447,448,449,450,451,452,453,454,455,456,457,458,459,460,461],{"_149":471,"_463":1332},{"_149":471,"_463":1327},{"_149":471,"_463":1322},{"_149":471,"_463":1318},{"_149":489,"_463":1313},{"_149":484,"_463":1304},{"_149":471,"_463":1299},{"_149":471,"_463":1296},{"_149":489,"_463":1291},{"_149":484,"_463":1281},{"_149":471,"_463":1276},{"_149":471,"_463":1271},{"_149":471,"_463":1268},{"_149":489,"_463":1264},{"_149":484,"_463":1255},{"_149":471,"_463":1250},{"_149":471,"_463":1245},{"_149":471,"_463":1242},{"_149":489,"_463":1238},{"_149":484,"_463":1230},{"_149":471,"_463":1225},{"_149":471,"_463":1222},{"_149":489,"_463":1218},{"_149":484,"_463":1210},{"_149":471,"_463":1205},{"_149":471,"_463":1200},{"_149":471,"_463":1197},{"_149":489,"_463":1193},{"_149":484,"_463":1183},{"_149":471,"_463":1178},{"_149":471,"_463":1173},{"_149":471,"_463":1170},{"_149":489,"_463":1166},{"_149":484,"_463":1157},{"_149":471,"_463":1152},{"_149":471,"_463":1149},{"_149":489,"_463":1145},{"_149":484,"_463":1137},{"_149":471,"_463":1132},{"_149":471,"_463":1129},{"_149":489,"_463":1125},{"_149":484,"_463":1117},{"_149":471,"_463":1112},{"_149":471,"_463":1107},{"_149":471,"_463":1104},{"_149":489,"_463":1100},{"_149":484,"_463":1092},{"_149":471,"_463":1087},{"_149":471,"_463":1084},{"_149":489,"_463":1080},{"_149":484,"_463":1072},{"_149":471,"_463":1067},{"_149":471,"_463":1062},{"_149":471,"_463":1059},{"_149":489,"_463":1054},{"_149":484,"_463":1040},{"_149":471,"_463":1035},{"_149":471,"_463":1030},{"_149":471,"_463":1027},{"_149":489,"_463":1023},{"_149":484,"_463":1015},{"_149":471,"_463":1010},{"_149":471,"_463":1005},{"_149":471,"_463":1002},{"_149":489,"_463":998},{"_149":484,"_463":990},{"_149":471,"_463":985},{"_149":471,"_463":980},{"_149":471,"_463":977},{"_149":471,"_463":973},{"_149":489,"_463":968},{"_149":484,"_463":961},{"_149":471,"_463":956},{"_149":471,"_463":951},{"_149":471,"_463":948},{"_149":471,"_463":942},{"_149":489,"_463":937},{"_149":484,"_463":926},{"_149":471,"_463":921},{"_149":471,"_463":916},{"_149":471,"_463":913},{"_149":489,"_463":909},{"_149":484,"_463":901},{"_149":471,"_463":896},{"_149":471,"_463":891},{"_149":471,"_463":888},{"_149":489,"_463":884},{"_149":484,"_463":873},{"_149":471,"_463":868},{"_149":471,"_463":863},{"_149":471,"_463":860},{"_149":489,"_463":856},{"_149":484,"_463":848},{"_149":471,"_463":843},{"_149":471,"_463":838},{"_149":471,"_463":835},{"_149":489,"_463":831},{"_149":484,"_463":823},{"_149":471,"_463":818},{"_149":471,"_463":813},{"_149":471,"_463":810},{"_149":489,"_463":806},{"_149":484,"_463":797},{"_149":471,"_463":792},{"_149":471,"_463":787},{"_149":471,"_463":784},{"_149":489,"_463":780},{"_149":484,"_463":769},{"_149":471,"_463":764},{"_149":471,"_463":759},{"_149":471,"_463":756},{"_149":489,"_463":752},{"_149":484,"_463":743},{"_149":471,"_463":738},{"_149":471,"_463":733},{"_149":471,"_463":730},{"_149":489,"_463":726},{"_149":484,"_463":717},{"_149":471,"_463":712},{"_149":471,"_463":707},{"_149":471,"_463":704},{"_149":489,"_463":700},{"_149":484,"_463":692},{"_149":471,"_463":687},{"_149":471,"_463":682},{"_149":471,"_463":679},{"_149":489,"_463":675},{"_149":484,"_463":667},{"_149":471,"_463":662},{"_149":471,"_463":657},{"_149":471,"_463":654},{"_149":489,"_463":649},{"_149":484,"_463":638},{"_149":471,"_463":633},{"_149":471,"_463":628},{"_149":471,"_463":625},{"_149":471,"_463":620},{"_149":471,"_463":615},{"_149":471,"_463":612},{"_149":489,"_463":608},{"_149":484,"_463":600},{"_149":471,"_463":595},{"_149":471,"_463":592},{"_149":489,"_463":588},{"_149":484,"_463":577},{"_149":471,"_463":572},{"_149":471,"_463":567},{"_149":471,"_463":564},{"_149":489,"_463":560},{"_149":484,"_463":550},{"_149":471,"_463":545},{"_149":471,"_463":540},{"_149":471,"_463":534},{"_149":489,"_463":529},{"_149":484,"_463":509},{"_149":471,"_463":500},{"_149":471,"_463":492},{"_149":489,"_463":490},{"_149":484,"_463":485},{"_149":471,"_463":472},{"_149":462,"_463":464},"turn/completed","params",{"_465":466,"_86":467},"threadId","task_e_6995ade3452c8323a4bb7d7eb8515f97",{"_102":-5,"_41":82,"_468":469,"_470":112},"items",[],"status","rawResponseItem/completed",{"_473":474,"_465":466,"_475":82},"item",{"_476":477,"_478":-5,"_41":-5,"_479":-5,"_95":92,"_91":480},"turnId","content",[481],"end_turn","phase","message",{"_45":482,"_91":483},"### Summary\n* Updated the S3 core async behavior to be explicitly event-loop safe by overriding async methods and offloading sync boto3 operations with `asyncio.to_thread` (`aget_entry`, `aget_entry_by_key`, `aset_entry`, `amark_entry_being_calculated`, `amark_entry_not_calculated`). This preserves delegated async semantics (not native async).【F:src/cachier/cores/s3.py†L29-L35】【F:src/cachier/cores/s3.py†L374-L422】\n* Added an async regression test for S3 cache-hit behavior using `@pytest.mark.asyncio` and `@cachier(backend=\"s3\", ...)`, asserting second async call is served from cache (`call_count == 1`).【F:tests/s3_tests/test_s3_core.py†L191-L209】\n* Updated README to reflect S3 as a current supported backend, removed it from future features, added S3 dependency install guidance, documented delegated sync/async behavior, and added S3 to the core compatibility table as `Yes (delegated)` with thread-offloaded constraint wording.【F:README.rst†L55-L76】【F:README.rst†L583-L587】【F:README.rst†L598-L644】【F:README.rst†L669-L676】\n\n### Key behavior change for async S3\n* Async-decorated functions using the S3 backend now avoid direct blocking I/O on the event-loop thread by routing key async cache operations through `asyncio.to_thread`, while still using sync boto3 underneath (delegated mode, backward compatible).【F:src/cachier/cores/s3.py†L374-L422】\n\n### Testing\n* ⚠️ `pytest tests/s3_tests/test_s3_core.py` (all tests skipped in this environment because `boto3`/`moto` are not installed). \n* ✅ `ruff check src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py`\n\n### Follow-up recommendation\n* If desired later, open a separate issue/PR for optional native async S3 support (`aioboto3`) as an additive enhancement; keep current delegated mode as default for compatibility.","output_text","item/completed",{"_473":486,"_465":466,"_475":82},{"_41":487,"_479":-5,"_45":482,"_91":488},"legacy_agentMessage_28","agentMessage","item/started",{"_473":491,"_465":466,"_475":82},{"_41":487,"_479":-5,"_45":180,"_91":488},{"_473":493,"_465":466,"_475":82},{"_476":-5,"_494":495,"_41":496,"_497":498,"_91":499},"encrypted_content","gAAAAABpla6k5u4NjFespeDsZ5twcMNxuyfx6RpngJP16GSqxPQCxoWmrOrA6unswASw44YzJ17PF-5Y22pBdtBlGS48ldhRVFBg7J4GDKUoHDgH3Fk_Y5l2sctbfkpkTTNfEBbIW2JRV4gQokF6apw1LQnZ_Hgo_QhwobcdBroLT7XzOZPEOD_YYq6Yx4nm1AvcmYsSGV1QU6EJOi2XAdI12SGhJu6X8jsvL8TBIRkFGYoRYbxZPcS_qgCJQ-UefgOw0f3J9X3IU1PlsMSb8d_NFKMzL1GV2ef1CQzchJq2WX5fNdBaDyRDGqvBgYKv41jMBxfnfP_oEmEZyyy0V3XuyV55MRqtpk2ygd83s2aWyHpBj2NKTH4FRN8pxzppU4wyFlmHWyuQURK2Ksc4RVrRUpaV-wRnhEMSXMJ0R8YTls5kIiJkAqzSWFvKaJ6iK1Mo29_evTiOAI1pgYbLgrcSffrg2PfoeJ7V6tX8F-k6C4SdNnwanQHezM3q-7BpyS110MQZW6xij1qyhmMPB3CRld_6xc2XP7Vgowl3FLpGtKnlIFrys8VR_6OKNibOyviIycNNbuNs5A61GAhKSy4mqposMzcjg9Px1aUxfE8Rtv1I5M2xFx8UV6I9zUqjIDuWW2fhpPzrzJiiew4H-IIPmMFOeVK_Accw83PcBRkNfby4zpBGIUCyWh6WuYI7FR0M_-zwWHw8ngzJjqmV--ZPVuRs-7SjJeoiSH6aQFYhyAUSXFMsyzmQqu7nLSZY-ZVo_BY8wxCBGVpPW32__vN5iioqdW13xp_NF-Sql0LpqZf_NEYB8QEy8UjFnTvfKk_ETGffsAmZs-f_YG1LvZjl2BoosKdnx0kJes8kKTFta8zCcg3VSiBIDeRxicz93Ek7JpbbX--2ms5SKkuhOEErCOYXdNY6_SNScOXG-ozszm6anGRAvaYPqHPfqgHaM4ohMe1Rv9yk2BOTv7tP2a3tNbf_4MqsMUVqc3bfbWo0yDHb850vPWtWC_V3XnnPVReQFSMI0eqHD1k3D8Fs76gVZYVuJZH_fVhjmFiPGh4ROq7aqkyAhiTNjbR_IVVEsViUuPm1O8kiZ_ICAZIoHavANb9cYvqWKHB2xRQzsDOQlFj49uXzJo_r2bONi8GeUac5TTGFy1jyF__qKCn1_EaY_XMsz32Ldj_dDIdKD9bMDjwvakmajZLGi0PXlXmutC8pn2gQSX6hD5V0pzPkpJR5QNa-zroR9c5n4lTFFi4HCsn-WLFUOzhA4_iqAn0ViGLpCjmMCN_UjVAa6cSQHeXik9eQJUXjbc5Q0O82VJl73NvHvucJKS_BBWYGJ3wSIpYuPSiKodNFdnANHFVHNyo4183GZuzLyqQaMl0ZbguJH3Kv5-8VOIJ0SjrjGCKiK4H_G-T5qjByjnA5XZl0zWOL4-vCqyxOhmuMqg6e3qNgAgruwK7bBbIxqbM9fsAgj_Gb7Wsbcz497_qiFpe3TqXX7QC5MNpSc8puO_KfD-t44Y2U7LRtqqAIYheC0aMywWKKIqPiIpjTbBSUBSaN-VHspEL9qphGQZ_x7S5KZZ4DKkj6hCQdc9LcL_IiLAYaqn_K_monloqWcUhzXgdpm5StA9Kil9ph9FTIioYejfZVqaoArryYbSWDdLESoKD4AyjZsF-53ShDsFwmZSuiG3WcHtmBhwta4FEJ1V_jeaKHAQGzNmJlFY3qvF9VHKnpG3qecPuZPIsCWWynMbX7LSF1SEWMiztWgEzCUHbBO4e4CSPLTCH8yn9ZUzl0b-G-YnSntX8BMDfK4OL58ocXOTB6pdleYSNkKjNFkOIGfiXHeo0dlRjmYLN6n63L4jSPGna-88-y0TEu_P4cT66CzbRuPYGNMAFdkfgcXJM7bII-I31VCr8lpBxh1-CGZHueUIylZTqW2heTysgO5cFzQ76cJpojqsIKvzDR0CXMd_2e4bhbRoDk5ljl2OdAw3peS1fF_hoL80wonyceI34u3Cau2R2CqZIBToV6bssTmv17Cve0c4DIkDEfpBvyyezAgi7SFNqCSsK_uC4tAXCNKcClZaamlaWtkCkBKXwkm8Ll9XL0dQEWFUKn0Pp2CKkhbS4hhEyT8ajgz19mya9dkyJ4jPgb15BB8tzV7YY9sgb4xE4_UkVV3h9gviy-ntMPW5-FFPtmK8PS_t9-xiyYZX3-DeyUnd0Ro9Bx3X3I2RK2F94w2OQP6W-6zcIyBJB1XowtMaFs6SB5","legacy_responseItem_reasoning_27","summary",[],"reasoning",{"_473":501,"_465":466,"_475":82},{"_502":503,"_504":505,"_91":506},"call_id","call_gI8lifRJhxr2sw9Evqh0RJtv","output",{"_273":507,"_508":-5},"function_call_output","Chunk ID: a59046\nWall time: 0.0510 seconds\nProcess exited with code 0\nOriginal token count: 1686\nOutput:\n 50\t* Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n 51\t* Supported and `tested on Linux, OS X and Windows `_.\n 52\t* A simple interface.\n 53\t* Defining \"shelf life\" for cached values.\n 54\t* Async and sync functions support.\n 55\t* Multiple caching backends (cores):\n 56\t\n 57\t * Local caching using pickle files.\n 58\t * In-memory caching using the memory core.\n 59\t * Cross-machine caching using MongoDB.\n 60\t * SQL-based caching using SQLAlchemy-supported databases.\n 61\t * Redis-based caching for high-performance scenarios.\n 62\t * S3-based caching for cross-machine object storage backends.\n 63\t\n 64\t* Thread-safety.\n 65\t* **Per-call max age:** Specify a maximum age for cached values per call.\n 66\t\n 67\tCachier is **NOT**:\n 68\t\n 69\t* Meant as a transient cache. Python's @lru_cache is better.\n 70\t* Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n 71\t\n 72\tFuture features\n 73\t---------------\n 74\t\n 75\t* Multi-core caching.\n 76\t* `Cache replacement policies `_\n 77\t\n 78\t\n 79\tUse\n 80\t===\n 81\t\n 82\tCachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutable containers). Also, notice that since objects which are instances of user-defined classes are hashable but all compare unequal (their hash value is their id), equal objects across different sessions will not yield identical keys.\n 83\t\n 84\tSetting up a Cache\n 85\t------------------\n 86\tYou can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n 87\t\n 88\t.. code-block:: python\n 89\t\n 90\t from cachier import cachier\n 572\t\n 573\t**Table Schema:**\n 574\t\n 575\t- ``function_id``: Unique identifier for the cached function\n 576\t- ``key``: Cache key\n 577\t- ``value``: Pickled result\n 578\t- ``timestamp``: Datetime of cache entry\n 579\t- ``stale``: Boolean, is value stale\n 580\t- ``processing``: Boolean, is value being calculated\n 581\t- ``completed``: Boolean, is value calculation completed\n 582\t\n 583\t**S3 Sync/Async Support:**\n 584\t\n 585\t- Sync functions use direct boto3 calls.\n 586\t- Async functions are supported via thread-offloaded sync boto3 calls\n 587\t (delegated mode), not a native async client.\n 588\t\n 589\t**Limitations & Notes:**\n 590\t\n 591\t- Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n 592\t- For production, use a persistent database (not ``:memory:``)\n 593\t- Thread/process safety is handled via transactions and row-level locks\n 594\t- Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database is compromised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if security is a concern.\n 595\t- For best performance, ensure your DB supports row-level locking\n 596\t\n 597\t\n 598\tCore Sync/Async Compatibility\n 599\t------------------------------\n 600\t\n 601\tThe table below summarises sync and async function support across all cachier cores.\n 602\tCores marked as *delegated* run async operations on top of the sync implementation\n 603\t(no event loop or async driver is required). Cores marked as *native* use dedicated\n 604\tasync drivers and require the client or engine type to match the decorated function.\n 605\t\n 606\t.. list-table::\n 607\t :header-rows: 1\n 608\t :widths: 15 12 12 50\n 609\t\n 610\t * - Core\n 611\t - Sync\n 612\t - Async\n 613\t - Constraint\n 614\t * - **Pickle**\n 615\t - Yes\n 616\t - Yes (delegated)\n 617\t - None. No special configuration needed for async functions.\n 618\t * - **Memory**\n 619\t - Yes\n 620\t - Yes (delegated)\n 621\t - None. No special configuration needed for async functions.\n 622\t * - **MongoDB**\n 623\t - Yes\n 624\t - Yes (native)\n 625\t - ``mongetter`` must be a sync callable for sync functions and an async callable\n 626\t for async functions. Passing a sync ``mongetter`` to an async function raises\n 627\t ``TypeError``.\n 628\t * - **SQL**\n 629\t - Yes\n 630\t - Yes (native)\n 631\t - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n 632\t functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n 633\t in either direction raises ``TypeError``.\n 634\t * - **Redis**\n 635\t - Yes\n 636\t - Yes (native)\n 637\t - ``redis_client`` must be a sync client or sync callable for sync functions and\n 638\t an async callable returning a ``redis.asyncio.Redis`` client for async\n 639\t functions. Passing a sync callable to an async function raises ``TypeError``.\n 640\t * - **S3**\n 641\t - Yes\n 642\t - Yes (delegated)\n 643\t - Async support is delegated via thread-offloaded sync boto3 calls\n 644\t (``asyncio.to_thread``). No async S3 client is required.\n 645\t\n 646\t\n 647\tContributing\n 648\t============\n 649\t\n 650\tCurrent maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n 651\t\n 652\tInstalling for development\n 660\t\n 661\t\n 662\tInstall in development mode with test dependencies for local cores (memory and pickle) only:\n 663\t\n 664\t.. code-block:: bash\n 665\t\n 666\t cd cachier\n 667\t pip install -e . -r tests/requirements.txt\n 668\t\n 669\tEach additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n 670\t\n 671\t.. code-block:: bash\n 672\t\n 673\t pip install -r tests/requirements_mongodb.txt\n 674\t pip install -r tests/requirements_redis.txt\n 675\t pip install -r tests/requirements_postgres.txt\n 676\t pip install -r tests/requirements_s3.txt\n 677\t\n 678\tRunning the tests\n 679\t-----------------\n 680\t\n 681\tTo run the tests, call the ``pytest`` command in the repository's root, or:\n 682\t\n 683\t.. code-block:: bash\n 684\t\n","success",{"_473":510,"_465":466,"_475":82},{"_511":512,"_513":514,"_515":516,"_517":518,"_519":520,"_521":31,"_41":503,"_522":523,"_470":112,"_91":524},"aggregatedOutput"," 50\t* Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n 51\t* Supported and `tested on Linux, OS X and Windows `_.\n 52\t* A simple interface.\n 53\t* Defining \"shelf life\" for cached values.\n 54\t* Async and sync functions support.\n 55\t* Multiple caching backends (cores):\n 56\t\n 57\t * Local caching using pickle files.\n 58\t * In-memory caching using the memory core.\n 59\t * Cross-machine caching using MongoDB.\n 60\t * SQL-based caching using SQLAlchemy-supported databases.\n 61\t * Redis-based caching for high-performance scenarios.\n 62\t * S3-based caching for cross-machine object storage backends.\n 63\t\n 64\t* Thread-safety.\n 65\t* **Per-call max age:** Specify a maximum age for cached values per call.\n 66\t\n 67\tCachier is **NOT**:\n 68\t\n 69\t* Meant as a transient cache. Python's @lru_cache is better.\n 70\t* Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n 71\t\n 72\tFuture features\n 73\t---------------\n 74\t\n 75\t* Multi-core caching.\n 76\t* `Cache replacement policies `_\n 77\t\n 78\t\n 79\tUse\n 80\t===\n 81\t\n 82\tCachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutable containers). Also, notice that since objects which are instances of user-defined classes are hashable but all compare unequal (their hash value is their id), equal objects across different sessions will not yield identical keys.\n 83\t\n 84\tSetting up a Cache\n 85\t------------------\n 86\tYou can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n 87\t\n 88\t.. code-block:: python\n 89\t\n 90\t from cachier import cachier\n 572\t\n 573\t**Table Schema:**\n 574\t\n 575\t- ``function_id``: Unique identifier for the cached function\n 576\t- ``key``: Cache key\n 577\t- ``value``: Pickled result\n 578\t- ``timestamp``: Datetime of cache entry\n 579\t- ``stale``: Boolean, is value stale\n 580\t- ``processing``: Boolean, is value being calculated\n 581\t- ``completed``: Boolean, is value calculation completed\n 582\t\n 583\t**S3 Sync/Async Support:**\n 584\t\n 585\t- Sync functions use direct boto3 calls.\n 586\t- Async functions are supported via thread-offloaded sync boto3 calls\n 587\t (delegated mode), not a native async client.\n 588\t\n 589\t**Limitations & Notes:**\n 590\t\n 591\t- Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n 592\t- For production, use a persistent database (not ``:memory:``)\n 593\t- Thread/process safety is handled via transactions and row-level locks\n 594\t- Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database is compromised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if security is a concern.\n 595\t- For best performance, ensure your DB supports row-level locking\n 596\t\n 597\t\n 598\tCore Sync/Async Compatibility\n 599\t------------------------------\n 600\t\n 601\tThe table below summarises sync and async function support across all cachier cores.\n 602\tCores marked as *delegated* run async operations on top of the sync implementation\n 603\t(no event loop or async driver is required). Cores marked as *native* use dedicated\n 604\tasync drivers and require the client or engine type to match the decorated function.\n 605\t\n 606\t.. list-table::\n 607\t :header-rows: 1\n 608\t :widths: 15 12 12 50\n 609\t\n 610\t * - Core\n 611\t - Sync\n 612\t - Async\n 613\t - Constraint\n 614\t * - **Pickle**\n 615\t - Yes\n 616\t - Yes (delegated)\n 617\t - None. No special configuration needed for async functions.\n 618\t * - **Memory**\n 619\t - Yes\n 620\t - Yes (delegated)\n 621\t - None. No special configuration needed for async functions.\n 622\t * - **MongoDB**\n 623\t - Yes\n 624\t - Yes (native)\n 625\t - ``mongetter`` must be a sync callable for sync functions and an async callable\n 626\t for async functions. Passing a sync ``mongetter`` to an async function raises\n 627\t ``TypeError``.\n 628\t * - **SQL**\n 629\t - Yes\n 630\t - Yes (native)\n 631\t - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n 632\t functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n 633\t in either direction raises ``TypeError``.\n 634\t * - **Redis**\n 635\t - Yes\n 636\t - Yes (native)\n 637\t - ``redis_client`` must be a sync client or sync callable for sync functions and\n 638\t an async callable returning a ``redis.asyncio.Redis`` client for async\n 639\t functions. Passing a sync callable to an async function raises ``TypeError``.\n 640\t * - **S3**\n 641\t - Yes\n 642\t - Yes (delegated)\n 643\t - Async support is delegated via thread-offloaded sync boto3 calls\n 644\t (``asyncio.to_thread``). No async S3 client is required.\n 645\t\n 646\t\n 647\tContributing\n 648\t============\n 649\t\n 650\tCurrent maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n 651\t\n 652\tInstalling for development\n 660\t\n 661\t\n 662\tInstall in development mode with test dependencies for local cores (memory and pickle) only:\n 663\t\n 664\t.. code-block:: bash\n 665\t\n 666\t cd cachier\n 667\t pip install -e . -r tests/requirements.txt\n 668\t\n 669\tEach additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n 670\t\n 671\t.. code-block:: bash\n 672\t\n 673\t pip install -r tests/requirements_mongodb.txt\n 674\t pip install -r tests/requirements_redis.txt\n 675\t pip install -r tests/requirements_postgres.txt\n 676\t pip install -r tests/requirements_s3.txt\n 677\t\n 678\tRunning the tests\n 679\t-----------------\n 680\t\n 681\tTo run the tests, call the ``pytest`` command in the repository's root, or:\n 682\t\n 683\t.. code-block:: bash\n 684\t\n","command","/bin/bash -lc 'nl -ba README.rst | sed -n '\"'\"'50,90p'\"'\"' && nl -ba README.rst | sed -n '\"'\"'572,652p'\"'\"' && nl -ba README.rst | sed -n '\"'\"'660,684p'\"'\"''","commandActions",[525],"cwd","/workspace/cachier","durationMs",51,"exitCode","processId","43383","commandExecution",{"_513":526,"_166":527,"_156":527,"_91":528},"nl -ba README.rst","README.rst","read",{"_473":530,"_465":466,"_475":82},{"_511":-5,"_513":514,"_515":531,"_517":518,"_519":-5,"_521":-5,"_41":503,"_522":523,"_470":532,"_91":524},[533],"inProgress",{"_513":526,"_166":527,"_156":527,"_91":528},{"_473":535,"_465":466,"_475":82},{"_536":537,"_502":503,"_41":-5,"_166":538,"_91":539},"arguments","{\"cmd\":\"nl -ba README.rst | sed -n '50,90p' && nl -ba README.rst | sed -n '572,652p' && nl -ba README.rst | sed -n '660,684p'\"}","exec_command","function_call",{"_473":541,"_465":466,"_475":82},{"_476":-5,"_494":542,"_41":543,"_497":544,"_91":499},"gAAAAABpla6eoCcDGZp1lIQQ_jXt98QOf2YJceRwJ7jmtzHOFJRikQM5uxaaI3i39vpRRR0-h6s7GO8aLQW5lRO5yTji_ZgCAspe_TvW8ft6QzPCXXiZpTx-nnzbYfbXuCBY7V-HD2u-cBflbPmbrC0gHH5fnLT6EfJiDAzoTOy5q3lXm7ZDYRHQ8iEUDnoKFGlbbw3vPXDVP1yuw65hvClW1Kip5Y-fLcYhSFcPvk1hzm2PoALshH2y7haUJ0PiVRgFzlM0PTDY_cLr4pLosIMFE9ZYm70_VpWK8lNwdjERpXaJz9GpMULk5JaZ4AoXbAGanh5dQdFgztJoCnZ5T6ScBTuwDRGD8TnFV14_PVPlUrbFeRYLdspohTxiiNathPcHq1oM0vY1Xgf8m5YqjdEkCWogrpIK8I2EaR3u3XZnNkKbzu606f3d7cI0rjxfrtb0gxQnJ_R0DGSFlFrlDVDaqTkXiS5QOzEDT_w0kKuLrONUYUf9P1m1Is3Kq2ROyant2xUs_ddl4Ver0JC51x5xki7ooI50UHsHY5nMR4BnTHkicRf9R-twx3mq0BgO01dJ6Qt_uvGpNOLA6jj-4Z6rTQSSdtc1aygzTtuZVshPI2BjluySmCDzOOmYLaX7LZmDYFeLrcO4QRejSc97TWNFOHchwc5OPeyV3qsn6xl8QlT50EHPkN7XDqQknXPfZJ-QMGT2gLPjgnEOPDZd2su9H2F7I6uV2g6yWENdjQ9Jkd4Z43H1eQYq_Tc0pyMjXmRfjfNv7RL7b0_ulYQTHauMe8s314uyghlu_CdrpL7PqlUDgiMgo3RHZib_65JdZHMp85PRd7oKQEK6t08Cnl3xulL3vIiUpQtv5wi85SrT_omOZS2Fjyg=","legacy_responseItem_reasoning_26",[],{"_473":546,"_465":466,"_475":82},{"_502":547,"_504":548,"_91":506},"call_a7kV5vBs0KHWYWjVOvERndqP",{"_273":549,"_508":-5},"Chunk ID: 609ff7\nWall time: 0.0511 seconds\nProcess exited with code 0\nOriginal token count: 2225\nOutput:\n 1\t\"\"\"Tests for the S3 caching core.\"\"\"\n 2\t\n 3\timport asyncio\n 4\timport contextlib\n 5\timport threading\n 6\timport warnings\n 7\tfrom datetime import timedelta\n 8\tfrom random import random\n 9\t\n 10\timport pytest\n 11\t\n 12\tfrom tests.s3_tests.helpers import S3_DEPS_AVAILABLE, TEST_BUCKET, TEST_REGION, skip_if_missing\n 13\t\n 14\tif S3_DEPS_AVAILABLE:\n 15\t import boto3\n 16\t from moto import mock_aws\n 17\t\n 18\t from cachier import cachier\n 19\t from cachier.cores.s3 import MissingS3Bucket, _S3Core\n 20\t\n 21\t\n 22\t# ---------------------------------------------------------------------------\n 23\t# Helpers\n 24\t# ---------------------------------------------------------------------------\n 25\t\n 26\t\n 27\tdef _make_core(s3_bucket=TEST_BUCKET, s3_client=None, s3_prefix=\"cachier\"):\n 28\t \"\"\"Return a bare _S3Core (set_func must still be called before use).\"\"\"\n 29\t skip_if_missing()\n 30\t return _S3Core(\n 31\t hash_func=None,\n 32\t s3_bucket=s3_bucket,\n 33\t s3_prefix=s3_prefix,\n 34\t s3_client=s3_client,\n 35\t )\n 36\t\n 37\t\n 38\t# ---------------------------------------------------------------------------\n 39\t# Basic construction and validation\n 40\t# ---------------------------------------------------------------------------\n 41\t\n 42\t\n 43\t@pytest.mark.s3\n 44\tdef test_missing_bucket_raises():\n 45\t skip_if_missing()\n 46\t with pytest.raises(MissingS3Bucket):\n 47\t _S3Core(hash_func=None, s3_bucket=None)\n 48\t\n 49\t\n 50\t@pytest.mark.s3\n 51\tdef test_missing_bucket_empty_string_raises():\n 52\t skip_if_missing()\n 53\t with pytest.raises(MissingS3Bucket):\n 54\t _S3Core(hash_func=None, s3_bucket=\"\")\n 55\t\n 56\t\n 57\t@pytest.mark.s3\n 58\tdef test_missing_boto3_warns(monkeypatch):\n 59\t skip_if_missing()\n 60\t import cachier.cores.s3 as s3_mod\n 61\t\n 62\t monkeypatch.setattr(s3_mod, \"BOTO3_AVAILABLE\", False)\n 63\t with warnings.catch_warnings(record=True) as caught:\n 64\t warnings.simplefilter(\"always\")\n 65\t with contextlib.suppress(Exception):\n 66\t _S3Core(hash_func=None, s3_bucket=\"bucket\")\n 67\t assert any(\"boto3\" in str(w.message) for w in caught)\n 68\t\n 69\t\n 70\t# ---------------------------------------------------------------------------\n 71\t# Core caching behaviour\n 72\t# ---------------------------------------------------------------------------\n 73\t\n 74\t\n 75\t@pytest.mark.s3\n 76\tdef test_s3_core_basic_caching(s3_bucket):\n 77\t \"\"\"Cached result is returned on the second call.\"\"\"\n 78\t\n 79\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 80\t def _cached(x):\n 81\t return random() + x\n 82\t\n 83\t _cached.clear_cache()\n 84\t val1 = _cached(1)\n 85\t val2 = _cached(1)\n 86\t assert val1 == val2\n 87\t\n 88\t\n 89\t@pytest.mark.s3\n 90\tdef test_s3_core_different_args(s3_bucket):\n 91\t \"\"\"Different arguments produce different cache entries.\"\"\"\n 92\t\n 93\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 94\t def _cached(x):\n 95\t return random() + x\n 96\t\n 97\t _cached.clear_cache()\n 98\t val1 = _cached(1)\n 99\t val2 = _cached(2)\n 100\t assert val1 != val2\n 101\t\n 102\t\n 103\t@pytest.mark.s3\n 104\tdef test_s3_core_skip_cache(s3_bucket):\n 105\t \"\"\"cachier__skip_cache bypasses the cache.\"\"\"\n 106\t\n 107\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 108\t def _cached(x):\n 109\t return random()\n 110\t\n 111\t _cached.clear_cache()\n 112\t val1 = _cached(1)\n 113\t val2 = _cached(1, cachier__skip_cache=True)\n 114\t assert val1 != val2\n 115\t\n 116\t\n 117\t@pytest.mark.s3\n 118\tdef test_s3_core_overwrite_cache(s3_bucket):\n 119\t \"\"\"cachier__overwrite_cache forces recalculation.\"\"\"\n 120\t\n 121\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 122\t def _cached(x):\n 123\t return random()\n 124\t\n 125\t _cached.clear_cache()\n 126\t val1 = _cached(1)\n 127\t val2 = _cached(1, cachier__overwrite_cache=True)\n 128\t val3 = _cached(1)\n 129\t assert val1 != val2\n 130\t assert val2 == val3\n 131\t\n 132\t\n 133\t@pytest.mark.s3\n 134\tdef test_s3_core_stale_after(s3_bucket):\n 135\t \"\"\"A result older than stale_after is recomputed.\"\"\"\n 136\t\n 137\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, stale_after=timedelta(seconds=1))\n 138\t def _cached(x):\n 139\t return random()\n 140\t\n 141\t _cached.clear_cache()\n 142\t val1 = _cached(1)\n 143\t import time\n 144\t\n 145\t time.sleep(2)\n 146\t val2 = _cached(1)\n 147\t assert val1 != val2\n 148\t\n 149\t\n 150\t@pytest.mark.s3\n 151\tdef test_s3_core_next_time(s3_bucket):\n 152\t \"\"\"With next_time=True, stale result is returned immediately.\"\"\"\n 153\t\n 154\t @cachier(\n 155\t backend=\"s3\",\n 156\t s3_bucket=s3_bucket,\n 157\t s3_region=TEST_REGION,\n 158\t stale_after=timedelta(seconds=1),\n 159\t next_time=True,\n 160\t )\n 161\t def _cached(x):\n 162\t return random()\n 163\t\n 164\t _cached.clear_cache()\n 165\t val1 = _cached(1)\n 166\t import time\n 167\t\n 168\t time.sleep(2)\n 169\t val2 = _cached(1) # stale; should return old value immediately\n 170\t assert val1 == val2\n 171\t\n 172\t\n 173\t@pytest.mark.s3\n 174\tdef test_s3_core_allow_none(s3_bucket):\n 175\t \"\"\"None results are cached when allow_none=True.\"\"\"\n 176\t call_count = [0]\n 177\t\n 178\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, allow_none=True)\n 179\t def _cached(x):\n 180\t call_count[0] += 1\n 181\t return None\n 182\t\n 183\t _cached.clear_cache()\n 184\t res1 = _cached(1)\n 185\t res2 = _cached(1)\n 186\t assert res1 is None\n 187\t assert res2 is None\n 188\t assert call_count[0] == 1\n 189\t\n 190\t\n 191\t@pytest.mark.s3\n 192\t@pytest.mark.asyncio\n 193\tasync def test_s3_core_async_cache_hit(s3_bucket):\n 194\t \"\"\"Async S3 cache calls should hit cache on repeated arguments.\"\"\"\n 195\t call_count = [0]\n 196\t\n 197\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 198\t async def _cached(x):\n 199\t call_count[0] += 1\n 200\t await asyncio.sleep(0)\n 201\t return x * 5\n 202\t\n 203\t await _cached.clear_cache()\n 204\t value_1 = await _cached(6)\n 205\t value_2 = await _cached(6)\n 206\t\n 207\t assert value_1 == 30\n 208\t assert value_2 == 30\n 209\t assert call_count[0] == 1\n 210\t\n 211\t\n 212\t@pytest.mark.s3\n 213\tdef test_s3_core_none_not_cached_without_allow_none(s3_bucket):\n 214\t \"\"\"None results are NOT cached when allow_none=False (default).\"\"\"\n 215\t call_count = [0]\n 216\t\n 217\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, allow_none=False)\n 218\t def _cached(x):\n 219\t call_count[0] += 1\n 220\t return None\n 221\t\n 222\t _cached.clear_cache()\n 223\t _cached(1)\n 224\t _cached(1)\n 225\t assert call_count[0] == 2\n 226\t\n 227\t\n 228\t@pytest.mark.s3\n 229\tdef test_s3_core_clear_cache(s3_bucket):\n 230\t \"\"\"clear_cache removes all entries so the next call recomputes.\"\"\"\n 231\t call_count = [0]\n 232\t\n 233\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 234\t def _cached(x):\n 235\t call_count[0] += 1\n 236\t return x * 2\n 237\t\n 238\t _cached.clear_cache()\n 239\t _cached(5)\n 240\t _cached(5)\n 241\t assert call_count[0] == 1\n 242\t _cached.clear_cache()\n 243\t _cached(5)\n 244\t assert call_count[0] == 2\n 245\t\n 246\t\n 247\t@pytest.mark.s3\n 248\tdef test_s3_core_clear_being_calculated(s3_bucket):\n 249\t \"\"\"clear_being_calculated resets the processing flag on all entries.\"\"\"\n 250\t\n 251\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 252\t def _cached(x):\n 253\t return x\n 254\t\n 255\t _cached.clear_cache()\n 256\t _cached(1)\n 257\t _cached.clear_being_calculated() # should not raise\n 258\t\n 259\t\n 260\t# ---------------------------------------------------------------------------\n 261\t# entry_size_limit\n 262\t# ---------------------------------------------------------------------------\n 263\t\n 264\t\n 265\t@pytest.mark.s3\n 266\tdef test_s3_entry_size_limit(s3_bucket):\n 267\t \"\"\"Results larger than entry_size_limit are not cached.\"\"\"\n 268\t call_count = [0]\n 269\t\n 270\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, entry_size_limit=1)\n",{"_473":551,"_465":466,"_475":82},{"_511":552,"_513":553,"_515":554,"_517":518,"_519":520,"_521":31,"_41":547,"_522":555,"_470":112,"_91":524}," 1\t\"\"\"Tests for the S3 caching core.\"\"\"\n 2\t\n 3\timport asyncio\n 4\timport contextlib\n 5\timport threading\n 6\timport warnings\n 7\tfrom datetime import timedelta\n 8\tfrom random import random\n 9\t\n 10\timport pytest\n 11\t\n 12\tfrom tests.s3_tests.helpers import S3_DEPS_AVAILABLE, TEST_BUCKET, TEST_REGION, skip_if_missing\n 13\t\n 14\tif S3_DEPS_AVAILABLE:\n 15\t import boto3\n 16\t from moto import mock_aws\n 17\t\n 18\t from cachier import cachier\n 19\t from cachier.cores.s3 import MissingS3Bucket, _S3Core\n 20\t\n 21\t\n 22\t# ---------------------------------------------------------------------------\n 23\t# Helpers\n 24\t# ---------------------------------------------------------------------------\n 25\t\n 26\t\n 27\tdef _make_core(s3_bucket=TEST_BUCKET, s3_client=None, s3_prefix=\"cachier\"):\n 28\t \"\"\"Return a bare _S3Core (set_func must still be called before use).\"\"\"\n 29\t skip_if_missing()\n 30\t return _S3Core(\n 31\t hash_func=None,\n 32\t s3_bucket=s3_bucket,\n 33\t s3_prefix=s3_prefix,\n 34\t s3_client=s3_client,\n 35\t )\n 36\t\n 37\t\n 38\t# ---------------------------------------------------------------------------\n 39\t# Basic construction and validation\n 40\t# ---------------------------------------------------------------------------\n 41\t\n 42\t\n 43\t@pytest.mark.s3\n 44\tdef test_missing_bucket_raises():\n 45\t skip_if_missing()\n 46\t with pytest.raises(MissingS3Bucket):\n 47\t _S3Core(hash_func=None, s3_bucket=None)\n 48\t\n 49\t\n 50\t@pytest.mark.s3\n 51\tdef test_missing_bucket_empty_string_raises():\n 52\t skip_if_missing()\n 53\t with pytest.raises(MissingS3Bucket):\n 54\t _S3Core(hash_func=None, s3_bucket=\"\")\n 55\t\n 56\t\n 57\t@pytest.mark.s3\n 58\tdef test_missing_boto3_warns(monkeypatch):\n 59\t skip_if_missing()\n 60\t import cachier.cores.s3 as s3_mod\n 61\t\n 62\t monkeypatch.setattr(s3_mod, \"BOTO3_AVAILABLE\", False)\n 63\t with warnings.catch_warnings(record=True) as caught:\n 64\t warnings.simplefilter(\"always\")\n 65\t with contextlib.suppress(Exception):\n 66\t _S3Core(hash_func=None, s3_bucket=\"bucket\")\n 67\t assert any(\"boto3\" in str(w.message) for w in caught)\n 68\t\n 69\t\n 70\t# ---------------------------------------------------------------------------\n 71\t# Core caching behaviour\n 72\t# ---------------------------------------------------------------------------\n 73\t\n 74\t\n 75\t@pytest.mark.s3\n 76\tdef test_s3_core_basic_caching(s3_bucket):\n 77\t \"\"\"Cached result is returned on the second call.\"\"\"\n 78\t\n 79\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 80\t def _cached(x):\n 81\t return random() + x\n 82\t\n 83\t _cached.clear_cache()\n 84\t val1 = _cached(1)\n 85\t val2 = _cached(1)\n 86\t assert val1 == val2\n 87\t\n 88\t\n 89\t@pytest.mark.s3\n 90\tdef test_s3_core_different_args(s3_bucket):\n 91\t \"\"\"Different arguments produce different cache entries.\"\"\"\n 92\t\n 93\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 94\t def _cached(x):\n 95\t return random() + x\n 96\t\n 97\t _cached.clear_cache()\n 98\t val1 = _cached(1)\n 99\t val2 = _cached(2)\n 100\t assert val1 != val2\n 101\t\n 102\t\n 103\t@pytest.mark.s3\n 104\tdef test_s3_core_skip_cache(s3_bucket):\n 105\t \"\"\"cachier__skip_cache bypasses the cache.\"\"\"\n 106\t\n 107\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 108\t def _cached(x):\n 109\t return random()\n 110\t\n 111\t _cached.clear_cache()\n 112\t val1 = _cached(1)\n 113\t val2 = _cached(1, cachier__skip_cache=True)\n 114\t assert val1 != val2\n 115\t\n 116\t\n 117\t@pytest.mark.s3\n 118\tdef test_s3_core_overwrite_cache(s3_bucket):\n 119\t \"\"\"cachier__overwrite_cache forces recalculation.\"\"\"\n 120\t\n 121\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 122\t def _cached(x):\n 123\t return random()\n 124\t\n 125\t _cached.clear_cache()\n 126\t val1 = _cached(1)\n 127\t val2 = _cached(1, cachier__overwrite_cache=True)\n 128\t val3 = _cached(1)\n 129\t assert val1 != val2\n 130\t assert val2 == val3\n 131\t\n 132\t\n 133\t@pytest.mark.s3\n 134\tdef test_s3_core_stale_after(s3_bucket):\n 135\t \"\"\"A result older than stale_after is recomputed.\"\"\"\n 136\t\n 137\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, stale_after=timedelta(seconds=1))\n 138\t def _cached(x):\n 139\t return random()\n 140\t\n 141\t _cached.clear_cache()\n 142\t val1 = _cached(1)\n 143\t import time\n 144\t\n 145\t time.sleep(2)\n 146\t val2 = _cached(1)\n 147\t assert val1 != val2\n 148\t\n 149\t\n 150\t@pytest.mark.s3\n 151\tdef test_s3_core_next_time(s3_bucket):\n 152\t \"\"\"With next_time=True, stale result is returned immediately.\"\"\"\n 153\t\n 154\t @cachier(\n 155\t backend=\"s3\",\n 156\t s3_bucket=s3_bucket,\n 157\t s3_region=TEST_REGION,\n 158\t stale_after=timedelta(seconds=1),\n 159\t next_time=True,\n 160\t )\n 161\t def _cached(x):\n 162\t return random()\n 163\t\n 164\t _cached.clear_cache()\n 165\t val1 = _cached(1)\n 166\t import time\n 167\t\n 168\t time.sleep(2)\n 169\t val2 = _cached(1) # stale; should return old value immediately\n 170\t assert val1 == val2\n 171\t\n 172\t\n 173\t@pytest.mark.s3\n 174\tdef test_s3_core_allow_none(s3_bucket):\n 175\t \"\"\"None results are cached when allow_none=True.\"\"\"\n 176\t call_count = [0]\n 177\t\n 178\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, allow_none=True)\n 179\t def _cached(x):\n 180\t call_count[0] += 1\n 181\t return None\n 182\t\n 183\t _cached.clear_cache()\n 184\t res1 = _cached(1)\n 185\t res2 = _cached(1)\n 186\t assert res1 is None\n 187\t assert res2 is None\n 188\t assert call_count[0] == 1\n 189\t\n 190\t\n 191\t@pytest.mark.s3\n 192\t@pytest.mark.asyncio\n 193\tasync def test_s3_core_async_cache_hit(s3_bucket):\n 194\t \"\"\"Async S3 cache calls should hit cache on repeated arguments.\"\"\"\n 195\t call_count = [0]\n 196\t\n 197\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 198\t async def _cached(x):\n 199\t call_count[0] += 1\n 200\t await asyncio.sleep(0)\n 201\t return x * 5\n 202\t\n 203\t await _cached.clear_cache()\n 204\t value_1 = await _cached(6)\n 205\t value_2 = await _cached(6)\n 206\t\n 207\t assert value_1 == 30\n 208\t assert value_2 == 30\n 209\t assert call_count[0] == 1\n 210\t\n 211\t\n 212\t@pytest.mark.s3\n 213\tdef test_s3_core_none_not_cached_without_allow_none(s3_bucket):\n 214\t \"\"\"None results are NOT cached when allow_none=False (default).\"\"\"\n 215\t call_count = [0]\n 216\t\n 217\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, allow_none=False)\n 218\t def _cached(x):\n 219\t call_count[0] += 1\n 220\t return None\n 221\t\n 222\t _cached.clear_cache()\n 223\t _cached(1)\n 224\t _cached(1)\n 225\t assert call_count[0] == 2\n 226\t\n 227\t\n 228\t@pytest.mark.s3\n 229\tdef test_s3_core_clear_cache(s3_bucket):\n 230\t \"\"\"clear_cache removes all entries so the next call recomputes.\"\"\"\n 231\t call_count = [0]\n 232\t\n 233\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 234\t def _cached(x):\n 235\t call_count[0] += 1\n 236\t return x * 2\n 237\t\n 238\t _cached.clear_cache()\n 239\t _cached(5)\n 240\t _cached(5)\n 241\t assert call_count[0] == 1\n 242\t _cached.clear_cache()\n 243\t _cached(5)\n 244\t assert call_count[0] == 2\n 245\t\n 246\t\n 247\t@pytest.mark.s3\n 248\tdef test_s3_core_clear_being_calculated(s3_bucket):\n 249\t \"\"\"clear_being_calculated resets the processing flag on all entries.\"\"\"\n 250\t\n 251\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n 252\t def _cached(x):\n 253\t return x\n 254\t\n 255\t _cached.clear_cache()\n 256\t _cached(1)\n 257\t _cached.clear_being_calculated() # should not raise\n 258\t\n 259\t\n 260\t# ---------------------------------------------------------------------------\n 261\t# entry_size_limit\n 262\t# ---------------------------------------------------------------------------\n 263\t\n 264\t\n 265\t@pytest.mark.s3\n 266\tdef test_s3_entry_size_limit(s3_bucket):\n 267\t \"\"\"Results larger than entry_size_limit are not cached.\"\"\"\n 268\t call_count = [0]\n 269\t\n 270\t @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION, entry_size_limit=1)\n","/bin/bash -lc 'nl -ba tests/s3_tests/test_s3_core.py | sed -n '\"'\"'1,270p'\"'\"''",[556],"98163",{"_513":557,"_166":558,"_156":559,"_91":528},"nl -ba tests/s3_tests/test_s3_core.py | sed -n '1,270p'","test_s3_core.py","tests/s3_tests/test_s3_core.py",{"_473":561,"_465":466,"_475":82},{"_511":-5,"_513":553,"_515":562,"_517":518,"_519":-5,"_521":-5,"_41":547,"_522":555,"_470":532,"_91":524},[563],{"_513":557,"_166":558,"_156":559,"_91":528},{"_473":565,"_465":466,"_475":82},{"_536":566,"_502":547,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"nl -ba tests/s3_tests/test_s3_core.py | sed -n '1,270p'\"}",{"_473":568,"_465":466,"_475":82},{"_476":-5,"_494":569,"_41":570,"_497":571,"_91":499},"gAAAAABpla6bXOL0al96iOAGI6Ef3gTCRn_K5bpRwcP694Fl54LBQNK2qMgxFT0EPVMSF41anuYA9L2WWqivp-duYqs6CTqTiJPqavRrmLofDYxEPypJfISCM8LhxO9sZ8fcy0y2yuJ41U2RwGz7NFYSdh7vMwseGr_prD8xo67mCyLXd49hH87bNvV2a0U2uZPgk_3Svuoq2VjD-KPm_CWpdX8d287ffaf6WKGUn0uvcSKL1Ctv7FYfQf854lgFMDN8g8HzXeX2Z3Hq-E_AgnYpFZUPadlTkqMd59TLdd7iT4YSBODqMmq-JYzg7bYXevYBtVgQSuqlNlA04CBSPn80n_xJNJ72dHkpCp9A4y31_mC7FmOcyEXkM3jvOSm_4fYHXg-yarrRkZa_E3CQd2WNLvmteI7U3HZ9h4GEWK7m0Pg9FIUvKCiPqwArSbZSwPR6Tpg-e8Q8sUYjUEcdP0kS1Q6tk-HrkzwHbWREPeLshzIZMDyX56UvKxAVMnyHNoA7zRN6Kb3YvpALlQuWR_YIAXFwn4_UWBfPERmOxPm_SFZQPd6v4am3n5lb5wHXzF6ZiFLyzvkDqiEKEN96aLUQ00TBGmBM_N7WK0Q4MLZhMWOcUf7FTwhH1KrJiubZsxk4kzYzK1pQrxvFIa9CMgfgc9odsQdjgfQQRublGCWiJCbLNvuszmHNGnk81_CSCnrqCImgWwXef_38-JX0Y0ZxK1svD3-LQcyyIGZBwr08eaUVxKpXQMxrKN1DmfV93xRDnkkSLB6fOnnBHS6IJy1kszHUO-S-V4ixXDOEDFzhnXZkKkY53jOSmuX4sIU0Mp6usJ1-PF3T04PxLqnCx4vzxWBUMyHJgkYkmS3Bh0OHxtlC_VTZZFE=","legacy_responseItem_reasoning_25",[],{"_473":573,"_465":466,"_475":82},{"_502":574,"_504":575,"_91":506},"call_QonOzyBWUtsk93j3NPANRRfm",{"_273":576,"_508":-5},"Chunk ID: dadd41\nWall time: 0.0509 seconds\nProcess exited with code 0\nOriginal token count: 794\nOutput:\n 360\t for page in pages:\n 361\t for obj in page.get(\"Contents\", []):\n 362\t s3_key = obj[\"Key\"]\n 363\t try:\n 364\t response = client.get_object(Bucket=self.s3_bucket, Key=s3_key)\n 365\t body = response[\"Body\"].read()\n 366\t entry = self._load_entry(body)\n 367\t if entry is not None and entry.time < threshold:\n 368\t client.delete_object(Bucket=self.s3_bucket, Key=s3_key)\n 369\t except Exception as exc:\n 370\t warnings.warn(f\"S3 delete_stale_entries entry check failed: {exc}\", stacklevel=2)\n 371\t except Exception as exc:\n 372\t warnings.warn(f\"S3 delete_stale_entries failed: {exc}\", stacklevel=2)\n 373\t\n 374\t # ------------------------------------------------------------------\n 375\t # Async variants explicitly offload sync boto3 operations to avoid\n 376\t # blocking the event loop thread.\n 377\t # ------------------------------------------------------------------\n 378\t\n 379\t async def aget_entry(self, args, kwds) -> Tuple[str, Optional[CacheEntry]]:\n 380\t \"\"\"Async-compatible variant of :meth:`get_entry`.\n 381\t\n 382\t This method delegates to the sync implementation via\n 383\t ``asyncio.to_thread`` because boto3 is sync-only.\n 384\t\n 385\t \"\"\"\n 386\t return await asyncio.to_thread(self.get_entry, args, kwds)\n 387\t\n 388\t async def aget_entry_by_key(self, key: str) -> Tuple[str, Optional[CacheEntry]]:\n 389\t \"\"\"Async-compatible variant of :meth:`get_entry_by_key`.\n 390\t\n 391\t This method delegates to the sync implementation via\n 392\t ``asyncio.to_thread`` because boto3 is sync-only.\n 393\t\n 394\t \"\"\"\n 395\t return await asyncio.to_thread(self.get_entry_by_key, key)\n 396\t\n 397\t async def aset_entry(self, key: str, func_res: Any) -> bool:\n 398\t \"\"\"Async-compatible variant of :meth:`set_entry`.\n 399\t\n 400\t This method delegates to the sync implementation via\n 401\t ``asyncio.to_thread`` because boto3 is sync-only.\n 402\t\n 403\t \"\"\"\n 404\t return await asyncio.to_thread(self.set_entry, key, func_res)\n 405\t\n 406\t async def amark_entry_being_calculated(self, key: str) -> None:\n 407\t \"\"\"Async-compatible variant of :meth:`mark_entry_being_calculated`.\n 408\t\n 409\t This method delegates to the sync implementation via\n 410\t ``asyncio.to_thread`` because boto3 is sync-only.\n 411\t\n 412\t \"\"\"\n 413\t await asyncio.to_thread(self.mark_entry_being_calculated, key)\n 414\t\n 415\t async def amark_entry_not_calculated(self, key: str) -> None:\n 416\t \"\"\"Async-compatible variant of :meth:`mark_entry_not_calculated`.\n 417\t\n 418\t This method delegates to the sync implementation via\n 419\t ``asyncio.to_thread`` because boto3 is sync-only.\n 420\t\n 421\t \"\"\"\n 422\t await asyncio.to_thread(self.mark_entry_not_calculated, key)\n",{"_473":578,"_465":466,"_475":82},{"_511":579,"_513":580,"_515":581,"_517":518,"_519":582,"_521":31,"_41":574,"_522":583,"_470":112,"_91":524}," 360\t for page in pages:\n 361\t for obj in page.get(\"Contents\", []):\n 362\t s3_key = obj[\"Key\"]\n 363\t try:\n 364\t response = client.get_object(Bucket=self.s3_bucket, Key=s3_key)\n 365\t body = response[\"Body\"].read()\n 366\t entry = self._load_entry(body)\n 367\t if entry is not None and entry.time < threshold:\n 368\t client.delete_object(Bucket=self.s3_bucket, Key=s3_key)\n 369\t except Exception as exc:\n 370\t warnings.warn(f\"S3 delete_stale_entries entry check failed: {exc}\", stacklevel=2)\n 371\t except Exception as exc:\n 372\t warnings.warn(f\"S3 delete_stale_entries failed: {exc}\", stacklevel=2)\n 373\t\n 374\t # ------------------------------------------------------------------\n 375\t # Async variants explicitly offload sync boto3 operations to avoid\n 376\t # blocking the event loop thread.\n 377\t # ------------------------------------------------------------------\n 378\t\n 379\t async def aget_entry(self, args, kwds) -> Tuple[str, Optional[CacheEntry]]:\n 380\t \"\"\"Async-compatible variant of :meth:`get_entry`.\n 381\t\n 382\t This method delegates to the sync implementation via\n 383\t ``asyncio.to_thread`` because boto3 is sync-only.\n 384\t\n 385\t \"\"\"\n 386\t return await asyncio.to_thread(self.get_entry, args, kwds)\n 387\t\n 388\t async def aget_entry_by_key(self, key: str) -> Tuple[str, Optional[CacheEntry]]:\n 389\t \"\"\"Async-compatible variant of :meth:`get_entry_by_key`.\n 390\t\n 391\t This method delegates to the sync implementation via\n 392\t ``asyncio.to_thread`` because boto3 is sync-only.\n 393\t\n 394\t \"\"\"\n 395\t return await asyncio.to_thread(self.get_entry_by_key, key)\n 396\t\n 397\t async def aset_entry(self, key: str, func_res: Any) -> bool:\n 398\t \"\"\"Async-compatible variant of :meth:`set_entry`.\n 399\t\n 400\t This method delegates to the sync implementation via\n 401\t ``asyncio.to_thread`` because boto3 is sync-only.\n 402\t\n 403\t \"\"\"\n 404\t return await asyncio.to_thread(self.set_entry, key, func_res)\n 405\t\n 406\t async def amark_entry_being_calculated(self, key: str) -> None:\n 407\t \"\"\"Async-compatible variant of :meth:`mark_entry_being_calculated`.\n 408\t\n 409\t This method delegates to the sync implementation via\n 410\t ``asyncio.to_thread`` because boto3 is sync-only.\n 411\t\n 412\t \"\"\"\n 413\t await asyncio.to_thread(self.mark_entry_being_calculated, key)\n 414\t\n 415\t async def amark_entry_not_calculated(self, key: str) -> None:\n 416\t \"\"\"Async-compatible variant of :meth:`mark_entry_not_calculated`.\n 417\t\n 418\t This method delegates to the sync implementation via\n 419\t ``asyncio.to_thread`` because boto3 is sync-only.\n 420\t\n 421\t \"\"\"\n 422\t await asyncio.to_thread(self.mark_entry_not_calculated, key)\n","/bin/bash -lc 'nl -ba src/cachier/cores/s3.py | sed -n '\"'\"'360,470p'\"'\"''",[584],50,"68789",{"_513":585,"_166":586,"_156":587,"_91":528},"nl -ba src/cachier/cores/s3.py | sed -n '360,470p'","s3.py","src/cachier/cores/s3.py",{"_473":589,"_465":466,"_475":82},{"_511":-5,"_513":580,"_515":590,"_517":518,"_519":-5,"_521":-5,"_41":574,"_522":583,"_470":532,"_91":524},[591],{"_513":585,"_166":586,"_156":587,"_91":528},{"_473":593,"_465":466,"_475":82},{"_536":594,"_502":574,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"nl -ba src/cachier/cores/s3.py | sed -n '360,470p'\"}",{"_473":596,"_465":466,"_475":82},{"_502":597,"_504":598,"_91":506},"call_OgRU49vk3DSF4dcqXfeKim3q",{"_273":599,"_508":-5},"Chunk ID: b98ba9\nWall time: 0.0516 seconds\nProcess exited with code 0\nOriginal token count: 1267\nOutput:\n 1\t\"\"\"An S3-based caching core for cachier.\"\"\"\n 2\t\n 3\timport asyncio\n 4\timport pickle\n 5\timport time\n 6\timport warnings\n 7\tfrom datetime import datetime, timedelta\n 8\tfrom typing import Any, Callable, Optional, Tuple\n 9\t\n 10\ttry:\n 11\t import boto3 # type: ignore[import-untyped]\n 12\t import botocore.exceptions # type: ignore[import-untyped]\n 13\t\n 14\t BOTO3_AVAILABLE = True\n 15\texcept ImportError:\n 16\t BOTO3_AVAILABLE = False\n 17\t\n 18\tfrom .._types import HashFunc\n 19\tfrom ..config import CacheEntry\n 20\tfrom .base import RecalculationNeeded, _BaseCore, _get_func_str\n 21\t\n 22\tS3_SLEEP_DURATION_IN_SEC = 1\n 23\t\n 24\t\n 25\tclass MissingS3Bucket(ValueError):\n 26\t \"\"\"Thrown when the s3_bucket keyword argument is missing.\"\"\"\n 27\t\n 28\t\n 29\tclass _S3Core(_BaseCore):\n 30\t \"\"\"S3-based core for Cachier, supporting AWS S3 and S3-compatible backends.\n 31\t\n 32\t Async support in this core is delegated rather than native. Since boto3 is a\n 33\t synchronous client, async methods explicitly offload I/O work to a thread via\n 34\t ``asyncio.to_thread``.\n 35\t\n 36\t Parameters\n 37\t ----------\n 38\t hash_func : callable, optional\n 39\t A callable to hash function arguments into a cache key string.\n 40\t s3_bucket : str\n 41\t The name of the S3 bucket to use for caching.\n 42\t wait_for_calc_timeout : int, optional\n 43\t Maximum seconds to wait for a concurrent calculation. 0 means wait forever.\n 44\t s3_prefix : str, optional\n 45\t Key prefix for all cache entries. Defaults to ``\"cachier\"``.\n 46\t s3_client : boto3 S3 client, optional\n 47\t A pre-configured boto3 S3 client instance.\n 48\t s3_client_factory : callable, optional\n 49\t A callable that returns a boto3 S3 client. Allows lazy initialization.\n 50\t s3_region : str, optional\n 51\t AWS region name used when creating the S3 client.\n 52\t s3_endpoint_url : str, optional\n 53\t Custom endpoint URL for S3-compatible services (e.g. MinIO, localstack).\n 54\t s3_config : boto3 Config, optional\n 55\t Optional ``botocore.config.Config`` object passed when creating the client.\n 56\t entry_size_limit : int, optional\n 57\t Maximum allowed size in bytes of a cached value.\n 58\t\n 59\t \"\"\"\n 60\t\n 61\t def __init__(\n 62\t self,\n 63\t hash_func: Optional[HashFunc],\n 64\t s3_bucket: Optional[str],\n 65\t wait_for_calc_timeout: Optional[int] = None,\n 66\t s3_prefix: str = \"cachier\",\n 67\t s3_client: Optional[Any] = None,\n 68\t s3_client_factory: Optional[Callable[[], Any]] = None,\n 69\t s3_region: Optional[str] = None,\n 70\t s3_endpoint_url: Optional[str] = None,\n 71\t s3_config: Optional[Any] = None,\n 72\t entry_size_limit: Optional[int] = None,\n 73\t ):\n 74\t if not BOTO3_AVAILABLE:\n 75\t warnings.warn(\n 76\t \"`boto3` was not found. S3 cores will not function. Install with `pip install boto3`.\",\n 77\t ImportWarning,\n 78\t stacklevel=2,\n 79\t )\n 80\t\n 81\t super().__init__(\n 82\t hash_func=hash_func,\n 83\t wait_for_calc_timeout=wait_for_calc_timeout,\n 84\t entry_size_limit=entry_size_limit,\n 85\t )\n 86\t\n 87\t if not s3_bucket:\n 88\t raise MissingS3Bucket(\"must specify ``s3_bucket`` when using the s3 core\")\n 89\t\n 90\t self.s3_bucket = s3_bucket\n 91\t self.s3_prefix = s3_prefix\n 92\t self._s3_client = s3_client\n 93\t self._s3_client_factory = s3_client_factory\n 94\t self._s3_region = s3_region\n 95\t self._s3_endpoint_url = s3_endpoint_url\n 96\t self._s3_config = s3_config\n 97\t self._func_str: Optional[str] = None\n 98\t\n 99\t def set_func(self, func: Callable) -> None:\n 100\t \"\"\"Set the function this core will use.\"\"\"\n 101\t super().set_func(func)\n 102\t self._func_str = _get_func_str(func)\n 103\t\n 104\t def _get_s3_client(self) -> Any:\n 105\t \"\"\"Return a boto3 S3 client, creating one if not already available.\"\"\"\n 106\t if self._s3_client_factory is not None:\n 107\t return self._s3_client_factory()\n 108\t if self._s3_client is not None:\n 109\t return self._s3_client\n 110\t kwargs: dict = {}\n 111\t if self._s3_region:\n 112\t kwargs[\"region_name\"] = self._s3_region\n 113\t if self._s3_endpoint_url:\n 114\t kwargs[\"endpoint_url\"] = self._s3_endpoint_url\n 115\t if self._s3_config:\n 116\t kwargs[\"config\"] = self._s3_config\n 117\t self._s3_client = boto3.client(\"s3\", **kwargs)\n 118\t return self._s3_client\n 119\t\n 120\t def _get_s3_key(self, key: str) -> str:\n",{"_473":601,"_465":466,"_475":82},{"_511":602,"_513":603,"_515":604,"_517":518,"_519":520,"_521":31,"_41":597,"_522":605,"_470":112,"_91":524}," 1\t\"\"\"An S3-based caching core for cachier.\"\"\"\n 2\t\n 3\timport asyncio\n 4\timport pickle\n 5\timport time\n 6\timport warnings\n 7\tfrom datetime import datetime, timedelta\n 8\tfrom typing import Any, Callable, Optional, Tuple\n 9\t\n 10\ttry:\n 11\t import boto3 # type: ignore[import-untyped]\n 12\t import botocore.exceptions # type: ignore[import-untyped]\n 13\t\n 14\t BOTO3_AVAILABLE = True\n 15\texcept ImportError:\n 16\t BOTO3_AVAILABLE = False\n 17\t\n 18\tfrom .._types import HashFunc\n 19\tfrom ..config import CacheEntry\n 20\tfrom .base import RecalculationNeeded, _BaseCore, _get_func_str\n 21\t\n 22\tS3_SLEEP_DURATION_IN_SEC = 1\n 23\t\n 24\t\n 25\tclass MissingS3Bucket(ValueError):\n 26\t \"\"\"Thrown when the s3_bucket keyword argument is missing.\"\"\"\n 27\t\n 28\t\n 29\tclass _S3Core(_BaseCore):\n 30\t \"\"\"S3-based core for Cachier, supporting AWS S3 and S3-compatible backends.\n 31\t\n 32\t Async support in this core is delegated rather than native. Since boto3 is a\n 33\t synchronous client, async methods explicitly offload I/O work to a thread via\n 34\t ``asyncio.to_thread``.\n 35\t\n 36\t Parameters\n 37\t ----------\n 38\t hash_func : callable, optional\n 39\t A callable to hash function arguments into a cache key string.\n 40\t s3_bucket : str\n 41\t The name of the S3 bucket to use for caching.\n 42\t wait_for_calc_timeout : int, optional\n 43\t Maximum seconds to wait for a concurrent calculation. 0 means wait forever.\n 44\t s3_prefix : str, optional\n 45\t Key prefix for all cache entries. Defaults to ``\"cachier\"``.\n 46\t s3_client : boto3 S3 client, optional\n 47\t A pre-configured boto3 S3 client instance.\n 48\t s3_client_factory : callable, optional\n 49\t A callable that returns a boto3 S3 client. Allows lazy initialization.\n 50\t s3_region : str, optional\n 51\t AWS region name used when creating the S3 client.\n 52\t s3_endpoint_url : str, optional\n 53\t Custom endpoint URL for S3-compatible services (e.g. MinIO, localstack).\n 54\t s3_config : boto3 Config, optional\n 55\t Optional ``botocore.config.Config`` object passed when creating the client.\n 56\t entry_size_limit : int, optional\n 57\t Maximum allowed size in bytes of a cached value.\n 58\t\n 59\t \"\"\"\n 60\t\n 61\t def __init__(\n 62\t self,\n 63\t hash_func: Optional[HashFunc],\n 64\t s3_bucket: Optional[str],\n 65\t wait_for_calc_timeout: Optional[int] = None,\n 66\t s3_prefix: str = \"cachier\",\n 67\t s3_client: Optional[Any] = None,\n 68\t s3_client_factory: Optional[Callable[[], Any]] = None,\n 69\t s3_region: Optional[str] = None,\n 70\t s3_endpoint_url: Optional[str] = None,\n 71\t s3_config: Optional[Any] = None,\n 72\t entry_size_limit: Optional[int] = None,\n 73\t ):\n 74\t if not BOTO3_AVAILABLE:\n 75\t warnings.warn(\n 76\t \"`boto3` was not found. S3 cores will not function. Install with `pip install boto3`.\",\n 77\t ImportWarning,\n 78\t stacklevel=2,\n 79\t )\n 80\t\n 81\t super().__init__(\n 82\t hash_func=hash_func,\n 83\t wait_for_calc_timeout=wait_for_calc_timeout,\n 84\t entry_size_limit=entry_size_limit,\n 85\t )\n 86\t\n 87\t if not s3_bucket:\n 88\t raise MissingS3Bucket(\"must specify ``s3_bucket`` when using the s3 core\")\n 89\t\n 90\t self.s3_bucket = s3_bucket\n 91\t self.s3_prefix = s3_prefix\n 92\t self._s3_client = s3_client\n 93\t self._s3_client_factory = s3_client_factory\n 94\t self._s3_region = s3_region\n 95\t self._s3_endpoint_url = s3_endpoint_url\n 96\t self._s3_config = s3_config\n 97\t self._func_str: Optional[str] = None\n 98\t\n 99\t def set_func(self, func: Callable) -> None:\n 100\t \"\"\"Set the function this core will use.\"\"\"\n 101\t super().set_func(func)\n 102\t self._func_str = _get_func_str(func)\n 103\t\n 104\t def _get_s3_client(self) -> Any:\n 105\t \"\"\"Return a boto3 S3 client, creating one if not already available.\"\"\"\n 106\t if self._s3_client_factory is not None:\n 107\t return self._s3_client_factory()\n 108\t if self._s3_client is not None:\n 109\t return self._s3_client\n 110\t kwargs: dict = {}\n 111\t if self._s3_region:\n 112\t kwargs[\"region_name\"] = self._s3_region\n 113\t if self._s3_endpoint_url:\n 114\t kwargs[\"endpoint_url\"] = self._s3_endpoint_url\n 115\t if self._s3_config:\n 116\t kwargs[\"config\"] = self._s3_config\n 117\t self._s3_client = boto3.client(\"s3\", **kwargs)\n 118\t return self._s3_client\n 119\t\n 120\t def _get_s3_key(self, key: str) -> str:\n","/bin/bash -lc 'nl -ba src/cachier/cores/s3.py | sed -n '\"'\"'1,120p'\"'\"''",[606],"48759",{"_513":607,"_166":586,"_156":587,"_91":528},"nl -ba src/cachier/cores/s3.py | sed -n '1,120p'",{"_473":609,"_465":466,"_475":82},{"_511":-5,"_513":603,"_515":610,"_517":518,"_519":-5,"_521":-5,"_41":597,"_522":605,"_470":532,"_91":524},[611],{"_513":607,"_166":586,"_156":587,"_91":528},{"_473":613,"_465":466,"_475":82},{"_536":614,"_502":597,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"nl -ba src/cachier/cores/s3.py | sed -n '1,120p'\"}",{"_473":616,"_465":466,"_475":82},{"_476":-5,"_494":617,"_41":618,"_497":619,"_91":499},"gAAAAABpla6YmW34rmtUxcATfwrRe1xbrORCF-FHaffTIhvpTGQt_vXlx7VkmH9gWL4jZUUMcPBlKBtj18lFeX1hLDpOrORfgi97c_X0HfGXsvXy0NQISIF2mdYJrQT9j-BMFj9dZQRd8lD0ZbRPSiL4IyFgGEFKI7ryNCX9EWsJVr2DJ0TvU0WaQyqOQffpkKv5bEkOZ6CuLepaftyb-IAeOGrRw7_J8OiOyGvoBaP_hRwjQoo_ybzJiPG7txWUKNS4qg644_A4DNDONsRd2hnVlQg1mNjAVcVfBO4HPb4-gzgn597pUTusd2FUqkMT9tsNbe6Wko1pmDUiUKz6RY1_3sOl__QGGglD-8SbybdWDek5ecKgMEiCGk6cZUD6UYRy1W9KN77J-c4rDD3gRKuSSqm2twfa6j_ZFEV9rKtjNirOORjx4aqz6cqv1sc4D46qfATY9Wghbr2JcCGVNns_NtfiWfAJ0xN5CvoLHiCdVwxLfQ02dGIFBAuoggK6JSF3ZVbrQFOcp5ms6kTAEcHUg9LXGpdHvvK8qK4zlVkdBlzdPNh0olZAT21Kw3IzzpidNYCL5BA8uXCcx37dxfQRbzL4-h3Z0ZgqqyQ9O3Qa0OE1sy9qKXPYe2BlsIeFftgCrv1TffNd2VQmwsurLf_nsIEIsNRGMo0RzSXrYPshmhFqdsH7eMqjdDvM3fkJqZl9zK1z94krX3wOsoUJsAsa_nE1TCETjCIV7kpEb_s6bkjd-vTcrvxjiExI_uVrYQlGoiFsZStvtEYUtsKldjnC5hNnPVfWXJnYTMi1hBl79kUe7A7Hq5VxsUzT2-hpNEb5hTfUjT2XwOnFuaEy0FR1TOl9wTu3KMJwgdecJZO0q0_G0xMzLLgabFVyryXIXHMub1eZ11e7IEYMTi_ahAB0CEuE21wrwqDS1FbsEdtesQ_jXlGUrNbVuEjrjFdUirtu58W5UsF9b025nsLpHsKzeETkP0DkCw==","legacy_responseItem_reasoning_24",[],{"_473":621,"_465":466,"_475":82},{"_502":622,"_504":623,"_91":506},"call_eTX8LnZGsIR5tlSMJpysbyNX",{"_273":624,"_508":-5},"{\"title\":\"Follow-up for #338: offload S3 async paths and complete README support matrix\",\"body\":\"## Summary\\nThis follow-up PR builds on #338 to close the remaining merge blockers:\\n\\n1. Make S3 async behavior event-loop safe by explicitly offloading sync boto3 operations.\\n2. Fully document S3 as a supported core in README, including sync/async compatibility.\\n\\n## Changes\\n- `src/cachier/cores/s3.py`\\n - Added explicit async overrides that delegate to `asyncio.to_thread` for:\\n - `aget_entry`\\n - `aget_entry_by_key`\\n - `aset_entry`\\n - `amark_entry_being_calculated`\\n - `amark_entry_not_calculated`\\n - Updated class and method docs/comments to clarify S3 async support is delegated (thread-offloaded sync boto3), not native async.\\n\\n- `tests/s3_tests/test_s3_core.py`\\n - Added `@pytest.mark.asyncio` regression test for async decorated function cache-hit behavior with S3 backend.\\n\\n- `README.rst`\\n - Moved S3 from future features into current supported cores.\\n - Added S3 to additional core dependency install guidance.\\n - Updated Core Sync/Async Compatibility table with S3:\\n - Sync: Yes\\n - Async: Yes (delegated)\\n - Constraint: delegated/thread-offloaded sync boto3 implementation; no async client required.\\n - Added a short S3 sync/async support note.\\n\\n## Validation\\n- `pytest tests/s3_tests/test_s3_core.py` (environment skipped S3 tests due to missing boto3/moto)\\n- `ruff check src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py`\"}",{"_473":626,"_465":466,"_475":82},{"_536":624,"_502":622,"_41":-5,"_166":627,"_91":539},"mcp__make_pr__make_pr",{"_473":629,"_465":466,"_475":82},{"_476":-5,"_494":630,"_41":631,"_497":632,"_91":499},"gAAAAABpla6P9Jr5Opurof7Kp1xGvkgJHCRR96On4ltNboJGbEUbMC0cZTfnaRVXzImx-cnOynkXn9NJWssZb_9aXTgdxZnOhMf67CQ3fUuM71-hytpm3dsy-3FmRv5ZL3jsR3Waxj16taYGm7TAIR4R4R56OELJ5mWTLbgSj_fU-eDNpKBlOt2EV0ZPZVLOuxMQCu8A4xskItEyEUqW4qmrfqbdfVWjIlBx58DeQXJvfMJ_-F36SplGq9LEg6tq7TN347CA6lLC0jWAt6hr-RFS8zAWV05IXAajGtIr6RrHFDPhim-cN0CDc0YUcUs2wzo3Mg4-WMrMRMrmWG3GGQybI03-j12KvLHHUVeEyg9ABdpuURHVEacJDAkzBZ-Ati3AVs4a9GTAQ6WC_L3OfPBzmsYUu5ajF-F_BNLOnavUW28EUyfRS9Am81EqoDYx5jla-vXU-9QVT3C4hom3ivK_aHuPOP_ZgogdegkKUoKx2C0R4Sju-3eAOBgk707HK8N9xcrdiRuoDUj2Uq-x3qmmKsL1XIkdQdCIantCEoRpcLXj7Fa45XLpXE9lnD3um1mr1WiY5elyQDheOo1Mn0MGrepEpySWuv-PFRy80rg95Ih099yxaTbnOYcUoqFpXYiiqTAhb_s3U3EerQgUXCZ4viKFiaUMWVn4kkBKX6w_zn-1HF7Ilb1OdnWjzcGslELZAfDoDagqE60ZrNfer-zPXl2_GoJvsp5-9IJpkUEtTKssxMfj1VuLmWz3YxEAt3OeBGh9Fl5qnY6i40cuuaHlGlqjFqA0M7SF0o52avqYAl1UZDDk8BDY-OREpYE6YW9SZoBWC7_FnJvNVUxm9OIrefB3_1Mty3fisD8FgCwDOBd6F5LGQ3r_gGskyFUpVhIeruzxFa4kbJHOL6OqInqDm6-CaXfG0ZLD3qWggpfz5I7F7AWNRHlhA_1w7cGytlMAW6QWbgxBiTm8QupYCsItxf5aVBPmisSabLCHTSKJbxmo_v2YBz7oOKGfcRDUihq5F3Cuv0dK","legacy_responseItem_reasoning_23",[],{"_473":634,"_465":466,"_475":82},{"_502":635,"_504":636,"_91":506},"call_Z2djyUU3o0AkM4BX8jy3Nq0S",{"_273":637,"_508":-5},"Chunk ID: f2fc84\nWall time: 0.0517 seconds\nProcess exited with code 0\nOriginal token count: 29\nOutput:\n[work c7a8724] Fix delegated async behavior and docs for S3 core\n 3 files changed, 88 insertions(+), 4 deletions(-)\n",{"_473":639,"_465":466,"_475":82},{"_511":640,"_513":641,"_515":642,"_517":518,"_519":520,"_521":31,"_41":635,"_522":643,"_470":112,"_91":524},"[work c7a8724] Fix delegated async behavior and docs for S3 core\n 3 files changed, 88 insertions(+), 4 deletions(-)\n","/bin/bash -lc 'git add README.rst src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py && git commit -m \"Fix delegated async behavior and docs for S3 core\"'",[644,645],"18181",{"_513":648,"_91":647},{"_513":646,"_91":647},"git commit -m 'Fix delegated async behavior and docs for S3 core'","unknown","git add README.rst src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py",{"_473":650,"_465":466,"_475":82},{"_511":-5,"_513":641,"_515":651,"_517":518,"_519":-5,"_521":-5,"_41":635,"_522":643,"_470":532,"_91":524},[652,653],{"_513":648,"_91":647},{"_513":646,"_91":647},{"_473":655,"_465":466,"_475":82},{"_536":656,"_502":635,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"git add README.rst src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py && git commit -m \\\"Fix delegated async behavior and docs for S3 core\\\"\"}",{"_473":658,"_465":466,"_475":82},{"_476":-5,"_494":659,"_41":660,"_497":661,"_91":499},"gAAAAABpla6Mq55YyGW429gjUakK9noaEp56KnCKKmnnCylwG6g66pmpK7VT4bvf42lMgeKMRz9-akOOxqman7ugT_MoZuZh7T2cdK6-krV_Ev97LROsrP-lIviSWvZUxmjHOeoO5v9oZtpFXUPO8qvaLdNrg_lSkXJUatmrBQRjiOudab6XB970aN-JGR8tIQN1J4460c79tT9GhZJUJL6xPixhGqgjf00_4cMzKNE1Lgps7B95t8Xu6Wj8N_OC9xaB_Wkx5gu2-0nFGPIGDFdGccenwvz5quVbs-5ULVaR0p4HArVLHntGTxovney4HQ3enMS_ncQfMGCddMU53ssueisI1R8g_VYfxBwTxf0RNSeQ5cMCdAf6pX2OW18dFrooH1dBmFZjVRy40yly4XQ0w4-ZgcO-kjGi21IfY6WJOlH6Wk0S-bfExGZ6VSNh_JFAJv12hwtzrChl7LqZGYe3FMhp5fnUx0EbYhi4HBSSJYwCEmmLDAYoyQz1bzAD4iEj6PbDpYlIbR_8Zr09a3yoF-oPuGmD7ItO1PK7CJsRr4LD6HnKC6XB50TMoSGqsf6L6GCB87JVKt8qzj29RFOFnTMqgsfqQlrRuZPnNcSEBx93OGZtXvZ_p9aMRSH54UlQSYsskVVe49Rae8XBD3MjYCbUAgUzFRTy17DVVnCHZqZXY-93mtssVcUd0djvnXvINSZ3G-lqMhnrCFYPLYsi-qA7zteRd_IdV7UOLuH4NLp-EAqyq4mPsI_D4JJhfYVLgZyYTArUX8Hyv1R4hl5l_-BC723VBT-2xeTn8uQ1jdORT0t7aUk-H644rSporTrXFhqVRVzd01t8ptjBLNcVvS_PXp68Ig==","legacy_responseItem_reasoning_22",[],{"_473":663,"_465":466,"_475":82},{"_502":664,"_504":665,"_91":506},"call_E94kzAI0GCIlWaziQQhmSMNe",{"_273":666,"_508":-5},"Chunk ID: c89557\nWall time: 0.0518 seconds\nProcess exited with code 0\nOriginal token count: 19\nOutput:\n M README.rst\n M src/cachier/cores/s3.py\n M tests/s3_tests/test_s3_core.py\n",{"_473":668,"_465":466,"_475":82},{"_511":669,"_513":670,"_515":671,"_517":518,"_519":520,"_521":31,"_41":664,"_522":672,"_470":112,"_91":524}," M README.rst\n M src/cachier/cores/s3.py\n M tests/s3_tests/test_s3_core.py\n","/bin/bash -lc 'git status --short'",[673],"70525",{"_513":674,"_91":647},"git status --short",{"_473":676,"_465":466,"_475":82},{"_511":-5,"_513":670,"_515":677,"_517":518,"_519":-5,"_521":-5,"_41":664,"_522":672,"_470":532,"_91":524},[678],{"_513":674,"_91":647},{"_473":680,"_465":466,"_475":82},{"_536":681,"_502":664,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"git status --short\"}",{"_473":683,"_465":466,"_475":82},{"_476":-5,"_494":684,"_41":685,"_497":686,"_91":499},"gAAAAABpla6LhupHlcx82GKeLmEZn52dFUoQnfcmK-YQGhAAlTz7BNsJNpO_uZXHRqznIpk-u6YBb6FCA90qcbnm3TCl_NDg-_ErrF95zWvlCfeKhpdvn4LmX4JdzoTgqULGXyOxKLsg_CQKuOWavjWZ3hqehI2GibgnZsGNpWQ1ylG5wvd6arXQR-4JzzOZ5NzVajEeexjU-BqyvBxgNT-nDXWOJFUyzu0GcntarWt8IdBuaEw4yReETtpPmvaMOlIBb4Do4oDF8o0rxu1hIkCRGIXpmD0su2W-KQDO3OwaK-rsTHWZtFy9_WtU1uw1CGtSaLUAoEkYolljAa6ehyvYyu7oYOljV9YYUzqgu4Hhrzq4MY1xLUI-DS7ZuR6A0a-pFDY-_dWeJoCwXQMlTMqW1cZu0X0rpIkjJ5sfnw0DDy_sFEfJ0EVTsXQc7OW8g19Ox4G0If5S8mcQ-3fBhorOOqJGFt14TujKUkLzLojDOAjxNWjvAuifywJDbpqQDlmWbaS3y75wwYp6qJOOR94-Z0dlqDNnHd0DVZLD_zRqlnkkFlWlGzyX_ppOGPjT-1Ls_JUw1d_icIeSMzlvTL32mQ9rO_6gc18wK3qlFzxoKFy8qa7r6kQRBttifL9RrbTHXobG5tNeLLAhEhPgoWSda2PhN7N5-h90X-iXgIHQWbB4VNlveNvTZI3vi-hUTcg_BHduP3AX6k_pWdmTcW9UpNGhubdAhvqldrngfINOJ-hXpodkBEph8Tqug_ccLgUKovi04TdDPmMKYiKm3M2Yq2SuEyn4AdVa-4tX_VyXnJmRVZkNEfwbBKtf6we5bWIvSi5Vd302rpv_7z4tV6rHnsKApbPanm2TeWIMTbXHyUHfJBav-0nFDSIc2Yk73rS5uYvLCrdaIz6JporIm03n_uzrm0KR3nFgHcaYShKcqaECREbf5d9miXzkGq9aL9LVY92Ncn0SL4n6_6Vxm6GI29FgcLSMgGrhSO2bP20QOhbNOQZ2MM2J653CrIUd3FvSvLgUvm8knmJ2RZ2dROmX4A9tReDqIEHUfEq_YFSa70OXK0xHHYI=","legacy_responseItem_reasoning_21",[],{"_473":688,"_465":466,"_475":82},{"_502":689,"_504":690,"_91":506},"call_xugaEdFmOHOH8J8NdOsLic5v",{"_273":691,"_508":-5},"Chunk ID: b42e77\nWall time: 0.0513 seconds\nProcess exited with code 0\nOriginal token count: 1618\nOutput:\ndiff --git a/README.rst b/README.rst\nindex 55e3828..924ba55 100644\n--- a/README.rst\n+++ b/README.rst\n@@ -59,6 +59,7 @@ Current features\n * Cross-machine caching using MongoDB.\n * SQL-based caching using SQLAlchemy-supported databases.\n * Redis-based caching for high-performance scenarios.\n+ * S3-based caching for cross-machine object storage backends.\n \n * Thread-safety.\n * **Per-call max age:** Specify a maximum age for cached values per call.\n@@ -71,7 +72,6 @@ Cachier is **NOT**:\n Future features\n ---------------\n \n-* S3 core.\n * Multi-core caching.\n * `Cache replacement policies `_\n \n@@ -580,6 +580,12 @@ Cachier supports Redis-based caching for high-performance scenarios. Redis provi\n - ``processing``: Boolean, is value being calculated\n - ``completed``: Boolean, is value calculation completed\n \n+**S3 Sync/Async Support:**\n+\n+- Sync functions use direct boto3 calls.\n+- Async functions are supported via thread-offloaded sync boto3 calls\n+ (delegated mode), not a native async client.\n+\n **Limitations & Notes:**\n \n - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n@@ -631,6 +637,11 @@ async drivers and require the client or engine type to match the decorated funct\n - ``redis_client`` must be a sync client or sync callable for sync functions and\n an async callable returning a ``redis.asyncio.Redis`` client for async\n functions. Passing a sync callable to an async function raises ``TypeError``.\n+ * - **S3**\n+ - Yes\n+ - Yes (delegated)\n+ - Async support is delegated via thread-offloaded sync boto3 calls\n+ (``asyncio.to_thread``). No async S3 client is required.\n \n \n Contributing\n@@ -655,13 +666,14 @@ Install in development mode with test dependencies for local cores (memory and p\n cd cachier\n pip install -e . -r tests/requirements.txt\n \n-Each additional core (MongoDB, Redis, SQL) requires additional dependencies. To install all dependencies for all cores, run:\n+Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n \n .. code-block:: bash\n \n pip install -r tests/requirements_mongodb.txt\n pip install -r tests/requirements_redis.txt\n pip install -r tests/requirements_postgres.txt\n+ pip install -r tests/requirements_s3.txt\n \n Running the tests\n -----------------\ndiff --git a/src/cachier/cores/s3.py b/src/cachier/cores/s3.py\nindex eb39e67..556d3ef 100644\n--- a/src/cachier/cores/s3.py\n+++ b/src/cachier/cores/s3.py\n@@ -1,5 +1,6 @@\n \"\"\"An S3-based caching core for cachier.\"\"\"\n \n+import asyncio\n import pickle\n import time\n import warnings\n@@ -28,6 +29,10 @@ class MissingS3Bucket(ValueError):\n class _S3Core(_BaseCore):\n \"\"\"S3-based core for Cachier, supporting AWS S3 and S3-compatible backends.\n \n+ Async support in this core is delegated rather than native. Since boto3 is a\n+ synchronous client, async methods explicitly offload I/O work to a thread via\n+ ``asyncio.to_thread``.\n+\n Parameters\n ----------\n hash_func : callable, optional\n@@ -367,6 +372,51 @@ class _S3Core(_BaseCore):\n warnings.warn(f\"S3 delete_stale_entries failed: {exc}\", stacklevel=2)\n \n # ------------------------------------------------------------------\n- # Async variants delegate to the thread-based defaults in _BaseCore\n- # since boto3 is a sync library.\n+ # Async variants explicitly offload sync boto3 operations to avoid\n+ # blocking the event loop thread.\n # ------------------------------------------------------------------\n+\n+ async def aget_entry(self, args, kwds) -> Tuple[str, Optional[CacheEntry]]:\n+ \"\"\"Async-compatible variant of :meth:`get_entry`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.get_entry, args, kwds)\n+\n+ async def aget_entry_by_key(self, key: str) -> Tuple[str, Optional[CacheEntry]]:\n+ \"\"\"Async-compatible variant of :meth:`get_entry_by_key`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.get_entry_by_key, key)\n+\n+ async def aset_entry(self, key: str, func_res: Any) -> bool:\n+ \"\"\"Async-compatible variant of :meth:`set_entry`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.set_entry, key, func_res)\n+\n+ async def amark_entry_being_calculated(self, key: str) -> None:\n+ \"\"\"Async-compatible variant of :meth:`mark_entry_being_calculated`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ await asyncio.to_thread(self.mark_entry_being_calculated, key)\n+\n+ async def amark_entry_not_calculated(self, key: str) -> None:\n+ \"\"\"Async-compatible variant of :meth:`mark_entry_not_calculated`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ await asyncio.to_thread(self.mark_entry_not_calculated, key)\ndiff --git a/tests/s3_tests/test_s3_core.py b/tests/s3_tests/test_s3_core.py\nindex b38a466..a5e1c28 100644\n--- a/tests/s3_tests/test_s3_core.py\n+++ b/tests/s3_tests/test_s3_core.py\n@@ -1,5 +1,6 @@\n \"\"\"Tests for the S3 caching core.\"\"\"\n \n+import asyncio\n import contextlib\n import threading\n import warnings\n@@ -187,6 +188,27 @@ def test_s3_core_allow_none(s3_bucket):\n assert call_count[0] == 1\n \n \n+@pytest.mark.s3\n+@pytest.mark.asyncio\n+async def test_s3_core_async_cache_hit(s3_bucket):\n+ \"\"\"Async S3 cache calls should hit cache on repeated arguments.\"\"\"\n+ call_count = [0]\n+\n+ @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n+ async def _cached(x):\n+ call_count[0] += 1\n+ await asyncio.sleep(0)\n+ return x * 5\n+\n+ await _cached.clear_cache()\n+ value_1 = await _cached(6)\n+ value_2 = await _cached(6)\n+\n+ assert value_1 == 30\n+ assert value_2 == 30\n+ assert call_count[0] == 1\n+\n+\n @pytest.mark.s3\n def test_s3_core_none_not_cached_without_allow_none(s3_bucket):\n \"\"\"None results are NOT cached when allow_none=False (default).\"\"\"\n",{"_473":693,"_465":466,"_475":82},{"_511":694,"_513":695,"_515":696,"_517":518,"_519":520,"_521":31,"_41":689,"_522":697,"_470":112,"_91":524},"diff --git a/README.rst b/README.rst\nindex 55e3828..924ba55 100644\n--- a/README.rst\n+++ b/README.rst\n@@ -59,6 +59,7 @@ Current features\n * Cross-machine caching using MongoDB.\n * SQL-based caching using SQLAlchemy-supported databases.\n * Redis-based caching for high-performance scenarios.\n+ * S3-based caching for cross-machine object storage backends.\n \n * Thread-safety.\n * **Per-call max age:** Specify a maximum age for cached values per call.\n@@ -71,7 +72,6 @@ Cachier is **NOT**:\n Future features\n ---------------\n \n-* S3 core.\n * Multi-core caching.\n * `Cache replacement policies `_\n \n@@ -580,6 +580,12 @@ Cachier supports Redis-based caching for high-performance scenarios. Redis provi\n - ``processing``: Boolean, is value being calculated\n - ``completed``: Boolean, is value calculation completed\n \n+**S3 Sync/Async Support:**\n+\n+- Sync functions use direct boto3 calls.\n+- Async functions are supported via thread-offloaded sync boto3 calls\n+ (delegated mode), not a native async client.\n+\n **Limitations & Notes:**\n \n - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n@@ -631,6 +637,11 @@ async drivers and require the client or engine type to match the decorated funct\n - ``redis_client`` must be a sync client or sync callable for sync functions and\n an async callable returning a ``redis.asyncio.Redis`` client for async\n functions. Passing a sync callable to an async function raises ``TypeError``.\n+ * - **S3**\n+ - Yes\n+ - Yes (delegated)\n+ - Async support is delegated via thread-offloaded sync boto3 calls\n+ (``asyncio.to_thread``). No async S3 client is required.\n \n \n Contributing\n@@ -655,13 +666,14 @@ Install in development mode with test dependencies for local cores (memory and p\n cd cachier\n pip install -e . -r tests/requirements.txt\n \n-Each additional core (MongoDB, Redis, SQL) requires additional dependencies. To install all dependencies for all cores, run:\n+Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n \n .. code-block:: bash\n \n pip install -r tests/requirements_mongodb.txt\n pip install -r tests/requirements_redis.txt\n pip install -r tests/requirements_postgres.txt\n+ pip install -r tests/requirements_s3.txt\n \n Running the tests\n -----------------\ndiff --git a/src/cachier/cores/s3.py b/src/cachier/cores/s3.py\nindex eb39e67..556d3ef 100644\n--- a/src/cachier/cores/s3.py\n+++ b/src/cachier/cores/s3.py\n@@ -1,5 +1,6 @@\n \"\"\"An S3-based caching core for cachier.\"\"\"\n \n+import asyncio\n import pickle\n import time\n import warnings\n@@ -28,6 +29,10 @@ class MissingS3Bucket(ValueError):\n class _S3Core(_BaseCore):\n \"\"\"S3-based core for Cachier, supporting AWS S3 and S3-compatible backends.\n \n+ Async support in this core is delegated rather than native. Since boto3 is a\n+ synchronous client, async methods explicitly offload I/O work to a thread via\n+ ``asyncio.to_thread``.\n+\n Parameters\n ----------\n hash_func : callable, optional\n@@ -367,6 +372,51 @@ class _S3Core(_BaseCore):\n warnings.warn(f\"S3 delete_stale_entries failed: {exc}\", stacklevel=2)\n \n # ------------------------------------------------------------------\n- # Async variants delegate to the thread-based defaults in _BaseCore\n- # since boto3 is a sync library.\n+ # Async variants explicitly offload sync boto3 operations to avoid\n+ # blocking the event loop thread.\n # ------------------------------------------------------------------\n+\n+ async def aget_entry(self, args, kwds) -> Tuple[str, Optional[CacheEntry]]:\n+ \"\"\"Async-compatible variant of :meth:`get_entry`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.get_entry, args, kwds)\n+\n+ async def aget_entry_by_key(self, key: str) -> Tuple[str, Optional[CacheEntry]]:\n+ \"\"\"Async-compatible variant of :meth:`get_entry_by_key`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.get_entry_by_key, key)\n+\n+ async def aset_entry(self, key: str, func_res: Any) -> bool:\n+ \"\"\"Async-compatible variant of :meth:`set_entry`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ return await asyncio.to_thread(self.set_entry, key, func_res)\n+\n+ async def amark_entry_being_calculated(self, key: str) -> None:\n+ \"\"\"Async-compatible variant of :meth:`mark_entry_being_calculated`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ await asyncio.to_thread(self.mark_entry_being_calculated, key)\n+\n+ async def amark_entry_not_calculated(self, key: str) -> None:\n+ \"\"\"Async-compatible variant of :meth:`mark_entry_not_calculated`.\n+\n+ This method delegates to the sync implementation via\n+ ``asyncio.to_thread`` because boto3 is sync-only.\n+\n+ \"\"\"\n+ await asyncio.to_thread(self.mark_entry_not_calculated, key)\ndiff --git a/tests/s3_tests/test_s3_core.py b/tests/s3_tests/test_s3_core.py\nindex b38a466..a5e1c28 100644\n--- a/tests/s3_tests/test_s3_core.py\n+++ b/tests/s3_tests/test_s3_core.py\n@@ -1,5 +1,6 @@\n \"\"\"Tests for the S3 caching core.\"\"\"\n \n+import asyncio\n import contextlib\n import threading\n import warnings\n@@ -187,6 +188,27 @@ def test_s3_core_allow_none(s3_bucket):\n assert call_count[0] == 1\n \n \n+@pytest.mark.s3\n+@pytest.mark.asyncio\n+async def test_s3_core_async_cache_hit(s3_bucket):\n+ \"\"\"Async S3 cache calls should hit cache on repeated arguments.\"\"\"\n+ call_count = [0]\n+\n+ @cachier(backend=\"s3\", s3_bucket=s3_bucket, s3_region=TEST_REGION)\n+ async def _cached(x):\n+ call_count[0] += 1\n+ await asyncio.sleep(0)\n+ return x * 5\n+\n+ await _cached.clear_cache()\n+ value_1 = await _cached(6)\n+ value_2 = await _cached(6)\n+\n+ assert value_1 == 30\n+ assert value_2 == 30\n+ assert call_count[0] == 1\n+\n+\n @pytest.mark.s3\n def test_s3_core_none_not_cached_without_allow_none(s3_bucket):\n \"\"\"None results are NOT cached when allow_none=False (default).\"\"\"\n","/bin/bash -lc 'git diff -- src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py README.rst | sed -n '\"'\"'1,260p'\"'\"''",[698],"56825",{"_513":699,"_91":647},"git diff -- src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py README.rst",{"_473":701,"_465":466,"_475":82},{"_511":-5,"_513":695,"_515":702,"_517":518,"_519":-5,"_521":-5,"_41":689,"_522":697,"_470":532,"_91":524},[703],{"_513":699,"_91":647},{"_473":705,"_465":466,"_475":82},{"_536":706,"_502":689,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"git diff -- src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py README.rst | sed -n '1,260p'\"}",{"_473":708,"_465":466,"_475":82},{"_476":-5,"_494":709,"_41":710,"_497":711,"_91":499},"gAAAAABpla6JSK1YvvoJIlj-aloB0hjkq7Is_wZLUbZn-1sLVpQoQXfXWFa1KrrNZ6BEtxZuFcMqrPmnfaKpp6RVtnMHG1gtJD6Ngs1W4TUkJ9jgcoSVcbK62sqa3IQ-GvSR2qssGmioPGYm9WIezY71JOwGsVm3xnOUbp680Z13RUUtLMciFqjrzEYilXLayST4CGDs45fSj16ozl_-p-aE87bvxToutGJwSSrzOlKmYGDaCqRbo-uEIC6Sox4nPbMEHxbSF1gpbvYZysYAeAhG5RuUcVL2NEVT_b2QTh2tsoLOzT2xzIOjDB629tL7lz9qI6J4zHiEuIvozdbsw9_YivAL01z8SbSG-ODeQChjPzMn1mEqdKoImYSfs8xe6tJ-2sCkkmX0N9bEGf9EjbmverqWUAOP3-UyNwFKaZhAkcPf6IS0i-8vdyDsfCm5KhPMk721TyLYrqYYQv9vWMs50Iuv2Cou9eTnwIv6EcZ-MyTk_pptWb1hf3pyuvcZJOwlWfLGjLVV_0MFOGAHCHTY0omJDzJ1I6yOwE1RT9NnJwtzCf_DJIV0xuc0vO6i9XGDYF5XZA0q82OxJ2HFvrQi6LGLTMK8-hwZZFU1iUpchhFi_sbmHTGaXDGfttQKBMp2C8SrWUZsqhcK0y7emO1NLdPOMmA8jXWdQaRwP7zjoyNYNAJc2BB_IeDgs_6pokErHxCJO8pkzOOmabnsXqapN-87fOm6hgD-UoG7m130_RshZF_MeZy797EEOzU93N4_0oumvEQvIJARC4Yq-k_rnmeQjct-pjgfkNx7uvl7y6EAKg3YEtnUEG61v_YKcrk83EuTh0OA7EjbZbKnFIWm8ksKv0MFHInkqrLJ8o3XltbgMgqW8t1L81Fc8GeuqcBWHMP5xsCKDLjTlHU5qI08praAYDYQqbr2MgcfZQKNEaErWxJDtay0JqscfhMztACzAREJ1rctkDZr9x8H4V3iduclKWfIYg==","legacy_responseItem_reasoning_20",[],{"_473":713,"_465":466,"_475":82},{"_502":714,"_504":715,"_91":506},"call_1AN1SZqUwVY7nWpiANOp5qEv",{"_273":716,"_508":-5},"Chunk ID: 5682e2\nWall time: 0.6684 seconds\nProcess exited with code 0\nOriginal token count: 82\nOutput:\nwarning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\nAll checks passed!\n",{"_473":718,"_465":466,"_475":82},{"_511":719,"_513":720,"_515":721,"_517":518,"_519":722,"_521":31,"_41":714,"_522":723,"_470":112,"_91":524},"warning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\nAll checks passed!\n","/bin/bash -lc 'ruff check src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py'",[724],668,"37137",{"_513":725,"_91":647},"ruff check src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py",{"_473":727,"_465":466,"_475":82},{"_511":-5,"_513":720,"_515":728,"_517":518,"_519":-5,"_521":-5,"_41":714,"_522":723,"_470":532,"_91":524},[729],{"_513":725,"_91":647},{"_473":731,"_465":466,"_475":82},{"_536":732,"_502":714,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"ruff check src/cachier/cores/s3.py tests/s3_tests/test_s3_core.py\"}",{"_473":734,"_465":466,"_475":82},{"_476":-5,"_494":735,"_41":736,"_497":737,"_91":499},"gAAAAABpla6FwONnSHfPEpUeTtG_3blBAZkuLP42Z8BiE1UmqswteLstv59FVY_oyl7jpUor18eZlWtDWRMgH9q5EupPSuWA1eeZ4-k5hvCXmERbdmZSLpX780wJw9FaKUND6Srg6N_r4mbM2CrMxa0q5oelu8nJFaL4X0yyS2nFmW9j2iV8irkmfnpRHJ9vfdBa-A0NhQ98VmLFtGPKW5ZQc0_Vcnn7b0ReXNmwofcjMT_LheZ_yOAgwXEOQaV3exYEw_3v17meFHcEf5BtXqeDJ2nAdhtTr5SMCMoWHMx3f6ilnBfot8_xYZYEJro92JSq4aZbfMSPeSpiQiI6Ds0oIyPbyZCkCgeoGOus5E0FCj50M3LoNN8ldqUrMfB2b1vO_Ybz_F4C9DKlFhnCwR4_1xvrCURjrD_T-0L0kf0jQBt8C1P57BvqRRfGv4n91GxDinJnVlezOAK1QhMZ93E2C7jTNv_FHx_zgEgk-3k3WhcJgd7pqNqosE0y21YKNHTaPQH32NAYJlJk6NVcPp-G4inSZU-mSYtMF-hnNQ1y5K9ecm1tU2hRO8jpv2Cta8OyhQiyr3fQFUMeoHIqjUnfsIWsb-nt0CnC4Sdp5KBAzYYgCaHAwgiWrEayXhKJJmLBj91EPXG1bxDOxHVAHn38BuE9rgou11OeZ5IPnZSeewwPJIX5OgNZbqcNxo870tv0BZ6LuMytG8KK3CaFBcMqVbwbWTIaolBPwsLm3dXQdThb7kOKVEcj9X9fym--9ni4twOJp79Lqlexq3Fmgrew5vNquL4DRkaGk4-wMur_S24VSrXLR9OeVyuUOCVek-gGw1H4Ez-ZhyB03i7PGZ_J3yH11VZC-xQOewhyNi0cLU5PY2qs_U3yheqqofjY_zvf33D0ghiB","legacy_responseItem_reasoning_19",[],{"_473":739,"_465":466,"_475":82},{"_502":740,"_504":741,"_91":506},"call_iGAGH0Hj37un8L5Z7fgvDHPu",{"_273":742,"_508":-5},"Chunk ID: 05b389\nWall time: 0.6728 seconds\nProcess exited with code 0\nOriginal token count: 87\nOutput:\nwarning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\nFound 1 error (1 fixed, 0 remaining).\n",{"_473":744,"_465":466,"_475":82},{"_511":745,"_513":746,"_515":747,"_517":518,"_519":748,"_521":31,"_41":740,"_522":749,"_470":112,"_91":524},"warning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\nFound 1 error (1 fixed, 0 remaining).\n","/bin/bash -lc 'ruff check --fix tests/s3_tests/test_s3_core.py src/cachier/cores/s3.py'",[750],672,"29606",{"_513":751,"_91":647},"ruff check --fix tests/s3_tests/test_s3_core.py src/cachier/cores/s3.py",{"_473":753,"_465":466,"_475":82},{"_511":-5,"_513":746,"_515":754,"_517":518,"_519":-5,"_521":-5,"_41":740,"_522":749,"_470":532,"_91":524},[755],{"_513":751,"_91":647},{"_473":757,"_465":466,"_475":82},{"_536":758,"_502":740,"_41":-5,"_166":538,"_91":539},"{\"cmd\":\"ruff check --fix tests/s3_tests/test_s3_core.py src/cachier/cores/s3.py\"}",{"_473":760,"_465":466,"_475":82},{"_476":-5,"_494":761,"_41":762,"_497":763,"_91":499},"gAAAAABpla6DY8xsdIBe8sHX5KoPi9mqTKtd4MAOCpWQAVLGDyw_Q2oz8ZoGxEuGPaYdxNZWizJRy5lbOr61d151i6yvi-N-ulh5pnPJC69eTqzdcp45734Y6d30wuXFeGoUlWKw2ungQIUR4sgYi0vLAKEg1E7OJVPn84BOKnhvRLtJfmjPQ7VVVKhTDUS_qWdG2Ov-XVA5LlvBSt2EDk_RtLmcFyzcwBdvQPYweE-v1MOP9Y7U0VzUbcYUI8aiaQBuV3R9gipDwJCeT9rUUWM1cIw0qe5ubjVm1XPVT6sJOAR8i7hr9wPRK3Bw-FV-Vbwn2k7RuumOsWZmym19ZO8oN6obFZRdjn_FcYmQErBx4VsGMNFBEVoU7or6qiDhWYDqwF0xVm2p8ATByFquUFnhhltVaPJdlrZR9sTgY2dj8UMaMZvb6Utbkmet1WbkY0XlKcrjyXytmWmxu8QawRsoSVeuFOcQR1lWi16pl4F8MdtoPjrV7AlLfTUV4LJsI9NQZO4ajx2G6jiltbEMx2XXSKSfXpRr9dIlnjrV-UlyXicvoldbCf45fS5GYziVmz0fJ68qje6Al2WjRpSk33lYbbSDwBwuBk92Q-MIUQm-1jZFwfvARR0JzSIWCUIlNx1NsbSlxwXtX4TWxZ7-jg1iA6Kyw04U0wg4aQgu6WP-ElgQUIDwK3nia4TAi2Bn3sbZgeBDI1fx2xVhjdvpnIaSE5R72vVSCn1HynTWArGeprgIyKf2r2nrFbwpW08pUILZdrg-fqBSc4MmeLZbQzav7szg6JMXTXFMldMzYB2L-crI3csw8VMrZpZ3571HHBuUYH4-bUUA-gromv_VPJAHsJIKuNFzP02jlv-PxuCyo-dtTUf3g_Kx_2wkKcyGGfUU6Dwtai6n2ubRa407rwZbvQ1Yy1S5s4jnh-6wyX3js9hRhAOKyL2TbqU8rWzMDX2QcNZdIul_6gw6-jlvAky28Sv3K4AQbuhKGhsynF8vOYdYJP3aDnG5M3_BJhh7p8m09cgb18WqFckPh6pfKyieO5Z0IxkBeajVZ8_u9ZpRWbhORru4O6UQ-LleukVa_i9JznVeKb0qJ4g1GqQSsBQwnfDsALhRSC4XQsQUh7bA6YHKLuxL82mKoZ-5_Dykf-ivOQ9rQ1suvckrACQCFmiSLvFhOkfI1HZs3idbWO6y7tturjb383VELTOj4gqCyWZsUbyW7YxsXsWPOXLuUNPwFSf3mfflKJVRIdGIoO6fQXIcn3rHT7c-EiI7JF7R4Y1FwDx35VkT7p1hvea_h1S7c_OpRY_3_s_t_k3GTBXZJ2tlgrmohH8LTpXQxF8LDuT8b2h2dpAUeionlR9Bb2iF4kPcCdaSbg==","legacy_responseItem_reasoning_18",[],{"_473":765,"_465":466,"_475":82},{"_502":766,"_504":767,"_91":506},"call_iBonynpHcUAl70YvMNHlrgy1",{"_273":768,"_508":-5},"Chunk ID: b7e11f\nWall time: 0.7725 seconds\nProcess exited with code 1\nOriginal token count: 297697\nOutput:\nTotal output lines: 33668\n\nwarning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\ninvalid-syntax: Expected a statement\n --> README.rst:4:1\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:15\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:27\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:43\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:58\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:68\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:81\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:90\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:6:49\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^^^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:6:57\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:6:68\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^^^^^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:6:78\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:8:1\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:8:2\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:8:4\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^^^^^^^^^^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:8:15\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:10:1\n |\n 8 | .. code-block:: python\n 9 |\n10 | from cachier import cachier\n | ^^\n11 | import datetime\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:19:1\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:19:2\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:19:9\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:20:1\n |\n19 | .. role:: python(code)\n20 | :language: python\n | ^^\n21 |\n22 | .. contents::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:20:3\n |\n19 | .. role:: python(code)\n20 | :language: python\n | ^\n21 |\n22 | .. contents::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:1\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:2\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:22:13\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:14\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:24:1\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:24:2\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:24:4\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:24:22\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:1\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:3\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:5\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:7\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:9\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:11\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:13\n |\n28 | Installation\n29 | ============\n | ^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:9\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:10\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:18\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:19\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Expected the start of an expression after `with` keyword\n --> README.rst:31:25\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:33:1\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:33:2\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:33:4\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^^^^^^^^^^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:33:15\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:35:1\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:35:9\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:35:17\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:37:1\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:5\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:9\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:16\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:24\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:35\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:42\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:46\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:53\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:37:57\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:39:1\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:39:2\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:39:4\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^^^^^^^^^^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:39:15\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:41:1\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:41:9\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:41:17\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^^^^^^^^^^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:43:1\n |\n41 | pip install 'cachier==1.2.8'\n42 |\n43 | Features\n | ^\n44 | ========\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:1\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:3\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:5\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:7\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:9\n |\n43 | Features\n44 | ========\n | ^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:46:9\n |\n44 | ========\n45 |\n46 | Current features\n | ^^^^^^^^\n47 | ----------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:47:17\n |\n46 | Current features\n47 | ----------------\n | ^\n48 |\n49 | * Pure Python.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:49:8\n |\n47 | ----------------\n48 |\n49 | * Pure Python.\n | ^^^^^^\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:49:15\n |\n47 | ----------------\n48 |\n49 | * Pure Python.\n | ^\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:50:14\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:26\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `)`, found float\n --> README.rst:50:39\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:50:43\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:50:47\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^^^^^^^^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:71\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:74\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found `)`\n --> README.rst:50:76\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^\n51 | * Supported and `tested on Linux, OS X and Windows README.rst:853:1\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:853:2\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:853:4\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:853:5\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^^^^^^^^^^^^^^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:853:20\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:853:28\n |\n851 | :target: https://github.com/python-cachier/cachier/actions/workflows/ci-test.yml\n852 |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n | ^^\n854 | :target: https://pypi.python.org/pypi/cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:854:1\n |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n854 | :target: https://pypi.python.org/pypi/cachier\n | ^^\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:854:3\n |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n854 | :target: https://pypi.python.org/pypi/cachier\n | ^\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:854:17\n |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n854 | :target: https://pypi.python.org/pypi/cachier\n | ^\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:854:18\n |\n853 | .. |LICENCE| image:: https://img.shields.io/pypi/l/cachier.svg\n854 | :target: https://pypi.python.org/pypi/cachier\n | ^^\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:856:1\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:856:2\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:856:4\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:856:5\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^^^^^^^^^^^^^^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:856:20\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:856:28\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Got unexpected token ?\n --> README.rst:856:83\n |\n854 | :target: https://pypi.python.org/pypi/cachier\n855 |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n | ^\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:857:1\n |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n | ^^^\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:857:4\n |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n | ^\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:857:18\n |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n | ^\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:857:19\n |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n | ^^\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n |\n\ninvalid-syntax: Got unexpected token ?\n --> README.rst:857:61\n |\n856 | .. |Codecov| image:: https://codecov.io/github/python-cachier/cachier/coverage.svg?branch=master\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n | ^\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:859:1\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:859:2\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:859:4\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:859:5\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^^^^^^^^^^^^^^^^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:859:22\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:859:30\n |\n857 | :target: https://codecov.io/github/python-cachier/cachier?branch=master\n858 |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n | ^^\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:860:1\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n | ^^^^^\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:860:6\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n | ^\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:860:20\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n | ^\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:860:21\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n | ^^\n861 | :alt: PePy stats\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:861:6\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n | ^\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:861:17\n |\n859 | .. |Downloads| image:: https://pepy.tech/badge/cachier\n860 | :target: https://pepy.tech/project/cachier\n861 | :alt: PePy stats\n | ^^^^^\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:863:1\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:863:2\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:863:4\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:863:5\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^^^^^^^^^^^^^^^^^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:863:23\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:863:31\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Got unexpected token ?\n --> README.rst:863:97\n |\n861 | :alt: PePy stats\n862 |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n | ^\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:864:1\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n | ^^^^^\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:864:6\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n | ^\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:864:20\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n | ^\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:864:21\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n | ^^\n865 | :alt: Codefactor code quality\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:865:6\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n | ^\n866 |\n867 | .. links:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:865:23\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n | ^^^^\n866 |\n867 | .. links:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:865:28\n |\n863 | .. |Codefactor| image:: https://www.codefactor.io/repository/github/python-cachier/cachier/badge?style=plastic\n864 | :target: https://www.codefactor.io/repository/github/python-cachier/cachier\n865 | :alt: Codefactor code quality\n | ^^^^^^^\n866 |\n867 | .. links:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:867:1\n |\n865 | :alt: Codefactor code quality\n866 |\n867 | .. links:\n | ^\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:867:2\n |\n865 | :alt: Codefactor code quality\n866 |\n867 | .. links:\n | ^\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:867:10\n |\n865 | :alt: Codefactor code quality\n866 |\n867 | .. links:\n | ^\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:868:1\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n | ^\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:868:2\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n | ^\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:868:19\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n | ^\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:868:20\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n | ^^\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:868:53\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n | ^\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:869:1\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:869:2\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:869:20\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:869:21\n |\n867 | .. links:\n868 | .. _pymongo: https://api.mongodb.com/python/current/\n869 | .. _watchdog: https://github.com/gorakhargosh/watchdog\n | ^^\n |\n\nI001 [*] Import block is un-sorted or un-formatted\n --> tests/s3_tests/test_s3_core.py:3:1\n |\n 1 | \"\"\"Tests for the S3 caching core.\"\"\"\n 2 |\n 3 | / import contextlib\n 4 | | import asyncio\n 5 | | import threading\n 6 | | import warnings\n 7 | | from datetime import timedelta\n 8 | | from random import random\n 9 | |\n10 | | import pytest\n11 | |\n12 | | from tests.s3_tests.helpers import S3_DEPS_AVAILABLE, TEST_BUCKET, TEST_REGION, skip_if_missing\n | |_______________________________________________________________________________________________^\n13 |\n14 | if S3_DEPS_AVAILABLE:\n |\nhelp: Organize imports\n\nFound 3185 errors.\n[*] 1 fixable with the `--fix` option.\n",{"_473":770,"_465":466,"_475":82},{"_511":771,"_513":772,"_515":773,"_517":518,"_519":774,"_521":775,"_41":766,"_522":776,"_470":777,"_91":524},"warning: `incorrect-blank-line-before-class` (D203) and `no-blank-line-before-class` (D211) are incompatible. Ignoring `incorrect-blank-line-before-class`.\nwarning: `multi-line-summary-first-line` (D212) and `multi-line-summary-second-line` (D213) are incompatible. Ignoring `multi-line-summary-second-line`.\ninvalid-syntax: Expected a statement\n --> README.rst:4:1\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:15\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:27\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:43\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:58\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:68\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:81\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:4:90\n |\n2 | #######\n3 |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n | ^\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:6:49\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^^^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:6:57\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:6:68\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^^^^^^^^^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:6:78\n |\n4 | |PyPI-Status| |Downloads| |PyPI-Versions| |Build-Status| |Codecov| |Codefactor| |LICENCE|\n5 |\n6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n | ^\n7 |\n8 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:8:1\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:8:2\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:8:4\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^^^^^^^^^^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:8:15\n |\n 6 | Persistent, stale-free, local and cross-machine caching for Python functions.\n 7 |\n 8 | .. code-block:: python\n | ^\n 9 |\n10 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:10:1\n |\n 8 | .. code-block:: python\n 9 |\n10 | from cachier import cachier\n | ^^\n11 | import datetime\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:19:1\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:19:2\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:19:9\n |\n19 | .. role:: python(code)\n | ^\n20 | :language: python\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:20:1\n |\n19 | .. role:: python(code)\n20 | :language: python\n | ^^\n21 |\n22 | .. contents::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:20:3\n |\n19 | .. role:: python(code)\n20 | :language: python\n | ^\n21 |\n22 | .. contents::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:1\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:2\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:22:13\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:22:14\n |\n20 | :language: python\n21 |\n22 | .. contents::\n | ^\n23 |\n24 | .. section-numbering:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:24:1\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:24:2\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:24:4\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:24:22\n |\n22 | .. contents::\n23 |\n24 | .. section-numbering:\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:1\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:3\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:5\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:7\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:9\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:11\n |\n28 | Installation\n29 | ============\n | ^^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:29:13\n |\n28 | Installation\n29 | ============\n | ^\n30 |\n31 | Install ``cachier`` with:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:9\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:10\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:18\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:31:19\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Expected the start of an expression after `with` keyword\n --> README.rst:31:25\n |\n29 | ============\n30 |\n31 | Install ``cachier`` with:\n | ^\n32 |\n33 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:33:1\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:33:2\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:33:4\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^^^^^^^^^^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:33:15\n |\n31 | Install ``cachier`` with:\n32 |\n33 | .. code-block:: python\n | ^\n34 |\n35 | pip install cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:35:1\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:35:9\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:35:17\n |\n33 | .. code-block:: python\n34 |\n35 | pip install cachier\n | ^^^^^^^\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:37:1\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:5\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:9\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:16\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:24\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:35\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:42\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:46\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:37:53\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^^^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:37:57\n |\n35 | pip install cachier\n36 |\n37 | For the latest version supporting Python 2.7 please use:\n | ^\n38 |\n39 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:39:1\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:39:2\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:39:4\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^^^^^^^^^^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:39:15\n |\n37 | For the latest version supporting Python 2.7 please use:\n38 |\n39 | .. code-block:: python\n | ^\n40 |\n41 | pip install 'cachier==1.2.8'\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:41:1\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:41:9\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:41:17\n |\n39 | .. code-block:: python\n40 |\n41 | pip install 'cachier==1.2.8'\n | ^^^^^^^^^^^^^^^^\n42 |\n43 | Features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:43:1\n |\n41 | pip install 'cachier==1.2.8'\n42 |\n43 | Features\n | ^\n44 | ========\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:1\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:3\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:5\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:7\n |\n43 | Features\n44 | ========\n | ^^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:44:9\n |\n43 | Features\n44 | ========\n | ^\n45 |\n46 | Current features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:46:9\n |\n44 | ========\n45 |\n46 | Current features\n | ^^^^^^^^\n47 | ----------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:47:17\n |\n46 | Current features\n47 | ----------------\n | ^\n48 |\n49 | * Pure Python.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:49:8\n |\n47 | ----------------\n48 |\n49 | * Pure Python.\n | ^^^^^^\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:49:15\n |\n47 | ----------------\n48 |\n49 | * Pure Python.\n | ^\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:50:14\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:26\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `)`, found float\n --> README.rst:50:39\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:50:43\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:50:47\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^^^^^^^^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:71\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found float\n --> README.rst:50:74\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found `)`\n --> README.rst:50:76\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `,`, found `.`\n --> README.rst:50:77\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected `:`, found newline\n --> README.rst:50:78\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n | ^\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:51:1\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Boolean expression cannot be used here\n --> README.rst:51:3\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^^^^^^^^^^^^^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:51:17\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:51:17\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:51:25\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:51:28\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^^^^^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:51:28\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:51:38\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:51:59\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:51:92\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:51:95\n |\n49 | * Pure Python.\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n | ^\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:52:5\n |\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n | ^^^^^^\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:52:12\n |\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n | ^^^^^^^^^\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:52:22\n |\n50 | * Compatible with Python 3.9+ (Python 2.7 was discontinued in version 1.2.8).\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n | ^\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:53:12\n |\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n | ^^^^^^^^^^^^\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:53:25\n |\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n | ^^^\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:53:36\n |\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n | ^^^^^^\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:53:43\n |\n51 | * Supported and `tested on Linux, OS X and Windows `_.\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n | ^\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:54:1\n |\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n | ^\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Boolean expression cannot be used here\n --> README.rst:54:3\n |\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n | ^^^^^^^^^^^^^^\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:54:18\n |\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n | ^^^^^^^^^\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:54:28\n |\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n | ^^^^^^^\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:54:36\n |\n52 | * A simple interface.\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n | ^\n55 | * Multiple caching backends (cores):\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:55:12\n |\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n | ^^^^^^^\n56 |\n57 | * Local caching using pickle files.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:55:20\n |\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n | ^^^^^^^^\n56 |\n57 | * Local caching using pickle files.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:55:37\n |\n53 | * Defining \"shelf life\" for cached values.\n54 | * Async and sync functions support.\n55 | * Multiple caching backends (cores):\n | ^\n56 |\n57 | * Local caching using pickle files.\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:57:1\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:57:11\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^^^^^^^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:57:19\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^^^^^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:57:25\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^^^^^^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:57:32\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^^^^^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:57:38\n |\n55 | * Multiple caching backends (cores):\n56 |\n57 | * Local caching using pickle files.\n | ^\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:58:15\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^^^^^^^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:58:23\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^^^^^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:58:29\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^^^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:58:33\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^^^^^^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:58:40\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^^^^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:58:45\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n | ^\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:59:19\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n | ^^^^^^^\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:59:27\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n | ^^^^^\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:59:33\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n | ^^^^^^^\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:59:41\n |\n57 | * Local caching using pickle files.\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n | ^\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:60:15\n |\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n | ^^^^^^^\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:60:23\n |\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n | ^^^^^\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:60:29\n |\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n | ^^^^^^^^^^\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:60:50\n |\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n | ^^^^^^^^^\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:60:60\n |\n58 | * In-memory caching using the memory core.\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n | ^\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:61:17\n |\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n | ^^^^^^^\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:61:25\n |\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n | ^^^\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:61:29\n |\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n | ^^^^^^^^^^^^^^^^\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:61:46\n |\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n | ^^^^^^^^^\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:61:56\n |\n59 | * Cross-machine caching using MongoDB.\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n | ^\n62 | * S3-based caching for cross-machine object storage backends.\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:62:3\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:62:14\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^^^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:62:22\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:62:26\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^^^^^^^^^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:62:40\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:62:47\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^^^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:62:55\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^^^^^^^^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:62:64\n |\n60 | * SQL-based caching using SQLAlchemy-supported databases.\n61 | * Redis-based caching for high-performance scenarios.\n62 | * S3-based caching for cross-machine object storage backends.\n | ^\n63 |\n64 | * Thread-safety.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:64:1\n |\n62 | * S3-based caching for cross-machine object storage backends.\n63 |\n64 | * Thread-safety.\n | ^\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:64:17\n |\n62 | * S3-based caching for cross-machine object storage backends.\n63 |\n64 | * Thread-safety.\n | ^\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:65:3\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:14\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:18\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:65:22\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:33\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:35\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^^^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:43\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:65:47\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:65:58\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:65:65\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:65:69\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^^^^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:65:74\n |\n64 | * Thread-safety.\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n | ^\n66 |\n67 | Cachier is **NOT**:\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:67:1\n |\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n66 |\n67 | Cachier is **NOT**:\n | ^^^^^^^^^^^^^^^^^^\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:67:12\n |\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n66 |\n67 | Cachier is **NOT**:\n | ^^\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:67:19\n |\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n66 |\n67 | Cachier is **NOT**:\n | ^\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:67:20\n |\n65 | * **Per-call max age:** Specify a maximum age for cached values per call.\n66 |\n67 | Cachier is **NOT**:\n | ^\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:69:9\n |\n67 | Cachier is **NOT**:\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n | ^^\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:69:14\n |\n67 | Cachier is **NOT**:\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n | ^^^^^^^^^\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:69:24\n |\n67 | Cachier is **NOT**:\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n | ^^^^^\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:69:37\n |\n67 | Cachier is **NOT**:\n68 |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n | ^^^^^^^^^^^^^^^^^^^^^^^^\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:14\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:32\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:35\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:43\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:52\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:58\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:63\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:68\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:73\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:77\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:81\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:70:83\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Expected `,`, found int\n --> README.rst:70:115\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:70:117\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^^^^^^^\n71 |\n72 | Future features\n |\n\nE501 Line too long (129 > 120)\n --> README.rst:70:121\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^^^^^^^^^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:70:130\n |\n69 | * Meant as a transient cache. Python's @lru_cache is better.\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n | ^\n71 |\n72 | Future features\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:72:8\n |\n70 | * Especially fast. It is meant to replace function calls that take more than... a second, say (overhead is around 1 millisecond).\n71 |\n72 | Future features\n | ^^^^^^^^\n73 | ---------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:73:16\n |\n72 | Future features\n73 | ---------------\n | ^\n74 |\n75 | * Multi-core caching.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:75:14\n |\n73 | ---------------\n74 |\n75 | * Multi-core caching.\n | ^^^^^^^\n76 | * `Cache replacement policies `_\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:75:22\n |\n73 | ---------------\n74 |\n75 | * Multi-core caching.\n | ^\n76 | * `Cache replacement policies `_\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:76:3\n |\n75 | * Multi-core caching.\n76 | * `Cache replacement policies `_\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:76:10\n |\n75 | * Multi-core caching.\n76 | * `Cache replacement policies `_\n | ^^^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:76:22\n |\n75 | * Multi-core caching.\n76 | * `Cache replacement policies `_\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:76:38\n |\n75 | * Multi-core caching.\n76 | * `Cache replacement policies `_\n | ^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:76:89\n |\n75 | * Multi-core caching.\n76 | * `Cache replacement policies `_\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:80:1\n |\n79 | Use\n80 | ===\n | ^^\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:80:3\n |\n79 | Use\n80 | ===\n | ^\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:80:4\n |\n79 | Use\n80 | ===\n | ^\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:9\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:18\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:20\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:30\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:36\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:40\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:44\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:49\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:56\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:61\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:71\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:74\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:79\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:84\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:86\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:97\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^\n83 |\n84 | Setting up a Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:108\n |\n80 | ===\n81 |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n | ^^^^^^^^^^\n83 |\n84 | Setting up a Cache\n |\n\nE501 Line too long (464 > 120)\n --> README.rst:82:121\n |\n80 | …\n81 | …\n82 | …al and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutable containers). Also, notice that since objects which are instances of user-defined classes are hashable but all compare unequal (their hash value is their id), equal objects across different sessions will not yield identical keys.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:131\n |\n80 | …\n81 | …\n82 | …s to give them a persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immut…\n | ^^^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:141\n |\n80 | …\n81 | …\n82 | …ve them a persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable bu…\n | ^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:144\n |\n80 | …\n81 | …\n82 | …them a persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built…\n | ^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:148\n |\n80 | …\n81 | …\n82 | … persistent cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in ob…\n | ^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:156\n |\n80 | …\n81 | …\n82 | …nt cache. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, no…\n | ^^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:165\n |\n80 | …\n81 | …\n82 | …e. The positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutab…\n | ^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:170\n |\n80 | …\n81 | …\n82 | …he positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutable c…\n | ^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:82:173\n |\n80 | …\n81 | …\n82 | …itional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in objects, not mutable contain…\n | ^^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:82:194\n |\n80 | …\n81 | …\n82 | …ython's immutable built-in objects, not mutable containers). Also, notice that since objects which are instances of user-defined classes are hashable but all compare unequal (their hash value is their id), equal objects across different sessions will not yield identical keys.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n83 | …\n84 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:84:1\n |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n83 |\n84 | Setting up a Cache\n | ^^^^^^^\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:84:9\n |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n83 |\n84 | Setting up a Cache\n | ^^\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:84:12\n |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n83 |\n84 | Setting up a Cache\n | ^\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:84:14\n |\n82 | Cachier provides a decorator which you can wrap around your functions to give them a persistent cache. The positional and keyword argu…\n83 |\n84 | Setting up a Cache\n | ^^^^^\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:5\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:9\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:13\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:15\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:49\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:55\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:58\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:63\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:82\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:85\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:90\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:95\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:102\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:112\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:119\n |\n84 | Setting up a Cache\n85 | ------------------\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n | ^^^^^^^\n87 |\n88 | .. code-block:: python\n |\n\nE501 Line too long (226 > 120)\n --> README.rst:86:121\n |\n84 | …\n85 | …\n86 | …ent Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:127\n |\n84 | …\n85 | …\n86 | …unction - meaning it will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` d…\n | ^^^^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:135\n |\n84 | …\n85 | …\n86 | …n - meaning it will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorat…\n | ^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:139\n |\n84 | …\n85 | …\n86 | …aning it will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (no…\n | ^^^^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:147\n |\n84 | …\n85 | …\n86 | …will last across different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the …\n | ^^^^^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:161\n |\n84 | …\n85 | …\n86 | …s different Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^^^^^^^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:172\n |\n84 | …\n85 | …\n86 | …rent Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `)`, found `with`\n --> README.rst:86:175\n |\n84 | …\n85 | …\n86 | … Python kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:184\n |\n84 | …\n85 | …\n86 | … kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:185\n |\n84 | …\n85 | …\n86 | …kernels calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:193\n |\n84 | …\n85 | …\n86 | …calling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:194\n |\n84 | …\n85 | …\n86 | …alling the wrapped function - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:86:214\n |\n84 | …\n85 | …\n86 | …nction - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^^^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:218\n |\n84 | …\n85 | …\n86 | …ion - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:219\n |\n84 | …\n85 | …\n86 | …on - by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:222\n |\n84 | …\n85 | …\n86 | …- by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:86:223\n |\n84 | …\n85 | …\n86 | … by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected `,`, found `!`\n --> README.rst:86:224\n |\n84 | …\n85 | …\n86 | …by decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:86:227\n |\n84 | …\n85 | …\n86 | …decorating it with the ``cachier`` decorator (notice the ``()``!).\n | ^\n87 | …\n88 | …\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:88:1\n |\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n87 |\n88 | .. code-block:: python\n | ^\n89 |\n90 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:88:2\n |\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n87 |\n88 | .. code-block:: python\n | ^\n89 |\n90 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:88:4\n |\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n87 |\n88 | .. code-block:: python\n | ^^^^^^^^^^\n89 |\n90 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:88:15\n |\n86 | You can add a default, pickle-based, persistent cache to your function - meaning it will last across different Python kernels calling …\n87 |\n88 | .. code-block:: python\n | ^\n89 |\n90 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:90:1\n |\n88 | .. code-block:: python\n89 |\n90 | from cachier import cachier\n | ^^\n91 |\n92 | @cachier()\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:97:1\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:18\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:26\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:30\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:35\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:38\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:54\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:59\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^^^^^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:73\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:80\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:97:84\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:97:89\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:101\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:106\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^^^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:118\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^\n98 |\n99 | .. code-block:: python\n |\n\nE501 Line too long (262 > 120)\n --> README.rst:97:121\n |\n95 | …\n96 | …\n97 | …g the cache key for an object method. **This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:122\n |\n95 | return {'arg1': arg1, 'arg2': arg2}\n96 |\n97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n | ^^^^^\n98 |\n99 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:128\n |\n95 | …\n96 | …\n97 | …atically ignore the `self` parameter when determining the cache key for an object method. **This means that methods will be cached a…\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:97:132\n |\n95 | …\n96 | …\n97 | …ally ignore the `self` parameter when determining the cache key for an object method. **This means that methods will be cached acros…\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:97:139\n |\n95 | …\n96 | …\n97 | …ore the `self` parameter when determining the cache key for an object method. **This means that methods will be cached across all in…\n | ^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:97:146\n |\n95 | …\n96 | …\n97 | … `self` parameter when determining the cache key for an object method. **This means that methods will be cached across all instances…\n | ^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:97:154\n |\n95 | …\n96 | …\n97 | …` parameter when determining the cache key for an object method. **This means that methods will be cached across all instances of an…\n | ^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:161\n |\n95 | …\n96 | …\n97 | …er when determining the cache key for an object method. **This means that methods will be cached across all instances of an object, …\n | ^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:167\n |\n95 | …\n96 | …\n97 | …en determining the cache key for an object method. **This means that methods will be cached across all instances of an object, which…\n | ^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:172\n |\n95 | …\n96 | …\n97 | …rmining the cache key for an object method. **This means that methods will be cached across all instances of an object, which may no…\n | ^^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:180\n |\n95 | …\n96 | …\n97 | …g the cache key for an object method. **This means that methods will be cached across all instances of an object, which may not be w…\n | ^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:185\n |\n95 | …\n96 | …\n97 | …e cache key for an object method. **This means that methods will be cached across all instances of an object, which may not be what …\n | ^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:188\n |\n95 | …\n96 | …\n97 | …he key for an object method. **This means that methods will be cached across all instances of an object, which may not be what you w…\n | ^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:195\n |\n95 | …\n96 | …\n97 | …for an object method. **This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:202\n |\n95 | …\n96 | …\n97 | … object method. **This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:206\n |\n95 | …\n96 | …\n97 | … method. **This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:216\n |\n95 | …\n96 | …\n97 | …d. **This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:219\n |\n95 | …\n96 | …\n97 | …**This means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:97:222\n |\n95 | …\n96 | …\n97 | …s means that methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:97:236\n |\n95 | …\n96 | …\n97 | …methods will be cached across all instances of an object, which may not be what you want.**\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `,`, found `not`\n --> README.rst:97:240\n |\n95 | …\n96 | …\n97 | …ods will be cached across all instances of an object, which may not be what you want.**\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:97:247\n |\n95 | …\n96 | …\n97 | …l be cached across all instances of an object, which may not be what you want.**\n | ^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:97:252\n |\n95 | …\n96 | …\n97 | …cached across all instances of an object, which may not be what you want.**\n | ^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:97:256\n |\n95 | …\n96 | …\n97 | …ed across all instances of an object, which may not be what you want.**\n | ^^^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:97:261\n |\n95 | …\n96 | …\n97 | …cross all instances of an object, which may not be what you want.**\n | ^^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:97:263\n |\n95 | …\n96 | …\n97 | …oss all instances of an object, which may not be what you want.**\n | ^\n98 | …\n99 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:99:1\n |\n 97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n 98 |\n 99 | .. code-block:: python\n | ^\n100 |\n101 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:99:2\n |\n 97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n 98 |\n 99 | .. code-block:: python\n | ^\n100 |\n101 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:99:4\n |\n 97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n 98 |\n 99 | .. code-block:: python\n | ^^^^^^^^^^\n100 |\n101 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:99:15\n |\n 97 | Class and object methods can also be cached. Cachier will automatically ignore the `self` parameter when determining the cache key fo…\n 98 |\n 99 | .. code-block:: python\n | ^\n100 |\n101 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:101:1\n |\n 99 | .. code-block:: python\n100 |\n101 | from cachier import cachier\n | ^^\n102 |\n103 | class Foo():\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:126:1\n |\n126 | Resetting a Cache\n | ^\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:126:11\n |\n126 | Resetting a Cache\n | ^\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:126:13\n |\n126 | Resetting a Cache\n | ^^^^^\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:127:18\n |\n126 | Resetting a Cache\n127 | -----------------\n | ^\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:5\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:13\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:21\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:26\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:128:28\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:128:29\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:128:43\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:128:44\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:55\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:58\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:63\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:71\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:84\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:90\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:94\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:100\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:103\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:107\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:115\n |\n126 | Resetting a Cache\n127 | -----------------\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n | ^^^^^^^^\n129 |\n130 | .. code-block:: python\n |\n\nE501 Line too long (147 > 120)\n --> README.rst:128:121\n |\n126 | …\n127 | …\n128 | …d function. To reset the cache of the wrapped function simply call this method:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:124\n |\n126 | …\n127 | …\n128 | …h wrapped function. To reset the cache of the wrapped function simply call this method:\n | ^^^^^^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:131\n |\n126 | …\n127 | …\n128 | …ped function. To reset the cache of the wrapped function simply call this method:\n | ^^^^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:136\n |\n126 | …\n127 | …\n128 | …unction. To reset the cache of the wrapped function simply call this method:\n | ^^^^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:128:141\n |\n126 | …\n127 | …\n128 | …n. To reset the cache of the wrapped function simply call this method:\n | ^^^^^^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:128:148\n |\n126 | …\n127 | …\n128 | … reset the cache of the wrapped function simply call this method:\n | ^\n129 | …\n130 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:130:1\n |\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n129 |\n130 | .. code-block:: python\n | ^\n131 |\n132 | foo.clear_cache()\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:130:2\n |\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n129 |\n130 | .. code-block:: python\n | ^\n131 |\n132 | foo.clear_cache()\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:130:4\n |\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n129 |\n130 | .. code-block:: python\n | ^^^^^^^^^^\n131 |\n132 | foo.clear_cache()\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:130:15\n |\n128 | The Cachier wrapper adds a ``clear_cache()`` function to each wrapped function. To reset the cache of the wrapped function simply cal…\n129 |\n130 | .. code-block:: python\n | ^\n131 |\n132 | foo.clear_cache()\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:132:1\n |\n130 | .. code-block:: python\n131 |\n132 | foo.clear_cache()\n | ^^\n133 |\n134 | General Configuration\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:134:1\n |\n132 | foo.clear_cache()\n133 |\n134 | General Configuration\n | ^\n135 | ----------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:134:9\n |\n132 | foo.clear_cache()\n133 |\n134 | General Configuration\n | ^^^^^^^^^^^^^\n135 | ----------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:135:23\n |\n134 | General Configuration\n135 | ----------------------\n | ^\n136 |\n137 | Global Defaults\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:137:8\n |\n135 | ----------------------\n136 |\n137 | Global Defaults\n | ^^^^^^^^\n138 | ~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:138:16\n |\n137 | Global Defaults\n138 | ~~~~~~~~~~~~~~~\n | ^\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:10\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:14\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:17\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:26\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:37\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:44\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:48\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:56\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:65\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^^^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:73\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:77\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:81\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:84\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^^^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:140:88\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:140:107\n |\n138 | ~~~~~~~~~~~~~~~\n139 |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n | ^\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n |\n\nE501 Line too long (354 > 120)\n --> README.rst:140:121\n |\n138 | …\n139 | …\n140 | …n. This function takes the same keyword parameters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:124\n |\n138 | …\n139 | …\n140 | …rs through the use of the `set_default_params` function. This function takes the same keyword parameters as the ones defined in the …\n | ^^^^^^^^\n141 | …\n142 | …efined after `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:133\n |\n138 | …\n139 | …\n140 | …gh the use of the `set_default_params` function. This function takes the same keyword parameters as the ones defined in the decorato…\n | ^^^^^\n141 | …\n142 | …fter `set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:139\n |\n138 | …\n139 | …\n140 | …e use of the `set_default_params` function. This function takes the same keyword parameters as the ones defined in the decorator, wh…\n | ^^^\n141 | …\n142 | …`set_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:143\n |\n138 | …\n139 | …\n140 | …e of the `set_default_params` function. This function takes the same keyword parameters as the ones defined in the decorator, which …\n | ^^^^\n141 | …\n142 | …_default_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:148\n |\n138 | …\n139 | …\n140 | …e `set_default_params` function. This function takes the same keyword parameters as the ones defined in the decorator, which can be …\n | ^^^^^^^\n141 | …\n142 | …t_params` is called:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:156\n |\n138 | …\n139 | …\n140 | …fault_params` function. This function takes the same keyword parameters as the ones defined in the decorator, which can be passed al…\n | ^^^^^^^^^^\n141 | …\n142 | … is called:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:140:167\n |\n138 | …\n139 | …\n140 | …arams` function. This function takes the same keyword parameters as the ones defined in the decorator, which can be passed all at on…\n | ^^\n141 | …\n142 | …led:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:174\n |\n138 | …\n139 | …\n140 | …unction. This function takes the same keyword parameters as the ones defined in the decorator, which can be passed all at once or wi…\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:179\n |\n138 | …\n139 | …\n140 | …. This function takes the same keyword parameters as the ones defined in the decorator, which can be passed all at once or with mult…\n | ^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:140:194\n |\n138 | …\n139 | …\n140 | …takes the same keyword parameters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Para…\n | ^^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:211\n |\n138 | …\n139 | …\n140 | … keyword parameters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given d…\n | ^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:215\n |\n138 | …\n139 | …\n140 | …yword parameters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given dire…\n | ^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:218\n |\n138 | …\n139 | …\n140 | … parameters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly …\n | ^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:225\n |\n138 | …\n139 | …\n140 | …eters as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a d…\n | ^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:229\n |\n138 | …\n139 | …\n140 | …rs as the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a deco…\n | ^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:232\n |\n138 | …\n139 | …\n140 | …s the ones defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a decorato…\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `with` that cannot be used here\n --> README.rst:140:240\n |\n138 | …\n139 | …\n140 | …es defined in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a decorator take p…\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:245\n |\n138 | …\n139 | …\n140 | …ned in the decorator, which can be passed all at once or with multiple calls. Parameters given directly to a decorator take preceden…\n | ^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:254\n |\n138 | …\n139 | …\n140 | …he decorator, which can be passed all at once or with multiple calls. Parameters given directly to a decorator take precedence over …\n | ^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:272\n |\n138 | …\n139 | …\n140 | …h can be passed all at once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by …\n | ^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:278\n |\n138 | …\n139 | …\n140 | …e passed all at once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by this fu…\n | ^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:287\n |\n138 | …\n139 | …\n140 | …ed all at once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:290\n |\n138 | …\n139 | …\n140 | …all at once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:292\n |\n138 | …\n139 | …\n140 | … once or with multiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:302\n |\n138 | …\n139 | …\n140 | …r with multiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:307\n |\n138 | …\n139 | …\n140 | …ultiple calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:318\n |\n138 | …\n139 | …\n140 | …calls. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:323\n |\n138 | …\n139 | …\n140 | …. Parameters given directly to a decorator take precedence over any values set by this function.\n | ^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:327\n |\n138 | …\n139 | …\n140 | …ameters given directly to a decorator take precedence over any values set by this function.\n | ^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:334\n |\n138 | …\n139 | …\n140 | …s given directly to a decorator take precedence over any values set by this function.\n | ^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:338\n |\n138 | …\n139 | …\n140 | …iven directly to a decorator take precedence over any values set by this function.\n | ^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:341\n |\n138 | …\n139 | …\n140 | … directly to a decorator take precedence over any values set by this function.\n | ^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:140:346\n |\n138 | …\n139 | …\n140 | …ly to a decorator take precedence over any values set by this function.\n | ^^^^^^^^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:140:355\n |\n138 | \n139 | …\n140 | …a decorator take precedence over any values set by this function.\n | ^\n141 | …\n142 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:5\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:15\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:26\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:31\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:36\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:39\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:47\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:50\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:61\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:142:69\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^^^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:142:75\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:142:94\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:142:96\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:142:106\n |\n140 | Settings can be globally configured across all Cachier wrappers through the use of the `set_default_params` function. This function t…\n141 |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n | ^\n143 |\n144 | * `hash_func`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:144:4\n |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n143 |\n144 | * `hash_func`\n | ^\n145 | * `backend`\n146 | * `mongetter`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:144:14\n |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n143 |\n144 | * `hash_func`\n | ^\n145 | * `backend`\n146 | * `mongetter`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:144:15\n |\n142 | The following parameters will only be applied to decorators defined after `set_default_params` is called:\n143 |\n144 | * `hash_func`\n | ^\n145 | * `backend`\n146 | * `mongetter`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:145:4\n |\n144 | * `hash_func`\n145 | * `backend`\n | ^\n146 | * `mongetter`\n147 | * `cache_dir`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:145:12\n |\n144 | * `hash_func`\n145 | * `backend`\n | ^\n146 | * `mongetter`\n147 | * `cache_dir`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:145:13\n |\n144 | * `hash_func`\n145 | * `backend`\n | ^\n146 | * `mongetter`\n147 | * `cache_dir`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:146:4\n |\n144 | * `hash_func`\n145 | * `backend`\n146 | * `mongetter`\n | ^\n147 | * `cache_dir`\n148 | * `pickle_reload`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:146:14\n |\n144 | * `hash_func`\n145 | * `backend`\n146 | * `mongetter`\n | ^\n147 | * `cache_dir`\n148 | * `pickle_reload`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:146:15\n |\n144 | * `hash_func`\n145 | * `backend`\n146 | * `mongetter`\n | ^\n147 | * `cache_dir`\n148 | * `pickle_reload`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:147:4\n |\n145 | * `backend`\n146 | * `mongetter`\n147 | * `cache_dir`\n | ^\n148 | * `pickle_reload`\n149 | * `separate_files`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:147:14\n |\n145 | * `backend`\n146 | * `mongetter`\n147 | * `cache_dir`\n | ^\n148 | * `pickle_reload`\n149 | * `separate_files`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:147:15\n |\n145 | * `backend`\n146 | * `mongetter`\n147 | * `cache_dir`\n | ^\n148 | * `pickle_reload`\n149 | * `separate_files`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:148:4\n |\n146 | * `mongetter`\n147 | * `cache_dir`\n148 | * `pickle_reload`\n | ^\n149 | * `separate_files`\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:148:18\n |\n146 | * `mongetter`\n147 | * `cache_dir`\n148 | * `pickle_reload`\n | ^\n149 | * `separate_files`\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:148:19\n |\n146 | * `mongetter`\n147 | * `cache_dir`\n148 | * `pickle_reload`\n | ^\n149 | * `separate_files`\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:149:4\n |\n147 | * `cache_dir`\n148 | * `pickle_reload`\n149 | * `separate_files`\n | ^\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:149:19\n |\n147 | * `cache_dir`\n148 | * `pickle_reload`\n149 | * `separate_files`\n | ^\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:149:20\n |\n147 | * `cache_dir`\n148 | * `pickle_reload`\n149 | * `separate_files`\n | ^\n150 | * `entry_size_limit`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:150:4\n |\n148 | * `pickle_reload`\n149 | * `separate_files`\n150 | * `entry_size_limit`\n | ^\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:150:21\n |\n148 | * `pickle_reload`\n149 | * `separate_files`\n150 | * `entry_size_limit`\n | ^\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:150:22\n |\n148 | * `pickle_reload`\n149 | * `separate_files`\n150 | * `entry_size_limit`\n | ^\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:7\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^^^^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:18\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:22\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:25\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:33\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:36\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:40\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:54\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:59\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:65\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:68\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:152:72\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^^^^^^^^^^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:152:83\n |\n150 | * `entry_size_limit`\n151 |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n | ^\n153 |\n154 | * `allow_none`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:154:4\n |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n153 |\n154 | * `allow_none`\n | ^\n155 | * `caching_enabled`\n156 | * `stale_after`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:154:15\n |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n153 |\n154 | * `allow_none`\n | ^\n155 | * `caching_enabled`\n156 | * `stale_after`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:154:16\n |\n152 | These parameters can be changed at any time and they will apply to all decorators:\n153 |\n154 | * `allow_none`\n | ^\n155 | * `caching_enabled`\n156 | * `stale_after`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:155:4\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n | ^\n156 | * `stale_after`\n157 | * `next_time`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:155:20\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n | ^\n156 | * `stale_after`\n157 | * `next_time`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:155:21\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n | ^\n156 | * `stale_after`\n157 | * `next_time`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:156:4\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n156 | * `stale_after`\n | ^\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:156:16\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n156 | * `stale_after`\n | ^\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:156:17\n |\n154 | * `allow_none`\n155 | * `caching_enabled`\n156 | * `stale_after`\n | ^\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:157:4\n |\n155 | * `caching_enabled`\n156 | * `stale_after`\n157 | * `next_time`\n | ^\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:157:14\n |\n155 | * `caching_enabled`\n156 | * `stale_after`\n157 | * `next_time`\n | ^\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:157:15\n |\n155 | * `caching_enabled`\n156 | * `stale_after`\n157 | * `next_time`\n | ^\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:158:4\n |\n156 | * `stale_after`\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n | ^\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:158:26\n |\n156 | * `stale_after`\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n | ^\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:158:27\n |\n156 | * `stale_after`\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n | ^\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:159:4\n |\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n | ^\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:159:18\n |\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n | ^\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:159:19\n |\n157 | * `next_time`\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n | ^\n160 | * `cleanup_interval`\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:160:4\n |\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n | ^\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:160:21\n |\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n | ^\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:160:22\n |\n158 | * `wait_for_calc_timeout`\n159 | * `cleanup_stale`\n160 | * `cleanup_interval`\n | ^\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:5\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^^^^^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:13\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^^^^^^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:22\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:26\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:29\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^^^^^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:37\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:162:40\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^^^^^^^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:162:48\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:162:67\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:162:68\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:162:69\n |\n160 | * `cleanup_interval`\n161 |\n162 | The current defaults can be fetched by calling `get_default_params`.\n | ^\n163 |\n164 | Threads Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:164:9\n |\n162 | The current defaults can be fetched by calling `get_default_params`.\n163 |\n164 | Threads Limit\n | ^^^^^\n165 | ~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:165:14\n |\n164 | Threads Limit\n165 | ~~~~~~~~~~~~~\n | ^\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:4\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:10\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:14\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:21\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:24\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:32\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:51\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:167:54\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:65\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:167:69\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:167:70\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:167:90\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:167:91\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:167:93\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:102\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:110\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^\n |\n\nE501 Line too long (229 > 120)\n --> README.rst:167:121\n |\n165 | …\n166 | …\n167 | …number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:122\n |\n165 | ~~~~~~~~~~~~~\n166 |\n167 | To limit the number of threads Cachier is allowed to spawn, set the ``CACHIER_MAX_WORKERS`` with the desired number. The default is 8…\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:139\n |\n165 | …\n166 | …\n167 | …HIER_MAX_WORKERS`` with the desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a …\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:142\n |\n165 | …\n166 | …\n167 | …MAX_WORKERS`` with the desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a highe…\n | ^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:149\n |\n165 | …\n166 | …\n167 | …ERS`` with the desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit …\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:157\n |\n165 | …\n166 | …\n167 | … with the desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit expli…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:160\n |\n165 | …\n166 | …\n167 | … the desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:166\n |\n165 | …\n166 | …\n167 | …desired number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:171\n |\n165 | …\n166 | …\n167 | …ed number. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:167:176\n |\n165 | …\n166 | …\n167 | …er. The default is 8, so to enable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^^^^\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:167:188\n |\n165 | …\n166 | …\n167 | …nable Cachier to spawn even more threads, you'll have to set a higher limit explicitly.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `:`, found newline\n --> README.rst:167:230\n |\n165 | …\n166 | …\n167 | … even more threads, you'll have to set a higher limit explicitly.\n | ^\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:170:1\n |\n170 | Global Enable/Disable\n | ^^^^^^\n171 | ---------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:170:8\n |\n170 | Global Enable/Disable\n | ^^^^^^\n171 | ---------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:171:22\n |\n170 | Global Enable/Disable\n171 | ---------------------\n | ^\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:9\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:13\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:16\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:23\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:27\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:34\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:38\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:49\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:52\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:173:60\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:173:76\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:173:77\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:173:79\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:88\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:101\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:173:104\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:173:112\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\nE501 Line too long (128 > 120)\n --> README.rst:173:121\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^^^^^^^^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:173:127\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:173:128\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:173:129\n |\n171 | ---------------------\n172 |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n | ^\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:7\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:17\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:21\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:33\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:42\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:49\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:175:53\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:175:69\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:175:79\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:175:87\n |\n173 | Caching can be turned off across all decorators by calling `disable_caching`, and then re-activated by calling `enable_caching`.\n174 |\n175 | These functions are convenience wrappers around the `caching_enabled` default setting.\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:178:7\n |\n178 | Cache Shelf Life\n | ^^^^^\n179 | ----------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:178:13\n |\n178 | Cache Shelf Life\n | ^^^^\n179 | ----------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:179:17\n |\n178 | Cache Shelf Life\n179 | ----------------\n | ^\n180 |\n181 | Setting Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:181:9\n |\n179 | ----------------\n180 |\n181 | Setting Shelf Life\n | ^^^^^\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:181:15\n |\n179 | ----------------\n180 |\n181 | Setting Shelf Life\n | ^^^^\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:182:19\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n | ^\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:5\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:9\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:13\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:17\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:183:26\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:33\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:39\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:44\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:47\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:54\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:68\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:71\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:73\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:82\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:85\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:95\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:97\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^^^^^^^^^^^^^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:111\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:112\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\nE501 Line too long (164 > 120)\n --> README.rst:183:121\n |\n181 | …\n182 | …\n183 | …tion by providing a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:122\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:123\n |\n181 | Setting Shelf Life\n182 | ~~~~~~~~~~~~~~~~~~\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n | ^\n184 |\n185 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:132\n |\n181 | …\n182 | …\n183 | … of a function by providing a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:183:135\n |\n181 | …\n182 | …\n183 | …a function by providing a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^^^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:139\n |\n181 | …\n182 | …\n183 | …unction by providing a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:140\n |\n181 | …\n182 | …\n183 | …nction by providing a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:152\n |\n181 | …\n182 | …\n183 | …oviding a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:183:153\n |\n181 | …\n182 | …\n183 | …viding a corresponding ``timedelta`` object to the ``stale_after`` parameter:\n | ^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:183:165\n |\n181 | …\n182 | …\n183 | …responding ``timedelta`` object to the ``stale_after`` parameter:\n | ^\n184 | …\n185 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:185:1\n |\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n184 |\n185 | .. code-block:: python\n | ^\n186 |\n187 | import datetime\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:185:2\n |\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n184 |\n185 | .. code-block:: python\n | ^\n186 |\n187 | import datetime\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:185:4\n |\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n184 |\n185 | .. code-block:: python\n | ^^^^^^^^^^\n186 |\n187 | import datetime\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:185:15\n |\n183 | You can set any duration as the shelf life of cached return values of a function by providing a corresponding ``timedelta`` object to…\n184 |\n185 | .. code-block:: python\n | ^\n186 |\n187 | import datetime\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:187:1\n |\n185 | .. code-block:: python\n186 |\n187 | import datetime\n | ^^\n188 |\n189 | @cachier(stale_after=datetime.timedelta(weeks=2))\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:193:1\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:5\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:10\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:12\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:19\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:25\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:34\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:38\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:44\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:63\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:67\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:72\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:75\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:79\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^^^^^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\nE702 Multiple statements on one line (semicolon)\n --> README.rst:193:101\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:193:103\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:193:111\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^^^^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:193:116\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:193:117\n |\n191 | return {'arg1': arg1, 'arg2': arg2}\n192 |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n | ^\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n |\n\nE501 Line too long (254 > 120)\n --> README.rst:193:121\n |\n191 | …\n192 | …\n193 | …``stale_after`` time has since passed, the function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:193:129\n |\n191 | …\n192 | …\n193 | …he time of its calculation is checked; if more than ``stale_after`` time has since passed, the function will be run again for the sa…\n | ^\n194 | …\n195 | …c data source.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:193:130\n |\n191 | …\n192 | …\n193 | …e time of its calculation is checked; if more than ``stale_after`` time has since passed, the function will be run again for the sam…\n | ^\n194 | …\n195 | … data source.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:137\n |\n191 | …\n192 | …\n193 | …f its calculation is checked; if more than ``stale_after`` time has since passed, the function will be run again for the same argume…\n | ^^^\n194 | …\n195 | …urce.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:141\n |\n191 | …\n192 | …\n193 | … calculation is checked; if more than ``stale_after`` time has since passed, the function will be run again for the same arguments a…\n | ^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:147\n |\n191 | …\n192 | …\n193 | …lation is checked; if more than ``stale_after`` time has since passed, the function will be run again for the same arguments and the…\n | ^^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:193:159\n |\n191 | …\n192 | …\n193 | …cked; if more than ``stale_after`` time has since passed, the function will be run again for the same arguments and the new value wi…\n | ^^^^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:193:168\n |\n191 | …\n192 | …\n193 | …f more than ``stale_after`` time has since passed, the function will be run again for the same arguments and the new value will be c…\n | ^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:193:173\n |\n191 | …\n192 | …\n193 | …re than ``stale_after`` time has since passed, the function will be run again for the same arguments and the new value will be cache…\n | ^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:193:176\n |\n191 | …\n192 | …\n193 | …han ``stale_after`` time has since passed, the function will be run again for the same arguments and the new value will be cached an…\n | ^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:193:180\n |\n191 | …\n192 | …\n193 | …`stale_after`` time has since passed, the function will be run again for the same arguments and the new value will be cached and ret…\n | ^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:193:186\n |\n191 | …\n192 | …\n193 | …e_after`` time has since passed, the function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:193:194\n |\n191 | …\n192 | …\n193 | …` time has since passed, the function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:193:199\n |\n191 | …\n192 | …\n193 | …as since passed, the function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^^^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:217\n |\n191 | …\n192 | …\n193 | …, the function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:221\n |\n191 | …\n192 | …\n193 | … function will be run again for the same arguments and the new value will be cached and returned.\n | ^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:227\n |\n191 | …\n192 | …\n193 | …tion will be run again for the same arguments and the new value will be cached and returned.\n | ^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:232\n |\n191 | …\n192 | …\n193 | … will be run again for the same arguments and the new value will be cached and returned.\n | ^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:193:235\n |\n191 | …\n192 | …\n193 | … be run again for the same arguments and the new value will be cached and returned.\n | ^^^^^^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:193:255\n |\n191 | …\n192 | …\n193 | …the same arguments and the new value will be cached and returned.\n | ^\n194 | …\n195 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:195:16\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:195:28\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^^^^^^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:195:41\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:46\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:53\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:56\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:58\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:66\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:195:71\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^^^^^^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:195:78\n |\n193 | Now when a cached value matching the given arguments is found the time of its calculation is checked; if more than ``stale_after`` ti…\n194 |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n | ^\n196 |\n197 | Fuzzy Shelf Life\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:197:7\n |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n196 |\n197 | Fuzzy Shelf Life\n | ^^^^^\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:197:13\n |\n195 | This is useful for lengthy calculations that depend on a dynamic data source.\n196 |\n197 | Fuzzy Shelf Life\n | ^^^^\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:198:17\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n | ^\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:11\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:15\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:19\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:24\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:29\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:38\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:41\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:49\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:51\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^^^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:63\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:68\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:71\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:82\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:84\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:199:90\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:199:102\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found `not`\n --> README.rst:199:108\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:199:117\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^\n200 |\n201 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:199:120\n |\n197 | Fuzzy Shelf Life\n198 | ~~~~~~~~~~~~~~~~\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n | ^^\n200 |\n201 | .. code-block:: python\n |\n\nE501 Line too long (317 > 120)\n --> README.rst:199:121\n |\n197 | …\n198 | …\n199 | … on it if it's not that critical. In that case, you can set ``next_time`` to ``True`` to have your function trigger a recalculation **in a separate thread**, but return the currently cached stale value:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n200 | …\n201 | …\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:199:128\n |\n197 | …\n198 | …\n199 | …if it's not that critical. In that case, you can set ``next_time`` to ``True`` to have your function trigger a recalculation **in a separate thread**, but return the currently cached stale value:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n200 | …\n201 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:201:1\n |\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n200 |\n201 | .. code-block:: python\n | ^\n202 |\n203 | @cachier(next_time=True)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:201:2\n |\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n200 |\n201 | .. code-block:: python\n | ^\n202 |\n203 | @cachier(next_time=True)\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:201:4\n |\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n200 |\n201 | .. code-block:: python\n | ^^^^^^^^^^\n202 |\n203 | @cachier(next_time=True)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:201:15\n |\n199 | Sometimes you may want your function to trigger a calculation when it encounters a stale result, but still not wait on it if it's not…\n200 |\n201 | .. code-block:: python\n | ^\n202 |\n203 | @cachier(next_time=True)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:203:1\n |\n201 | .. code-block:: python\n202 |\n203 | @cachier(next_time=True)\n | ^^\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n |\n\ninvalid-syntax: Expected class, function definition or async function definition after decorator\n --> README.rst:205:1\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:9\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:18\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:24\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:205:29\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:205:39\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^^^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:60\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:70\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:75\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:87\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:205:97\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^^^^^^^^^^^^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:205:110\n |\n203 | @cachier(next_time=True)\n204 |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n | ^\n206 |\n207 | Automatic Cleanup of Stale Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:207:11\n |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n206 |\n207 | Automatic Cleanup of Stale Values\n | ^^^^^^^\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:207:19\n |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n206 |\n207 | Automatic Cleanup of Stale Values\n | ^^\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:207:22\n |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n206 |\n207 | Automatic Cleanup of Stale Values\n | ^^^^^\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:207:28\n |\n205 | Further function calls made while the calculation is being performed will not trigger redundant calculations.\n206 |\n207 | Automatic Cleanup of Stale Values\n | ^^^^^^\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:208:34\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n | ^\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:9\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:10\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:29\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:30\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:35\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:37\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:47\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:52\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:58\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:60\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:71\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:78\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:83\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:96\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:104\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:110\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^\n210 |\n211 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:116\n |\n207 | Automatic Cleanup of Stale Values\n208 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n | ^^^^^^^\n210 |\n211 | .. code-block:: python\n |\n\nE501 Line too long (220 > 120)\n --> README.rst:209:121\n |\n207 | …\n208 | …\n209 | …tale cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:129\n |\n207 | …\n208 | …\n209 | …und thread that periodically removes stale cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` an…\n | ^^^^^^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:138\n |\n207 | …\n208 | …\n209 | …d that periodically removes stale cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and default…\n | ^^^^^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:146\n |\n207 | …\n208 | …\n209 | …eriodically removes stale cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one…\n | ^^^^^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:154\n |\n207 | …\n208 | …\n209 | …cally removes stale cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:173\n |\n207 | …\n208 | …\n209 | …e cache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:176\n |\n207 | …\n208 | …\n209 | …ache entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:177\n |\n207 | …\n208 | …\n209 | …che entries. The interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:194\n |\n207 | …\n208 | …\n209 | …interval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:209:195\n |\n207 | …\n208 | …\n209 | …nterval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:209:197\n |\n207 | …\n208 | …\n209 | …rval between cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:210\n |\n207 | …\n208 | …\n209 | … cleanup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:213\n |\n207 | …\n208 | …\n209 | …anup runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:209:217\n |\n207 | …\n208 | …\n209 | … runs is controlled by ``cleanup_interval`` and defaults to one day.\n | ^^^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:209:221\n |\n207 | …\n208 | …\n209 | …ns is controlled by ``cleanup_interval`` and defaults to one day.\n | ^\n210 | …\n211 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:211:1\n |\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n210 |\n211 | .. code-block:: python\n | ^\n212 |\n213 | @cachier(stale_after=timedelta(seconds=30), cleanup_stale=True)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:211:2\n |\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n210 |\n211 | .. code-block:: python\n | ^\n212 |\n213 | @cachier(stale_after=timedelta(seconds=30), cleanup_stale=True)\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:211:4\n |\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n210 |\n211 | .. code-block:: python\n | ^^^^^^^^^^\n212 |\n213 | @cachier(stale_after=timedelta(seconds=30), cleanup_stale=True)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:211:15\n |\n209 | Setting ``cleanup_stale=True`` on a decorator will spawn a background thread that periodically removes stale cache entries. The inter…\n210 |\n211 | .. code-block:: python\n | ^\n212 |\n213 | @cachier(stale_after=timedelta(seconds=30), cleanup_stale=True)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:213:1\n |\n211 | .. code-block:: python\n212 |\n213 | @cachier(stale_after=timedelta(seconds=30), cleanup_stale=True)\n | ^^\n214 | def compute():\n215 | ...\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:219:1\n |\n219 | Working with unhashable arguments\n | ^\n220 | ---------------------------------\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:219:9\n |\n219 | Working with unhashable arguments\n | ^^^^\n220 | ---------------------------------\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:219:25\n |\n219 | Working with unhashable arguments\n | ^^^^^^^^^\n220 | ---------------------------------\n |\n\ninvalid-syntax: Expected `:`, found newline\n --> README.rst:219:34\n |\n219 | Working with unhashable arguments\n | ^\n220 | ---------------------------------\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:220:1\n |\n219 | Working with unhashable arguments\n220 | ---------------------------------\n | ^\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:220:34\n |\n219 | Working with unhashable arguments\n220 | ---------------------------------\n | ^\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:222:4\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:222:14\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:222:14\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ______________^\n223 | |\n224 | | .. code-block:: python\n | |_____________^\n225 |\n226 | def calculate_hash(args, kwds):\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:25\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:48\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:58\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:61\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:65\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:73\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:82\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:87\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:222:90\n |\n220 | ---------------------------------\n221 |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n | ^^^^^^^^\n223 |\n224 | .. code-block:: python\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:222:111\n |\n220 | …\n221 | …\n222 | …ython's immutable built-in objects, not mutable containers). To get around this limitation the ``hash_func`` parameter of the ``cachier`` decorator can be provided with a callable that gets the args and kwargs from the decorated function and returns a hash key for them.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n223 | …\n224 | …\n |\n\nE501 Line too long (375 > 120)\n --> README.rst:222:121\n |\n220 | …\n221 | …\n222 | …mutable built-in objects, not mutable containers). To get around this limitation the ``hash_func`` parameter of the ``cachier`` decorator can be provided with a callable that gets the args and kwargs from the decorated function and returns a hash key for them.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n223 | …\n224 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:224:2\n |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n223 |\n224 | .. code-block:: python\n | ^\n225 |\n226 | def calculate_hash(args, kwds):\n |\n\ninvalid-syntax: Expected `)`, found `:`\n --> README.rst:224:14\n |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n223 |\n224 | .. code-block:: python\n | ^\n225 |\n226 | def calculate_hash(args, kwds):\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:224:15\n |\n222 | As mentioned above, the positional and keyword arguments to the wrapped function must be hashable (i.e. Python's immutable built-in o…\n223 |\n224 | .. code-block:: python\n | ^\n225 |\n226 | def calculate_hash(args, kwds):\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:226:1\n |\n224 | .. code-block:: python\n225 |\n226 | def calculate_hash(args, kwds):\n | ^^\n227 | key = ... # compute a hash key here based on arguments\n228 | return key\n |\n\ninvalid-syntax: Expected an indented block after function definition\n --> README.rst:231:49\n |\n230 | @cachier(hash_func=calculate_hash)\n231 | def calculate_super_complex_stuff(custom_obj):\n | ^\n232 | # amazing code goes here\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:234:1\n |\n232 | # amazing code goes here\n233 |\n234 | See here for an example:\n | ^\n235 |\n236 | `Question: How to work with unhashable arguments `_\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:234:5\n |\n232 | # amazing code goes here\n233 |\n234 | See here for an example:\n | ^^^^\n235 |\n236 | `Question: How to work with unhashable arguments `_\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:234:10\n |\n232 | # amazing code goes here\n233 |\n234 | See here for an example:\n | ^^^\n235 |\n236 | `Question: How to work with unhashable arguments `_\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:234:17\n |\n232 | # amazing code goes here\n233 |\n234 | See here for an example:\n | ^^^^^^^\n235 |\n236 | `Question: How to work with unhashable arguments `_\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:236:1\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:236:16\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:236:19\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^^^^\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:236:24\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:236:40\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^^^^^^^^^\n |\n\nE701 Multiple statements on one line (colon)\n --> README.rst:236:56\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^\n |\n\ninvalid-syntax: Expected a simple statement\n --> README.rst:236:57\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:236:103\n |\n234 | See here for an example:\n235 |\n236 | `Question: How to work with unhashable arguments `_\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:239:12\n |\n239 | Precaching values\n | ^^^^^^\n240 | ---------------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:240:34\n |\n239 | Precaching values\n240 | ---------------------------------\n | ^\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:4\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:8\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:13\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:16\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:21\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:23\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:29\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:34\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:38\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:44\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:52\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:60\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:64\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:242:75\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:242:90\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:242:94\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:242:97\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:242:102\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^^^^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:242:111\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^\n243 |\n244 | .. code-block:: python\n |\n\nE501 Line too long (136 > 120)\n --> README.rst:242:121\n |\n240 | …\n241 | …\n242 | … underlying function, this can be done with the `precache_value` function.\n | ^^^^^^^^^^^^^^^^\n243 | …\n244 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:242:126\n |\n240 | ---------------------------------\n241 |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n | ^\n243 |\n244 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:242:137\n |\n240 | …\n241 | …\n242 | …ng function, this can be done with the `precache_value` function.\n | ^\n243 | …\n244 | …\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:244:1\n |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n243 |\n244 | .. code-block:: python\n | ^\n245 |\n246 | @cachier()\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:244:2\n |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n243 |\n244 | .. code-block:: python\n | ^\n245 |\n246 | @cachier()\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:244:4\n |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n243 |\n244 | .. code-block:: python\n | ^^^^^^^^^^\n245 |\n246 | @cachier()\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:244:15\n |\n242 | If you want to load a value into the cache without calling the underlying function, this can be done with the `precache_value` functi…\n243 |\n244 | .. code-block:: python\n | ^\n245 |\n246 | @cachier()\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:246:1\n |\n244 | .. code-block:: python\n245 |\n246 | @cachier()\n | ^^\n247 | def add(arg1, arg2):\n248 | return arg1 + arg2\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:256:1\n |\n256 | Per-function call arguments\n | ^\n257 | ---------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:256:14\n |\n256 | Per-function call arguments\n | ^^^^\n257 | ---------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:256:19\n |\n256 | Per-function call arguments\n | ^^^^^^^^^\n257 | ---------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:257:28\n |\n256 | Per-function call arguments\n257 | ---------------------------\n | ^\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:9\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:14\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:22\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:30\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:38\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:55\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:61\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:64\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:68\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:77\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:80\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:86\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:93\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:105\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^^^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:115\n |\n257 | ---------------------------\n258 |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n | ^^^^\n260 |\n261 | **Max Age (max_age)**\n |\n\nE501 Line too long (186 > 120)\n --> README.rst:259:121\n |\n257 | …\n258 | …\n259 | …ther than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:259:130\n |\n257 | …\n258 | …\n259 | …e function it wraps rather than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:259:134\n |\n257 | …\n258 | …\n259 | …unction it wraps rather than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:259:137\n |\n257 | …\n258 | …\n259 | …on it wraps rather than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:259:144\n |\n257 | …\n258 | …\n259 | …wraps rather than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:259:148\n |\n257 | …\n258 | …\n259 | …ather than in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^^^^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:259:158\n |\n257 | …\n258 | …\n259 | …han in the decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:259:164\n |\n257 | …\n258 | …\n259 | …he decorator call, allowing you to modify its behaviour for a specific function call.\n | ^^^^^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:259:173\n |\n257 | …\n258 | …\n259 | …tor call, allowing you to modify its behaviour for a specific function call.\n | ^^^^^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:259:182\n |\n257 | …\n258 | …\n259 | …l, allowing you to modify its behaviour for a specific function call.\n | ^^^^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:259:187\n |\n257 | …\n258 | …\n259 | …llowing you to modify its behaviour for a specific function call.\n | ^\n260 | …\n261 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:261:1\n |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n260 |\n261 | **Max Age (max_age)**\n | ^^\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:261:7\n |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n260 |\n261 | **Max Age (max_age)**\n | ^^^\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:261:22\n |\n259 | Cachier also accepts several keyword arguments in the calls of the function it wraps rather than in the decorator call, allowing you …\n260 |\n261 | **Max Age (max_age)**\n | ^\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:262:34\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n | ^\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:5\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:9\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:17\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:19\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:27\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:35\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:263:39\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:263:45\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:263:52\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:58\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:61\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:63\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:72\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:78\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:84\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:263:88\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:263:96\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:106\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:119\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^\n264 |\n265 | .. code-block:: python\n |\n\nE501 Line too long (321 > 120)\n --> README.rst:263:121\n |\n261 | …\n262 | …\n263 | …If the cached value is older than this threshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:123\n |\n261 | **Max Age (max_age)**\n262 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n | ^^^^^^\n264 |\n265 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:130\n |\n261 | …\n262 | …\n263 | …call basis using the `max_age` keyword argument. If the cached value is older than this threshold, a recalculation is triggered. Thi…\n | ^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:145\n |\n261 | …\n262 | …\n263 | …ng the `max_age` keyword argument. If the cached value is older than this threshold, a recalculation is triggered. This is in additi…\n | ^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:150\n |\n261 | …\n262 | …\n263 | …e `max_age` keyword argument. If the cached value is older than this threshold, a recalculation is triggered. This is in addition to…\n | ^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:155\n |\n261 | …\n262 | …\n263 | …ge` keyword argument. If the cached value is older than this threshold, a recalculation is triggered. This is in addition to the `st…\n | ^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:168\n |\n261 | …\n262 | …\n263 | …ument. If the cached value is older than this threshold, a recalculation is triggered. This is in addition to the `stale_after` para…\n | ^^^^^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `in` that cannot be used here\n --> README.rst:263:204\n |\n261 | …\n262 | …\n263 | …older than this threshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator lev…\n | ^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:207\n |\n261 | …\n262 | …\n263 | …than this threshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; th…\n | ^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:216\n |\n261 | …\n262 | …\n263 | …his threshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; the stri…\n | ^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:219\n |\n261 | …\n262 | …\n263 | …threshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictes…\n | ^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:263:223\n |\n261 | …\n262 | …\n263 | …eshold, a recalculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (…\n | ^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:263:235\n |\n261 | …\n262 | …\n263 | …calculation is triggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) th…\n | ^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:247\n |\n261 | …\n262 | …\n263 | …s triggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is en…\n | ^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:251\n |\n261 | …\n262 | …\n263 | …riggered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enfor…\n | ^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:254\n |\n261 | …\n262 | …\n263 | …ered. This is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:258\n |\n261 | …\n262 | …\n263 | …his is in addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:263:268\n |\n261 | …\n262 | …\n263 | …n addition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^^^\n264 | …\n265 | …\n |\n\nE702 Multiple statements on one line (semicolon)\n --> README.rst:263:273\n |\n261 | …\n262 | …\n263 | …ddition to the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:279\n |\n261 | …\n262 | …\n263 | … the `stale_after` parameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:263:300\n |\n261 | …\n262 | …\n263 | …rameter set at the decorator level; the strictest (smallest) threshold is enforced.\n | ^^^^^^^^^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:263:322\n |\n261 | …\n262 | …\n263 | … decorator level; the strictest (smallest) threshold is enforced.\n | ^\n264 | …\n265 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:265:1\n |\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n264 |\n265 | .. code-block:: python\n | ^\n266 |\n267 | from datetime import timedelta\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:265:2\n |\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n264 |\n265 | .. code-block:: python\n | ^\n266 |\n267 | from datetime import timedelta\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:265:4\n |\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n264 |\n265 | .. code-block:: python\n | ^^^^^^^^^^\n266 |\n267 | from datetime import timedelta\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:265:15\n |\n263 | You can specify a maximum allowed age for a cached value on a per-call basis using the `max_age` keyword argument. If the cached valu…\n264 |\n265 | .. code-block:: python\n | ^\n266 |\n267 | from datetime import timedelta\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:267:1\n |\n265 | .. code-block:: python\n266 |\n267 | from datetime import timedelta\n | ^^\n268 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:277:1\n |\n275 | result = add(1, 2, max_age=timedelta(seconds=10)) # Only use cache if value is <10s old\n276 |\n277 | **How it works:**\n | ^\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:277:7\n |\n275 | result = add(1, 2, max_age=timedelta(seconds=10)) # Only use cache if value is <10s old\n276 |\n277 | **How it works:**\n | ^^\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:277:10\n |\n275 | result = add(1, 2, max_age=timedelta(seconds=10)) # Only use cache if value is <10s old\n276 |\n277 | **How it works:**\n | ^^^^^\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:277:16\n |\n275 | result = add(1, 2, max_age=timedelta(seconds=10)) # Only use cache if value is <10s old\n276 |\n277 | **How it works:**\n | ^^\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:277:18\n |\n275 | result = add(1, 2, max_age=timedelta(seconds=10)) # Only use cache if value is <10s old\n276 |\n277 | **How it works:**\n | ^\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:7\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^^^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:17\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:21\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:25\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^^^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:42\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:50\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:278:53\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:278:65\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `from` that cannot be used here\n --> README.rst:278:68\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:278:73\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:77\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^^^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:278:86\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:278:88\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:278:92\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:278:100\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `from` that cannot be used here\n --> README.rst:278:103\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:278:108\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:278:112\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^^^^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:278:116\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:278:117\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:278:118\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n | ^\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:6\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:10\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:17\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:32\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:37\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:279:42\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^^^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:279:55\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:279:59\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^^^^^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:279:92\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^^^^^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:279:109\n |\n277 | **How it works:**\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n | ^\n280 | - If not, the cached value is returned as usual.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:280:6\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^^^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:280:9\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:280:15\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^^^^^^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:280:22\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^^^^^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:280:40\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:280:49\n |\n278 | - The effective max age threshold is the minimum of `stale_after` (from the decorator) and `max_age` (from the call).\n279 | - If the cached value is older than this threshold, a new calculation is triggered and the cache is updated.\n280 | - If not, the cached value is returned as usual.\n | ^\n281 |\n282 | Entry Size Limit\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:282:7\n |\n280 | - If not, the cached value is returned as usual.\n281 |\n282 | Entry Size Limit\n | ^^^^\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:282:12\n |\n280 | - If not, the cached value is returned as usual.\n281 |\n282 | Entry Size Limit\n | ^^^^^\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:283:17\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n | ^\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:5\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:9\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:17\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:22\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:28\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:284:42\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Expected `import`, found name\n --> README.rst:284:53\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:284:60\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:284:63\n |\n282 | Entry Size Limit\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n | ^^^^^^^^^^\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:285:1\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:285:2\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:285:19\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:285:20\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:25\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:29\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^^^^^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:47\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:54\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:59\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:64\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:285:70\n |\n283 | ~~~~~~~~~~~~~~~~\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n | ^^^\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:10\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:14\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:30\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:36\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^^^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:44\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:47\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^^^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:55\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:62\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:286:65\n |\n284 | You can prevent very large return values from being cached by specifying\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n | ^^^^^\n287 | human readable string like ``\"200MB\"``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:287:7\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^^^^^^^^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:287:16\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^^^^^^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:287:23\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^^^^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:287:28\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:287:29\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:287:37\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:287:38\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:287:39\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:287:40\n |\n285 | ``entry_size_limit`` on the decorator. Values larger than this limit are\n286 | returned but not stored. The limit accepts an integer number of bytes or a\n287 | human readable string like ``\"200MB\"``.\n | ^\n288 |\n289 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:289:1\n |\n287 | human readable string like ``\"200MB\"``.\n288 |\n289 | .. code-block:: python\n | ^\n290 |\n291 | @cachier(entry_size_limit=\"10KB\")\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:289:2\n |\n287 | human readable string like ``\"200MB\"``.\n288 |\n289 | .. code-block:: python\n | ^\n290 |\n291 | @cachier(entry_size_limit=\"10KB\")\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:289:4\n |\n287 | human readable string like ``\"200MB\"``.\n288 |\n289 | .. code-block:: python\n | ^^^^^^^^^^\n290 |\n291 | @cachier(entry_size_limit=\"10KB\")\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:289:15\n |\n287 | human readable string like ``\"200MB\"``.\n288 |\n289 | .. code-block:: python\n | ^\n290 |\n291 | @cachier(entry_size_limit=\"10KB\")\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:291:1\n |\n289 | .. code-block:: python\n290 |\n291 | @cachier(entry_size_limit=\"10KB\")\n | ^^\n292 | def load_data():\n293 | ...\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:295:1\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:295:6\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:295:7\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:295:29\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:295:30\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:295:32\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:42\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:45\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:47\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:52\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:57\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^^^^^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:65\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:295:67\n |\n293 | ...\n294 |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n | ^^^^^\n296 | exceeding the limit, an informative message is printed.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:296:11\n |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n296 | exceeding the limit, an informative message is printed.\n | ^^^\n297 |\n298 | Ignore Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:296:15\n |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n296 | exceeding the limit, an informative message is printed.\n | ^^^^^\n297 |\n298 | Ignore Cache\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:296:25\n |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n296 | exceeding the limit, an informative message is printed.\n | ^^^^^^^^^^^\n297 |\n298 | Ignore Cache\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:296:37\n |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n296 | exceeding the limit, an informative message is printed.\n | ^^^^^^^\n297 |\n298 | Ignore Cache\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:296:56\n |\n295 | When ``cachier__verbose=True`` is passed to a call that returns a value\n296 | exceeding the limit, an informative message is printed.\n | ^\n297 |\n298 | Ignore Cache\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:298:8\n |\n296 | exceeding the limit, an informative message is printed.\n297 |\n298 | Ignore Cache\n | ^^^^^\n299 | ~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:299:13\n |\n298 | Ignore Cache\n299 | ~~~~~~~~~~~~\n | ^\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:5\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:9\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:14\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:15\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:23\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:24\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:33\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:37\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:46\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:301:52\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:301:58\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:301:67\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:76\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:81\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:84\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^^^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:92\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:93\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:118\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:301:119\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^\n302 |\n303 | .. code-block:: python\n |\n\nE501 Line too long (214 > 120)\n --> README.rst:301:121\n |\n299 | …\n300 | …\n301 | …_skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:124\n |\n299 | ~~~~~~~~~~~~\n300 |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n | ^^^\n302 |\n303 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:128\n |\n299 | …\n300 | …\n301 | … function call by passing ``cachier__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the …\n | ^^^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:137\n |\n299 | …\n300 | …\n301 | …on call by passing ``cachier__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new ret…\n | ^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:147\n |\n299 | …\n300 | …\n301 | …passing ``cachier__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:153\n |\n299 | …\n300 | …\n301 | …ng ``cachier__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:158\n |\n299 | …\n300 | …\n301 | …chier__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:166\n |\n299 | …\n300 | …\n301 | …__skip_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:169\n |\n299 | …\n300 | …\n301 | …_cache=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:177\n |\n299 | …\n300 | …\n301 | …=True`` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:301:181\n |\n299 | …\n300 | …\n301 | …` to the function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:301:189\n |\n299 | …\n300 | …\n301 | …he function call. The cache will neither be checked nor updated with the new return value.\n | ^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:301:198\n |\n299 | …\n300 | …\n301 | …on call. The cache will neither be checked nor updated with the new return value.\n | ^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Expected `:`, found `return`\n --> README.rst:301:202\n |\n299 | …\n300 | …\n301 | …ll. The cache will neither be checked nor updated with the new return value.\n | ^^^^^^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:301:215\n |\n299 | …\n300 | …\n301 | …he will neither be checked nor updated with the new return value.\n | ^\n302 | …\n303 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:303:1\n |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n302 |\n303 | .. code-block:: python\n | ^\n304 |\n305 | @cachier()\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:303:2\n |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n302 |\n303 | .. code-block:: python\n | ^\n304 |\n305 | @cachier()\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:303:4\n |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n302 |\n303 | .. code-block:: python\n | ^^^^^^^^^^\n304 |\n305 | @cachier()\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:303:15\n |\n301 | You can have ``cachier`` ignore any existing cache for a specific function call by passing ``cachier__skip_cache=True`` to the functi…\n302 |\n303 | .. code-block:: python\n | ^\n304 |\n305 | @cachier()\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:305:1\n |\n303 | .. code-block:: python\n304 |\n305 | @cachier()\n | ^^\n306 | def sum(first_num, second_num):\n307 | return first_num + second_num\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:312:1\n |\n310 | print(sum(5, 3, cachier__skip_cache=True))\n311 |\n312 | Overwrite Cache\n | ^\n313 | ~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:312:11\n |\n310 | print(sum(5, 3, cachier__skip_cache=True))\n311 |\n312 | Overwrite Cache\n | ^^^^^\n313 | ~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:313:16\n |\n312 | Overwrite Cache\n313 | ~~~~~~~~~~~~~~~\n | ^\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:5\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:9\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:14\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:15\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:23\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:24\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:36\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:39\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:48\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:54\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `if` that cannot be used here\n --> README.rst:315:62\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:65\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:69\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `for` that cannot be used here\n --> README.rst:315:78\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:82\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:84\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:93\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:102\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:107\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:110\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^^^^^^^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:118\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:119\n |\n313 | ~~~~~~~~~~~~~~~\n314 |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n | ^\n316 |\n317 | Verbose Cache Call\n |\n\nE501 Line too long (249 > 120)\n --> README.rst:315:121\n |\n313 | …\n314 | …\n315 | …g ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:149\n |\n313 | …\n314 | …\n315 | …specific function call by passing ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be …\n | ^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:315:150\n |\n313 | …\n314 | …\n315 | …pecific function call by passing ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be u…\n | ^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:155\n |\n313 | …\n314 | …\n315 | …c function call by passing ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated…\n | ^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:159\n |\n313 | …\n314 | …\n315 | …tion call by passing ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with …\n | ^^^^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:168\n |\n313 | …\n314 | …\n315 | …ll by passing ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with the new…\n | ^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:178\n |\n313 | …\n314 | …\n315 | …ng ``cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with the new return val…\n | ^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:184\n |\n313 | …\n314 | …\n315 | …cachier__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:189\n |\n313 | …\n314 | …\n315 | …er__overwrite_cache=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:196\n |\n313 | …\n314 | …\n315 | …rite_cache=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:204\n |\n313 | …\n314 | …\n315 | …ache=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:208\n |\n313 | …\n314 | …\n315 | …=True`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:213\n |\n313 | …\n314 | …\n315 | …e`` to the function call. The cache will not be checked but will be updated with the new return value.\n | ^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:315:216\n |\n313 | …\n314 | …\n315 | … the function call. The cache will not be checked but will be updated with the new return value.\n | ^^^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:315:224\n |\n313 | …\n314 | …\n315 | …unction call. The cache will not be checked but will be updated with the new return value.\n | ^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:315:233\n |\n313 | …\n314 | …\n315 | …all. The cache will not be checked but will be updated with the new return value.\n | ^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Expected `:`, found `return`\n --> README.rst:315:237\n |\n313 | …\n314 | …\n315 | …The cache will not be checked but will be updated with the new return value.\n | ^^^^^^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:315:250\n |\n313 | …\n314 | …\n315 | …ill not be checked but will be updated with the new return value.\n | ^\n316 | …\n317 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:317:9\n |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n316 |\n317 | Verbose Cache Call\n | ^^^^^\n318 | ~~~~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:317:15\n |\n315 | You can have ``cachier`` overwrite an existing cache entry - if one exists - for a specific function call by passing ``cachier__overw…\n316 |\n317 | Verbose Cache Call\n | ^^^^\n318 | ~~~~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:318:19\n |\n317 | Verbose Cache Call\n318 | ~~~~~~~~~~~~~~~~~~\n | ^\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:5\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:9\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:14\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:15\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:23\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:24\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:32\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:36\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:38\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:47\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^^^^^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:59\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:62\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:66\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:72\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:75\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:77\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:86\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:91\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:94\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^^^^^^^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:102\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:103\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\nE501 Line too long (242 > 120)\n --> README.rst:320:121\n |\n318 | …\n319 | …\n320 | …bose=True`` to the function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:125\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:320:126\n |\n318 | ~~~~~~~~~~~~~~~~~~\n319 |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n | ^\n321 |\n322 | Cache `None` Values\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:131\n |\n318 | …\n319 | …\n320 | ogic of a specific call by passing ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a cert…\n | ^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:135\n |\n318 | …\n319 | …\n320 | …f a specific call by passing ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a certain fu…\n | ^^^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:144\n |\n318 | …\n319 | …\n320 | …cific call by passing ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a certain function …\n | ^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:155\n |\n318 | …\n319 | …\n320 | …by passing ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a certain function result is, …\n | ^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:159\n |\n318 | …\n319 | …\n320 | …passing ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a certain function result is, or …\n | ^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:162\n |\n318 | …\n319 | …\n320 | …ng ``cachier__verbose=True`` to the function call. This can be useful if you are not sure why a certain function result is, or is no…\n | ^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected `else`, found name\n --> README.rst:320:176\n |\n318 | …\n319 | …\n320 | …_verbose=True`` to the function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:180\n |\n318 | …\n319 | …\n320 | …bose=True`` to the function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:189\n |\n318 | …\n319 | …\n320 | …`` to the function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:193\n |\n318 | …\n319 | …\n320 | …to the function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:195\n |\n318 | …\n319 | …\n320 | …e function call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:203\n |\n318 | …\n319 | …\n320 | …on call. This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:320:212\n |\n318 | …\n319 | …\n320 | … This can be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^^^^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:320:221\n |\n318 | …\n319 | …\n320 | …an be useful if you are not sure why a certain function result is, or is not, returned.\n | ^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:320:223\n |\n318 | …\n319 | …\n320 | … be useful if you are not sure why a certain function result is, or is not, returned.\n | ^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:320:226\n |\n318 | …\n319 | …\n320 | … useful if you are not sure why a certain function result is, or is not, returned.\n | ^^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:320:232\n |\n318 | …\n319 | …\n320 | …l if you are not sure why a certain function result is, or is not, returned.\n | ^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:320:243\n |\n318 | …\n319 | …\n320 | …e not sure why a certain function result is, or is not, returned.\n | ^\n321 | …\n322 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:322:7\n |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n321 |\n322 | Cache `None` Values\n | ^\n323 | ~~~~~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:322:12\n |\n320 | You can have ``cachier`` print out a detailed explanation of the logic of a specific call by passing ``cachier__verbose=True`` to the…\n321 |\n322 | Cache `None` Values\n | ^\n323 | ~~~~~~~~~~~~~~~~~~~\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:323:20\n |\n322 | Cache `None` Values\n323 | ~~~~~~~~~~~~~~~~~~~\n | ^\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:325:4\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:13\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:14\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:22\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:23\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found `not`\n --> README.rst:325:30\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:325:30\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:40\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:41\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:325:42\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:46\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:47\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:61\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:65\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:74\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:79\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:89\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:325:92\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:100\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:101\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:117\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:325:118\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^\n |\n\nE501 Line too long (140 > 120)\n --> README.rst:325:121\n |\n323 | …\n324 | …\n325 | …override this behaviour by passing ``allow_none=True`` to the function call.\n | ^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:325:123\n |\n323 | ~~~~~~~~~~~~~~~~~~~\n324 |\n325 | By default, ``cachier`` does not cache ``None`` values. You can override this behaviour by passing ``allow_none=True`` to the functio…\n | ^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:325:127\n |\n323 | …\n324 | …\n325 | …override this behaviour by passing ``allow_none=True`` to the function call.\n | ^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:325:136\n |\n323 | …\n324 | …\n325 | …e this behaviour by passing ``allow_none=True`` to the function call.\n | ^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:325:141\n |\n323 | …\n324 | …\n325 | …is behaviour by passing ``allow_none=True`` to the function call.\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:328:9\n |\n328 | Cachier Cores\n | ^^^^^\n329 | =============\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:1\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:3\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:5\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:7\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:9\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:11\n |\n328 | Cachier Cores\n329 | =============\n | ^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:13\n |\n328 | Cachier Cores\n329 | =============\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:329:14\n |\n328 | Cachier Cores\n329 | =============\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:332:8\n |\n332 | Pickle Core\n | ^^^^\n333 | -----------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:333:12\n |\n332 | Pickle Core\n333 | -----------\n | ^\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:335:1\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:14\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:335:22\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:30\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:335:39\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:45\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:55\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:59\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:335:69\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:77\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:88\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:101\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:112\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:116\n |\n333 | -----------\n334 |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n | ^^^^^^^^^^\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n |\n\nE501 Line too long (209 > 120)\n --> README.rst:335:121\n |\n333 | …\n334 | …\n335 | … operations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n336 | …\n337 | …ate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:127\n |\n333 | …\n334 | …\n335 | …ed with no additional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuratio…\n | ^^^^^^^^^\n336 | …\n337 | …on will store its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-spe…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:137\n |\n333 | …\n334 | …\n335 | …h no additional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is n…\n | ^^\n336 | …\n337 | …l store its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:140\n |\n333 | …\n334 | …\n335 | … additional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is neede…\n | ^^^\n336 | …\n337 | …ore its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:144\n |\n333 | …\n334 | …\n335 | …itional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^^^\n336 | …\n337 | …its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:149\n |\n333 | …\n334 | …\n335 | …tup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^^^^^^^^^^^^^\n336 | …\n337 | …in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:335:168\n |\n333 | …\n334 | …\n335 | …erations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^\n336 | …\n337 | … pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Expected `:`, found `async`\n --> README.rst:335:171\n |\n333 | …\n334 | …\n335 | …ons are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^^^^\n336 | …\n337 | …le file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found `-`\n --> README.rst:335:176\n |\n333 | …\n334 | …\n335 | … are internally delegated to the sync implementation, so no async-specific configuration is needed.\n | ^\n336 | …\n337 | …file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:335:186\n |\n333 | …\n334 | …\n335 | …delegated to the sync implementation, so no async-specific configuration is needed.\n | ^^^^^^^^^^^^^\n336 | …\n337 | ….cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:335:210\n |\n333 | …\n334 | …\n335 | …ync implementation, so no async-specific configuration is needed.\n | ^\n336 | …\n337 | …ry. Naturally, this kind of cache is both machine-specific and user-specific.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:337:5\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:337:13\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:337:18\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:337:22\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^^^^^^^^^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:337:40\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:55\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:60\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:69\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:74\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:80\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:84\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:95\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:104\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:111\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^^^^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\nE501 Line too long (221 > 120)\n --> README.rst:337:121\n |\n335 | …tions are internally delegated to the sync implementation, so no async-specific configuration is needed.\n336 | …\n337 | …ckle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n338 | …\n339 | …path to that directory:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:337:123\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:337:124\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:337:126\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:337:127\n |\n335 | **Sync/Async Support:** Both sync and async functions are supported with no additional setup. Async operations are internally delegat…\n336 |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n | ^\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:337:135\n |\n335 | …ith no additional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is…\n336 | …\n337 | …ill store its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specifi…\n | ^\n338 | …\n339 | …he ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:337:136\n |\n335 | …th no additional setup. Async operations are internally delegated to the sync implementation, so no async-specific configuration is …\n336 | …\n337 | …ll store its cache in a separate pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific…\n | ^\n338 | …\n339 | …e ``cache_dir`` parameter with the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:165\n |\n335 | …operations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n336 | …\n337 | …te pickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n | ^^^^\n338 | …\n339 | … the path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:170\n |\n335 | …ations are internally delegated to the sync implementation, so no async-specific configuration is needed.\n336 | …\n337 | …ickle file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n | ^^\n338 | …\n339 | … path to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:173\n |\n335 | …s are internally delegated to the sync implementation, so no async-specific configuration is needed.\n336 | …\n337 | … file in the ``~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n | ^^^^^\n338 | …\n339 | … to that directory:\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:337:187\n |\n335 | …y delegated to the sync implementation, so no async-specific configuration is needed.\n336 | …\n337 | …~/.cachier`` directory. Naturally, this kind of cache is both machine-specific and user-specific.\n | ^^^^^^^\n338 | …\n339 | …ory:\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:337:222\n |\n335 | …tation, so no async-specific configuration is needed.\n336 | …\n337 | …y, this kind of cache is both machine-specific and user-specific.\n | ^\n338 | …\n339 | …\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:339:1\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:5\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:9\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:19\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:20\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:28\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:29\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:34\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:38\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:46\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:56\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:59\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:339:69\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:73\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:74\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:84\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:339:85\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:339:97\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:339:106\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:339:111\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:339:114\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:339:119\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\nE501 Line too long (128 > 120)\n --> README.rst:339:121\n |\n337 | The default core for Cachier is pickle based, meaning each function will store its cache in a separate pickle file in the ``~/.cachie…\n338 |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n | ^^^^^^^^\n340 |\n341 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:341:1\n |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n340 |\n341 | .. code-block:: python\n | ^\n342 |\n343 | @cachier(cache_dir='~/.temp/.cache')\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:341:2\n |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n340 |\n341 | .. code-block:: python\n | ^\n342 |\n343 | @cachier(cache_dir='~/.temp/.cache')\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:341:4\n |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n340 |\n341 | .. code-block:: python\n | ^^^^^^^^^^\n342 |\n343 | @cachier(cache_dir='~/.temp/.cache')\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:341:15\n |\n339 | You can configure ``cachier`` to use another directory by providing the ``cache_dir`` parameter with the path to that directory:\n340 |\n341 | .. code-block:: python\n | ^\n342 |\n343 | @cachier(cache_dir='~/.temp/.cache')\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:343:1\n |\n341 | .. code-block:: python\n342 |\n343 | @cachier(cache_dir='~/.temp/.cache')\n | ^^\n |\n\ninvalid-syntax: Expected class, function definition or async function definition after decorator\n --> README.rst:346:1\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:5\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:9\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:18\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:27\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:40\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `else`, found name\n --> README.rst:346:55\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:60\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:65\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:70\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:75\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:80\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:83\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:93\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:100\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:107\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:119\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^\n347 |\n348 | .. code-block:: python\n |\n\nE501 Line too long (129 > 120)\n --> README.rst:346:121\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:346:122\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^^^^^^^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:346:130\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n | ^\n347 |\n348 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:348:1\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n347 |\n348 | .. code-block:: python\n | ^\n349 |\n350 | @cachier(pickle_reload=False)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:348:2\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n347 |\n348 | .. code-block:: python\n | ^\n349 |\n350 | @cachier(pickle_reload=False)\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:348:4\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n347 |\n348 | .. code-block:: python\n | ^^^^^^^^^^\n349 |\n350 | @cachier(pickle_reload=False)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:348:15\n |\n346 | You can slightly optimise pickle-based caching if you know your code will only be used in a single thread environment by setting:\n347 |\n348 | .. code-block:: python\n | ^\n349 |\n350 | @cachier(pickle_reload=False)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:350:1\n |\n348 | .. code-block:: python\n349 |\n350 | @cachier(pickle_reload=False)\n | ^^\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n |\n\ninvalid-syntax: Expected class, function definition or async function definition after decorator\n --> README.rst:352:1\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:6\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:11\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:19\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:27\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:31\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:37\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:42\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:45\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:50\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:56\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:71\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:78\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:81\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:83\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:352:88\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:352:99\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:110\n |\n350 | @cachier(pickle_reload=False)\n351 |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n | ^^^^^\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n |\n\nE501 Line too long (293 > 120)\n --> README.rst:352:121\n |\n350 | …\n351 | …\n352 | …thread functionality (the code is still thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n353 | …\n354 | …file per argument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:352:123\n |\n350 | …\n351 | …\n352 | …eeding things up a bit, while also nullifying inter-thread functionality (the code is still thread safe, but different threads will …\n | ^^^^^^^^^^^^^\n353 | …\n354 | …ll cause the cache to be stored in several files: A file per argument set, per function. This can help if your per-function cache fi…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:142\n |\n350 | …\n351 | …\n352 | …up a bit, while also nullifying inter-thread functionality (the code is still thread safe, but different threads will have different…\n | ^^^^\n353 | …\n354 | …ache to be stored in several files: A file per argument set, per function. This can help if your per-function cache files become too…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:156\n |\n350 | …\n351 | …\n352 | … also nullifying inter-thread functionality (the code is still thread safe, but different threads will have different versions of th…\n | ^^^^^^\n353 | …\n354 | …ed in several files: A file per argument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:163\n |\n350 | …\n351 | …\n352 | …nullifying inter-thread functionality (the code is still thread safe, but different threads will have different versions of the cach…\n | ^^^^\n353 | …\n354 | …several files: A file per argument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:173\n |\n350 | …\n351 | …\n352 | …ter-thread functionality (the code is still thread safe, but different threads will have different versions of the cache at times, a…\n | ^^^^^^^^^\n353 | …\n354 | …: A file per argument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:183\n |\n350 | …\n351 | …\n352 | …d functionality (the code is still thread safe, but different threads will have different versions of the cache at times, and will s…\n | ^^^^^^^\n353 | …\n354 | …per argument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:191\n |\n350 | …\n351 | …\n352 | …tionality (the code is still thread safe, but different threads will have different versions of the cache at times, and will sometim…\n | ^^^^\n353 | …\n354 | …gument set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:196\n |\n350 | …\n351 | …\n352 | …lity (the code is still thread safe, but different threads will have different versions of the cache at times, and will sometime mak…\n | ^^^^\n353 | …\n354 | …t set, per function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:201\n |\n350 | …\n351 | …\n352 | …e code is still thread safe, but different threads will have different versions of the cache at times, and will sometime make unnece…\n | ^^^^^^^^^\n353 | …\n354 | …er function. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:211\n |\n350 | …\n351 | …\n352 | … still thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary fun…\n | ^^^^^^^^\n353 | …\n354 | …on. This can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:220\n |\n350 | …\n351 | …\n352 | … thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary function …\n | ^^\n353 | …\n354 | …is can help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:223\n |\n350 | …\n351 | …\n352 | …ead safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary function call…\n | ^^^\n353 | …\n354 | …an help if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:227\n |\n350 | …\n351 | …\n352 | …afe, but different threads will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^\n353 | …\n354 | …lp if your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:233\n |\n350 | …\n351 | …\n352 | … but different threads will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^\n353 | …\n354 | …f your per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:236\n |\n350 | …\n351 | …\n352 | …different threads will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^\n353 | …\n354 | …r per-function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found `and`\n --> README.rst:352:243\n |\n350 | …\n351 | …\n352 | …ent threads will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^\n353 | …\n354 | …function cache files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:252\n |\n350 | …\n351 | …\n352 | will have different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^^^^\n353 | …\n354 | …che files become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:261\n |\n350 | …\n351 | …\n352 | …ave different versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^\n353 | …\n354 | …es become too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:266\n |\n350 | …\n351 | …\n352 | …rent versions of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^^^^^^^\n353 | …\n354 | … too large.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:278\n |\n350 | …\n351 | …\n352 | …ons of the cache at times, and will sometime make unnecessary function calls).\n | ^^^^^^^^\n353 | …\n354 | ….\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:352:287\n |\n350 | …\n351 | …\n352 | …he cache at times, and will sometime make unnecessary function calls).\n | ^^^^^\n353 | …\n354 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:352:294\n |\n350 | …\n351 | …\n352 | …che at times, and will sometime make unnecessary function calls).\n | ^\n353 | …\n354 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:9\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:13\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:22\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:31\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:32\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:47\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:48\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:53\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:54\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:59\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:354:60\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:67\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:73\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:77\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:83\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:86\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:89\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:107\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:116\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^^\n355 |\n356 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:121\n |\n352 | This will prevent reading the cache file on each cache read, speeding things up a bit, while also nullifying inter-thread functionali…\n353 |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n | ^^^\n355 |\n356 | .. code-block:: python\n |\n\nE501 Line too long (216 > 120)\n --> README.rst:354:121\n |\n352 | …ifying inter-thread functionality (the code is still thread safe, but different threads will have different versions of the cache at…\n353 | …\n354 | …ral files: A file per argument set, per function. This can help if your per-function cache files become too large.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:125\n |\n352 | …peeding things up a bit, while also nullifying inter-thread functionality (the code is still thread safe, but different threads will…\n353 | …\n354 | …ill cause the cache to be stored in several files: A file per argument set, per function. This can help if your per-function cache f…\n | ^^^^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:354:134\n |\n352 | … things up a bit, while also nullifying inter-thread functionality (the code is still thread safe, but different threads will have d…\n353 | …\n354 | …se the cache to be stored in several files: A file per argument set, per function. This can help if your per-function cache files be…\n | ^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:143\n |\n352 | …a bit, while also nullifying inter-thread functionality (the code is still thread safe, but different threads will have different ve…\n353 | …\n354 | …e to be stored in several files: A file per argument set, per function. This can help if your per-function cache files become too la…\n | ^^^^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:158\n |\n352 | …also nullifying inter-thread functionality (the code is still thread safe, but different threads will have different versions of the…\n353 | …\n354 | …d in several files: A file per argument set, per function. This can help if your per-function cache files become too large.\n | ^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:162\n |\n352 | … nullifying inter-thread functionality (the code is still thread safe, but different threads will have different versions of the cac…\n353 | …\n354 | … several files: A file per argument set, per function. This can help if your per-function cache files become too large.\n | ^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `else`, found name\n --> README.rst:354:175\n |\n352 | …nter-thread functionality (the code is still thread safe, but different threads will have different versions of the cache at times, …\n353 | …\n354 | …s: A file per argument set, per function. This can help if your per-function cache files become too large.\n | ^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:188\n |\n352 | …nctionality (the code is still thread safe, but different threads will have different versions of the cache at times, and will somet…\n353 | …\n354 | …argument set, per function. This can help if your per-function cache files become too large.\n | ^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:194\n |\n352 | …ality (the code is still thread safe, but different threads will have different versions of the cache at times, and will sometime ma…\n353 | …\n354 | …nt set, per function. This can help if your per-function cache files become too large.\n | ^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:200\n |\n352 | …(the code is still thread safe, but different threads will have different versions of the cache at times, and will sometime make unn…\n353 | …\n354 | …, per function. This can help if your per-function cache files become too large.\n | ^^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:207\n |\n352 | …ode is still thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessa…\n353 | …\n354 | …function. This can help if your per-function cache files become too large.\n | ^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:354:211\n |\n352 | …s still thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary fu…\n353 | …\n354 | …ion. This can help if your per-function cache files become too large.\n | ^^^^^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:354:217\n |\n352 | …ill thread safe, but different threads will have different versions of the cache at times, and will sometime make unnecessary functi…\n353 | …\n354 | … This can help if your per-function cache files become too large.\n | ^\n355 | …\n356 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:356:1\n |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n355 |\n356 | .. code-block:: python\n | ^\n357 |\n358 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:356:2\n |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n355 |\n356 | .. code-block:: python\n | ^\n357 |\n358 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:356:4\n |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n355 |\n356 | .. code-block:: python\n | ^^^^^^^^^^\n357 |\n358 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:356:15\n |\n354 | Setting the optional argument ``separate_files`` to ``True`` will cause the cache to be stored in several files: A file per argument …\n355 |\n356 | .. code-block:: python\n | ^\n357 |\n358 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:358:1\n |\n356 | .. code-block:: python\n357 |\n358 | from cachier import cachier\n | ^^\n359 |\n360 | @cachier(separate_files=True)\n |\n\nE501 Line too long (122 > 120)\n --> README.rst:362:121\n |\n360 | @cachier(separate_files=True)\n361 | def foo(arg1, arg2):\n362 | \"\"\"Your function now has a persistent cache mapped by argument values, split across several files, per argument set\"\"\"\n | ^^\n363 | return {'arg1': arg1, 'arg2': arg2}\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:365:1\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:5\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:9\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:13\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:17\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:23\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:33\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:38\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:41\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:45\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:55\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:58\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:64\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:70\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:75\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:78\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:79\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:87\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:88\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:91\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:92\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:365:94\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:365:95\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:103\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:104\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:109\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^^^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:365:116\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^\n366 |\n367 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:121\n |\n363 | return {'arg1': arg1, 'arg2': arg2}\n364 |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n | ^^^^^^^\n366 |\n367 | .. code-block:: python\n |\n\nE501 Line too long (159 > 120)\n --> README.rst:365:121\n |\n363 | …\n364 | …\n365 | …by ``cachier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:365:129\n |\n363 | …\n364 | …\n365 | …iles used by ``cachier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^^^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:133\n |\n363 | …\n364 | …\n365 | …s used by ``cachier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:134\n |\n363 | …\n364 | …\n365 | … used by ``cachier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:148\n |\n363 | …\n364 | …\n365 | …hier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:365:149\n |\n363 | …\n364 | …\n365 | …ier`` (``~/.cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:365:160\n |\n363 | …\n364 | …\n365 | ….cachier`` by default) by calling the ``cache_dpath()`` function:\n | ^\n366 | …\n367 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:367:1\n |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n366 |\n367 | .. code-block:: python\n | ^\n368 |\n369 | >>> foo.cache_dpath()\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:367:2\n |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n366 |\n367 | .. code-block:: python\n | ^\n368 |\n369 | >>> foo.cache_dpath()\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:367:4\n |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n366 |\n367 | .. code-block:: python\n | ^^^^^^^^^^\n368 |\n369 | >>> foo.cache_dpath()\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:367:15\n |\n365 | You can get the fully qualified path to the directory of cache files used by ``cachier`` (``~/.cachier`` by default) by calling the `…\n366 |\n367 | .. code-block:: python\n | ^\n368 |\n369 | >>> foo.cache_dpath()\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:369:1\n |\n367 | .. code-block:: python\n368 |\n369 | >>> foo.cache_dpath()\n | ^^\n370 | \"/home/bigus/.cachier/\"\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:369:3\n |\n367 | .. code-block:: python\n368 |\n369 | >>> foo.cache_dpath()\n | ^^\n370 | \"/home/bigus/.cachier/\"\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:369:5\n |\n367 | .. code-block:: python\n368 |\n369 | >>> foo.cache_dpath()\n | ^\n370 | \"/home/bigus/.cachier/\"\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:370:1\n |\n369 | >>> foo.cache_dpath()\n370 | \"/home/bigus/.cachier/\"\n | ^^^^^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:373:1\n |\n373 | MongoDB Core\n | ^\n374 | ------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:373:9\n |\n373 | MongoDB Core\n | ^^^^\n374 | ------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:374:13\n |\n373 | MongoDB Core\n374 | ------------\n | ^\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:376:1\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:376:14\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:376:22\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:376:30\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:376:39\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:376:45\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^^^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:376:55\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:376:59\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^^^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:376:59\n |\n374 | …\n375 | …\n376 | …c and async functions are supported, but the ``mongetter`` callable type must match the decorated function:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n377 | …\n378 | …ync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:376:74\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:376:78\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:376:79\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:376:89\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:376:90\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found `type`\n --> README.rst:376:101\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:376:106\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found `match`\n --> README.rst:376:111\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:376:117\n |\n374 | ------------\n375 |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n | ^^^\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:376:121\n |\n374 | …\n375 | …\n376 | …upported, but the ``mongetter`` callable type must match the decorated function:\n | ^^^^^^^^^\n377 | …\n378 | …r callable returning a ``pymongo.Collection``).\n |\n\nE501 Line too long (139 > 120)\n --> README.rst:376:121\n |\n374 | …\n375 | …\n376 | …ted, but the ``mongetter`` callable type must match the decorated function:\n | ^^^^^^^^^^^^^^^^^^^\n377 | …\n378 | …lable returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:376:131\n |\n374 | …\n375 | …\n376 | … but the ``mongetter`` callable type must match the decorated function:\n | ^^^^^^^^\n377 | …\n378 | …e returning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:376:140\n |\n374 | …\n375 | …\n376 | …he ``mongetter`` callable type must match the decorated function:\n | ^\n377 | …\n378 | …rning a ``pymongo.Collection``).\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:378:3\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:10\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^^^^^^^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:30\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:32\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:37\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:38\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:48\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:49\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:378:54\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^^^^^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:62\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^^^^^^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:71\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^^^^^^^^^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:378:81\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:83\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:84\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:103\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:378:104\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:378:105\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:378:106\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:378:107\n |\n376 | **Sync/Async Support:** Both sync and async functions are supported, but the ``mongetter`` callable type must match the decorated fun…\n377 |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n | ^\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:379:3\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:379:11\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^^^^^^^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:379:31\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:379:34\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^^^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:379:40\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:379:41\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:379:51\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:379:52\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:379:57\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^^^^^^^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:379:67\n |\n378 | - **Sync functions** require a sync ``mongetter`` (a regular callable returning a ``pymongo.Collection``).\n379 | - **Async functions** require an async ``mongetter`` (a coroutine callable returning an async collection, e.g. via ``motor`` or ``pym…\n | ^^^^^^^^\n380 |\n381 | You can set a MongoDB-based cache by assigning ``mongetter`` with a callable that returns a ``pymongo.Collection`` object with writin…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:379:76\n |\n378 | - **Sync functions** requi |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:450:69\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:450:72\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:450:76\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^^^^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected `,`, found `and`\n --> README.rst:450:103\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:450:113\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^^^^^^^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\nE501 Line too long (122 > 120)\n --> README.rst:450:121\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:450:123\n |\n448 | pip install SQLAlchemy\n449 |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n | ^\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:452:1\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:452:9\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^^^^^^^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:452:9\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:452:35\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^^^^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:452:41\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:452:43\n |\n450 | Cachier supports a generic SQL backend via SQLAlchemy, allowing you to use SQLite, PostgreSQL, MySQL, and other databases.\n451 |\n452 | **Usage Example (SQLite in-memory sync):**\n | ^\n453 |\n454 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:454:1\n |\n452 | **Usage Example (SQLite in-memory sync):**\n453 |\n454 | .. code-block:: python\n | ^\n455 |\n456 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:454:2\n |\n452 | **Usage Example (SQLite in-memory sync):**\n453 |\n454 | .. code-block:: python\n | ^\n455 |\n456 | from cachier import cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:454:4\n |\n452 | **Usage Example (SQLite in-memory sync):**\n453 |\n454 | .. code-block:: python\n | ^^^^^^^^^^\n455 |\n456 | from cachier import cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:454:15\n |\n452 | **Usage Example (SQLite in-memory sync):**\n453 |\n454 | .. code-block:: python\n | ^\n455 |\n456 | from cachier import cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:456:1\n |\n454 | .. code-block:: python\n455 |\n456 | from cachier import cachier\n | ^^^^\n457 |\n458 | @cachier(backend=\"sql\", sql_engine=\"sqlite:///:memory:\")\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:462:1\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:462:9\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^^^^^^^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:462:9\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^^^^^^^^^^^^^^^^^^^^^^^^^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:462:29\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^^^^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:462:35\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:462:37\n |\n460 | return x * 2\n461 |\n462 | **Usage Example (PostgreSQL sync):**\n | ^\n463 |\n464 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:464:1\n |\n462 | **Usage Example (PostgreSQL sync):**\n463 |\n464 | .. code-block:: python\n | ^\n465 |\n466 | @cachier(backend=\"sql\", sql_engine=\"postgresql+psycopg://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:464:2\n |\n462 | **Usage Example (PostgreSQL sync):**\n463 |\n464 | .. code-block:: python\n | ^\n465 |\n466 | @cachier(backend=\"sql\", sql_engine=\"postgresql+psycopg://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:464:4\n |\n462 | **Usage Example (PostgreSQL sync):**\n463 |\n464 | .. code-block:: python\n | ^^^^^^^^^^\n465 |\n466 | @cachier(backend=\"sql\", sql_engine=\"postgresql+psycopg://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:464:15\n |\n462 | **Usage Example (PostgreSQL sync):**\n463 |\n464 | .. code-block:: python\n | ^\n465 |\n466 | @cachier(backend=\"sql\", sql_engine=\"postgresql+psycopg://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:466:1\n |\n464 | .. code-block:: python\n465 |\n466 | @cachier(backend=\"sql\", sql_engine=\"postgresql+psycopg://user:pass@localhost/dbname\")\n | ^^^^\n467 | def my_func(x):\n468 | return x * 2\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:470:1\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:470:9\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^^^^^^^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:470:9\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `for`, found `)`\n --> README.rst:470:34\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:470:36\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:470:38\n |\n468 | return x * 2\n469 |\n470 | **Usage Example (PostgreSQL async):**\n | ^\n471 |\n472 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:472:1\n |\n470 | **Usage Example (PostgreSQL async):**\n471 |\n472 | .. code-block:: python\n | ^\n473 |\n474 | import asyncio\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:472:2\n |\n470 | **Usage Example (PostgreSQL async):**\n471 |\n472 | .. code-block:: python\n | ^\n473 |\n474 | import asyncio\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:472:4\n |\n470 | **Usage Example (PostgreSQL async):**\n471 |\n472 | .. code-block:: python\n | ^^^^^^^^^^\n473 |\n474 | import asyncio\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:472:15\n |\n470 | **Usage Example (PostgreSQL async):**\n471 |\n472 | .. code-block:: python\n | ^\n473 |\n474 | import asyncio\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:474:1\n |\n472 | .. code-block:: python\n473 |\n474 | import asyncio\n | ^^^^\n475 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:482:1\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:482:9\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^^^^^^^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:482:9\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^^^^^^^^^^^^^^^^^^^^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:482:24\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^^^^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:482:30\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:482:32\n |\n480 | return x * 2\n481 |\n482 | **Usage Example (MySQL sync):**\n | ^\n483 |\n484 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:484:1\n |\n482 | **Usage Example (MySQL sync):**\n483 |\n484 | .. code-block:: python\n | ^\n485 |\n486 | @cachier(backend=\"sql\", sql_engine=\"mysql+pymysql://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:484:2\n |\n482 | **Usage Example (MySQL sync):**\n483 |\n484 | .. code-block:: python\n | ^\n485 |\n486 | @cachier(backend=\"sql\", sql_engine=\"mysql+pymysql://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:484:4\n |\n482 | **Usage Example (MySQL sync):**\n483 |\n484 | .. code-block:: python\n | ^^^^^^^^^^\n485 |\n486 | @cachier(backend=\"sql\", sql_engine=\"mysql+pymysql://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:484:15\n |\n482 | **Usage Example (MySQL sync):**\n483 |\n484 | .. code-block:: python\n | ^\n485 |\n486 | @cachier(backend=\"sql\", sql_engine=\"mysql+pymysql://user:pass@localhost/dbname\")\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:486:1\n |\n484 | .. code-block:: python\n485 |\n486 | @cachier(backend=\"sql\", sql_engine=\"mysql+pymysql://user:pass@localhost/dbname\")\n | ^^^^\n487 | def my_func(x):\n488 | return x * 2\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:490:1\n |\n488 | return x * 2\n489 |\n490 | Redis Core\n | ^\n491 | ----------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:490:7\n |\n488 | return x * 2\n489 |\n490 | Redis Core\n | ^^^^\n491 | ----------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:491:11\n |\n490 | Redis Core\n491 | ----------\n | ^\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:493:1\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:493:14\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:493:22\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:493:30\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:493:39\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:493:45\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^^^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:493:55\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:493:59\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^^^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:493:59\n |\n491 | …\n492 | …\n493 | …and async functions are supported, but the ``redis_client`` callable type must match the decorated function:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n494 | …\n495 | …c ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:493:74\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:493:78\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:493:79\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:493:92\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:493:93\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found `type`\n --> README.rst:493:104\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:493:109\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found `match`\n --> README.rst:493:114\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:493:120\n |\n491 | ----------\n492 |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n | ^^^\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n |\n\nE501 Line too long (142 > 120)\n --> README.rst:493:121\n |\n491 | …\n492 | …\n493 | …ed, but the ``redis_client`` callable type must match the decorated function:\n | ^^^^^^^^^^^^^^^^^^^^^^\n494 | …\n495 | …ync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:493:124\n |\n491 | …\n492 | …\n493 | …orted, but the ``redis_client`` callable type must match the decorated function:\n | ^^^^^^^^^\n494 | …\n495 | …a sync callable returning one.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:493:134\n |\n491 | …\n492 | …\n493 | …t the ``redis_client`` callable type must match the decorated function:\n | ^^^^^^^^\n494 | …\n495 | …llable returning one.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:493:143\n |\n491 | …\n492 | …\n493 | …``redis_client`` callable type must match the decorated function:\n | ^\n494 | …\n495 | … returning one.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:495:3\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:10\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^^^^^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:30\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:32\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:495:37\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:495:38\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:495:50\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:495:51\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:65\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:70\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^^^^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:79\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^^^^^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:495:89\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^^^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:495:93\n |\n493 | **Sync/Async Support:** Both sync and async functions are supported, but the ``redis_client`` callable type must match the decorated …\n494 |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n | ^\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:496:3\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:11\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:31\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:496:34\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:496:40\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:49\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:59\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:61\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:62\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:82\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:83\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:101\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:103\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:108\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:117\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:120\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\nE501 Line too long (158 > 120)\n --> README.rst:496:121\n |\n495 | …able returning one.\n496 | …io.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n497 | …\n498 | …s not installed by default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:496:123\n |\n495 | - **Sync functions** require a sync ``redis.Redis`` client or a sync callable returning one.\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n | ^^^^^\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:496:129\n |\n495 | …nc callable returning one.\n496 | …s.asyncio.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^^^\n497 | …\n498 | …d. It is not installed by default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:496:138\n |\n495 | …ble returning one.\n496 | …o.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^\n497 | …\n498 | … not installed by default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:145\n |\n495 | …eturning one.\n496 | …is`` client. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | …installed by default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:146\n |\n495 | …turning one.\n496 | …s`` client. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | …nstalled by default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:156\n |\n495 | …e.\n496 | …. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | …y default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:496:157\n |\n495 | ….\n496 | … Passing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | … default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:496:158\n |\n495 | …\n496 | …Passing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | …default with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:496:159\n |\n495 | …\n496 | …assing a sync callable to an async function raises ``TypeError``.\n | ^\n497 | …\n498 | …efault with cachier. To use the Redis backend, run::\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:498:1\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:498:8\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:15\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:21\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:26\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:35\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:39\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:45\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:53\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:56\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:59\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:90\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:498:93\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:498:101\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:498:118\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^\n499 |\n500 | pip install redis\n |\n\nE501 Line too long (145 > 120)\n --> README.rst:498:121\n |\n496 | ….asyncio.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n497 | …\n498 | …. It is not installed by default with cachier. To use the Redis backend, run::\n | ^^^^^^^^^^^^^^^^^^^^^^^^^\n499 | …\n500 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:498:122\n |\n496 | - **Async functions** require an async callable returning a ``redis.asyncio.Redis`` client. Passing a sync callable to an async funct…\n497 |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n | ^^^\n499 |\n500 | pip install redis\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:498:126\n |\n496 | …redis.asyncio.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n497 | …\n498 | …alled. It is not installed by default with cachier. To use the Redis backend, run::\n | ^^^^^\n499 | …\n500 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:498:132\n |\n496 | …syncio.Redis`` client. Passing a sync callable to an async function raises ``TypeError``.\n497 | …\n498 | …It is not installed by default with cachier. To use the Redis backend, run::\n | ^^^^^^^\n499 | …\n500 | …\n |\n\ninvalid-syntax: Expected a simple statement\n --> README.rst:498:145\n |\n496 | …is`` client. Passing a sync callable to an async function raises ``TypeError``.\n497 | …\n498 | …installed by default with cachier. To use the Redis backend, run::\n | ^\n499 | …\n500 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:498:146\n |\n496 | …s`` client. Passing a sync callable to an async function raises ``TypeError``.\n497 | …\n498 | …nstalled by default with cachier. To use the Redis backend, run::\n | ^\n499 | …\n500 | …\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:500:1\n |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n499 |\n500 | pip install redis\n | ^^^^\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:500:9\n |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n499 |\n500 | pip install redis\n | ^^^^^^^\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:500:17\n |\n498 | **Note:** The Redis core requires the redis package to be installed. It is not installed by default with cachier. To use the Redis ba…\n499 |\n500 | pip install redis\n | ^^^^^\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:502:1\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:502:9\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:502:18\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:502:30\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:502:38\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Invalid assignment target\n --> README.rst:502:42\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:502:59\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:502:76\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:502:85\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:502:100\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:502:108\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\nE501 Line too long (133 > 120)\n --> README.rst:502:121\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:502:122\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^^^^^^^^^^^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:502:134\n |\n500 | pip install redis\n501 |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n | ^\n503 |\n504 | **Usage Example (Local Redis):**\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:504:1\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:504:9\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^^^^^^^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:504:9\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^^^^^^^^^^^^^^^^^^^^^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:504:24\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^^^^^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:504:31\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:504:33\n |\n502 | Cachier supports Redis-based caching for high-performance scenarios. Redis provides fast in-memory storage with optional persistence.\n503 |\n504 | **Usage Example (Local Redis):**\n | ^\n505 |\n506 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:506:1\n |\n504 | **Usage Example (Local Redis):**\n505 |\n506 | .. code-block:: python\n | ^\n507 |\n508 | import redis\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:506:2\n |\n504 | **Usage Example (Local Redis):**\n505 |\n506 | .. code-block:: python\n | ^\n507 |\n508 | import redis\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:506:4\n |\n504 | **Usage Example (Local Redis):**\n505 |\n506 | .. code-block:: python\n | ^^^^^^^^^^\n507 |\n508 | import redis\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:506:15\n |\n504 | **Usage Example (Local Redis):**\n505 |\n506 | .. code-block:: python\n | ^\n507 |\n508 | import redis\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:508:1\n |\n506 | .. code-block:: python\n507 |\n508 | import redis\n | ^^^^\n509 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:518:1\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:518:9\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^^^^^^^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `)`, found `with`\n --> README.rst:518:24\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^^^^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:518:36\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^^^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:518:40\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^^^^^^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found `)`\n --> README.rst:518:46\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:518:48\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:518:50\n |\n516 | return x * 2\n517 |\n518 | **Usage Example (Redis with custom key prefix):**\n | ^\n519 |\n520 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:520:1\n |\n518 | **Usage Example (Redis with custom key prefix):**\n519 |\n520 | .. code-block:: python\n | ^\n521 |\n522 | import redis\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:520:2\n |\n518 | **Usage Example (Redis with custom key prefix):**\n519 |\n520 | .. code-block:: python\n | ^\n521 |\n522 | import redis\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:520:4\n |\n518 | **Usage Example (Redis with custom key prefix):**\n519 |\n520 | .. code-block:: python\n | ^^^^^^^^^^\n521 |\n522 | import redis\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:520:15\n |\n518 | **Usage Example (Redis with custom key prefix):**\n519 |\n520 | .. code-block:: python\n | ^\n521 |\n522 | import redis\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:522:1\n |\n520 | .. code-block:: python\n521 |\n522 | import redis\n | ^^^^\n523 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:531:1\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:531:9\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^^^^^^^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `)`, found `with`\n --> README.rst:531:24\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^^^^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:531:38\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^^^^^^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found `)`\n --> README.rst:531:44\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:531:46\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:531:48\n |\n529 | return x * 2\n530 |\n531 | **Usage Example (Redis with callable client):**\n | ^\n532 |\n533 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:533:1\n |\n531 | **Usage Example (Redis with callable client):**\n532 |\n533 | .. code-block:: python\n | ^\n534 |\n535 | import redis\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:533:2\n |\n531 | **Usage Example (Redis with callable client):**\n532 |\n533 | .. code-block:: python\n | ^\n534 |\n535 | import redis\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:533:4\n |\n531 | **Usage Example (Redis with callable client):**\n532 |\n533 | .. code-block:: python\n | ^^^^^^^^^^\n534 |\n535 | import redis\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:533:15\n |\n531 | **Usage Example (Redis with callable client):**\n532 |\n533 | .. code-block:: python\n | ^\n534 |\n535 | import redis\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:535:1\n |\n533 | .. code-block:: python\n534 |\n535 | import redis\n | ^^^^\n536 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:545:1\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:545:9\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:545:24\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:545:30\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `)`, found `with`\n --> README.rst:545:37\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected the start of an expression after `with` keyword\n --> README.rst:545:42\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:545:48\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^^^^^^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:545:56\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:545:57\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:545:58\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:545:60\n |\n543 | return x * 2\n544 |\n545 | **Usage Example (Async Redis client with async function):**\n | ^\n546 |\n547 | .. code-block:: python\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:547:1\n |\n545 | **Usage Example (Async Redis client with async function):**\n546 |\n547 | .. code-block:: python\n | ^\n548 |\n549 | import asyncio\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:547:2\n |\n545 | **Usage Example (Async Redis client with async function):**\n546 |\n547 | .. code-block:: python\n | ^\n548 |\n549 | import asyncio\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:547:4\n |\n545 | **Usage Example (Async Redis client with async function):**\n546 |\n547 | .. code-block:: python\n | ^^^^^^^^^^\n548 |\n549 | import asyncio\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:547:15\n |\n545 | **Usage Example (Async Redis client with async function):**\n546 |\n547 | .. code-block:: python\n | ^\n548 |\n549 | import asyncio\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:549:1\n |\n547 | .. code-block:: python\n548 |\n549 | import asyncio\n | ^^^^\n550 | import redis.asyncio as redis\n551 | from cachier import cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:568:1\n |\n566 | asyncio.run(main())\n567 |\n568 | **Configuration Options:**\n | ^\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:568:17\n |\n566 | asyncio.run(main())\n567 |\n568 | **Configuration Options:**\n | ^^^^^^^\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:568:25\n |\n566 | asyncio.run(main())\n567 |\n568 | **Configuration Options:**\n | ^^\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:568:27\n |\n566 | asyncio.run(main())\n567 |\n568 | **Configuration Options:**\n | ^\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:570:3\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:570:4\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:570:15\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:570:16\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:570:17\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:570:30\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^^^^^^^^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:570:41\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^^^^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected `,`, found `or`\n --> README.rst:570:57\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:570:69\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^^^^^^^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:570:79\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:570:82\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^^^^^^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:570:89\n |\n568 | **Configuration Options:**\n569 |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n | ^\n571 | - All other standard cachier options are supported.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:7\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:13\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^^^^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:22\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^^^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:30\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^^^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:38\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:571:42\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^^^^^^^^^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:571:52\n |\n570 | - ``sql_engine``: SQLAlchemy connection string, Engine, or callable returning an Engine.\n571 | - All other standard cachier options are supported.\n | ^\n572 |\n573 | **Table Schema:**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:573:1\n |\n571 | - All other standard cachier options are supported.\n572 |\n573 | **Table Schema:**\n | ^^\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:573:9\n |\n571 | - All other standard cachier options are supported.\n572 |\n573 | **Table Schema:**\n | ^^^^^^\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:573:16\n |\n571 | - All other standard cachier options are supported.\n572 |\n573 | **Table Schema:**\n | ^^\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:573:18\n |\n571 | - All other standard cachier options are supported.\n572 |\n573 | **Table Schema:**\n | ^\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:575:3\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:575:4\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:575:16\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:575:17\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:575:18\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:575:27\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^^^^^^^^^^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:575:38\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^^^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:575:46\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^^^^^^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:575:53\n |\n573 | **Table Schema:**\n574 |\n575 | - ``function_id``: Unique identifier for the cached function\n | ^^^^^^^^\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:576:3\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:576:4\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:576:8\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:576:9\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:576:10\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:576:18\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n | ^^^\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:577:3\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:577:4\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:577:10\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:577:11\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:577:12\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:577:22\n |\n575 | - ``function_id``: Unique identifier for the cached function\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n | ^^^^^^\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:578:3\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:578:4\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:578:14\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:578:15\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:578:16\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:578:27\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:578:30\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^^^^^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:578:36\n |\n576 | - ``key``: Cache key\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n | ^^^^^\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:579:3\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:579:4\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:579:10\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:579:11\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:579:12\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:579:23\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:579:32\n |\n577 | - ``value``: Pickled result\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n | ^^^^^\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:580:3\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:580:4\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:580:15\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:580:16\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:580:17\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:580:28\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:580:37\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^^^^^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:580:43\n |\n578 | - ``timestamp``: Datetime of cache entry\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n | ^^^^^^^^^^\n581 | - ``completed``: Boolean, is value calculation completed\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:581:3\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:581:4\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:581:14\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:581:15\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:581:16\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:581:27\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:581:36\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^^^^^^^^^^^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:581:48\n |\n579 | - ``stale``: Boolean, is value stale\n580 | - ``processing``: Boolean, is value being calculated\n581 | - ``completed``: Boolean, is value calculation completed\n | ^^^^^^^^^\n582 |\n583 | **S3 Sync/Async Support:**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:583:1\n |\n581 | - ``completed``: Boolean, is value calculation completed\n582 |\n583 | **S3 Sync/Async Support:**\n | ^^\n584 |\n585 | - Sync functions use direct boto3 calls.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:583:6\n |\n581 | - ``completed``: Boolean, is value calculation completed\n582 |\n583 | **S3 Sync/Async Support:**\n | ^^^^\n584 |\n585 | - Sync functions use direct boto3 calls.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:583:17\n |\n581 | - ``completed``: Boolean, is value calculation completed\n582 |\n583 | **S3 Sync/Async Support:**\n | ^^^^^^^\n584 |\n585 | - Sync functions use direct boto3 calls.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:583:25\n |\n581 | - ``completed``: Boolean, is value calculation completed\n582 |\n583 | **S3 Sync/Async Support:**\n | ^^\n584 |\n585 | - Sync functions use direct boto3 calls.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:583:27\n |\n581 | - ``completed``: Boolean, is value calculation completed\n582 |\n583 | **S3 Sync/Async Support:**\n | ^\n584 |\n585 | - Sync functions use direct boto3 calls.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:585:8\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^^^^^^^^^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:585:18\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^^^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:585:22\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^^^^^^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:585:29\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^^^^^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:585:35\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^^^^^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:585:41\n |\n583 | **S3 Sync/Async Support:**\n584 |\n585 | - Sync functions use direct boto3 calls.\n | ^\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:9\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^^^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:19\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:23\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^^^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:33\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:37\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:54\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:59\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:586:65\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n | ^^^^^\n587 | (delegated mode), not a native async client.\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:587:1\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:587:14\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^^^^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:587:18\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:587:19\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:587:27\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^^^^^^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:587:34\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^^^^^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:587:40\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^^^^^^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:587:47\n |\n585 | - Sync functions use direct boto3 calls.\n586 | - Async functions are supported via thread-offloaded sync boto3 calls\n587 | (delegated mode), not a native async client.\n | ^\n588 |\n589 | **Limitations & Notes:**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:589:1\n |\n587 | (delegated mode), not a native async client.\n588 |\n589 | **Limitations & Notes:**\n | ^\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:589:23\n |\n587 | (delegated mode), not a native async client.\n588 |\n589 | **Limitations & Notes:**\n | ^^\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:589:25\n |\n587 | (delegated mode), not a native async client.\n588 |\n589 | **Limitations & Notes:**\n | ^\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:591:12\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^^^^^^^^^^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Expected `)`, found `with`\n --> README.rst:591:32\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^^^^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:591:37\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:591:38\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:591:43\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^^^^^^^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:591:51\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^^^^^^^^^^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:591:61\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:591:62\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:591:63\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:591:64\n |\n589 | **Limitations & Notes:**\n590 |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n | ^\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:592:7\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^^^^^^^^^^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:592:7\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:592:23\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:592:25\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^^^^^^^^^^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:592:36\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^^^^^^^^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:592:50\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:592:51\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected `)`, found `:`\n --> README.rst:592:52\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:592:59\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:592:60\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:592:61\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:592:62\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:592:63\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n | ^\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:593:18\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n | ^^^^^^\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:593:36\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n | ^^^\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:593:40\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n | ^^^^^^^^^^^^\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:593:67\n |\n591 | - Requires SQLAlchemy (install with ``pip install SQLAlchemy``)\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n | ^^^^^\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:9\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^^^^^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:23\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:28\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:29\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:36\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:37\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:594:38\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:594:40\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:594:50\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:53\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:60\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:66\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:74\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:84\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:89\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:96\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^^^^^^^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\ninvalid-syntax: Expected `else`, found name\n --> README.rst:594:119\n |\n592 | - For production, use a persistent database (not ``:memory:``)\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n | ^^^^^\n595 | - For best performance, ensure your DB supports row-level locking\n |\n\nE501 Line too long (269 > 120)\n --> README.rst:594:121\n |\n592 | …\n593 | …\n594 | …he cache database is compromised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if security is a concern.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:125\n |\n592 | …\n593 | …vel locks\n594 | …an execute arbitrary code during deserialization if the cache database is compromised. Ensure the cache is stored securely and consi…\n | ^^^^^^^^\n595 | …ing\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:157\n |\n592 | …\n593 | …\n594 | …ng deserialization if the cache database is compromised. Ensure the cache is stored securely and consider using safer serialization …\n | ^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:161\n |\n592 | …\n593 | …\n594 | …serialization if the cache database is compromised. Ensure the cache is stored securely and consider using safer serialization metho…\n | ^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:177\n |\n592 | …\n593 | …\n594 | …the cache database is compromised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if…\n | ^^^^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:199\n |\n592 | …\n593 | …\n594 | … compromised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if security is a concer…\n | ^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:205\n |\n592 | …\n593 | …\n594 | …omised. Ensure the cache is stored securely and consider using safer serialization methods like `json` if security is a concern.\n | ^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:211\n |\n592 | …\n593 | …\n594 | …sure the cache is stored securely and consider using safer serialization methods like `json` if security is a concern.\n | ^^^^^^^^^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:225\n |\n592 | …\n593 | …\n594 | …che is stored securely and consider using safer serialization methods like `json` if security is a concern.\n | ^^^^^^^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:594:233\n |\n592 | …\n593 | …\n594 | … stored securely and consider using safer serialization methods like `json` if security is a concern.\n | ^^^^\n595 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:238\n |\n592 | …\n593 | …\n594 | …red securely and consider using safer serialization methods like `json` if security is a concern.\n | ^\n595 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:594:243\n |\n592 | …\n593 | …\n594 | …ecurely and consider using safer serialization methods like `json` if security is a concern.\n | ^\n595 | …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:594:262\n |\n592 | …\n593 | …\n594 | …sing safer serialization methods like `json` if security is a concern.\n | ^^^^^^^\n595 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:594:270\n |\n592 | …\n593 | …\n594 | …safer serialization methods like `json` if security is a concern.\n | ^\n595 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:595:7\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:595:12\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:595:32\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:595:37\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:595:40\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:595:49\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:595:59\n |\n593 | - Thread/process safety is handled via transactions and row-level locks\n594 | - Value serialization uses ``pickle``. **Warning:** `pickle` can execute arbitrary code during deserialization if the cache database …\n595 | - For best performance, ensure your DB supports row-level locking\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:598:6\n |\n598 | Core Sync/Async Compatibility\n | ^^^^\n599 | ------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:598:17\n |\n598 | Core Sync/Async Compatibility\n | ^^^^^^^^^^^^^\n599 | ------------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:599:31\n |\n598 | Core Sync/Async Compatibility\n599 | ------------------------------\n | ^\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:5\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:11\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:17\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:28\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:601:37\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:43\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:52\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:60\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:67\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:71\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:601:79\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^^^^^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:601:85\n |\n599 | ------------------------------\n600 |\n601 | The table below summarises sync and async function support across all cachier cores.\n | ^\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:7\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:602:14\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:602:33\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:602:39\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^^^^^^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:50\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:53\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:57\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:60\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:64\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:602:69\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n | ^^^^^^^^^^^^^^\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:603:5\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:603:11\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:603:19\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:603:25\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:603:43\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:603:44\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:603:52\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:603:59\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:603:75\n |\n601 | The table below summarises sync and async function support across all cachier cores.\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n | ^^^^^^^^^\n604 | async drivers and require the client or engine type to match the decorated function.\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:604:7\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:27\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:31\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:48\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:53\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:56\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Cannot use `match` statement on Python 3.9 (syntax was added in Python 3.10)\n --> README.rst:604:56\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:604:66\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:604:76\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^^^^^^^^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:604:85\n |\n602 | Cores marked as *delegated* run async operations on top of the sync implementation\n603 | (no event loop or async driver is required). Cores marked as *native* use dedicated\n604 | async drivers and require the client or engine type to match the decorated function.\n | ^\n605 |\n606 | .. list-table::\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:606:1\n |\n604 | async drivers and require the client or engine type to match the decorated function.\n605 |\n606 | .. list-table::\n | ^\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:606:2\n |\n604 | async drivers and require the client or engine type to match the decorated function.\n605 |\n606 | .. list-table::\n | ^\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:606:4\n |\n604 | async drivers and require the client or engine type to match the decorated function.\n605 |\n606 | .. list-table::\n | ^^^^^^^^^^\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:606:15\n |\n604 | async drivers and require the client or engine type to match the decorated function.\n605 |\n606 | .. list-table::\n | ^\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:606:16\n |\n604 | async drivers and require the client or engine type to match the decorated function.\n605 |\n606 | .. list-table::\n | ^\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:607:1\n |\n606 | .. list-table::\n607 | :header-rows: 1\n | ^^^\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:607:4\n |\n606 | .. list-table::\n607 | :header-rows: 1\n | ^\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:607:5\n |\n606 | .. list-table::\n607 | :header-rows: 1\n | ^^^^^^^^^^^\n608 | :widths: 15 12 12 50\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:608:4\n |\n606 | .. list-table::\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n | ^\n609 |\n610 | * - Core\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:608:16\n |\n606 | .. list-table::\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n | ^^\n609 |\n610 | * - Core\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:608:19\n |\n606 | .. list-table::\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n | ^^\n609 |\n610 | * - Core\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:608:22\n |\n606 | .. list-table::\n607 | :header-rows: 1\n608 | :widths: 15 12 12 50\n | ^^\n609 |\n610 | * - Core\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:611:1\n |\n610 | * - Core\n611 | - Sync\n | ^^^^^\n612 | - Async\n613 | - Constraint\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:614:4\n |\n612 | - Async\n613 | - Constraint\n614 | * - **Pickle**\n | ^\n615 | - Yes\n616 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:614:8\n |\n612 | - Async\n613 | - Constraint\n614 | * - **Pickle**\n | ^^\n615 | - Yes\n616 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:614:18\n |\n612 | - Async\n613 | - Constraint\n614 | * - **Pickle**\n | ^\n615 | - Yes\n616 | - Yes (delegated)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:615:1\n |\n613 | - Constraint\n614 | * - **Pickle**\n615 | - Yes\n | ^^^^^\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:617:17\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^^^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:617:25\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^^^^^^^^^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:617:39\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:617:46\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:617:50\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:617:56\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^^^^^^^^^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:617:66\n |\n615 | - Yes\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n | ^\n618 | * - **Memory**\n619 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:618:4\n |\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n618 | * - **Memory**\n | ^\n619 | - Yes\n620 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:618:8\n |\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n618 | * - **Memory**\n | ^^\n619 | - Yes\n620 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:618:18\n |\n616 | - Yes (delegated)\n617 | - None. No special configuration needed for async functions.\n618 | * - **Memory**\n | ^\n619 | - Yes\n620 | - Yes (delegated)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:619:1\n |\n617 | - None. No special configuration needed for async functions.\n618 | * - **Memory**\n619 | - Yes\n | ^^^^^\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:621:17\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^^^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:621:25\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^^^^^^^^^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:621:39\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:621:46\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:621:50\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:621:56\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^^^^^^^^^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:621:66\n |\n619 | - Yes\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n | ^\n622 | * - **MongoDB**\n623 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:622:4\n |\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n622 | * - **MongoDB**\n | ^\n623 | - Yes\n624 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:622:8\n |\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n622 | * - **MongoDB**\n | ^^\n623 | - Yes\n624 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:622:19\n |\n620 | - Yes (delegated)\n621 | - None. No special configuration needed for async functions.\n622 | * - **MongoDB**\n | ^\n623 | - Yes\n624 | - Yes (native)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:623:1\n |\n621 | - None. No special configuration needed for async functions.\n622 | * - **MongoDB**\n623 | - Yes\n | ^^^^^\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:625:8\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:625:9\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:625:19\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:625:20\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:625:27\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:625:30\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:625:32\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:625:37\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^^^^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:625:46\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:625:55\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^^^^^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Expected `:`, found `async`\n --> README.rst:625:72\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:625:78\n |\n623 | - Yes\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n | ^^^^^^^^\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:626:1\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:626:12\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:626:18\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:626:37\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:626:39\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:626:44\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:626:45\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:626:55\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:626:56\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:626:61\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:626:64\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:626:70\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:626:79\n |\n624 | - Yes (native)\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n | ^^^^^^\n627 | ``TypeError``.\n628 | * - **SQL**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:627:8\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:627:9\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:627:19\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:627:20\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:627:21\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:627:22\n |\n625 | - ``mongetter`` must be a sync callable for sync functions and an async callable\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n | ^\n628 | * - **SQL**\n629 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:628:4\n |\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n628 | * - **SQL**\n | ^\n629 | - Yes\n630 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:628:8\n |\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n628 | * - **SQL**\n | ^^\n629 | - Yes\n630 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:628:15\n |\n626 | for async functions. Passing a sync ``mongetter`` to an async function raises\n627 | ``TypeError``.\n628 | * - **SQL**\n | ^\n629 | - Yes\n630 | - Yes (native)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:629:1\n |\n627 | ``TypeError``.\n628 | * - **SQL**\n629 | - Yes\n | ^^^^^\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:8\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:9\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:20\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:21\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:631:28\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:631:31\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:631:33\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^^^^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:38\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:39\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:46\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:631:47\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `or` that cannot be used here\n --> README.rst:631:50\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Expected `)`, found name\n --> README.rst:631:53\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^^^^^^^^^^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:631:64\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^^^^^^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:631:70\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Expected `in`, found newline\n --> README.rst:631:80\n |\n629 | - Yes\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n | ^\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:632:24\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^^^^^^^^^^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:632:35\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:632:36\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:632:48\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:632:49\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:632:55\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^^^^^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:632:61\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^^^^^^^^^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Expected `:`, found `type`\n --> README.rst:632:74\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^^^^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:632:79\n |\n630 | - Yes (native)\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n | ^^^^^^^^\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:633:8\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:633:18\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^^^^^^^^^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:633:28\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^^^^^^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:633:35\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:633:36\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:633:46\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:633:47\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:633:48\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:633:49\n |\n631 | - ``sql_engine`` must be a sync ``Engine`` (or connection string) for sync\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n | ^\n634 | * - **Redis**\n635 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:634:4\n |\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n | ^\n635 | - Yes\n636 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:634:8\n |\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n | ^^\n635 | - Yes\n636 | - Yes (native)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:634:17\n |\n632 | functions and a SQLAlchemy ``AsyncEngine`` for async functions. A type mismatch\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n | ^\n635 | - Yes\n636 | - Yes (native)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:635:1\n |\n633 | in either direction raises ``TypeError``.\n634 | * - **Redis**\n635 | - Yes\n | ^^^^^\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:637:8\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:637:9\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:637:22\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:637:23\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:637:30\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:637:33\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:637:35\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:637:40\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^^^^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:637:55\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^^^^^^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:637:64\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:637:73\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^^^^^^^^^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:637:86\n |\n635 | - Yes\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n | ^\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:638:11\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^^^^^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:638:17\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^^^^^^^^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:638:26\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^^^^^^^^^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:638:36\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:638:38\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:638:39\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:638:59\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:638:60\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:638:69\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^^^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Expected an identifier, but found a keyword `async` that cannot be used here\n --> README.rst:638:73\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^^^^^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Expected `in`, found newline\n --> README.rst:638:78\n |\n636 | - Yes (native)\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n | ^\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:639:8\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:27\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:29\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:34\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:43\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:46\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:639:49\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:639:55\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:639:64\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^^^^^^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:639:71\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:639:72\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:639:82\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:639:83\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:639:84\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:639:85\n |\n637 | - ``redis_client`` must be a sync client or sync callable for sync functions and\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n | ^\n640 | * - **S3**\n641 | - Yes\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:640:4\n |\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n | ^\n641 | - Yes\n642 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:640:8\n |\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n | ^^\n641 | - Yes\n642 | - Yes (delegated)\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:640:14\n |\n638 | an async callable returning a ``redis.asyncio.Redis`` client for async\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n | ^\n641 | - Yes\n642 | - Yes (delegated)\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:641:1\n |\n639 | functions. Passing a sync callable to an async function raises ``TypeError``.\n640 | * - **S3**\n641 | - Yes\n | ^^^^^\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:14\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^^^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:35\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:39\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:56\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:61\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:643:67\n |\n641 | - Yes\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n | ^^^^^\n644 | (``asyncio.to_thread``). No async S3 client is required.\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:644:1\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:644:9\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:644:10\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:644:28\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:644:29\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:644:30\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:644:31\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:644:36\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^^^^^\n |\n\ninvalid-syntax: Expected `def`, `with` or `for` to follow `async`, found name\n --> README.rst:644:42\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:644:45\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^^^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:644:64\n |\n642 | - Yes (delegated)\n643 | - Async support is delegated via thread-offloaded sync boto3 calls\n644 | (``asyncio.to_thread``). No async S3 client is required.\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:647:1\n |\n647 | Contributing\n | ^\n648 | ============\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:648:1\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:3\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:5\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:7\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:9\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:11\n |\n647 | Contributing\n648 | ============\n | ^^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:648:13\n |\n647 | Contributing\n648 | ============\n | ^\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:9\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:21\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:25\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:30\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:38\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:38\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:45\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:76\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:100\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:104\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:105\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 120)\n --> README.rst:650:121\n |\n648 | …\n649 | …\n650 | …https://github.com/shaypal5>`_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:650:122\n |\n648 | ============\n649 |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:650:144\n |\n648 | …\n649 | …\n650 | …ay.palachy@gmail.com>`_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda README.rst:650:146\n |\n648 | …\n649 | …\n650 | ….palachy@gmail.com>`_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda README.rst:650:148\n |\n648 | …\n649 | …\n650 | …lachy@gmail.com>`_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda README.rst:650:152\n |\n648 | …\n649 | …\n650 | …hy@gmail.com>`_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda README.rst:650:159\n |\n648 | …\n649 | …\n650 | …om>`_, `@shaypal5 `_) and `Jirka Borovec `_ (`@Borda README.rst:650:174\n |\n648 | …\n649 | …\n650 | …ypal5 `_) and `Jirka Borovec `_ (`@Borda `_ on GitH…\n | ^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:650:193\n |\n648 | …\n649 | …\n650 | …ub.com/shaypal5>`_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more t…\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:650:194\n |\n648 | …\n649 | …\n650 | …aypal5>`_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than welco…\n | ^^^^^^^^^^^^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:650:197\n |\n648 | …\n649 | …\n650 | …om/shaypal5>`_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than …\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected `)`, found `@`\n --> README.rst:650:198\n |\n648 | …\n649 | …\n650 | …m/shaypal5>`_) and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than w…\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:650:212\n |\n648 | …\n649 | …\n650 | … and `Jirka Borovec `_ (`@Borda `_ on GitHub); You are more than welcome to appr…\n | ^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:650:231\n |\n648 | …\n649 | …\n650 | … `_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help.…\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:234\n |\n648 | …\n649 | …\n650 | …ttps://github.com/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Co…\n | ^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:237\n |\n648 | …\n649 | …\n650 | …//github.com/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contrib…\n | ^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:650:243\n |\n648 | …\n649 | …\n650 | …thub.com/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributio…\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:650:244\n |\n648 | …\n649 | …\n650 | …hub.com/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contribution…\n | ^\n651 | …\n652 | …\n |\n\nE702 Multiple statements on one line (semicolon)\n --> README.rst:650:244\n |\n648 | …\n649 | …\n650 | …hub.com/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contribution…\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:250\n |\n648 | …\n649 | …\n650 | …/Borda>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are v…\n | ^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:254\n |\n648 | …\n649 | …\n650 | …da>`_ (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are very …\n | ^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:259\n |\n648 | …\n649 | …\n650 | … (`@Borda `_ on GitHub); You are more than welcome to approach them for help. Contributions are very welco…\n | ^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:264\n |\n648 | …\n649 | …\n650 | …da `_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:272\n |\n648 | …\n649 | …\n650 | …ttps://github.com/Borda>`_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:275\n |\n648 | …\n649 | …\n650 | …/github.com/Borda>`_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:284\n |\n648 | …\n649 | …\n650 | ….com/Borda>`_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:650:289\n |\n648 | …\n649 | …\n650 | …Borda>`_ on GitHub); You are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:650:313\n |\n648 | …\n649 | …\n650 | … are more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:650:317\n |\n648 | …\n649 | …\n650 | … more than welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:650:322\n |\n648 | …\n649 | …\n650 | …han welcome to approach them for help. Contributions are very welcomed! :)\n | ^^^^^^^^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected newline, found `!`\n --> README.rst:650:330\n |\n648 | …\n649 | …\n650 | …elcome to approach them for help. Contributions are very welcomed! :)\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:650:332\n |\n648 | …\n649 | …\n650 | …come to approach them for help. Contributions are very welcomed! :)\n | ^\n651 | …\n652 | …\n |\n\nE701 Multiple statements on one line (colon)\n --> README.rst:650:332\n |\n648 | …\n649 | …\n650 | …come to approach them for help. Contributions are very welcomed! :)\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:650:333\n |\n648 | …\n649 | …\n650 | …ome to approach them for help. Contributions are very welcomed! :)\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:650:334\n |\n648 | …\n649 | …\n650 | …me to approach them for help. Contributions are very welcomed! :)\n | ^\n651 | …\n652 | …\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:652:12\n |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:652:27\n |\n650 | Current maintainers are Shay Palachy Affek (`shay.palachy@gmail.com `_, `@shaypal5 README.rst:653:1\n |\n652 | Installing for development\n653 | --------------------------\n | ^\n654 |\n655 | Clone:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:653:27\n |\n652 | Installing for development\n653 | --------------------------\n | ^\n654 |\n655 | Clone:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:655:7\n |\n653 | --------------------------\n654 |\n655 | Clone:\n | ^\n656 |\n657 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:657:1\n |\n655 | Clone:\n656 |\n657 | .. code-block:: bash\n | ^\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:657:2\n |\n655 | Clone:\n656 |\n657 | .. code-block:: bash\n | ^\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:657:4\n |\n655 | Clone:\n656 |\n657 | .. code-block:: bash\n | ^^^^^^^^^^\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:657:15\n |\n655 | Clone:\n656 |\n657 | .. code-block:: bash\n | ^\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:659:1\n |\n657 | .. code-block:: bash\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:659:7\n |\n657 | .. code-block:: bash\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n | ^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:659:13\n |\n657 | .. code-block:: bash\n658 |\n659 | git clone git@github.com:python-cachier/cachier.git\n | ^^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:662:1\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:662:24\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:662:29\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:662:39\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^^^^^^^^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `:`, found `for`\n --> README.rst:662:52\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:662:62\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:662:88\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^^^^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:662:93\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n | ^\n663 |\n664 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:664:1\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n663 |\n664 | .. code-block:: bash\n | ^\n665 |\n666 | cd cachier\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:664:2\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n663 |\n664 | .. code-block:: bash\n | ^\n665 |\n666 | cd cachier\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:664:4\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n663 |\n664 | .. code-block:: bash\n | ^^^^^^^^^^\n665 |\n666 | cd cachier\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:664:15\n |\n662 | Install in development mode with test dependencies for local cores (memory and pickle) only:\n663 |\n664 | .. code-block:: bash\n | ^\n665 |\n666 | cd cachier\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:666:1\n |\n664 | .. code-block:: bash\n665 |\n666 | cd cachier\n | ^^\n667 | pip install -e . -r tests/requirements.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:666:6\n |\n664 | .. code-block:: bash\n665 |\n666 | cd cachier\n | ^^^^^^^\n667 | pip install -e . -r tests/requirements.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:667:7\n |\n666 | cd cachier\n667 | pip install -e . -r tests/requirements.txt\n | ^^^^^^^\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:667:20\n |\n666 | cd cachier\n667 | pip install -e . -r tests/requirements.txt\n | ^\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:667:23\n |\n666 | cd cachier\n667 | pip install -e . -r tests/requirements.txt\n | ^^^^^\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:669:1\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:6\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:17\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:48\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:57\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:68\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:85\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:93\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:669:97\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:669:110\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:669:118\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\nE501 Line too long (128 > 120)\n --> README.rst:669:121\n |\n667 | pip install -e . -r tests/requirements.txt\n668 |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n | ^^^^^^^^\n670 |\n671 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:671:1\n |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n670 |\n671 | .. code-block:: bash\n | ^\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:671:2\n |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n670 |\n671 | .. code-block:: bash\n | ^\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:671:4\n |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n670 |\n671 | .. code-block:: bash\n | ^^^^^^^^^^\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:671:15\n |\n669 | Each additional core (MongoDB, Redis, SQL, S3) requires additional dependencies. To install all dependencies for all cores, run:\n670 |\n671 | .. code-block:: bash\n | ^\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:673:1\n |\n671 | .. code-block:: bash\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n | ^^\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:673:7\n |\n671 | .. code-block:: bash\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n | ^^^^^^^\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:673:18\n |\n671 | .. code-block:: bash\n672 |\n673 | pip install -r tests/requirements_mongodb.txt\n | ^^^^^\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:674:7\n |\n673 | pip install -r tests/requirements_mongodb.txt\n674 | pip install -r tests/requirements_redis.txt\n | ^^^^^^^\n675 | pip install -r tests/requirements_postgres.txt\n676 | pip install -r tests/requirements_s3.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:674:18\n |\n673 | pip install -r tests/requirements_mongodb.txt\n674 | pip install -r tests/requirements_redis.txt\n | ^^^^^\n675 | pip install -r tests/requirements_postgres.txt\n676 | pip install -r tests/requirements_s3.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:675:7\n |\n673 | pip install -r tests/requirements_mongodb.txt\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n | ^^^^^^^\n676 | pip install -r tests/requirements_s3.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:675:18\n |\n673 | pip install -r tests/requirements_mongodb.txt\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n | ^^^^^\n676 | pip install -r tests/requirements_s3.txt\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:676:7\n |\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n676 | pip install -r tests/requirements_s3.txt\n | ^^^^^^^\n677 |\n678 | Running the tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:676:18\n |\n674 | pip install -r tests/requirements_redis.txt\n675 | pip install -r tests/requirements_postgres.txt\n676 | pip install -r tests/requirements_s3.txt\n | ^^^^^\n677 |\n678 | Running the tests\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:678:1\n |\n676 | pip install -r tests/requirements_s3.txt\n677 |\n678 | Running the tests\n | ^\n679 | -----------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:678:9\n |\n676 | pip install -r tests/requirements_s3.txt\n677 |\n678 | Running the tests\n | ^^^\n679 | -----------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:678:13\n |\n676 | pip install -r tests/requirements_s3.txt\n677 |\n678 | Running the tests\n | ^^^^^\n679 | -----------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:679:18\n |\n678 | Running the tests\n679 | -----------------\n | ^\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:681:4\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:681:8\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:681:12\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:681:24\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:681:28\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:681:29\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:681:36\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:681:37\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:681:54\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^^^^^^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:681:64\n |\n679 | -----------------\n680 |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n | ^^^^^^^^^^^^\n682 |\n683 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:683:1\n |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n682 |\n683 | .. code-block:: bash\n | ^\n684 |\n685 | python -m pytest\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:683:2\n |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n682 |\n683 | .. code-block:: bash\n | ^\n684 |\n685 | python -m pytest\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:683:4\n |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n682 |\n683 | .. code-block:: bash\n | ^^^^^^^^^^\n684 |\n685 | python -m pytest\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:683:15\n |\n681 | To run the tests, call the ``pytest`` command in the repository's root, or:\n682 |\n683 | .. code-block:: bash\n | ^\n684 |\n685 | python -m pytest\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:685:1\n |\n683 | .. code-block:: bash\n684 |\n685 | python -m pytest\n | ^^\n686 |\n687 | To run only MongoDB core related tests, use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:685:13\n |\n683 | .. code-block:: bash\n684 |\n685 | python -m pytest\n | ^^^^^^\n686 |\n687 | To run only MongoDB core related tests, use:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:687:1\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:4\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:8\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:13\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^^^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:21\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:26\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^^^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:687:34\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^^^^^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:687:45\n |\n685 | python -m pytest\n686 |\n687 | To run only MongoDB core related tests, use:\n | ^\n688 |\n689 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:689:1\n |\n687 | To run only MongoDB core related tests, use:\n688 |\n689 | .. code-block:: bash\n | ^\n690 |\n691 | pytest -m mongo\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:689:2\n |\n687 | To run only MongoDB core related tests, use:\n688 |\n689 | .. code-block:: bash\n | ^\n690 |\n691 | pytest -m mongo\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:689:4\n |\n687 | To run only MongoDB core related tests, use:\n688 |\n689 | .. code-block:: bash\n | ^^^^^^^^^^\n690 |\n691 | pytest -m mongo\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:689:15\n |\n687 | To run only MongoDB core related tests, use:\n688 |\n689 | .. code-block:: bash\n | ^\n690 |\n691 | pytest -m mongo\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:691:1\n |\n689 | .. code-block:: bash\n690 |\n691 | pytest -m mongo\n | ^^\n692 |\n693 | To run only memory core related tests, use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:691:13\n |\n689 | .. code-block:: bash\n690 |\n691 | pytest -m mongo\n | ^^^^^\n692 |\n693 | To run only memory core related tests, use:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:693:1\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:4\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:8\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:13\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:20\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:25\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^^^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:693:33\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^^^^^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:693:44\n |\n691 | pytest -m mongo\n692 |\n693 | To run only memory core related tests, use:\n | ^\n694 |\n695 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:695:1\n |\n693 | To run only memory core related tests, use:\n694 |\n695 | .. code-block:: bash\n | ^\n696 |\n697 | pytest -m memory\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:695:2\n |\n693 | To run only memory core related tests, use:\n694 |\n695 | .. code-block:: bash\n | ^\n696 |\n697 | pytest -m memory\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:695:4\n |\n693 | To run only memory core related tests, use:\n694 |\n695 | .. code-block:: bash\n | ^^^^^^^^^^\n696 |\n697 | pytest -m memory\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:695:15\n |\n693 | To run only memory core related tests, use:\n694 |\n695 | .. code-block:: bash\n | ^\n696 |\n697 | pytest -m memory\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:697:1\n |\n695 | .. code-block:: bash\n696 |\n697 | pytest -m memory\n | ^^\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:697:13\n |\n695 | .. code-block:: bash\n696 |\n697 | pytest -m memory\n | ^^^^^^\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:699:1\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:4\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:8\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:12\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:18\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:25\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:33\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:38\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:699:46\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^^^^^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:699:57\n |\n697 | pytest -m memory\n698 |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n | ^\n700 |\n701 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:701:1\n |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n700 |\n701 | .. code-block:: bash\n | ^\n702 |\n703 | pytest -m \"not mongo\"\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:701:2\n |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n700 |\n701 | .. code-block:: bash\n | ^\n702 |\n703 | pytest -m \"not mongo\"\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:701:4\n |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n700 |\n701 | .. code-block:: bash\n | ^^^^^^^^^^\n702 |\n703 | pytest -m \"not mongo\"\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:701:15\n |\n699 | To run all tests EXCEPT MongoDB core related tests, use:\n700 |\n701 | .. code-block:: bash\n | ^\n702 |\n703 | pytest -m \"not mongo\"\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:703:1\n |\n701 | .. code-block:: bash\n702 |\n703 | pytest -m \"not mongo\"\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:703:13\n |\n701 | .. code-block:: bash\n702 |\n703 | pytest -m \"not mongo\"\n | ^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:706:1\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:4\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:8\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:12\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:18\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:25\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:32\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:37\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:41\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:49\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:54\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:706:62\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^^^^^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:706:73\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n | ^\n707 |\n708 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:708:1\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n707 |\n708 | .. code-block:: bash\n | ^\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:708:2\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n707 |\n708 | .. code-block:: bash\n | ^\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:708:4\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n707 |\n708 | .. code-block:: bash\n | ^^^^^^^^^^\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:708:15\n |\n706 | To run all tests EXCEPT memory core AND MongoDB core related tests, use:\n707 |\n708 | .. code-block:: bash\n | ^\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:710:1\n |\n708 | .. code-block:: bash\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:710:13\n |\n708 | .. code-block:: bash\n709 |\n710 | pytest -m \"not (mongo or memory)\"\n | ^^^^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:713:1\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:9\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:17\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:23\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:31\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:33\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:38\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:713:46\n |\n713 | Running MongoDB tests against a live MongoDB instance\n | ^^^^^^^^\n714 | -----------------------------------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:714:54\n |\n713 | Running MongoDB tests against a live MongoDB instance\n714 | -----------------------------------------------------\n | ^\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:716:1\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:716:8\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:716:11\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:716:22\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:716:28\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:716:28\n |\n714 | …-------------------------------\n715 | …\n716 | …* By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n717 | …\n718 | …test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:41\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:49\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:55\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:59\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:63\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:71\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:73\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:80\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:88\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^^^^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:107\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:110\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^^^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:716:114\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:716:115\n |\n714 | -----------------------------------------------------\n715 |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n | ^\n717 |\n718 | **Option 1: Using the test script (recommended)**\n |\n\nE501 Line too long (217 > 120)\n --> README.rst:716:121\n |\n714 | …\n715 | …\n716 | …ed by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:716:132\n |\n714 | …\n715 | …\n716 | …nst a mocked MongoDB instance, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now ha…\n | ^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:716:133\n |\n714 | …\n715 | …\n716 | …st a mocked MongoDB instance, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now hav…\n | ^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:147\n |\n714 | …\n715 | …\n716 | …goDB instance, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several optio…\n | ^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:151\n |\n714 | …\n715 | …\n716 | … instance, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:156\n |\n714 | …\n715 | …\n716 | …ce, provided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:164\n |\n714 | …\n715 | …\n716 | …rovided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:166\n |\n714 | …\n715 | …\n716 | …ided by the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:171\n |\n714 | …\n715 | …\n716 | … the ``pymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:179\n |\n714 | …\n715 | …\n716 | …ymongo_inmemory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:193\n |\n714 | …\n715 | …\n716 | …ory`` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:197\n |\n714 | …\n715 | …\n716 | …` package. To run them against a live MongoDB instance, you now have several options:\n | ^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:202\n |\n714 | …\n715 | …\n716 | …ge. To run them against a live MongoDB instance, you now have several options:\n | ^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:716:210\n |\n714 | …\n715 | …\n716 | …un them against a live MongoDB instance, you now have several options:\n | ^^^^^^^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:716:218\n |\n714 | …\n715 | …\n716 | …em against a live MongoDB instance, you now have several options:\n | ^\n717 | …\n718 | …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:718:1\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:718:10\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:718:19\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^^^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:718:23\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^^^^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:718:28\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^^^^^^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:718:50\n |\n716 | **Note to developers:** By default, all MongoDB tests are run against a mocked MongoDB instance, provided by the ``pymongo_inmemory``…\n717 |\n718 | **Option 1: Using the test script (recommended)**\n | ^\n719 |\n720 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:720:1\n |\n718 | **Option 1: Using the test script (recommended)**\n719 |\n720 | .. code-block:: bash\n | ^\n721 |\n722 | # Test MongoDB only\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:720:2\n |\n718 | **Option 1: Using the test script (recommended)**\n719 |\n720 | .. code-block:: bash\n | ^\n721 |\n722 | # Test MongoDB only\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:720:4\n |\n718 | **Option 1: Using the test script (recommended)**\n719 |\n720 | .. code-block:: bash\n | ^^^^^^^^^^\n721 |\n722 | # Test MongoDB only\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:720:15\n |\n718 | **Option 1: Using the test script (recommended)**\n719 |\n720 | .. code-block:: bash\n | ^\n721 |\n722 | # Test MongoDB only\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:723:1\n |\n722 | # Test MongoDB only\n723 | ./scripts/test-local.sh mongo\n | ^^\n724 |\n725 | # Test MongoDB with local backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:723:3\n |\n722 | # Test MongoDB only\n723 | ./scripts/test-local.sh mongo\n | ^\n724 |\n725 | # Test MongoDB with local backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:723:4\n |\n722 | # Test MongoDB only\n723 | ./scripts/test-local.sh mongo\n | ^\n724 |\n725 | # Test MongoDB with local backends\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:723:27\n |\n722 | # Test MongoDB only\n723 | ./scripts/test-local.sh mongo\n | ^^^^^\n724 |\n725 | # Test MongoDB with local backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:726:3\n |\n725 | # Test MongoDB with local backends\n726 | ./scripts/test-local.sh mongo memory pickle\n | ^\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:726:4\n |\n725 | # Test MongoDB with local backends\n726 | ./scripts/test-local.sh mongo memory pickle\n | ^\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:726:27\n |\n725 | # Test MongoDB with local backends\n726 | ./scripts/test-local.sh mongo memory pickle\n | ^^^^^\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:726:33\n |\n725 | # Test MongoDB with local backends\n726 | ./scripts/test-local.sh mongo memory pickle\n | ^^^^^^\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:726:40\n |\n725 | # Test MongoDB with local backends\n726 | ./scripts/test-local.sh mongo memory pickle\n | ^^^^^^\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:728:1\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:6\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:13\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:27\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:35\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:42\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:728:52\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:728:52\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:728:75\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Expected `,`, found `and`\n --> README.rst:728:86\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:728:110\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^^^^^^^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:728:118\n |\n726 | ./scripts/test-local.sh mongo memory pickle\n727 |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n | ^\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:730:3\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:730:4\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:730:5\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^^^^^^^^^^^^^^^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:730:18\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:730:19\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:730:27\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^^^^^^^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:730:35\n |\n728 | This script automatically handles Docker container lifecycle, environment variables, and cleanup. Additional options:\n729 |\n730 | - ``-v, --verbose``: Show verbose output\n | ^^^^^^\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:731:3\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:731:4\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:731:5\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^^^^^^^^^^^^^^^^^^^^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:731:23\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:731:24\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:731:32\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^^^^^^^^^^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:731:43\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^^^^^^^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:731:51\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^^^^^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:731:57\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n | ^^^^^\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:732:3\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:732:4\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Only single target (not tuple) can be annotated\n --> README.rst:732:5\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^^^^^^^^^^^^^^^^^^^^^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:732:24\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:732:25\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:732:37\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^^^^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:732:42\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^^^^^^^^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:732:51\n |\n730 | - ``-v, --verbose``: Show verbose output\n731 | - ``-k, --keep-running``: Keep containers running after tests\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n | ^^^^^^\n733 |\n734 | **Option 2: Using Make**\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:734:1\n |\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n733 |\n734 | **Option 2: Using Make**\n | ^^\n735 |\n736 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:734:10\n |\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n733 |\n734 | **Option 2: Using Make**\n | ^\n735 |\n736 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:734:19\n |\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n733 |\n734 | **Option 2: Using Make**\n | ^^^^\n735 |\n736 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:734:25\n |\n732 | - ``-h, --html-coverage``: Generate HTML coverage report\n733 |\n734 | **Option 2: Using Make**\n | ^\n735 |\n736 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:736:1\n |\n734 | **Option 2: Using Make**\n735 |\n736 | .. code-block:: bash\n | ^\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:736:2\n |\n734 | **Option 2: Using Make**\n735 |\n736 | .. code-block:: bash\n | ^\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:736:4\n |\n734 | **Option 2: Using Make**\n735 |\n736 | .. code-block:: bash\n | ^^^^^^^^^^\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:736:15\n |\n734 | **Option 2: Using Make**\n735 |\n736 | .. code-block:: bash\n | ^\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:738:1\n |\n736 | .. code-block:: bash\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n | ^^\n739 | make test-all-local # Run all backends with Docker\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:738:8\n |\n736 | .. code-block:: bash\n737 |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n | ^^^^\n739 | make test-all-local # Run all backends with Docker\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:739:8\n |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n739 | make test-all-local # Run all backends with Docker\n | ^^^^\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:740:8\n |\n738 | make test-mongo-local # Run MongoDB tests with Docker\n739 | make test-all-local # Run all backends with Docker\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n | ^^^^\n741 |\n742 | **Option 3: Manual setup**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:742:1\n |\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n741 |\n742 | **Option 3: Manual setup**\n | ^\n743 |\n744 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:742:10\n |\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n741 |\n742 | **Option 3: Manual setup**\n | ^\n743 |\n744 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:742:20\n |\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n741 |\n742 | **Option 3: Manual setup**\n | ^^^^^\n743 |\n744 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:742:27\n |\n740 | make test-mongo-inmemory # Run with in-memory MongoDB (default)\n741 |\n742 | **Option 3: Manual setup**\n | ^\n743 |\n744 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:744:1\n |\n742 | **Option 3: Manual setup**\n743 |\n744 | .. code-block:: bash\n | ^\n745 |\n746 | # Start MongoDB with Docker\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:744:2\n |\n742 | **Option 3: Manual setup**\n743 |\n744 | .. code-block:: bash\n | ^\n745 |\n746 | # Start MongoDB with Docker\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:744:4\n |\n742 | **Option 3: Manual setup**\n743 |\n744 | .. code-block:: bash\n | ^^^^^^^^^^\n745 |\n746 | # Start MongoDB with Docker\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:744:15\n |\n742 | **Option 3: Manual setup**\n743 |\n744 | .. code-block:: bash\n | ^\n745 |\n746 | # Start MongoDB with Docker\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:747:1\n |\n746 | # Start MongoDB with Docker\n747 | docker run -d -p 27017:27017 --name cachier-test-mongo mongo:latest\n | ^^\n748 |\n749 | # Run tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:747:10\n |\n746 | # Start MongoDB with Docker\n747 | docker run -d -p 27017:27017 --name cachier-test-mongo mongo:latest\n | ^^^\n748 |\n749 | # Run tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:747:20\n |\n746 | # Start MongoDB with Docker\n747 | docker run -d -p 27017:27017 --name cachier-test-mongo mongo:latest\n | ^^^^^\n748 |\n749 | # Run tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:747:39\n |\n746 | # Start MongoDB with Docker\n747 | docker run -d -p 27017:27017 --name cachier-test-mongo mongo:latest\n | ^^^^^^^\n748 |\n749 | # Run tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:747:58\n |\n746 | # Start MongoDB with Docker\n747 | docker run -d -p 27017:27017 --name cachier-test-mongo mongo:latest\n | ^^^^^\n748 |\n749 | # Run tests\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:750:31\n |\n749 | # Run tests\n750 | CACHIER_TEST_HOST=localhost CACHIER_TEST_PORT=27017 CACHIER_TEST_VS_DOCKERIZED_MONGO=true pytest -m mongo\n | ^^^^^^^^^^^^^^^^^\n751 |\n752 | # Clean up\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:750:55\n |\n749 | # Run tests\n750 | CACHIER_TEST_HOST=localhost CACHIER_TEST_PORT=27017 CACHIER_TEST_VS_DOCKERIZED_MONGO=true pytest -m mongo\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n751 |\n752 | # Clean up\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:750:93\n |\n749 | # Run tests\n750 | CACHIER_TEST_HOST=localhost CACHIER_TEST_PORT=27017 CACHIER_TEST_VS_DOCKERIZED_MONGO=true pytest -m mongo\n | ^^^^^^\n751 |\n752 | # Clean up\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:750:103\n |\n749 | # Run tests\n750 | CACHIER_TEST_HOST=localhost CACHIER_TEST_PORT=27017 CACHIER_TEST_VS_DOCKERIZED_MONGO=true pytest -m mongo\n | ^^^^^\n751 |\n752 | # Clean up\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:753:10\n |\n752 | # Clean up\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n | ^^^^\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:753:15\n |\n752 | # Clean up\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n | ^^^^^^^\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:753:35\n |\n752 | # Clean up\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n | ^\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:753:44\n |\n752 | # Clean up\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n | ^^\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:753:47\n |\n752 | # Clean up\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n | ^^^^^^^\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:755:1\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:6\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^^^^^^^^^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:755:18\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:25\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:26\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:59\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:60\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:74\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^^^^^^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:90\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:93\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:94\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:99\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:755:100\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:755:102\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:109\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^^^^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:116\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^^^^^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\nE501 Line too long (221 > 120)\n --> README.rst:755:121\n |\n753 | …\n754 | …\n755 | …he GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n756 | …\n757 | …tibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:124\n |\n753 | docker stop cachier-test-mongo && docker rm cachier-test-mongo\n754 |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n | ^^\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:755:127\n |\n753 | …\n754 | …\n755 | …onment variable is set to ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every c…\n | ^^^^^^^^^^^\n756 | …\n757 | …e before submitting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:146\n |\n753 | …\n754 | …\n755 | … is set to ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull …\n | ^^^^\n756 | …\n757 | …ting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:151\n |\n753 | …\n754 | …\n755 | …t to ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull reques…\n | ^^^^^\n756 | …\n757 | …Rs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:157\n |\n753 | …\n754 | …\n755 | …True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^^\n756 | …\n757 | …nsure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:165\n |\n753 | …\n754 | …\n755 | …` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^\n756 | …\n757 | … compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:167\n |\n753 | …\n754 | …\n755 | …n the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^\n756 | …\n757 | …mpatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:172\n |\n753 | …\n754 | …\n755 | …itHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^^\n756 | …\n757 | …lity, though the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:180\n |\n753 | …\n754 | …\n755 | …tions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^^^\n756 | …\n757 | …ough the in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:189\n |\n753 | \n754 | …\n755 | …CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^\n756 | …\n757 | …he in-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:192\n |\n753 | …\n754 | …\n755 | …vironment, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^\n756 | …\n757 | …-memory MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:198\n |\n753 | …\n754 | …\n755 | …ent, which runs tests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^\n756 | …\n757 | …y MongoDB instance serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:755:214\n |\n753 | …\n754 | …\n755 | …ests against a real MongoDB instance on every commit and pull request.\n | ^^^^^^^\n756 | …\n757 | …e serves as a good proxy for most development.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:755:222\n |\n753 | …\n754 | …\n755 | …against a real MongoDB instance on every commit and pull request.\n | ^\n756 | …\n757 | …ves as a good proxy for most development.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:14\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:18\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:29\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:32\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:37\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:45\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:47\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:52\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:60\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:69\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:76\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:87\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:91\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:94\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:101\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^^^^^^^^^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\nE501 Line too long (197 > 120)\n --> README.rst:757:121\n |\n755 | …`True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n758 | …\n759 | …ning tests for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:757:123\n |\n755 | **CI Environment:** The ``CACHIER_TEST_VS_DOCKERIZED_MONGO`` environment variable is set to ``True`` in the GitHub Actions CI environ…\n756 |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n | ^^^\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:757:137\n |\n755 | …ariable is set to ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit an…\n756 | …\n757 | … submitting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^^^\n758 | …\n759 | … PR are the determining tests for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:757:145\n |\n755 | …is set to ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull r…\n756 | …\n757 | …ing PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^^^^\n758 | …\n759 | …the determining tests for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:757:154\n |\n755 | …o ``True`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^^\n758 | …\n759 | …rmining tests for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:757:161\n |\n755 | …rue`` in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …sure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^\n758 | …\n759 | …ng tests for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:166\n |\n755 | …in the GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …ompatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^\n758 | …\n759 | …ts for deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:757:171\n |\n755 | … GitHub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …bility, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^\n758 | …\n759 | … deciding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:757:177\n |\n755 | …ub Actions CI environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …y, though the in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^\n758 | …\n759 | …ding whether your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:757:186\n |\n755 | … environment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | … in-memory MongoDB instance serves as a good proxy for most development.\n | ^^^^^^^^^^^\n758 | …\n759 | …your code functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:757:198\n |\n755 | …nment, which runs tests against a real MongoDB instance on every commit and pull request.\n756 | …\n757 | …ory MongoDB instance serves as a good proxy for most development.\n | ^\n758 | …\n759 | …de functions correctly against MongoDB.**\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:759:1\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:16\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:22\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:26\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:34\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:36\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:41\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:49\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:58\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:63\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:67\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:74\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:76\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:79\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:83\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:87\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:759:99\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:759:105\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:759:118\n |\n757 | Contributors are encouraged to test against a real MongoDB instance before submitting PRs to ensure compatibility, though the in-memo…\n758 |\n759 | **HOWEVER, the tests run against a live MongoDB instance when you submit a PR are the determining tests for deciding whether your cod…\n | ^^^^^^^\n |\n\nE501 Line too long (173 > 120)\n --> README.rst:759:121\n |\n757 | …ting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | … the determining tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:759:126\n |\n757 | …stance before submitting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most developm…\n758 | …\n759 | … you submit a PR are the determining tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:759:131\n |\n757 | …e before submitting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …submit a PR are the determining tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:759:136\n |\n757 | … submitting PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | … PR are the determining tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:759:146\n |\n757 | …g PRs to ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …e determining tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:759:156\n |\n757 | …ensure compatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …ning tests for deciding whether your code functions correctly against MongoDB.**\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:759:164\n |\n757 | …ompatibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …ts for deciding whether your code functions correctly against MongoDB.**\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:759:172\n |\n757 | …ibility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …r deciding whether your code functions correctly against MongoDB.**\n | ^^\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:759:174\n |\n757 | …ility, though the in-memory MongoDB instance serves as a good proxy for most development.\n758 | …\n759 | …deciding whether your code functions correctly against MongoDB.**\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:762:9\n |\n762 | Testing all backends locally\n | ^^^\n763 | -----------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:762:13\n |\n762 | Testing all backends locally\n | ^^^^^^^^\n763 | -----------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:762:22\n |\n762 | Testing all backends locally\n | ^^^^^^^\n763 | -----------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:763:30\n |\n762 | Testing all backends locally\n763 | -----------------------------\n | ^\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:765:4\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:765:9\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:765:13\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^^^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:765:21\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^^^^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:765:68\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^^^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:765:76\n |\n763 | -----------------------------\n764 |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n | ^^^^\n766 |\n767 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected an indented block after `with` statement\n --> README.rst:767:1\n |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n766 |\n767 | .. code-block:: bash\n | ^\n768 |\n769 | # Test all backends at once\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:767:2\n |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n766 |\n767 | .. code-block:: bash\n | ^\n768 |\n769 | # Test all backends at once\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:767:4\n |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n766 |\n767 | .. code-block:: bash\n | ^^^^^^^^^^\n768 |\n769 | # Test all backends at once\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:767:15\n |\n765 | To test all cachier backends (MongoDB, Redis, SQL, Memory, Pickle) locally with Docker:\n766 |\n767 | .. code-block:: bash\n | ^\n768 |\n769 | # Test all backends at once\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:770:1\n |\n769 | # Test all backends at once\n770 | ./scripts/test-local.sh all\n | ^^\n771 |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:770:3\n |\n769 | # Test all backends at once\n770 | ./scripts/test-local.sh all\n | ^\n771 |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:770:4\n |\n769 | # Test all backends at once\n770 | ./scripts/test-local.sh all\n | ^\n771 |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:770:27\n |\n769 | # Test all backends at once\n770 | ./scripts/test-local.sh all\n | ^^^\n771 |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:773:3\n |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n773 | ./scripts/test-local.sh external\n | ^\n774 |\n775 | # Test specific combinations\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:773:4\n |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n773 | ./scripts/test-local.sh external\n | ^\n774 |\n775 | # Test specific combinations\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:773:27\n |\n772 | # Test only external backends (MongoDB, Redis, SQL)\n773 | ./scripts/test-local.sh external\n | ^^^^^^^^\n774 |\n775 | # Test specific combinations\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:776:3\n |\n775 | # Test specific combinations\n776 | ./scripts/test-local.sh mongo redis\n | ^\n777 |\n778 | # Keep containers running for debugging\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:776:4\n |\n775 | # Test specific combinations\n776 | ./scripts/test-local.sh mongo redis\n | ^\n777 |\n778 | # Keep containers running for debugging\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:776:27\n |\n775 | # Test specific combinations\n776 | ./scripts/test-local.sh mongo redis\n | ^^^^^\n777 |\n778 | # Keep containers running for debugging\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:776:33\n |\n775 | # Test specific combinations\n776 | ./scripts/test-local.sh mongo redis\n | ^^^^^\n777 |\n778 | # Keep containers running for debugging\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:779:3\n |\n778 | # Keep containers running for debugging\n779 | ./scripts/test-local.sh all -k\n | ^\n780 |\n781 | # Test specific test files with selected backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:779:4\n |\n778 | # Keep containers running for debugging\n779 | ./scripts/test-local.sh all -k\n | ^\n780 |\n781 | # Test specific test files with selected backends\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:779:27\n |\n778 | # Keep containers running for debugging\n779 | ./scripts/test-local.sh all -k\n | ^^^\n780 |\n781 | # Test specific test files with selected backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:782:3\n |\n781 | # Test specific test files with selected backends\n782 | ./scripts/test-local.sh mongo -f tests/test_mongo_core.py\n | ^\n783 |\n784 | # Test multiple files across all backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:782:4\n |\n781 | # Test specific test files with selected backends\n782 | ./scripts/test-local.sh mongo -f tests/test_mongo_core.py\n | ^\n783 |\n784 | # Test multiple files across all backends\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:782:27\n |\n781 | # Test specific test files with selected backends\n782 | ./scripts/test-local.sh mongo -f tests/test_mongo_core.py\n | ^^^^^\n783 |\n784 | # Test multiple files across all backends\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:782:36\n |\n781 | # Test specific test files with selected backends\n782 | ./scripts/test-local.sh mongo -f tests/test_mongo_core.py\n | ^^^^^\n783 |\n784 | # Test multiple files across all backends\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:785:3\n |\n784 | # Test multiple files across all backends\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n | ^\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:785:4\n |\n784 | # Test multiple files across all backends\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n | ^\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:785:27\n |\n784 | # Test multiple files across all backends\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n | ^^^\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:785:34\n |\n784 | # Test multiple files across all backends\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n | ^^^^^\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:785:56\n |\n784 | # Test multiple files across all backends\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n | ^^^^^\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:787:1\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:5\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:13\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:18\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:25\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:39\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:47\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:787:54\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:75\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:84\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found `and`\n --> README.rst:787:98\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:107\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:111\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^^^^^^^^\n |\n\nE501 Line too long (306 > 120)\n --> README.rst:787:121\n |\n785 | …\n786 | …\n787 | …priate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:123\n |\n785 | ./scripts/test-local.sh all -f tests/test_main.py -f tests/test_redis_core_coverage.py\n786 |\n787 | The unified test script automatically manages Docker containers, installs required dependencies, and runs the appropriate test suites…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:128\n |\n785 | …t_redis_core_coverage.py\n786 | …\n787 | … installs required dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific te…\n | ^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:140\n |\n785 | …re_coverage.py\n786 | …\n787 | …required dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files i…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:141\n |\n785 | …e_coverage.py\n786 | …\n787 | …equired dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files in…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:144\n |\n785 | …overage.py\n786 | …\n787 | …ired dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files inste…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:145\n |\n785 | …verage.py\n786 | …\n787 | …red dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instea…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found `/`\n --> README.rst:787:147\n |\n785 | …rage.py\n786 | …\n787 | …d dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead …\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:149\n |\n785 | …ge.py\n786 | …\n787 | …dependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:150\n |\n785 | …e.py\n786 | …\n787 | …ependencies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of …\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:158\n |\n785 | …\n786 | …\n787 | …ies, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the enti…\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:159\n |\n785 | …\n786 | …\n787 | …es, and runs the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entir…\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:168\n |\n785 | …\n786 | …\n787 | …s the appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suit…\n | ^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:175\n |\n785 | …\n786 | …\n787 | …appropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:179\n |\n785 | …\n786 | …\n787 | …ropriate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:182\n |\n785 | …\n786 | …\n787 | …iate test suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scri…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:186\n |\n785 | …\n786 | …\n787 | …est suites. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/RE…\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:195\n |\n785 | …\n786 | …\n787 | …tes. The ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-lo…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:200\n |\n785 | …\n786 | …\n787 | …he ``-f`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-te…\n | ^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:206\n |\n785 | …\n786 | …\n787 | …`` / ``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.m…\n | ^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:214\n |\n785 | …\n786 | …\n787 | …``--files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` f…\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:217\n |\n785 | …\n786 | …\n787 | …files`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for d…\n | ^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:221\n |\n785 | …\n786 | …\n787 | …`` option allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detail…\n | ^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:228\n |\n785 | …\n786 | …\n787 | …ion allows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detailed doc…\n | ^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:787:233\n |\n785 | …\n786 | …\n787 | …lows you to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documenta…\n | ^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:244\n |\n785 | …\n786 | …\n787 | …to run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:245\n |\n785 | …\n786 | …\n787 | …o run specific test files instead of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:277\n |\n785 | …\n786 | …\n787 | …d of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:787:278\n |\n785 | …\n786 | …\n787 | … of the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:787:280\n |\n785 | …\n786 | …\n787 | … the entire test suite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^^^\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:787:293\n |\n785 | …\n786 | …\n787 | …uite. See ``scripts/README-local-testing.md`` for detailed documentation.\n | ^^^^^^^^^^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:787:307\n |\n785 | …\n786 | …\n787 | …e ``scripts/README-local-testing.md`` for detailed documentation.\n | ^\n |\n\ninvalid-syntax: Expected an indented block after `for` statement\n --> README.rst:790:1\n |\n790 | Running pre-commit hooks locally\n | ^^^^^^^\n791 | --------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:790:9\n |\n790 | Running pre-commit hooks locally\n | ^^^\n791 | --------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:790:20\n |\n790 | Running pre-commit hooks locally\n | ^^^^^\n791 | --------------------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:790:26\n |\n790 | Running pre-commit hooks locally\n | ^^^^^^^\n791 | --------------------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:791:33\n |\n790 | Running pre-commit hooks locally\n791 | --------------------------------\n | ^\n792 |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:793:7\n |\n791 | --------------------------------\n792 |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n | ^^^\n794 |\n795 | .. code-block:: bash\n |\n\ninvalid-syntax: missing closing quote in string literal\n --> README.rst:793:10\n |\n791 | --------------------------------\n792 |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n794 |\n795 | .. code-block:: bash\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:795:1\n |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n794 |\n795 | .. code-block:: bash\n | ^\n796 |\n797 | pre-commit run --all-files\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:795:2\n |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n794 |\n795 | .. code-block:: bash\n | ^\n796 |\n797 | pre-commit run --all-files\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:795:4\n |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n794 |\n795 | .. code-block:: bash\n | ^^^^^^^^^^\n796 |\n797 | pre-commit run --all-files\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:795:15\n |\n793 | After you've installed test dependencies, you can run pre-commit hooks locally by using the following command:\n794 |\n795 | .. code-block:: bash\n | ^\n796 |\n797 | pre-commit run --all-files\n |\n\ninvalid-syntax: Unexpected indentation\n --> README.rst:797:1\n |\n795 | .. code-block:: bash\n796 |\n797 | pre-commit run --all-files\n | ^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:797:14\n |\n795 | .. code-block:: bash\n796 |\n797 | pre-commit run --all-files\n | ^^^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:800:1\n |\n800 | Adding documentation\n | ^\n801 | --------------------\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:800:8\n |\n800 | Adding documentation\n | ^^^^^^^^^^^^^\n801 | --------------------\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:801:21\n |\n800 | Adding documentation\n801 | --------------------\n | ^\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:6\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:28\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:34\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:803:38\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:45\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:55\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:803:66\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:76\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:81\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:803:88\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:96\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:100\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:108\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:112\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:117\n |\n801 | --------------------\n802 |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n | ^^^^^^\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\nE501 Line too long (356 > 120)\n --> README.rst:803:121\n |\n801 | …\n802 | …\n803 | … widely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstrings (in my personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:131\n |\n801 | …\n802 | …\n803 | …hich were chosen as they are perhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and r…\n | ^^^^^^^^^^^\n804 | …\n805 | …latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:143\n |\n801 | …\n802 | …\n803 | …e chosen as they are perhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and result in…\n | ^^^^\n804 | …\n805 | …ormat.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:148\n |\n801 | …\n802 | …\n803 | …sen as they are perhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and result in huma…\n | ^^^\n804 | …\n805 | ….html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:152\n |\n801 | …\n802 | …\n803 | …as they are perhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and result in human-re…\n | ^^^^\n804 | …\n805 | …l\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:157\n |\n801 | …\n802 | …\n803 | …are perhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable d…\n | ^^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:167\n |\n801 | …\n802 | …\n803 | …rhaps the most widely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstri…\n | ^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:170\n |\n801 | …\n802 | …\n803 | … the most widely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstrings (…\n | ^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:177\n |\n801 | …\n802 | …\n803 | …st widely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstrings (in my p…\n | ^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:183\n |\n801 | …\n802 | …\n803 | …dely-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstrings (in my person…\n | ^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:803:188\n |\n801 | …\n802 | …\n803 | …-spread conventions that are both supported by common tools such as Sphinx and result in human-readable docstrings (in my personal o…\n | ^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:227\n |\n801 | …\n802 | …\n803 | … by common tools such as Sphinx and result in human-readable docstrings (in my personal opinion, of course). When documenting code y…\n | ^^^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected an expression or a ')'\n --> README.rst:803:239\n |\n801 | …\n802 | …\n803 | …on tools such as Sphinx and result in human-readable docstrings (in my personal opinion, of course). When documenting code you add t…\n | ^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:245\n |\n801 | …\n802 | …\n803 | …such as Sphinx and result in human-readable docstrings (in my personal opinion, of course). When documenting code you add to this pr…\n | ^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:254\n |\n801 | …\n802 | …\n803 | …phinx and result in human-readable docstrings (in my personal opinion, of course). When documenting code you add to this project, pl…\n | ^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:266\n |\n801 | …\n802 | …\n803 | …esult in human-readable docstrings (in my personal opinion, of course). When documenting code you add to this project, please follow…\n | ^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:280\n |\n801 | …\n802 | …\n803 | …adable docstrings (in my personal opinion, of course). When documenting code you add to this project, please follow `these conventio…\n | ^^^^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:292\n |\n801 | …\n802 | …\n803 | …ocstrings (in my personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:297\n |\n801 | …\n802 | …\n803 | …ings (in my personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:301\n |\n801 | …\n802 | …\n803 | … (in my personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:305\n |\n801 | …\n802 | …\n803 | …n my personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:308\n |\n801 | …\n802 | …\n803 | … personal opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:803:313\n |\n801 | …\n802 | …\n803 | …al opinion, of course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:329\n |\n801 | …\n802 | …\n803 | …course). When documenting code you add to this project, please follow `these conventions`_.\n | ^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:803:336\n |\n801 | …\n802 | …\n803 | …e). When documenting code you add to this project, please follow `these conventions`_.\n | ^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:803:343\n |\n801 | …\n802 | …\n803 | …umenting code you add to this project, please follow `these conventions`_.\n | ^^^^^^^^^^^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:803:354\n |\n801 | …\n802 | …\n803 | …ng code you add to this project, please follow `these conventions`_.\n | ^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:803:357\n |\n801 | …\n802 | …\n803 | …code you add to this project, please follow `these conventions`_.\n | ^\n804 | …\n805 | …\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:805:1\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:805:2\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:805:5\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:805:12\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^^^^^^^^^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:805:22\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^^^^^^^^^^^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:805:33\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:805:34\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:805:42\n |\n803 | This project is documented using the `numpy docstring conventions`_, which were chosen as they are perhaps the most widely-spread con…\n804 |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^^\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:806:1\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:806:2\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:806:5\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:806:12\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^^^^^^^^^^^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:806:23\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:806:24\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:806:32\n |\n805 | .. _`numpy docstring conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n | ^^\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:808:15\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:808:22\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^^^\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:808:29\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:34\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:35\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:46\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:47\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:59\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:60\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:808:68\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:808:77\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^^^^^^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:86\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:808:87\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:808:92\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:808:101\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:808:104\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^^^^^^^^\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:808:113\n |\n806 | .. _`these conventions`: https://numpydoc.readthedocs.io/en/latest/format.html\n807 |\n808 | Additionally, if you update this ``README.rst`` file, use ``python setup.py checkdocs`` to validate it compiles.\n | ^\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:812:1\n |\n811 | Credits\n812 | =======\n | ^^\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:812:3\n |\n811 | Credits\n812 | =======\n | ^^\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:812:5\n |\n811 | Credits\n812 | =======\n | ^^\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:812:7\n |\n811 | Credits\n812 | =======\n | ^\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:812:8\n |\n811 | Credits\n812 | =======\n | ^\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:814:9\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:814:12\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:814:18\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^^^^^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:814:26\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^^^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:814:39\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:814:61\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:814:96\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^^^^^^^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:814:106\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^^^^^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\nE501 Line too long (128 > 120)\n --> README.rst:814:121\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^^^^^^^^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:814:129\n |\n812 | =======\n813 |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n | ^\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:816:9\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:816:14\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^^^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:816:37\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:816:44\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:816:59\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:816:78\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:816:79\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^^^^^^^^^^^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:816:82\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected `)`, found `@`\n --> README.rst:816:83\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:816:97\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:816:116\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:816:119\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^\n817 |\n818 | Other major contributors:\n |\n\nE501 Line too long (129 > 120)\n --> README.rst:816:121\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^^^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:816:122\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^^^^^^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:816:128\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:816:129\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Expected a statement\n --> README.rst:816:130\n |\n814 | Created by `Shay Palachy Affek `_ (shay.palachy@gmail.com), which currently assists in maintenance.\n815 |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n | ^\n817 |\n818 | Other major contributors:\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:818:7\n |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n817 |\n818 | Other major contributors:\n | ^^^^^\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:818:13\n |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n817 |\n818 | Other major contributors:\n | ^^^^^^^^^^^^\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:818:26\n |\n816 | Current lead developer/contributor: `Jirka Borovec `_ (`@Borda `_ on GitHub).\n817 |\n818 | Other major contributors:\n | ^\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:820:3\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:820:10\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^^^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:820:25\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:820:44\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:820:53\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:820:59\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^^^^^^^^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Compound statements are not allowed on the same line as simple statements\n --> README.rst:820:88\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Expected `in`, found name\n --> README.rst:820:97\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Expected `:`, found name\n --> README.rst:820:104\n |\n818 | Other major contributors:\n819 |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n | ^^^^\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n |\n\nE501 Line too long (154 > 120)\n --> README.rst:820:121\n |\n818 | …\n819 | …\n820 | … args-to-kwargs for less unique keys and numerous development and CI contributions.\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n821 | …\n822 | …ching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:820:122\n |\n818 | …\n819 | …\n820 | …ependence, args-to-kwargs for less unique keys and numerous development and CI contributions.\n | ^^^^^^^^^^^\n821 | …\n822 | … method caching support and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:820:141\n |\n818 | …\n819 | …\n820 | …wargs for less unique keys and numerous development and CI contributions.\n | ^^^^^^^^^^^^^\n821 | …\n822 | …ort and numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:820:155\n |\n818 | …\n819 | …\n820 | …r less unique keys and numerous development and CI contributions.\n | ^\n821 | …\n822 | …numerous improvements and bugfixes.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:822:3\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:822:11\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:822:23\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:822:46\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:822:70\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^^^^^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:822:78\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^^^^^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Expected `,`, found name\n --> README.rst:822:99\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^^^^^^^^^^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\nE501 Line too long (124 > 120)\n --> README.rst:822:121\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^^^^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:822:125\n |\n820 | * `Jirka Borovec `_ - Arg order independence, args-to-kwargs for less unique keys and numerous development …\n821 |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n | ^\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:824:3\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:824:4\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^^^^^^^^^^^^^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:824:18\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:824:38\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:824:48\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^^^^^^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:824:55\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^^^^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:824:60\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^^^^^^^^^^^^^^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:824:75\n |\n822 | * `Judson Neer `_ - Precaching, method caching support and numerous improvements and bugfixes.\n823 |\n824 | * `cthoyt `_ - Base memory core implementation.\n | ^\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:3\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:826:4\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^^^^^^^^^^^^^^^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:826:20\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:42\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:51\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:52\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:62\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:826:63\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:826:71\n |\n824 | * `cthoyt `_ - Base memory core implementation.\n825 |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n | ^\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:3\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Invalid annotated assignment target\n --> README.rst:828:4\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^^^^^^^^^^^^^^^^^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:828:22\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:46\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:55\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:56\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:78\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:828:79\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Expected an identifier\n --> README.rst:828:87\n |\n826 | * `amarczew `_ - The ``hash_func`` kwarg.\n827 |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n | ^\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:830:3\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:830:9\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^^^^^^^^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Expected an expression\n --> README.rst:830:25\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:830:46\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:830:62\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^^^^^^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Simple statements must be separated by newlines or semicolons\n --> README.rst:830:69\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^^^^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:830:81\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport `_ - Multi-file Pickle core, a.k.a ``separate_files`` (released on ``v1.5.3``).\n | ^\n831 |\n832 | * `John Didion `_ - Support for pickle-based caching for cases where two identically-named methods of dif…\n |\n\ninvalid-syntax: Got unexpected token `\n --> README.rst:830:82\n |\n828 | * `non-senses `_ - The ``wait_for_calc_timeout`` kwarg.\n829 |\n830 | * `Elad Rapaport