-
Notifications
You must be signed in to change notification settings - Fork 35
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
Installation into virtualenv doesn't install the saunter executable #53
Comments
Bump. I'm getting the same thing using pyenv. After doing a bit of research it seems you aren't supposed to provide a script as an entry point:
See: http://python-packaging.readthedocs.io/en/latest/command-line-scripts.html If I am understanding this, you need wrap all your code inside saunter/main.py in a 'main' function and then change your entry point from:
to:
|
Found after uploading a test release to test pypi. Pip install then generated an error: Invalid script entry point: <ExportEntry leow = leo.core.runLeo.run:None []> for req: leo - A callable suffix is required. Which lead me to Element-34/py.saunter#53 and the dot-colon mistake.
Found after uploading a test release to test pypi. Pip install then generated an error: Invalid script entry point: <ExportEntry leow = leo.core.runLeo.run:None []> for req: leo - A callable suffix is required. Which lead me to Element-34/py.saunter#53 and the dot-colon mistake.
When I install into a virtualenv using Pip 8.1.2, I get the error:
Invalid script entry point: <ExportEntry saunter = saunter.main:None []> for req: saunter - A callable suffix is required. Cf https://packaging.python.org/en/latest/distributing.html#console-scripts for more information.
I don't encounter this when installing into the OS Python.
The text was updated successfully, but these errors were encountered: