I have a new library that has to include a lot of subfolders of small datafiles, and I&#39;m trying to add them as package data.  Imagine I have my library as so:

     library
        - foo.py
        - bar.py
     data
       subfolderA
          subfolderA1
          subfolderA2
       subfolderB
          subfolderB1 
          ...

I want to add all of the data in all of the subfolders through setup.py, but it seems like I manually have to go into every single subfolder (there are 100 or so) and add an __init__.py file.  Furthermore, will setup.py find these files recursively, or do I need to manually add all of these in setup.py like:

    package_data={
      &#39;mypackage.data.folderA&#39;: [&#39;*&#39;],
      &#39;mypackage.data.folderA.subfolderA1&#39;: [&#39;*&#39;],
      &#39;mypackage.data.folderA.subfolderA2&#39;: [&#39;*&#39;]
       },

I can do this with a script, but seems like a super pain.  How can I achieve this in setup.py?

PS, the hierarchy of these folders is important because this is a database of material files and we want the file tree to be preserved when we present them in a GUI to the user, so it would be to our advantage to keep this file structure intact.

How to add package data recursively in Python setup.py?

Is there a way to use an extra Python package index (ala `pip --extra-index-url pypi.example.org mypackage`) with `setup.py` so that running `python setup.py install` can find the packages hosted on `pypi.example.org`?

Using an extra python package index url with setup.py

I have installed a python package with `python setup.py install`.

How do I uninstall it?

python setup.py uninstall

I tried to install the Python package [dulwich](https://pypi.python.org/pypi/dulwich):

&lt;!-- language-all: lang-none --&gt;

    pip install dulwich

But I get a cryptic error message:

    error: Unable to find vcvarsall.bat

The same happens if I try installing the package manually:

    &gt; python setup.py install
    running build_ext
    building &#39;dulwich._objects&#39; extension
    error: Unable to find vcvarsall.bat

error: Unable to find vcvarsall.bat

I started working with Python. I&#39;ve added `requirements.txt` and `setup.py` to my project. But, I am still confused about the purpose of both files. I have read that `setup.py` is designed for redistributable things and that `requirements.txt` is designed for non-redistributable things.  But I am not certain this is accurate.

How are those two files truly intended to be used?

requirements.txt vs setup.py

My Python package has a `setup.py` which builds fine locally on Ubuntu Trusty and on a fresh Vagrant Ubuntu Trusty VM when I provision it like this:

    sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
    curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
    sudo -H pip install setuptools wheel virtualenv --upgrade

But when I do the same on a Travis CI Trusty Beta VM:

    - sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
    - curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
    - sudo -H pip install setuptools wheel virtualenv --upgrade

I get:

    python2.7 setup.py bdist_wheel
    usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
       or: setup.py --help [cmd1 cmd2 ...]
       or: setup.py --help-commands
       or: setup.py cmd --help
    error: invalid command &#39;bdist_wheel&#39;

This https://stackoverflow.com/questions/26664102/why-can-i-not-create-a-wheel-in-python is related but note I am installing wheel and upgrading setuptools.

Why is python setup.py saying invalid command &#39;bdist_wheel&#39; on Travis CI?

I have an external package I want to install into my python virtualenv from a tar file.
What is the best way to install the package?

I&#39;ve discovered 2 ways that can do it:

 1. Extract the tar file, then run `python setup.py install` inside of the extracted directory.
 2. `pip install packagename.tar.gz` from example # 7 in https://pip.pypa.io/en/stable/reference/pip_install/#examples

Is if there is any difference doing them in these 2 ways.

Difference between &#39;python setup.py install&#39; and &#39;pip install&#39;

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&#39;s Colab, so that I can import the packages?

How do I install Python packages in Google&#39;s Colab?

Is it possible to specify a post-install Python script file as part of the setuptools setup.py file so that a user can run the command:
    
    python setup.py install

on a local project file archive, or

    pip install &lt;name&gt;

for a PyPI project and the script will be run at the completion of the standard setuptools install?  I am looking to perform post-install tasks that can be coded in a single Python script file (e.g. deliver a custom post-install message to the user, pull additional data files from a different remote source repository).

I came across [this SO answer from several years ago][1] that addresses the topic and it sounds as though the consensus at that time was that you need to create an install subcommand.  If that is still the case, would it be possible for someone to provide an example of how to do this so that it is not necessary for the user to enter a second command to run the script?


  [1]: https://stackoverflow.com/questions/250038/how-can-i-add-post-install-scripts-to-easy-install-setuptools-distutils

Post-install script with Python setuptools

I want to install setup file of twilio. When I install it through given command it is given me an error:
&gt;No module named setuptools. 

Could you please let me know what should I do?

I am using `python 2.7` 


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Python27&gt;python D:\test\twilio-twilio-python-26f6707\setup.py install
    Traceback (most recent call last):
      File &quot;D:\test\twilio-twilio-python-26f6707\setup.py&quot;, line 2, in &lt;module&gt;
        from setuptools import setup, find_packages
    ImportError: No module named setuptools


No module named setuptools

I&#39;m using pip with virtualenv to package and install some Python libraries.  

I&#39;d imagine what I&#39;m doing is a pretty common scenario.  I&#39;m the maintainer on several libraries for which I can specify the dependencies explicitly.  A few of my libraries are dependent on third party libraries that have transitive dependencies over which I have no control.

What I&#39;m trying to achieve is for a `pip install` on one of my libraries to download/install all of its upstream dependencies.  What I&#39;m struggling with in the pip documentation is if/how [requirements files][1] can do this on their own or if they&#39;re really just a supplement to using `install_requires`.

Would I use `install_requires` in all of my libraries to specify dependencies and version ranges and then only use a requirements file to resolve a conflict and/or freeze them for a production build?

Let&#39;s pretend I live in an imaginary world (I know, I know) and my upstream dependencies are straightforward and guaranteed to never conflict or break backward compatibility. Would I be compelled to use a pip requirements file at all or just let pip/setuptools/distribute install everything based on `install_requires`?

There are a lot of similar questions on here, but I couldn&#39;t find any that were as basic as when to use one or the other or using them both together harmoniously.

  [1]: http://www.pip-installer.org/en/latest/cookbook.html#requirements-files

When to use pip requirements file versus install_requires in setup.py?

There are basically two ways to install Python console scripts to my path by `setup.py`:

    setup(
        ...
        entry_points = {
            &#39;console_scripts&#39;: [
                &#39;foo = package.module:func&#39;,
            ],
        }
    )

