I corrected the build_ext error and successfully built/installed by
adding the full path to pg_config in setup.cfg.
On Jun 23, 10:19 am, Chris Haynes wrote:
> Using what I believe is the latest version of psycopyg, I get:
>
> 509 ~/Desktop/psycopg2-2.0.9$ python setup.py build
> running build
>
Apache is the easiest and most documented route. It is pretty easy to
set-up and config so don't let that put you off.
However, I had a situation where I needed a single self-contained
install for deployment. On that occasion I used CherryPy3 + WSGI and
ran the whole thing as a windows serv
like python setuptools to install django and the
> project. The http server must be run in python. Have to install
> sqlite manually?
>
> It seems 2) is better but it might still be too complex to install.
> Still evaluating my options now...
>
> On Aug 10, 5:36 pm, Justin John
I've managed to get Django working nicely with CherryPy using WSGI.
Previously I've deployed Django with Apache and ModPython where each
requested is serviced by a separate Python instance.
This isn't the case with CherryPy though as it's thread based which
leads me to the following concern:
ery careful with parallel requests.
Justin
> On Aug 29, 1:39 am, Justin Johnson <[EMAIL PROTECTED]> wrote:
>
>> I've managed to get Django working nicely with CherryPy using WSGI.
>> Previously I've deployed Django with Apache and ModPython where each
>>
There may be a performance issue for large object sets and retrieving
all tags:
def tag_list(request):
all_tags = TaggedItem.objects.order_by('tag')
tag_names = {}
for tag in all_tags:
if tag.tag not in tag_names:
tag_names[tag.tag] = tag
names = sorted(tag_
Django really does need stream uploading. IIRC, there's a patch to
do this.
Does anyone know if that patch is ever going to make it into an
official release?
On 25 Jan 2007, at 02:08, Jeremy Dunck wrote:
>
> On 1/24/07, Julio Nobrega <[EMAIL PROTECTED]> wrote:
>>
>> Uploading a video i
I'm completely new to GeoDjango. I'm working through the tutorial for
Django version 2.0, and I am encountering an error when I follow the steps
in the GeoDjango section.
Specifically, when I attempt to slice a Layer object to extract Features,
it gives me an error which looks like a poss
I have a user who saw how new objects can be created using the Admin forms,
and asked if I could reproduce some of that functionality. I'm still new
to Django, and even newer to building forms. I'm wondering if there is a
way to "borrow" elements from the Admin forms into my own forms and
tem
9 matches
Mail list logo
