[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] first crack at distutils

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] first crack at distutils
Date: Sun, 22 Feb 2004 10:58:23 +0100
User-agent: Mutt/

> I think a script like this would work for me:
> PYTHONPATH=/home/david/cvs/gnumed/gnumed
No. PYTHONPATH may already contain pathes so you need to *add*
to them.

> /home/david/cvs/gnumed/gnumed/client/wxwindows/
wxPython, client/wxwindows would be a C / C++ client

> The only annoying thing is that "client" is the base package name.  I'd 
> rather have the name gnumed-client.  Or I can make the "gnumed" 
> directory a package.  But then we'd always have to be importing 
><modulename> or something like that.  Actually I 
> kind of like that.  And there are some python modules outside of client, 
> which maybe are useful as well.... I makes sense to have the base 
> package called gnumed too doesn't it?  I'll make the fixes tonight.   
> The script would change to:
> PYTHONPATH=/home/david/cvs/gnumed
> /home/david/cvs/gnumed/gnumed/client/wxwindows/
> All imports would start from gnumed.something.something, instead of 
> client.something.something..... 

This sounds premature to me and needs more though. IMO, before
changing the way we use import we better think twice about our
directory layout and fix that first. Let's cool our temper
before attempting to do such changes.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]