setup.py

I'd like to make use of someone else's python utility, foobartools , whose native environment is linux. Foobartools is pure python so there's no reason it can't be used on Windows, where I am. In their setup.py they're using the older style scripts=['bin/foobar'], . Running pip install -e b:\code\foobar creates a file called foobar in %pythonhome%\Scripts , but Windows doesn't know about it even though Scripts is in PATH. To use it I need to make a @python %pythonhome%\scripts\foobar batch file. This works but is non-optimal ( ctrl-c handling is ugly for instance). I know that if I add the

I have a EC2 instance created on AWS and use PuTTY to connect to it. I'm unable to install MySQL-python using python pip command as follows: pip install MySQL-python (via root privileges) Here is the console output of the error Collecting MySQL-python Using cached MySQL-python-1.2.5.zip Complete output from command python setup.py egg_info: sh: mysql_config: command not found Traceback (most recent call last): File "<string>", line 20, in <module> File "/tmp/pip-build-JGbAEI/MySQL-python/setup.py", line 17, in <module> metadata, options = get_config() File "/tmp/pip-build-JGbAEI/MySQL-python

There are quite a few people wondering for an alternative to dependency links in the setup.py (activated with the pip flag --process-dependency-links ): What is the alternative to using --process-dependency-links with pip , Depend on git repository in setup.py . Basically, I got bitten by the deprecation warning: "DEPRECATION: Dependency Links processing has been deprecated and will be removed in a future release." Some people have suggested using requirements.txt , however that is not an alternative as it is meant to provide an entire environment, usually more associated with development. The

I'm following a Flask tutorial that has me using virtualenv , and with it I built an app directory tree that looks like this: app/ |__app/ |__app.egg-inf/ |__setup.py |__venv/ Inside my venv the tutorial tells me to run pip install -e . which appears to be using my setup.py to install dependencies and my application. Why does the tutorial have me running pip install -e . ? Why not python setup.py install ? What are the differences? (FWIW, export FLASK_APP=app; flask run works fine after pip install -e . but doesn't work after a python setup.py install ) First, the commands you mention are not

In a project, I have e.g. two different packages, How can I use the setup.py to install these two packages in the Google's Colab, so that I can import the packages? You can use !setup.py install to do that. Colab is just like a Jupyter notebook. Therefore, we can use the ! operator here to install any package in Colab. What ! actually does is, it tells the notebook cell that this line is not a Python code, its a command line script . So, to run any command line script in Colab, just add a ! preceding the line. For example: !pip install tensorflow . This will treat that line (here pip install

I've got a python module that calls an external binary, built from C source. The source for that external executable is part of my python module, distributed as a .tar.gz file. Is there a way of unzipping, then compiling that external executable, and installing it using setuptools/setup.py? What I'd like to achieve is: installing that binary into virtual environments manage compilation/installation of the binary using setup.py install , setup.py build etc. making the binary part of my python module, so that it can be distributed as a wheel without external dependencies Solved in the end by

I want to create a setup.py which would install my files into custom directories. I have a certain prefix, where I would like to get the following result: /my/prefix/ bin/ script.sh libexec/ one.py two.py ... lib/pythonX.Y/site-packages/ package/... My initial project is following: / script.sh one.py two.py ... setup.py package/... __init__.py ... What would be the best way to achieve that? I would like to be able to install it later with something like: python setup.py install --prefix=/my/prefix I can get "package" nicely installed in the correct directory as lib/pythonX.Y/site-packages