r...@zedat.fu-berlin.de (Stefan Ram) writes:
> "Loris Bennett" writes:
>>However, in the development environment, if I run
>> python stoat/main.py hpc user --help
>>then is
>> stoat/hpc/main.py
>>being found via
>> import hpc.main
>>because Python looks in
>> stoat
>>as the parent directory
Hi Stefan,
r...@zedat.fu-berlin.de (Stefan Ram) writes:
> "Loris Bennett" writes:
>>Why is the module 'hpc' not found by the poetry script?
>
> I have tried to execute the following sequence of shell
> commands to understand your problem. Here they all worked
> without error messages. Warn
r...@zedat.fu-berlin.de (Stefan Ram) writes:
> "Loris Bennett" writes:
>>However, this raises the question of why it worked in the first place
>>in the poetry shell.
>
> It might have had a different or extended sys.path.
In the poetry shell sys.path has this additional path
/home/loris/gi
"Loris Bennett" writes:
> Hi,
>
> The following is a little bit involved, but I hope can make the problem clear.
>
> Using poetry I have written a dummy application which just uses to typer
> to illustrate a possible interface design. The directory structure is a
> follows:
>
> $ tree -P *.py
Hi,
The following is a little bit involved, but I hope can make the problem clear.
Using poetry I have written a dummy application which just uses to typer
to illustrate a possible interface design. The directory structure is a
follows:
$ tree -P *.py
.
|-- dist
|-- stoat
| |-- hpc
