-
Notifications
You must be signed in to change notification settings - Fork 75
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
Added setuptools structure to enable installation #26
base: master
Are you sure you want to change the base?
Conversation
@lurch These changes look sane to me but I am not a Python expert, any comments from you? |
Sorry, I hadn't seen this before, oops. The changes to |
Yes, making the package available on PyPi is also possible. Ref: https://packaging.python.org/tutorials/packaging-projects/. Structure is similar to the one I'm making. I would have preferred to have kept the files in the root directory. It seems that having a subdirectory with the Python package (application in our case) name is "standard". Refs: |
Fair enough, always good to adhere to standards 🙂 |
…ng setuptools Re-structured directory tree to permit setuptools installation Added "main" function definition in pico_project.py to permit executable installation using setuptools Updated pico_configs.tsv configuration file read function to read from python script installation directory
Have rebased as requested and put pip installation as "optional" and at the foot of the README. |
Updated pico_project to move default tsv file specification to argparse function.
Added setup.py for setuptools installation support using Pip
Changed pico_generator to include a main() function for script execution when installed
GIF and TSV copied to installation directory
Changed pico_generator to read TSV file from current installation directory
Added section to README for Pip installation