Setup.cfg migration and CI with Travis #30
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
astrojuanlu
reviewed
Apr 14, 2019
| ], | ||
| long_description=open('README.rst').read() | ||
| ) | ||
| setup(setup_cfg=True) |
Add travis for CI Add src layout Improve setup.cfg and apply isort Add installation requirements to travis Add sudo false Move to Python 3 Improve setup.cfg Update travis configuration Apply black
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I thought it would be interesting to migrate to a
setup.cfgfile. In addition, I added a small.travis.ymlfile so we could apply some kind of CI to the project. My experience with this kind of files is limited, so it would be nice someone else to make an small review of them.Also, some extra requirements are added to the☺️
setup-cfgfile in order documentation be compiled in read the docs