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

error: invalid command 'bdist_wheel' #1

Open
BluesGuy opened this issue Nov 27, 2014 · 8 comments
Open

error: invalid command 'bdist_wheel' #1

BluesGuy opened this issue Nov 27, 2014 · 8 comments

Comments

@BluesGuy
Copy link

From https://github.com/PySide/shiboken-setup#building-shiboken-on-a-windows-system

When I try to run the command:
c:\Python27\python.exe setup.py bdist_wheel --version=1.2.2 --qmake=c:\Qt\4.8.5\bin\qmake.exe

from the "Building Shiboken distribution from git repository section", step 3, I keep getting an error "error: invalid command 'bdist_wheel'"

Also, its confusing because in step 2 I'm instructed to switch to the shiboken-setup directory, but step 3 shows the command being run from the C:\ root directory.

I get the error in both cases ( when run from C:\ and from C:\shiboken-setup

@lck
Copy link
Contributor

lck commented Nov 27, 2014

The bdist_wheel command requires the wheel package to be installed in Python.
Did you install the "wheel" package as described in "Installing prerequisities" -> "Step 7." ?

c:> c:\Python27\Scripts\pip install wheel

@BluesGuy
Copy link
Author

Yes I did. I just ran it again to make sure. Executed without any errors and then returned me to the C prompt. How do I check that it actually installed?

@lck
Copy link
Contributor

lck commented Nov 27, 2014

Check if file "c:\Python27\Scripts\wheel.exe" exists
Then run "c:\Python27\python.exe setup.py --help-commands --ignore-git" in "C:\shiboken-setup" folder and check the output - note the "bdist_wheel" text:
...
Extra commands:
saveopts save supplied options to setup.cfg or other config file
develop install package in 'development mode'
upload_docs Upload documentation to PyPI
test run unit tests after in-place build
setopt set an option in setup.cfg or another config file
install_egg_info Install an .egg-info directory for the package
rotate delete older distributions, keeping N newest files
bdist_wheel create a wheel distribution
egg_info create a distribution's .egg-info directory
alias define a shortcut to invoke one or more commands
easy_install Find/get/install Python packages
bdist_egg create an "egg" distribution
...

@BluesGuy
Copy link
Author

First, thank you for your detailed help.

"Check if file "c:\Python27\Scripts\wheel.exe" exists" It doesn't.

Even though I just ran" c:\Python27\Scripts\pip install wheel " without error. Seeing this, I went back to the instructions and re-ran " pip install --use-wheel -U Shiboken " which appeared to successfully execute:

image

So, still no "c:\Python27\Scripts\wheel.exe" . What would be my next step?

@BluesGuy
Copy link
Author

BluesGuy commented Dec 1, 2014

Any suggestions? Anyone?

@lck
Copy link
Contributor

lck commented Dec 2, 2014

This looks like you have problem installing wheel package in general.
Please try to install any python wheel package to be sure it's not the Shiboken distribution problem.
Thanks

@ftomassetti
Copy link

I have the executable, but still I get the error. I added the executable to my path and I launching I get:

fixme:ntdll:NtCreateJobObject stub: 0x33f958 1f001f <null>
fixme:ntdll:NtQueryInformationJobObject stub: 0xdead 9 0x33fc68 112 0x33fc0c
Fatal error in launcher: Job information querying failed

Consider that I am using wine

@shenjiefeng
Copy link

shenjiefeng commented May 18, 2017

ref
http://software-engineer.gatsbylee.com/python-pip-error-invalid-command-bdist_wheel/

How to resolve this issue?

There could be two approaches.

  1. using the pip packages from CentOS 6 which is 1.3.1.

$ python -m pip uninstall pip setuptools
$ yum install python-pip python-setuptools

  1. upgrading python setuptool module

pip install setuptools --upgrade

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

4 participants