From 11b9aadeebf22a5c4c204a2c1e1d4f51872766be Mon Sep 17 00:00:00 2001 From: "Yamashita, Yuu" Date: Sun, 21 Jul 2013 23:41:21 -0700 Subject: [PATCH] Updated Understanding binstubs (markdown) --- Understanding-binstubs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Understanding-binstubs.md b/Understanding-binstubs.md index a327d53..2368f83 100644 --- a/Understanding-binstubs.md +++ b/Understanding-binstubs.md @@ -51,9 +51,9 @@ pyenv adds its own "shims" directory to `$PATH` which contains binstubs for every executable related to Python. There are binstubs for `python`, `pip`, and for all setuptools binstubs across each installed Python version. -When you call `rspec` on the command-line, it results in this call chain: +When you call `nosetests` on the command-line, it results in this call chain: -1. `$PYENV_ROOT/shims/rspec` (pyenv shim) +1. `$PYENV_ROOT/shims/nosetests` (pyenv shim) 1. `$PYENV_ROOT/versions/2.7.5/bin/nosetests` (setuptools binstub) 1. `$PYENV_ROOT/versions/2.7.5/lib/python2.7/site-packages/nose/__init__.py` (original)