aboutsummaryrefslogtreecommitdiff
path: root/discord/client.py
Commit message (Collapse)AuthorAgeFilesLines
* Add support for guild widgetNCPlayz2019-03-191-14/+33
|
* Expose MetadataNCPlayz2019-03-191-4/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added access to: * `/users/@me/guilds` * `/guilds/{guild_id}` * `/guilds/{guild_id}/members/{member_id}` BREAKING CHANGE: * `get_user_info` -> `fetch_user_info` to match naming scheme. Remove useless note Remove `reverse` and corresponding documentation Update documentation to reflect #1988 Rename `get_` HTTP functions to `fetch_` Breaking Changes: * `get_message` -> `fetch_message` * `get_invite` -> `fetch_invite` * `get_user_profile` -> `fetch_user_profile` * `get_webhook_info` -> `fetch_webhook` * `get_ban` -> `fetch_ban` Fix InviteConverter, update migrating.rst Rename get_message to fetch_message
* Organise documentationNCPlayz2019-03-191-53/+56
|
* Add on_disconnect event.Rapptz2019-03-181-0/+1
| | | | I assume this is where it has to be. Fix #1937
* Moved http.close to before _closed.setNCPlayz2019-03-091-2/+1
|
* Expose more information from partial invites, along with counts.Rapptz2019-02-121-5/+9
| | | | | | | | | | | | | This adds the following information. * `PartialInviteGuild` to replace `Object` patching * `PartialInviteChannel` to replace `Object` patching * Invite.approximate_member_count and Invite.approximate_presence_count The new partial objects provide better documentation on what is expected when you fetch random invites. Fixes #1830
* Bumped copyright years to 2019.Dante Dam2019-01-281-1/+1
|
* Support discordapp.com invite URLs.Rapptz2018-11-251-1/+1
|
* Add support for multiple activitiesSnowyLuma2018-11-241-1/+1
|
* [lint] Removed unused variable handlerHornwitser2018-11-241-1/+0
| | | | Left over by the removal of handlers in 2721689.
* [lint] Changed missed docstrings to raw-stringHornwitser2018-11-241-2/+2
| | | | Missed by a4d1599 despite being pointed out in #1570.
* [lint] Fix import orderHornwitser2018-11-241-9/+11
| | | | | Reorder imports to be consistenly grouped by standard library, third party library, and local modules in that order thoughout the library.
* [lint] Rename exception variables to excHornwitser2018-11-241-6/+6
| | | | | Use the more explicit (and common) exc instead of e as the variable holding the exception in except handlers.
* [lint] Limit unneccessarily broad except clausesHornwitser2018-11-241-3/+3
| | | | Add exception qualifier(s) to bare except clauses swallowing exceptions.
* Optimise tight loops in DiscordGateway.received_messageRapptz2018-09-241-8/+5
| | | | | | * type(x) is y is faster than isinstance(x, y) * Re-arrange if-statements for common statements * Drop handler getattr for most events that don't use it
* Fix up the Sphinx strings causing warnings.Rapptz2018-09-151-1/+1
|
* [lint] Fix incorrect and inconsistent whitespaceHornwitser2018-08-221-4/+2
| | | | Adjust whitespace to be consistent with the rest of the library.
* [lint] Remove unused variablesHornwitser2018-08-221-1/+1
| | | | Left over from various refactoring and rewrites.
* More informations for the Application infoEl Laggron2018-08-221-1/+6
| | | | | This adds the rpc_origin, bot_public and bot_require_code_grant attributes
* Explicitly mark event handlers privateRapptz2018-08-091-2/+2
|
* Fix dumb typo in the warning.Rapptz2018-07-241-2/+3
|
* Add a warning for self-bots in Client.loginRapptz2018-07-241-0/+6
| | | | Closes #1449
* Add clarification about creating guildsKot2018-07-241-2/+2
|
* [docs] discord/client: remove reference to async_eventbmintz2018-07-191-9/+2
|
* Remove remaining asyncio.coroutine calls.bmintz2018-07-051-7/+0
| | | | Also remove Client.async_event
* Remove dead package references.Rapptz2018-06-101-1/+1
|
* Drop support for Python 3.4 and make minimum version 3.5.2.Rapptz2018-06-101-75/+53
|
* Fixes various documentation errors/inconsistenciesSteve C2018-05-181-1/+4
| | | | Mostly dealing with permissions, also fixes Raw Events inclusion.
* Convert Client.activity back to an Activity-like objectRapptz2018-03-061-2/+2
|
* Missing import for _ActivityTag inside ClientRapptz2018-03-061-0/+1
|
* Add ability to change the activity used when logging in at runtime.Rapptz2018-03-051-0/+14
|
* Split Game object to separate Activity subtypes for Rich Presences.Rapptz2018-03-051-19/+20
| | | | | | | | | | | This is a massive breaking change. * All references to "game" have been renamed to "activity" * Activity objects contain a majority of the rich presence information * Game and Streaming are subtypes for memory optimisation purposes for the more common cases. * Introduce a more specialised read-only type, Spotify, for the official Spotify integration to make it easier to use.
* Add intersphinxTobotimus2018-01-061-12/+10
|
* Proper variable name in Client.clear.Rapptz2017-12-201-1/+1
|
* Add Client.clear to clear the bot's internal state to a clean slate.Rapptz2017-12-161-0/+12
| | | | In case you want to have some external restart loop.
* Fix AppInfo.id being a stringReinaSakuraba2017-10-021-1/+1
|
* Changed discord.Client.event to debug log success instead of info log.espeonofespeonage2017-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | This is suggested to prevent spamming the console unnecesarilly. Info should be used to output information to the user that is important, but not a warning or an error. If I am bundling a bot as a modular package then it doesn't really make sense to spam their console with every time a coroutine is subscribed to, as it likely will not mean anything to the user. If they are interested in this, it would make more sense to just to enable debugging first. I have made this change, as I am writing a wrapper for this library for a private project, and that will handle dispatching events, thus, I do not need a prompt for each event that is subscribed to in this module outside of DEBUG. Currently, with logging set to INFO, I am getting 47 lines reading: INFO:discord.client:coroutine has successfully been registered as an event ...being output as my bot starts, and without having to disable INFO logging altogether, I am currently having to temporarily change the verbosity of the logger as the events are initialised, which is not desirable as it could potentially cover up any other INFO messages that would be useful to have output. Using a filter seems like a bit of a hacky workaround. If this isn't acceptable then another alternative would be to add a parameter to the constructor of discord.Client to enable or disable printing this information.
* Add an example for on_reaction_add waiting.Rapptz2017-09-181-0/+19
| | | | | Apparently people would rather read examples than the actual documentation.
* Add webhook support.Rapptz2017-08-211-0/+24
| | | | | | | Allows for usage of either `requests` and `aiohttp` when used in "Standalone" mode. Fixes #704
* Add Client.latency, AutoShardedClient.latency and latencies.Rapptz2017-08-151-0/+9
| | | | | | This should allow an easier way to query the Discord protocol gateway latency, defined by the difference HEARTBEAT_ACK between and the last sent HEARTBEAT.
* Fix the proxy support for aiohttp>=1.4.PapyrusThePlant2017-08-111-3/+8
|
* Add heartbeat_timeout to the Client options.Rapptz2017-08-081-0/+5
| | | | | | | This setting configures how long before a timeout event is emitted internally and disconnects the websocket. Since some users were experiencing issues with the gateway not responding, this should help mitigate the issue for those with poor PCs.
* Add documentation examples for AsyncIterator and change_presence.Gorialis2017-08-081-0/+5
|
* accept_invite() doesn't exist on rewriteJuan2017-07-251-3/+0
|
* Don't re-raise in Client.connect if it's a clean close code.Rapptz2017-07-141-0/+3
|
* Implement a LRU cache for private channels.Rapptz2017-07-041-1/+7
| | | | | | Another fix related to the discord issue[1]. [1]: https://github.com/hammerandchisel/discord-api-docs/issues/184
* Add support for user flags in Profile.Rapptz2017-06-301-2/+3
|
* Defer logging formatting until the logger is actually called.Rapptz2017-06-091-2/+2
| | | | | This would cause unnecessary format calls even if you didn't have logging enabled.
* Don't expose Client.messagesRapptz2017-05-261-12/+1
| | | | | | | Not entirely sure why it was exposed in the first place. Most uses with it essentially boiled down to mis-usage when they meant to use the /messages endpoint (via Client.logs_from or Messageable.history) or complaining about the partial data woes that came from it.
* Log when a KeyboardInterrupt is met in Client.runRapptz2017-05-251-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2026-05-06 20:10:19 +0000