Skip to content

Syntax error in pip 9 #4077

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

Closed
btimby opened this issue Nov 3, 2016 · 3 comments
Closed

Syntax error in pip 9 #4077

btimby opened this issue Nov 3, 2016 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@btimby
Copy link

btimby commented Nov 3, 2016

  • Pip version: 9.0
  • Python version: 2.7.2
  • Operating System: Fedora 20

Description:

I am packaging an RPM which includes pip. RPM bytecompiles *.py files as part of the packaging process. This fails with the message below. If I package pip 8.1.2 all works as expected (and as it has until the release of pip 9.0).

What I've run:

+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Compiling /home/btimby/rpmbuild/BUILDROOT/foobar-1.1-22.x86_64/usr/local/upgrayedd/venv/lib/python2.7/site-packages/pip/_vendor/html5lib/treewalkers/etree.py ...
  File "/usr/local/foobar/venv/lib/python2.7/site-packages/pip/_vendor/html5lib/treewalkers/etree.py", line 13
    from pip._vendor. import string_types
                           ^
SyntaxError: invalid syntax

error: Bad exit status from /var/tmp/rpm-tmp.CAeMne (%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.CAeMne (%install)
make: *** [rpm] Error 1
@xavfernandez
Copy link
Member

Thanks @btimby for your report but this is a duplicate of #4059.

@btimby
Copy link
Author

btimby commented Nov 3, 2016

Sorry, I looked but did not see #4059

@rudyvogt
Copy link

rudyvogt commented Nov 7, 2016

Just tested 9.0.1 seems to work 100% - Great work for fixing it so quickly

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

3 participants