aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
| * | Bump h11 from 0.14.0 to 0.16.0 in the pip groupGravatar dependabot[bot]2025-05-31-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps the pip group with 1 update: [h11](https://github.com/python-hyper/h11). Updates `h11` from 0.14.0 to 0.16.0 - [Commits](https://github.com/python-hyper/h11/compare/v0.14.0...v0.16.0) --- updated-dependencies: - dependency-name: h11 dependency-version: 0.16.0 dependency-type: indirect dependency-group: pip ... Signed-off-by: dependabot[bot] <[email protected]>
* | | Merge pull request #3309 from python-discord/update-pep-cog-2Gravatar ChrisJL2025-05-31-123/+59
|\ \ \ | |/ / |/| | Simplify PEP cog to use PEP API
| * | Fix: Move PEP link back to titleGravatar wookie1842025-04-19-1/+1
| | |
| * | Tidy PEP code + improve cachingGravatar wookie1842025-04-09-15/+25
| | |
| * | Only fetch PEP data when needed, and fix function callGravatar wookie1842025-04-09-10/+8
| | |
| * | Simplify PEP cog to use PEP apiGravatar wookie1842025-04-09-121/+49
| | |
* | | Merge pull request #3286 from python-discord/dependabot/pip/markdownify-1.1.0Gravatar ChrisJL2025-05-31-22/+21
|\ \ \ | | | | | | | | Bump markdownify from 0.14.1 to 1.1.0
| * | | Remove broken hack for reflowing markdown textGravatar wookie1842025-04-08-5/+4
| | | |
| * | | Fix markdownify breaking change: convert_as_inline->parent_tagsGravatar wookie1842025-04-08-12/+12
| | | | | | | | | | | | | | | | Now _inline is set as a pseudo value in parent_tags
| * | | Bump markdownify from 0.14.1 to 1.1.0Gravatar dependabot[bot]2025-03-08-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps [markdownify](https://github.com/matthewwithanm/python-markdownify) from 0.14.1 to 1.1.0. - [Release notes](https://github.com/matthewwithanm/python-markdownify/releases) - [Commits](https://github.com/matthewwithanm/python-markdownify/compare/0.14.1...1.1.0) --- updated-dependencies: - dependency-name: markdownify dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
* | | | Merge pull request #3310 from python-discord/vivek/pastebin-codeblockGravatar ChrisJL2025-05-31-14/+64
|\ \ \ \ | |_|_|/ |/| | | Display selected lines from our pastebin as codeblock
| * | | Fix return type annotationGravatar Vivek Ashokkumar2025-04-12-1/+1
| | | | | | | | | | | | Co-authored-by: Anand <[email protected]>
| * | | CodeSnippets: Add support for paste.pythondiscord.comGravatar vivekashok12212025-04-10-14/+64
| | |/ | |/|
* | | !timeit use 3.13 defaultGravatar Joe Banks2025-05-31-2/+2
| | | | | | | | | | | | | | | 3.12 support has been removed but !timeit was not updated. Corrects the error of inferior programmers like @ChrisLovering.
* | | 3.14 in snekbox (#3324)Gravatar ChrisJL2025-05-22-41/+57
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Replace 3.12 support in snekbox for 3.14-dev * Add extra info about pre-release versions in snekbox output * Dynamically get the default snekbox Python version by looking at the first supported version * Move snekbox help docs to the @command decorator This allows us to use a f-string to get the supported Python versions, instead of hard coding * Update snekbox tests to use new default python version
| * | | Update snekbox tests to use new default python versionGravatar Chris Lovering2025-05-17-18/+24
| | | |
| * | | Move snekbox help docs to the @command decoratorGravatar Chris Lovering2025-05-17-20/+25
| | | | | | | | | | | | | | | | This allows us to use a f-string to get the supported Python versions, instead of hard coding
| * | | Dynamically get the default snekbox Python version by looking at the first ↵Gravatar Chris Lovering2025-05-17-1/+1
| | | | | | | | | | | | | | | | supported version
| * | | Add extra info about pre-release versions in snekbox outputGravatar Chris Lovering2025-05-17-1/+6
| | | |
| * | | Replace 3.12 support in snekbox for 3.14-devGravatar Chris Lovering2025-05-17-2/+2
|/ / /
* | | Merge pull request #3320 from python-discord/remove-cban-aliasGravatar Joe Banks2025-04-20-2/+2
|\ \ \ | | | | | | | | Remove cban alias, Add clban & cpban aliases
| * | | Remove cban alias, Add clban & cpban aliasesGravatar vivekashok12212025-04-20-2/+2
|/ / /
* | | Merge pull request #3313 from shenanigansd/patch-1Gravatar Joe Banks2025-04-15-1/+1
|\ \ \ | | | | | | | | Remove Ned's name from 'projects' tag
| * | | Remove Ned's name from 'projects' tagGravatar Bradley Reynolds2025-04-12-1/+1
| |/ /
* | | Merge pull request #3311 from MeGaGiGaGon/mainGravatar Joe Banks2025-04-14-26/+53
|\ \ \ | |/ / |/| | Add step to zen command slicing
| * | fix testsGravatar MeGaGiGaGon2025-04-10-2/+2
| | |
| * | fix ruff lintsGravatar MeGaGiGaGon2025-04-10-5/+9
| | |
| * | fix whitespace and file end lintsGravatar MeGaGiGaGon2025-04-10-3/+3
| | |
| * | Add step to zen command slicingGravatar MeGaGiGaGon2025-04-10-27/+50
|/ /
* | Actually used capped durationGravatar Joe Banks2025-04-08-1/+1
| | | | | | | | | | | | Handle errors introduced by inferior developers such as @shtlrs Co-authored-by: Chris Lovering <[email protected]>
* | Founders Talentpool permissions (#3308)Gravatar Joe Banks2025-04-06-10/+11
| | | | | | | | | | * Add founders role to constants.py * Add Founders to some talentpool commands
* | Remove unused `ValidDiscordServerInvite` converter (#3307)Gravatar decorator-factory2025-04-06-39/+0
| |
* | Merge pull request #3306 from python-discord/remove-ping-on-auto-banGravatar Boris Muratov2025-03-31-1/+4
|\ \ | | | | | | Remove pings when auto-banning in filters
| * | Remove pings when auto-banning in filtersGravatar Chris Lovering2025-03-30-1/+4
|/ / | | | | | | Mods no longer want to be pinged when a fitler results in an auto ban, but we still want the message to be sent to mod-alerts.
* | Bump getsentry/action-release from 1 to 3 (#3305)Gravatar dependabot[bot]2025-03-29-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps [getsentry/action-release](https://github.com/getsentry/action-release) from 1 to 3. - [Release notes](https://github.com/getsentry/action-release/releases) - [Changelog](https://github.com/getsentry/action-release/blob/master/CHANGELOG.md) - [Commits](https://github.com/getsentry/action-release/compare/v1...v3) --- updated-dependencies: - dependency-name: getsentry/action-release dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* | Zen slicing (#3297)Gravatar ChrisJL2025-03-29-13/+116
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Added the possibility of slicing for the zen command * Fixed off-by-one error, as the end index can be equal to the length of the zen * Added support for negative signs and replaced re.search by re.match * Allows for end_index == len(zen_lines). Previously, in that case, end_index % zen_lines would be 0, even though it's the last line * Allows for slicing without a specified end index (e.g. "1:" will return all lines from the second to the last) * Update end index display when slicing in the zen command Co-authored-by: Vivek Ashokkumar <[email protected]> * Added tests for the zen command --------- Co-authored-by: Vivek Ashokkumar <[email protected]> Co-authored-by: ChrisJL <[email protected]>
| * \ Merge branch 'main' into zen_slicingGravatar ChrisJL2025-03-29-9/+157
| |\ \ | |/ / |/| |
* | | Merge pull request #2973 from python-discord/feat/reminder-add-notifyGravatar ChrisJL2025-03-29-6/+153
|\ \ \ | | | | | | | | Button for others to opt-in to be notified for reminders
| * \ \ Merge branch 'main' into feat/reminder-add-notifyGravatar ChrisJL2025-03-29-3/+4
| |\ \ \ | |/ / / |/| | |
* | | | Correct dependabot configGravatar Chris Lovering2025-03-29-3/+4
| |_|/ |/| |
| * | Merge branch 'main' into feat/reminder-add-notifyGravatar ChrisJL2025-03-29-2430/+4027
| |\ \ | |/ / |/| |
| * | Reminders: Simplify helper function to get button embedGravatar hedy2024-03-27-25/+11
| | | | | | | | | | | | | | | | | | | | | | | | This removes the need of any form of error handling from `embeds` list indexing, and makes the code more concise and readable. The drawback is that a whole new embed object have to be allocated each time, rather than editing the description like before.
| * | Reminders: Refactor all opt-in button related logic into View classGravatar hedy2024-03-26-41/+37
| | | | | | | | | | | | | | | - More resilient handling of API errors. - Don't rely on string manipulation to disable the button.
| * | Reminders: More robust implementation of mention opt-in buttonGravatar hedy2024-03-25-89/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This solves most, if not all issues from the previous commit. - A timeout of 5 minutes is enforced - this means the button can no longer be used either when the reminder arrives or 5 minutes passes since creation, whichever comes first. - Reminder edits in between creation and button clicks will be handled responsibly - This includes both edits of duration, mentions, and deleting reminders altogether. - UX is improved. This list of to-be-mentioned users is sent up-front with the author included. Instructions to click the button comes right after the list. - No updates to the API or site schema required, as the button message will disable itself when it encounters any sort of errors. - Implementation is also somewhat simplified. There are probably more improvements, maybe one caveat, but it's like almost midnight and I want to sleep :/ I sure hope the list above covers most of it. Further testing will be done. Now `.remind 10s test` is ingrained in my muscle memory...
| * | Reminders: Add a button for others to opt-in to a pingGravatar hedy2024-03-24-7/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is the initial implementation - it's currently _far_ from perfect and is very susceptible to errors. Notable features beyond the basic requirements: - Fails safely when max mentions reached (we're limited by the 2000-character limit when sending the reminder with the pings), and disables the button. - Adds an additional embed to the initial confirmation message to show who clicked on the notify button. - Edits the additional embed and disables the button when the reminder is sent. In many ways, this implementation is quite bad: - Uses an async callback to delegate the task of PATCH-ing the API to edit mentions to the `new_reminders` method. - Edits to the opt-in list embed relies on the fact that the reminder is not edited (using !remind edit) before someone clicks on the button. A trivial way to fix this would be to add another field to the site schema to store the `notification_view` in some way. - The button is neither disabled nor any edits to the embed made when the reminder is deleted before someone clicks on the button. - String splitting is used which relies on the exact format of the embed message when editing the embed to disable the button. We have to reminder to update this piece of code when adjusting its format in the future. The UX can also be improved. Currently, I can't think of a way to concisely phrase the button embed message so that it is clear that the button is for people _other than_ the reminder author. Notes: - Max reminder mentions: - Mentions are pinged directly in a discord message when the reminder is sent. This means we're limited by the 2000-char limit. If we take each User ID snowflake to be 18-characters, and considering each mention to be formated as "<@ID> " (with extra space), it results in about 90 mentions max. I've set the constant to 80 just in case. - This is not an issue when the mentions are added in through other means than the button we're adding in this commit, because the user has to use @-mentions when sending the `!remind edit` command, which is already under the discord's character limit. - Log messages are added when something unexpected occurs within the code. Hopefully this is unlikely to happen after the implementation issues listed above are solved. - The opt-in list in the second embed is separate from mentions added in the original reminder creation, or any further edits, because mentions are added by the to-be-mentioned-user, rather than by the reminder author in this way. (Even though they are stored the same way.)
| | * Added tests for the zen commandGravatar LeandroVandari2025-03-24-0/+90
| | |
| | * Update end index display when slicing in the zen commandGravatar Leandro Vandari2025-03-20-1/+1
| | | | | | | | | Co-authored-by: Vivek Ashokkumar <[email protected]>
| | * Allows for slicing without a specified end index (e.g. "1:" will return all ↵Gravatar LeandroVandari2025-03-18-2/+2
| | | | | | | | | | | | lines from the second to the last)
| | * Allows for end_index == len(zen_lines). Previously, in that case, end_index ↵Gravatar LeandroVandari2025-03-18-1/+1
| | | | | | | | | | | | % zen_lines would be 0, even though it's the last line
| | * Added support for negative signs and replaced re.search by re.matchGravatar LeandroVandari2025-03-17-1/+1
| | |
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-19 03:55:00 +0000