setup.py for sdist #240
Merged
setup.py for sdist #240
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
Closed
ax3l
force-pushed
the
topic-setupPy
branch
3 times, most recently
from
8135502 to
81033ba
Compare
ax3l
force-pushed
the
topic-setupPy
branch
13 times, most recently
from
b375922 to
0e0934a
Compare
ax3l
commented
Oct 3, 2018
setup.py
Outdated
| 'Topic :: Scientific/Engineering', | ||
| 'Topic :: Database :: Front-Ends', | ||
| 'Programming Language :: C++', | ||
| 'Programming Language :: Python', |
There was a problem hiding this comment.
this line probably needs to go to make sure it's really just matching Python 3 on PyPI and a pip2 install openpmd-api can fail early.
There was a problem hiding this comment.
uh, it's python_requires for setuptools on PyPI.
(ref)
ax3l
force-pushed
the
topic-setupPy
branch
5 times, most recently
from
cff44ae to
ac83915
Compare
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.
Developed a
setup.pyfor python-level install from source (actually compiling!).I am not sure it it does more harm than good to expose this to the user or if I should hide a perfectly tailored,
PyPIdistribution building only,setup.pydeep in the source tree. Or I just keep this not as a documented (aka recommended) install method.I will keep this here for now for documentation purposes.Done:
sdistIntentionally skipepd:
bdist_wheel: fully static, non-MPImingw(nostd::futuresupport as of 7.0) -> VC 2015? PEP?