{"push_id":610930177,"size":1,"distinct_size":1,"ref":"refs/heads/text-cache","head":"c89d43b5a49b99c1653f7987c3bc9c5d481dc1a5","before":"d17944ba715b06aeef1824fb1a8a58b0b470df6f","commits":[{"sha":"c89d43b5a49b99c1653f7987c3bc9c5d481dc1a5","author":{"email":"9343557fe728326ecca60ea600eccabb6754179b@redhat.com","name":"Adam Williamson"},"message":"cache page text until next edit operation\n\nStore the results of page.text() operations in a simple cache\ndict. This avoids unnecessary remote roundtrips. Cache is\ncleared on each successful page save operation; we might want\nto also have a method to clear the cache, TTL, whatever, if\nfolks are likely to keep Page instances around a long time and\nneed to refresh them for possible third party edits.\n\nThis also gets rid of the section attribute, which looks bogus\nto me. All it appears to achieve is that if you retrieve the\ntext of a particular section, then run a 'save' operation\nwithout explicitly specifying a section, the save operation\nis applied to the same section. This seems a completely wrong\nand potentially dangerous assumption. Maybe I'm missing\nsomething, though.","distinct":true,"url":"https://api.github.com/repos/AdamWill/mwclient/commits/c89d43b5a49b99c1653f7987c3bc9c5d481dc1a5"}]}