ok, guys, it was indeed the environment, thanks for 'forcing' me again
to look at it.
However, the reason was different: One module expects a different
environment variable to be set, and unfortunately crashed with this
variable missing. Of course, failing modules will just be silently
ignored dur
Before you start python (assuming *nix, including os/x), type:
$ which python
Then, in the subshell, before starting python, type the same thing. Compare.
Bill
On Mon, Oct 5, 2009 at 12:02 PM, Ralph Heinkel wrote:
>
> Hi,
>
> I just checked the environment for PYTHONPATH, it is neither s
On Mon, 2009-10-05 at 09:02 -0700, Ralph Heinkel wrote:
> Hi,
>
> I just checked the environment for PYTHONPATH, it is neither set in
> the parent nor in the subshell.
>
> Actually, I can reduce the problem to this:
>
> 1. In my unix shell I start the python interpreter
> 2. in Python: import
Hi,
I just checked the environment for PYTHONPATH, it is neither set in
the parent nor in the subshell.
Actually, I can reduce the problem to this:
1. In my unix shell I start the python interpreter
2. in Python: import os; os.system('/bin/bash')
3. In the just opened subshell: python manag
On Mon, 2009-10-05 at 15:52 +0200, Ralph Heinkel wrote:
> Hi,
>
> We have an automatic build system with scons and through this we want
> to initialize djangos tables.
>
> This is a weird problem:
> - If I run "python manage.py syncdb" from my unix shell,
>all tables are nicely created.
> -
Hi,
We have an automatic build system with scons and through this we want
to initialize djangos tables.
This is a weird problem:
- If I run "python manage.py syncdb" from my unix shell,
all tables are nicely created.
- If run run the same command from a SConstruct script,
only django's sy
6 matches
Mail list logo
