User template-tag behavior inconsistent between apache2 mod_python and development server

[pootow@…]

If the template-tag name and the project's name are the same, then, development server runs fine, and mod_python breaks.

[pootow@…]

for example:

if my project's name is "myproject", and I have a application "myapp".

The directory structure follows the default rule.

I have a "tamplatetags" directory in "myapp", and "myproject.py" is just in that "templatetags" directory.

That's it.

[Graham.Dumpleton@…]

What is the actual exception traceback you get?

Are you sure this isn't a configuration problem with your mod_python setup whereby you haven't set PythonPath directive properly based on how you are using Django.

See post:

​http://groups.google.com/group/django-users/browse_frm/thread/24deb095a2b2e450/1c982558d464017a

You may have to add the actual site directory as well as the parent directory to PythonPath.

The post talks about urls file, but may also apply to your case.

[Simon G. <dev@…>]

marked as invalid until someone can confirm this w.r.t Graham's comment above. If this is a valid clash, and not a config. glithc please re-open.