[Distutils] Buildout + namespace packages + Django management commands?

[Jim Fulton]

On Sun, Sep 20, 2009 at 4:56 AM, Lennart Regebro <regebro at gmail.com> wrote:
> 2009/9/20 Kyle MacFarlane <kylemacfarlane at gmail.com>:
>> I was hoping more if anybody knew a recipe to get round my problem but
>> I had a look inside Django to see how it looks through packages.
>>
>> The problem is caused by line 58 at this link raising an ImportError:
>> http://code.djangoproject.com/browser/django/trunk/django/core/management/__init__.py
>
> Yeah, sorry. You can either use Django, or not use namespaces, or fix Django. :)
> Django simply doesn't support namespaces in this case. Yet another
> case of Django being the new Zope, although Zope has fixed that
> problem since a couple of years, and Zope Products can be namespace
> packages nowadays (and the special Products directory is now a
> namespace).
>
> This all is a part Djangos biggest problem: It doesn't play well with
> non-Django stuff. They are however aware of this problem, and I'm sure
> they would appreciate help with fixing this particular issue. In open
> source it's all a matter of available programmer time. :)

That's BS.  This discussion is is happening because Django is using
buildout, which I think qualifies as "non-Django stuff".  Now, when
someone is asking about a technical problem using a non-Django tool,
they get grief that they're problem is that they don't use non-Django
tools.

Even if this argument had a shred of reason, it is totally
inappropriate to use a response to a technical query as a platform for
advocacy, especially negative advocacy.

Finally, I am ashamed when I see members of the Zope community
bad-mouth other frameworks,

Jim

-- 
Jim Fulton