Package Details: python-maybe 0.3.0-1

Git Clone URL: https://aur.archlinux.org/python-maybe.git (read-only, click to copy)
Package Base: python-maybe
Description: See what a program does before deciding whether you really want it to happen.
Upstream URL: https://github.com/p-e-w/maybe
Keywords: python
Licenses: GPLv3
Submitter: kpj
Maintainer: kpj
Last Packager: kpj
Votes: 8
Popularity: 0.000013
First Submitted: 2016-02-06 18:58
Last Updated: 2017-10-20 16:00

Latest Comments

liara commented on 2016-02-06 22:18

It works for me now.

kpj commented on 2016-02-06 21:55

True, if I install it using `pip install maybe` into a virtual env, I get the executable as well.
However, I don't get the executable when installing it via `pip install --target='new_root' maybe`. So for some reason, the `--target` option makes it omit the executable.

I now changed the way I pull the source from pip and it seems to work.

ammonaur commented on 2016-02-06 21:07

When I install via pip, I get a /usr/bin/maybe that looks like this: http://pastebin.com/rBaa0FCi

You didn't get this file in the manual install? When installed the package using
"python setup.py install --prefix=/usr --root='/tmp/_maybe' --optimize=1", I got the following file output: http://pastebin.com/ShPs4zq9

kpj commented on 2016-02-06 20:58

Thanks for your comment, I added the missing dependency.

Regarding the executable, I am not sure how to handle that.
The `setup.py` file simply says
[..]
entry_points={
"console_scripts": [
"maybe = maybe.maybe:main",
],
}
[..]
and a manual install only gives
.
├── maybe
│   ├── __init__.py
│   ├── maybe.py
│   ├── __pycache__
│   │   ├── __init__.cpython-35.pyc
│   │   ├── maybe.cpython-35.pyc
│   │   ├── syscall_filters.cpython-35.pyc
│   │   └── utilities.cpython-35.pyc
│   ├── syscall_filters.py
│   └── utilities.py
└── maybe-0.2.1-py3.5.egg-info
├── dependency_links.txt
├── entry_points.txt
├── installed-files.txt
├── PKG-INFO
├── requires.txt
├── SOURCES.txt
└── top_level.txt
I could of course manually write an executable and place it in `/usr/bin`, but that does not seem like a good idea, does it?

ammonaur commented on 2016-02-06 20:47

This package should depend on python-ptrace [AUR] and should install an executable in /usr/bin.

In order to install the executable, I think install.py should be used instead of pip, like is done in the python-ptrace package: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-ptrace