and

    setup(
        ...
        scripts = [
            &#39;scripts/myscript.sh&#39;
        ]
    )

What are the differences? I see the first approach allows me to choose nice, specific name for my script, but are there any other differences? Different original purposes, compatibility (setuptools, distutils, ...?), usage, ...? I am quite confused and a nice elaborated reply could help me (and probably also others) to properly understand all this.

**Update:** Since I asked the question [PyPA](https://www.pypa.io/) published [these cool docs on the topic](https://python-packaging-user-guide.readthedocs.io/guides/distributing-packages-using-setuptools/#scripts).

Difference between entry_points/console_scripts and scripts in setup.py?

I am trying to make a python package which I want to install using `pip install .` locally. The package name is listed in `pip freeze` but `import &lt;package&gt;` results in an error `No module named &lt;package&gt;`. Also the site-packages folder does only contain a dist-info folder. `find_packages()` is able to find packages. What am I missing?


    import io
    import os
    import sys
    from shutil import rmtree
    
    from setuptools import find_packages, setup, Command
    
    # Package meta-data.
    NAME = &#39;&lt;package&gt;&#39;
    DESCRIPTION = &#39;description&#39;
    URL = &#39;&#39;
    EMAIL = &#39;email&#39;
    AUTHOR = &#39;name&#39;
    
    # What packages are required for this module to be executed?
    REQUIRED = [
        # &#39;requests&#39;, &#39;maya&#39;, &#39;records&#39;,
    ]
    
    # The rest you shouldn&#39;t have to touch too much :)
    # ------------------------------------------------
    # Except, perhaps the License and Trove Classifiers!
    # If you do change the License, remember to change the Trove Classifier for that!
    
    here = os.path.abspath(os.path.dirname(__file__))
    
    
    
    # Where the magic happens:
    setup(
        name=NAME,
        #version=about[&#39;__version__&#39;],
        description=DESCRIPTION,
        # long_description=long_description,
        author=AUTHOR,
        author_email=EMAIL,
        url=URL,
        packages=find_packages(),
        # If your package is a single module, use this instead of &#39;packages&#39;:
        # py_modules=[&#39;mypackage&#39;],
    
        # entry_points={
        #     &#39;console_scripts&#39;: [&#39;mycli=mymodule:cli&#39;],
        # },
        install_requires=REQUIRED,
        include_package_data=True,
        license=&#39;MIT&#39;,
        classifiers=[
            # Trove classifiers
            # Full list: https://pypi.python.org/pypi?%3Aaction=list_classifiers
            &#39;License :: OSI Approved :: MIT License&#39;,
            &#39;Programming Language :: Python&#39;,
            &#39;Programming Language :: Python :: 2.6&#39;,
            &#39;Programming Language :: Python :: 2.7&#39;,
            &#39;Programming Language :: Python :: 3&#39;,
            &#39;Programming Language :: Python :: 3.3&#39;,
            &#39;Programming Language :: Python :: 3.4&#39;,
            &#39;Programming Language :: Python :: 3.5&#39;,
            &#39;Programming Language :: Python :: 3.6&#39;,
            &#39;Programming Language :: Python :: Implementation :: CPython&#39;,
            &#39;Programming Language :: Python :: Implementation :: PyPy&#39;
        ],
    
    )



pip install . creates only the dist-info not the package

I am trying to understand the difference between `extras_require()` and `install_requires()` in setup.py but couldn&#39;t get it. Both are used for installing Python dependencies, but what&#39;s the difference between them?

Difference between extras_require() and install_requires() in setup.py?

Please prompt me how to pass a user-defined parameter both from the command line and setup.cfg configuration file to distutils&#39; setup.py script. I want to write a setup.py script, which accepts my package specific parameters. For example:

    python setup.py install -foo myfoo


distutils: How to pass a user defined parameter to setup.py?

I&#39;m having troubles with installing packages in Python 3.

I have always installed packages with `setup.py install`. But now, when I try to install the ansicolors package I get:

    importerror &quot;No Module named Setuptools&quot;

I have no idea what to do because I didn&#39;t have setuptools installed in the past. Still, I was able to install many packages with `setup.py install` without setuptools. Why should I get setuptools now?

I can&#39;t even install setuptools because I have Python 3.3 and setuptools doesn&#39;t support Python 3.

Why doesn&#39;t my install command work anymore?


Python 3: ImportError &quot;No Module named Setuptools&quot;

I understand that `setup.py` uses the same `CFLAGS` that were used to build Python. I have a single C extension of ours that is segfaulting. I need to build it **without** `-O2` because `-O2` is optimizing out some values and code so that the core files are not sufficient to pin down the problem.

I just need to modify `setup.py` so that `-O2` is not used.

I&#39;ve read `distutils` documentation, in particular `distutils.ccompiler` and `distutils.unixccompiler` and see how to add flags and libs and includes, but not how to modify the default GCC flags.

Specifically, this is for a legacy product on Python 2.5.1 with a bunch of backports (Fedora 8, yes, I know...). No, I cannot change the OS or Python version and I cannot, without great problems, recompile Python. I just need to build a one off of the C extension for one customer whose environment is the only one segfaulting.

How may I override the compiler (GCC) flags that setup.py uses by default?

Can anyone please explain what `setup.py` is and how it can be configured or used?

What is setup.py?

When I run

      python setup.py sdist

it creates an sdist in my ./dist directory. This includes a &quot;PROJECT-egg.info&quot; file in the zip inside my &quot;dist&quot; folder, which I don&#39;t use, but it doesn&#39;t hurt me, so I just ignore it.

My question is why does it *also* create a &quot;PROJECT-egg.info&quot; folder in my project root directory? Can I make it stop creating this? If not, can I just delete it immediately after creating the sdist?

I&#39;m using the &#39;setup&#39; function imported from setuptools.
WindowsXP, Python2.7, Setuptools 0.6c11, Distribute 0.6.14.

My setup config looks like:

    {&#39;author&#39;: &#39;Jonathan Hartley&#39;,
     &#39;author_email&#39;: &#39;tartley@tartley.com&#39;,
     &#39;classifiers&#39;: [&#39;Development Status :: 1 - Planning&#39;,
                     &#39;Intended Audience :: Developers&#39;,
                     &#39;License :: OSI Approved :: BSD License&#39;,
                     &#39;Operating System :: Microsoft :: Windows&#39;,
                     &#39;Programming Language :: Python :: 2.7&#39;],
     &#39;console&#39;: [{&#39;script&#39;: &#39;demo.py&#39;}],
     &#39;data_files&#39;: [(&#39;Microsoft.VC90.CRT&#39;,
                     [&#39;..\\lib\\Microsoft.VC90.CRT\\Microsoft.VC90.CRT.manifest&#39;,
                      &#39;..\\lib\\Microsoft.VC90.CRT\\msvcr90.dll&#39;])],
     &#39;description&#39;: &#39;Utilities for games and OpenGL graphics, built around Pyglet.\n&#39;,
     &#39;keywords&#39;: &#39;&#39;,
     &#39;license&#39;: &#39;BSD&#39;,
     &#39;long_description&#39;: &quot;blah blah blah&quot;,
     &#39;name&#39;: &#39;pygpen&#39;,
     &#39;options&#39;: {&#39;py2exe&#39;: {&#39;ascii&#39;: True,
                            &#39;bundle_files&#39;: 1,
                            &#39;dist_dir&#39;: &#39;dist/pygpen-0.1-windows&#39;,
                            &#39;dll_excludes&#39;: [],
                            &#39;excludes&#39;: [&#39;_imaging_gif&#39;,
                                         &#39;_scproxy&#39;,
                                         &#39;clr&#39;,
                                         &#39;dummy.Process&#39;,
                                         &#39;email&#39;,
                                         &#39;email.base64mime&#39;,
                                         &#39;email.utils&#39;,
                                         &#39;email.Utils&#39;,
                                         &#39;ICCProfile&#39;,
                                         &#39;Image&#39;,
                                         &#39;IronPythonConsole&#39;,
                                         &#39;modes.editingmodes&#39;,
                                         &#39;startup&#39;,
                                         &#39;System&#39;,
                                         &#39;System.Windows.Forms.Clipboard&#39;,
                                         &#39;_hashlib&#39;,
                                         &#39;_imaging&#39;,
                                         &#39;_multiprocessing&#39;,
                                         &#39;_ssl&#39;,
                                         &#39;_socket&#39;,
                                         &#39;bz2&#39;,
                                         &#39;pyexpat&#39;,
                                         &#39;pyreadline&#39;,
                                         &#39;select&#39;,
                                         &#39;win32api&#39;,
                                         &#39;win32pipe&#39;,
                                         &#39;calendar&#39;,
                                         &#39;cookielib&#39;,
                                         &#39;difflib&#39;,
                                         &#39;doctest&#39;,
                                         &#39;locale&#39;,
                                         &#39;optparse&#39;,
                                         &#39;pdb&#39;,
                                         &#39;pickle&#39;,
                                         &#39;pyglet.window.xlib&#39;,
                                         &#39;pyglet.window.carbon&#39;,
                                         &#39;pyglet.window.carbon.constants&#39;,
                                         &#39;pyglet.window.carbon.types&#39;,
                                         &#39;subprocess&#39;,
                                         &#39;tarfile&#39;,
                                         &#39;threading&#39;,
                                         &#39;unittest&#39;,
                                         &#39;urllib&#39;,
                                         &#39;urllib2&#39;,
                                         &#39;win32con&#39;,
                                         &#39;zipfile&#39;],
                            &#39;optimize&#39;: 2}},
     &#39;packages&#39;: [&#39;pygpen&#39;],
     &#39;scripts&#39;: [&#39;demo.py&#39;],
     &#39;url&#39;: &#39;http://code.google.com/p/edpath/&#39;,
     &#39;version&#39;: &#39;0.1&#39;,
     &#39;zipfile&#39;: None}

All setup.py Solutions on Gang of Coders

Total of 19 setup.py Solutions