Clarify that methods take a string which is interpreted as a regex,
not a regex object.

Also clarify what the old `-1`, `0`, `1` and `2` options were.
(cherry picked from commit 8fb1f6e)

Clarify that methods take a string which is interpreted as a regex,
not a regex object.

Also clarify what the old `-1`, `0`, `1` and `2` options were.
(cherry picked from commit 8fb1f6e)

Clarify that methods take a string which is interpreted as a regex,
not a regex object.

Also clarify what the old `-1`, `0`, `1` and `2` options were.

(cherry picked from commit 8fb1f6e)

Clarify that methods take a string which is interpreted as a regex,
not a regex object.

Also clarify what the old `-1`, `0`, `1` and `2` options were.

(cherry picked from commit 8fb1f6e)

stackless.current.switch()

Fix an assertion violation caused by incorrect usage of
ts->st.del_post_switch.
Add a test case for "switch to current".

This commit also adds the test class TestTaskletSwitching, which was
only in 2.7-slp.

https://bitbucket.org/stackless-dev/stackless/issues/88
(grafted from f0db3bdf1061, b85b07e9f10effdbf52adc71d452d1e93bd3c5fd, 782a1b292460
and 7d9b4398011f)

The object's thread-id may be zero by the time _Py_queue_object is
called. Get the thread-id before marking the object as queued in
_Py_DecRefShared.

Fixes #88

…ation fabrication

Adds a script symmetric to scripts/numstat_bundle.sh that mechanizes
the "is this symbol called anywhere?" check, so dead-code-deletion
recommendations can no longer fail by quoting a head-truncated grep
that misses callers in sibling subtrees.

Per pythia python#88 + supervisor L2603 mechanization directive: theologian's
head-truncation incident (L2581) was caught by medic only because she
happened to re-grep independently. Mechanize the check so future similar
slips are caught by tooling, not by chance.

Discipline mechanized:
  - Searches the whole built source tree (Python Include Tools Lib
    Modules Programs), NOT just /Python/jit/.
  - NO head/tail truncation; full output to stdout.
  - Reports total + per-file count + verbatim grep cmd, so the caller
    can paste the result into chat without paraphrase.
  - Verdict line: ACTIVE / DEAD-CODE CANDIDATE.
  - Optional --exclude=<regex> for tagged-variant disambiguation
    (e.g. PhyRegisterSet vs RegisterSet).

VALIDATION (2 tests against the actual incident):

TEST 1 — would have prevented the L2581 fabrication:
    scripts/caller_grep.sh 'hir::Simplify\\{\\}'
    -> ACTIVE: 3 caller(s) across 1 file(s)
    -> Python/jit/compiler.cpp:106,120,128
    -> Verdict: 'DO NOT delete without rewiring callers first.'

TEST 2 — confirms Batch 2-A analysis was sound:
    scripts/caller_grep.sh '\\bRegisterSet\\b' --exclude='PhyRegisterSet'
    -> 0 lines across 0 files
    -> Verdict: 'DEAD-CODE CANDIDATE'

Both verdicts match medic L2583 + theologian L2591 manual-grep results.