mach doc fails to use pipenv, "ModuleNotFoundError: No module named 'livereload'"
Categories
(Developer Infrastructure :: Source Documentation, defect)
Tracking
(Not tracked)
People
(Reporter: chutten, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Linux Mint 19.1 x64
I've been struggling with my environment's python/pip for the last few weeks. I had some packages installed as root, I have about 5 different versions of Python installed... the sorts of things that happen if you don't know what you're doing and your computer's setup is over a year old.
mach doc used to work for me back at the beginning of July, but now (July 23) when I run it, it fails with the attached output. (I've included output for when the virtualenv already exists and when it doesn't and is created from scratch)
If mach doc can't find livereload, it must not be using the virtualenv because I've looked in the virtualenv and found it there:
$ ls obj-debug-x86_64-pc-linux-gnu/_virtualenvs/moztreedocs-anOrb84v/lib/python3.8/site-packages/livereload
cli.py handlers.py __init__.py management __pycache__ server.py vendors watcher.py
I'm convinced it's something I have wrong in my own setup, but I thought pipenv was supposed to render my setup irrelevant.
| Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Hoping this gets fixed automatically by bug 1655107, though there's a chance it's unrelated to pipenv.
| Reporter | ||
Updated•6 years ago
|
Comment 3•6 years ago
•
|
||
I somewhat scope bloated myself in bug 1655107 and it got a little stalled waiting for better virtualenv creation support in mach core.
| Reporter | ||
Comment 4•6 years ago
|
||
Huzzah, it appears as though bug 1656993 has fixed my issues!
:ahal, do you want this to remain open, or shall this go RESOLVED>FIXED?
Comment 5•6 years ago
|
||
Woohoo, let's close this.
Updated•4 years ago
|
Description
•