pythondiscorddiscord-apipython-3python-2

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: b6655fcabd

ci/buildyboi

develop

feature/docs

feature/docs-redux

feature/message-builder

feature/refactor

feature/storage

feature/voice

feature/zlib-stream-compression

gh-pages

master

staging/v1.0.0

v0.0.1

v0.0.10

v0.0.11

v0.0.11-rc.1

v0.0.11-rc.2

v0.0.11-rc.3

v0.0.11-rc.4

v0.0.11-rc.5

v0.0.11-rc.6

v0.0.11-rc.7

v0.0.11-rc.8

v0.0.12

v0.0.12-rc.1

v0.0.12-rc.2

v0.0.12-rc.3

v0.0.12-rc.4

v0.0.13-rc.1

v0.0.13-rc.2

v0.0.14-rc.1

v0.0.2

v0.0.3

v0.0.4

v0.0.5

v0.0.6

v0.0.7

v0.0.8

v0.0.9

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'b6655fcabd'

${ noResults }

disco/disco/types

History

Andrei e0ce459c96 [bugfix] fix behavior of cached_property This commit is a fairly large chunk of code that fixes a previously annoying and nasty bug causing cached_properties to not be cleared. Alongside this bug fix I took the opportunity to refactor the entire methdology behind cached properties, and bind them more strictly to the behavior of models. Prior to this commit, cached_properties where not be properly reset upon a model's `update` method being called due to some invalid code. Along with this issue, the actual behavior of cached properties landed in a weird in-between/gray area where they had to support both non-model and model use cases. The new version of cached_property is strictly for use with models, and another version `simple_cached_property` was added to support other use cases. The new cached_property simply builds an actual `property` within the metaclass. This is fairly efficient, and also reduces the surface area of behavior. When writing this I messed around with a few ideas, including allowing the user of `cached_property` to define a linkage between the property and fields that should invalidate its cached value, but this was both messy and introduced massive cognitive load on understand when a cached_property should be cleared. Although this version is slighty less efficient, I'm very much in favor of it vs the alternatives I tried.		8 years ago
..
__init__.py	Various fixes and improvements	9 years ago
base.py	[bugfix] fix behavior of cached_property	8 years ago
channel.py	[bugfix] fix behavior of cached_property	8 years ago
guild.py	[bugfix] fix behavior of cached_property	8 years ago
invite.py	Audit Log (#35)	8 years ago
message.py	[bugfix] fix behavior of cached_property	8 years ago
permissions.py	Users with administrator can execute all permissions	8 years ago
user.py	Fix image hashes incorrectly using `binary` type	8 years ago
voice.py	[bugfix] fix behavior of cached_property	8 years ago
webhook.py	[bugfix] fix behavior of cached_property	8 years ago