what am I doing wrong?

C:\>pipx install pyjokes
  installed package pyjokes 0.5.0, Python 3.7.2
  These binaries are now globally available
    - pyjoke
    - pyjokes
  Note: 'C:\\Users\\Nebu\\.local\\bin' is not on your PATH environment variable. These binaries will not be globally accessible until your PATH is updated. Run `pipx ensurepath` to automatically add it, or manually modify your PATH in your shell's config file (i.e. ~/.bashrc).
done!

C:\>pipx run pyjoke
Assuming binary is 'pyjoke.exe' (Windows only)
Command "python setup.py egg_info" failed with error code 1 in C:\Users\Nebu\AppData\Local\Temp\pip-install-yygzrenk\nltk\
'C:\\Users\\Nebu\\.local\\pipx\\.cache\\8c2f5730a463fd9\\Scripts\\python.exe -m pip install pyjoke -q' failed

C:\>pyjoke
'pyjoke' is not recognized as an internal or external command,
operable program or batch file.

C:\>pip list
Package    Version  Location
---------- -------- --------------------------------
pip        19.0.3
pipx       0.12.3.2 c:\projects\python\_helping\pipx
setuptools 40.8.0
wheel      0.33.1

C:\>pipx list
venvs are in C:\Users\Nebu\.local\pipx\venvs
binaries are exposed on your $PATH at C:\Users\Nebu\.local\bin
   package pyjokes 0.5.0, Python 3.7.2
    - pyjoke
    - pyjokes

C:\>pipx --version
0.12.3.2

C:\>

[Laurentiu-Andronache]

Thanks, you’re both awesome. The pyjokes dude said he’ll push a new version with a fix when he gets a chance.

[sahensley]

Sure thing. I get the same results as above on Windows while using both pipx and a standard venv. It’s not a pipx issue but a pyjokes packaging issue.

It looks like the setup.py file is using the legacy scripts keyword instead of entry_points with console_scripts. That’s why .exes aren’t being generated on the Windows install.

The automatic script creation section of the setuptools docs has the details.