CI: Use recent Python image to build packages #1790
Merged
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
effigies
force-pushed
the
ci/upgrade_package_build_env
branch
2 times, most recently
from
98ec9a2
to
f0d1e0e
Compare
effigies
force-pushed
the
ci/upgrade_package_build_env
branch
from
f0d1e0e
to
7006e38
Compare
Probably not after this change 👍 |
|
I looked, and it looks like we still have a cython extension. For some reason I thought that had gone with sdcflows. |
|
mmm yeah, that should be gone. |
|
Okay. I'll open a PR to kill it shortly. |
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to oesteban/mriqc
that referenced
this pull request
Sep 25, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
NPann
pushed a commit
to NPann/mriqc
that referenced
this pull request
Dec 12, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
NPann
pushed a commit
to NPann/mriqc
that referenced
this pull request
Dec 12, 2019
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
oesteban
added a commit
to nipreps/nireports
that referenced
this pull request
Feb 28, 2023
Similarly to nipreps/fmriprep#1790, we are changing to the Python 3.7+ docker image to test and deploy the Pypi package since twine has stopped support for python <3.6 since their latest relase 2.0.
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.
Changes proposed in this pull request
Switches to
circleci/python:3.7.4for building packages on, as this should have a long lifetime before we need to upgrade it.The latest twine breaks Python 3.5 but still installs on it, so our current strategy fails. We could pin an older twine, but there doesn't seem much value.
@oesteban I see we're still using manylinux to build wheels. I believe we no longer need that?
Documentation that should be reviewed