En Thu, 06 Sep 2007 14:41:42 -0300, Samuel <[EMAIL PROTECTED]> escribi�:
> On Sep 6, 6:44 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote:
>> On 6 sep, 13:13, Samuel <[EMAIL PROTECTED]> wrote:
>>
>> That's fine, and a good requirement. Place start2.py inside the
>> container directory, and your pac
On Sep 6, 6:44 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote:
> On 6 sep, 13:13, Samuel <[EMAIL PROTECTED]> wrote:
>
> > On Sep 6, 5:44 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote:
> > > They should import the package as any other
> > > client code, without doing any import tricks nor playing
On 6 sep, 13:13, Samuel <[EMAIL PROTECTED]> wrote:
> On Sep 6, 5:44 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote:
> > They should import the package as any other
> > client code, without doing any import tricks nor playing with
> > sys.path.
>
> Why does it matter whether I install it in sys.pa
On Sep 6, 6:13 pm, Samuel <[EMAIL PROTECTED]> wrote:
> Why does it matter whether I install it in sys.path or whether
> sys.path is modified? What's the difference?
>
> What I am doing is I ship two modules in one tarball with my software.
> The software is only unpacked and ran. It has to work wit
On Sep 6, 5:44 pm, Gabriel Genellina <[EMAIL PROTECTED]> wrote:
> On 6 sep, 08:47, Samuel <[EMAIL PROTECTED]> wrote:
> > Given the following directory structure:
>
> > -
> > |-- Obj.py
> > |-- __init__.py
> > |-- foo
> > | |-- FooTest.py
> > | `-- __init__.py
> > `-- start1.py
> > -
On 6 sep, 08:47, Samuel <[EMAIL PROTECTED]> wrote:
> Given the following directory structure:
>
> -
> |-- Obj.py
> |-- __init__.py
> |-- foo
> | |-- FooTest.py
> | `-- __init__.py
> `-- start1.py
> -
The container looks like a package (you didn't tell us the name).
Should be p
Hi,
Given the following directory structure:
-
|-- Obj.py
|-- __init__.py
|-- foo
| |-- FooTest.py
| `-- __init__.py
`-- start1.py
-
With the following content:
-
$ cat Obj.py
class Obj(object):
pass
$ cat __init__.py
import Obj
__all__ = ['Obj']
$ cat foo/FooT
