Skip to content
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

Rebuild for pypy #100

Merged
merged 10 commits into from
Mar 21, 2020
Merged

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update pypy.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:

And potentially more.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://circleci.com/gh/regro/circle_worker/15031, please use this URL for debugging

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@bollwyvl
Copy link
Contributor

bollwyvl commented Mar 14, 2020

Still something else going on...

Output in format: Requested package -> Available versions

Package python conflicts for:
python_abi==3.6[build=_pypy36_pp73]
setuptools[version='>=18.5'] -> certifi[version='>=2016.9.26'] -> python_abi=2.7[build=
_cp27mu]
curio -> python[version='>=3.6'] -> python_abi==3.6[build=_pypy36_pp73]
trio -> python[version='>=3.6,<3.7.0a0'] -> python_abi==3.6[build=
_pypy36_pp73]

Package certifi conflicts for:
matplotlib -> setuptools -> certifi[version='>=2016.09|>=2016.9.26']
pip -> setuptools -> certifi[version='>=2016.09|>=2016.9.26']
nose[version='>=0.10.1'] -> setuptools -> certifi[version='>=2016.09|>=2016.9.26']
requests -> certifi[version='>=2017.4.17']
requests -> urllib3[version='>=1.21.1,<1.26,!=1.25.0,!=1.25.1'] -> certifi
setuptools[version='>=18.5'] -> certifi[version='>=2016.09|>=2016.9.26']
pygments -> setuptools -> certifi[version='>=2016.09|>=2016.9.26']

Package decorator conflicts for:
traitlets[version='>=4.2'] -> decorator
nbformat -> traitlets[version='>=4.1'] -> decorator
decorator

Package enum34 conflicts for:
matplotlib -> pyqt -> enum34
nbformat -> traitlets[version='>=4.1'] -> enum34
traitlets[version='>=4.2'] -> enum34

Package numpy conflicts for:
matplotlib -> matplotlib-base==3.1.0=py37h5f35d83_0 -> numpy[version='>=1.11.3,<2.0a0|>=1.9.3,<2.0a0']
numpy
matplotlib -> numpy[version='1.10.|1.11.|>=1.14.6,<2.0a0']

Package gdbm conflicts for:
python_abi==3.6[build=*_pypy36_pp73] -> pypy3.6=7.3 -> gdbm[version='>=1.18,<1.19.0a0']
python[version='>=3.6,<3.7.0a0'] -> pypy3.6=7.3.0 -> gdbm[version='>=1.18,<1.19.0a0']

Package functools32 conflicts for:
matplotlib -> functools32
nbformat -> jsonschema[version='>=2.4,!=2.5.0'] -> functools32
Note that strict channel priority may have removed packages required for satisfiability.

@bollwyvl
Copy link
Contributor

Hid yet more deps, and it built locally with...

conda build recipe -c conda-forge -m .ci_support/linux_python3.6.____73_pypy.yaml --clobber-file .ci_support/clobber_linux_python3.6.____73_pypy.yaml

...so hopefully this sorts it!

@bollwyvl
Copy link
Contributor

Here's as reduced an error set as I can seem to get:

Output in format: Requested package -> Available versions

Package python_abi conflicts for:
decorator -> python -> python_abi==3.6[build=*_pypy36_pp73]
pip -> python -> python_abi[version='3.6.*|3.6|3.8.*|3.7.*',build='*_cp37m|*_cp36m|*_pypy36_pp73|*_cp38']
setuptools[version='>=18.5'] -> python_abi[version='3.6|3.6.*|3.8.*|3.7.*',build='*_pypy36_pp73|*_cp37m|*_cp38|*_cp36m']
python_abi==3.6[build=*_pypy36_pp73]
setuptools[version='>=18.5'] -> certifi[version='>=2016.9.26'] -> python_abi=2.7[build=*_cp27mu]
prompt_toolkit[version='>=2.0.0,<4,!=3.0.0,!=3.0.1'] -> python[version='>=3.6'] -> python_abi==3.6[build=*_pypy36_pp73]
backcall -> python -> python_abi==3.6[build=*_pypy36_pp73]
python[version='>=3.6,<3.7.0a0'] -> python_abi==3.6[build=*_pypy36_pp73]
traitlets[version='>=4.2'] -> python_abi[version='2.7.*|3.6|3.6.*|3.8.*|3.7.*',build='*_cp37m|*_cp27mu|*_pypy36_pp73|*_cp38|*_cp36m']
pygments -> python[version='>=3.5'] -> python_abi[version='3.6.*|3.6|3.8.*|3.7.*',build='*_cp37m|*_cp36m|*_pypy36_pp73|*_cp38']
pexpect -> python[version='>=3.6,<3.7.0a0'] -> python_abi==3.6[build=*_pypy36_pp73]
jedi[version='>=0.10'] -> python_abi[version='2.7.*|3.6|3.6.*|3.8.*|3.7.*',build='*_cp37m|*_cp27mu|*_cp38|*_pypy36_pp73|*_cp36m']
pickleshare -> python[version='>=3.6,<3.7.0a0'] -> python_abi[version='2.7.*|3.6.*|3.6|3.7.*|3.8.*',build='*_cp27mu|*_pypy36_pp73|*_cp37m|*_cp38|*_cp36m']

