Conversation
… empty json file; clean up ignore list
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…na/trio into fix/issue-3226-docstrings
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3523 +/- ##
===============================================
Coverage 100.00000% 100.00000%
===============================================
Files 128 128
Lines 19474 19474
Branches 1323 1322 -1
===============================================
Hits 19474 19474
🚀 New features to boost your workflow:
|
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…na/trio into fix/issue-3226-docstrings
|
I believe there's a bug-typo in pypy which made some of the tests fail - pypy/pypy#5594 . Tests are fragile for when new symbols appear. I added exclude for "missing" symbol in test_exports.py until bug is fixed. It's not really a missing symbol, it's a symbol pypy adds with typo. |
|
I think this is ready for review @A5rocks @CoolCat467 . new docstrings wording could probably be better. |
A5rocks
left a comment
There was a problem hiding this comment.
Thank you!! I did a quick skim through, though I wasn't very thorough and probably some of my comments are incorrect.
I think some of your new docstrings are invalid RST, but that's fine because the only thing that will show them is Pyright, I guess? (or maybe ty too...).
|
I made an issue about cryptography failing to install, see pyca/cryptography#15735 IMO just ignore that CI error for now! |
for more information, see https://pre-commit.ci
I believe cryptography 50.0.2 has a correct wheel https://pypi.org/project/cryptography/#cryptography-50.0.2-pp311-pypy311_pp80-win_amd64.whl |
…na/trio into fix/issue-3226-docstrings
for more information, see https://pre-commit.ci
|
Feel free to make another PR that bumps our cryptography version to that! I didn't notice. Edit: done in #3525 |
|
@A5rocks I have updated docstings per comments. Disclosure that I used Claude for format checks, and for proof-reading. Please re-review/approve/merge . |
|
Changing the way CI works makes me feel uneasy and feels outside the scope of this pull request. I would much prefer if you factored that out into a separate pull request. |
I didn't change how ci works (if you're refering to recent commits to ci.yml?). that was done by some other PRs that got merged into main and then merged here. I don't see their changes in https://github.com/python-trio/trio/pull/3523/changes :
cc @CoolCat467 I removed not used code from src\trio_tests\check_type_completeness.py that's all I can revert check_type_completeness.py to what'as now in main and bring back empty json file, is that the case? |
done |
|
Yes, it was the On other notes, +1 on one of the review comments earlier
I see a couple docstrings that are yet to follow this. I haven't looked at the wording super closely quite yet, will review more closely later. |
…na/trio into fix/issue-3226-docstrings

Fixes #3226.