Add aiologic and culsans to Awesome Trio Libraries in the docs

[x42005e1f]

Hi, I'd like to add aiologic to your list of awesome libraries. My library can be used to communicate with both threads and event loops in those threads, which can also be seen as an alternative approach to Trio/asyncio interoperability. But I'm not sure about which category aiologic is better to be in, so I put it under "Tools and Utilities". No documentation yet, but hopefully someone will find it useful.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.62%. Comparing base (b43383d) to head (1768a9f).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3092   +/-   ##
=======================================
  Coverage   99.62%   99.62%           
=======================================
  Files         124      124           
  Lines       18381    18381           
  Branches     1226     1226           
=======================================
  Hits        18312    18312           
  Misses         47       47           
  Partials       22       22           

[A5rocks]

I was looking at your README and it seems pretty nice! I don't think this is a good idea though:

Optional Trio-style checkpoints

If something is optional, that means there are no guarantees. And it's the guarantees that every await will call a checkpoint that make trio easier to use.

[x42005e1f]

I agree @A5rocks, it does look weird, but the point is there: if a Trio run loop is running in a thread, then by default every await in that thread will call a checkpoint, otherwise it won't. This behavior can be changed via environment variables: you can even enable checkpoints for synchronous calls at the threading level (and get very nice fairness). It all depends on what the user wants.

[x42005e1f]

Now, since the last commit, the above behavior is clarified in my README.

[A5rocks]

This seems fine to me, though I'm not too sure about the summary. If you think that describes it best then good enough.

[A5rocks]

This still looks good to me :P

I didn't merge this previously cause I wanted someone else to sanity check. But if nobody does I'll merge this eventually (not that soon though.)

[trio-bot]

Hey @x42005e1f, it looks like that was the first time we merged one of your PRs! Thanks so much! 🎉 🎂

If you want to keep contributing, we'd love to have you. So, I just sent you an invitation to join the python-trio organization on Github! If you accept, then here's what will happen:

• Github will automatically subscribe you to notifications on all our repositories. (But you can unsubscribe again if you don't want the spam.)

• You'll be able to help us manage issues (add labels, close them, etc.)

• You'll be able to review and merge other people's pull requests

• You'll get a [member] badge next to your name when participating in the Trio repos, and you'll have the option of adding your name to our member's page and putting our icon on your Github profile (details)

If you want to read more, here's the relevant section in our contributing guide.

Alternatively, you're free to decline or ignore the invitation. You'll still be able to contribute as much or as little as you like, and I won't hassle you about joining again. But if you ever change your mind, just let us know and we'll send another invitation. We'd love to have you, but more importantly we want you to do whatever's best for you.

If you have any questions, well... I am just a humble Python script, so I probably can't help. But please do post a comment here, or in our chat, or on our forum, whatever's easiest, and someone will help you out!