By default, when installing a package as root, relative directory names in the data_files list are are resolved against either the value of sys.prefix (for pure-python libraries) or sys.exec_prefix (for libraries with a compiled extension), so you can retrieve your files based on that. Qouting from the distutils documentation: If directory is a relative path, … Read more
Yes, in the documentation of the setuptools. Here it is: https://setuptools.readthedocs.io/en/latest/userguide/declarative_config.html
That’s because that file has a configure.py not a setup.py. configure.py generate a make file that you use to build pyqt against the qt lib you choose by passing –qmake option to configure.py, it has different options too. I suggest filing a bug with the pip maintainer.
This argument for setuptools uses the PEP440 version specifiers spec, so you can ask for: python_requires=”>=2.7,!=3.0.*,!=3.1.*” The commas , are equivalent to logical and operator. Note that the metadata generated is only respected by pip>=9.0.0 (Nov 2016).
platforms is an argument the setuptools package inherits from distutils; see the Additional meta-data section in the distutils documentation: Meta-Data: platforms Description: a list of platforms Value: list of strings So, yes, using a list is the correct syntax. The field just provides metadata; what platforms does the package target. Use this to communicate to … Read more
You’ll need to create a MANIFEST.in file and include some simple instructions on what extra files you want to include (See MANIFEST.in Template) Example (to include docs dir and all files directly underneath): include docs/* or, to include all files in the doc dir (recursively): recursive-include docs *
When you invoke ansible from the shell, bash will search in your $PATH for a file named ansible that is executable. This may not be the only issue, but this is the immediate cause for the error you’re seeing. The .egg file itself is not an executable, it’s just a file used for distributing the … Read more
Update July 2022: if your TOML file uses setuptools as its build system, setuptools will happily create and install a command-line script. For example, my pyproject.toml file starts like this: [build-system] requires = [“setuptools>=61.0”] build-backend = “setuptools.build_meta” Extend your pyproject.toml file with an entry like this, naming the package, module and entry-point function names: [project.scripts] … Read more
You get an ImportError, because the module in question is not in sys.path or not accessible, because of some file system permissions. Here’s a script to check file system permissions of a given distribution, group and name. chk_perm.py from pkg_resources import get_distribution import os import sys dist, group, name = sys.argv[1:] dist = get_distribution(dist) location … Read more
This is like using the src-layout for the “foo” and “bar” packages, but the flat layout for “baz”. It’s possible, but requires some custom configuration in the setup.py. Setuptools’ find_packages supports a “where” keyword (docs), you can use that. setup( … packages=( find_packages() + find_packages(where=”./bar-pack”) + find_packages(where=”./foo-pack”) ), … ) Since find_packages returns a plain … Read more