Re: [jokosher-devel] Planning 0.2
- From: "Stuart Langridge" <sil kryogenix org>
- To: "Stephen Thorne" <stephen thorne id au>
- Cc: jokosher-devel-list gnome org, Laszlo Pandy <laszlok2 gmail com>
- Subject: Re: [jokosher-devel] Planning 0.2
- Date: Mon, 17 Jul 2006 08:19:05 +0100
On 7/17/06, Stephen Thorne <stephen thorne id au> wrote:
>Nice file structure might be nice, but is it really that important?
Yes. It's the difference between having an extensible python application that can be extended cleanly, and a bunch of files that you have to rape+paste or monkeyhack in order to use them externally.
Use case: Alternate tool, based on jokosher's libraries, in order to import jokosher libraries, that tool will have to have every single module named differently, and will have to use sys.path hacks to import jokosher.
If the libs are instead done nicely into a package, it would be trivial to import jokosher libs and mix them with my own code, as jokosher could live in site-packages/jokosher/.
On the other hand, it makes it a little more fiddly to grab the code
and run it *without* installation, I suspect, andone of my goals is
that Jokosher should be relocatable. I suppose the "jokosher"
executable, which would actually be a script, can just "import
jokosher" which would pick it up from . if it's there and
site-packages (which is already on sys.path) if it isn't.
If hard data were the filtering criterion you could fit the entire
contents of the Internet on a floppy disk.
-- Cecil Adams
] [Thread Prev