Getting started problem on Mac Ventura, Xcode CLI Tools, "ModuleNotFoundError: No module named 'scalene.crdp'"

[arubdesu]

Hello, I'm trying to run the test/testme.py on macOS 13.1 (arm64-architecture/Apple Silicon) with Apple's pip3/python 3.9.6 from the Xcode Command Line Tools, and not succeeding after multiple attempts, with or without sudo:

% /usr/bin/pip3 --version
pip 21.2.4 from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/site-packages/pip (python 3.9)
% pip3 install -U scalene                              
Defaulting to user installation because normal site-packages is not writeable
Collecting scalene
  Using cached scalene-1.5.19-cp39-cp39-macosx_10_9_universal2.whl
Requirement already satisfied: cloudpickle>=1.5.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from scalene) (2.2.0)
Requirement already satisfied: pynvml>=11.0.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from scalene) (11.4.1)
Requirement already satisfied: Jinja2>=3.0.3 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from scalene) (3.1.2)
Requirement already satisfied: rich>=10.7.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from scalene) (13.0.1)
Requirement already satisfied: wheel>=0.36.1 in /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/site-packages (from scalene) (0.37.0)
Requirement already satisfied: MarkupSafe>=2.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from Jinja2>=3.0.3->scalene) (2.1.1)
Requirement already satisfied: pygments<3.0.0,>=2.6.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from rich>=10.7.0->scalene) (2.14.0)
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in /Users/allister/Library/Python/3.9/lib/python/site-packages (from rich>=10.7.0->scalene) (0.9.1)
Installing collected packages: scalene
  WARNING: The script scalene is installed in '/Users/allister/Library/Python/3.9/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed scalene-1.5.19
% git clone https://github.com/plasma-umass/scalene.git
Cloning into 'scalene'...
<snip>
% cd scalene
% ~/Library/Python/3.9/bin/scalene test/testme.py 
Traceback (most recent call last):
  File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/private/tmp/scalene/scalene/__main__.py", line 4, in <module>
    from scalene import scalene_profiler
  File "/private/tmp/scalene/scalene/scalene_profiler.py", line 62, in <module>
    from scalene.scalene_json import ScaleneJSON
  File "/private/tmp/scalene/scalene/scalene_json.py", line 18, in <module>
    from scalene.crdp import rdp
ModuleNotFoundError: No module named 'scalene.crdp'
% /usr/bin/python3 -m ~/Library/Python/3.9/bin/scalene test/testme.py
/Library/Developer/CommandLineTools/usr/bin/python3: Error while finding module specification for '/Users/allister/Library/Python/3.9/bin/scalene' (ModuleNotFoundError: No module named '/Users/allister/Library/Python/3')

Any pointers would be appreciated! (Homebrew is not my friend, so I stay away from it 😅)

[emeryberger]

Hi - you don't need to (and shouldn't) clone the repo if all you want to do is run Scalene. You should be able to just do this:

pip install scalene
scalene yourfile.py

I recommend you run your code in a different directory than the repo.

[arubdesu]

On macOS (Monterey, as of 12.3 which came out early last year) there is no pip (or python3, until you e.g. install the command line tools) so I explicitly call pip3 to differentiate what I'm using.
I could probably make this work in a venv, should I give that a try?

[emeryberger]

You can also just run python3 -m pip, which is what I always to do to make sure I use the version of pip that matches the installed version of Python.