Package python conflicts for:
pygments -> setuptools -> python[version='>=3.8,<3.9.0a0']
setuptools[version='>=18.5'] -> python_abi=3.8[build=*_cp38] -> python[version='3.7.*|3.8.*']
python[version='>=3.6,<3.7.0a0']
pygments -> python[version='2.7.*|3.5.*|3.6.*|>=3.5|3.4.*|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=2.7,<2.8.0a0|>=3.5,<3.6.0a0']
prompt_toolkit[version='>=2.0.0,<4,!=3.0.0,!=3.0.1'] -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|>=3.7,<3.8.0a0']
decorator -> python[version='2.7.*|3.5.*|3.6.*|3.4.*|>=3.7,<3.8.0a0|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0']
pip -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.8,<3.9.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0|3.4.*']
setuptools[version='>=18.5'] -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0|3.4.*']
traitlets[version='>=4.2'] -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.5,<3.6.0a0']
prompt_toolkit[version='>=2.0.0,<4,!=3.0.0,!=3.0.1'] -> pygments -> python[version='3.4.*|>=3.5|>=3.8,<3.9.0a0']
jedi[version='>=0.10'] -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0']
jedi[version='>=0.10'] -> parso[version='>=0.5.2'] -> python[version='3.4.*|3.7.*|3.8.*']
pexpect -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0|3.4.*']
pexpect -> ptyprocess[version='>=0.5'] -> python
pygments -> setuptools -> certifi[version='>=2016.09|>=2016.9.26']

Package decorator conflicts for:
traitlets[version='>=4.2'] -> decorator

@bollwyvl
Copy link
Contributor

Perhaps https://github.com/conda-forge/pexpect-feedstock needs to be built for pypy first?

@isuruf
Copy link
Member

isuruf commented Mar 14, 2020

If you do conda build recipe -c conda-forge -m .ci_support/linux_python3.6.____73_pypy.yaml --clobber-file .ci_support/clobber_linux_python3.6.____73_pypy.yaml and you see packages from defaults coming in, then those needs to be built first. We are using strict channel priority with PyPy builds as in https://conda-forge.org/blog/2020/03/10/pypy

@isuruf
Copy link
Member

isuruf commented Mar 16, 2020

Restarted the builds and tests pass now

@bollwyvl
Copy link
Contributor

working on merge conflicts...

# - pygments
# - requests
# - testpath
# - trio
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way for us to keep these for cpython @isuruf?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +48 to +58
# TODO: restore after pypy migration
# - curio # [unix]
# - ipykernel
# - matplotlib
# - nbformat
# - nose >=0.10.1
# - numpy
# - pygments
# - requests
# - testpath
# - trio
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# TODO: restore after pypy migration
# - curio # [unix]
# - ipykernel
# - matplotlib
# - nbformat
# - nose >=0.10.1
# - numpy
# - pygments
# - requests
# - testpath
# - trio
# TODO: add after pypy migration
- curio # [unix and python_impl == "cpython"]
- nbformat # [python_impl == "cpython"]
- nose >=0.10.1 # [python_impl == "cpython"]
- numpy # [python_impl == "cpython"]
- pygments # [python_impl == "cpython"]
- requests # [python_impl == "cpython"]
- testpath # [python_impl == "cpython"]
- ipykernel # [python_impl == "cpython"]
- trio # [python_impl == "cpython"]
- matplotlib !=3.2.0 # [python_impl == "cpython"]

Comment on lines +83 to +85
# TODO: restore after pypy migration
# - NOSE_EXCLUDE="{{ nose_exclude }}" iptest # [unix]
# - set NOSE_EXCLUDE="{{ nose_exclude }}" && iptest # [win]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# TODO: restore after pypy migration
# - NOSE_EXCLUDE="{{ nose_exclude }}" iptest # [unix]
# - set NOSE_EXCLUDE="{{ nose_exclude }}" && iptest # [win]
# TODO: add after pypy migration
- NOSE_EXCLUDE="{{ nose_exclude }}" iptest # [unix and python_impl == "cpython"]
- set NOSE_EXCLUDE="{{ nose_exclude }}" && iptest # [win and python_impl == "cpython"]

@jakirkham
Copy link
Member

Made some suggestions so testing can be restored for cpython at least. pypy will still need to wait for the test dependencies to be migrated.

@bollwyvl
Copy link
Contributor

LGTM

@bollwyvl bollwyvl merged commit d798af0 into conda-forge:master Mar 21, 2020
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the rebuild-pypy-0-1 branch March 21, 2020 14:13
@bollwyvl bollwyvl mentioned this pull request Jun 27, 2020
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants