I'm attempting to use python-dateutil to parse the date output from
Feedparser, but continue to get an error when importing the parser.
I'm building a quick filter in a timeutil.py file in a templatetag
folder on the pythonpath
from dateutil.parser import parse
def parsefeedtime(value):
"""Us
to work.
On Jan 14, 12:12 pm, newspaper-django-lackey
wrote:
> I've had a breakthrough. Evidently some packages that are on the
> python path for the interpreter are not available to my django wsgi
> settings file. I had to put the exact path to parser.py in my wsgi
> setting
Naming conflicts are a consistent issue brought up on the boards. I've
had issues several times where an app name conflicted with a core
Python library, Pluggable, or library extension. Generally the process
I follow for apps, both personally created and pluggable, is to put
them not directly on th
If you are using wsgi you can touch your wsgi settings file and it has
the same effect as restarting apache without a restart most of the
time. If you are only running one site on the django installation it
isn't any better, but if you are hosting multiple sites and your
change is on one settings.p
The others are correct. You can't put block tags inside an include.
It's pretty logical really. The block system cascades down templates
through the "extends" system. Includes are by nature outside that
track. They can be pulled into any template at any point in the
process. Block tags in an includ
Occasionally when I use the include tag, I'm seeing a tokenized hard
return appear before the include. The return shows in both the source
html and in the resulting display. The only way to get rid of this
"hard space" is to remove the include and place the code from the
include directly into the p
6 matches
Mail list logo
