aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* [commands] Support callables in Greedy converterRapptz2019-04-131-1/+1
|
* [commands] Fix lambda converters in non-module contexts.Rapptz2019-04-131-1/+1
| | | | Not sure why anyone would do this but might as well fix it.
* Change slowmode max value in docsapple502j2019-04-131-1/+1
|
* Add `Permissions.stream`NCPlayz2019-04-121-3/+10
| | | | Add stream to Permissions classmethods
* Improvements to intro docs.Dante Dam2019-04-121-7/+7
|
* [tasks] set internal task to None after cancelingSteve C2019-04-121-0/+1
|
* Remove "needs python 3.5+" from async iter sectionapple502j2019-04-121-2/+1
|
* [tasks] Add before_loop and after_loop decoratorsRapptz2019-04-122-19/+124
|
* Export tasks extensionRapptz2019-04-121-1/+1
|
* [commands] Add versionadded to dm_onlyRapptz2019-04-121-0/+2
|
* Update FAQ with some common tagsVexs2019-04-121-4/+70
| | | | | | | Pointed references to random.cat to use their aws api Added details about custom and unicode emojis to how to add a reaction Added watching example to presence changing Added new fetch methods to specific model FAQ
* [tasks] Document version addedRapptz2019-04-111-0/+2
|
* [tasks] Ensure total number of seconds is not less than 0.Rapptz2019-04-111-3/+6
|
* [tasks] Rename Loop.run to Loop.start to avoid blocking connotationsRapptz2019-04-112-6/+6
|
* [tasks] Add a new background helper 'tasks' extension.Rapptz2019-04-113-0/+292
|
* [commands] Fix erroneous string in dm_only checkRapptz2019-04-111-1/+1
|
* [commands] Added dm_only checkDante Dam2019-04-112-7/+29
| | | | Raises PrivateMessageOnly on failure.
* [commands] Fix references in Bot to actually link.Rapptz2019-04-103-71/+68
| | | | Exceptions can't seem to link due to a bug in Sphinx.
* Update changelogv1.0.1Rapptz2019-04-102-1/+13
|
* Version bump to v1.0.1Rapptz2019-04-101-2/+2
|
* [commands] Properly name heading for ExtensionErrorRapptz2019-04-101-2/+2
|
* Fix voice handshake race conditionImayhaveborkedit2019-04-101-0/+10
| | | In the event that two voice_server_updates are received in a short time frame, the second one is now ignored.
* Add notes warning that fetch_ methods are api callsVexs2019-04-102-0/+25
| | | | Also recommends using cache attributes/methods instead
* Fix various bugs with Asset._url None handling.Rapptz2019-04-091-2/+4
|
* Fix cleanup code on Linux not working properly.Rapptz2019-04-091-9/+17
|
* Stop the event loop if it's running during cleanup.Rapptz2019-04-091-1/+8
| | | | Also handle the coroutine directly instead of using run_until_complete
* Use is_connected() instead of _connected in checksDaniel2019-04-091-2/+2
| | | Was doing a falsy check on an Event object instead of using the (unused) is_connected() function.
* Fix broken documentation attributeSteve C2019-04-091-1/+1
|
* Fix issue with speaking state causing an error.Rapptz2019-04-081-0/+3
|
* Update classifier in setup.pyv1.0.0Rapptz2019-04-081-1/+1
|
* Version bump to v1.0.0Rapptz2019-04-081-2/+2
|
* Update Japanese translation files.Rapptz2019-04-088-3488/+8740
|
* Add notes stating what Guild.fetch_guild and Guild.fetch_guilds returnsNCPlayz2019-04-081-2/+12
| | | | Also fixed two typos.
* Fix documentation so Sphinx can build semi-cleanly.Rapptz2019-04-082-4/+4
|
* Bump PyNaCl to 1.3.0Rapptz2019-04-081-1/+1
|
* Wording nit, library -> function in load_opusRapptz2019-04-081-1/+1
|
* Change all IntEnum to EnumRapptz2019-04-082-8/+8
| | | | A testament to how many 3.5 users there are.
* Remove manual documentation for AppInfoRapptz2019-04-082-50/+4
|
* Missing a word in Attachment.saveRapptz2019-04-081-2/+2
|
* Fix oversight where on_disconnect did not get called on WS termination.Rapptz2019-04-082-0/+3
|
* Fix long-standing issue with user updates not dispatching properly.Rapptz2019-04-083-8/+43
| | | | | | | | | | | | | | | | | | | | | | This fix is long coming. For a long time due to the addition of a global user cache, the on_member_update event would only have the updated user in the very first dispatch due to a quirk in the reference only being updated once. In order to fix this issue two things had to change: 1. There had to be a new event, `on_user_update` to complement the equivalent member event. 2. Unnecessary copies of User had to be removed to compensate for the performance hit from the diffing. While doing these two fixes I also re-evaluated some more unnecessary copies done during the PRESENCE_UPDATE to add member case while fetch_offline_members=False is set or due to chunking issues. The number of copies was brought down from 2 to 1, discounting the original Member creation. Unsure on the benefits of this one, however. N.B: this doesn't change the pre-existing behaviour of on_member_update
* GUILD_MEMBER_UPDATE no longer does actual user updates.Rapptz2019-04-082-8/+2
| | | | | This had been delegated to PRESENCE_UPDATE a long time ago, unfortunately.
* Don't use an enum when unnecessary in Member._client_statusRapptz2019-04-081-1/+1
|
* Add a note to load_opus that it's auto loaded on Windows.Rapptz2019-04-081-0/+5
|
* Add some version guarantees to the documentation.Rapptz2019-04-084-6/+45
|
* terminate iterators immediately once out of datakhazhyk2019-04-071-2/+2
| | | | | | | | | | if len(data) < 100, either limit was less than 100, or we ran out of results, in both cases, we should terminate the lookup. This fixes, e.g., hangs in audit_logs(limit=999999), and will reduce the number of fetch calls for any case where limit is greater than the number of results. (Prior, would just kinda loop calling audit-logs)
* simplify AuditLogIterator orderingkhazhyk2019-04-072-24/+21
| | | | | | rename reverse to oldest_first and remove cases where messages would be ordered differently from the order we fetch audit log entries, similar to HistoryIterator
* simplify HistoryIterator message orderingkhazhyk2019-04-074-32/+29
| | | | | | | | | | | | | | | | | | | | rename reverse -> oldest_first, which is more obvious what it does. Then, honor it entirely - if you specify no `after` endpoint, we default to the beginning of message history, similar to how `before` defaults to the end of message history. This is a breaking change, and will change the behavior of any iterator that previously would have been returning messages in a weird order for limits over 100 `for msg in history(reversed=True, limit=300)` would return the newest 300 messages, in a messed up order (100..0, 200..100, 300..200). `for msg in history(oldest_first=True, limit=300)` will now return the oldest 300 messages in order. And so on. `for msg in history(after=msg)` is unchanged, this previously would return the oldest 100 messages after `msg`, oldest->newest order, and still will.
* allow passing 0 for logs_from parameterskhazhyk2019-04-071-3/+3
|
* Client.event raises TypeError instead of ClientException.Rapptz2019-04-071-2/+7
|