>> >> Does anybody else actually do this? Last I checked, Pylons, >> TurboGears >> and Zope apps didn't install or need to be installed into >> framework-specific locations. Django applications are just Python >> modules, and that's a *strength* from where I sit. > > 100% with James here. I had a discussion about namespace packages [1] > with Mark Ramm at PyCon, and hist short answer was "don't do it, it > isn't worth it". Seeing as he's the maintainer of TurboGears and > probably knows setuptools about as well as anyone, I'd tend to trust > him on that one. I understand the appeal, but the consequences aren't > worth it. > > J
+1 on just packaging stuff as eggs, and being able to easy_install them. Works great with my buildout infrastructure for managing Django builds too. I wouldn't worry about putting stuff that's not useful outside a Django context up; that's exactly what the categories system is for. There's plenty of Zope stuff there, for example, and I personally haven't seen any complaints. Maybe I just missed them. On the namespace package front, I'd be wary; I started trying to use them, but a client of mine on Windows has experienced problems using them in Django (in places where some __import__ magic is done). I'll raise a ticket when I get down to a minimal example. Cheers, Dan -- Dan Fairs <[EMAIL PROTECTED]> | http://www.stereoplex.com/ --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
