aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* properly send message with `asyncio.run`Gravatar mathsman51332019-10-05-3/+7
|
* add requested changes for reviewGravatar mathsman51332019-10-05-15/+28
|
* revert back `tests.cogs.test_information`. I got them in the wrong order...Gravatar mathsman51332019-10-05-2/+2
|
* revert back `tests.cogs.test_information`Gravatar mathsman51332019-10-05-3/+4
|
* Create the !mention commandGravatar mathsman51332019-10-05-8/+47
|
* Merge pull request #441 from python-discord/add-role-info-commandGravatar Chris G2019-10-04-1/+97
|\ | | | | Add role info command
| * Merge branch 'master' into add-role-info-commandGravatar Chris G2019-10-04-37/+288
| |\ | |/ |/|
* | Merge pull request #490 from python-discord/bb-previous-reasonGravatar Chris G2019-10-04-2/+39
|\ \ | | | | | | Show previous watch reason and total after invoking watch command
| * \ Merge branch 'master' into bb-previous-reasonGravatar Chris G2019-10-04-0/+122
| |\ \ | |/ / |/| |
* | | Merge pull request #473 from python-discord/ISODate-converterGravatar Mark2019-10-04-0/+122
|\ \ \ | | | | | | | | Add converter for ISO-formatted datetime strings
| * \ \ Merge branch 'master' into ISODate-converterGravatar Mark2019-10-04-38/+130
| |\ \ \ | |/ / / |/| | |
| * | | Check if tzinfo is None in ISODateTime testGravatar Sebastiaan Zeeff2019-10-03-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | As we have decided that the converter should return naive datetime objects, we should explicitly test that datetime strings with a timezone offset are still converted to a naive datetime object. I have done this by adding a `tzinfo is None` assertion.
| * | | Make ISODateTime return tz-unaware datetimeGravatar Sebastiaan Zeeff2019-10-02-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parser we use, `dateutil.parsers.isoparse` returns a timezone- aware or timezone-unaware `datetime` object depending on whether or not the datetime string included a timezone offset specification. Since we can't compare tz-aware objects to tz-unaware objects it's better to make sure our converter is consistent in the type it will return. For now, I've chosen to return tz-unaware datetime objects, since `discord.py` also returns tz-unaware datetime objects when accessing datetime-related attributes of objects. Since we're likely to compare "our" datetime objects to discord.py-provided datetime objects, I think that's the most parsimonious option for now. Note: It's probably a good idea to open a larger discussion about using timezone-aware datetime objects throughout the library to avoid a UTC-time being interpreted as localtime. This will require a broader discussion than this commit/PR allows, though.
| * | | Remove angle brackets from ISODateTime docstringGravatar Sebastiaan Zeeff2019-10-02-1/+1
| | | | | | | | | | | | | | | | | | | | This commit removes the angle brackets from the url in the docstring of `ISODateTime.convert`. The reason: it's ugly.
| * | | Apply docstring review suggestionGravatar Sebastiaan Zeeff2019-10-02-1/+1
| | | | | | | | | | | | Co-Authored-By: Mark <[email protected]>
| * | | Remove surplus quotation mark in class docstringGravatar Sebastiaan Zeeff2019-10-01-1/+1
| | | | | | | | | | | | Co-Authored-By: S. Co1 <[email protected]>
| * | | Add converter for ISO-formatted datetime stringsGravatar Sebastiaan Zeeff2019-10-01-0/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Related to https://github.com/python-discord/bot/issues/458 This commit adds a converter that automatically parses ISO-formatted datetime strings and returns a `datetime.datetime` object. It uses `dateutil.parser.isoparse` to do the heavy lifting, so it supports the same formats as this method. In addition, I have added tests that ensure that it accepts certain formats and added a description of these 'guaranteed' formats to the `ISODate.convert` docstring. This commit should make it easy to implement #485
| | * | Adjust verbiage of totals for watch commandsGravatar MarkKoz2019-10-04-2/+2
| | | |
| | * | Show previous watch reason and total after invoking watch commandGravatar MarkKoz2019-10-04-2/+39
| |/ / |/| |
* | | Merge pull request #481 from bendiller/fetch_posts_retriesGravatar S. Co12019-10-03-15/+24
|\ \ \ | | | | | | | | Add checks for valid response and retries to fetch_posts()
| * \ \ Merge branch 'master' into fetch_posts_retriesGravatar Mark2019-10-03-23/+106
| |\ \ \ | |/ / / |/| | |
* | | | Merge pull request #486 from python-discord/mute-fixGravatar Joseph2019-10-03-5/+42
|\ \ \ \ | | | | | | | | | | Fix mutes not being re-applied on rejoins.
| * \ \ \ Merge branch 'master' into mute-fixGravatar Joseph2019-10-03-1/+1
| |\ \ \ \ | |/ / / / |/| | | |
* | | | | Merge pull request #483 from python-discord/fix-watchchannels-unload-cog-bugGravatar S. Co12019-10-02-1/+1
|\ \ \ \ \ | | | | | | | | | | | | Fix `cog_unload` bug in WatchChannel ABC
| * \ \ \ \ Merge branch 'master' into fix-watchchannels-unload-cog-bugGravatar S. Co12019-10-02-7/+36
| |\ \ \ \ \ | |/ / / / / |/| | | | |
| * | | | | Fix `cog_unload` bug in WatchChannel ABCGravatar Sebastiaan Zeeff2019-10-02-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/python-discord/bot/issues/482 There was small bug in the `cog_unload` method of the WatchChannel ABC in `bot.cogs.watchchannels.watchchannel`. The problem was that it tries to check if the Task assigned to `self._consume_task` is done by accessing its `done` method. However, if a watch channel has not yet relayed messages after the bot has started, it will not have a consumption task yet, meaning this `_consume_task` attribute will be assigned to `None`. The solution is to change the `if` condition to: `if self._consume_task and not self._consume_task.done():` This commit closes #482
| | * | | | Fix mutes not being re-applied on rejoins.Gravatar scragly2019-10-03-5/+42
| |/ / / / |/| | | |
* | | | | Merge pull request #467 from Ayplow/short-docsGravatar Mark2019-10-01-5/+5
|\ \ \ \ \ | | | | | | | | | | | | Forward arguments to !docs get
| * \ \ \ \ Merge branch 'master' into short-docsGravatar Mark2019-10-01-12/+58
| |\ \ \ \ \ | |/ / / / / |/| | | | |
* | | | | | Merge pull request #475 from python-discord/fix-tags-edit-commandGravatar Mark2019-10-01-2/+31
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | Make `!tags edit` use PATCH to update tags
| * | | | | Merge branch 'master' into fix-tags-edit-commandGravatar Mark2019-10-01-10/+27
| |\ \ \ \ \ | |/ / / / / |/| | | | |
* | | | | | Merge pull request #480 from python-discord/separate_tools_and_resourcesGravatar Mark2019-10-01-7/+24
|\ \ \ \ \ \ | | | | | | | | | | | | | | Split !resources into !tools and !resources.
| * | | | | | Fix missing type annotations and docstring errors.Gravatar Leon Sandøy2019-10-01-7/+3
| | | | | | |
| * | | | | | Create !tools alias and split !site resources.Gravatar Leon Sandøy2019-10-01-7/+28
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This splits the former !site resources into two separate commands, one for !site resources and one for !site tools. This makes sense now that we've split up the lists into two pages. It also adds a new alias, !tools, to call this command. This addresses #478. https://github.com/python-discord/bot/issues/478
| * | | / / Make `!tags edit` use PATCH to update tagsGravatar Sebastiaan Zeeff2019-10-01-2/+31
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/python-discord/bot/issues/474 This commit makes sure we're using the PATCH method to update tags, instead of the POST method. The problem was that the `!tags edit` command was an alias of `!tags set`, which uses the POST method to post new tags to the API. However, when a tag with a given name already exists, the API will refuse a POST request in an attempt to update it; we need to use the PATCH method to the `bot/tags/{tag_name}` endpoint instead. I fixed this by creating a separate subcommand, `!tags edit`, that uses the correct PATCH method to update an existing tag. This commit closes #474
| | * | | Update docs cog docstring & fix URL converter attribute errorGravatar S. Co12019-10-01-4/+4
| | | | |
| | * | | Update bot/cogs/doc.pyGravatar Ayplo2019-10-01-1/+1
| | | | | | | | | | | | | | | Co-Authored-By: S. Co1 <[email protected]>
| | * | | Forward arguments to getGravatar Tom Sputz2019-09-30-1/+1
| |/ / /
| | * | Improve readabilityGravatar Ben Diller2019-10-03-0/+1
| | | | | | | | | | | | Co-Authored-By: Mark <[email protected]>
| | * | Move asyncio.sleep() to avoid disturbing function signatures.Gravatar bendiller2019-10-03-16/+13
| | | |
| | * | Add sleep(3) between retries, with bot indicating typing during sleepGravatar bendiller2019-10-02-4/+9
| | | |
| | * | Add logging for invalid response (after all retries are exhausted)Gravatar bendiller2019-10-02-1/+3
| | | |
| | * | Add checks for valid response and retries to fetch_posts()Gravatar bendiller2019-10-01-9/+13
| |/ /
| | * Merge branch 'add-role-info-command' of github.com:python-discord/bot into ↵Gravatar Joseph Banks2019-10-01-2347/+1646
| | |\ | | | | | | | | | | | | add-role-info-command
| | | * Merge branch 'master' into add-role-info-commandGravatar S. Co12019-10-01-2347/+1646
| | | |\ | |_|_|/ |/| | |
* | | | Update contrib doc for new wiki links (#470)Gravatar scragly2019-10-02-3/+3
|\ \ \ \ | |/ / / |/| | | Update contrib doc for new wiki links
| * | | Remove single-item listGravatar S. Co12019-10-01-2/+1
| | | | | | | | | | | | It looks silly
| * | | Update contrib doc for new wiki linksGravatar sco12019-09-30-3/+4
|/ / /
* | | Adjust development workflow inline with new `site` changes. (#464)Gravatar scragly2019-09-30-13/+28
|\ \ \ | | | | | | | | Adjust development workflow inline with new `site` changes.
| * | | Remove temp instructions, add link to contrib guide on website.Gravatar scragly2019-09-30-27/+1
| | | |