re is a mod_php
conflict addressed there.)
So if you are looking to run mod_php4 and mod_python, yes, there could
be a problem. The FAQ link gives some pointer on how to compile php to
avoid trouble.
-- Wade Leftwich
Ithaca, NY
--~--~-~--~~~---~--~~
You received
Ned Batchelder wrote:
> Why not use the existing Python Cheeseshop
> (http://cheeseshop.python.org/pypi) for this? Advantages:
>
> 1) You don't have to build anything, it's already there.
> 2) More visibility for Django: with a Django-specific repository, only
> Django developers will see the pac
').encode('latin1',
'xmlcharrefreplace')
In [8]: u'\u2014'.encode('utf-8')
Out[8]: '\xe2\x80\x94'
In [9]: utf8tolatin1('\xe2\x80\x94')
Out[9]: '—'
Also see:
http://www.oreillynet.com/onlamp/blog/2006/01/turning_mysql_data_in_latin1_t.html
Solr does look good. I'm checking it out along with NXLucene
(http://www.cps-project.org/sections/projects/nxlucene) , which is a
similar architecture (search server with an XML API), built with
pyLucene and Twisted.
-- Wade Leftwich
Ithac
clients sight this week and don't want any surprises! =)
>
> Iain
sudo /etc/init.d/apachectl graceful
This will restart apache after it finishes serving current requests
-- Wade Leftwich
Ithaca, NY
--~--~-~--~~~---~--~~
You received this message beca
one
search server that you load via a web API. The advantage to this
approach is that you can integrate search across multiple saites and
applications.
-- Wade Leftwich
Ithaca, NY
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
use this technique for a scheduled task application written in
> Django. It works well, avoids the threading issues, and in my case is
> good enough for the problem at hand.
>
This is a commonly used pattern in the Zope world (where I'm coming
from). An advantage to doing it like this is t
EST_URI' key
in the environment -- instead it gives you PATH_INFO.
So change line 31 to this:
site_id, cachekey = fjlib.getcurrentsite(request.META['HTTP_HOST'],
(request.META.get('REQUEST_URI') or request.META.get('PATH_INFO') or
'/
g, so people with titles like Web Producer can edit
templates through a web interface, and we can use the content database
for managing the templates.
Has this approach -- putting templates in the DB -- been tried with Django?
Wade Leftwich
Ithac
9 matches
Mail list logo