setuptools

I have a custom project package with structure like: package-dir/ mypackage/ __init__.py submodule1/ __init__.py testmodule.py main.py requirements.txt setup.py using cd package-dir followed by $pip install -e . or pip install . as suggested by python-packaging as long as I access the package from package-dir For example : $cd project-dir $pip install . at this point this works: $python -c 'import mypackage; import submodule1' but This does not work $ cd some-other-dir $ python -c 'import mypackage; import submodule1' Traceback (most recent call last): File "<stdin>", line 1, in <module>

我的电脑是windows7的版本， 1.之前就安装 了python27 2，下载了django却总是提示 没有setuptools，我不知道这个还需要单独安装，也不相信要单独安装，为此花费了将近一个小时捯饬，最后还是单独安装了setuptools，此后django安装成功，再设置一下环境变量，添入django和scripts的路径到path 3.下载mysqldb并安装， 至此安装结束，我开始连接了，看django能否练到数据库，先去试试，再来写心得。 来源： oschina 链接： https://my.oschina.net/u/2323085/blog/390911

I'm using namespaces with setuptools to distribute a same module in two different repositories. The goal is to get mymodule.one and mymodule.two installed, knowing that the content of one and two comes from different repos. But it looks like two setup.py sweep each other content. ├── repo1 │ ├── mymodule │ │ ├── __init__.py │ │ └── one │ │ └── __init__.py │ └── setup.py └── repo2 ├── mymodule │ ├── __init__.py │ └── two │ └── __init__.py └── setup.py The namespace has the __init__.py below: test$ cat repo1/mymodule/__init__.py from pkgutil import extend_path __path__ = extend_path(__path__, _

I've got several packages I'm working on, and I'd like to share code between their setup.py scripts. Is there any good way to do this or is code duplication my only option? Martijn Pieters Normally setup.py is the entry point for distribution of distinct packages. As such, it's hard to then share code between those packages. If you use setuptools (or it's fork, distribute ) in your setup.py , you can specify packages that must be installed when installing your package with the setup_requires entry. Unfortunately, your setup.py is executed first; as soon as the setup_requires line is parsed,

I want my setup.py to do some custom actions besides just installing the Python package (like installing an init.d script, creating directories and files, etc.) I know I can customize the distutils/setuptools classes to do my own actions. The problem I am having is that everything works when I cd to the package directory and do "python setup.py install", but my custom classes don't seem to be executed when I do "easy_install mypackage.tar.gz". Here's my setup.py file (create an empty myfoobar.py file in the same dir to test): import setuptools from setuptools.command import install as _install

I like to figure out the myth behind Python's namespace packages by setuptools , and here is what I did test. Make a virtual environment by virtualenv . Find a namespaced package on PyPI . Install that package by pip install . Check the installed file hierarchy. The package I played with is zope.interface and it worked well with the following file hierarchy on my virtualenv: ~virenv/.../site-packages/zope.interface-3.8.0-py2.6-nspkg.pth /zope.interface-3.8.0-py2.6.egg-info/ /zope/ /interface/ /... Everything looked fine and I love the way zope.interface got installed as a real namespaced

I am creating a setup.py to distribute my application. This application has a number of dependencies which can be installed via pip, it also has some custom dependencies which can not be installed from PyPI. So, I have created a custom_package_0.1.whl which will be included into the distribution and must be installed as a dependency after setup.py installs everything from install_requires . Imagine the following app structure: my_app/ win_deps/custom_package_0.1.whl my_app/ __init__.py main.py setup.py setup.cfg How do I do that? There are several options that you can choose from: Upload your