PyPI ready! #9
Merged
PyPI ready! #9
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
For ignoring files that don't belong in source control
This ensures 2 things: - pydown can be used outside of the project directory - pydown can be crossplatform
- Adds setup.py with pydown entry-point - Adds MANIFEST.in - Adds NOTICE
|
Great job! Thanks! |
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.
This makes pydown ready for the PyPI.
It adds a setup.py file that includes a
pydownentry-point. So, after you install...You can run
pydownas a console script.This also adds the
MANIFEST.in(specifies which files to include) andNOTICE(licenses for vendorized packages) files.The only thing you'll need to do to put this on the PyPI is
$ python setup.py publish.