Hi Wouter,
I am having this same issue (or a very similar one - I am using Centos 8),
and this is the only place I have seen someone else with it. Do you mind
sharing your solution? I have the packages installed as suggested by DANIEL
URBANO DE LA RUA, and I see on the docs that geodjango supor
I had the same issue yesterday with geodjango and this MemoryError and
managed to find out it was caused by selinux. I wrote a custom selinux
httpd policy, which took me a couple of iterations because after fixing one
sealert I ran into the next.
If you are still looking for a solution and inter
thanks but i already did it, and the error is still there...i just have a
question, does geodjango has support gdal 3.0?
El jue., 5 dic. 2019 a las 17:13, DANIEL URBANO DE LA RUA (<
dannybombas...@gmail.com>) escribió:
> In your case use yum to get thoses package
>
> On Fri, 6 Dec 2019, 00:12 DAN
In your case use yum to get thoses package
On Fri, 6 Dec 2019, 00:12 DANIEL URBANO DE LA RUA,
wrote:
> Try installing apt-ger install binutils libproj-dev gdal-bin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from thi
Try installing apt-ger install binutils libproj-dev gdal-bin
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view t
Try installing apt-ger install binutils libproj-dev gdal-bin
On Fri, 6 Dec 2019, 00:01 Fernando González Cisneros, <
hellhammerh...@gmail.com> wrote:
> Hello, having some trouble here.
>
> I'm developing an app using the postgis backend in django, i'm releasing
> it using an apache server on Cent
Hello, having some trouble here.
I'm developing an app using the postgis backend in django, i'm releasing it
using an apache server on Centos 7, i'm using mod_wsgi for python 3.6 and
i've already published a test "hello world" app without trouble, however
when i try to publish my app a 500 inte
On Wed, 2009-08-05 at 13:09 -0700, drakkan wrote:
> The code is something like this
>
> obj=DBModels.objects.filter(somefilter)
> results=[]
> for o in obj:
> results.append({'field1':o.field1,'field2':o.field2})
>
> return JsonResponse(results)
>
> where JsonResponse is a class derived from
On 08/05/2009 04:09 PM, drakkan wrote:
> The code is something like this
>
> obj=DBModels.objects.filter(somefilter)
> results=[]
> for o in obj:
>results.append({'field1':o.field1,'field2':o.field2})
>
> return JsonResponse(results)
>
> where JsonResponse is a class derived from HttpResponse
The code is something like this
obj=DBModels.objects.filter(somefilter)
results=[]
for o in obj:
results.append({'field1':o.field1,'field2':o.field2})
return JsonResponse(results)
where JsonResponse is a class derived from HttpResponse that add a
simplejson.dumps
I have a really large databa
On 08/05/2009 12:26 PM, drakkan wrote:
> No I'm not serving static file I have a very large json file
> dinamycally generated (based on a db query)
>
Please post the relevant view and model code, so we can see what's
happening. Also, if your db query is actually a really large number of
db
No I'm not serving static file I have a very large json file
dinamycally generated (based on a db query)
On 5 Ago, 15:28, Mike Ramirez wrote:
> On Wednesday 05 August 2009 04:08:15 am drakkan wrote:
>
>
>
> > here is the excpetion returned while trying to serve a large file:
>
> > Traceback:
> >
On Wednesday 05 August 2009 04:08:15 am drakkan wrote:
> here is the excpetion returned while trying to serve a large file:
>
> Traceback:
> File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py"
> in get_response
> 92. response = callback(request, *callback_args,
>
No sorry isn't a file upload but is django to serve a large file
On 5 Ago, 13:47, krylatij wrote:
> tryhttp://docs.djangoproject.com/en/dev/ref/settings/#file-upload-max-me...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
try
http://docs.djangoproject.com/en/dev/ref/settings/#file-upload-max-memory-size
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups
here is the excpetion returned while trying to serve a large file:
Traceback:
File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py"
in get_response
92. response = callback(request, *callback_args,
**callback_kwargs)
File "/usr/lib/python2.4/site-packages/django/co
On 5/12/06, arthur debert <[EMAIL PROTECTED]> wrote:
> This only happens when uploading large files (+1 MB) on the admin
> interface.
Related:
Jason from TextDrive replied to the TXD forum thread on this issue[1]
and indicated that it's probably due to the file being stored in
memory during uplo
I have an app deployed on lighttpd, but I am getting this memory error.
My local codebase runs fine (both on the devserver and on my local
lighttpd),which leads me to think it's a server issue. I am hosted on
textdrive - we're running lighttp + fcgi.
This only happens when uploading l
18 matches
Mail list logo
