-
Notifications
You must be signed in to change notification settings - Fork 0
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
Do we need to setup.py install the pysparc package? #54
Comments
Not a must, can just use |
I would not get rid of the setup.py, it still helps define what the package is used for and what the requirements are. You could use a requirements.txt instead, but that would make it less explicit. |
I'm not sure why we install the package at all. It runs (or I thought it did) from the checked out repository. But maybe it imports from the installed package. I'm not sure anymore. |
Supervisor just runs the DAQ from the checkedout bin directory: |
Hmmm. But currently I can change code in the repository and then run the script manually and the changes take effect. So, from where does it import modules in that case? I'd like to be able to do that (at least on development Pi's while the software is still young). So maybe not install the package at all? But do the import paths need to be different in a 'run from repo' situation as opposed to a 'run from installed version and place script in /usr/local/bin'? I need to read up on this. |
If you install with pip with |
Time to wake up. This is what we did, yes: pysparc/provisioning/pysparc.yml Line 19 in ceab275
entry_points , thanks!
|
Currently we do this on the raspberry pi's.
The text was updated successfully, but these errors were encountered: