mitsuhiko / mitsuhiko/python-logical-call-context

Decide on Terms

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
9
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently there are a few terms which are weird:

  • Context.key (and call context)
  • Context.local_key (and logical call context)

This is in particular a bit at odds with isolated_call_context creating a new logical call context and nonlocal data not being transported into new logical call contexts.

Contributor guide

No contributing guide indexed for this repository

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

No files or tests are named. Review the terminology around Context.key, Context.local_key, isolated_call_context, and nonlocal data, then determine a consistent naming scheme that matches the described behavior. Done means the project has an agreed terminology and the issue's inconsistency is resolved.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.