Yeah. It was that.
In this mail this become clear
(http://www.mail-archive.com/distutils-sig@python.org/msg00439.html )
it seems the semi-colons are needed in .pth files, and i was using
indentation as in python files. Thank you.
--adso
On Tue, Dec 14, 2010 at 2:23 AM, P.J. Eby wrote:
> At 01
At 01:54 AM 12/14/2010 +0100, adso wrote:
Hi,
i am doing something wrong probably, but when i try to get a custom
site-packages location in Debian, i need to set the contents of
altinstall.pth just several line with the absolute paths.
If i use the usual python code with site.addsitedir(...
At 05:11 PM 12/13/2010 -0600, Brad Allen wrote:
Where I work we're considering a change to moving a group of packages
to using namespaces. We want the namespace paths to reflect a
dependency hierarchy,
Note that you don't *need* to use namespace paths to reflect
dependencies; the main purpose
Hi,
i am doing something wrong probably, but when i try to get a custom
site-packages location in Debian, i need to set the contents of
altinstall.pth just several line with the absolute paths.
If i use the usual python code with site.addsitedir() in
altinstall.pth the directories are not add
On Mon, Dec 13, 2010 at 5:57 PM, "Martin v. Löwis" wrote:
> You can't put code into __init__.py of any of the namespace packages.
> Otherwise, having additional modules in any of these packages is fine.
Ok, that answers my question. Thanks!
___
Distuti
Am 14.12.2010 00:11, schrieb Brad Allen:
> Where I work we're considering a change to moving a group of packages
> to using namespaces. We want the namespace paths to reflect a
> dependency hierarchy, and the current plan requires putting some
> source code into actual module distributions at the l
Where I work we're considering a change to moving a group of packages
to using namespaces. We want the namespace paths to reflect a
dependency hierarchy, and the current plan requires putting some
source code into actual module distributions at the level of some of
the namespace packages.
Example:
On 10.12.2010 13:42, Brian Sutherland wrote:
The current method using dpkg-divert is not too bad, more packages than
python-zope.interface could include that file as well. So you don't
force installation of python-zope.interface.
It also uses standard dpkg functionality, which is a robustness bo
A quick look through the Distribute docs shows that we call the
settings we give to setup py various things. Both "options" and
"arguments" and "parameters" (that last is my fault).
We should probably decide on one thing, and go through the docs to
make sure it's consistent. I prefer "option", alt
