Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mycroft-pip install #143

Open
krisgesling opened this issue Nov 18, 2019 · 2 comments
Open

mycroft-pip install #143

krisgesling opened this issue Nov 18, 2019 · 2 comments

Comments

@krisgesling
Copy link
Contributor

Dependencies section needs to include info on manually installing python packages to the Mycroft virtual environment using mycroft-pip install

@fidesachates
Copy link

I'm developing a skill and I created a requirements.txt as per documentation, but the skill was complaining it couldn't find the module. It wasn't until I did as you alluded by calling mycroft-pip install did the skill work.

When does requirements.txt get evaluated? I restarted the mycroft service, but it still seemed my packages in requirements.txt still were not installed. Relatedly, after I mycroft-pip installed the deps, deleting the requirements.txt file did not impact functionality. I'm guessing this means requirements.txt only get processed when the skill gets installed and changes to it are not reflected?

@forslund
Copy link
Collaborator

forslund commented Jan 2, 2020

The requirements.txt is parsed and the deps in it is installed at skill install time. Basically when msm installs the skill into the mycroft venv the requirements.txt or manifest.yml is parsed and pip is executed accordingly.

Currently the installed dependencies aren't tracked by msm so the installed dependencies would need to be manually removed from the mycroft venv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants