[Grok-dev] Re: Python UK meeting and Django

[Martijn Faassen]

Hi there,

Brandon Craig Rhodes wrote:
[snip]
> I am happy to report that Martijn is exactly correct; the module
> versions installed by "easy_install grok" no longer prevent the user
> from finding out that he's supposed to use "grokproject", and when he
> does, the buildout environment ignores the wrong-versioned packages in
> site-packages which, while they take up space, don't prevent Grok from
> then running successfully.

This is good news! Thanks for trying this out.

> I have a slight guess that some novices probably expect "grokproject"
> to be a script that comes with "grok", until they realize that it's
> its own module rather than just being something that "comes with" the
> "grok" module itself.

Hm. We could add a dependency to 'grokproject' to 'grok', so that it'll 
appear even if you do the wrong thing. You'd have to sit through all the 
downloads again when you first run grokproject, but least you can proceed.

Are there any drawbacks to this idea? It's just covering all the bases; 
I wouldn't propose that this way to install things would in any way 
become official.

Regards,

Martijn