You can see such a file in JoshData/pdfminer/MANIFEST.in or openstack/deb-python-falcon/MANIFEST.in for instance. It is a python project which uses the MANIFEST.in template A MANIFEST.in file can be added in a project to define the list of files to include in the distribution built by the sdist command. When sdist is run, it will look for … Read more
If you have a single-file module like this, no folder will be created, your .py file will be moved directly into the directory which contains the other python modules (/usr/lib/pythonX.X/site-packages/, for example). That’s why you have to create a directory: $ . |– happy_birthday/ |– __init__.py |– art.txt |– MANIFEST.in |– README.rst |– setup.py
TL;DR: The keys in the package_data dictionaries are packages; the values are lists of globs. ” is not a valid name for any Python package. If you want to have bar.txt be installed next to the __init__.py of package foo, use package_data={‘foo’: [‘bar.txt’]} I have the layout: foo/ __init__.py bar.txt setup.py Now, if foo is … Read more
You’ve got an incorrect keyword. It’s extras_require, and it’s supposed to be a dict. setup( name=”django-cherrypy”, … extras_require = { ‘mysterious_feature_x’: [“newrelic”] } )
You can automate most of the work with regular python tools. Let’s start with clean virtualenv. [zart@feena ~]$ mkdir ziplib-demo [zart@feena ~]$ cd ziplib-demo [zart@feena ziplib-demo]$ virtualenv . New python executable in ./bin/python Installing setuptools………….done. Installing pip……………done. Now let’s install set of packages that will go into zipped library. The trick is to force installing … Read more
There is a new technique (Since version 19.1) called Direct references. Just pretend like your file is hosted on localhost. from setuptools import setup path_to_my_project = “/home/user/projects/my_package” # Do any sort of fancy resolving of the path here if you need to setup(# … other arguments install_requires=[f”my_package @ file://localhost/{path_to_my_project}#egg=my_package”] )
I believe what you’re looking for is something like this for you setup.py, which will recursively find any packages in the project, also be sure and include __init__.py files to subdirectories for each package you want. from setuptools import setup, find_packages setup(name=”MySoftware”, packages=find_packages() )
I would recommend using the find_packages() function available with setuptools such as: from setuptools import setup, find_packages and then do packages=find_packages()
It looks like conda automatically adds pip to your conda environment, so after you source your conda environment, i.e.: source activate ~/anaconda/envs/dataset you should be able to install it like this: git clone git://github.com/pudo/dataset.git pip install ./dataset EDIT Here are the exact steps I took: $ conda create -p ~/anaconda/envs/py33 python=3.3 anaconda pip $ source … Read more
Found a solution that worked for me here. Using setuptools==2.0.2 I did: setuptools.setup( … packages=setuptools.find_packages(), include_package_data=True, # use MANIFEST.in during install … )