debian/cubicweb-dev.install
author David Douard <david.douard@logilab.fr>
Tue, 03 Mar 2015 12:26:47 +0100
changeset 11152 fccc6ddd975c
parent 10891 5f0442600a3b
permissions -rw-r--r--
[skeleton] do not import the __pkginfo__.py module to make cubes installable via setuptools When using a simple "import" statement, running 'python setup.py install' for a cube fails in a fresh virtualenv due to the fact the install of the dependencies (here cubicweb iteself) is done by the python process doing the cube's installation, so the __pkginfo__ module from the cube is already loaded (thus used) when installing cubicweb... So we apply the third technique from: https://packaging.python.org/en/latest/single_source_version.html

usr/lib/python2*/*-packages/cubicweb/devtools/
usr/lib/python2*/*-packages/cubicweb/skeleton/
usr/lib/python2*/*-packages/cubicweb/test
usr/lib/python2*/*-packages/cubicweb/dataimport/test
usr/lib/python2*/*-packages/cubicweb/entities/test
usr/lib/python2*/*-packages/cubicweb/ext/test
usr/lib/python2*/*-packages/cubicweb/server/test
usr/lib/python2*/*-packages/cubicweb/sobjects/test
usr/lib/python2*/*-packages/cubicweb/hooks/test
usr/lib/python2*/*-packages/cubicweb/web/test
usr/lib/python2*/*-packages/cubicweb/etwist/test