-
Notifications
You must be signed in to change notification settings - Fork 90
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
Provide example on skipping certain Python versions #29
Comments
Sorry, just realized this should probably go to the https://github.com/pypa/python-manylinux-demo repo, right? |
Cool. Is that something you would be able to contribute? It should just be a little bit of bash scripting. Sent from my iPhone
|
I use this for my own library at the moment: PYBINS=(
"/opt/python/cp27-cp27m/bin"
"/opt/python/cp27-cp27mu/bin"
"/opt/python/cp33-cp33m/bin"
"/opt/python/cp34-cp34m/bin"
"/opt/python/cp35-cp35m/bin"
)
# and later...
for PYBIN in ${PYBINS[@]}; do
# ...
done |
There's a few different options depending on what exactly you want... for example I guess it might be useful to have some example that explicitly uses a blacklist and gets all new variants by default - obviously projects can do what they want, but I think everyone's better off in the long run if we make it easy to add new interpreters and if projects that don't care that much then get automatically opted in. Possibly the best is something like
(Or this could avoid an indent level if bash has a |
I've been wrapping the |
@njsmith Bash has a
|
In my library I don't support Python 2.6 anymore, and I was wondering what the best way is to skip this version in the build-wheels.sh script, instead of the loop
for PYBIN in /opt/python/*/bin
.The text was updated successfully, but these errors were encountered: