Update setup.py to allow deployments to PyPI - #27 #28
Conversation
This file contains hidden or 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
doctorlard
force-pushed
the
pypi-setup
branch
from
982d2e6 to
c574bd3
Compare
Author
|
Pushed a better commit, with pbr and setup.cfg instead. |
doctorlard
force-pushed
the
pypi-setup
branch
from
c574bd3 to
d894eb6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 possibly helps with pushing to PyPI. The "OData" name is taken (PyPI is case insensitive) so I've tested it using "python-odata" and using our Catalyst account to do a test upload onto test-pypi. For some reason the Markdown README didn't translate, which the
long_description_content_typesetup parameter is supposed to handle.