-
Notifications
You must be signed in to change notification settings - Fork 3
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
README and travis.yml should be linked #37
Comments
Unfortunately I have no idea how to do this, the README is a static file. For sphinx docu, which is build, I guess one could rig something .. but for the README, I see no nice way. A simple hyperlink into the travis.yml would be a start, I think. I think, we struggle with this, since we try to accomplish something unusual in the Python ecosystem. Usually one would write a thing, be it an application or program or a library, which depends on other libraries. And these dependencies, one would simply note in the setup.py. Installing the project should be: pip install This is most easy, when all dependencies are already PyPI, the Python Package Index (https://pypi.python.org/pypi). |
Maybe we could have test_install_script.py were we compare travis.yml and README.md |
I have no real solution for this ... but ... in principle we should try to work towards making the install as easy as: Then this becomes a non-issue |
I'd like to see, what is needed to make this repo even easer to install so I assign this one to me |
Still I had no time to work on this ... volunteers to take this over? |
In order to guaranty that installation procedure is the same in both files we should have the README and travis.yaml linked.
I propose that the README is built from the travis.yml or the other way around (if possible).
Do you have any suggestions for that ?
The text was updated successfully, but these errors were encountered: