2013/12/10 Laurent Bristiel <
lau...@bristiel.com>:
> Something still not clear to me, maybe someone could enlight me.
> Let's say I include (unziped) Robot Framework and (unziped) Requests in GIT,
> then once they are checked out on a machine, can I use them directly without
> any further "install"?
> (calling folder_with_pybot/pybot --pythonpath folder_with_requests)
> or do I have to go through some "install" step before beeing able to use
> Robot and Requests.
I don't know about Requests, but with Robot you don't need anything
else than `robot` package that contains the framework source code.
This package doesn't contain interpreter specific start-up scripts
like `pybot`, `jybot` or `rebot`, but you can run `robot/run.py` or
`robot/rebot.py` directly. Obviously you can create the familiar
start-up scripts too if you want.
For more details about manual installation and the direct entry points
see the User Guide:
http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#manual-installation
http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#direct-entry-points
> Putting it another way, when I do "python setup.py install", does it just
> move the files around or does it do something else?
This depends does the package you install contain only Python code or
does it also contain C code or something else. Pure-Python packages
are, AFAIK, just copied to appropriate location, but C needs to be
compiled. In the latter case the resulting binary is obviously also
operating system dependent. In other words, you should be able to put
all your pure-Python packages to version control, and require users
only to install possible C-based dependencies using appropriate binary
installers.