python-trio / python-trio/trio

Python 3.8 wishlist

Open
#495 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

project meta
Dominant language
Python
Stars
7.3k
Forks
431
Avg merge
2d 17h
Merged PRs (30d)
6

Description

3.7 is in beta now, so I'm closing the old 3.7 wishlist (#103) and starting a new one :-). This isn't complete or fully-fleshed out, but to get us started, here's some stuff off the top of my head:

  • Better MultiError support: the main two pain points are catching them, and printing them (in particular we can override sys.excepthook, but that doesn't help with other code that wants to print or capture tracebacks like IPython, pytest, raven, ...)

  • Whatever we decide we need to improve handling of cancel scope/nursery interaction with generators. PEP 568 is one approach (#265). This is complicated because cancel scopes and nurseries have somewhat different needs. Or maybe we just want to disallow yielding from inside them... but that would also need some kind of help from the interpreter. Details: https://github.com/python-trio/trio/issues/264#issuecomment-418989328

  • Motion on bpo-32561 would be neat (better performance for async file operations)

  • Making KeyboardInterrupt protection more reliable:

  • Try proposing a hook that runs on bare calls to async functions (so e.g. await f() doesn't call the hook, but f() does). Trio would make this an error (#79), asyncio would make it call ensure_future, twisted would call asDeferred, etc.

  • Adding a signal.raise_ wrapper (bpo-35568, see also #816)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a broad Python 3.8 wishlist covering several independent proposals, with related discussions in issues #265, #264, #79, #816, the linked PEP, and the referenced bpo items. Start by choosing one item and reading its linked discussion; the work is done only when that item has a separately agreed scope and acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.