Hi Daniel,
no, I was not aware of this. I just read it up on
http://sayspy.blogspot.de/2010/03/various-ways-of-distributing-python.html
Yeah, thank you very much for this hint, very useful! ;-)
cheers - Chris
On 16.11.12 04:22, Daniel Holth wrote:
Are you familiar with executing directories
Are you familiar with executing directories having __main__.py as python
scripts?
Daniel Holth
On Nov 15, 2012, at 4:43 PM, Christian Tismer wrote:
> Hi Kristjan,
>
> does that mean that your scheme simply works, without any config step
> necessary after I did my checkout?
> This would in fac
Hi Kristjan,
does that mean that your scheme simply works, without any config step
necessary after I did my checkout?
This would in fact be an interesting alternative to
Python setup.py develop
but I'm not sure if this is the same scheme on windows and Os X.
Getting this part right was ra
When python is being run from a compile environment, it detects this by looking
for "Lib" folders in directories above the one containing the executable.
(I always thought that this "special" execution mode, hardwired in, was a bit
odd, and suggested that this could be made a function of pep405)
Hi Nick, Holger,
this is a crazy fault of mine, see the end below.
I wrote:
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
- relati
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
