setuptools

问题 What is the purpose of the namespace_packages argument in setup.py when working with PEP420 namespace packages (the ones without __init__.py)? I played with it and saw no difference whether I declared the namespace packages or not. "setup.py install" and "pip install ." worked in any case. I am building an automatic setup.py code generator and would be happy not to handle this if this is not necessary. 回答1: As long as you: aim for Python 3.3 and newer or Python 2.7 with importlib2 dependency

问题 I have a package with a structure that would (simplified) look like: mypackage/ __init__.py setup.py module1.py module2.py mysubpackage/ __init__.py mysubmodule1.py mysubmodule2.py I'm using a configuration for setup.py like this: from setuptools import setup, find_packages setup( name = "mypackage", version = "0.1", author = "Foo", author_email = "foo@gmail.com", description = ("My description"), packages=find_packages(), ) The default where argument for find_packages() is '.' , but it doesn

问题 I have read several similar topics but haven't succeeded yet. I feel I miss or misunderstand some fundamental thing and this is the reason of my failure. I have an 'application' written in a python which I want to deploy with help of standard setup.py. Due to complex functionality it consists of different python modules. But there is no sense in separate release of this modules as they are too specific. Expected result is to have package installed in a system with help of pip install and be

问题 I have read several similar topics but haven't succeeded yet. I feel I miss or misunderstand some fundamental thing and this is the reason of my failure. I have an 'application' written in a python which I want to deploy with help of standard setup.py. Due to complex functionality it consists of different python modules. But there is no sense in separate release of this modules as they are too specific. Expected result is to have package installed in a system with help of pip install and be

问题 I have read several similar topics but haven't succeeded yet. I feel I miss or misunderstand some fundamental thing and this is the reason of my failure. I have an 'application' written in a python which I want to deploy with help of standard setup.py. Due to complex functionality it consists of different python modules. But there is no sense in separate release of this modules as they are too specific. Expected result is to have package installed in a system with help of pip install and be

问题 I have read several similar topics but haven't succeeded yet. I feel I miss or misunderstand some fundamental thing and this is the reason of my failure. I have an 'application' written in a python which I want to deploy with help of standard setup.py. Due to complex functionality it consists of different python modules. But there is no sense in separate release of this modules as they are too specific. Expected result is to have package installed in a system with help of pip install and be

问题 I have read several similar topics but haven't succeeded yet. I feel I miss or misunderstand some fundamental thing and this is the reason of my failure. I have an 'application' written in a python which I want to deploy with help of standard setup.py. Due to complex functionality it consists of different python modules. But there is no sense in separate release of this modules as they are too specific. Expected result is to have package installed in a system with help of pip install and be

问题 Pip supports the pyproject.toml file but so far all practical usage of the new schema requires a 3rd party tool that auto-generates these files (e.g., poetry and pip). Unlike setup.py which is already human-writeable, pyproject.toml is not (yet). From setuptools docs, [build-system] requires = [ "setuptools >= 40.9.0", "wheel", ] build-backend = "setuptools.build_meta" However, this file does not include package dependencies (as it should not in PEP518 which only deals with build dependencies

问题 I have written a Python extension module in C++. I plan to distribute the module with setuptools. There will be binary distributions for 32- and 64-bit Windows (built with setup.py bdist_egg ) and a source distribution for UNIX-like platforms (built with setup.py sdist ). I plan to license the module under the BSD license. In my source tree, the file LICENSE.txt is in the top folder along with setup.py. How should I include it in the installation package? I tried the following setup.py script

问题 I have written a Python extension module in C++. I plan to distribute the module with setuptools. There will be binary distributions for 32- and 64-bit Windows (built with setup.py bdist_egg ) and a source distribution for UNIX-like platforms (built with setup.py sdist ). I plan to license the module under the BSD license. In my source tree, the file LICENSE.txt is in the top folder along with setup.py. How should I include it in the installation package? I tried the following setup.py script