Hi friends,
I have a project that has its root somewhere on my machine.
This project has many folders and contains quite some modules.
There is a common root of the module tree, and I want to use
- either absolute imports
- relative imports with '.'
Problem:
- I want to run any module inside
Once again on this:
With the introduction of module folders
without __init__, it has become even harder to deduce a sensible project root
Dir without relying on a global settings file. Abd as you probably agree, such
files are a bad idea. Any global is bad, also in the file system.
Guido, this
On Sun, Nov 11, 2012 at 1:53 PM, Christian Tismer wrote:
> Once again on this:
>
> With the introduction of module folders
> without __init__, it has become even harder to deduce a sensible project
> root
> Dir without relying on a global settings file. Abd as you probably agree,
> such files are
Hi Eric,
On 11.11.12 22:45, Eric Snow wrote:
On Sun, Nov 11, 2012 at 1:53 PM, Christian Tismer
mailto:tis...@stackless.com>> wrote:
Once again on this:
With the introduction of module folders
without __init__, it has become even harder to deduce a sensible
project root
Dir
The only way I know how to do it is to have my cwd set to the directory I
want on sys.path, then use -m for script execution (using a separate shell
session for anything where I want a different working directory).
I don't know of any way to handle a varying cwd without manipulating the
path direc
