Menu
I know MANIFEST.in recognizes relative paths. However, can I use relative paths that point to directories outside of the project?
For example:
/home
/random_dir
/python_project
MANIFEST.in
setup.py
/packages
And then inside MANIFEST.in
graft ../random_dir/
If not, is there an alternative way of including such directories other than just copying and pasting the directory into the project?
266
Source Distribution (or “sdist”) A distribution format (usually generated using python setup.py sdist ) that provides metadata and the essential source files needed for installing by a tool like pip, or for generating a Built Distribution. System Package.
The MANIFEST.in file contains commands that allow you to discover and manipulate lists of files. There are many commands that can be used with different objectives, but you should try to not make your MANIFEST.in file too fine grained.
The setup. cfg is an ini file, containing option defaults for setup.py commands. You can pretty much specify every keyword we used in the setup.py file in the new setup. cfg file and simply use the setup.py file as the command line interface.
The setup.py file may be the most significant file that should be placed at the root of the Python project directory. It primarily serves two purposes: It includes choices and metadata about the program, such as the package name, version, author, license, minimal dependencies, entry points, data files, and so on.
I tested it for you . It seem to not want to go any lower than the project root.
Use a symlink instead. Depending on the data and your workstructure, a git submodule could solve your situation better.
147
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
