gzz-dev
[Top][All Lists]
Advanced

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

Re: [Gzz] Pegs


From: Benja Fallenstein
Subject: Re: [Gzz] Pegs
Date: Fri, 28 Mar 2003 16:01:28 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319 Debian/1.3-3

Tuomas Lukka wrote:
On Fri, Mar 28, 2003 at 02:11:18PM +0100, Benja Fallenstein wrote:

Tuomas Lukka wrote:

Well, As said, I'm working for this, progressing and learning slowly the
differences between Java and python package/object model :)

;) Have fun... And remember also jython sometimes screws up badly.

Remember that using only the first org/ directory on the path may not be screwing up, but design (in Python). If there are two org/ directories, whose __init__.py would define the package?

This is exactly what learning the differences between Java's and Python's packages means...


Hmmmmmmmm...

So in essence we could actually best work around it by making the python 
classpath point
not to the same point as the Java classpath but to the first unique componend,
i.e. fenfire, libvob, alph, storm?

Yeah, right. That would be more like Python packages, I think.

The idea about Python packages is that they are multiple modules bundled into a single new module, I think. So 'org' isn't really a good Python package-- it's not anything in itself. 'storm', on the other hand, is actually a package in its own right... (hum, anybody following?)

Here's an article about Python packaging:

    http://www.python.org/doc/essays/packages.html

Quote from the top of one specific section:

    Warning: the following may be confusing for those who are familiar
    with Java's package notation, which is similar to Python's, but
    different.

;-)

- Benja





reply via email to

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