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

auditwheel crash on current image #230

Closed
whs opened this issue Oct 2, 2018 · 6 comments
Closed

auditwheel crash on current image #230

whs opened this issue Oct 2, 2018 · 6 comments

Comments

@whs
Copy link

whs commented Oct 2, 2018

The auditwheel command does not work on the current image (quay.io/pypa/manylinux1_x86_64@sha256:7967d9758d679ce31d0c314a24752550bc41c612b35e07d9f4ce42ed898c165e)

[root@4bfc75c75596 wheelhouse]# auditwheel show protobuf-3.6.1-py2.py3-none-any.whl
Traceback (most recent call last):
  File "/usr/local/bin/auditwheel", line 11, in <module>
    sys.exit(main())
  File "/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/main.py", line 49, in main
    rval = args.func(args, p)
  File "/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/main_show.py", line 22, in execute
    from .wheel_abi import analyze_wheel_abi
  File "/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/wheel_abi.py", line 9, in <module>
    from .genericpkgctx import InGenericPkgCtx
  File "/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/genericpkgctx.py", line 1, in <module>
    from .wheeltools import InWheelCtx
  File "/opt/_internal/cpython-3.6.6/lib/python3.6/site-packages/auditwheel/wheeltools.py", line 14, in <module>
    from wheel.util import urlsafe_b64encode, open_for_csv, native  # type: ignore
ImportError: cannot import name 'open_for_csv'
@whs
Copy link
Author

whs commented Oct 2, 2018

Seems to be due to pypa/auditwheel#102 . Waiting on that issue to be fixed and new image released.

@whs
Copy link
Author

whs commented Oct 2, 2018

Should be fixed by #229

@whs whs closed this as completed Oct 2, 2018
@trishankatdatadog
Copy link
Member

trishankatdatadog commented Oct 2, 2018 via email

@njsmith
Copy link
Member

njsmith commented Oct 2, 2018 via email

@matthew-brett
Copy link
Contributor

Yes, seconded - there wasn't any easy way to know what was going to happen here.

Having said that, it might be worth adding a policy of holding off on tool updates for a bit.

@sidarthagracias
Copy link

Do we know when a new image might come out. It seems like since the only images published is "latest" which gets overwritten, we don't have access to an old good image. Is that correct, do we just have to wait for the next image to come out?

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

No branches or pull requests

5 participants