On 13 September 2013 18:12, nils wrote:
> I had a problem along the same lines, it turned out that uwsgi was compile
> with python 3.3 support.
>
> This was Ubuntu 13.04 and I installed it via apt-get , check the entire
> uwsgi logs for the python version.
>
>
> Thanks for this. I only came bac
This is now done in 2.6.1
On Friday, 13 September 2013 14:05:39 UTC-5, Michele Comitini wrote:
>
> @niphlod I'd prefer having everything under the gluon namespace
>
> import gluon.
>
>
> 2013/9/13 nils >
>
>> Hi,
>>
>> I had a problem along the same lines, it turned out that uwsgi was
>> compile
@niphlod I'd prefer having everything under the gluon namespace
import gluon.
2013/9/13 nils
> Hi,
>
> I had a problem along the same lines, it turned out that uwsgi was compile
> with python 3.3 support.
>
> This was Ubuntu 13.04 and I installed it via apt-get , check the entire
> uwsgi logs
Hi,
I had a problem along the same lines, it turned out that uwsgi was compile
with python 3.3 support.
This was Ubuntu 13.04 and I installed it via apt-get , check the entire
uwsgi logs for the python version.
regards,
Nils
On Fri, Sep 13, 2013 at 10:48 AM, Johann Spies wrote:
> On 12 Septe
On 12 September 2013 03:52, Massimo Di Pierro wrote:
In both cases print the sys.path.
>
>
On 'spyker' where the problem is:
$ python web2py.py -M -S alterit
web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2013
Version 2.5.1-stable+timestamp.2013.06.06.15.39.19
Database drivers
+1
2013/9/12 Massimo Di Pierro
> I agree. Less ambiguitiy
>
>
> On Thursday, 12 September 2013 02:18:32 UTC-5, Niphlod wrote:
>>
>> usually this is due to gluon not being in sys.path directly.
>>
>> BTW: we should adopt something standard in imports too throughout all
>> the code. Either we d
so let's go for all imports done prefixing them with gluon or the other one
? I'll put it in the roadmap ^_^
On Thursday, September 12, 2013 11:26:17 PM UTC+2, Michele Comitini wrote:
>
> +1
>
>
>
> 2013/9/12 Massimo Di Pierro >
>
>> I agree. Less ambiguitiy
>>
>>
>> On Thursday, 12 September 201
I agree. Less ambiguitiy
On Thursday, 12 September 2013 02:18:32 UTC-5, Niphlod wrote:
>
> usually this is due to gluon not being in sys.path directly.
>
> BTW: we should adopt something standard in imports too throughout all the
> code. Either we do
> from gluon.module import something
> or
>
usually this is due to gluon not being in sys.path directly.
BTW: we should adopt something standard in imports too throughout all the
code. Either we do
from gluon.module import something
or
from module import something
I vote for the 1st option.
Il giorno giovedì 12 settembre 2013 03:52:18
In both cases print the sys.path.
On Wednesday, 11 September 2013 16:11:07 UTC-5, Johann Spies wrote:
>
> I have (as far as I can see) identical configurations on two debian
> computers. On one nginx with uwsgi works. On the other, however, I get
> the following uwsgi-error in the logs:
>
> We
10 matches
Mail list logo
