Re: Modular Django

[lugal]

> That's cool -- mind posting your code somewhere?

http://cheeseshop.python.org/pypi/urlrelay/

CheeseShop and setuptools makes installation of even my trivial modules
on my webhost and other places I need it convienient.

>> 1) Develop a loosely coupled module that acts like the "usual" Python
>> module
>> 2) Develop a piece of WSGI middleware
>> 3) Something else
>
> Personally, I would lean towards #1, but since Django modularity
> isn't an itch I have, chances are someone with a more pressing need
> will beat me to it.

At least in the case of urlresolvers, the existing loose coupling of
Django's modules following the approach of #1 to some extent made #2
relatively painless. That may be as good a way to go it as any.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Modular Django

[lugal]

For a personal project, I modified Django's urlresolvers module to make
it into a piece of WSGI middleware. I liked Django-style URL
dispatching but I didn't need the whole framework.

>From that experience, I can see at least a few ways to modularize
Django components:

1) Develop a loosely coupled module that acts like the "usual" Python
module
2) Develop a piece of WSGI middleware
3) Something else

I'm curious where Django modularity is going in the future, all things
remaining equal.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---