mirror of
https://github.com/asciinema/asciinema.git
synced 2026-04-25 07:55:51 +03:00
[GH-ISSUE #174] asciinema 1.3 does not provide a wrapper #750
Labels
No labels
bug
compatibility
feature request
fit for beginners
help wanted
hosting
idea
improvement
packaging
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asciinema#750
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @carnager on GitHub (Aug 1, 2016).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/174
Since asciinema is now installed in python's site-packages directory, the binary won't be in $PATH anymore.
asciinema should probably provide a little wrapper to be placed in $PATH. I guess setup.py is the place to do this.
@ku1ik commented on GitHub (Aug 3, 2016):
setup.py has it configured: https://github.com/asciinema/asciinema/blob/master/setup.py#L29
In all systems I checked asciinema installation it was correctly creating a wrapper script.
@fornwall commented on GitHub (Aug 31, 2016):
When I installed from source with
python3.5 setup.py install, the resulting installation did not have the asciinema command-line wrapper.I noticed the warnings
I had to
pip3 install setuptools- after that the installation correctly set up the bin/asciinema wrapper.I don't know enough about python packaging to know if this is the expected behaviour or not.
@ku1ik commented on GitHub (Aug 31, 2016):
Does anyone know a way to make it generate a wrapper in a reliable way (also in the absence of setuptools)?
@ku1ik commented on GitHub (Mar 9, 2017):
This has been solved in #179, the fix will be part of the next release.
@ku1ik commented on GitHub (Apr 11, 2017):
1.4.0 has been just released, including fix (#179) by @jakubjedelsky.