Andrew Montalenti comments

Results 46 comments of


                                            Andrew Montalenti

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

I imagine it must be something about my environment (specific zsh profile, Ubuntu 20.04 LTS, etc.) ... What other environmental details can I provide to figure it out?

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

@dsp Good idea, but didn't seem to help: ``` ❯ cd ~/repos/xyz ❯ env -u PYTHONHOME -u PYTHONPATH rye run python Cannot read termcap database; using dumb terminal settings. Python...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

I also tried simplifying my PATH, with same result. Just the rye shims + system paths. ``` ❯ echo $PATH /home/am/.rye/shims:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ```

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

What would probably help me is to understand, based on this contents inside site-packages: ``` ❯ ls .venv/lib/python3.12/site-packages _tcl-init.pth _virtualenv.pth _virtualenv.py xyz-0.1.0.dist-info _xyz.pth ``` How is `import xyz` supposed to...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

Thanks @dsp, these are good tips. When I `cat` the `_xyz.path` file, it's empty: ``` ❯ cat .venv/lib/python3.12/site-packages/_xyz.pth ``` I do have the `direct_url.json` file with the pointer to the...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

I also stole an idea from another GitHub issue, which is to run the `python3` interpreter under a heavily verbose mode, which will show where it tries to do module...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

One more pretty whacky result. Out of sheer curiosity, I tried installing `pip` into the rye-managed venv. This is because I wanted to inspect the output of `pip list`: ```...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

Alright, at least we're getting warmer. First, I tried revising `rye` config to no longer use `uv` via `config.toml`. I then blew away the venv and remade it. That didn't...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

Also just wanted to share all my version info that applies to my last couple comments: ``` ❯ ~/.rye/pip-tools/[email protected]/bin/pip-sync --version pip-sync, version 7.3.0 ❯ ~/.rye/pip-tools/[email protected]/bin/pip-compile --version pip-compile, version 7.3.0 ❯...

First-run experience failure: `rye run hello` after `rye init` + `rye sync` -- results in "ModuleNotFoundError: no module named 'xyz' ..."

@dsp Ah, good point: ``` ❯ ~/.rye/self/bin/uv --version uv 0.1.9 ``` (Edited the original comment to remove uv version so there isn't any confusion.)