Are my standard library modules supposed to come from outside my hatch environments?

[jesshart]

I expect to feel silly after lobbing this out to the community, but is this supposed to happen?

$ hatch run python -c "import pathlib; print(pathlib.__file__)"
/opt/homebrew/Cellar/[email protected]/3.11.9/Frameworks/Python.framework/Versions/3.11/lib/python3.11/pathlib.py

I would expect python standard library modules to live in corresponding hatch environment python path.

$ hatch run env | grep hatch
VIRTUAL_ENV=/Users/jhartman/Library/Application Support/hatch/env/virtual/italk-utype/IFCf39DD/italk-utype
$ hatch run which python
/Users/jhartman/Library/Application Support/hatch/env/virtual/italk-utype/IFCf39DD/italk-utype/bin/python

I installed hatch using homebrew, but this behavior has me scratching my head.

Resources to Explore

• https://hatch.pypa.io/latest/how-to/python/custom/

[ofek]

Yes that is expected, every virtual environment (by default) only gets its own site-packages and the standard library uses the parent. There is no reason not to because they are the same code so it saves space.